30 Claude Prompts for DocuSign

You are a customer onboarding specialist who sends contracts to clients who have never used DocuSign before. <context> Most of my clients are not technical and I keep getting phone calls asking how to sign a document I already sent them. </context> <inputs> - Client name: [CLIENT NAME] - Document type: [DOCUMENT TYPE] - Number of fields they must complete: [NUMBER] - Deadline to sign: [DATE] - Support contact if they get stuck: [NAME AND EMAIL] </inputs> <task> Write an email with clear step-by-step instructions for opening the DocuSign email, reviewing the document, completing each required field, and submitting the signature. </task> <constraints> Use plain language, no jargon like envelope or recipient. Keep steps to no more than seven. Do not assume the reader has signed anything digitally before. </constraints> <format> A short greeting, a numbered list of steps, and a closing line with the support contact. </format>

You are a client success manager introducing a new customer to electronic signing for the first time. <context> A new customer just asked why they received an email from DocuSign instead of directly from our company, and I want to reassure them before they sign anything. </context> <inputs> - Customer name: [CUSTOMER NAME] - Our company name: [COMPANY NAME] - Document they are about to receive: [DOCUMENT TYPE] - Security detail worth mentioning: [E.G. AUDIT TRAIL, ENCRYPTION] </inputs> <task> Write a short message that explains why DocuSign is being used, confirms it is legitimate and not a phishing attempt, and tells them what to expect next. </task> <constraints> Keep it under 120 words. Avoid sounding defensive about the phishing concern, just address it plainly. Do not use legal disclaimers that would scare a first-time user. </constraints> <format> A short paragraph followed by a one-line next-step sentence. </format>

You are a paralegal who prepares complex agreements with many fillable fields for signature. <context> Our agreement has initials on every page plus a signature block and a few date fields, and signers keep missing one and having to be re-sent the envelope. </context> <inputs> - Document type: [DOCUMENT TYPE] - Number of pages: [NUMBER] - Fields per page needing action: [E.G. INITIAL TOP RIGHT, SIGNATURE PAGE 4] - Signer name: [SIGNER NAME] </inputs> <task> Write a walkthrough that lists every field the signer must complete, in the order they will encounter them, describing where on the page each one appears. </task> <constraints> Be specific about page numbers and field locations. Do not skip any field, since a missed initial is what causes the re-send. Keep language simple enough for a non-lawyer. </constraints> <format> A numbered list, one line per field, with page number, field type, and location. </format>

You are a support specialist handling signers who only have a phone available to complete a document. <context> A growing share of our signers open the DocuSign email on their phone and get confused by the smaller screen layout. </context> <inputs> - Document type: [DOCUMENT TYPE] - Common sticking point on mobile: [E.G. FINDING THE SIGNATURE TAG, ZOOMING] - Signer device likely used: [IPHONE OR ANDROID] </inputs> <task> Write mobile-specific signing instructions that account for the smaller screen, including how to zoom, how to scroll between fields, and how to submit once finished. </task> <constraints> Assume the signer is using the DocuSign mobile browser flow, not the app, unless told otherwise. Keep each instruction to one short sentence. Avoid describing desktop-only features. </constraints> <format> A numbered list of five to eight short steps written for a phone screen. </format>

You are an account manager coordinating a document that two people on the client side must sign together. <context> Both signers work at the same company and I need them to know who signs first and that the document is not final until both have completed it. </context> <inputs> - Signer 1 name and role: [NAME, ROLE] - Signer 2 name and role: [NAME, ROLE] - Document type: [DOCUMENT TYPE] - Deadline: [DATE] </inputs> <task> Write a coordination note sent to both signers explaining the signing order, what happens after the first signs, and confirming the document is only binding once both signatures are in. </task> <constraints> Address both people by name in one message rather than sending two separate emails. Keep it under 150 words. State the deadline once, clearly. </constraints> <format> A short email with both names in the greeting, three short paragraphs, and a closing line stating the deadline. </format>

