SMS Tools Walkthrough

There are a couple of options that we provide through our SMS Tools add-on that can help improve your workflow by enabling SMS features. Take a look at the different features we offer to see if this add-on can increase the capability for your workflow.

SMS Tools Add-on

The SMS Tools add-on is an additional charge that provides two SMS-based features that can be included in your workflow: SMS authentication and SMS delivery. This add-on can be used with a Standard API plan or higher. For more details on our API plans, please see our plans and pricing page. For any questions regarding the SMS Tools add-on option or billing, please contact our Sales team with this form.

SMS Authentication

The SMS authentication feature provides the option to include a unique SMS authentication code that is sent to the signer once the signature request is submitted. In order for the signer to open and complete their portion of the document, they’ll need to provide the unique code sent via SMS. This adds an additional layer of security when having your signers complete their signature requests.

SMS Delivery

The SMS delivery feature provides a link to sign the signature request via both email and SMS. Once the signature request is sent to the signers, each signer will receive both an email notification and an SMS message with a link to complete their portion of the document.

Requirements

Updating Admin Console Settings

Admin Console	Images
Access Admin Console: 1. Log in to your Dropbox Sign account. 2. Select the initials in the top right corner of the home page and click on “Admin Console”. 3. Select the “Settings” in the left panel on the Admin Console and then click on “Signature Requests”. 4. Scroll to “Signature Request options”.
Steps to update signer authentication: 1. For the “Signer authentication” option, click the toggle switch to the right to enable it. 2. Select one or both of the following: - Access code: enter the code you’d like to give to the signer for document access. - Text message: enter the signer’s mobile number. 3. Click “Save settings” in the bottom right corner.
Steps to update signature request delivery methods: 1. For the “Signature request delivery methods” option, click the toggle switch to the right to enable it. Signature requests can now be sent by both email and text message. 2. Click “Save settings” in the bottom right corner.

Using SMS Authentication and SMS Delivery

Both features available for the following API endpoints:

• Send Signature Request
• Send with Template
• Bulk Send with Template
• Create Embedded Signature Request
• Create Embedded Signature Request with Template
• Embedded Bulk Send with Template

Process

Steps	Images
1. For SMS authentication, once you send your request your signers will receive an email with a link to sign the document.
2. The signer will then open that link and they will be prompted to verify their identity.
3. At this point, they can select the “Send code” button to receive a 6-digit code via text message to the phone number associated with that signer (redacted in the prompt). They can then enter the code and continue with the signing process. Additionally, they can request the code to be sent again if needed.
4. Once the correct code has been entered, the document will appear ready for the signer to complete their portion of the document.

Steps	Images
1. For SMS delivery, when the request is sent, both an email and a text message with a link to sign the document will be sent to the signers.
2. They can then complete their portion of the document by clicking on either link. Once signed, they will receive a text message stating they have completed it and to check their email for the completed document.
3. Additionally, if enabled on your account, they will see the 3 and 7 day signature request reminders via text message as well.

Examples:

SMS Authentication

1
{
2
  "title": "NDA with Acme Co.",
3
  "subject": "The NDA we talked about",
4
  "message": "Please sign this NDA and then we can discuss more. Let me know if you have any questions.",
5
  "signers": [
6
    {
7
      "role": "Client",
8
      "email_address": "jack@example.com",
9
      "name": "Jack",
10
      "order": 0,
11
      // Add E.164 formatted phone number
12
      "sms_phone_number": "12345678901",
13
      // Add the phone number type as authentication
14
      "sms_phone_number_type": "authentication"
15
    }
16
  ],
17
  "file_urls": [
18
    "https://www.dropbox.com/s/ad9qnhbrjjn64tu/mutual-NDA-example.pdf?dl=1"
19
  ],
20
  "signing_options": {
21
    "draw": true,
22
    "type": true,
23
    "upload": true,
24
    "phone": true,
25
    "default_type": "draw"
26
  },
27
  // Test mode must be false
28
  "test_mode": false
29
}

SMS Delivery

1
curl -X POST 'https://api.hellosign.com/v3/signature_request/send_with_template' \
2
  -u 'YOUR_API_KEY:' \
3
  -F 'client_id=YOUR_CLIENT_ID' \
4
  -F 'template_ids[]=61a832ff0d8423f91d503e76bfbcc750f7417c78' \
5
  -F 'title=NDA with Acme Co.'
6
  -F 'subject=The NDA we talked about' \
7
  -F 'message=Please sign this NDA and then we can discuss more. Let me know if you\nhave any questions.' \
8
  -F 'signers[0][role]=Client' \
9
  -F 'signers[0][name]=Jack' \
10
  -F 'signers[0][email_address]=jack@example.com' \
11
  -F 'signers[0][sms_phone_number]=12345678901' \
12
  -F 'signers[0][sms_phone_number_type]=delivery' \
13
  -F 'signing_options[draw]=1' \
14
  -F 'signing_options[type]=1' \
15
  -F 'signing_options[upload]=1' \
16
  -F 'signing_options[phone]=1' \
17
  -F 'signing_options[default_type]=draw' \
18
  -F 'test_mode=0'