eSignature eSignAnywhere - Use Case Example: Travel Insurance
Charly goes on a backpacker adventure for some weeks. At the Airport he finds out that he doesn’t have a travel insurance, therefore he is looking for travel insurance online. You find a list of available stories here.
Use Case Description
- The Customer (Charly) finds the company online
- Charly calls the Hotline
- Charly is answering the questions of the operator for preparing the travel insurance
- The travel insurance contract is prepared and reviewed by an supervisor of the operator
- The supervisor checks the data and conditions and the contract is automatically forwared to Charly
- Charly receives the contract via smartphone and authenticate himself via SMS-OTP
- Charly reads and signs the contract via Click2Sign
- Charly receives a copy of the finally signed travel insurance contract
The contract is prepared by the insurance customer relation management system and the signing transaction started with eSignAnyWhere. Therefore the workflow for integration is quite simple:
- Upload the contract as PDF document
- Send envelope with Workstep Configuration
- Wait on callback to download and archive the final contract
Here you can download the PDF and Workstepconfiguration used for this example. You can use for example SoapUI to text the example yourself (Attention: the example uses en-us language, so you have to add it to your organization; under settings > localization).
The ZIP file contains:
- The SoapUI call for UploadTemporarySspFile_v1
- The SoapUI call for SendEnvelope_v1
- The original PDF for Charly
You have to replace ##xyz## in the XML documents (with your API-Key, Sender-Email [user of your organization], recipient-Emails and Phonenumber of Charly for SMS-OTP).
<envelope> <name>Travel Insurance for Charly</name> <eMailSubject>Travel Insurance for Charly</eMailSubject> <eMailBody>Dear #RecipientFirstName#! Please sign this insurance contract.</eMailBody> <enableReminders>True</enableReminders> <firstReminderDayAmount>1</firstReminderDayAmount> <recurrentReminderDayAmount>1</recurrentReminderDayAmount> <beforeExpirationReminderDayAmount>1</beforeExpirationReminderDayAmount> <daysUntilExpire>2</daysUntilExpire> <!-- callback to your backend system on a completed envelope <callbackUrl>http://172.16.17.78:57550/default.aspx?EnvelopeId=##EnvelopeId##&myParamForMe=1234</callbackUrl> --> <callbackUrl /> <steps> <step> <emailBodyExtra /> <orderIndex>1</orderIndex> <recipientType>Signer</recipientType> <recipients> <recipient> <languageCode>en-us</languageCode> <eMail>##SUPERVISOREMAIL##</eMail> <firstName>Bob</firstName> <lastName>Supervisor</lastName> </recipient> </recipients> <workstepConfiguration>...</workstepConfiguration> </step> <step> <emailBodyExtra /> <orderIndex>2</orderIndex> <recipientType>Signer</recipientType> <recipients> <recipient> <languageCode>en-us</languageCode> <eMail>##Charly Email##</eMail> <firstName>Charly</firstName> <lastName>Backpacker</lastName> <authentications> <authentication> <method>SMS</method> <parameter>##Phonenumber##</parameter> </authentication> </authentications> </recipient> </recipients> <workstepConfiguration>...</workstepConfiguration> </step> </steps> </envelope>
You can see the first recipient is the supervisor (without authentication) and then followed by Charly with SMS-OTP authentication.
<authentications> <authentication> <method>SMS</method> <parameter>##Phonenumber##</parameter> </authentication> </authentications>