Reminders skip uninvited sequential signers
On a sequential Inkpacket envelope, reminders and resend only email people who already have a live invite. Later orders wait. That is uninvited-reminder honesty — not a skip, not a leak.
Sequential routing emails the current order, then the next after everyone at that order finishes. A later signer who opens early sees This envelope is waiting for an earlier signer. Reminders and resend only email people who have already been invited. That is uninvited-reminder honesty: the cadence job does not leak the next PDF, Resend does not pull order 2 forward, and interval 0 is still a mute on nudges — not a skip of the wait.
The waiting page is first-signer waiting message. Shared slots at one order are when recipients share a sequential order. When parallel is the better room is when parallel beats sequential routing. Desk help is Docs. This guide is who the reminder actually talks to.
The FAQ says sequential routing invites the current order first. Features names the same wait under signing link. Ask Inkpacket for reminders skip uninvited sequential signers to open this article. Ask how do reminders work to open help. Ask how routing works to open routing help. Those phrases stay on the product screens. This article is the public version of why order 2’s inbox stays quiet until order 1 finishes.
Who gets the nudge
- Current sequential order — invited. Reminders can email them when the interval is not 0 and Resend is configured.
- Shared Order slots — invited together. They sign in parallel. A reminder talks to that whole slot.
- Later orders — not invited yet. No reminder. No resend. No signing URL to copy for them.
- Parallel routing — everyone was invited at send. Reminders can talk to every outstanding person.
After a sequential send the desk says First signer was invited. Later recipients get their link after earlier ones finish. That sentence is the product. Do not paste a later person’s email into a side thread with a link you invented. They do not have a token yet. When the current order finishes, Inkpacket invites the next. Then reminders can include that next person.
Resend and correct
Envelope admin Resend emails outstanding invited signer(s) again. It does not rotate the token — resend does not rotate the signing token — and it does not invite the next order. Correct updates an outstanding invited person. You cannot correct a later sequential signer who has not been invited; they are not mid-flight yet. If the next email is already wrong, wait until they are invited, or void and send a new envelope with the right roster.
One decline still closes the whole envelope, including people who never received a link. Void after a partial sign is the sender stop if the current order already marked. Neither verb emails later uninvited people. Tell them out of band if they were expecting a turn that will not come.
The click-path
- On Documents → new #routing, set Sequential and Order. Place fields per recipient before send.
- Set reminder interval and expiration. Interval 0 skips nudges for whoever is invited. Expiration 0 skips the clock — expiration 0 means the link does not expire.
- Send. Copy the current signer’s URL if mail skips. Do not hunt a URL for order 2.
- If the current person is slow, resend or wait for the cadence. Do not start a twin envelope “for the countersigner only.”
- If they must all start now, this envelope wanted Parallel. Void and send that way. Count it.
An envelope accepts up to 20 recipients. Public API send accepts recipients and routingMode SEQUENTIAL or PARALLEL. Mail still soft-fails. Text-message (SMS) is coming soon. Reminders go out by email today. Inkpacket does not text a signing link. Drive archive waits for completed. Stripe off: Payments not live.
Ask and the wait
Ask Inkpacket for reminders skip uninvited sequential signers to open this article. Ask what does this envelope is waiting for an earlier signer mean to open help. Marketing Ask stays site Q&A and deep links. It will not invite the next order or fire a reminder from this article. On a phone, Documents is a drawer row. Routing is on that send form.
Caps and what is not open yet
A reminder 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 invite a later sequential signer or leak their link. The FAQ and More on signing order use Reminders and resend only email people who have already been invited in the same words.
Wait for the current order. Nudge only the people who already have a token. File the envelope when the last invited person finishes. Open a workspace on Free — see published pricing — and send a two-order throwaway so uninvited-reminder honesty is an empty inbox on purpose, not a leak you opened Settings to “fix.”
Open a workspace on Free
Billing is published, not charging. Send an envelope from the desk without a card.
Open a workspace