Why Phone number must be a valid E.164 number is not an SMS soft-fail

Send and correct accept an optional phone on a signer. Empty is fine. A value that is not E.164 returns Phone number must be a valid E.164 number. The envelope stays a draft if it was still a draft. No invite goes out. Inkpacket does not text a signing link. That is e164-phone honesty: the number failed the store format. Text-message (SMS) is coming soon, and opening Billing will not “accept a junk phone.”

Why the signing link still shows while text-message (SMS) is coming soon is when SMS invites soft-fail. Why a phone-only correct keeps the token is phone-only correct keeps the signing token. Why an empty recipient list is a different 400 is why Signer name and email are required is not a unique-email 400. Desk help is Docs. This guide is why send and correct name a bad phone, and why that name is not the SMS-not-configured state.

The FAQ and SMS signing invites on Features start from an optional phone. Ask Inkpacket for why Phone number must be a valid E.164 number is not an SMS soft-fail to open this article. Ask how SMS invites work to open help. Those phrases stay on the product screens. This article is the public version of Phone number must be a valid E.164 number — the string send and correct already use next to a number that cannot be stored.

What e164-phone covers

• Desk send with a phone that is not E.164. Phone number must be a valid E.164 number.
• POST /api/v1/packets/:id/send with the same bad phone on the envelope or a recipient. The same 400.
• Correct that writes a bad phone on a SENT envelope. The same 400. The token stays put. No invite goes out.
• A legal send with a stored phone. Text-message (SMS) is coming soon. That is not this 400.

Reading Phone number must be a valid E.164 number is not a send. The draft never left DRAFT, or the SENT envelope never stored the new number. Free allows 5 packets a month. A refused bad phone does not return HTTP 402 ENVELOPE_LIMIT. Signer name and email are required is an empty list. Each recipient needs a unique email is a twin inbox on one payload. X is already a recipient on this envelope is a stored inbox. Text-message (SMS) is coming soon. A phone that cannot be stored as E.164 is this door.

What this is not

• Not a text. Text-message (SMS) is coming soon, and reminders go out by email today. This article does not send a text.
• Not a text. Text-message (SMS) is coming soon. Reminders go out by email today.
• Not phone-only correct keeps the token. That guide is a successful phone change. This article never stored the number.
• Not checkout. Billing is not open. Paying a listed price does not accept a junk phone.

Leave the phone blank, or store + and 8–15 digits that normalize to E.164. Ten national digits without a plus are stored as +1 then those digits. A value that still fails the pattern is this 400. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on a later legal send, not on this 400. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags hide Phone number must be a valid E.164 number or count a refused phone toward the monthly cap.

The click-path

1. Place at least one field. Add a name and email. Leave phone blank, or type a number that stores as E.164. Then send.
2. If send or correct returns Phone number must be a valid E.164 number, fix the number. Do not open Billing. Do not assume a text was sent. Text-message (SMS) is coming soon.
3. If send succeeds, the phone was stored. Text-message (SMS) is coming soon, and reminders go out by email today. Copy the signing link.
4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the phone format.
5. On a phone, Documents is a drawer row. The 400 copy is the same. Help is not a drawer row — it stays in the header.

The SMS product walkthrough is SMS signing invites are coming soon. Why a stored inbox is a different 409 is why X is already a recipient on this envelope is not a unique-email 400. Ask Inkpacket for why Phone number must be a valid E.164 number is not an SMS soft-fail to open this article. Ask how SMS invites work to open help. Ask send sms invite to open the send form.

Ask and the bad phone

Ask Inkpacket for why Phone number must be a valid E.164 number is not an SMS soft-fail to open this article. Ask how SMS invites work to open help. Marketing Ask stays site Q&A and deep links. It will not store a junk phone or increment the monthly cap from this article. Text-message (SMS) is coming soon. Blank or E.164.

Caps and what is not open yet

Reading Phone number must be a valid E.164 number is not a send. Send of a draft that finally has a name, an email, and a blank or E.164 phone is. 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 store a junk phone or hide the e164-phone string. The FAQ and More on sending use Phone number must be a valid E.164 number in the same words.

Leave the phone blank, or store E.164. Then send. Open a workspace on Free — see published pricing — and hit Send with a throwaway name, email, and a junk phone so e164-phone honesty is a named 400 you already read, not a checkout you opened to “force SMS through a bad number” this pass does not ship.