Telephony Best Practices
Recommended practices drawn from across the Telephony guides, covering how to connect 3CX, set up agents and queues, handle calls and review them afterward. Each section below matches its own detailed guide.
Overview
Telephony is easiest to roll out in a fixed order. See Telephony Overview.
- Connect 3CX first, then users, then everything else. Statuses, queues, call records and click to call all depend on the connection and on synced extensions.
- Plan versions and licences before the project starts. The prerequisites list the 3CX and UNICONNECT AI versions required and the connectivity the two systems need.
Getting Started
A first call confirms the whole chain. See Telephony Getting Started.
- Start the shift before testing any call. Call icons stay greyed out until the agent has an active shift in a status that allows External Calls.
- Test with one agent and one number first. One working call proves the plugin, the sync and the status setup before the rest of the team is added.
3CX Plugin Configuration
The plugin is the link to the PBX. See 3CX Plugin Configuration.
- Create the API key with the access the guide lists. A key without the required access lets the plugin save but leaves features such as sync or call control unavailable.
- Keep the Data Sync Interval reasonable. A short interval keeps extensions current, and a very short one adds load for little benefit.
- Decide on Self Registration and Historical Data Import before saving. Both change how users arrive and what history is loaded, so choose them deliberately.
3CX User Sync
Synced extensions become platform users. See 3CX User Sync.
- Watch the seat counter before syncing. The 3CX Users screen shows seats used and seats left. A sync cannot add more users than the licence allows.
- Check each user's extension and role after a sync. The Users screen shows extension, role and registration status for each person.
Status Management with 3CX
Statuses decide what an agent can do. See Status Management with 3CX.
- Give each status a clear purpose. Available allows External Calls and keeps the agent logged into queues. Break statuses log the agent out of queues.
- Leave call statuses to the platform. Dialing, Ringing, Talking and On Hold are applied automatically as a call progresses.
Group Management with 3CX Queues and Ring Groups
Groups decide where inbound calls go. See Group Management with 3CX Queues and Ring Groups.
- Use a queue when callers should wait, and a ring group when everyone should ring. A queue distributes calls one by one. A ring group rings all members at once.
- Keep membership current. An agent who has left a team should be removed from the group, or calls will ring a person who is not there.
Number Handling with AI Agent
An AI Agent can answer a number instead of a person. See Number Handling with AI Agent.
- Define a transfer path to a person. Callers who need a human should reach one without repeating themselves.
- Start with one number. Route a single low risk number to the AI Agent and review its calls before adding more.
Call Module Configuration
The call record is a module like any other. See Call Module, Call Module Relationship and Call Module Layout Configuration.
- Leave the built in call fields as they are. Reports and workflows read them, so add new fields instead of changing existing ones.
- Use the Lead and Group relationships when reporting. They tie a call to a campaign lead and to the queue that handled it.
IVR
An IVR template lets a campaign call be handled by a menu. See IVR.
- Build and test the menu on the 3CX server first. UNICONNECT AI only lists existing menus, so a menu that is not ready cannot be chosen.
- Start with a small number of concurrent calls. Raise it once the menu has handled a few real calls correctly.
Calling from CRM
Any phone field can be dialed. See Calling from CRM and Call Options for CRM Module Leads.
- Confirm the number before pressing Call. The Confirm Call dialog is the last chance to stop a call to the wrong number.
- Set up outbound rules in 3CX. They decide how every dialed number is routed.
Call Records
Every call is stored. See Call Records.
- Filter before you scroll. Use Call Status, a date range or a Call ID instead of paging through thousands of rows.
- Open the Call Path when a call went somewhere unexpected. It shows each leg, who it rang and for how long.
Call Dispositions
Dispositions record outcomes. See Call Dispositions.
- Keep the list of outcomes short. Five to eight values are easier to report on than twenty overlapping ones.
- Record a follow up when one is promised. Use Follow Up Date and the assignee so the promise appears on someone's list.
Live Call Controls
Supervisors can step into a call. See Live Call Controls.
- Escalate gently. Listen first, whisper if coaching helps, and barge in only when the call has to be taken over.
- Tell agents that monitoring is part of the job. It sets expectations and avoids surprises.
System Workflows
Ready made workflows react to call events. See System Workflows Telephony.
- Add your own workflow instead of editing a System one. System workflows keep status and lead data in step for every user.
- Check the History tab after a change. It shows whether the workflow ran.
Reports and Dashboards
One dashboard and six reports cover Telephony. See Telephony Reports and Dashboards.
- Use the dashboard for the moment and the reports for the day after. Inbound Live & Queue Monitor shows what is happening now. Call Distribution and Abandoned Calls show how a period went.
- Click Generate Report on gated reports. Their date range is already filled in, so the report appears straight away.
Permissions
Twelve permissions decide who can do what. See Telephony Permissions.
- Give agents calling and nothing more. The built in User role grants Make Outbound Calls and Ring My Mobile only.
- Grant supervision permissions to supervisors only. Recordings, monitoring, barge in and Force Transfer each affect real customer calls.