Zendesk,
Twelve Demos Deep
A guided tour of how a support desk really works — from your first ticket to a fully connected system. Use the arrows, or your keyboard.
Working a ticket
The ticket is the heartbeat of Zendesk. Everything starts with reading one, replying, and resolving it.
- Open a ticket from your queue.
- Check the required fields: status, priority, type, assignee.
- Write a public reply to the customer — or an internal note for your team.
- Apply a macro to drop in a consistent answer.
- Set the status and submit.
Assigning & creating tickets
Every ticket needs an owner — and sometimes you create one yourself, like logging a phone call.
- Set the assignee (who owns it) and group (which team).
- Reassign by choosing a different agent.
- To log a new request, click + Add → Ticket.
- Pick the requester, add a subject and description.
- Submit — it joins the queue like any other.
Users & organizations
People are records. Companies are records. They're linked — a relational database hiding in plain sight.
- Open an end user's profile.
- Click their organization to see everyone linked to it.
- Notice the parent → child link: org to users.
- Add a new user or organization from People.
- Use that context to resolve faster.
Tags
Small labels that quietly run the show — driving routing, follow-up, and automation.
- Open a ticket.
- Add a tag — vip, escalation, follow-up.
- See it land on the ticket.
- Tags can be added by hand or by a rule.
- Other rules watch for tags and act on them.
Handling escalations
Not a button — a judgment call. Get the urgent issue to the right person, fast, and keep everyone in the loop.
- Raise the priority (e.g., to Urgent).
- Reassign to a senior agent or group.
- Add a CC / follower to loop people in.
- Add an escalation tag.
- Leave an internal note explaining the handoff.
Creating macros
Build a reusable response once; apply it forever. The biggest single lever for speed and consistency.
- Go to Admin Center → Workspaces → Macros.
- Click Add macro.
- Name it and write the comment.
- Add actions — set status, add a tag, set priority.
- Save, then apply it on any ticket.
Triggers & SLAs
Automate "when this happens, do that" — and let Zendesk track the promises you make to customers.
- Go to Admin Center → Business rules → Triggers.
- Set conditions — when a VIP ticket is created.
- Set actions — then set priority High, add a tag.
- Add an SLA policy with a first-reply target.
- Zendesk enforces it automatically.
Views
Saved, filtered lists — the lens each agent looks through. Good views are the difference between calm and chaos.
- Go to Views in the sidebar (or Admin Center).
- Click Add view.
- Set filters — Status = Open and Priority = Urgent.
- Choose columns and grouping.
- Save — it becomes a shared work queue.
Bulk import by CSV
The relational database at scale: load hundreds of records in two files instead of hundreds of forms.
- Go to Admin Center → Tools → Data importer.
- Import organizations first.
- Then import users — they link to those orgs.
- Map the fields and start the import.
- Find your new roster in People.
An AI chatbot on the website
A front door that answers the easy questions and opens a ticket — with full context — for the rest.
- Go to Admin Center → Channels → Messaging.
- Turn on the Web Widget and configure the bot.
- Add the answers and flows it should handle.
- Embed the snippet on your website.
- When it can't help, it opens a ticket automatically.
Gmail into Zendesk
Turn every support email into a tracked ticket — and meet OAuth, the secure handshake between apps.
- Go to Admin Center → Channels → Email.
- Add your address and connect Gmail with Google sign-in (OAuth).
- Send a test email.
- Watch it become a ticket in about a minute.
- Reply from Zendesk — the whole thread is tracked.
APIs, webhooks & Zapier
No software is an island. One event in Zendesk can fan out to every other tool you use.
- Pick an event — a ticket tagged urgent.
- A webhook / Zap fires automatically.
- It posts an alert to Slack.
- It logs a row in Google Sheets.
- One event, many tools — all through their APIs.
You just ran the desk.
From a single ticket to a connected system — Gmail, Slack, Sheets, and a website bot, all talking through APIs. That's support as an operation, not just an inbox.