Automated Conga Signature Chasing
Every morning, WebRun signs into Conga, lists documents sent out for signature that are still unsigned, works out how long each has been waiting, saves the dated chase list into Google Drive, and queues a short Twilio SMS reminder per signer that you approve before anything sends.
How do I chase unsigned documents waiting for signature?
WebRun signs into Conga every morning, lists documents sent for signature that are still unsigned, and records how long each signer has been holding things up. It files the dated chase list in Google Drive and queues a Twilio SMS nudge per long-waiting signer for you to approve.
- Signers waiting over three days get a nudge instead of silence
- Every chase is approved by a person before it sends
- Google Drive keeps a dated record of how long each deal waited
Built for sales operations · contract managers · legal teams · revenue operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
conga.comin a real browser with your saved login - no setup, no API keys. -
1
Conga - find documents still unsigned
WebRun opens Conga to find documents still unsigned. - Sign into Conga and open your sent documents
- Filter to documents awaiting signature
- Capture the document name, recipient, owner, date sent, and days waiting
- Note which signer in a multi-party document is the one holding it up
- Only read. Never resend, void, or alter a document
Done when Every unsigned document is listed with its signer and days waiting.
-
2
Google Drive - file the dated chase list
WebRun opens Google Drive to file the dated chase list. - Open your contracts folder in Google Drive
- Write today's chase list into a dated document with one row per unsigned item
- Include document name, signer, owner, days waiting, and the Conga link
- Keep earlier days in the folder so the wait history is auditable
Done when Today's chase list is filed in Google Drive.
-
3
Twilio - queue an SMS nudge for approval
WebRun opens Twilio to queue an SMS nudge for approval. - Compose a short, polite SMS per signer waiting more than three days
- Reference the document name and the person who sent it, with no contract detail in the text
- Queue every message in Twilio as pending approval and send nothing automatically
- Wait for your explicit approval before any SMS goes out
Done when A queued SMS awaits your approval for every long-waiting signer.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it text signers without me?
No. Every SMS is queued in Twilio as pending and sends only after you approve it. WebRun writes the nudge. You decide whether it leaves.
Does it resend or void documents in Conga?
No. WebRun reads the status of documents awaiting signature and nothing more. Resending, voiding, and editing a document all stay manual actions in Conga.
Is any contract detail put in the SMS?
No. The message names only the document title and the sender, so nothing confidential travels by text. The full detail stays in the Google Drive chase list.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.