How to Create a TFN Registration

TFN Registration APIs allow you to create and submit registrations, update details, and get status. Enterprises that want to send and receive SMS and MMS messages over Toll-Free Numbers need to have their numbers "registered" for reliability purposes.

A Registered Toll-Free Number means that the message content has been reviewed and does not fall under the Disallowed Content Policy. The message sender’s traffic type is vetted, the number is only associated with the company submitted on the registration request and does not send spam (unsolicited messages) to users.

An Unregistered TFN is restricted and has not successfully completed the registration process. All unregistered TFN messages get blocked. It is recommended to register all TFNs regardless of message traffic volumes.

Prerequisites

The following is a list of general prerequisites:

  • Users can only send messages with the same use case that has been registered with their registration.
  • Resellers of Vonage SMS services will, in most cases, need to register their users' TFN registrations for them.

Register a Toll-Free Number

  1. Login to the Vonage API Dashboard and under the Phone Numbers tab, select the Toll-Free Number Registration tab on the left-hand bar to access the Toll-Free Number Registration page. If you do not have a Vonage account, you can create one for free here.
  2. If you have not purchased a US Toll-Free Number, you will be asked to navigate to Buy Number to buy/purchase a US Toll-Free Number.
    Note: US TFNs offer coverage in both the US and Canada.
  3. Go to Toll-Free Number Registration and click on Register to access the TFN registration form.
  4. Follow the three screens (steps) to complete the Toll-Free Number Registration form request.
    1. The Business Profile screen includes fields related to the business/content provider.
    2. The Toll-Free Number Information screen includes fields related to the messaging campaign.
    3. Review the confirmation screen
    4. Agree to Vonage Terms and submit.
  5. Once your request is submitted, a confirmation message is displayed.
  6. Navigate back to the Toll-Free Number Registration screen to track the status of your request.

This process can also be completed programmatically via the API endpoint: https://api-eu.vonage.com/tfn/v1/registrations See the API Reference for example requests and responses.

The following tables describe the data values you will need when you register a TFN:

Business Information

Name Description Required? Example
Official Entity Name Parent company or organization full name. The actual content provider (end-customer), not an ISV or reseller. Yes Telefonaktiebolaget LM Ericsson
Brand Name (Doing Business As) If applicable, the Brand name ‘Doing Business As (DBA)’ No Vonage Holdings Corp.
Entity Type Select a legal classification for the company/organization Yes Private Profit
Tax Identifier Type For the US, a Federal Tax ID or Employee Identification Number (EIN) is required.

For Canada, the Canada Business Number (CBN) is required.

Sole Proprietorship may apply without an EIN/CBN, but there will be additional checks to validate that the provided information is accurate

For other country-specific registration, select the relevant option or Other.		 Yes EIN
Tax Identifier Number For the US, provide the Employee Identification Number (EIN) for the company/organization

For Canada, provide the Canada Business Number (CBN) for the company/organization

For Sole Proprietorship, you may leave this field blank

For country-specific registration types, provide the relevant Tax ID number.		 Yes 12-3456789
Tax Identifier Issuing Country Select the relevant issuing country Yes US
Registered Address If the Brand name (DBA) is applicable, the address provided should match the brand's registered address. Street number and name. Yes 101 Crawfords Corner Rd
City City name Yes Holmdel
State/Province State or province. For the United States, use 2-character codes, e.g., CA for California. Yes NJ
Zip/Postal Code Zip Code or postal code. For the United States, use a 5-digit ZIP code, e.g., 21012. Yes 07733
Country Two-letter ISO-2 country code, e.g., US. Yes US
Website Link Provide a publicly available website link for the company/organization Yes https://www.vonage.com/
Terms & Conditions Link Provide Terms link for the company/organization No https://www.vonage.com/legal/messaging-service-supplementary-terms/
Privacy Policy Link Provide Privacy Policy link for the company/organization No https://www.vonage.com/legal/privacy-policy/
Contact First Name First name of business contact. Yes John
Contact Last Name Last name of business contact. Yes Smith
Contact Email Email address must match the company, organization or brand (DBA) name if entered Yes john.smith@vonage.com
Contact Phone Number Phone number of business contact. Must be a valid phone number in E.164 format without the + prefix. Yes 12125551212
ISV/Reseller If you are an ISV/Reseller, enter the name of your business No Google LLC.
ISV/Reseller Contact Email Email address of the ISV/Reseller. Vonage will only communicate with this email address for ISV/Reseller submissions No john.doe@google.com