You are an accounts receivable coordinator who follows up on unsigned contracts without sounding pushy. <context> A contract has been sitting unsigned for three days and I want a gentle nudge that does not read as an escalation yet. </context> <inputs> - Signer name: [SIGNER NAME] - Document type: [DOCUMENT TYPE] - Days since sent: [NUMBER] - Original deadline: [DATE] </inputs> <task> Write a short, friendly reminder email that assumes the signer simply got busy, restates the deadline, and includes a direct line about needing help if something is blocking them. </task> <constraints> Keep it under 80 words. Do not use guilt language or mention consequences. Avoid the word urgent. </constraints> <format> One short email, subject line included. </format>

You are a sales operations manager sending a last-chance reminder before a DocuSign envelope automatically expires. <context> The envelope expires in two days and the signer has opened it twice but not completed it, so I need to convey urgency without sounding threatening. </context> <inputs> - Signer name: [SIGNER NAME] - Document type: [DOCUMENT TYPE] - Expiration date and time: [DATE AND TIME] - What happens if it expires: [E.G. MUST BE RE-SENT, OFFER LAPSES] </inputs> <task> Write a final notice email that states the exact expiration date and time, explains plainly what happens if it lapses, and offers one easy way to get help completing it now. </task> <constraints> State the deadline in the first two sentences. Keep tone respectful, not alarmist. Do not use all caps or exclamation points. </constraints> <format> One email with a clear subject line naming the expiration date, three short paragraphs. </format>

You are an office manager reminding a colleague inside the same company to sign an internal document. <context> An internal approval is stuck because a coworker has not signed yet, and I want a casual tone since we work together daily. </context> <inputs> - Colleague name: [COLLEAGUE NAME] - Document type: [DOCUMENT TYPE] - Reason it matters: [E.G. BLOCKS NEW HIRE START DATE] - Preferred channel: [EMAIL OR SLACK] </inputs> <task> Write a short, casual nudge appropriate for the given channel that reminds the colleague to sign and briefly explains why it is time-sensitive. </task> <constraints> Match the tone to an internal colleague, not a client, meaning it can be brief and informal. Keep it under 50 words. Do not include a formal signature block if the channel is Slack. </constraints> <format> One short message matching the specified channel's typical style. </format>

You are a deal desk manager who needs to escalate a stalled signature to the signer's manager. <context> I have sent two reminders directly to the signer with no response and the deal is now at risk of missing quarter end. </context> <inputs> - Signer name: [SIGNER NAME] - Signer's manager name: [MANAGER NAME] - Document type: [DOCUMENT TYPE] - Business impact of the delay: [E.G. MISSES QUARTER-END PRICING] - Number of prior reminders sent: [NUMBER] </inputs> <task> Write an escalation email to the manager that states the situation factually, notes the prior reminders sent, and asks for their help getting the signature completed by a specific date. </task> <constraints> Do not blame or criticize the signer directly. State facts and dates rather than opinions. Keep it under 130 words. </constraints> <format> One email with a clear subject line, a factual summary paragraph, and a specific ask with a date. </format>

You are a client relationship manager who follows up right after a client completes signing. <context> A client just finished signing a contract and I want to send a quick thank-you that also tells them what happens next. </context> <inputs> - Client name: [CLIENT NAME] - Document type: [DOCUMENT TYPE] - Next step for them: [E.G. KICKOFF CALL, INVOICE TO FOLLOW] - Next step date if known: [DATE] </inputs> <task> Write a short thank-you email confirming the signature is complete, telling them a signed copy is on its way, and outlining the next step in the process. </task> <constraints> Keep it under 90 words. Sound genuinely appreciative, not templated. Do not repeat contract terms already covered in the document. </constraints> <format> One short email with a warm opening line and a clear next-step sentence. </format>

You are a legal operations specialist building a reusable DocuSign template for non-disclosure agreements. <context> We send the same NDA structure to dozens of prospects and partners each month and want a repeatable template instead of rebuilding the envelope every time. </context> <inputs> - Parties typically involved: [COMPANY NAME AND COUNTERPARTY TYPE] - Standard fields needed: [NAME, TITLE, COMPANY, DATE, SIGNATURE] - Mutual or one-way NDA: [MUTUAL OR ONE-WAY] - Legal reviewer: [NAME] </inputs> <task> Outline the structure of a reusable DocuSign template for this NDA, listing each field, its type, and which party fills it in. </task> <constraints> Keep the field list to what is actually needed for signing, not full contract terms. Mark which fields are pre-filled by us versus completed by the counterparty. Note where legal review is required before reuse. </constraints> <format> A table with columns: field name, field type, who completes it, and a short note on template setup. </format>

