The Ticket
Every conversation in Zendesk — email, chat, web form, voice — becomes a ticket: one record with a requester, an assignee, fields, tags, and a status that tells the whole team exactly where things stand.
Sample ticket · #4127
The lifecycle
New — the ticket just arrived and no agent has touched it yet. This is the queue everyone watches.
Why it matters: status is a promise. "Pending" tells your team the ball is in the customer's court; "Open" says it's in yours. Get the statuses honest and the whole queue runs itself.
Views
A view is a saved, live-updating filter over your tickets — "unassigned," "urgent," "waiting on customer." Shared views are how a support team agrees on what to work next without anyone shouting across the room.
Team queue ·
| # | Subject | Requester | Assignee | Priority | Status |
|---|
Why it matters: search finds one ticket; a view runs the room. Build the view once and the queue sorts itself every minute after that.
Macros
A macro is a one-click play an agent calls on purpose: it drops in a ready reply, sets fields, and adds tags — all at once. Placeholders like the requester's name fill themselves in.
Pick a play
Reply to Dana
Why it matters: macros are how a team answers the same question 200 times without typing it 200 times — or drifting into 200 different answers.
Triggers
A trigger is event-based automation: every time a ticket is created or updated, Zendesk checks your conditions — and if they're met, runs your actions instantly. No human presses anything. Build one, then test-fire it.
Build the trigger
Firing log
Why it matters: macros are plays an agent calls; triggers are the defense that's always on the field. Routing, notifications, and auto-priority all live here.
Automations
Automations are the time-based cousin of triggers: they run on the clock (hourly), not on events. Classic use: a ticket sits in Pending too long → nudge the customer; still nothing → solve it politely. Advance the clock and watch.
Pending tickets
| # | Requester | Pending for | State |
|---|
Hourly sweep log
Why it matters: nobody should babysit stale tickets. Automations quietly close the loop so agents spend their day on live conversations, not archaeology.
SLA Policies
An SLA policy puts a countdown on your promises — like first reply time: how long from ticket creation to your first public reply. Pick a plan, watch the clock, and get the reply out before it breaches.
Urgent ticket · #4130
Result
The metric is running. Every minute you wait, the bar fills. Reply in time and the target is achieved; miss it and it's a breach on the board.
Why it matters: SLAs turn "we try to answer fast" into a number the whole team can see, sort by, and defend. Views + SLAs = agents always know which ticket is next.
CSAT
When a ticket is solved, Zendesk can send a one-question survey: good or bad? The rolling percentage of "good" is your CSAT. Solve the ticket, take the survey, and watch the meter move.
Close the loop
Rolling CSAT · 8 ratings
Seeded with 7 good / 1 bad. Your rating joins the sample — one voice among many, which is exactly how CSAT behaves in real life.
Why it matters: CSAT is the scoreboard the customer keeps. Pair it with handle time and you can prove you're fast and good — not one at the cost of the other.
Help Center & Deflection
The help center is your self-service library. Wire it into the ticket form and Zendesk suggests articles while the customer is still typing — every answered question that never becomes a ticket is a deflection.
Customer, mid-form
Deflection counter
Click "This answered it" on a suggested article and the ticket never gets filed. The customer's happy in 30 seconds; your queue never even noticed.
Why it matters: the cheapest ticket is the one that never arrives. A good help center is a teammate who works nights, weekends, and holidays without complaint.
Reporting
Everything the first eight innings produced — statuses, SLAs, ratings, deflections — rolls up into reporting. This is where a support team stops guessing and starts managing to the numbers.
Ticket volume by channel
Why it matters: targets only mean something if you can see them. Solved counts, first-reply medians, one-touch rate, CSAT — the box score of a support team's season.
Certification
Nine questions, one per inning. Score 7 of 9 and the Support Solutions Academy certifies you on the spot. Misses go on the board as errors — but you can always take another at-bat.