Guide · Helpdesk
Ticket categories that route themselves
In short
Good ticket categories describe what the customer needs, not how your company is organised. Keep the top level short, add subcategories that say what to do, let the customer pick one where they ask, and give each category a team and a priority. Then most tickets reach the right person before anyone sorts them.
Reviewed 9 November 2026. Terms used: Ticketing system, Shared inbox vs helpdesk, SLA (service level agreement).
How to design categories that route
Do it on paper first, with a week of real tickets beside you.
Start from what customers ask
Sort a week of tickets into piles by what the customer wanted. The piles are your first draft. A category nobody’s ticket fits is one you can drop.
Keep the top level short, and add one level below
A customer choosing from a form or a menu should see a short list they can read at a glance. Put the detail in subcategories, where it tells the team what to do.
Two levels for a furniture shop Delivery › Late delivery · Damaged on arrival · Change of address
Warranty › Repair visit · Spare parts
Orders › Change an order · Cancel
Payments › Refunds · Invoices
General
Let the customer choose where they ask
Offer the top-level categories as the topics on your support form and the options in your chatbot menu, worded the way a customer would say them. The category is then set before the ticket exists.
Give each category a team and a priority
Write the routing down as rules: Delivery goes to the delivery team, Warranty to warranty and repairs, anything damaged on arrival is high priority. Rules on a parent category should cover its subcategories, so you don’t repeat them.
Ask for the right details per category
A delivery question needs an order number; a repair visit needs a photo and an address. Make those fields required for that category only, so customers aren’t asked for things that don’t apply.
Keep a catch-all, and read it every week
Some tickets won’t fit. Send them to “General”, owned by one team, and look through it weekly. If the same kind of ticket keeps landing there, it needs a category of its own.
Change categories carefully
Report by category to see what customers struggle with most, and write help articles for the top ones. When a category stops being useful, archive it rather than deleting it, so old tickets and reports keep their history.
How it works in Axonave
A category tree that sets the team before anyone looks.
Axonave tickets have your own categories with subcategories, three levels by default. The support form offers the categories you choose and asks the fields each one needs, and the chatbot’s Leave a message step sets one too. Assignment rules by category, priority, source and team give the ticket its team and skills, and a rule on a category covers everything under it. Reports → Tickets rolls categories up by level.
- Round robin or fewest open tickets, with a cap per agent
- Held after hours, then assigned when you open
- Archive a category; tickets keep it
Teras Home’s tickets in our demo workspace, each with its category and subcategory (Warranty › Repair visit, Delivery › Damaged on arrival) and the team its rules gave it.
Common questions
How many ticket categories should we have?
As few at the top as a customer can choose from at a glance, with subcategories for the detail. If agents keep re-categorising tickets, the categories are wrong; if “General” is full, one is missing.
Should customers choose the category, or agents?
Customers, where they ask, in their own words: it routes the ticket straight away. Agents can still change it, and in Axonave the assignment rules use whatever the ticket has.
Can we change categories later without breaking reports?
Yes. In Axonave you can rename your own categories, move them in the tree and archive the ones you no longer use; tickets keep the category they had, and reports can still filter by it.
See it working with your own customers.
We reply within one business day by email or WhatsApp.