DocuSign and Twilio integrate through DocuSign Connect webhooks and the Twilio Messages API to send SMS notifications to envelope recipients when documents are sent for signature, when envelopes are viewed, and when all parties have signed and the envelope is completed, reducing signature delays by reaching signatories on their phones rather than relying solely on email. This integration is used by legal teams, real estate agencies, HR departments, and sales operations teams that send DocuSign envelopes and experience signing delays because email notifications are missed, delayed, or buried in the recipient's inbox. The connection uses DocuSign Connect to deliver envelope status change events to your middleware, which extracts the recipient's phone from a custom DocuSign field or a CRM lookup and dispatches a targeted Twilio SMS for each event type.
What You Need Before You Start
Access DocuSign Connect by logging into your DocuSign Admin account at admindemo.docusign.com or your production admin, navigating to Integrations, then Connect, and clicking Add Configuration to create a new webhook configuration that delivers envelope events to your middleware endpoint. Determine how recipient phone numbers will be sourced for the SMS dispatch: either by adding a custom text field to your DocuSign template with the label Recipient Mobile Phone so signatories enter their own phone during signing, by prepopulating the field from your sending application using the DocuSign eSign REST API tabs object, or by looking up the recipient's phone from your CRM using the recipient email address from the Connect payload. From Twilio, provision an SMS-capable phone number under an A2P 10DLC campaign registered for the transactional notification use case, and collect your Account SID and Auth Token from the Twilio Console under Account, then General Settings. Create a DocuSign Connected App or Integration Key for your middleware by navigating to DocuSign Admin, then Integrations, then API and Keys, clicking Add App and Integration Key, and noting the integration key and RSA key pair for JWT authentication if your middleware needs to make outbound DocuSign API calls to retrieve envelope data.
Step-by-Step Integration Guide
Configure the DocuSign Connect webhook by navigating to Connect in the DocuSign Admin, clicking Add Configuration, entering your middleware endpoint HTTPS URL, selecting the events Envelope Sent, Envelope Viewed, Envelope Signed, Envelope Completed, Envelope Declined, and Envelope Voided, and enabling Include Documents to false to reduce payload size while enabling Include Custom Fields to true so your custom Recipient Mobile Phone tab value is included in the payload. In your middleware, receive the DocuSign Connect POST which delivers an XML or JSON payload depending on your Connect configuration, parse the envelope status from the EnvelopeStatus element or status field, extract the recipients array from the Recipients element, and for each recipient read the CustomFields or Tabs object to find the Recipient Mobile Phone value you configured on the template. Normalize the extracted phone to E.164 format and dispatch a Twilio SMS by calling POST https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json with Basic authentication, To set to the normalized phone, From set to your Twilio number, and Body set to an event-appropriate message such as for Envelope Sent: 'A document requires your signature. Please check your email to review and sign.' For Envelope Completed, dispatch a completion confirmation SMS to all recipients including the sender with a message referencing the envelope subject from the Subject element in the Connect payload, and return HTTP 200 to DocuSign within 10 seconds to prevent Connect retry.
Common Issues and How to Fix Them
DocuSign Connect webhook deliveries retry up to 6 times over 12 hours if your middleware does not return HTTP 200 within a specific window, causing duplicate Twilio SMS to be sent to recipients for the same envelope event. Implement idempotency by storing each processed envelope ID and event status combination in a database using the EnvelopeId and EnvelopeStatus fields from the Connect payload as a composite key, and skipping the Twilio dispatch if the same combination is already in the database before dispatching and inserting. The Recipient Mobile Phone custom tab field is empty when the envelope was sent directly from the DocuSign web interface rather than through your API integration, because the custom field value is only populated when your application pre-fills it via the API using the textTabs array in the recipient object. Add a fallback phone lookup in your middleware that queries your CRM or customer database using the recipient email address extracted from the Recipients array Email field, retrieving the stored mobile phone for that contact when the DocuSign custom field is empty. DocuSign Connect sends events for every recipient on the envelope including signers, carbon copy recipients, and witnesses, and your middleware may dispatch Twilio SMS to carbon copy recipients who should not receive an action-prompting SMS since they only receive a completed copy. Filter the recipients array by the recipientType field and only dispatch the signing prompt SMS to recipients where recipientType equals Signer, dispatching a different confirmation body to CarbonCopy recipients to inform them the document is complete without prompting unnecessary action.
How to Get More from This Integration
Build an SMS reminder escalation flow by storing each Envelope Sent event timestamp in your database and running a scheduled job every hour that checks for envelopes sent more than 24 hours ago that have not yet been signed, dispatching a second Twilio SMS reminder to the pending signatory with a direct signing link extracted from the DocuSign eSign REST API at GET https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients using your API credentials and reading the embeddedStartingView or recipientAuthorizationUrl from the response. Add a DocuSign signing link directly in the SMS body by generating a recipient view URL through the DocuSign eSign API at POST https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/views/recipient with the recipientEmail and recipientName from the Connect payload, and including the returned url in the Twilio SMS body so the signatory can tap the link to open and sign the document directly from their mobile browser without searching their email. Create a Twilio two-way SMS confirmation for declined envelopes by sending an SMS to the sender when a recipient declines, detecting an inbound reply from the sender using your Twilio inbound webhook, and if the reply is RESEND triggering a new DocuSign envelope void and re-send via the DocuSign eSign API at DELETE https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId} followed by a new envelope creation, enabling envelope management by SMS reply without logging into DocuSign. Extend the integration to voice by configuring a Twilio phone number for inbound calls from signatories, building a TwiML IVR that reads the envelope subject and current status by looking up the caller's phone in your envelope tracking database, and providing a keypress option that sends the signing link SMS on demand, giving signatories phone-based access to their pending documents.
Conclusion
DocuSign and Twilio together ensure every document requiring a signature reaches the recipient by SMS in addition to email, dramatically reducing signing delays and abandoned envelopes. Contact Telphi Consulting to build and configure the DocuSign Twilio SMS notification integration for your document workflow.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.