Send a Document for E-Signature from Salesforce with Dochly
Before you send
Three things must be in place before you can send a document for signature:
Dochly → Settings → E-Signature must be enabled with authentication, consent language, and storage all configured. If not done yet, complete Set up native e-signature first.
The template must have at least one signature field placed in the document layout. Without a signature field, signers have nowhere to sign. See Set up signature fields in a template.
You need the signer's email address to send the request. For customer documents, the Contact's email on the Salesforce record is typically used. Confirm the Contact email field is populated before sending.
You send a generated document for signature — not a template directly. Generate the document from the record first, then send the generated file for signature. The Send for Signature button appears on the generated document, not on the template.
Step-by-step: sending a document for signature
Generate the document from the Salesforce record
Open the Salesforce record (e.g. the Opportunity). Click Generate Document and select the template that has your signature fields configured. Wait for generation to complete — the document appears in the Files related list.
If you want to generate and immediately send for signature in one workflow, you can check Send for Signature after generation in the generation modal — this takes you directly to the signature sending panel after the document is created.
Click Send for Signature
On the generated document in the Files related list, click the Send for Signature button. Alternatively, open the Dochly activity panel on the record — it shows all generated documents and a Send for Signature action next to each PDF file.
The Dochly Send for Signature modal opens. This is where you configure all signing options before the request goes out.
If you don't see the Send for Signature button on a generated document, confirm e-signature is enabled in Dochly Settings and that the document is a PDF. DOCX and XLSX files cannot be sent for signature — only PDF.
Add signers
In the Signers section of the sending modal, add each person who needs to sign. For each signer, enter:
You can pre-fill the first signer's email from the Contact linked to the record by clicking Add from Record. For internal signers (your own team), enter the email address manually or use the user picker.
Each signer corresponds to a signature field in the document — if your template has two signature fields assigned to two signers, both signers must be added here. Signer order in this list determines signing sequence when sequential signing is used.
Set signing order
Choose how multiple signers sign the document:
One at a time, in order
Signer 1 receives the request. After they sign, Signer 2 receives their request. Each signer only gets notified when it's their turn.
All at the same time
All signers receive the request simultaneously. Anyone can sign in any order — the document completes when the last signer finishes. Faster but less controlled.
For most contract workflows, Sequential is recommended — it ensures the customer signs before the internal approver countersigns, which is the expected order for most legal agreements.
Configure delivery options
Before sending, review these optional delivery settings in the modal:
Add a personalised message to the signature request email. This appears above the Sign button in the email. Keep it brief — one or two sentences explaining what the document is and what you need from the signer.
Add email addresses to be CC'd on all signing notifications — useful for keeping a manager or admin informed without adding them as a signer. CC recipients receive all status emails but do not sign.
Override the org-level signing expiry for this specific request. Use this for time-sensitive documents that should expire sooner than the default (e.g. 48 hours for a proposal with a same-week deadline).
Override the default reminder schedule for this request. Useful when you know the signer has a specific deadline and want reminders more or less frequently than the org default.
Review and send
The modal shows a summary — document name, signer list, signing order, and delivery settings. Review carefully, then click Send.
The signature request is sent immediately. For sequential signing, Signer 1 receives the email right away. For parallel signing, all signers receive the email simultaneously.
After sending, the Dochly signature tracking panel on the Salesforce record updates to show the current signing status — who has been notified, who has opened the document, and who has signed. See Track e-signature status for full tracking details.
Once sent, the document content cannot be changed. If you need to modify the document after sending, you must void the current request and generate a new document from an updated template.
Sequential vs parallel signing — when to use each
The customer must sign before an internal approver countersigns. A manager needs to review the signed customer document before adding their own signature. Legal requires a specific signing order to be documented in the audit trail. Most contract and NDA workflows.
Multiple parties can sign in any order — e.g. two co-founders both need to sign a partnership agreement. Speed is more important than signing order. All signers have equal visibility to the document before signing. Both signers are internal team members.
What signers experience
Understanding the signer's experience helps you set expectations with customers and troubleshoot signing issues when they arise.
Email received
Signer receives a branded email with your company's from-name, subject line, and custom message. A prominent button links to the signing page.
Document preview
Signer sees the full document in their browser before signing. They can scroll and read the entire content. No account required — works on mobile and desktop.
Consent screen
Signer confirms they agree to sign electronically. The consent language you configured in setup appears here. Required before accessing the signature fields.
Signing
Signature fields are highlighted in the document. Signer draws, types, or uploads their signature. Date fields auto-populate. All required fields must be completed before submitting.
Confirmation
After signing, the signer sees a confirmation screen. If all parties have signed, they receive the completed document by email. If others still need to sign, they're notified it's in progress.
Completed document
Once all parties sign, every signer receives the final signed PDF by email (if completion emails are enabled). The signed document is also stored on the Salesforce record.
After sending — what happens next
After clicking Send, the signature workflow runs automatically. Here's what happens at each stage:
The Dochly signature tracking panel on the Salesforce record updates in real time — showing email sent, document opened, signing started, and signed status for each signer. See Track e-signature status.
If the signer hasn't signed by the configured reminder date, Dochly sends automatic reminder emails without any manual action required. See Set up reminders and expiry.
When all parties sign, the completed document is automatically stored on the Salesforce record. See Store signed documents in Salesforce.
If the signer reports not receiving the email or you need to cancel the request, use the Dochly signature panel on the record — Resend sends a new notification, Void cancels the request permanently.
Frequently asked questions
Your document is sent and the signing workflow is running. Next in this series: Track e-signature status in Salesforce with Dochly — monitor signing progress, view the audit trail, and take action on outstanding requests directly from the Salesforce record.
Rated 5 stars · Native Salesforce app · Free to install