Creating a custom metric for CSAT in the 'Ticket Updates' dataset involves replicating existing metrics with adjustments.
Start by recreating the '% Satisfaction Score' metric from the 'Tickets' dataset. Use the formula: COUNT(Good satisfaction tickets)/COUNT(Rated satisfaction tickets). Define 'Good satisfaction tickets' and 'Rated satisfaction tickets' using pre-built metrics like 'Good initial satisfaction ratings'. This approach allows you to leverage the 'Update' time attribute in 'Ticket Updates', providing a more accurate reflection of CSAT events.
Creating a report on customer satisfaction by agent in Zendesk Explore is straightforward with the right permissions and data. To start, ensure you have Zendesk Explore Professional or Enterprise and the necessary Editor or Admin permissions. Begin…
To create a customer satisfaction report in Zendesk Explore, you need specific permissions and access. You'll require Zendesk Explore Professional or Enterprise, along with Editor or Admin permissions. These permissions allow you to access the…
Enhancing your customer satisfaction report in Zendesk Explore can provide deeper insights and more tailored data. You can add filters such as 'Ticket solved - Date' to focus on specific time periods. Use top/bottom filters to highlight…
CSAT reporting can be volatile when using the 'Ticket solved - Date' attribute due to retrospective changes in data. If a ticket is initially solved and rated poorly in one month, but the conversation continues and the ticket is resolved in the…
Currently, Zendesk Explore does not have a native attribute for the date a CSAT rating was given. The closest available attribute is 'Time - Ticket solved', as surveys are sent upon ticket resolution. However, this can lead to issues if the…