Toll-Free Number Information

Name Description Required? Example
Toll-Free Number(s) for verification Add purchased Toll-Free Number(s) for verification (up to 5) Yes 18001234567
Valid Business Reason If more than one number, must enter a valid business reason for each number to get multiple numbers verified for messaging services Conditionally Yes Two numbers are for two sales regions, one number per region to manage and track the business (East and West)
Estimated Message Volume (per month) Select projected monthly total message volume No 1000
Use Case Category Select a use case category that represents your business industry; choose “Mixed” if marketing and alerts No Mixed
Use Case Description Describe the business reason for the selected use case, and enter any other important information about this request (up to 500 characters) No This Toll-Free Number will be used to deliver opt-in SMS communications, such as one-time passwords (OTPs), alerts, and notifications, to end users who have provided explicit consent.
Campaign Verify Authorization Token Provide the campaign verify token. If you do not have a token, visit Campaign Verify at https://www.campaignverify.org/ to get started.
A valid token follows a specific, pipe-delimited format, comprised of six fields:
cv|1.0|mno|tfree|UUID|SecretString

cv: A constant prefix indicating a Campaign Verify token.
1.0: The token version number (currently 1.0).
mno: The Service ID for Toll-Free numbers (for 10DLC, this would be tcr).
tfree: The Channel ID for Toll-Free.
UUID: A unique identifier specific to your verified committee/brand.
SecretString: A unique, 32-bit URL-safe random string.		 No cv|1.0|mno|tfree|9957c339-d46f-49b7-a399-2e6d5ebac66d|GQ3NMEjED8xSlaAgR
Message Content Provide an example of a message to be sent (up to 1000 characters) No Your confirmation code is: ${code}\n
Age Gated Content Select ‘True’ if your messages include content that is legally restricted to certain age groups over 21 years of age (e.g., alcohol, gambling, adult content).

On your website,
1. Provide the end user's birth date to receive promotional/alert messages.
2. On the bottom, add instructions that "If a user is too young to purchase, then place a hold on sending messages until age-appropriate."

On end user's mobile device,
1. Double Opt-In age gate text message flow includes a Birthdate entry field

2. End user receives opt-in message from an online/mobile site. Example: [Brand Name]: Welcome! Reply with your "birthdate" (MM/DD/YYYY) to successfully sign-up for promotional/alerts messages from _____ (content provider name). Reply STOP to cancel.

3. End user sends message in this format: MM/DD/YYYY

4. If user replies with age of 21+ then add to opt-in list and send opt-in confirmation message. Example: [Brand Name]: Welcome! Msg frequency varies. Msg & data rates may apply. For support, reply HELP for STOP to cancel.		 No False
Opt-In Consent Workflow Select consent method collected from the message recipient No Other
Opt-In Consent Workflow Description Describe the opt-in process where consent is collected from the message recipient No Paper-based opt-in: End-customer consent may be obtained via a paper form. The form requires the end user to enter their mobile phone number and affirmatively select a consent checkbox stating “I agree to receive text messages.” The signed and completed form constitutes valid opt-in documentation.
Opt-In Consent Link Provide shared link to URL or a screenshot; only input publicly accessible URLs, no additional content (i.e. "here's a list"); multiple URLs must be separated by a semi-colon ";" No https://drive.google.com/file/e/1Y8igd356bjkR6Dve_KlKj2HXIikloHCLJq2yu/view
Opt-In Keywords Provide one or more opt-in keywords that trigger an auto-response message to the recipient No JOIN, START, YES
Opt-In Confirmation Message The opt-in message responds to the recipient with your brand name, welcome, use case category and helpful hints.

Note: SMS response message is limited to 160 characters for compliance purposes.		 No Example: [Brand Name]: Welcome! You've signed up for [Use Case Category] messages. Msg freq varies. Msg&data rates may apply. Reply HELP for info, STOP to opt-out.
Help Confirmation Message The HELP keyword confirmation message sent to a user should contain your Brand name and two (2) contact methods, such as a toll-free number, email address or a link to a customer support page.

Note: SMS response message is limited to 160 characters for compliance purposes.		 No Example: [Brand Name]: Thanks for contacting us. Please visit https://www.vonage.com/support or email support@api.vonage.com.
Additional Information Provide any additional information such as description and/or a list of URLs No