Cannon VoIP Help

Connect HaloPSA

What connecting HaloPSA does, from caller names to calls logged back, and how to get its details and connect it.

Updated 1 week ago

HaloPSA is a PSA and service desk for IT providers. This article explains what connecting it does and how to connect it.

What it does

Your HaloPSA contacts are copied into your company contacts, so a caller HaloPSA knows shows by name on every desk phone and app before anyone picks up, and in your call history afterwards.

With call logging on, every finished call is filed in HaloPSA on the matching record: who took it, how long it lasted, missed calls and voicemails, and the call summary. You can log texts too (one note per conversation once it goes quiet for half an hour), and add a link to the call in the portal. When HaloPSA doesn't know the caller, you choose to skip the call.

Contacts sync every 6 hours (HaloPSA can only send everything at once), with a full sync each day that also removes contacts deleted there. Sync now on Contacts brings changes in straight away.

Before you start

  • Plan: any HaloPSA plan with API access.
  • On our side: a company administrator connects it, once, for the whole company.

Get your details from HaloPSA

  1. In Halo, go to Configuration > Integrations > Halo API > View Applications > New.
  2. Name it Cannon VoIP, tick Active, and set the authentication method to Client ID and Secret (Services).
  3. Choose an agent for it to log in as (or Application identity).
  4. On the Permissions tab, allow reading and editing customers (users) and tickets.
  5. Copy the Client ID and Client Secret, then save. The secret isn't shown again.

Connect it

  1. In the portal, go to Contacts and click Connect a CRM (or Connect another CRM). You can also start from Company > Integrations.
  2. Choose HaloPSA and fill in:
  3. - Halo address (https://company.halopsa.com): your Halo address - Client id: step 5 - Client secret: step 5 - Ticket type id for logged calls (optional) (optional): the id of a "Phone call" ticket type you make for this (Configuration > Tickets > Ticket Types) - Tenant name (hosted Halo only, optional) (optional): on the Halo API page, for Halo-hosted accounts

  4. Click Connect & sync. The first sync runs straight away and says how many contacts came across.
  5. To file calls in HaloPSA, tick Log finished calls into HaloPSA on the connection, and choose what happens when HaloPSA doesn't know the caller.

If it says Needs attention

The connection's card on Company > Integrations shows the last error. The usual causes:

  • The key was reset, expired or deleted in HaloPSA: make a new one and connect again with it.
  • The person who made the key lost access or left: make the key as someone who is staying.
  • Calls are logged as tickets. A ticket type that closes on its own keeps them out of your team's queues.

Press Sync now on the connection to try again straight away. To stop, press Disconnect: contacts already copied stay in your contacts, and calls already logged stay in HaloPSA.

Was this helpful?
← All help articles