Keep 3CX as the system of record
Extensions, users, queues, ring groups, business-hours rules and reporting stay in 3CX. VoxLink only receives the calls a 3CX rule sends it.
3CX + VOXLINK
Add AI Voice Agents to Your 3CX Phone System
You already run 3CX for extensions, queues, ring groups and business-hours routing. VoxLink is added beside it, not instead of it.
The calls that get missed are rarely the ones your team is sitting waiting for: they arrive while everyone is already on a call, during lunch, on site, or ten minutes after close.
Where the deployment supports it, selected 3CX call paths - after hours, overflow from a busy queue, or a dedicated service route - can be sent to a VoxLink AI agent that answers, qualifies, books and transfers back.
Your 3CX users, extensions, numbers and existing call flows stay exactly where they are. Nothing is replaced, and the supported connection method is confirmed for your environment first.
Answer calls, book appointments, qualify leads, handle enquiries and connect customers with your team - 24/7.
Connection
3CX + VoxLink
- Connection type
- SIP
- Routing
- Selected call flows
- Direction
- Inbound + outbound
- Validation
- Tested before go-live
Keep your phone system. Keep your numbers. Add AI to the conversations you choose.
Why add AI
Why Add AI to 3CX?
3CX is good at deciding where a call should go. What it cannot do is have the conversation when nobody picks up. Voicemail collects the call; it does not qualify the caller, answer the question or put an appointment in the calendar.
VoxLink sits at the end of a 3CX routing decision you already control. You choose which destinations point at the AI - typically an after-hours destination, a queue overflow or no-answer path, or a dedicated inbound route for sales or service - and everything else continues to ring your 3CX users exactly as it does today.
Start with one route, not a migration
Most 3CX deployments start with a single destination pointed at the AI - after hours is the usual first step - then widen once the behaviour is proven.
Deployment-specific by design
3CX environments differ by version, hosting model and permitted SIP architecture, so the connection method is confirmed for your instance rather than assumed.
What VoxLink adds
What You Can Automate With 3CX
After-hours answering
Give your out-of-hours 3CX destination a real conversation instead of a voicemail prompt.
Queue overflow
Where a 3CX queue is configured to overflow, that path can reach AI instead of ringing out.
Booking and rescheduling
Callers can book, move or confirm an appointment during the call rather than waiting for a callback.
Sales qualification
A dedicated 3CX inbound route can qualify new enquiries before a person is involved.
Transfer back into 3CX
Where transfer routing is configured and tested, callers can be handed to the right 3CX destination.
Selected outbound workflows
Reminders and approved follow-ups where the outbound route, permissions and caller ID allow it.
In practice
Example Call Flow
This is what an after-hours 3CX route looks like to the customer. No configuration details are shown - only the journey.
- 01
A customer dials your existing business number.
- 02
3CX receives the call and applies your normal routing rules.
- 03
Outside business hours, the configured 3CX destination sends the call to VoxLink.
- 04
The AI answers, understands the reason for the call and books or captures what is needed.
- 05
The call completes, or transfers back to a 3CX destination where that path is configured.
CallerHi, is anyone there? I need someone out to look at a hot water system.
VoxLink AIThe office is closed right now, but I can book you in. Is this for a home or a business address?
CallerHome. Tomorrow morning if possible.
VoxLink AII have a slot between 8 and 10am tomorrow. I'll put your name and number against it and the team will confirm first thing.
Outcome: booking captured overnight, details waiting for the team before the 3CX phones open.
Positioning
Keep Your 3CX. Add AI.
Use VoxLink alongside a compatible 3CX environment so selected conversations can be handled by AI while 3CX continues to manage the broader business phone system.
Pricing is the same whether calls arrive from 3CX or anywhere else - plans are based on your VoxLink usage, not on the phone system you already own.
See VoxLink pricing and plans →Your 3CX extensions, users, desk phones and softphone apps.
Your existing numbers and carrier or SIP trunk arrangements, where routing permits.
Your queues, ring groups, business-hours rules and internal call flows.
Control over exactly which 3CX destinations reach the AI and which stay with your team.
Use cases
3CX Use Cases
Where compatible 3CX deployments typically start.
- Route selected after-hours calls from a 3CX out-of-hours destination to AI.
- Send queue or no-answer overflow to AI where the 3CX queue is configured for it.
- Let AI qualify a caller first, then transfer back to a 3CX user or ring group.
- Point a dedicated sales or service inbound route at AI while everything else rings as normal.
- Handle repeat FAQ calls from your configured knowledge base instead of tying up an extension.
- Run selected outbound reminder or follow-up workflows where 3CX routing and permissions support it.
Technical model
How the Connection Works
VoxLink uses SIP connectivity. For a 3CX deployment, confirm the supported registration/trunk architecture for that environment, configure matching SIP authentication and routing, then send selected calls to the VoxLink AI Agent.
Existing Number
3CX
SIP Connection
VoxLink AI Agent
Customer / Team
The supported connection method is deployment-specific. We confirm the version, hosting model and permitted SIP architecture for your environment before configuring anything.
Requirements
What You'll Need
A short list for whoever administers your 3CX system. We never publish or display server addresses, registration names or passwords.
- Administrative access to your 3CX management console.
- Your 3CX version and hosting model, so the permitted SIP connection method can be confirmed.
- The ability to create or configure a dedicated SIP account or trunk connection for VoxLink.
- Agreement on which inbound routes, queues or after-hours destinations should reach the AI.
- Appropriate network, firewall and NAT configuration for SIP signalling and audio.
- A VoxLink account and an authorised phone-system administrator available for the test call session.
Setup
Connecting 3CX
Our team works through this with you. No configuration details, credentials or server addresses are ever published.
- 1
Confirm the customer's 3CX version, hosting model and permitted SIP connection method.
- 2
Create or configure the appropriate dedicated SIP account or trunk connection.
- 3
Enter the matching server and authentication details in the VoxLink SIP connection.
- 4
Route selected inbound calls from 3CX to VoxLink.
- 5
Configure outbound routing and caller ID where required.
- 6
Test inbound, outbound, audio, transfer, DTMF and failover before go-live.
Before go-live
Every Connection Is Tested First
Compatibility and call quality are confirmed on your environment before customers reach the AI.
- SIP registration or trunk connectivity
- Inbound and outbound audio in both directions
- DTMF handling
- Transfers back to your team
- Caller ID presentation
- Firewall and NAT behaviour
- Failover when the AI path is unavailable
Use it with
What to Set Up After Connecting 3CX
Other phone systems
Connect a Different System
Not sure what you have?
Send us your phone system details and we'll confirm whether a supported SIP connection is available.
Request a compatibility check →FAQ
3CX Questions
Your 3CX Phone System. Now Ready for AI.
Add VoxLink to your compatible 3CX environment and start automating the conversations that matter most.