For managed service providers and service desks working in HaloPSA: the end user is identified while the phone rings, every call opens a ticket and chats are logged.
Highlights
- User and client identified while the phone rings
- A HaloPSA ticket per call
- Chat and SMS logging
- 3CX AI analysis added to the ticket when enabled
- OAuth 2.0 connection
HaloPSA is a service management platform for managed service providers and internal IT service desks: clients, sites, users, tickets and contracts. On the help desk, the phone is still the channel for urgent requests, and every call should leave a trace in a ticket.
With our native template, the calling user is looked up in HaloPSA by phone number or email. The technician sees which user, and therefore which client, is calling before answering. When the call ends, a ticket is created and attached to that user. 3CX chats and texts are logged too, and when 3CX AI analysis is enabled, the transcript, summary, sentiment and recording link are added to the ticket.
You upload the template to your 3CX and it connects directly to the HaloPSA API. There is nothing else to host.
- Lookup by phone number or email
- HaloPSA search from the 3CX dialler
- A ticket per call
- Chat and SMS logging
- 3CX AI analysis added to the ticket when enabled
Frequently asked questions
Can I create a HaloPSA user from 3CX?
No. The template finds existing users and creates tickets, but it does not create users.
How is the connection authorised?
With OAuth 2.0, directly between your 3CX and HaloPSA, without an intermediary. You need 3CX V20 Pro or AI with CRM integration enabled.
