How to Assign Adaptive AI Phone Numbers to Users

Overview

This guide outlines methods for assigning a dedicated Adaptive AI number to an individual user in your system. The process ensures that all inbound calls to that number are routed specifically to the user.

Steps to Assign an Adaptive AI Number to a User

Method 1

Step 1: Purchase & Add the Number After purchasing an Adaptive AI Phone

• Go to Location Settings > Phone Numbers.
• Click on "Add Number" to add the new number to the system.

Step 2: Assign the Number to a User

• Navigate to My Staff.
• Edit the specific user profile who needs the number.

Step 3: Configure Call Settings

• Expand the Call & Voicemail Settings section.
• Use the Inbound Number dropdown to select the Adaptive AI number you just added. Important Note: Only one Adaptive AI number can be assigned to one user. Once assigned, all incoming calls to that Adaptive AI number will go to the designated user.

Method 2

You can go directly to the Phone Numbers section and select the user under the ' Ring All ' category to route contact calls to them

Method 3

You can assign a user directly from the contac t record by going to the contact, selecting ' Unassigned User,' and choosing the appropriate user.

Frequently Asked Questions

Q)Can I assign multiple Adaptive AI numbers to one user? A)No, only one Adaptive AI number can be assigned to a user at a time for direct routing.

Q) How many users can share one Adaptive AI number? A)Only one user can be assigned to an Adaptive AI number at any given time. Once assigned, all calls to that number will be directed solely to that user.

Before you begin

“How to Assign Adaptive AI Phone Numbers to Users” 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.