Zendesk Ticket Tagging and Reason Taxonomy
Design tags and reasons that support reporting.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a ticket tagging scheme for Zendesk. Ticket categories we see: [CATEGORIES]. Questions leadership asks: [LEADERSHIP_QUESTIONS]. Current tag problems: [TAG_PROBLEMS]. Keep the list short enough to fit in a dropdown, no more than 30 reasons. Provide an indented two-level taxonomy with a controlled list of contact reasons, product areas and outcomes, each with a definition and a typical example ticket, and a tiebreak rule for tickets fitting two reasons. Apply them with ticket fields (dropdowns) rather than free-text tags where possible [VERIFY]. Give agent rules, a mapping table from old tags (flagging those that cannot be mapped), and the reports each question needs (including the top five reasons by count with arithmetic). Agreement test: two people classify the same ten tickets, count matches, and compute the percentage; below 80 percent means the definitions need work. Review misc or other usage monthly. Ask me for a sample of ten real ticket subjects if I did not provide them, and use them to test the taxonomy. Say which five reasons will probably carry most tickets, so the list can be piloted first.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.