BlogTag
Reminders and expiry
Set a reminder cadence and an expiration on send so outstanding envelopes move — or close when the window ends.
Related product pages
Guides
Reminders and expiry so envelopes don’t stall
Set a reminder interval and an expiration on every Inkpacket send — workspace defaults of 3 and 14 days, interval 0 to skip nudges, and hourly expiry so outstanding links cannot sit forever.
How to choose an envelope expiry
A decision guide for Inkpacket expiration: when to keep the 14-day default, when to set 0, how bulk and Web Forms inherit a window, and why expiry is a clock — not a void.
What happens after a signing reminder fires
After Inkpacket sends a reminder, the envelope stays SENT, the token stays the same, and only already-invited signers are nudged — until they sign, decline, you void, or the window expires.
Reminder cadence versus envelope expiry
Inkpacket reminder cadence and envelope expiry are two send fields, not one. Cadence nudges a SENT envelope. Expiry closes the link. Interval 0 skips nudges. Days 0 skips the window. That is cadence-versus-expiry honesty.
Web Form reminders and expiry on publish
Inkpacket Web Form reminder days (0–90) and expiration (0–365) are set when you publish. Later fills inherit that pair. Envelopes already created keep the days they were born with. That is publish-cadence honesty.
Why expired is not voided
When an Inkpacket signing window ends, status becomes expired. That is not a void and not a cancel. Envelope admin will not reopen it. That is expired-not-voided honesty — send a new envelope if the work still needs a mark.
Why expiration 0 means the link does not expire
On an Inkpacket send, expiration 0 means the signing link does not expire. It is not expire-now. Reminder interval 0 is a different zero. That is expiry-zero honesty.