How to recreate the Insights CSAT dashboard in Explore
我们的目标
It can be really satisfying (ha) to see all of your CSAT ratings with clear visual indicators for good and bad CSAT in the Reporting section of your instance. As Insights will be removed in February 2021, I thought I would share how we recreated this experience using Explore.
先决条件
- Zendesk Explore Professional
- Image links for the indicator you would like to use
Explore doesn't have a way to highlight the rating name as green or red, but you can add a URL to an image and use that to make it easy to visually identify good and bad ratings. In my case, I chose a green dot for good and a red dot for bad.
Instructions
Step 1
- Create a newExplore queryusing the Support: Tickets dataset
Step 2
- Add the metric COUNT(Rated Satisfaction tickets)
- Add the following attributes to Rows:
- Ticket solved - Date (filter: Edit date ranges>Advanced> 1 month in the past to today) You may need to adjust the date filter depending upon the number of rows generated. Reducing the timeframe should allow you to avoid reaching the row limit.
- Assignee Name
- Clickable Ticket ID
- Ticket Satisfaction (filter: Include Good, Bad)
- Ticket Satisfaction Comment
Step 3
- Create a Renamed Set Attribute
- For this step you will need your image URLs
- Click on Calculations at the right
- Select "Renamed Set"
- Name your new attribute, I chose "Ticket Satisfaction Dots Rename"
- Set the "Computed From" to Ticket Satisfaction Rating
- For each condition add the URL for the image you would like to represent that attribute
- Save your changes
Step 5
Now you'll need to configure your query to recognize the links we just added.
- Click on the Configuration paint brush icon on the right side
- 选择图
- Change the "Text Interpretation" field to HTML
Once saved, you can now add this new attribute to your rows. Your attributes will look like this:
Step 5
- Apply any filters that make sense for your business model. For instance, we tag chat trolls so they can be excluded from our satisfaction comments.
The Result
Your finished product will look similar to this:
Now you can have a quick and easy view of your CSAT in Explore. Enjoy!
-
Official comment
I absolutely love this recipe. It's amazing to see the clever things people are making Explore do. Thanks for posting!!!
-
好的文章!Thx@...!
特别是图像的评级。我从来没想过something like this is possible in Explore ;)
-
Glad to help@...!
-
Thanks@..., this was an excellent tip!!
However I do have the same issue as Jacob, when pasting the URLs for the images I want to use in Step 3, it will only show them as an URL and not as an image. Would you mind sharing the links that you used in your query so I can try, or let me know what I did wrong?
If I copy-paste the actual emoticons ( and ), that works, and it looks kind of nice.
But if possible I would prefer if I could use these little images I created with the words "Good" in green and "Bad" in red. Feel free to use them if you like:
-
Sorry for double posting, but I figured it out while reading the article aboutclickable Ticket IDs!
@...if you're still having the issue, you can fix this under the Chart configuration > Chart menu.
It looks pretty nice, doesn't it? :)
-
Antonio Rodríguez Raserothat looks fantastic! You are correct, I missed the step of changing the display behavior. I'll update that in the article. Thank you!
-
It's frustrating to not have these hyperlink directly to each ticket the way the Insights tab did. Any fixes for that?
-
HiKristen Nilles, thanks for the question. I think this recipe should help you out. You can integrate that process into this procedure.
https://support.zendesk.com/hc/en-us/articles/360022372293
I hope this helps!
-
Hi. I think I need some help. I have created the query as mentioned above and also the "Clickable Ticket ID" query. But somehow I cannot find the "Clickable Ticket ID" in the attributes?
-
The clickable link is a "Calculated metric" I believe. It won't be in the regular attributes.
-
HiLou, thanks for the feedback.
It neither shows in the attributes nor in the metrics. Also the article above mentiones in Step 2 of the introduction that it should be a attribute?
Pleasesign into leave a comment.
12 Comments