VOICE OF CUSTOMER ANALYTICS FOR ZENDESK
Zendesk ticket analysis that tells you why
Zendesk measures what happened. Pivony tells you why.
Pivony reads every ticket, chat and message in your Zendesk, groups them into the causes behind them, and writes the answer back into Zendesk as tags and fields. Your Explore reports, views and triggers finally run on the reason, not on whatever an agent picked from a dropdown.
First root-cause report in 24 hours · No manual tagging · Support, Chat and Messaging
24 h
to the first root-cause report
90 days
of history analyzed on connect
0
tags your agents have to pick
9
languages natively, mixed-language queues fine
HOW PIVONY SEES YOUR QUEUE
Root cause analysis for support tickets
Thousands of tickets in, a handful of causes out. Every email, chat and message is read and grouped by the cause behind it. The biggest causes go straight back into Zendesk as tags and fields.
New to the method? Read how root cause analysis works, or get a free root cause audit on a ticket export.
AI ticket sentiment analysis for Zendesk
Pivony reads every ticket, public reply, Chat and Messaging transcript and scores its sentiment. You see sentiment per ticket and across each cause, so you know which causes make customers angriest and whether that is getting worse.
- Sentiment on every ticket, chat and message
- Negative sentiment traced to the cause behind it
- Written back to Zendesk for views, triggers and Explore
Automatic ticket tagging and categorization
Agents stop picking tags. Pivony categorizes each new ticket by its cause within minutes and adds pivony_ tags and two custom fields, in every language your customers write in. Your existing tags, fields and workflows stay untouched.
- Categorized within minutes of arrival
- pivony_ tags plus two Pivony custom fields
- Existing tags and triggers left as they are
THE GAP
Labeling a ticket is not the same as explaining a trend.
Intelligent Triage stops at one ticket
Intent, language and sentiment on each ticket are useful for routing. They do not tell you why volume rose 30% this month, or which product change caused it.
Explore reports only what is tagged
If agents tag inconsistently, every dashboard built on those tags is wrong. Most teams know this and stop trusting the numbers.
The ticket is only one channel
The same customer also answers surveys, writes reviews and posts on social. Zendesk sees the ticket. It does not see the rest of the relationship.
INSIDE ZENDESK
Four places your team sees Pivony, without leaving Zendesk
Pivony installs as a Zendesk app. Agents and leads work where they already work; the analysis happens in the background.
Ticket sidebar
On every ticket: the root cause, how many similar tickets came in over 14 days, whether the cause is growing, the sentiment, and how often this requester has written in about it.
Tags and fields, written back
Each analyzed ticket gets a pivony_ tag and two custom fields, Pivony Root Cause and Pivony Sentiment. Build views, triggers, SLAs and Explore reports on them like any other field.
Weekly root-cause report
A Pivony tab in the Zendesk navigation: the top causes this week, last week, the change, and which causes are rising. One click opens the full analysis in Pivony.
Monday email for support leads
Every Monday morning: what changed, which causes are growing, and the link to the evidence. Written for the person who has to explain the numbers upstairs.
BEYOND THE TICKET
Every requester, connected to the rest of their customer journey
With Pivony Customer 365, the ticket is no longer an island. Pivony matches the requester by email or external ID to the same person in your surveys, reviews and social channels, and every analyzed ticket appears on their Customer 365 timeline.
Customer 365 features appear when your organization uses Pivony Customer 365.
Customer 365BOUNDARIES
What Pivony does, and what it deliberately does not
Pivony does
- Reads tickets, public replies, Chat and Messaging transcripts
- Adds pivony_ tags and fills two Pivony custom fields
- Creates one webhook and one trigger so new tickets arrive in minutes
- Shows a sidebar app and a navigation-bar report inside Zendesk
Pivony does not
- Does not route, reassign or reprioritize tickets
- Does not reply to customers or draft answers
- Does not score or monitor agents
- Does not remove or rename your existing tags
- Does not read agent-only internal notes
NEXT TO ZENDESK
Pivony vs Zendesk Intelligent Triage and VOC Patterns
They do different jobs. Intelligent Triage classifies each new ticket so it can be routed. VOC Patterns, a Zendesk Labs app, finds patterns in solved and closed tickets. Pivony explains the causes behind your whole queue and writes them back to every ticket. Based on Zendesk’s own documentation, October 2026.
| Capability | Pivony | Intelligent Triage | VOC Patterns |
|---|---|---|---|
| Intent, sentiment and language per new ticket | Sentiment and cause per ticket | Yes (Suite or Support Professional and above) | No, works on patterns |
| Patterns or causes across many tickets | Yes, every cause linked to its tickets | No, one ticket at a time | Yes, in solved and closed tickets |
| Which tickets and how fresh | Open and past tickets; new ones within minutes | New tickets as they arrive | Solved and closed; refreshed every 12 hours |
| Writes results back to the ticket | pivony_ tags and two custom fields | Standard fields; workflows need the Copilot add-on | Not described |
| Same customer across surveys, reviews and social | With Customer 365 | Tickets only | Tickets only |
WHO IT IS FOR
One analysis, three teams
Head of Support / CX
Explain why volume moved, with evidence, before the weekly review. Bring product and operations the three causes worth fixing first.
Support operations
Stop maintaining a tag taxonomy nobody follows. Build views, triggers and SLAs on Pivony fields that are filled the same way every time.
Product and VoC
See which release, policy or partner drives contacts, and which of those customers are also unhappy in surveys and reviews.
SETUP
How it works: connect Zendesk in minutes
Connecting takes minutes. The first root-cause report arrives within 24 hours, and you are fully live within 48.
01
Connect Zendesk from Pivony
In Pivony, open Settings › Integrations, choose Zendesk and sign in with your Zendesk admin account. Pivony uses OAuth, so there are no API keys to paste.
02
Install the Zendesk app
Install Pivony from Zendesk and paste the token shown on the connect page. Pivony reads the last 90 days of tickets and conversations; the first report arrives within 24 hours.
03
Choose what is written back
Keep tags, fields or both. From then on every new ticket is analyzed within minutes, and the Monday email starts the following week.
SECURITY AND PERMISSIONS
Your ticket data stays protected
- Zendesk permissions: read and ticket write-back, plus webhook and trigger rights used only for Pivony’s own webhook
- Personal data is masked before analysis, following GDPR and KVKK patterns
- Access tokens encrypted at rest and refreshed automatically; nothing to rotate by hand
- Hosted on Google Cloud; ISO 27001, 27017 and 27018 aligned
- Encrypted with AES-256 at rest and TLS 1.3 in transit
- Disconnect any time: syncing stops at once and synced text is deleted within 30 days
FAQ
Questions support leaders ask
How does it run inside Zendesk?
Pivony is built for Zendesk: it installs as a Zendesk app, connects with Zendesk OAuth and writes back through the Zendesk API. During early access we set it up together with your team.
How do I analyze Zendesk tickets?
Connect Zendesk to Pivony with OAuth and install the Pivony app. Pivony reads the last 90 days of tickets and conversations, groups them by cause and sends the first root-cause report within 24 hours. After that, every new ticket is analyzed within minutes.
Can AI tag Zendesk tickets automatically?
Yes. Pivony categorizes each new ticket by its cause within minutes and writes pivony_ tags and two custom fields back to Zendesk, so agents no longer pick tags by hand. Your existing tags are not changed.
How is this different from Zendesk Intelligent Triage?
Intelligent Triage classifies each new ticket by intent, sentiment and language so it can be routed. Pivony works across tickets: it finds the causes behind your volume, tracks how each cause changes and writes the result back as tags and fields. Many teams use both: Triage routes, Pivony explains.
Which Zendesk plan do I need?
Any Support or Suite plan. Chat and Messaging transcripts are included wherever your plan provides them.
Does it change my existing tags?
No. Pivony adds its own pivony_ tags and fills its own two fields. Existing tags, fields and workflows are untouched.
Does Pivony route or answer tickets?
No. Pivony is an analysis layer. It does not reassign tickets, reply to customers or score agents, so it sits next to your routing, bots and QA tools without conflict.
Which languages are supported?
Turkish, English, Arabic, German, French, Spanish, Italian, Portuguese and Serbian natively, plus more than 20 others. Mixed-language queues are fine.
Do I need Pivony Customer 365?
No. Root causes, write-back, the sidebar, the weekly report and the Monday email work on Zendesk alone. With Customer 365 you also see each requester across surveys, reviews and social.
How is this different from a QA tool like Zendesk QA?
QA tools score how agents handled a conversation. Pivony explains why customers wrote in the first place. Most teams run both; they answer different questions.
See the reason behind every Zendesk number.
Connect your Zendesk on a 30-minute call and get your first root-cause report within a day.
Zendesk is a trademark of Zendesk, Inc. Pivony is an independent product built to work with Zendesk.