The agreement keeps moving after you hit send.
Reminders, questions, declines, delivery status, and corrections live in one workflow — so nothing stalls in silence.
An example, step by step
Keep the next action in context
- 1Invitation submitted
- 2Question received · reminders pause
- 3Reply and resolve the question
Project services agreement
Question: Can you confirm the start date?
Illustrative example with fictional details.
See completion recordsReminders that chase for you
Unsigned recipients get an automatic reminder sequence (about 4 hours, then 3 days, then 10 days after sending). If someone raises a question, their reminders pause so you're not nagging a person who's already waiting on you.
Questions, in context
A recipient can ask a question right from the signing page. It comes back to you by email and shows up on the envelope — no separate support thread.
Declines with a reason
If someone declines, they say why. The envelope stops, you're notified, and the reason is recorded on the envelope and in its activity trail.
Delivery you can see
When email delivery is configured, invites move from sent to delivered, and bounces are caught — so a recipient who never received the message doesn't look like one who's ignoring it.
Review changes before sending
Correct recipients and filled values while a request is a draft. Once sent, withdraw the unsigned request and prepare a reviewed replacement when changes are needed. Executed agreements remain sealed and locked.
Reminders and delivery tracking rely on email being configured for your workspace; the copy-link flow works either way.