The Zendesk Ticketing System

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

The moving parts

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 is 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 cannot 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 system can't see

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

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

Frequently asked questions

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?+

Yes. Start in suggest-only mode: Ticket Merger flags the pairs it believes are duplicates and leaves the decision to an agent. Most teams run that way for a week, check the hit rate, then let the confident matches merge on their own.

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

Rules you set. Match on requester, subject similarity, body similarity and a time window, and exclude anything you want left alone, like tickets from a specific form, group or tag. Anything below your confidence threshold gets suggested rather than merged.

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.