For those who may be unfamiliar, DocuSign for Salesforce integrates two industry leading, cloud based tools to easily launch, track, and capture customer eSignatures using Salesforce. Commonly, DocuSign for Salesforce is used to facilitate the capturing of electronic signatures from customers directly from Salesforce. Usually, as a part of the Contract Lifecycle process. However, did you know that DocuSign for Salesforce can do much more that capture an eSignature?
Does your sales cycle include installation or inspection services? Would capturing this information help you be a better partner to your third party entities? Rather than exploring the app exchange or creating a custom solution in Salesforce, a simpler and more efficient solution is to leverage DocuSign for Salesforce.
Let’s look at a hypothetical. “ABC Inc.” is a Direct-to-Consumer based business. They have a wide range of customizable products that can be tailored to best meet what the customer needs. Their products come with an installation service which involves someone who comes and installs the product that has been ordered. Typically, these installers are third party contractors who have been vetted by the company.
“ABC Inc.” uses DocuSign for Salesforce to capture customer signatures and “check a box” that signatures have been received. While “ABC Inc.” is confident in their customer’s buying experience, they still have little insight into the experience with the installation process. This does not just extend to the customer’s experience, but to their partners as well. So how can they fix this blind spot?
First, they will need to create a Custom Field on the desired Salesforce object to capture incoming information that is defined by the envelope recipient.
Second, they will need to create Custom Tags through the DocuSign Admin Tab in DocuSign for Salesforce. They will need to define an anchor text and input this anchor text onto their template. This will allow DocuSign to “read” where on the template to prompt the envelope recipient to input the information that they are trying to capture.
Finally, they will need to enable a custom tag to write back to salesforce by selecting the “Relate Field to Salesforce” checkbox. Now in the newly available drop down, they can select the object where the new field from the first step is located. Just like that, the problem is fixed! Easy enough, right?
For more information or another example, please click here.
About Nick Petersohn:
Nick is a consultant at Statera with over four years of Salesforce experience. He is a graduate of Colorado State University and the University of Northern Colorado.