First-signer waiting message

Sequential routing invites the current order, then the next after everyone at that order finishes. After you send, the desk says First signer was invited. Later recipients get their link after earlier ones finish. A later sequential signer who opens their URL early sees a waiting page — they cannot view the PDF until it is their turn. The page says This envelope is waiting for an earlier signer. That is waiting-page honesty, not a broken link.

Which mode to pick is sequential vs parallel signing. When everyone should start now is when parallel beats sequential routing. How to add the names is send one envelope to multiple signers. Desk help is Docs. This guide is the waiting page and the desk sentence after send.

What the later signer sees

• They cannot view the PDF yet.
• The page names an earlier signer, not a void and not an expiry.
• An embed framed too early shows the same waiting page inside the iframe.
• Reminders and resend only email people who have already been invited.

Do not void the envelope because someone forwarded a later URL. Do not correct the first signer unless the email is actually wrong — correct retires the old token if the address changes. Do not POST send again. That is a second envelope toward the monthly cap and a second audit trail. Stay on this envelope id.

Parallel is a different page

Parallel routing invites every recipient at once. There is no waiting page for turn order. The envelope completes when every signer has finished. One decline still closes the whole envelope in both modes — even when later sequential signers have not been invited yet. Tell both people that before you pick sequential to “keep the second person in the dark.” They may still receive a URL they cannot use yet.

Recipients who share the same sequential order sign in parallel with each other. The waiting page appears for a later order, not for a peer at the same number. An envelope accepts up to 20 recipients. Place fields for a recipient before you send — assign fields to each signer.

What you do on the desk

After a sequential send, read First signer was invited. Later recipients get their link after earlier ones finish. If the first person never saw the mail, resend — that emails outstanding invited signer(s), not the people still waiting their turn. If Resend is missing, copy the first signing link and share it. The later URLs can wait.

If the first person refuses, they decline with a reason and the whole envelope closes. Later waiting pages become a declined envelope, not a turn that finally arrived. If the deal is off, void it yourself instead of waiting for that decline — void does not email the signer. Correct, void, or decline an envelope is that fork.

The click-path

1. Add recipients and pick Sequential on Documents → new #routing.
2. Place fields for each slot before you send.
3. Send. Read First signer was invited on the desk.
4. If a later person writes that the PDF will not load, ask whether they see the waiting page.
5. Resend only the people already invited. Do not create a twin envelope.

Ask Inkpacket for first signer was invited or waiting for an earlier signer to open help. Those phrases stay on the product screen. This article is the public version of that wait.

Iframe and SMS follow the same turn

An embed URL for a later signer is still that signer. The parent hears nothing useful until it is their turn. Do not advance a portal because postMessage has been quiet — they may be on the waiting page. Embedded iframe parent page checklist is that parent. Text-message (SMS) is coming soon. Reminders go out by email today. Inkpacket does not text a signing link. A waiting page is about signer order.

Caps and what is not open yet

One multi-signer envelope is one envelope. Waiting is not a second 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 skip a sequential turn. The FAQ and More on signing order use First signer was invited and waiting for an earlier signer in the same words.

Send sequential when order matters. Tell the later person they may see a waiting page. Stay on that envelope id. Then file the stamped PDF after the last turn — the wait was the product working. Open a workspace on Free — see published pricing — and send a two-person sequential throwaway so both sentences are something you have read before a countersign depends on them.