This article serves as a one page reference for CS Ops new hires at all levels during their first few weeks supporting the eSignature product.
What Does the eSignature Product Do?
Sertifi’s eSignature product allows hotels to send documents to a client for electronic signature without collecting any payment or credit card details.
The product uses Data Tags within documents to configure required actions such as:
Signatures
Initials
Required uploads
Required acknowledgements
eSignature is designed for agreements and contracts where payment collection is not required.
Required Settings for eSignature to Function
The following settings must be configured for eSignature to work correctly.
Sending Page Defaults
Sending Page Defaults control signer visibility, CC behavior, and document upload options during the sending process.
Administration → Account Settings → Sending Page Defaults
These settings allow Admins to:
Configure signer levels that appear during sending
Automatically add CC recipients
Enable Show Signature Documents
Enable Show Reference Documents
These options allow Admins to upload signature and reference documents directly from their computer during the send flow.
Additional Settings
Other optional settings may be enabled depending on the client’s workflow, but the Sending Page Defaults listed above are the minimum required settings for eSignature usage.
Integrations Using eSignature
The eSignature product is required for integrations with the following platforms:
Delphi
Salesforce
Amadeus
To verify whether real time integrations are enabled:
Administration → Account Settings → Real Time Updates
If enabled, the integration will be listed as active within this section.
Key Takeaways for CS Ops
eSignature is used for documents that do not require payment collection
Data Tags control required signer actions
Sending Page Defaults are mandatory for proper document sending
eSignature is required for Delphi, Salesforce, and Amadeus integrations
Comments
0 comments
Please sign in to leave a comment.