Skip to main content

Troubleshooting: Proposal Won't Send or Your Client Sees an Error

What to do when a proposal won't save or submit, when it never reaches your customer, or when your customer hits an error opening or approving it.

Written by Fred Pape

1. The proposal won't save or submit (the error is on your end)

If you're seeing an error on your own screen while building, saving, or submitting a proposal — messages like "Please validate all inputs" or "Could not submit proposal" — that's a different problem from a delivery issue. The email address and spam folder checks below won't help.

Work through this instead:

  1. Try once more. If it saved fine a few minutes ago and fails now, it may be temporary.

  2. Write down the exact error message, word for word, and grab a screenshot if you can. The exact wording is the single most useful thing you can give us.

  3. Note the pattern. Does it fail on every proposal or just this one? Did it work for this customer before?

  4. If it fails a second time, stop. Don't start unlinking, deleting, or rebuilding the proposal — message us in the chat box with what you captured in steps 2 and 3, and we'll look at the data directly.

We'd rather look at it early than have you rebuild work you didn't need to rebuild.

2. Double-check the customer's email address

This is the most common cause. If there's even a small typo in the email address, the proposal email will either bounce or land in someone else's inbox entirely.

How to check:

  1. Open the Customer record for the job.

  2. Look at the primary contact's email address and verify it's spelled correctly.

  3. If you find a mistake, correct it, then re-send the proposal.

3. Check your customer's spam or junk folder

If the customer previously marked a SynkedUP email as spam, future proposal emails may go straight to their junk folder — or get blocked entirely.

Ask your customer to:

  • Search their inbox, Junk, and Spam folders for the proposal email.

  • If they find it in spam, mark it as "Not spam" before clicking through.

  • Whitelist your sending address and the SynkedUP mail domain so future emails come through normally.

4. Make sure the client clicks "Review Proposal" — not the PDF

The proposal email contains both a PDF attachment and a Review Proposal button. Signing and payment can only happen through the in-browser approval page — not from the downloaded PDF.

If your customer downloaded and opened the PDF, they won't see any way to sign or pay. Ask them to go back to the email and click the Review Proposal link or button instead.

5. Client sees an error when clicking the proposal link

If your customer clicks Review Proposal and sees a blank page, a 404, or a "something went wrong" message, have them try:

  1. A different browser (Chrome, Safari, Edge, or Firefox).

  2. An incognito or private browsing window to rule out browser extensions or a stuck session.

  3. A different device — for example, their phone instead of their computer, or vice versa.

If your client has already tried more than once

The browser and device steps above cover a stuck session or an extension getting in the way. If your customer has already tried several times, on more than one browser or device, it isn't a browser problem.

At that point, send us a message with the customer name, the job or proposal number, and what your customer sees. We can look at the proposal record directly — that's faster than having your customer keep retrying.

6. Still stuck? Let us know the exact error message

If none of the above solves the problem, reach out to SynkedUP support using the chat box in the lower right-hand corner of your screen. To help us diagnose the issue quickly, please include:

  • The customer name and job or proposal number.

  • The exact error message your customer is seeing (a screenshot is even better).

  • Whether the issue is on your end (proposal won't save or send) or the customer's end (they see an error when opening the link).

The more detail you can share up front, the faster we can get it sorted out for you.

Did this answer your question?