Phone authentication is a premium second-factor authentication method that secures a strong verification of identity by having the recipient authenticate with a code delivered to their phone (upon their request).
The authentication process initially presents the recipient with a notification that they must enter a verification code to access the agreement. This notification provides:
Once the Send Code button is clicked:
When the authentication is passed, the recipient is granted access to view and interact with the agreement.
If the recipient closes out the agreement for any reason before completing their action, they will have to re-authenticate.
The Phone authentication method is available to the business and enterprise service plans only.
Phone authentication is a premium authentication method that has a per-use charge.
When Phone authentication is enabled, the sender can select Phone from the Authentication drop-down just to the right of the recipient's email address:
If a "bad" phone number is detected when composing the agreement, the process stops and an error message is presented at the top of the page:
As a premium authentication method, Phone authentication transactions must be purchased and available to the account before agreements can be sent with the method configured.
Phone authentication transactions are consumed on a per-recipient basis.
e.g., An agreement configured with three recipients authenticating by Phone consumes three authentication transactions.
Configuring an agreement with multiple recipients decrements one transaction for each recipient authenticating by Phone authentication from the total volume available to the account.
Track available volume
To monitor the volume of Phone authentications available to the account:
Accounts that have purchased the service under the VIP licensing program have a modified format Track Usage pop-out to represent better the number of transactions within the context of their licensing scheme.
The audit report clearly identifies that a phone number was used for identity verification.
If the agreement is canceled due to the recipient being unable to authenticate, the reason is explicitly stated:
Phone authentication has two sets of controls, which are available to be configured at the account and group levels:
The option to use phone-based authentication can be enabled for senders by navigating to Send Settings > Identity Authentication Methods
Phone authentication requires the admin to configure a non-zero number of failed attempts allowed before the agreement is canceled. Five is the default.
This setting can be configured on the Security Settings page:
If you do not see the settings available in your menu, verify that the authentication method is enabled on the Send Settings page
If the limited number of Phone authentication attempts fails, the agreement is automatically canceled.
The agreement's originator is sent an email announcing the cancelation with a note identifying the recipient that failed to authenticate.
No other parties are notified.