- Home
- Integrations
- HaloPSA
3CX + HaloPSA
3CX and HaloPSA, built by people who use both all day
Our own help desk runs on HaloPSA and 3CX, so this integration is the one we would build for ourselves — because it is. A caller is matched to their client and user record, their open tickets pop, the call is logged as an action, and technicians dial from the ticket instead of a handset.
- Caller matched to Halo client and user
- Open tickets pop as the call rings
- Calls logged as ticket actions
- Click-to-dial from any Halo record
What it does
3CX and HaloPSA, call by call
Client and user lookup
The calling number is matched against Halo users and client contacts and shown on every 3CX device — the tech sees "Acme — Sarah" before answering.
Ticket pop
The caller's open tickets open in the browser as the call rings, so the conversation picks up where the last one stopped.
Logged as actions
Each call becomes an action on the ticket you choose — or a new ticket if there is none — with direction and duration. Time can be tracked against it.
Click-to-dial
Numbers on tickets, users and clients become dial links through the browser extension.
Queue awareness
Support queue calls can be tagged so Halo reporting separates phone-raised tickets from email and portal.
Built for MSPs
We are an MSP. The edge cases — shared numbers across a client's sites, after-hours on-call, tickets raised from missed calls — are the ones we hit first.
For MSPs and internal IT teams
If you run a service desk on HaloPSA — as an MSP or an internal team — this is the difference between "who is this and what did they ring about last time?" and answering with the ticket open. We use it in our own Adelaide help desk every day, which is the best support arrangement an integration can have.
Setup
An API application in Halo with least-privilege permissions, mapped to your 3CX users. We agree the logging rules — which queues log, whether missed calls raise tickets, how to handle unknown numbers — then roll out per technician.
How it is set up
Four steps, usually inside a day
You keep the keys. We do the mapping, the rollout and the looking-after.
API application
Created in HaloPSA with only the permissions the integration needs.
Rules
Which queues log, what missed calls do, how unknown callers are handled.
Roll out
Browser extension and a short session per technician.
Support
We run this integration ourselves; when Halo changes, we notice before you do.
Common questions about the HaloPSA integration
Does it work with HaloITSM and HaloCRM?
The Halo platform is shared, so the integration approach is the same. Tell us which product you run and we will confirm the specifics.
Can a missed call raise a ticket automatically?
Yes. A missed call on a support queue can raise a ticket assigned to the queue so it is worked like any other request.
Still have questions? Talk to a local specialist — no call centre, no scripts. Contact us
HubSpot
Caller ID from HubSpot contacts, calls logged as HubSpot call activities, click-to-dial — without paying for HubSpot calling minutes.
3CX + HubSpotSalesforce
Leads, contacts and accounts looked up as calls ring, calls logged as Salesforce tasks, click-to-dial from Lightning.
3CX + SalesforceZoho CRM
Contacts and leads matched from Zoho CRM, calls logged to the Calls module, click-to-dial — including Zoho One and Bigin.
3CX + Zoho CRMGet a quote
Ready to connect HaloPSA to 3CX?
Tell us which edition you run and what should happen when the phone rings. We will confirm whether it is a template, middleware or custom work, and quote it.
Prefer to talk?
1300 718 857Monday to Friday, 8:30am – 5:30pm ACST. 24/7 support for managed customers. Existing customer with a fault? Go to support.
- Written, itemised quote within one business day
- No obligation — we will say if you should stay put
- Titanium 3CX Partner, one of six in Australia