...
Send on Behalf - the user gets to choose both who the email is from, and who signs on behalf of the company.
Multi branding - be able to choose the branding of the e-Signature app based on the document being sent.
Usually based on the Salesforce record, or Record Type where the e-Signature originates.
Multi domain - be able to send from different domains and email addresses.
Quick to send
This is highly depended on the Document Generation tool though, as sometimes it does take a while to generate a complex document, but people just want to get document out for signing quickly.
SMS deliverability, SMS reminders or even sign via Mobile device.
Save to Dropbox or another document management App.
Be able to send ad-hoc documents completely manually, choosing the contacts, or entering the email, uploading the document, attaching the signer details etc.
And I want that to be done from Salesforce.
Options other than “typing” a signature.
Originator is notified immediately via Salesforce if the signer has a question or cancels signing.
Very large documents, possibly merged from multiple sources - eg a Doc Gen, Appendices, custom attachments.
...
Write back to Salesforce
e-Signature is not a forms tool, and you don’t use it bulk updating Salesforce, but simple notes or comments that the recipient adds, needs to be saved back to Salesforce, or a few fields that need to be updated from the signed document (eg Option A or Option B is chosen).
Send a Draft, allow the recipient to comment back, or approve for signing. That way you are only charged for the signing that is needed rather than having to cancel a heap of “envelopes” and re-sending. Allow the recipient to be in charge of this process. (This works in some cases).
Merge two or more merged documents into one e-Signing package.
Features that I would like
The users never need to rely on their Inbox. Eg to sign their side of the Contract they are alerted via Salesforce, and imitate initiate the signing via Salesforce (I’ve never seen that though, oh, now I have!).
Chatter is used extensively.
Generate the e-Sign via Flow
...
Pre-fill details onto a pre-prepared template. This is what Document Generation is for. I have never needed to “fill out PDF forms”.
Saved Templates that the users chooses to send from. Again, this is what Doc-Gen is for.
In-person signing
Signing rooms
Red-lining (full CLM)
Multilingual
Signer Authentication (although I’m sure it will be something I need to do soon).
Probably SMS authentication is the easiest for the signer.
Identity Verification Integration (but there are some companies that do need this level of feature, and just because they do, does not mean that they need a full CLM functionality).
Bulk e-Signing - sending out multiple documents at once to different people for e-Signing (some companies may need it, but I haven’t worked with that need).
Signer Attachments - signers adding their own attachments
Payments integrated with signing.
NOTEs: Document Generation Requirements
Just noting these here because I’m having difficulty with a Doc Gen app and thinking they are missing basic functionality.
Formatting of dates in any format - no having to create fields to format dates, because Salesforce completely sucks at that.
Formatting currency in any format - bonus points for full excel style formatting where you can format for positive, negative and null values (I’ve never seen that though).
Formatting percentages - with or without decimals, and handling null (eg display as 0%).
Formatting numbers - with or without decimals, and handling nulls.
Conditionally displaying text - easy with Word, I just use Word formulas, but if your Doc Gen solution is not on Word, it needs to be easy and robust and allow for many conditional elements in the document.
Conditionally displaying paragraphs, sections, bulleted list points etc. Your conditional text is not always inline text, it could be whole paragraphs or even pages.
Displaying Images from merge fields - we are not in 1999 anymore - this must be a given. Including Re-sizing the images to fit the desired area.
Displaying HTML from within Salesforce - yes this is hard because Salesforce Rich Text fields suck badly, but you have to be able to do this, at least basically.