eSignature
Send generated documents for signing through Docupilot’s built-in signing solution.
With Docupilot’s built-in eSignature feature, you can seamlessly deliver documents for signing right after generation. Here’s how to set it up.
Configuring eSignature Delivery
To add a new eSignature delivery, choose the eSignature option from the list of deliveries available in the Deliveries tab.
Name: Give your delivery a name for easier identification on what this delivery does.
Email Subject: Set the subject line of the email your signer will receive. You can personalize this by adding dynamic tokens. Click on the {{}} button to get the list of already available tokens or type in a new new token (like {{client_name}})
Email Message: Define the body of the email your signer will receive. You can also add dynamic tokens to personalize this message. This message will be included as part of a standard email template. For example:
Dear valued {{client_name}},
Please find the contract "Contract-AcmeCorp-{{client_company}}" as discussed
and sign it at the earliest possibility.Sender Email:
Your email address will be the sender email. If another collaborator set themselves as a Sender, you will have an option to change the sender email to your Docupilot account email. Only a Sender can track and manage the envelopes created in their account.
Recipients:
This section allows you to configure the recipient details for signing the document. The recipient entries should match signature tags placed in your template. For example, if your template has {{eSign 1}} and {{eSign 2}} signature tags configured (read more about how to add signature tags), ensure there are 2 signers configured in your delivery.
Enter the Name and Email of each signer who should receive the invite to sign.
Click Add another to include multiple recipients.
Enable the Set Signing Order option to control the signing sequence. Recipients will receive the document one after another, based on the order you specify.
Add recipients in CC if needed.
Enable Optional Recipients if you want to skip invalid recipient entries.
More options:
Reminder Settings allow you to automate follow-ups with recipients to ensure timely signing of documents. You can choose to use your account’s default reminder configuration, or set custom preferences under Reminder Settings:
Expires in: Number of days before the Envelope expires
First reminder in: Days after which the first reminder will be sent to current signers
Remind Signer every: Frequency of follow-up reminders to be sent to current signers
Expiry Warning before: Days before expiry when a warning is triggered
Advanced Settings (Optional)
If you like to get notified on delivery errors, or on successful execution of deliveries, configure advanced settings to take advantage of integrations. Following advanced integration options are available:
On Success Callback URL: Configure a Web-hook URL which will be invoked with data containing the Envelope ID once the Envelope is created. To configure additional settings for callback URL like setting custom Headers and Additional Payload use the Advanced Configuration section.
Emails to Notify on Delivery Failure: Failed deliveries are typically notified to the workspace owner, workspace admins and workspace managers via email. You can configure additional email IDs here to receive notifications on delivery failures.
Save Configuration
Once all fields are set, click Save at the top right to finalize the eSignature delivery setup.
Removing Watermark
Documents generated in Test mode will include a watermark that reads:
“For demo purpose only. Powered by Docupilot.”
To remove this watermark, simply activate the template. Once the template is in Active status, any documents generated from it will no longer display the watermark.
Placing Signature tags in Document
Place customizable eSignature fields directly into your templates using special placeholder tokens. These tokens define where and how each signer interacts with the document—adding a signature, initials, date, plain text, or more.
Each signer needs to be assigned a Signer ID in sequential order. Use this ID consistently while placing signature tags to ensure correct field assignment.
eSignature Placeholder Tokens
Following is the list of all supported eSignature tokens
Signature
{{eSign signer_id req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the signature box (ex: 100, 110 Default value: 85)
height = height of the signature box (ex: 40, 50 Default value: 25)
Initials
{{eInitials signer_id req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the initials box (ex: 40, 50 Default value: 25)
height = height of the initials box (ex: 40, 50 Default value: 25)
Date Signed
{{eDateSigned signer_id req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the signed date (ex: 70, 80 Default value: 67)
height = height of the signed date (ex: 12, 15 Default value: 10)
Date
{{eDate signer_id req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the date field (ex: 70, 80 Default value: 67)
height = height of the date field (ex: 12, 15 Default value: 10)
Text Input
{{eText signer_id label=<fieldLabel> req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
label* = Label of the text field ("Role", "Company Name", etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the text field (ex: 100, 120 Default value: 80)
height = height of the text field (ex: 12, 15 Default value: 10)
Dropdown
{{eDropDown signer_id label req=<bool> width=<num> height=<num> values=<string>}}signer_id* = ID of the signer (1, 2, 3, etc)
label* = Label of the text field ("Country", "State", etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the dropdown (ex: 100, 120 Default value: 80)
height = height of the dropdown (ex: 12, 15 Default value: 10)
Checkbox
{{eCheckbox signer_id label req=<bool> width=<num> height=<num>}}signer_id* = ID of the signer (1, 2, 3, etc)
label* = Label of the text field ("Accept Terms", "Consent to terms", etc)
req = whether this field is mandatory (true/false Default value: true )
width = width of the checkbox (ex: 12, 13 Default value: 11)
height = height of the checkbox (ex: 12, 13 Default value: 11)
Examples
Below examples show how the placeholders can be used in your template:
Signature
{{eSign 1}}
{{eSign 2 req=false width=100 height=40}}
Initials
{{eInitials 1}}
{{eInitials 2 req=false width=40 height=40}}
Date Signed
{{eDateSigned 1}}
{{eDateSigned 2 req=false width=80 height=20}}
Date
{{eDate 1}}
{{eDate 2 req=false width=80 height=20}}
Text Input
{{eText 1 "Role"}}
{{eText 2 "Role" req=false width=120 height=20}}
Dropdown
{{eDropDown 1 "Country" values="US,UK,Australia,India"}}
{{eDropDown 2 "Country" req=false values="Canada,France,Germany,Italy,Greece" width=120 height=20}}
Checkbox
{{eCheckbox 1 "AcceptTerms"}}
{{eCheckbox 2 "Accept Terms" req=false width=13 height=13}}
Sample Word template
Please see the attached document for guidance on placing signature tags in a Word template.
Sample Excel template
Please refer to the attached document for guidance on placing signature tags in an Excel template
Last updated
Was this helpful?