Phone-only correct keeps the signing token

Correct updates the outstanding signer’s name, email, or phone on the same sent envelope. A new invite goes out. If the email changes, the previous token is retired so the old inbox cannot finish. If you only change the phone — or only the display name — the token stays. That is phone-correct honesty: a number fix is not a rotate, a name fix is not a rotate, and the copy box after a phone-only correct should match the URL you already had.

When the inbox itself is wrong, email change retires the signing token. Manual mail again on the same URL is resend does not rotate the signing token. The in-place edit is correct an envelope mid-flight. Desk help is Docs. This guide is the phone-or-name fork of Correct — the one that keeps /sign/TOKEN.

The FAQ says correct updates the recipient on the same envelope. Features names the same verb under envelope admin. Ask Inkpacket for phone-only correct keeps 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 mobile typo does not mint a second link.

What stays the same

• Envelope id. The monthly envelope already counted on the original send.
• Signing token. /sign/TOKEN and /embed/sign/TOKEN stay the same strings after a phone-only or name-only correct.
• Access code. The PIN hash does not rotate. Share it separately — it is still not in the invite email or the SMS.
• Outstanding person. You are editing the invited signer, not pulling a later sequential order forward.

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 show it. Completed envelopes cannot be changed — why completed envelopes cannot be changed. Expired and declined envelopes cannot be corrected either. A draft is not mid-flight — send it first.

What phone-only correct is not

• Not an email change. If the inbox is a typo, change the email. That retires the previous token.
• Not a resend. Resend emails the existing link without editing fields. Phone-only correct can also retry SMS when that signer has a number.
• Not a void. The old URL stays live because it is still the same token.
• Not a skip to the next sequential order. There is no skip.

Text-message (SMS) is coming soon. Reminders go out by email today. Copy the signing link. A phone-only correct does not mint a new token. Resend is the mail-shaped twin of that update, not a new token mint. Drive archive still waits for completed. Stripe off: Payments not live. None of those flags rotate the link.

Mail, SMS, and the copy box

If Resend is configured, a correct still sends a new invite mail even when the email did not change — the name or phone on the row did. The token in that mail is the same token. If mail skips, the desk still shows the signing URL and says Invite email was not sent — copy the link and share it. That skip is the same soft-fail as the first invite — Docs. Copy the URL. Do not invent a second draft “so the new phone will get a new token.”

The access code is not in the invite email and not in the SMS. Share it on a second channel — why the access code is not in the invite. A phone-only correct does not print the PIN into the text just because you touched the number field.

The click-path

1. Open the sent document. Confirm whether the inbox is right before you click Correct.
2. If the inbox is wrong, change the email. Treat the old token as dead.
3. If the inbox is right and only the phone or name is wrong, change that field. Expect the same URL.
4. If SMS skips, copy the signing link. Text-message (SMS) is coming soon.
5. Do not open Billing to “buy a new token.” Checkout is not open and does not rotate links.

Ask Inkpacket for phone-only correct keeps 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 correct the envelope or rotate a token from this article.

Caps and what is not open yet

Correct is not a send. The send that created the envelope already counted. 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 retire a token on a phone-only correct 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 — the inverse of this guide.

Fix the number. Keep the token. File the envelope when they finish on that same URL. Open a workspace on Free — see published pricing — and correct one throwaway phone so phone-correct honesty is a URL that did not change, not a second envelope you filed because the first SMS felt stale.