Send a Document for E-Signature from Salesforce with Dochly

Updated June 2026 5 min read Native E-Signature

Once e-signature is configured and your templates have signature fields placed, sending a document for signing is a straightforward process — generate the document, click Send for Signature, add your signers, and send. This guide covers each step including what the signer experiences on their end.

Before you send

E-signature is enabled

E-signature must be enabled in Dochly Settings. If the Send for Signature button doesn't appear, see Set up native e-signature.

Template has signature fields

The document's template must have at least one Signature field placed. Without a signature field, the Send for Signature option will not appear after generation. See Set up signature fields.

Signer's email address

You need the signer's email address to send the request. For contacts, this is pulled from the Contact's Email field. For other object types, confirm the signer's email is known before sending.

PDF output template

E-signature only works with PDF output documents. If your template generates a Word/DOCX file, it cannot be sent for signature through Dochly native e-signature.

Step-by-step: sending for signature

Generate the document from a Salesforce record

Open the Salesforce record (Opportunity, Quote, Contract, or any other object where Dochly is configured). Click the Dochly button or use the Generate Document action. Select the template that has signature fields configured. Generate the document as you normally would.

The document must be successfully generated and stored before it can be sent for signature — Dochly sends the stored PDF, not a preview.

Click "Send for Signature"

After the document is generated, a Send for Signature button appears on the document preview or in the document's action menu. Click it to open the e-signature request panel.

If the button doesn't appear: confirm the template has at least one Signature field, confirm the document output is PDF (not DOCX), and confirm e-signature is enabled in Dochly Settings.

Add signers

In the signature request panel, add the people who need to sign the document:

Primary signer: Enter the signer's name and email address, or search for a Salesforce Contact
Additional signers: Click Add Signer to add more parties. Each signer must have a unique email address
Signing order: For multi-party documents, set whether signers sign sequentially (one after another) or in parallel (all at the same time)
CC recipients: Add email addresses that should receive a copy of the signed document but are not signers

Each signer you add should correspond to a signature field in the document. If you have two signers but the template only has one signature field, only one signed version is produced.

Configure the request settings

Before sending, optionally adjust the request-specific settings:

Subject line: The email subject the signer receives — defaults to your e-signature email template but can be overridden per-request
Message: A personal note to the signer included in the email body
Expiry: How many days the signing link remains active — defaults to your global expiry setting
Reminders: Whether to send automatic reminder emails to unsigned signers before expiry

Send the request

Click Send. Dochly sends the signature request email to each signer. You'll see a confirmation showing the request was submitted successfully, and the e-signature status on the Salesforce record updates to Sent.

A Dochly E-Signature record is created on the originating Salesforce record — this is where you track signing progress. See Track e-signature status.

After sending: what happens on the Salesforce record

Once the request is sent:

The E-Signature Status field on the Salesforce record updates to Sent
A Dochly E-Signature record is created showing each signer's individual status (Pending, Signed, Declined)
When all parties sign, the signed PDF is automatically stored in the Files list on the Salesforce record
If configured, Salesforce record fields update automatically on completion (e.g. Stage → "Contract Signed")

What the signer experiences

Signers do not need a Salesforce account or a Dochly account. Their entire signing experience happens through a secure link in the email they receive.

Receive the email

The signer receives an email from your configured from-name and from-address with a clear call-to-action button. The email includes the document name, your optional personal message, and the signing deadline.

Authenticate (if required)

If your e-signature settings require Email OTP or Access Code authentication, the signer is prompted to enter the code before they can access the document. For link-only authentication, they proceed directly after clicking the link.

Review the consent screen

Before signing, the signer sees your configured consent language confirming they agree to sign electronically. They must accept this to proceed.

Sign the document

The signer views the document in the browser. At each signature field, they are prompted to draw, type, or upload their signature. They scroll through the document and complete all required fields before finalising.

Signing complete

After signing, the signer sees a confirmation screen and optionally receives a copy of the signed document by email (depending on your settings). The Salesforce record updates in real time as each signer completes their signature.

Frequently asked questions

Yes. Add multiple signers in step 3. You can configure them to sign sequentially (each receives the request only after the previous signer has signed) or in parallel (all signers receive the request simultaneously). Set the signing order in the request panel before sending.

Yes. From the E-Signature record on the Salesforce record, use the Resend option to send the signing email again to signers who haven't signed yet. Resending does not create a new request — it sends the same signing link again to the pending signer.

Yes. Open the E-Signature record on the Salesforce record and use the Void/Cancel option. The signing link is immediately deactivated. The signer receives an email notifying them the request has been cancelled. You can then send a new request with a corrected document or updated signers.

If a signer clicks Decline in the signing interface, the E-Signature status on the Salesforce record updates to Declined. You receive a notification. The signer is prompted to enter a reason for declining, which appears on the E-Signature record. You can then void the request, address the concern, and send a new request.

Document sent. Next: Track e-signature status in Salesforce — see real-time signing progress, send reminders, and access the signed document once all parties have signed.