SMS verification is a security feature that requires recipients to verify their identity via a one-time code sent to their phone before they can sign a document. When SMS verification is enabled for a recipient, they receive a unique code via text message during the signing process and must enter it to proceed with their signature. This adds an extra authentication layer beyond the document access link, helping protect sensitive agreements and high-value deals from unauthorized signing.

SMS verification strengthens document security by confirming the recipient's identity at signing time. This is particularly valuable for:

Unlike a simple document access link, SMS verification ensures that the person who received the link is the same person completing the signature.

SMS verification is configured individually for each recipient in the Recipients panel. You can enable it when creating a new document or adjust it after sending.

To enable SMS verification:

You can apply SMS verification to one recipient or multiple recipients on the same document. Each recipient configured with SMS verification will be required to verify via their phone number before signing.

For SMS verification to work, the recipient must have a valid phone number on file. When you add a recipient, you can enter their phone number in the recipient details. The phone number must be a mobile number capable of receiving text messages. If a recipient's phone number is missing or invalid, they will see an error message during the signing process prompting them to provide a valid number before the SMS code can be sent.

SMS verification is triggered during the signing flow, not when the document is initially sent. Here's what happens:

Step 1: Recipient opens document
The recipient receives an email or link to your document and opens it in their browser.

Step 2: Recipient completes signing fields
They fill out all required form fields, initials, dates, or other content as needed.

Step 3: SMS code is sent
When they click the final signing button or attempt to confirm their signature, GetAccept sends a one-time verification code to their registered phone number via SMS.

Step 4: Recipient enters code
A code entry screen appears in the signing interface. The recipient must check their phone for the incoming text message, retrieve the code, and enter it in the code field.

Step 5: Signature is confirmed
After entering the correct code, the signing process completes and the document becomes fully signed.

The entire process is streamlined within the signing interface , recipients do not need to leave the document or use a separate app to verify.

From the recipient's perspective, SMS verification is straightforward. After filling out all required document fields, they see a prompt to verify via SMS. They receive a text message containing a 6-digit (or similar) code, which they then paste or type into the verification field shown on the signing page. The code is time-limited and valid for a short window (typically a few minutes), after which a new code must be requested. Once the correct code is entered, signing is complete immediately.

Recipients appreciate that verification happens seamlessly within the document interface , they do not need to switch between apps or manage separate authentication systems.

GetAccept offers multiple recipient verification options. SMS verification works alongside these methods, and you choose which is best for each recipient:

SMS Verification: Recipient receives a one-time code via text message. Confirms identity at signing time. Suitable for most documents and recipients with mobile numbers. No special authentication infrastructure required.

Password Verification: Recipient must enter a password you set before opening or signing the document. Useful when you want to control access before the signing step. Does not require a phone number.

Electronic Identification (eID): Recipients use their national electronic ID, BankID, or similar government-issued credentials. Provides government-level identity verification and qualifies as Advanced Electronic Signature. Available in select countries and on certain plans.

Qualified Electronic Signature (QES): The highest legal signature level under EU eIDAS regulations. Recipients sign using a certified QES method. Legally equivalent to a handwritten signature in the EU. Available on Professional and Enterprise Plus plans and requires specific configuration.

For most business documents and high-value deals, SMS verification offers a strong balance of security and user experience. For documents requiring the highest legal assurance in EU markets, consider eID or QES methods.

SMS verification is available on GetAccept's standard plans. Confirm that your plan includes SMS verification by checking your Entity Settings or contacting your account administrator. Enterprise accounts have full access to SMS verification and other advanced signing methods.

SMS verification relies on SMS delivery to recipients' phones. Depending on your entity's SMS settings and carrier agreements, SMS charges may apply. These costs are typically included in your plan's SMS allocation or billed separately per message sent. Review your subscription details or contact GetAccept support to understand SMS costs specific to your account.

SMS verification and SMS reminders are two distinct features and should not be confused:

SMS Verification is an authentication requirement during the signing process. It occurs when a recipient attempts to sign and requires them to enter a code received via text message. It is a one-time event tied to the signing action.

SMS Reminders are automated follow-up messages sent to recipients if they have not opened or signed a document within a specified time period. Reminders are configured in Communication Templates and send notifications on a schedule you define (e.g., after 3 days of no activity). Reminders are optional and designed to encourage engagement, not to verify identity.

You can use both features together: SMS verification protects the signing moment, while SMS reminders keep recipients engaged if they haven't yet completed the document.

SMS verification can be configured in two scenarios:

Before sending: When you create a document draft and add recipients, you can click the padlock icon and select SMS verification before clicking "Send." This ensures every recipient who needs verification has it configured from the start.

After sending: If you've already sent a document, you can still add or modify SMS verification. Open the Send-out, go to the Recipients tab, click the padlock icon next to any recipient, and select SMS verification. The change takes effect immediately for that recipient's next signing attempt or if they have not yet opened the document.

Changing verification methods after sending does not interrupt recipients who are in the middle of signing , they complete their current verification step, and new requirements apply if they return later.

Use SMS verification for:

Do not require SMS verification for:

Communicate clearly: If you enable SMS verification, briefly let the recipient know in your sending email that they will receive a verification code during signing. This sets expectations and reduces confusion.

Consider the total verification flow: If you require SMS verification on multiple recipients, be aware that each will need to complete the code entry step. For documents with many signers, balance security with signing friction.

Combine with other methods: Use SMS verification for some recipients and password or eID verification for others, depending on their risk profile and capabilities. You are not locked into one method per document.

For more information on signing methods and recipient management, see: