Email change retires the signing token

Correct updates the outstanding signer’s name, email, or phone on the same sent envelope. If the email changes, the previous token is retired so the old inbox cannot finish. If you only fix a display name, the signing token can stay. Phone is the same object. Correcting a phone does not by itself retire the link. Text-message (SMS) is coming soon, and reminders go out by email today. That is token-retire honesty: retirement is the email change, not the correct click, and resend never rotates the token for you.

The mid-flight verb is correct an envelope mid-flight. Retrying mail on the current token is resend after a soft-fail email. Copying a URL after mail skips is copy the signing link after mail skips. Desk help is Docs. This guide is when the old link dies.

The FAQ says correct updates the recipient on the same envelope. Features names the same verb under envelope admin. Ask Inkpacket for email change retires the signing token 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 forwarded typo must not complete the envelope.

When the old link dies

• Email changes — previous token retired. Copy the new signing URL if mail skips again. Do not paste the old link into the new thread.
• Name only — token can stay. Resend still emails that same link to the current outstanding signer.
• Phone only — token can stay. Text-message (SMS) is coming soon. Reminders go out by email today. Copy the signing link.
• Someone already signed — you cannot correct that finished mark. Correct the outstanding person only.

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.

Resend is not retirement

Envelope admin Resend emails the existing signing link to outstanding signer(s) again. The token stays. Use it when the address is right and they never saw the mail. After an email-change correct, resend talks to the new outstanding signer with the new token. It does not revive the old inbox. Do not resend hoping a forwarded message to the typo will follow the new address.

Embed uses the same token. After an email change, both the iframe at /embed/sign/TOKEN and a popup at /sign/TOKEN need the new URL from the desk. Embed iframe versus popup framing is those two frames. Do not leave the old embedUrl in a host page. Access codes still apply on the new token. Share the PIN separately — it is not in the invite email.

What correct will not do

• Restack Order. Shared sequential slots stay as you sent them — when recipients share a sequential order.
• Move field marks or change routing after send. Those lock when you send. Place them on the draft.
• Reopen a declined or expired envelope. Send a new envelope if the work still needs a signature.
• Mint a twin. The envelope id stays. The monthly count does not get a second send from this click.

If the PDF itself is wrong, void or abandon and send a new envelope from the right file. If the deal is off after a partial sign, void — void after a partial sign versus decline. If they already declined, you missed the window to correct a typo. One decline closes the whole envelope.

The click-path

1. Open the sent document. Confirm status is sent and who is outstanding.
2. If the inbox is wrong, Correct recipient and change the email. Treat the old token as dead.
3. If only the badge name is wrong, correct the name. Expect the same link to keep working.
4. Copy the new URL if mail skips. Do not create a second draft to “retry the right inbox.”
5. On a phone, Documents is a drawer row. Envelope admin sits on that envelope.

Ask Inkpacket for email change retires the signing token to open this article. Ask how to correct a recipient to open help. Marketing Ask stays site Q&A and deep links. It will not rotate a token from this article.

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 un-retire a token or mint a twin envelope. The FAQ and More on voiding, correcting and resending use If the email changes, the previous token is retired in the same words.

Change the inbox. Retire the old link. File the envelope when the new person finishes. Open a workspace on Free — see published pricing — and run a throwaway typo so token-retire honesty is a dead URL you have already watched fail, not a forwarded message you hoped would still work.