The Zendesk Ticketing System

How a ticket actually moves through the Zendesk ticketing system, and which parts you configure rather than accept.

The Zendesk ticketing system, part by part

Channels. Email, Web Widget, help centre forms, chat, talk, social and API all create tickets in the same queue.
Ticket fields. Requester, assignee, group, status, priority, type, plus your custom fields and forms.
Views. Saved filters that decide what each team sees. Views are where a Zendesk instance is won or lost, because agents work what's in front of them.
Triggers. Event-based rules firing on create and update. Routing, notifications, tagging.
Automations. Time-based rules firing on ageing tickets. Chasers, escalations, auto-close.
Macros. Prepared actions an agent applies deliberately.
SLA policies. Targets with a clock, optionally paused while you wait on the customer.
Explore. Reporting, deep enough to answer questions nobody anticipated and steep enough that most teams use a fraction of it.

The lifecycle

New, Open, Pending, On-hold, Solved, Closed. The two that matter operationally are Pending and Solved.

Pending means you're waiting on the customer, and it should pause your SLA clock. Teams that skip this end up reporting the customer response time as their own.

Closed is final in Zendesk. A closed ticket can't be reopened, so a customer replying to one gets a brand new ticket with a link back. That behaviour is a significant source of duplicate tickets, and it isn't configurable.

What the Zendesk ticketing system can't see

Every mechanism above evaluates one ticket. There's no view, trigger, automation or macro that can express "there's another open ticket from this person saying the same thing".

So duplicates are handled by an agent noticing, which means they're handled late or not at all. See duplicate tickets in Zendesk and how to merge them.

FAQ

Frequently asked questions

Is the Zendesk help desk ticketing system the same as Zendesk Support?

Yes. Zendesk Support is the product name; the Zendesk help desk ticketing system is what people call it when they're describing what it does.

What is the Zendesk ticketing system?

It's the core of Zendesk Support. Every message from email, chat, phone, web form or social becomes a ticket with a requester, a status, an assignee and a full history, and triggers and views decide where it goes next.

Does merging in Zendesk lose the customer replies?

No. Ticket Merger uses the native Zendesk merge, so the conversation, attachments and audit history move onto the surviving ticket. The duplicate is closed with a note pointing at the original.

Can I review merges before they happen?

No. Once a pair matches your rules, Ticket Merger merges it. What you control is what qualifies: requester, the subject keywords you list, the time window, and the groups, forms or tags you exclude. To see how it behaves before it touches everything, point it at one group first and widen from there. Every merge leaves a note on the thread saying what was merged and why.

What stops it merging two tickets that are not the same?

Rules you set. Match on requester, subject keywords, status, priority, category or group, and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything that does not clear those rules is left alone.

How long does setup take?

About five minutes to connect, and the first scan of your open queue runs immediately after. Onboarding help is included on every plan.

Add what the ticketing system is missing

Continuous comparison across the open queue, then a native merge. Live in five minutes.

Start free trial

14-day free trial. No credit card required.