You are a sales operations analyst standardizing how sales contracts get built in DocuSign. <context> Sales reps currently build each contract envelope manually and inconsistent field placement is causing pricing errors to slip through. </context> <inputs> - Contract type: [CONTRACT TYPE] - Variable fields per deal: [PRICE, TERM LENGTH, DISCOUNT, START DATE] - Fixed fields that never change: [COMPANY NAME, LEGAL TERMS] - Approver role required for discounts above a threshold: [ROLE, THRESHOLD] </inputs> <task> Map out which fields in the sales contract template should be variable per deal versus fixed, and specify where an approval step must be inserted when the discount threshold is exceeded. </task> <constraints> Be explicit about which fields a rep can edit and which are locked. State the exact threshold that triggers the approval step. Keep the map usable by someone who is not technical. </constraints> <format> A table with columns: field name, variable or fixed, editable by, and approval trigger if any. </format>

You are a procurement manager setting up a DocuSign template for new vendor agreements. <context> We onboard new vendors regularly and want a checklist that confirms the template has every required field before it goes out for signature. </context> <inputs> - Vendor agreement type: [AGREEMENT TYPE] - Required internal approvals before sending: [ROLE 1, ROLE 2] - Required vendor fields: [COMPANY NAME, TAX ID, BANKING INFO, SIGNATURE] - Compliance requirement to check: [E.G. INSURANCE CERTIFICATE ATTACHED] </inputs> <task> Build a pre-send checklist that a procurement coordinator runs through before releasing the vendor agreement envelope, covering internal approvals, required fields, and compliance attachments. </task> <constraints> Order the checklist in the sequence someone would actually complete it. Make each item a single yes or no check, not a paragraph. Flag any item that should block sending if unchecked. </constraints> <format> A numbered checklist, each item phrased as a yes or no question, with blocking items marked. </format>

You are a human resources operations specialist building a DocuSign template for new-hire offer letters. <context> We send offer letters weekly and want a consistent template that pulls in role-specific details without HR rewriting the letter each time. </context> <inputs> - Role types hired for: [ROLE TYPE 1, ROLE TYPE 2] - Variable fields per hire: [SALARY, START DATE, MANAGER NAME, TITLE] - Standard fields that stay the same: [BENEFITS SUMMARY, AT-WILL LANGUAGE] - Signer(s) besides the candidate: [HIRING MANAGER OR HR NAME] </inputs> <task> Structure the offer letter template by field, showing which parts are candidate-specific and filled in each time versus which sections stay fixed across all hires. </task> <constraints> Keep legal or benefits language flagged as fixed, not editable per hire. List variable fields in the order they appear in a typical offer letter. Note who signs and in what order. </constraints> <format> A table with columns: section, fixed or variable, and source of the value. </format>

You are a DocuSign template administrator responsible for keeping dozens of templates from going stale. <context> We have old versions of templates still in use because nobody archived them when the new version was approved, and it is causing outdated terms to go out. </context> <inputs> - Number of active templates: [NUMBER] - Departments that own templates: [DEPARTMENT LIST] - Current versioning practice, if any: [DESCRIPTION OR NONE] - Who approves new template versions: [ROLE OR NAME] </inputs> <task> Write a version control guide that defines how templates get named to show their version, who approves changes, and the process for archiving an old version once a new one is live. </task> <constraints> Include a specific naming pattern with a version number in it. Define exactly one owner per template who is accountable for archiving old versions. Keep the guide to under 200 words. </constraints> <format> A short guide with a naming pattern example, a three-step approval and archive process, and one line on ownership. </format>

You are a support specialist who helps signers who fail DocuSign's identity verification step. <context> A signer contacted me saying they cannot get past the ID verification screen and the deadline is close, so I need to respond quickly and clearly. </context> <inputs> - Signer name: [SIGNER NAME] - Verification method used: [SMS CODE, ID CHECK, KNOWLEDGE-BASED] - Error they described: [ERROR DESCRIPTION] - Alternate verification option available: [YES OR NO, AND WHAT IT IS] </inputs> <task> Write a response that acknowledges the problem, offers one or two concrete next steps to try, and explains what happens if the alternate verification method must be used instead. </task> <constraints> Do not ask the signer to share sensitive verification codes over email. Keep the tone calm and reassuring, not alarmed. Offer a real fallback, not just apologize. </constraints> <format> A short email with an empathetic opening line, two numbered troubleshooting steps, and a closing line about the fallback option. </format>

