How Does Zendesk Work?

How does Zendesk work? A customer writes in, and somewhere between that message and a solved ticket a lot of quiet machinery runs. Here is what it does.

Start free trial All guides

How does Zendesk work? Everything becomes a ticket

The single idea underneath Zendesk is that every customer conversation, no matter how it arrived, becomes one record called a ticket.

A ticket holds the requester, the conversation thread, an assignee, a group, a status, a priority, and whatever custom fields you have added. Email, web form, chat, phone, WhatsApp, a social message: all of them land as the same object. That is the whole trick, and it is why a helpdesk beats a shared inbox. You cannot report on an inbox. You can report on tickets.

Comments come in two kinds. Public comments go to the customer. Internal notes stay between agents. Mixing those up is the single most common new-agent mistake, and it's worth ten minutes of training on day one.

What happens when an email arrives

Trace one message end to end and the system stops feeling abstract.

The mail lands on your support address, which is either a Zendesk address or your own domain routed to Zendesk.

Zendesk matches the sender to an existing end user, or creates one. If the message is a reply to an existing ticket, an ID hidden in the mail headers threads it onto that ticket instead of opening a new one.

A ticket is created with status New and no assignee.

Triggers fire immediately. They read the ticket and act: route it to a group, set a priority, tag it, send the customer an acknowledgement.

An SLA policy attaches, if you have one, and starts a clock on first reply.

The ticket appears in a view, which is just a saved filtered list. Views are where agents actually live.

An agent opens it, replies publicly, and sets the status. Solved when it's done, Pending when the ball is back with the customer. Days later an automation closes it for good.

The rules layer

Four things do the automating, and people mix them up constantly.

Triggers run the instant a ticket is created or updated. Event-driven. "When a ticket comes in tagged billing, assign it to Finance."

Automations run on a clock, hourly, against tickets that meet a condition. Time-driven. "If a ticket has been Pending for four days, remind the customer."

Macros do nothing on their own. An agent applies one, and it fills in a reply and sets fields in a single click.

SLA policies define target times per priority and mark tickets that are about to breach so they float to the top of a view.

The distinction that matters: triggers react to something happening, automations react to nothing happening. More on that in triggers versus automations.

Who is who

Zendesk has three kinds of people and the licence cost follows the labels.

End users are your customers. Unlimited, free, and they only ever see their own tickets.

Agents work tickets. Each one costs a seat, and that is your bill.

Administrators are agents who can also change settings.

On some plans there are light agents too, internal people who can read tickets and add private notes but never reply to a customer. They are usually free, which makes them the right home for engineers and account managers.

The rest of the suite

Support is the ticketing core. Around it sit the help centre (Guide), where your public articles and the customer portal live, messaging and chat, Talk for voice, and Explore for reporting.

You do not need all of it on day one. Most teams run email plus a help centre for a year before adding anything, and they're right to.

What it does not do on its own

Zendesk stores and routes. It doesn't think.

It won't notice that the ticket in front of an agent is the same problem as one three rows down in the queue. It won't write your help centre. It will not decide your priorities. Out of the box you get an empty, well-built machine, and the value comes entirely from the handful of triggers, views and articles you configure in the first month.

FAQ

Frequently asked questions

What does Zendesk do, for someone completely new to it?

Zendesk for beginners, explained: it collects every customer message into one queue, gives each one an owner and a status, and applies rules so the right person sees it. What does Zendesk do beyond that is mostly reporting and self-service.

How does Zendesk work if we only use email?

No. Email is the most common channel, but chat, messaging, voice, web forms and social all create the same ticket object, which is the point.

What is the difference between a view and a queue?

A view is a saved filter over all tickets. Zendesk has no separate queue object, so views do that job. Agents pick work from views unless you route with omnichannel routing.

Do customers need a Zendesk login?

Not for email. They can raise and reply to tickets without ever signing in. A login only matters if you want them browsing their ticket history in the help centre.

How long does it take to learn?

An agent is productive in an afternoon. An administrator takes a few weeks to stop breaking things with triggers.