Zendesk Ticketing System: A Beginner's Guide

TL;DR

• The Zendesk ticketing system turns every request into a ticket with a requester, an assignee and a status; employees are "end users" and the people answering are "agents."

• Solved and Closed are different states. A solved ticket reopens when the employee replies, and a closed one never does.

• Triggers fire when a ticket changes, automations fire when time passes, and they both run in an order that decides what wins.

• If your desk only serves employees, price the Employee Service Suite, not the plans on Zendesk's main pricing page.

The Zendesk ticketing system was built to answer customers, and most of its documentation still reads that way. Plenty of internal IT teams run their help desk on it anyway, which means translating as you go: a "customer" is an employee, a "brand" might be your IT desk, and a "CSAT survey" is the message your colleagues ignore after you fix their laptop.

Most of what trips up a new admin comes from defaults nobody changed. A blank Priority field takes a ticket out of every SLA, email from your own monitoring tools can vanish into a queue nobody checks, and the plan you'd budget from the main pricing page isn't the one an IT desk should buy. All of it is below, checked against Zendesk's own help center on November 3, 2026. Your admin's configuration still overrides the defaults, so treat them as a starting point.

What Is the Zendesk Ticketing System?

The Zendesk ticketing system is the ticket engine inside Zendesk Support: it turns every email, form submission, message or call into one ticket with a requester, an assignee, a status and a full history. You can buy Support on its own or inside a Zendesk Suite with messaging and a help center. A Zendesk ticket is the record of one request, from the first message to the final reply, which is exactly what you want the day someone asks who changed a field and when.

Two roles matter on day one: agents work tickets inside Zendesk, and end users raise them. In an internal deployment, end users are every employee who emails the IT address or submits a form. They never see the agent interface; they see email replies and, once signed in, a help center where they can check their requests.

Two more terms get mixed up constantly. Groups hold agents ("Groups can only contain team members; no end users can be included"), so they map to your IT teams: Service Desk, Endpoint, Identity and Access. Organizations hold end users, and you can add employees to one automatically by email domain, so they map to departments, offices or subsidiaries. You route work with groups. You use organizations when a department or site needs its own rules or views.

Light agents are the third role worth knowing about. They can view tickets and add private comments, but they can't be assigned tickets or change a ticket's status. That suits the HR partner or security lead who needs to see a ticket without working it. Suite Growth includes up to 50, Professional up to 100, and on Suite Team they're an add-on.

Zendesk also sells an Employee Service Suite for IT, HR and other internal teams. Zendesk says its plans "include all the features of the equivalent Zendesk Suite Customer Service plans, except for Voice," and it adds a service catalog and approvals. Everything in this guide applies to both. The pricing doesn't, and that's covered further down.

How Do You Create a Ticket in Zendesk?

Tickets get into Zendesk through email to your support address, the help center's Submit a request form, messaging, and integrations like Slack and Microsoft Teams. An agent can also create one on a requester's behalf. Email is the default for most internal desks: mail sent to the IT address becomes a ticket, and Zendesk reads the email headers to set the sender as the requester.

Not every email makes it. Zendesk holds suspicious mail in a Suspended tickets view, and "if nobody reviews a suspended ticket, it's automatically deleted after 14 days." Internal desks get more of this than customer desks, because a lot of IT email is machine-generated: alerts from monitoring or MDM tools and employees' out-of-office replies are the usual suspects. Put someone's name on that view and have them check it daily while you're setting up.

Multiple ticket forms are where internal desks get real value, because a hardware request and an access request need different fields. They're available on Suite Growth and above (and Support Enterprise), so a Suite Team account gets one form. When an account has several, employees pick from a dropdown, and you can link straight to a form with its ID in the URL so nobody picks the wrong one.

The Slack for Zendesk Support integration lets people turn a Slack message into a ticket with a message action, the /zendesk shortcut, the sidebar app or an @zendesk mention in a Slack Connect channel. The requester defaults to the Slack user who created the ticket. Know its limits before you promise anything to the business: tickets created from Slack can only be assigned to a group, fields can't be edited there, and "you cannot currently close tickets using Slack." The Zendesk for Microsoft Teams integration goes further, letting users "create, view, and update Support tickets" and add internal notes or public replies from Teams, on every Suite plan.

When you need to log a request yourself, say after a hallway conversation or a phone call, you can create a ticket on the requester's behalf:

1. Hover over +Add in the top bar and select Ticket.

2. Check the composer. If your account creates agent tickets as private, it starts on Internal note and the employee won't see the ticket until you switch to Public reply. Otherwise the ticket is visible to them by default.

3. In Requester, search by name or email, or click +Add user for someone without an account.

4. Write the subject and description, fill in the fields that matter and click Submit as New.

The requester only gets a "we received your request" email if your admin has a trigger set up for it, so check that before you tell anyone they'll hear from you automatically.

What's on a Zendesk Ticket?

Every Zendesk ticket carries the same standard fields, and admins add custom fields on top. These are the ones you'll touch on every ticket:

Type is worth five minutes of your time, because it does more than just label the ticket. Mark the ticket behind a widespread outage as a Problem and link every "Wi-Fi is down on floor 3" report to it as an Incident. When you solve the problem, Zendesk solves every linked incident too, and it copies your solve comment onto every incident that isn't already solved. So write that comment for the 40 employees who'll read it, not for your team.

Leave Priority blank and the ticket has no SLA. A policy only applies when the system Priority field has a value, so a blank ticket can sit for a week and never breach. If you use SLAs, check whether your account already has a trigger that sets a default priority on new tickets, and add one if it doesn't.

Zendesk Ticket Statuses, and the One That Trips People Up

Every Zendesk ticket moves through a lifecycle of six statuses:

The one that trips people up is the gap between Solved and Closed. A solved ticket reopens the moment the requester replies, and it goes back to the agent who solved it (unless a trigger reassigns it). A closed ticket can't be reopened at all; a reply just creates a new follow-up ticket that references the original.

The move from Solved to Closed is done by an automation, four days after solving by default. Admins can change that window to anything up to 28 days, but they can't switch the automation off, and Zendesk closes every solved ticket at 28 days regardless. You've probably seen the employee who replies "still broken" a week later; with a four-day window that reply becomes a brand-new ticket, which means your reopen rate never counts it. If reopens are a number you report upward, lengthen the window or count follow-ups alongside reopens.

On-hold is invisible to employees, because "On-hold tickets appear as Open to your customers," per Zendesk. That's what you want when the delay is a hardware vendor. Use Pending for "send us a screenshot" and On-hold for "the vendor is shipping the part," and your waiting time ends up attributed to the right person.

If the six don't fit, admins can add custom statuses inside the Open, Pending, On-hold and Solved categories (not New or Closed), so "Waiting on Procurement" can sit inside On-hold and still report correctly. Newer accounts may also show an "In Progress" status, so don't be surprised if you count seven.

How to Work a Zendesk Ticket From Start to Finish

Say an account executive emails that her laptop camera stopped working after a macOS update, and she has a customer call at 2:00. Here's how that ticket should actually go in the Agent Workspace.

1. Check What Arrived Before You Act

Open the ticket from your view and read the description in full. Then search the requester's other open tickets, because she may have pinged the Slack channel too and created a second one. If she has, merge the duplicate into the main ticket (the clicks are in the FAQ below). The duplicate is closed, and merges "are permanent and can't be undone," so double-check the ticket number.

2. Set Type, Priority and Group

Zendesk defines an Incident as one occurrence of a larger problem, but plenty of IT desks use it for every break-fix ticket anyway. Pick one convention, write it down and stick to it. Here it's an Incident, and with a customer call in four hours it's High. Assign it to the Endpoint group, then to yourself if you're taking it, and note why a camera got High, because the next agent will want to know.

3. Reply Publicly, Note Privately

The composer switches between Public reply and Internal note, and the default your admin chose decides which one you get, so check it every time you type. A public reply goes to the employee; an internal note stays with agents and followers. A useful internal note reads something like this:

Camera not detected in Zoom or Photo Booth after macOS update this morning. Privacy settings show Zoom allowed. Asked user to restart; awaiting result. Next step: reset camera permissions via MDM if restart fails.

4. Use Pending and On-hold for What They're For

When you ask her to restart and confirm, set the ticket to Pending. If the restart fails and the MDM team has to push a fix, open a side conversation to them and move your ticket to On-hold. Their part of the work sits with them, and the thread stays on her ticket.

5. Solve With a Note the Next Person Can Use

Test the fix with her, then set the ticket to Solved with a public reply saying what changed. If she writes back "still broken" in two days, the ticket reopens to you. If she writes back in ten, she gets a follow-up ticket instead. Add an internal note if the fix was a workaround, because a workaround solved today is the same ticket next month.

Zendesk Views, Macros, Triggers and Automations

Views, macros, triggers and automations are Zendesk's four workflow tools, and new admins swap the last two constantly.

If something should happen because a ticket changed, it's a trigger: a new ticket from the CFO goes to High, or a ticket on the access form goes to Identity and Access. If it should happen because time passed, it's an automation: chase a ticket that's been sitting in Pending for 24 hours. "After 24 hours" actually means sometime in the hour after 24 hours, because automations run once an hour and not at the top of it. That matters when you've promised an employee a reminder at a specific time.

Order is the other thing to understand, and it's the usual reason an inherited instance does strange things. "Ticket triggers run in the order they are listed," and "if a ticket trigger updates a ticket during the cycle, the cycle starts over," according to Zendesk. A single trigger never fires twice in one cycle, but if trigger 3 sets the group to Endpoint and trigger 9 sets it to Service Desk, Service Desk wins. When something routes oddly, read your triggers top to bottom in the order Zendesk does. For which work to automate first, our guide to help desk automation is a good next read.

How Does Zendesk Assign Tickets Automatically?

Zendesk assigns tickets automatically in three layers. Triggers set a group or agent from any condition you can describe, like form, tag, requester or keywords in the subject, and every plan has them.

Omnichannel routing pushes tickets to available agents based on their status and spare capacity, on every Suite plan and on Support Team and above. Email tickets need an agent who is online or away, and in the standard queue a ticket has to be assigned to a group (and carry a routing tag) before it's eligible. Routing by skills and by priority starts at Professional.

Intelligent triage is the AI layer, classifying new tickets by topic, sentiment, language and entities on Professional and above, with Zendesk's Copilot add-on needed to use those classifications in workflows. Test it on your own tickets first: Zendesk describes its sentiment as "calibrated for customer service contexts," and an employee writing "laptop dead again" reads differently from a customer threatening to cancel. There's more on how AI ticketing systems classify requests in our guide to them.

How Do SLAs Work in Zendesk?

A Zendesk SLA policy sets reply and resolution targets for each ticket priority and times every matching ticket against them. SLA policies are on Suite Growth and above, and on Support Professional and Enterprise, and the order of your policies matters, so put the strictest at the top.

Set your business hours first. Without a schedule your targets run on calendar hours, so a ticket raised at 5:00 on a Friday can miss its first reply target before anyone is back on Monday. Growth and Professional get one schedule, and you need Enterprise for several (separate Seattle and London desks, say). Add public holidays too, though Zendesk can't do half days.

You can target seven metrics: first reply time, next reply time, periodic update, pausable update, requester wait time, agent work time and total resolution time. They don't all pause the same way:

• Agent work time pauses on both Pending and On-hold.

• Requester wait time pauses on Pending only, so time spent waiting on a vendor still counts against you.

• Next reply time restarts with each new employee comment, and periodic update resets after every public agent reply; neither pauses.

Decide which one goes in the leadership report. Requester wait time keeps counting while a vendor ships a part, and agent work time doesn't. Report requester wait time, because it's what the employee actually lived through, and put agent work time next to it so a vendor delay doesn't read as a slow desk.

A Starter Setup for an Internal IT Desk

If you're setting Zendesk up, start from this. If you've inherited it, compare what's already there against this list before you change anything, because triggers run in order and one edit can change what fires after it.

Groups: Service Desk, Endpoint and Devices, Identity and Access, Apps and SaaS. One group per team that owns work.

Ticket forms (Growth and above): Report a problem, Request access, Request hardware, New starter or leaver, Ask a question. Give each form only the fields that request needs.

Triggers. Keep the standard notification triggers, then add these:

Automations: activate the standard "Pending notification 24 hours" automation, which is inactive when you sign up, so employees get nudged a day after you set Pending. Add one that solves tickets left in Pending for five days and tags them auto_solved, so you can report on them. Every automation needs a condition or action that stops it firing again, and setting the status to Solved does that here.

Views: Unassigned in my groups, My open tickets, Pending for more than 3 days, On-hold by group, SLA breaching in the next hour.

Macros: Need more info (public reply, status Pending), Waiting on vendor (internal note, status On-hold, tag vendor_wait), Password reset steps (public reply with the help center link, status Solved), Escalate to Identity and Access (group change plus an internal note).

Housekeeping: switch on On-hold, set business hours, put a name on the Suspended tickets view, decide whether employees should get CSAT surveys at all, and agree a short tag vocabulary before everyone invents their own.

Zendesk Pricing in 2026: How Much Does It Cost?

Zendesk sells two Suites, and most pricing articles only show you one. If your desk only serves employees, the Employee Service Suite is the price list you'll be quoted from; Zendesk designs it for customers who "exclusively use Zendesk products for internal employee services." Prices were read on November 3, 2026, and Zendesk revises them often, so hold them loosely.

If the same team also answers customers, you're on the Customer Service Suite instead: Suite Team at $55 and Suite Professional at $115 per agent per month billed annually, with Support Team at $19 for ticketing alone. That page shows no Growth tier, so SLAs and multiple forms start at Suite Professional there. Pricing is per agent, and end users don't take a license, so the employees raising tickets are free. There's no free plan, but there is a 14-day trial.

Copilot and AI agents are billed on top of seats. Copilot costs $50 per agent per month, paid yearly, and can be added to Professional and above. AI agents come with a monthly allowance of automated resolutions, and past that you pay $1.50 each on a commitment or $2.00 pay-as-you-go, per the pricing page. An eight-agent IT desk on Employee Service Growth pays $472 a month on annual billing, or $792 on Professional, before any of that.

Zendesk only bills an automated resolution once the conversation has ended (72 hours after the first email on the email channel) and an LLM check has verified the AI agent actually resolved it. Escalated conversations don't draw on the allowance. I believe this is the line item IT leaders should model hardest. With outcome-based pricing, the invoice grows as the AI agent gets better at password resets and access questions. That's how the model is meant to work, but it's easy to miss when you budget, so price each resolution against your own cost per ticket before the AI agent goes live.

Is Zendesk Good for Internal IT Support?

Zendesk works well for internal IT when most requests arrive by email or a portal, or when the same team also supports customers. You get mature triggers and macros that cover most of what a small IT desk needs without writing code, the help center is a real knowledge base, and the Employee Service Suite adds the approvals and service catalog an IT desk leans on.

The friction is in two places. The vocabulary and default reports are written for customer service, so you'll spend the first month renaming things and switching off dashboards built for a different job. And the chat integrations bring requests in, but the work still happens in the Agent Workspace: the standard Slack integration can't close tickets or edit fields, and you'll want to test exactly what your plan can do in Teams.

The test is the same one we used for the Jira, ServiceNow, Freshservice and BMC Helix guides: look at where your requests actually arrive today. If it's email, Zendesk will feel like an upgrade. If it's Slack or Teams, check how much of the work can stay there before you commit, and compare it against the Zendesk alternatives built for that.

Ravenna: Ticketing That Starts in Slack and Teams

Ravenna starts from the other end, as a Slack and Teams ticketing system where the conversation is where the ticket gets created. An employee asks in Slack or Teams, and our AI agents answer from your connected knowledge when the answer exists, or escalate to your team when it doesn't, with the original thread kept on the ticket. Nobody gets sent to a portal, and you still get the record, the owner and the ticket history.

If you've spent years building a Zendesk help center, you don't have to throw it away. Ravenna's Zendesk knowledge integration syncs published articles from the help center categories you choose into Ravenna, so its AI agents can answer from them. The connection is read-only. With auto-sync on, new and edited articles flow in automatically, and anything you unpublish in Zendesk drops out of agent responses.

Everything above came with a translation layer: customers are employees, a brand is your IT desk, and the CSAT survey is still the message your colleagues ignore. Ravenna was built for employees from the start, so there's nothing to translate. Start where they already ask.

If you want to see it on your own requests, we're happy to walk you through it, or you can poke around the docs first.

Frequently Asked Questions

Is Zendesk a CRM or a Ticketing System?

Zendesk is a ticketing system first. Zendesk Support is the ticketing product, and the Suite adds messaging and a help center around it. It keeps user and organization records, which is why people call it a CRM, but it doesn't do the pipeline or deal tracking you'd get from a sales CRM.

What Is Zendesk Used For?

Zendesk is used to receive, track and answer support requests. Most companies run customer service on it across email, web forms, messaging and phone, and internal IT and HR teams use the same ticketing engine, often on the Employee Service Suite, for employee requests.

Is Zendesk Free?

No. There's no free plan, though there is a 14-day trial. Paid plans start at $19 per agent per month for Support Team on annual billing, or $29 for Employee Service Suite Team, and employees who only raise tickets don't need a seat.

How Do You Merge Tickets in Zendesk?

Open the duplicate, choose Ticket options > Merge into another ticket, pick the ticket to keep, set the merge comment to public or internal and click Merge tickets. The ticket you're merging has to be below Solved, though you can merge it into a solved ticket, and merges can't be undone. Tickets from different requesters can only be merged if CCs are enabled.

How Do You Close a Ticket in Zendesk?

You don't, directly. Agents set tickets to Solved, and an automation closes them, four days later by default and never more than 28 days after solving. If you need tickets locked sooner, ask your admin to shorten the close automation.

How Do You Create a Zendesk Ticket From Slack?

Install the Slack for Zendesk Support integration and invite it to the channel. Then use the message action on any Slack message, the /zendesk shortcut, the sidebar app or an @zendesk mention in a Slack Connect channel. The ticket can only be assigned to a group from Slack, and you'll need to open Zendesk to edit fields or close it.

Can Zendesk Assign Tickets Automatically?

Yes. Triggers can set the group or assignee on any plan, omnichannel routing assigns by agent availability and capacity on every Suite plan, and skills and priority routing start at Professional. Intelligent triage adds AI classification on Professional and above, with the Copilot add-on needed to route on it.

Who Are Zendesk's Biggest Competitors?

It depends on who's asking for help. In customer service, Zendesk competes with tools like Freshdesk, Intercom, Salesforce Service Cloud and Zoho Desk. For internal IT, it's weighed against ITSM platforms like ServiceNow, Jira Service Management and Freshservice, and against Slack and Teams-native tools like Ravenna.