How to Chase Unsigned Contracts With Automatic Reminders

Why unsigned contracts cost money

A contract that sits in an inbox is a deal that has not closed. The revenue may be booked in your forecast, but the work often cannot start, the supplier cannot be paid, and the staff member who sent the document keeps a mental note to chase it. That mental note is the real cost. It takes time, it gets forgotten, and it leaves no record of who was asked what and when.

The scale of the problem is easy to underestimate. A Lisbon-based consultant with a five-person team and a New York-based property manager with forty leases can both lose weeks to documents that nobody follows up on. Neither needs a new sales team. They need a dependable second step after the send button.

You can put a rough number on it with your own data. Take the number of documents you send for signature each month, multiply by the average days a document waits, and then multiply by the minutes your staff spend on each manual chase. Add the cost of the hour that a senior person spends asking whether a document was signed. For a small firm, the result is often a few hours a month. For a larger group with hundreds of documents, it becomes a full-time role spread across several people.

Late payment data points the same way. A PYMNTS Intelligence report, which we could not date precisely from the source we found, found that nearly 60% of invoices are paid late. Signed contracts are often the step before invoices, so a slow signature pushes back the whole billing cycle. The figure is about payment rather than signing, so treat it as context, not as a measure of your own losses.

The manual way and the automated way

Most teams do not have a reminder process. They have a memory process. The table below shows the difference in practical terms.

The automated column has one weakness that the manual column also has: it cannot make a customer agree to the terms. Automation removes the forgetting. It does not remove the reason the document stalled.

How to set it up, step by step

1. List the documents that need chasing. Start with the three or four document types you send most often, such as client agreements, supplier onboarding forms, or employment offers. Write down who signs each one and who owns the deal.
2. Choose where the signing happens. Most teams already use a signing tool. DocuSign, BoldSign, Xodo Sign, Fill and PandaDoc all offer automatic reminders in their settings. If you sign documents through a platform's API, check whether reminders are set in the API call itself, because account-level defaults may not apply to those envelopes.
3. Set the first reminder and the repeat interval. Use the schedule in the next section, or the settings your tool offers. Confirm that reminders go to the signer and not only to you.
4. Set an expiration date and a warning. A document that never expires can stay open for months. DocuSign's default expiration for requests sent through its API is 120 days, and its guidance is to warn signers a few days before expiry, which improves completion.
5. Define the routing order for multiple signers. If a second signer should only receive the document after the first one signs, set the signing order. Otherwise the second person may ignore a request they cannot yet act on.
6. Connect the signing status to your system of record. Use a no-code automation tool such as Zapier or Make, or your CRM's built-in integration. Create triggers for three events: signed, declined and expired. Each trigger should update the deal stage in your CRM, the customer record in your ERP, or a shared spreadsheet, depending on what you run.
7. Add an escalation rule. After the final reminder, create a task for the person who owns the relationship. The task should include the document name, the signer, the number of reminders sent, and the expiry date.
8. Add WhatsApp only where customers actually answer it. In some markets customers respond faster to a message on WhatsApp than to an email. Use the WhatsApp Business Platform through an approved provider, and send only pre-approved template messages when you contact someone outside an open conversation window.
9. Test with one live document. Send a test to an internal address, check each reminder's timing, check that signing stops the reminders, and check that the escalation task arrives in the right person's queue.

Choosing the cadence

A sensible default is a first reminder one or two days after sending, then a repeat every three to four days. The first nudge is early enough that the document is still fresh, and late enough that the signer has not already seen it and decided to wait. Three to four days between repeats gives a busy person time to act without making the sender look anxious.

This cadence is a recommendation from our own process design, not a figure from a study. Tool defaults vary. DocuSign's standard setting sends the first reminder after three days and then every three days. One popular platform, Enrollsy, sends a reminder after three days and a second after seven, then stops. Pick a cadence that matches how fast your deals move. A two-week renewal may need a faster rhythm than a supplier onboarding form.

Keep the number of reminders small. Three or four is usually enough. After that, a person should decide whether to call, change the terms, or let the offer lapse. Repeating the same email for months damages the relationship without helping the signature.

Routing stalled documents to the person who can act

