half our queue is stuff a tech closes in 2 minutes but it still sits for an hour waiting to get picked up. password resets, adding someone to a teams channel, that kind of thing. i’ve looked at halo’s automation rules but they seem better at routing than actually fixing anything. anyone found a setup that closes these without a human?
Hi all,
We are currently in the process of migrating to HaloPSA from CW Manage, and were hoping to get the following processes up and running before we go live. I am hoping someone else has solved this because I'm starting to go around in circles.
When a ticket is placed on hold and we're waiting for the customer to respond, we want Halo to:
Our issue is that the reminder emails are being sent outside of business hours, sometimes late at night.
Originally, we had this configured using the Ticket Status automation ("when ticket has been in this status for X time, send email"). This worked reliably but ignored working hours.
Research suggested moving the process to an SLA Hold workflow instead, as SLA timers should respect working hours. However, I can't get it to work at all using this method.
We also have a confirmation workflow where, when a ticket is marked Resolved, the end user receives an email asking whether the issue is fixed.
They can:
This part works fine.
The issue is that if the user doesn't respond, the ticket should automatically close after 8 working hours and send the CSAT request. Instead, it appears to close 8 hours after the ticket was resolved, regardless of business hours.
For example:
Not ideal.
Has anyone got either of these processes working in Halo while properly respecting working hours/business hours?
If so, what approach are you using? Ticket Status timers, SLA Holds, Scheduled Actions, Workflows, something else?
Thanks in advance.