One Touch Sign (OTS)

FAQs

3min

How can we configure or build workflows in a sequential or parallel way for signing?

Signzy will provide the signing URL link for all the signers. In case you want to configure or build a sequential workflow, it is recommended to load on the fly the signing URL link for signer 1 and then wait for signer 1 to complete the signing. Once signer 1 completes the signing and you receive the confirmation on your event callback URL, you can load on the fly the signing URL for signer 2 and keep on rotating this till the last signer.

In case you want to configure or build a parallel signing workflow, you can load on the fly the signing URL for each of the signers and let the signers complete the signing process as per their convenience. 

How can we send the signing URL link to the end customers through SMS/Email/WhatsApp?

Signzy will provide you with the unique signing URL for each signer. As next steps, you can do the following - 

  • Collect customer contact information (phone number for SMS, email address for email, or WhatsApp number).
  • Craft a concise message with the signing URL and any necessary instructions.
  • For SMS: Send the message with the signing URL to the customer's phone number using an SMS gateway.
  • For email: Send an email with a clear subject line, the signing URL as a hyperlink, and instructions.
  • For WhatsApp: Send a brief message with the signing URL to the customer's WhatsApp number using an API or platform.
  • Consider automated reminders or follow-ups to prompt customers who haven't completed the signing process.

Remember to comply with data protection and privacy laws and respect customer preferences.

What all UI components should you create?

Your mobile/web application can include the following screens:

  • Preview Screen/Page: Shows the contract/agreement to be signed by the user, including e-stamped versions if needed.
  • Success Screen/Page: After the signer successfully signs using the e-sign service provider (ESP), this screen confirms the successful signing and displays the signed agreement.
  • Failure Screen/Page: If the signing process fails for any reason on the ESP page, this screen informs the signer about the failure reasons and provides instructions for the next steps in the workflow.
  • Success With Deviation Screen/Page: In cases where there's a mismatch in data (e.g., name, gender, year of birth) from the Aadhaar database after the signer signs, this screen displays the data from Aadhaar, the reason for the mismatch, and prompts the user to retry the signing.