Plan requirement
| Subscription | Any plan |
| Access | Agent |
People often buy Support and then wonder where reporting lives. Here is which Zendesk product owns which job, and where they overlap.
One job each
| Product | What it owns |
|---|---|
| Support | Tickets, views, macros, triggers, automations, SLAs, users and organisations. |
| Knowledge | Help centre articles, categories and sections, themes, search, and the community. |
| Explore | Reports and dashboards over every other product. |
| Talk | Phone numbers, calls, voicemail, call recording and text messages. |
| Messaging | The web widget, WhatsApp, Facebook, Instagram, and the conversations that run through them. |
Where they overlap
The joins are where people get confused, so it is worth being precise about three of them.
- Every channel ends in Support. A call in Talk, a WhatsApp message, a form submission in Knowledge: all of them become tickets. There is no separate call inbox or chat inbox to keep an eye on.
- Explore reports on everything but owns nothing. If a figure looks wrong in Explore, the cause is almost always in the product that produced it.
- Knowledge feeds AI. Your articles are what an AI agent quotes and what Copilot suggests to your agents. Weak articles produce weak AI answers, which is why the two are more connected than they look.
What is not a product
Two things get talked about as if they were products but are not.
- Agent Workspace is the interface your agents work in, not a thing you buy separately.
- Admin Center is where you configure all of the above from one place.
Copilot, AI agents, Workforce Management and Quality Assurance are genuinely separate, but they are add-ons rather than products in their own right. They attach to what you already have.
Comments
0 comments
Article is closed for comments.