The reminder itself is the easy part. The harder question is who should act when the reminders fail. The signer's inbox is not the right place to escalate. A stalled document needs a human who can answer a question, change a term, or pick up the phone.

Set the rule before you need it. For a sales contract, route the task to the account executive. For an employment offer, route it to the hiring manager and HR. For a supplier form, route it to procurement or the finance contact. Each task should name the next action, such as calling the signer, checking whether a clause is the problem, or deciding to void and resend.

Some signing tools can also show when a document was opened but not signed. That detail matters. A document that was opened three times and never signed often has a question attached to it. A document that was never opened usually needs a different email address or a different contact.

Using WhatsApp for signers who do not read email

In many countries, WhatsApp is the main way business gets done with customers and suppliers. A reminder that links to a signing page can reach a signer who never opens email. The cost depends on the message type and the recipient's country.

Since July 1, 2025, Meta has billed WhatsApp Business Platform messages per delivered template message, based on the message category and the recipient's country. Replies inside an open 24-hour customer service window are free, and utility templates sent inside that window are free as well, according to a 2026 summary by Unipile. Outside that window, a utility template is billed. Vendor summaries from 2026 list a utility rate of about $0.004 in the United States and about ₹0.115 in India. Those are secondary sources, so check the current rate card on Meta's developer site before you budget.

A reminder about an unsigned contract is a transactional message, not a promotion. Write it as a utility template, keep it short, and include the signing link and the sender's name. A marketing-style message is billed at a higher rate and is more likely to be rejected or ignored. Do not send WhatsApp reminders to people who have not given you a phone number for business messages or who have asked you to stop.

What breaks and how to prevent it

• Settings that do not apply. DocuSign's documentation says that an envelope created through the API uses the instructions in the API call, and that account-level reminder settings are not applied unless the call tells the system to use them. Test one document from each sending path.
• Settings that cannot change after sending. BoldSign's API documentation states that automatic reminder settings can only be set when the document is created. If you need a different cadence for a live document, you will have to send a manual reminder or resend.
• Reminders after expiry. Expired documents stop receiving automatic reminders. If you want one more nudge before expiry, set a warning date.
• Wrong signer. A reminder sent to a former employee or an old address leaves the document stuck. Check signer details at the point of sending, not after the first reminder fails.
• Over-reminding. Too many messages in a short period make a signer less likely to answer. Cap the count and route the rest to a person.
• Reminders that keep going after a decision. If someone declines or asks for a change, the reminders should stop. Make sure the declined and expired triggers are wired up before you go live.
• Consent and data rules. If your signers are in the European Union or the United Kingdom, check your obligations under the GDPR before you use WhatsApp or email reminders that contain personal data. Keep the signer's contact details in a record you control.

When not to automate

Reminders cannot fix terms the customer dislikes. If a customer has not signed because the price, liability clause or payment schedule is wrong, a fifth reminder will only annoy them. The right response is a conversation, a revised draft, or a decision to walk away. Automation should flag that situation early, not hide it behind more messages.

High-value deals still need a call. For a large agreement, a person should speak to the signer before the first reminder goes out, and again before any escalation. Use automation for the routine follow-up on smaller or standard documents. Do not let it be the only contact on a deal where the cost of losing the signature is high.

Some documents also need a human check before they are sent at all. Employment contracts, regulated agreements, and documents that require legal review should not go out on an automatic schedule until the terms are final.

What it typically takes

Most of the effort is in the setup, not in the running. Configuring reminders and expirations in a signing tool is a matter of settings, and a non-technical owner can usually do it in an afternoon. Testing it with real documents takes a few more days, because you need to check each path, each signer type and each trigger.

Connecting the signing tool to a CRM, an ERP or a spreadsheet takes longer. The time depends on how many systems you use, whether they have ready-made connectors, and whether your data is clean. Plan for a few weeks of testing and fixing rather than a single session. After that, the work shifts to reviewing the escalation queue each day and updating the templates when your terms change.

The effect you should watch is simple. Track the average number of days from sending to signing for each document type before and after you switch on reminders. Also track how many documents expire unsigned. If the signing time does not improve after a month, check the cadence, the signer details and the escalation owner before you change anything else.