Register a toll free use case
This article lists the information required to register a toll free use case.
Registration steps
Fill out the information below in the TF SMS Verification Template and email it to lnp@avaya.cx. For more information about toll free messaging, see Overview: Toll free messaging.
Item
Description
Business Name
The official, legal name of your business.
Corporate Website
A URL directing to your business' website.
First Name
First name of an authorized representative for your business.
Last Name
Last name of an authorized representative for your business.
Email address of an authorized representative for your business.
Contact Phone Number
Contact number of an authorized representative for your business.
Address Line 1,
Address Line 2,
City,
State / Province / Region
ZIP / Postal Code
The official, legal address of your business.
Number(s)
Provide the number(s) that will be used for the campaign.
Note: You can have up to 5 numbers per campaign, however you will need to describe the business use case for having more than one sending number
Volume per month
1,000
10,000
100,000
250,000
500,000
750,000
1 Mil
5 Mil
10 Mil +
Use Case
2FA
Account Notification
Customer Care
Delivery Notification
Fraud Alert Messaging
Higher Education
Low Volume Mixed
Marketing
Mixed
Polling and Voting
Public Service Announcements
Summarize Use Case
Please describe your use case and the purpose of your messages (i.e. appointment reminders, receipts, etc.)
Messaging Content
160 characters max. What is the message a customer will receive when messaging into this number?
Opt-In Workflow
A step by step description of how the end user opts in.
Will the TFN be used solely for Customer Support and published as a means for customers to contact them?
Will the business ever outbound message customers?
Opt-In Workflow Image URL
Where can we find the Opt-In process?
Where is the number published?
How does the customer know to text in?
Additional Use Case Details
This is a good place to address multiple numbers on one request.
Anything else to add about the use case or how the customer will use messaging?