The main differences between native and alternate SLA metrics are how they handle active tickets and tickets saved in the wrong status. Alternate metrics do not count active tickets, ensuring that only fulfilled tickets are considered.
Additionally, if tickets are saved in the wrong status, alternate metrics will still return accurate results. This makes them particularly useful in cases where the native metrics might misrepresent the status of tickets due to schedule changes or other issues.
Creating alternate SLA metrics in Zendesk Explore involves using durations instead of status to determine when tickets are Achieved or Breached. This is particularly useful in rare cases where SLAs have accurate metric data but are saved in the…
To create alternate SLA metrics in Zendesk Explore, you'll need a few things. First, ensure you have Zendesk Explore Professional or Enterprise, as well as Editor or Admin permissions. You'll also need SLA data in Zendesk Support. The process is…
To create a calculated metric for SLA breach time in Zendesk Explore, start by opening the report builder and selecting the Support - SLAs dataset. Then, open the Calculations menu and click on Standard calculated metric. Name the new metric…
Once you've created the calculated attribute, you can use it to create alternate SLA metrics by replacing the native SLA target status attribute. This allows you to count achieved and breached tickets and calculate a percentage achievement metric….
Unfortunately, Zendesk Explore does not support real-time monitoring of active SLAs. Explore captures SLA durations only after the target has been fulfilled, as it syncs data at periodic intervals rather than providing a live feed. For real-time…