HaloPSA Integration
Connect it to HaloPSA and it starts working tickets as they come in. The easy ones get closed. If something still needs a person, the research is already on the ticket.
What you get
It closes the ticket in HaloPSA
A ticket comes in, Rallied figures out what's wrong, and does the work. Password and MFA resets finish once the requester is checked, on the clients you pick, and it writes what happened as a note.
The next person already knows what happened
If you hand a ticket off, they already have a note covering what happened so far. They can see what Rallied found, what it tried, and the plan, so they're not starting from scratch.
They approve it on the ticket
When something needs a sign-off, it shows up as a HaloPSA action on the ticket. Only the assigned agent can approve or deny it, so nobody has to leave HaloPSA.
You pick which clients it works
Pick which HaloPSA clients the agents handle, and set per tool what runs by itself and what stops for a technician. Plan mode lets you read what it would do before you switch it to Execute.
What it handles
- Triages the subject, requester, priority, and prior notes before it acts
- Keeps diagnosing and resolving as new notes land on the ticket
- Internal notes and customer replies, each labelled with its source
- Approvals raised as HaloPSA actions on the ticket
- Plan mode first, Execute mode once you have read it
- Resolves password and MFA resets, once the requester is verified
- Only the HaloPSA clients you pick, starting with one
- Answers inbound calls, matches the caller, and opens a ticket