What happens after a signing reminder fires

A reminder is not a new envelope. It is the same token, the same audit trail, and another attempt to put the signing link in front of someone who already owes a mark. After it fires, nothing about the envelope id changes. The desk still shows SENT. The signer still opens the URL they were given the first time — or the copy you pasted when mail was missing.

The cadence you type at send is documented in reminders and expiry so envelopes don’t stall. The window decision is how to choose an envelope expiry. Desk help is Docs. This guide is the hour after the job runs: who was emailed, what the list looks like, and which close actually stops the next nudge.

What actually fired

A scheduled job walks outstanding SENT envelopes whose reminder interval has elapsed. The default interval is every 3 days. Owners and admins change that default in Settings. Set the interval to 0 on a single envelope if this envelope should not nag. The job does not invent a second signing link. It does not rotate the token. It does not reset expiration.

When Resend is configured, the outstanding signer gets another email with the existing URL. When Resend is missing, or when Resend rejects the recipient, the reminder is logged the same way as the first invite — Invite email was not sent. The envelope stays SENT. Copy the signing link from the document and share it. The hourly job still did its work; mail just was not delivered.

Who is nudged — and who is not

• Already invited outstanding signers. They have a token they can use today.
• Not a later sequential signer who has not reached their turn. They do not have a usable link yet — send one envelope to multiple signers.
• Not a completed signer. Their mark is already on the envelope.
• Not a declined, voided, or expired envelope. Those statuses have already closed signing.

Text-message (SMS) reminders are coming soon, and reminders go out by email today. Inkpacket does not text a signing link. The desk still shows the URL.

What did not change

The envelope id stays put. Webhooks that already stored that id do not have to merge twins. Field marks stay where you placed them. An access code set at send stays the same hash. Resend is still available if you want another copy in the thread today — that is a manual click, not the cadence job. When to void, correct, or resend is the fork among those verbs.

Expiration is independent. A reminder does not add days. After the window ends the signer sees This signing link has expired and cannot complete the envelope. Embed uses the same token. Envelope admin cannot void, correct, or resend an expired envelope. Ask for a new envelope if the work still needs a signature.

When the next reminder stops

The job skips an envelope the moment signing is no longer outstanding. That is the honest list.

1. They signed — or every signer on a multi-recipient envelope finished. Status becomes completed. Download the stamped PDF from the same envelope.
2. They declined with a reason. The whole envelope closes. Reminders stop. Signing and embed links stop.
3. You voided it. The link dies. Void does not email the signer; tell them out of band if they need to know.
4. The window expired. The hourly cron marks overdue SENT envelopes expired so the document list stays accurate.

If the address was wrong and nobody has signed, correct the recipient on the same envelope. A new invite goes out. The cadence you set at send still applies. Do not create a second envelope because a reminder bounced — that is a second envelope toward the monthly cap and a second audit trail.

Resend is not the job

Use resend when the signer says they never saw the first message and you want another copy now. Use the reminder interval when you want the desk to keep tapping without you watching the list. Both leave the envelope id alone. Neither stretches an expired link. Envelope admin is the in-place toolkit.

Bulk jobs, Web Forms, and the API

A bulk job applies the reminder interval you set on the job — or the workspace default — to every row. You do not pick a different cadence per email in this pass. If one cohort should be quiet and another should be nudged every two days, run two jobs. Bulk send for HR and sales envelopes is the list path.

A Web Form stores reminder days on the published form. Every later fill inherits that interval. Envelopes already created keep the days they were born with. Web Form intake is when strangers start the envelope. Create-from-template on POST /api/v1/packets/:id/send accepts the same reminder field a desk send does.

Caps and what is not open yet

A reminder is not a send. It does not count as another envelope. The original send already counted. Free allows 5 packets a month. Free at 5 packets a month is the live send cap that desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 and code ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts on Pricing are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Workspaces start on Free. Drive archive still reports Drive not configured without credentials. Stripe off: Payments not live. None of those flags pause the reminder job. The FAQ uses the same phrases.

After a reminder fires, look at the envelope — not your inbox. If the link is still live, the signer can finish. If mail never left, copy the URL. If the deal is off, void it. If the window ended, start a new envelope from the template. Open a workspace on Free and send one envelope with a short interval so you have seen the log line, not just the default.