Correct an envelope mid-flight

A sent envelope is still in-flight. Correct updates the outstanding signer’s name, email, or phone on that 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 are locked once the envelope is sent. This corrects the signer on the same envelope. It does not create a second one. That is mid-flight-correct honesty: you fix the recipient on the id you already have, and you do not invent a second audit trail because someone typed .con.

The three sender verbs are when to void, correct, or resend an envelope. The fork that includes the signer’s verb is correct, void, or decline an envelope. After a mark already landed, void is void after a partial sign. Desk help is Docs. This guide is the mid-flight correct itself — what you can change while status is still sent.

The FAQ says correct updates the recipient on the same envelope. Features names the same verb under envelope admin. Ask Inkpacket for correct an envelope mid-flight to open this article. Ask how to correct a recipient to open help. Those phrases stay on the product screens. This article is the public version of why a typo is not a second send.

What correct changes

• The outstanding signer’s name, email, or phone on this envelope id.
• A new invite to the updated address. Mail skips still leave a copyable signing link.
• The previous token, when the email changes — the old inbox is done.
• Nothing about people who already signed. You cannot correct a finished mark.

Open the sent document at /desk/documents/:id. Envelope admin Correct recipient is the control. Public API: POST /api/v1/packets/:id/correct. Only SENT envelopes can use this action. Completed envelopes cannot be changed. Expired and declined envelopes cannot be corrected either. A draft is not mid-flight — edit the recipient before you send.

Token retirement is the point

If you only fix a display name, the signing token can stay. If you change the email, Inkpacket retires the previous token so a forwarded message to the wrong inbox cannot complete the envelope. Copy the new signing URL if mail skips again. Do not paste the old link into the new thread. Do not resend hoping the old token will follow the new address — resend emails the existing link to the current outstanding signer, and after a correct that signer is already the new one.

Phone is the same object. Correct can update it. Text-message (SMS) is coming soon. Reminders go out by email today. Copy the signing link. Drive archive still waits for a completed envelope. Stripe off: Payments not live. None of those flags rotate a token for you.

When correct is the wrong verb

• Someone already signed. Correct updates an outstanding signer only.
• The PDF itself is wrong. Void or abandon and send a new envelope from the right file.
• They already declined. The envelope is closed. Send a new envelope.
• The window ended. Expiration is not a correct. Ask for a new envelope.

Fields and routing are locked once the envelope is sent. Do not treat the editor as a way to move boxes after send. Placement belongs in assign fields to each signer, not in Envelope admin. If the deal is off, void. If they never saw the mail and the address is right, resend. If mail skipped, copy the signing link after mail skips.

One decline still closes

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. One decline closes the whole envelope, even when later sequential signers have not been invited yet. That closer is decline closes the envelope, not this screen.

The click-path

1. Open the sent document. Confirm status is sent and who is outstanding.
2. Correct recipient. Fix name, email, or phone. Save.
3. If the email changed, treat the old token as dead. Copy the new URL if mail skips.
4. Do not create a second draft to “retry the right inbox.”
5. If someone already signed and the next email is wrong, correct that outstanding signer — not the one who finished.

On a phone, Documents is in the desk menu. Open the envelope. Envelope admin sits on that draft. Ask Inkpacket for where is the hamburger if you cannot find the list. Help is Docs.

Caps and what is not open yet

Correct is not a send. 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. Those flags do not mint a twin envelope or un-retire a token. The FAQ and envelope admin on Features use correct updates the recipient on the same envelope in the same words.

Fix the outstanding person on the id you already have. File that envelope when they finish. Open a workspace on Free — see published pricing — and run a throwaway typo so mid-flight correct is a click you have watched before a real inbox waits.