Troubleshooting & Reference · Article 7.20
"The page looks broken on my phone / specific browser"
Clozo targets evergreen browsers (Chrome, Edge, Firefox, Safari last 2 versions) on desktop, and Safari/Chrome on iOS/Android. Outside that matrix (older browsers, niche mobile webviews) rendering can break.
Most freelancers don't see browser issues themselves — but clients sometimes do, especially if they open the proposal link from inside a social media app's embedded browser. The fix is simple: open in a real browser.
Step by step
Identify the browser.
Ask the client where they opened the link (which app).
Tell them to open in their main browser.
Most in-app browsers have a "..." menu → "Open in Safari" / "Open in Chrome".
They re-enter the PIN
in the proper browser; payment now works.
Why this works this way
In-app browsers (Facebook Messenger, Instagram, LinkedIn, etc.) often disable third-party cookies and limit JavaScript APIs Clozo relies on (specifically, Stripe Elements for card capture). The PIN gate may work, but the payment step may not.
Troubleshooting
Keep reading
Lifecycle
Status: Sent — the proposal is in your client's inbox
You've clicked `Send`. The PDF is rendered, the email is on its way, the proposal number is assigned, and the audit trail starts here. Now you wait — until the client opens it (`Viewed`) or signs (`Signed`).
Troubleshooting & Reference
"My client can't enter the PIN" (lockouts and lost codes)
The 4-digit PIN gate protects every proposal and amendment link. Five wrong attempts in 24 hours triggers a per-IP lockout. Recovery is one click away — issue a fresh link.
Troubleshooting & Reference
"My client says they didn't get the email"
The most common support question Clozo gets. Five checks resolve nearly all cases — most of the time, the email landed in spam.