Building Insights reports with Survey data

One thing to note about the reports shown in the video above is that the results are sliced by when the ticket was solved (this is the 'HOW' part of the report builder). While this is the simplest way to build an NPS report over in Inisghts, these reports will not exactly match the NPS reports available in-app because the in-app reports are sliced by the precise date the survey was last updated by the customer. Since the ticket solved date and the survey response date won't always match it means that results can pop up in different periods (quarter/month/week depending on what you're using).

But, it is also possible to slice the data in Insights by the moment the survey was received. This is done by using attributes that reference the 'event' eg. "month/year (event)" instead of "month/year (ticket solved)". However, the metrics in the video above will not allow you to slice by the event because they do not encompass the required part of the data model. To do this will require more complicated metrics that are outlined below. 

That being said, even if you build a report that slices by the event, there are two things will still prevent you from achieving parity with the in-app reports. These are:

1. If the ticket is already closed at the time when a customer responds to a survey app question, then the score is recorded in the app. (this is unlike the Zendesk CSAT scores that simply throw up an error saying 'you can't rate this ticket because it's closed'). Since the app is recording this score, but the ticket is closed, it is not possible for the app to update the ticket fields with those scores. So, the score would become part of the in-app results (including the NPS calculation) but over in Insights, this data would not exist. 

2. The other thing to note is that if the customer was to respond to a survey while the ticket was unclosed (say on Jan 27), the score would be recorded in both app & Zendesk. However, if after the ticket was closed (say on Feb 2) the customer updated their response (even if it was just to change the comment) then the app would register that the last update took place on Feb 2. But since the ticket was already closed, the data passed over to insights would have the last update recorded taking place on Jan 27. This would affect the scores of both Jan and Feb over in Insights.



Ok so now that you're aware of some of the data quirks if you're keen to build an insights report that gets broken down by the event here's how...

First, you'll need to create 4 metrics that to do essentially the same as what you saw in the video, it's just that they're structured a little differently. 

1. Total No. of  tickets with an NPS rating

2. No. of promotors

3. No. of detractors

4. NPS calculation


Below are the metrics you'll need to duplicate in your Insights. 

Note that, same as when building any metric, you can not just copy and paste stuff, you'll need to pay attention to the colours of the elements and find them in the right menu of the popup screen:

Facts: Blue
Metrics: Green
Attributes: Purple
Attribute values: Orange


1. Total No. of  tickets with an NPS rating



2. No. of promotors



3. No. of detractors



4. NPS calculation



Finally to build the NPS report, for "What" simply select "SURVEYAPP: NPS Score" or whatever you decided to name number 4. NPS calculation. 

For "How", select "month/year (event)".

And make it a bar chart to look something like this:



Of course, now that the report is built, you can then go about making all manner of other modifications to it like slicing it by group, individual, organisation, product type, reason codes etc. 



Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk