Docusign and AI: which agreements still need a signature?
You are ready to start work, but nobody is sure whether the agreement has been signed. If your team keeps opening Docusign to answer that question, its AI connector may be worth trying. Start with a list of agreements waiting for signatures, then decide what each one needs. A missing signature does not always mean someone needs another reminder.
What has changed
Docusign’s MCP Server is now generally available after its beta period. MCP is a standard that connects AI assistants to other software. Supported assistants can use it to check envelope and recipient status. An envelope is a package of documents sent through Docusign for signing.
The update adds controls for account administrators and flags incomplete agreement-search results. Access to individual features still depends on your Docusign subscription.
A sponsored Docusign item in TLDR AI’s November 3 edition led us to this story. We checked the details in Docusign’s documentation. We have not tested the product ourselves.
Docusign’s general-availability announcementDiscovery: Docusign advertisement in TLDR AI, November 3
The useful answer goes beyond “not signed”
Imagine a fictional equipment-hire business preparing a booking. Its agreement has gone to two people in sequence. The first has signed; the second has not. Separately, the business has agreed to revise the delivery date.
A status assistant could help identify the remaining signer. It should not conclude that this person is ignoring the request. The delivery-date conversation may be the reason to wait, and that context may not be in Docusign at all.
Confirm the new delivery date before asking for the signature again. Docusign’s status and the team’s explanation are two different pieces of information. Use both to choose the next step.
What your current subscription includes
For the official Claude connection, Docusign’s setup guide lists a production Docusign account and Claude Pro, Team or Enterprise. It says a paid eSignature account can access eSignature tools, but not Workflow Builder or Agreement Manager tools.
Workflow Builder and Agreement Manager tools require an active IAM subscription, according to Docusign’s developer documentation. IAM means Intelligent Agreement Management. Before considering an upgrade, check whether the eSignature tools in your current account can answer the question.
Use the official connector for a live business account. A free Docusign developer account is a separate place to test with synthetic documents through a custom connection; it is not a free production subscription. Check the AI account’s connector access and usage limits before committing to a new plan.
Docusign’s Claude setup requirements and plan boundariesConnector options and IAM subscription requirements
Start with one status check
Once access is approved, ask the assistant to check envelopes you sent in the past seven days. Request a list of those still waiting for signatures, with each envelope’s ID, sending date, current status and remaining recipient. Ask it to flag incomplete results and to leave every envelope unchanged.
This is a proposed check; we have not tested it. Where possible, the person configuring the connector should enable only the tools needed to read status. Asking an assistant to leave records unchanged does not restrict its permissions.
Compare the answer with Docusign using the same account, sender and date range. An empty list is only useful if the search succeeded and covered the records you intended.
- Does the answer match Docusign’s list for the same filters, including any envelopes the assistant missed? Check the current recipient status too.
- Does the answer cover the intended date range and flag incomplete results instead of calling them a complete list?
- Can the team use the summary to choose a next action? Does it distinguish the recorded status from any explanation for the delay?
Is it worth using every week?
This is most promising when several people repeatedly interrupt each other to ask what is signed, or when you need to ask different questions each week. If a quick look at your existing Docusign list already answers it, keep that simpler routine.
If the real problem is that nobody owns the next step, connecting an assistant will not settle that responsibility. Agree who follows up and where the decision is recorded. Our CRM follow-up guide covers that separate part of the process.
For French- or German-speaking teams, check a sample answer in the language people actually use. Docusign says the MCP Server and its app interface launched in English; non-English interactions depend on the connected AI assistant.
Before moving to a daily schedule, make sure one manual review is useful. Docusign says custom agents and scheduled jobs need their own approval steps. Adding automatic reminders or sending agreements would be a separate workflow to design.
Give CRM follow-ups an owner and a next actionSupported languages and approval requirements
Sources
Discuss one recurring task.
Tell forvertz which status question interrupts your team and which tools you use. A fictional example is enough to discuss the workflow; do not send contracts or client details.
Discuss your workflowUpdated