2-factor authentication (2FA) or one-time passcodes (OTP) are common use cases for toll-free messaging.
Although the type of consent may vary, all business messaging use cases – including 2FA/OTP messaging – requires consent from the end user to send messages. For 2FA/OTP messages, you must have express consent to send a 2FA or OTP text message. Typically, express consent for a 2FA/OTP text message is obtained by informing the user they will receive a 2FA/OTP notification at the phone number they provide, or informing them when they update their phone number in an online profile.
If you need more info on messaging best practices when it comes to consent, please refer to the
Unverified toll-free numbers (TFNs) and Pending Verification toll-free numbers (TFNs) are subject to industry-wide message blocking. Unverified toll-free numbers are TFNs that have not completed the toll-free sender verification process. Pending Verification toll-free numbers are TFNs where a verification request has been submitted, but the request is pending review and approval.
Note: In the past it was possible to send messages from an Unverified TFN or Pending Verification TFN. However, as a result of industry-wide changes, all toll-free numbers, regardless of the use case, must be Verified to originate traffic.
UNVERIFIED toll-free numbers (TFNs) are subject to industry-wide message blocking, effective November 8, 2023.
PENDING VERIFICATION toll-free numbers (TFNs) are subject to industry-wide message blocking, effective January 31, 2024.
All toll-free numbers (TFNs) must be in a VERIFIED state in order to originate traffic.
Unverified TFNs and TFNs pending verification will be blocked with Sinch error code 64 “Blocked due to exceeded quota”. Please see Toll-Free Delivery Report Errors for a full list of SinchToll-Free error codes.