Correct, void, or decline an envelope

Three outcomes look similar from a panicked thread and they are not. Correct fixes the outstanding recipient on the same envelope. Void is you stopping an in-flight envelope. Decline is the signer refusing with a reason. Pick the sender verb when you still own the mess. Leave decline to the person on the signing page. Cloning a second envelope because someone refused — or because you meant to stop the first link — splits the audit trail and spends another envelope.

The click-path for the sender verbs is when to void, correct, or resend an envelope. The longer admin loop is envelope admin: void, correct, resend, and when signers decline. Desk help is Docs. This guide is the three-way fork that includes the signer’s verb as a first-class choice, not a footnote.

The three-way fork

• The PDF is right and only the name or email is wrong, and nobody has signed → correct.
• You decided the agreement is off, the file was wrong, or collection must stop now → void.
• They read the PDF and will not sign → they decline with a reason. That is their action.

Resend is not on this fork. Resend is for a recipient who is right and never saw the mail. A reminder is the scheduled nudge. Neither one stops the envelope and neither one changes who was invited. If you are choosing among correct, void, and decline, resend will not help.

Stay on one envelope id

Correct, void, and decline keep the original document. The envelope id does not change. Webhooks fire corrected, voided, or declined on that same id. A second create-and-send looks tidy in a spreadsheet and is not: two reminder schedules, two tokens, and a signer who may finish the old link after you “replaced” it.

Correct when the recipient is wrong

Correct updates the outstanding signer’s name or email on the same envelope. A new invite goes out. If the email changes, the previous token is retired so the old inbox cannot finish. Fields and routing stay where you placed them on the draft. This corrects the signer on the same envelope. It does not create a second one.

Correct before they decline if nobody has signed and only the address was a typo. After a refusal the envelope is declined — you cannot correct it. After someone has signed, correct is the wrong tool. After the PDF itself is the wrong file, void or abandon and send a new envelope from the right template. The public route is POST /api/v1/packets/:id/correct.

Void when you stop the deal

Void marks the envelope voided, kills every signing and embed token, and stops reminders. The signer is not emailed. The link simply dies — This signing link was voided. Tell them out of band if they need to know. Use void when you already know collection should stop. Do not wait for the last sequential signer to decline a deal you have already killed. Do not wait for expiry to act like a cancel. Expiry is a clock. Void is a decision.

Void does not mint a replacement. If the work still needs a signature, start from the PDF or template. Void does not rewrite a completed PDF. Completed, expired, or declined envelopes cannot be voided, corrected, or resent. The filed copy stays filed. How to choose an envelope expiry is the window. This page is the stop.

Decline is the signer’s verb

On the signing page — and inside an embed — they can refuse and leave a reason. A decline reason is required, 500 characters or fewer. The envelope status becomes declined. Every signing and embed link stops. Reminders stop. The sender is emailed when Resend is configured; otherwise the decline is logged the same way as an invite. Intentional limit: one decline closes the whole envelope, even when later sequential signers have not been invited yet.

Treat the reason as operational data. Wrong entity and terms changed are different follow-ups. If you needed a different person after a refusal, send a new envelope. If nobody has signed and you only had the wrong email, you already missed the chance to correct — the envelope is closed. Do not ask them to “just ignore the link” while you send a twin. The old token is already dead.

Parallel envelopes and bulk rows

On parallel routing, one refusal still closes the whole envelope. Tell both people that before you invite them — when parallel beats sequential routing. A decline on one bulk-send row does not stop the rest of the job. Each row is its own envelope. Void or correct that row the same way you would a one-off.

After the envelope has closed

Completed envelopes cannot be changed. Expired envelopes cannot be voided, corrected, or resent. Declined envelopes cannot either. If the work still needs a signature, send a new envelope from the template. File the closed envelope as history. Reading an audit trail is how you quote what happened later.

Embed URLs follow the same closes. An iframe pointing at a voided, declined, or corrected-away token will not complete. Recopy Embed URL only after a correct that minted a new token. Embedded iframe parent page checklist is that parent. SMS, when enabled, retries on resend — not on void, and not on decline. Text-message (SMS) is coming soon. Reminders go out by email today.

Caps and what is not open yet

Correct, void, and decline do not count as a new envelope. A second create-and-send does. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. None of those flags pick the verb for you. The FAQ is the short version: void stops signing links; correct updates the recipient on the same envelope; signers can decline with a reason and the envelope status becomes declined.

Correct the typo. Void the dead deal. Let them decline when they refuse. Stay on the same envelope id unless the envelope already closed. Then file what remains, or open a workspace on Free — see published pricing — and practice the three outcomes on a throwaway send before a real countersign depends on the distinction.