Shopify
Stripe
Slack
Notion
Google Workspace
Confluence
How Do Tags Work in Zendesk? A Complete Guide to Zendesk Tags (2026)
Zendesk tags are exact labels that reach a ticket six ways, from an agent typing them to automatic tagging, and the same tag then drives triggers, SLAs, views and Explore reports. Get the spelling consistent and your automation works; let tags sprawl and it quietly misses tickets.
Key takeaways
- Zendesk tags reach a ticket six ways: typed by agents, added by custom fields, macros or business rules, copied from user and organization tags, or picked by automatic ticket tagging.
- The Zendesk Tags field holds up to 5,096 characters, and tags may use only letters, numbers, dash, underscore, colon and forward slash.
- Zendesk treats refund-request, refund_request and refund/request as three different tags, so one team-wide casing and separator keeps triggers and reports aligned.
- User and organization tags are copied onto a Zendesk ticket only when it is created, unless someone later changes the ticket's requester or organization.
- Zendesk discontinued the Tag Locker app on 29 August 2024, so custom-role tag permissions and drop-down fields now keep agents on an approved tag set.
Zendesk tags are exact labels (letters, numbers, dash, underscore, colon and forward slash, up to 5,096 characters per ticket) that reach a ticket six ways: an agent types them, a custom field, macro or business rule adds them, the requester's user or organization tags are copied in, or automatic ticket tagging picks the top three matches. Once on the ticket, the same tag is read by triggers, automations, SLA policies, views, search and Explore. Everything below is checked against Zendesk's own documentation.
| How the tag gets on | Who decides | Consistency |
|---|---|---|
| Typed by an agent | The agent | Lowest: depends on spelling |
| Drop-down, multi-select or checkbox field | The field's predefined values | Highest: one canonical tag per value |
| Macro | Agent chooses when, macro fixes what | High |
| Trigger or automation | Your rule conditions | High |
| User and organization tags | The requester's profile, at ticket creation | High, but never retroactive |
| Automatic ticket tagging | Word matches in the first description | Low: keyword-based, top three matches |
What is a tag in Zendesk?
A tag is a word, or a combination of words, that you attach to a record to add context. In Zendesk you can tag three kinds of records: tickets, users and organizations (Help Center topics can be tagged too). Most of the action happens on tickets, where tags sit in a dedicated Tags field in the ticket's properties panel.
Tags matter because they're machine-readable labels. A free-text note is for a colleague; a tag is a value your business rules, views, search and reports can match exactly. A ticket tagged refund can be routed, escalated, counted and reported on without anyone reading the conversation. Tags are how you teach Zendesk to recognize categories that don't have a dedicated field of their own.
A few mechanics worth knowing up front. The Tags field accepts up to 5,096 characters in total, so you're unlikely to hit a ceiling. Tags can contain only letters, numbers and four connector characters: dash, underscore, colon and forward slash. Characters like #, @ and ! are rejected. And the connectors are not interchangeable: refund-request, refund_request and refund/request are three different tags to Zendesk. Consistency is a requirement, not a nicety.
How does a tag get onto a Zendesk ticket?
Tags arrive from more directions than most admins realize. Knowing each path is the difference between a tidy taxonomy and a pile of labels nobody remembers creating.
1. Manually, by an agent
The simplest route: an agent types into the Tags field (multiple tags are separated by spaces) and removes one by clicking the small x next to it. This suits ad-hoc judgment calls like flagging a ticket vip or legal_review, but it's also the least consistent path, because it relies on every agent spelling the same concept the same way every time. Agents in custom roles can add and remove tags only if their role allows it, so tag editing is itself a permission you control.
2. Automatically, from custom fields
This is the cleanest way to get consistent tags, and most teams underuse it. Certain custom field types attach a tag whenever a value is selected:
- A drop-down field pairs every option with a tag (each option has a display title and a tag); pick "Refund" and the ticket quietly gains
refund. - A multi-select field does the same for each chosen value, so one field can apply several tags at once.
- A checkbox field applies one admin-defined tag when it's ticked.
Text, numeric, decimal, date, regex, credit-card and lookup fields do not generate tags. The payoff of field-driven tags is uniformity: because the values are predefined, you never get Refund, refunds and refund_ competing in your reports. The field produces one canonical tag every time.
3. Via macros
A macro is a one-click bundle of actions an agent applies manually, and one of those actions can add or remove tags. A "Close as spam" macro might post a reply, set the status and stamp spam in a single click. The agent decides when; the macro guarantees what.
4. Via triggers and automations
Tags can be applied without anyone touching the ticket. Triggers, automations and the other business rules can add tags as an action: a trigger might tag every ticket from your billing address billing the moment it's created, while a time-based automation might add aging to anything left Pending for three days. This is where tagging becomes a system rather than a habit.
5. From user and organization tags
You can tag the people and companies in your account, not just tickets. Tags on a user or organization profile can be added manually, through a bulk import, via the API, or through enterprise SSO (JWT or SAML). When the feature is enabled, those tags are copied onto the user's tickets automatically. Tag an organization premium and a contact manager, and a ticket that person opens arrives carrying both.
The caveat that trips up nearly everyone: user and organization tags are applied only when a ticket is created, not when it's updated, and never retroactively. Tag a customer vip today and only their future tickets inherit it. The one exception is changing a ticket's requester or organization: Zendesk then removes the old requester's or organization's tags and adds the new ones.
6. Automatic ticket tagging
Zendesk has a built-in setting called automatic ticket tagging. When it's on, Zendesk scans the description of each new incoming ticket, looks at words longer than two characters, compares them to tags you've already used, and adds the top three matches. Two limits from the setting's help article: it only runs on tickets end users submit through your channels (an agent creating a ticket inside Support gets no automatic tags, though one created by email does), and it may not work in languages other than English. It keys off raw word matches, not meaning, but it can seed routing rules with no manual effort.
AI classification raises the bar here, which we come back to below.
What do tags control in Zendesk?
Adding tags is only half the story. Tags earn their keep because almost every organizing feature in Zendesk can read them.
- Business rules. Tags are first-class conditions in triggers, automations and SLA policies. "If tags contain
urgent_vip, set priority to Urgent and notify the on-call group." "Apply the 1-hour first-reply SLA when the ticket is taggedenterprise." Because a tag is an exact value, these conditions are reliable in a way that scanning subject lines never is. - Views. A view is a saved, filtered list of tickets: your queues. Add a Tags condition with "Contains at least one of the following" and you have a live queue of, say, every
escalationticket across all groups. Tag-based views let teams carve out specialized work without inventing new fields. - Search. Agents can find tickets with the
tags:search operator.tags:refundreturns every ticket carrying that exact tag, so spelling counts here too. - Explore reporting. In Explore, tags are a reporting attribute: you can slice volume, resolution time and satisfaction by tag to answer "how many
bugtickets did we get last month, and how long did they take?" A disciplined tag set becomes a free analytics dimension.
Every one of these features reads the same labels. A tag applied by a drop-down field is the identical value a trigger matches, a view filters on and Explore counts. That shared vocabulary is why consistency matters so much.
Where are the tag settings in Admin Center?
Tagging is governed in Admin Center → Objects and rules → Tickets → Settings → Tags, where two switches live:
- Allow tags on tickets: the master toggle. Turning it off disables the Tags field entirely.
- Turn on automatic ticket tagging: enables the description-scanning behavior described above.
By default Zendesk lets agents create any tag on the fly, which is flexible and is also how sprawl begins. Older guides point to the Tag Locker app for restricting agents to an approved list. Zendesk discontinued Tag Locker on 29 August 2024 and it can no longer be installed. The native control today is the custom-role permission for adding and removing tags; for finite categories, a drop-down field does the restricting for you, because agents pick from its values instead of typing.
(The tags admin screens sit behind a Zendesk login and the layout shifts as Zendesk updates its UI, so confirm the path in your own Admin Center.)
How should you name and organize tags?
Tags fail quietly. Nothing breaks the day you create a sloppy one. It breaks months later when a report undercounts or a trigger misses.
- Design a deliberate taxonomy. Decide which categories you need before you start tagging: reasons (
billing,bug,how_to), segments (vip,enterprise) and workflow states (escalation,awaiting_legal). A planned vocabulary of a few dozen meaningful tags beats a thousand accidental ones. - Pick one casing and one separator, forever. The usual convention is lowercase with underscores (
shipping_delay, notShipping Delayorshipping-delay). Because Zendesk treats different separators as different tags, choosing one and sticking to it keeps your labels aligned. - Prefer field-driven tags over typed ones. Wherever a category is finite, capture it with a drop-down or checkbox field so the tag is generated identically every time. Keep free-typed tags for genuinely ad-hoc flags.
- Document them. Keep a short shared list of every approved tag and what it means. New agents shouldn't have to guess between
refundandrefunds.
What is tag sprawl, and why does it break reports?
Tag sprawl is the slow build-up of near-duplicate, one-off tags. refund, Refund, refunds, refund_request and refund-req look the same to a human and are five different things to Zendesk. The damage is invisible: a trigger keyed to refund ignores the tickets tagged refunds, and an Explore report splits one real category across five columns, so your numbers are wrong without anyone noticing. Sprawl is far easier to prevent (a taxonomy, field-driven tags and tighter tag permissions) than to clean up afterwards.
Can AI tag Zendesk tickets by intent?
Manual and rule-based tagging both depend on a human typing the right label or building a rule for every case, which is where consistency leaks. Zendesk's automatic tagging helps, but it matches words, not intent, so it's only as good as the literal words a customer happens to use.
This is one of the cleaner jobs for an AI agent layer like Macha, which sits on top of your existing Zendesk rather than replacing it. It reads the meaning of a ticket, classifies by intent and applies your canonical tags consistently, recognizing that "where's my order," "hasn't arrived" and "tracking says delivered but it's not here" all belong in shipping_status. That feeds straight back into the triggers, views, SLAs and reports above. The trade-offs: it's another integration to manage, and it only tags as well as the taxonomy you give it. Macha bills per ticket, one conversation charged once whether the agent only tags it or goes on to answer it, starting at $299 a month for 750 tickets with setup and monitoring by the Macha team included. You can try it with $50 of free usage, no credit card required.
Frequently asked questions
What are tags in Zendesk? Tags are words or combinations of words you attach to tickets, users and organizations to add context. Because they're exact, machine-readable values, they drive triggers, automations, SLAs, views, search and Explore reports without anyone having to read the ticket.
How do I add a tag to a Zendesk ticket? Type it into the Tags field on the ticket, separating multiple tags with spaces, and remove one by clicking the x beside it. Tags are also added by drop-down, multi-select and checkbox custom fields; by macros, triggers and automations; by user and organization tags; and by automatic ticket tagging.
Do Zendesk custom fields create tags? Some do. Drop-down and multi-select fields attach a tag for each selected value, and a checkbox field applies one admin-defined tag when ticked. Text, numeric, decimal, date, regex, credit-card and lookup fields don't. See Zendesk custom fields explained.
How do user and organization tags work? You tag user and organization records manually, by import, via the API or through SSO. With the feature enabled, those tags are copied onto the user's tickets only when a ticket is created, never retroactively. Changing a ticket's requester or organization swaps the old tags for the new ones.
What is automatic ticket tagging in Zendesk? A setting that scans the description of each new end-user ticket for words longer than two characters, compares them to tags you've already used, and adds the top three matches. It's keyword-based, may not work outside English, and doesn't understand intent the way an AI classifier does.
How do I prevent tag sprawl? Plan a small, deliberate taxonomy; standardize on one casing and separator (lowercase_with_underscores); generate tags from custom fields wherever the category is finite; document your approved tags; and limit who can add tags through custom-role permissions.
Is the Tag Locker app still available? No. Zendesk discontinued Tag Locker on 29 August 2024. Use custom-role tag permissions and drop-down fields to keep agents on an approved set.
From here, go deeper on the things that generate and consume tags: custom fields, macros and business rules.
Tag mechanics checked against Zendesk's help center on 24 September 2026. Zendesk updates its product periodically, so confirm specifics in your own account before relying on them.
