With Explore, you'll often want to create reports based on the channel from which a ticket was created. Channels are the means by which your customers create support requests and how you engage with them.
The channels you see will depend on the channels you have installed. For example, if you haven't set up Facebook integration with Zendesk Support, you won't see the Facebook channel.
Use this article to learn how to view the channels you can report about in Explore, and to learn how channel names will appear when you create reports that use them.
To learn more about channels in general, see About Zendesk Support channels.
This article contains the following topics:
How to view ticket channels in Explore
Use this simple report to see the names of all ticket channels you have used and the number of tickets assigned to each channel. If you need help creating a query, see Creating queries.
To view your ticket channels
- In Explore, open a new query using the Zendesk Tickets dataset.
- In the Metrics panel of query builder, add the Tickets metric.
- In the Rows panel, add the attribute Ticket channel.
You'll see a table that looks similar to the example below:
Support channels in Explore
The following support channels are available in Explore reports. The channels that are shown will vary depending on the channels you've configured.
| Ticket channel | Displayed in Explore as | Description |
|---|---|---|
| Answer Bot for Web Widget | Answer Bot for Web Widget | Tickets created from Answer Bot suggestions that led to a ticket being solved. |
| Any channel | Any channel | Tickets created from third-party Zendesk integrations. |
| Web service (API) | Api | Tickets generated or updated from the Zendesk API, for example:
|
| Chat | Chat | Tickets created from a Zendesk Chat session. |
| Tickets originating with an email request. | ||
| Facebook message
Facebook post |
Tickets generated from Facebook posts and messages. | |
| Forum topic | Forum | Tickets originating from a community post. |
| Help Center post | Help Center | Tickets that were created from a community post in the Help Center. |
| Mobile | Mobile | Tickets originating from a Zendesk mobile app. |
| Mobile SDK | Mobile SDK | Tickets generated from a custom app using the Zendesk Mobile SDK. |
| Text | SMS | Tickets originating from a text message. |
| System | System | Tickets created by Zendesk Support. Examples include tickets created by importing from another application. |
| Twitter
Twitter DM Twitter Like |
Tickets originating from a Twitter mention, DM, or like. | |
| Phone call (incoming)
Phone call (outgoing) Voicemail |
Voice | Tickets originating from Zendesk Talk calls and voicemails. |
| Web form
Web Widget |
Web | Tickets originating from a Support web form or the Web Widget. |
10 Comments
How is the web widget channel shown in Explore?
Hello, Kay,
In Explore, web widget is displayed as belonging to the web channel.
I am going to ask the Docs team to add that info to the article. Thanks!
Hi Kay, thanks for pointing this out. I've now added Web Widget to the article (thanks also Ricardo!).
Lumping the Support Web Form and Web Widget into the same channel (Web) in Explore is not ideal. They're distinctly different ways of getting in touch. You've separate out Mobile and Mobile SDK—I would think Web and Web Widget would be a similar case.
Hi Elizabeth,
Completely understand where you're coming from here. I would also recommend sharing your feedback in our Explore Product Feedback forum.
Appreciate you taking the time to share this with us!
It looks like integrations such as Google Play Reviews and Appfollow (for Apple reviews) are called "Any channel".
Has anyone else experienced this behavior?
What I don't understand is that we are able to differentiate between those channels inside Zendesk, views etc. why would they be aggregated to "Any channel" in Explore?
Hi Rob,
In the example you gave in the "How to view ticket channels in Explore" part, is the default tickets nubmer covered the whole time range?
Hi Wycherley Wei
Yes, the example will report for all of your tickets. You could add a date range like Tickets solved to the Filters panel to show only tickets between certain dates. Hope this helps!
Rob Stack was wondering if you could help me with something. We are looking to build a query that looks at when a tag value changes. I,e., we add a tag to a ticket.
Is there any custom metric you could help me think of that could solve this?
Hey Bobby,
We do have a recipe for Reporting on the duration of fields that may point you in the right direction.
I hope this helps!
Please sign in to leave a comment.