You are a compliance officer who explains DocuSign's audit trail to legal reviewers unfamiliar with the platform. <context> Our legal team is reviewing a signed contract for a dispute and asked what the audit trail actually proves about when and how it was signed. </context> <inputs> - Document type in question: [DOCUMENT TYPE] - Specific concern raised by legal: [E.G. WAS THE RIGHT PERSON SIGNING] - Audit trail elements available: [TIMESTAMP, IP ADDRESS, AUTHENTICATION METHOD] - Jurisdiction relevant to the dispute: [JURISDICTION] </inputs> <task> Explain in plain terms what the DocuSign audit trail records, how it addresses the specific concern legal raised, and what it does not prove so expectations stay realistic. </task> <constraints> Do not overstate what the audit trail can prove. Distinguish between what DocuSign records automatically and what would need separate evidence. Keep it under 200 words. </constraints> <format> A short explanation in three paragraphs: what the audit trail shows, how it addresses the concern, and its limits. </format>

You are a compliance analyst who files completed contracts for audit purposes. <context> I need a short summary attached to each Certificate of Completion so future auditors do not have to read the full technical document to understand what it confirms. </context> <inputs> - Document type: [DOCUMENT TYPE] - Number of signers: [NUMBER] - Completion date: [DATE] - Compliance framework this supports: [E.G. SOC 2, INTERNAL POLICY NAME] </inputs> <task> Write a one-paragraph plain-language summary that states who signed, when, and confirms the certificate supports the relevant compliance framework, suitable for attaching to the file. </task> <constraints> Keep it to under 100 words. State facts only, no interpretation of legal validity. Reference the compliance framework by name. </constraints> <format> One paragraph, ready to paste as a file note. </format>

You are an operations coordinator troubleshooting a DocuSign envelope that bounced because of a bad email address. <context> A signature request bounced back and I am not sure if the signer's email was wrong or if it landed in spam, and I need a plan to resolve it fast. </context> <inputs> - Signer name: [SIGNER NAME] - Email address used: [EMAIL ADDRESS] - Bounce message received, if any: [BOUNCE MESSAGE OR UNKNOWN] - Alternate contact method available: [PHONE OR SECONDARY EMAIL] </inputs> <task> Outline a step-by-step recovery plan to confirm the correct email, resend the envelope, and verify the signer actually received it this time. </task> <constraints> Cover both the case where the email was simply mistyped and the case where it may be a spam filtering issue. Keep steps actionable, not diagnostic theory. Limit to five steps. </constraints> <format> A numbered list of five steps, each one sentence. </format>

You are a data governance lead drafting a retention policy for signed DocuSign documents. <context> We store years of signed contracts with no clear rule on how long to keep them or when to delete them, and it came up in a recent security review. </context> <inputs> - Document categories: [CONTRACTS, NDAS, OFFER LETTERS] - Legal minimum retention period, if known: [NUMBER OF YEARS OR UNKNOWN] - Storage location: [DOCUSIGN, CRM, OR BOTH] - Who is accountable for enforcing deletion: [ROLE OR NAME] </inputs> <task> Draft a retention and deletion policy that sets a specific retention period per document category, states where each category is stored, and names who is accountable for enforcing deletion after the period ends. </task> <constraints> Use a specific number of years per category, not a vague range. Note where legal counsel should confirm the minimum before finalizing. Keep the policy under 250 words. </constraints> <format> A table with columns: document category, retention period, storage location, accountable role, followed by one line noting legal sign-off is required. </format>

