I'm aware of this idea existing and its status, but would like to refocus the discussion as the original idea's OP doesn't provide a lot of context.
Short description of the problem: Hubspot Service Hub needs more SLA metrics to make it a viable solution for professional customer support teams.
I've recently been running a project migrating from Zendesk to Hubspot Service Hub, where SLA metrics were a huge topic.
Despite the migration solving a lot of other issues, this remains a part where the client is hamstringed to this day: the lack of SLA metrics like Next Reply Time, Agent Work Time, Requester Wait time and Time until next breach (based on which other SLA metrics will breach first). Zendesk has these SLA metrics nailed quite well, and this article neatly visualizes what each of those metrics does.
Why do they need these metrics?
They're not just used for reporting. The Next Reply Time metric is the core metric used to prioritize which tickets agents need to work on throughout the day. They sort their tickets based on which ticket will first breach this NRT or the AWT. So we've done our best to recreate them in Hubspot. I've used Operations Hub to, what feels like, bend time and space itself to build a workflow that calculates the Next Reply Time, but instead of a duration, I have it as a Due Date. It's workable but not ideal.
Why should Hubspot prioritize this?
This project was for a Support team that were real power users of their support software, with well thought-out processes that they were constantly revising and optimizing. In short, they're the kind of team I think Hubspot would see as an ideal user of Service Hub. That they see the lacking of these metrics as a big problem should be a clear sign that this needs a solution to make Service Hub a viable competitor of the likes of Zendesk.
Aren't there any workarounds?
Trying to get a near-realtime AWT has me doing more complex wizardry. I get close, but I cannot get this calculated near-real time. I think the core of the issue is that Hubspot doesn't keep a running timer, to show the difference between a datetime property and 'now'. Even if these SLA metrics weren't supported natively, if it could somehow do that, I could probably build them through Ops Hub.
... Exibir mais