Genesys Cloud support of toll-free messaging verification for the United States and Canada

For now, registration is managed manually through a form submission. We are presently collecting your company and use case information in a registration form that you need to fill out in its entirety before Genesys can register the TFN on your behalf. Failing to provide all the required information extends the registration lead-time. Registration consists of five main pieces of information:

• Company information – Name, Federal EIN, Address, etc.
• Use case information – Customer service chat, notifications, marketing, etc.
• Opt-In Method – Website, Contract, IVR, Agent/Phone, Keyword, etc.
• Call to Action (CTA) – How your company is obtaining consent to text your customers including evidence of how you are obtaining it.
• The TFN phone number to be associated with each use case.

If you are a charity or political organization, contact GenesysCloudSMS@genesys.com for specific registration requirements.

What is A2P text messaging (SMS)?

The wireless carriers classify A2P text messaging as any business-to-consumer SMS routing to or from software, regardless of the use case. Any SMS sent from or received by Genesys software is classified as A2P.

What is toll-free number verification?

Toll-free number verification means that your use case was reviewed and deemed to be compliant before the TFN is approved for messaging.

When do I need to register?

Any new TFN must be verified before use.

Carriers have issued two deadlines for existing TFNs:

• November 1, 2023 – The final date to submit registration.
• November 8, 2023 – After this date, any TFN programs without registration in progress will be completely blocked until registration is submitted to the carriers.

How long does registration take?

The current lead-time to complete registration is 6-8 weeks. If you have not already done so, submit your registration request as soon as possible.

While your TFN is pending approval numbers have the following limits to send outbound messages:

• Daily limit: 2,000 message segments^*
• Weekly limit: 6,000 message segments^*
• Monthly limit: 10,000 message segments^*

* SMS exceeding the supported character limit (160 for GSM, 70 for Unicode) are split into segments for delivery. Each SMS segment counts separately against your outbound limits. For example, a 180-character GSM message is split into 2 segments for delivery, each its own message. In this example, 2 messages are counted against your outbound limits.

What happens if I don’t register?

If you don’t register your program, your TFNs will be blocked.

If you no longer want to use your TFNs due to this registration requirement, release them from Genesys Cloud in the SMS inventory and you will not incur further charges.

Does every program need to be registered?

Yes. Regardless of how you use TFNs (for high volume campaigns, inbound customer service, low-volume testing, 2FA/OTP, and so on), your company and use case must be registered to avoid being blocked. For more information, see SMS best practices for a compliant program.

Is Opt-in required for all programs?

Yes. In the eyes of the FCC, CTIA, and wireless carriers, obtaining consent is not optional, even for inbound-initiated programs. Wherever you advertise that your customer can use text as a communication channel or sign up for a recurring message program, the expectations must be clearly defined for why they are providing their mobile number.

Do these changes only apply to SMS or is MMS affected too?

These changes apply to both SMS and MMS. Throughput limits and surcharges for MMS vary by use case.

Do these changes apply to 10DLC as well?

Yes and no. There is a similar registration requirement for A2P messaging using US/CA 10DLC; however, there are more complexities behind throughput limits. For more information, see Genesys Cloud support of 10DLC (10-Digit Long Code).

Is voice on TFNs impacted by this change?

No. Voice calling is not impacted.