Whether the mail reached the signer is shown separately from whether the request is open. A request can be perfectly valid while one recipient's invitation bounced.
The states
| State | Meaning |
|---|---|
| Queued | Waiting to be handed to the mail service. |
| Accepted | The mail service took the message. This is not delivery. |
| Delivered | The service reports the message reached the mailbox provider. It does not mean the person read it. |
| Bounced | The address does not exist or refused the message. |
| Suppressed | The address was blocked earlier, for example after a complaint, so nothing was sent. |
| Failed | The message could not be handed over. |
| Outcome unknown | The message may or may not have gone out, for example when the service did not answer in time. |
Opening an email is never reported, and a tracking signal is never treated as proof that someone reviewed the document.
What to do
| What you see | What to do |
|---|---|
| Bounced or suppressed | The address is wrong or unreachable. Ask the person for another address and replace the request. Reminders to this recipient have stopped. |
| Failed | Use Resend for that recipient. It sends a fresh link and replaces the old one. |
| Outcome unknown | Do not send it again straight away: the first message may arrive. Wait a few minutes, then ask the recipient to look in spam, and Resend if nothing came. A resend never uses another request from your allowance. |
| Delivered, signer says nothing arrived | Ask them to check spam and the exact address. The invitation comes from your workspace. |
| The signer's link has expired | They can request a new one on the page; or press Resend. |
A resend or a reminder keeps the same operation key, so a retry after a network failure does not produce a second message. Sending twice by accident does not create two requests.
Complaints
A recipient who marks the mail as spam is recorded as a delivery failure in the request's history and stops further reminders to them. A complaint also pauses new signing requests for the workspace until it has been reviewed, so a mistake cannot become a flood. Requests already out, and every record, are not touched. Contact support to have sending reviewed.
Alerts
If you have browser or phone alerts on, a failed delivery raises a generic alert, "A signing request needs attention". It contains no document title and no name. Opening it checks your access to the request again. You can turn the topic off in your notification settings.
For developers
GET /api/v1/signing-requests/{id} lists the delivery state of each recipient. Automations can start from the delivery failed event. Errors on resend use recipient_unreachable for an address that is bounced or suppressed and reminder_cooldown when a reminder was sent less than an hour ago.
