Signature reminders that actually get documents signed
A good signature reminder gets someone to finish a document they've been putting off — without feeling like spam, and without you having to remember to send it yourself. On Esignapi specifically, reminders are fully automatic: there's no manual "resend" action in the interface, so what matters is understanding the timing built into the system rather than figuring out when you should personally nudge someone.
Why documents sit unsigned in the first place
Most delays aren't about someone refusing to sign — they're about a document getting buried in an inbox, a signer meaning to get to it later and forgetting, or the request simply not feeling urgent compared to everything else competing for their attention that day. Effective reminders work with that reality: they resurface the request at a reasonable moment, with enough context that the recipient immediately remembers what it's about.
What makes a reminder effective in general
- Reasonable timing: too soon feels pushy; too late and the request has lost momentum. A gap of roughly a day before the first nudge, with a longer window before a final one, tends to strike a workable balance.
- Clear context: a reminder that just repeats the same bare link, with no reference to what the document is, is easy to mistake for spam or to keep ignoring. The most effective reminders restate what's pending and why it matters.
- A hard stop: reminders that continue indefinitely stop being useful and start being annoying. An effective system reminds a limited number of times, then leaves further follow-up to a human judgment call.
- One recipient, one link: a reminder tied to the specific signer's own unique link, not a shared one, keeps the request unambiguous about who still needs to act.
How Esignapi's reminders actually work
Esignapi sends reminders to pending signers automatically — there's no button in the dashboard to manually resend a reminder, and reminders aren't something you draft or customize yourself. Specifically: a signer who hasn't completed their part receives a first reminder starting at 24 hours after the original request was sent, and a final reminder starting at 72 hours after the original send if they still haven't completed it by then. After that second reminder, the system doesn't send any more automatically for that request — at that point, following up through another channel (a message, a call) becomes the practical next step if the document is still urgent.
What this means day to day
In practice, this means you don't need to track who you've already reminded or remember to follow up within the first couple of days — the system is already doing that in the background. Where manual attention still helps is after those two automatic reminders have both gone out: if a signer still hasn't responded at that point, that's the signal that automated nudging has run its course and a more direct follow-up is worth considering.
Reminders only go to people who still need to act
Signers who have already completed their part don't receive further reminders about that document — the system tracks completion per signer, so reminders are only sent to whoever is still pending, not to the whole group every time.
If you're managing several pending documents at once
With more than one document out for signature at a time, it's still worth checking your dashboard periodically, even though reminders are handled automatically — mainly to catch documents that have gone past both automatic reminders without a response, since those are the ones where manual follow-up is actually useful.
When a document isn't relevant anymore
If circumstances change and a document no longer needs to be signed, cancel the request rather than letting it sit pending — this stops any further automatic reminders tied to it and keeps your dashboard reflecting only documents that are genuinely still active.
Why a fixed schedule instead of a configurable one
Some platforms let the sender set custom reminder intervals or write their own reminder copy. Esignapi takes a simpler, fixed approach instead: one schedule (24 hours, then 72 hours), applied the same way to every request. The tradeoff is less flexibility for senders who want highly custom timing, in exchange for predictability — you always know exactly when a pending signer will be nudged, without having to configure anything per document, and signers always receive the same consistent, recognizable reminder regardless of who sent the request.
Multi-signer documents and reminder timing
On a document with several signers, each signer's own 24-hour and 72-hour reminder windows are measured from when the overall request was created, not from when that specific signer's turn actually arrives. This matters on a document with a sequential signing order: if the first signer takes longer than 24 hours to complete their part, a later signer further down the order can still receive a reminder for a document they can't yet access, simply because the clock for their reminder started at the same time as everyone else's. If you're using a strict signing order on a document where signers might take a while, it's worth keeping this in mind rather than assuming a reminder only ever means "it's genuinely this signer's turn."
What a reminder email actually contains
The system reminder email references the original document and signer, and includes the same secure signing link the signer received in the initial request — it isn't a bare, context-free "you have something to sign" notice. This matters for the same reason context matters in any reminder: a signer who gets a reminder that clearly identifies what's pending is more likely to act on it immediately rather than needing to track down the original email first.
Reminders and spam filters
Automatic reminder emails occasionally land in a spam or promotions folder, especially for signers who haven't interacted with the sending domain before. If a signer reports never seeing a reminder despite the request still showing as pending on your dashboard, it's worth suggesting they check those folders before assuming the system failed to send one — the sending and completion status on your side is the more reliable source of truth than whether a specific email was visibly received.
Let the system handle the follow-up
Esignapi sends reminders automatically on a fixed schedule, so you can focus on the documents that need your personal attention instead of manually tracking who needs a nudge.
Frequently asked questions
Can I send a reminder manually if I don't want to wait 24 hours?
Not through the dashboard — reminders in Esignapi are automatic and follow the fixed 24-hour/72-hour schedule. If something is urgent sooner than that, reaching out to the signer directly through another channel is the practical option.
Do signers who already signed get reminder emails too?
No, automatic reminders are only sent to signers who still have a pending part of the document to complete.
Is there a limit to how many reminders get sent?
Yes — a maximum of two automatic reminders per signer, at the 24-hour and 72-hour marks. The system doesn't keep sending reminders indefinitely after that.
Can I customize the wording of the reminder email?
The reminder content is a fixed system email rather than something you write yourself for each request — what you control is the original message sent with the document, which the signer already has context from before any reminder arrives.
What should I do if a signer hasn't responded after both automatic reminders?
At that point, following up directly through another channel — a message or a call — tends to be more effective than waiting for a third automatic nudge that won't come, since it also lets you ask whether something specific is blocking them.