How to buy a toll free number inside Adaptive AI?

Overview

Understanding how to buy a toll-free number can be critical for your business operations. This guide

provides a straightforward walkthrough on purchasing a toll-free number for your subaccounts. Equip yourself with this knowledge to enhance your customer communications strategy.

How to Buy a Toll-Free Number?

Step 1. Head into your Location/ subaccount where you would like to

purchase a Toll-Free number:

Step 2. Click on Settings at the bottom left:

Step 3. Click on Phone Numbers:

Step 4. Click on Add Number:

Step 5. Country set to United States > Click on Filter:

Step 6. De-select Local & Mobile for the Phone Number Type:

Step 7. Select one of the phone numbers you like and click on Proceed to

Buy! Toll-free numbers are numbers that begin with one of the following three-digit codes: 800, 888, 877, 866, 855, 844 or 833

FAQs

1. 1What is the benefit of Toll-Free Numbers over Local/Phone numbers? Though Toll-Free numbers are high priced they have added advantages to it, please see below:
2. 2How can one register their US/Canada Toll-Free numbers?

If the sub-account is on the Adaptive AI Phone, you can sign up for Toll-Free Number Registration for Adaptive AI - Phone (US/Canada) from the application. [Only applicable to US/Canada Toll-Free Numbers] If the sub-account is using your/their own Adaptive AI Phone account, you will need to contact Adaptive AI Phone support to register your toll-free number. If the sub-account is on the Adaptive AI Phone, you can sign up for Toll-Free Number Registration for Adaptive AI - Phone (US/Canada) from the application. [Only applicable to US/Canada Toll-Free Numbers]

If the sub-account is using your/their own Adaptive AI Phone account, you will need to contact Adaptive AI Phone support to register your toll-free number.

Before you begin

“How to buy a toll free number inside Adaptive AI?” is part of the Conversations → Phone & Voicemail area in Adaptive AI. Configure calling, routing, voicemail, recordings, and phone-number behavior. Conversation, phone, SMS, chat, and messaging changes affect customer contact and consent. Test routing in both directions and confirm that messages land on the correct record and owner. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the phone number, inbox, social account, personal inbox, or chat channel is connected and assigned to the intended business.
• Verify user permissions, routing rules, forwarding destinations, business hours, voicemail behavior, and notification settings.
• Use an internal test contact with permission to receive the chosen channel and with do-not-disturb status set appropriately.
• Prepare the exact test message or call scenario, including the expected owner, reply, disposition, and follow-up action.
• Review registration, template, consent, opt-out, and service-window requirements before testing SMS or regulated messaging channels.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Initiate the test from the same direction a customer would use and confirm it appears in the correct conversation thread.
2. 2Verify assignment, notifications, sender identity, timestamps, contact matching, and message or call status.
3. 3Reply through Adaptive AI and confirm the recipient receives the response once from the expected number or account.
4. 4Test after-hours, missed-call, voicemail, forwarding, or automated follow-up behavior when those rules are part of the setup.
5. 5Confirm opt-out or do-not-disturb behavior stops restricted communication without blocking unrelated permitted channels.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Check channel connection status, number assignment, user availability, and routing rules before changing message content.
• Compare the contact's normalized phone number or email address when activity appears in a duplicate or unexpected thread.
• Review delivery, call, forwarding, or conversation logs for the first failed handoff and its provider response.
• Confirm business hours, quiet hours, service windows, approved templates, and opt-out status when a send is blocked or delayed.
• Test without overlapping workflows to determine whether duplicate replies come from routing, automation, or a second connected channel.

Best practices

• Use clear ownership and escalation rules so every inbound conversation has one accountable responder.
• Keep automated replies transparent, concise, and able to hand the conversation to a person when the request falls outside scope.
• Honor channel consent and opt-outs immediately and preserve the conversation history needed for support or compliance review.
• Use internal test records for routing changes and avoid sending experimental messages to active customers.
• Review missed, failed, unassigned, and long-waiting conversations as an operating metric, not only when a customer complains.