You are an operations analyst who reports weekly on the state of all outstanding DocuSign envelopes. <context> Leadership wants a quick weekly view of what is signed, what is stuck, and what needs attention without digging into DocuSign themselves. </context> <inputs> - Envelopes sent this week: [NUMBER] - Envelopes completed: [NUMBER] - Envelopes stuck over the deadline: [NUMBER, WITH NAMES IF FEW] - Audience for the report: [ROLE, E.G. VP OF SALES] </inputs> <task> Write a short weekly status report summarizing the counts, calling out any stuck envelopes by name, and noting one action being taken to resolve the biggest bottleneck. </task> <constraints> Keep it to one screen, no more than 150 words. Lead with the numbers, not narrative. Name specific envelopes only if there are five or fewer stuck. </constraints> <format> A short summary line with the three counts, followed by a bulleted list of stuck items and one action line. </format>

You are a deal desk coordinator who hands off newly signed contracts to the teams that need to act on them. <context> A contract just got fully signed and I need to make sure finance, the account team, and legal all get what they need without me manually chasing each one. </context> <inputs> - Document type: [DOCUMENT TYPE] - Teams that need notification: [FINANCE, ACCOUNT TEAM, LEGAL] - System each team needs the contract logged in: [CRM, BILLING SYSTEM, CONTRACT REPOSITORY] - Any special terms to flag: [E.G. CUSTOM PAYMENT TERMS] </inputs> <task> Build a handoff checklist listing each team, what they need to receive or be notified of, and which system they need the record logged in. </task> <constraints> Order the checklist by urgency, most time-sensitive team first. Call out the special terms clearly so no team misses them. Keep each line to one action. </constraints> <format> A numbered checklist with columns implied in text: team, action, system. </format>

You are a sales operations specialist who standardizes how reps update the CRM after a contract is signed. <context> Reps update the CRM inconsistently after a DocuSign contract completes, so deal stages and renewal dates are often wrong. </context> <inputs> - CRM used: [CRM NAME] - Fields that must be updated: [DEAL STAGE, CONTRACT VALUE, RENEWAL DATE] - Where the signed PDF should be attached: [FIELD OR RECORD TYPE] - Deadline after signature to complete the update: [NUMBER OF HOURS OR DAYS] </inputs> <task> Write clear instructions for reps on exactly which CRM fields to update, in what order, and where to attach the signed document once a DocuSign envelope completes. </task> <constraints> List fields in the order they appear in the CRM if possible. State the deadline plainly. Avoid generic advice like keep the CRM updated, give the exact fields. </constraints> <format> A numbered list of steps, each naming the exact field and required value type. </format>

You are a business analyst studying how long contracts take to get fully signed once sent. <context> I have turnaround time data from DocuSign and want to understand where the process is slow so we can fix the actual bottleneck instead of guessing. </context> <inputs> - Average turnaround time currently: [NUMBER OF DAYS] - Turnaround time by document type: [DOCUMENT TYPE 1: DAYS, DOCUMENT TYPE 2: DAYS] - Step where most delay happens, if known: [ROUTING STEP OR UNKNOWN] - Target turnaround time: [NUMBER OF DAYS] </inputs> <task> Analyze the turnaround data provided, identify which document type or step is the likely bottleneck, and suggest two concrete changes to close the gap to the target. </task> <constraints> Base conclusions only on the data given, do not invent numbers. Suggest changes specific to DocuSign workflow settings, not generic advice like communicate better. Keep the analysis under 200 words. </constraints> <format> A short analysis paragraph followed by two numbered recommendations. </format>

You are a customer success operations manager building a tracker for contracts coming up for renewal. <context> We keep missing renewal windows because nobody flags a contract until it has already lapsed, and I want a structured way to track what is coming due each quarter. </context> <inputs> - Number of contracts expiring this quarter: [NUMBER] - Lead time needed to start renewal outreach: [NUMBER OF DAYS BEFORE EXPIRATION] - Owner responsible for each renewal: [ROLE, E.G. ACCOUNT MANAGER] - Renewal document source: [DOCUSIGN TEMPLATE NAME] </inputs> <task> Design a quarterly renewal tracker structure that flags contracts by expiration date, assigns an owner, and marks when renewal outreach should start based on the lead time. </task> <constraints> Sort by expiration date, soonest first. Make the lead time trigger explicit as a calculated date, not a vague reminder. Keep the structure simple enough for a spreadsheet. </constraints> <format> A table with columns: contract name, expiration date, outreach start date, owner, status. </format>