Skip to main content

How to Configure the Telephony Use Case in UNICONNECT AI

note

This page is the technical companion to Telephony Use Case Scenario. It assumes the prerequisites in Telephony Getting Started are met. The steps run in the order a person follows them, and each part names the requirement from the scenario that it meets.

Part 1: Connect the Phone System​

Requirement: one phone system and one CRM

Everything else depends on the 3CX connection. The full steps and the field reference are in 3CX Plugin Configuration.

  1. Create the API key on the 3CX server. Give it the access the guide lists.
  2. Open Configuration → System → Plugins and choose 3CX.
  3. Enter the Host, Client Id and Api Key. Set the Data Sync Interval and decide on Enable 3CX Login, Self Registration and Historical Data Import.
  4. Turn the plugin on and click Save Configuration.

Part 2: Sync the Agents​

Requirement: one phone system and one CRM

Each agent needs a synced extension. See 3CX User Sync.

  1. Open Configuration → User Management → 3CX. Check Seats Used before syncing.
  2. Click Sync. Marcus Webb's extension, 1018, appears as a user.
  3. Open Users and check each person's extension, role and status. Use Activate where a user is not yet active.

Part 3: Set Up Statuses​

Requirement: agents who are ready

Presence statuses control who receives calls. See Status Management with 3CX.

  1. Open Configuration → Status Management.
  2. Check that Available allows External Calls and keeps the agent logged into queues.
  3. Check that break statuses log the agent out of queues.

Statuses page with Available selected, showing its General and Call Handling tabs, and Away and Out Of Office listed as queue logged out

Figure 1. The Statuses page. Available keeps the agent logged into queues, and Away takes them out.

Part 4: Build the Queues and Hand Off After Hours​

Requirement: the right team for the right call

See Group Management with 3CX Queues and Ring Groups and Number Handling with AI Agent.

  1. Open Configuration → User Management → Groups.
  2. Open the Loan Servicing queue and check its members. Add or remove agents so it matches the team.
  3. Open the Collections ring group and add the collections agents.
  4. For after hours, create an AI Agent and assign it to the number. Define where it transfers callers who need a person.

Groups page listing queues and ring groups, with a queue open showing its type, extension number, status and selected users

Figure 2. The Groups page, with a queue open and its members listed.

Part 5: Put the Customer on Screen​

Requirement: the customer on screen

The Inbound Call Popup workflow opens a page for the user receiving the call. See System Workflows Telephony.

  1. Open Configuration → Automation.
  2. Open Inbound Call Popup and read its Designer, History and Details.
  3. Adjust the page it opens only if the team wants a different record. Save the change, and check History after the next call.

Automations page showing system workflow cards for inbound calls, call segments and call ended

Figure 3. The Automations page, where the Inbound Call Popup and call event workflows live.

Part 6: Record Outcomes​

Requirement: a record of every call, and an outcome for every conversation

Calls are stored automatically. Outcomes come from the Disposition module. See Call Records and Call Dispositions.

  1. Open Configuration → CRM → Disposition → Fields. Check Call Type, Disposition, Message, Follow Up Date and Assign Follow Up To.
  2. Open Dependencies and set which dispositions belong to inbound calls.
  3. Ask agents to record an outcome after each call. Marcus chooses the outcome, adds a note and sets a follow up when a payment is promised.

Part 7: Set Who Can Do What​

Requirement: help for new agents, and clear limits

See Telephony Permissions and Live Call Controls.

  1. Open Configuration → User Management → Roles.
  2. Keep the built in User role for agents. It allows Make Outbound Calls and leaves supervision permissions off.
  3. Create or edit a supervisor role. Set Access Call Logs, Listen Call Recordings, Silent Monitoring, Call Whisper and Call Barge-In to the scope the supervisors need. Add Force Transfer only where it is required.
  4. Assign the roles to the users.

Edit Role panel with the Telephony group expanded, listing call, recording, monitoring and transfer permissions

Figure 4. The Telephony permissions of a role, where supervisor access is set.

Part 8: Read the Reports​

Requirement: visibility without chasing

Open Dashboards for the Inbound Live & Queue Monitor and Reports for the six Telephony reports. They are described in Telephony Reports and Dashboards.

warning

Abandoned Calls, Queue Statistics, Activity Summary, Activity Report and Login History show a Filters card first. Click Generate Report to see the data.