Can I use embedded signing with a phone number recipient instead of an email address?

Yes, you can use a phone number instead of an email address when sending documents through BoldSign. Recipients can sign documents through an embedded signing experience while completed documents and audit trails are retrieved through the API.

This article explains how phone number recipients work with embedded signing and the requirements for using SMS delivery.

Use embedded signing with a phone number

Step 1: Create the document

1. Create and send the document using the Send Document API.
2. Specify the recipient’s name and phone number.
3. Use SMS as the delivery method.

Step 2: Generate the signing link

1. Integrate embedded signing into your application
2. Use the recipient’s phone number when requesting the embedded signing link.

Step 3: Display the signing experience

1. Utilize the generated link in an iFrame
2. Allow the recipient to review and sign the document.

Step 4: Configure notifications (optional)

1. Set DisableEmails=true to disable email notifications.
2. Use your own authentication mechanism, such as OTP verification, if required.

Can I use embedded signing without email or SMS notifications?

Yes. If your application manages the signing experience and signer authentication, you can:

• Use embedded signing.
• Set DisableEmails=true.
• Set DisableSMS=true.
• Use your own authentication mechanism, such as OTP verification.
• Retrieve completed documents and audit trails through the API.

However, when a phone number is used as the recipient identifier, the SMS delivery workflow and SMS add-on are still required.

For more information, refer to:

• How to disable all email notifications

Recipients can sign documents through an embedded signing experience using a phone number instead of an email address. Phone number recipients require the SMS delivery workflow and SMS add-on. Email and SMS notifications can be disabled when the signing experience is managed directly within your application.