What it means
Tags are the data layer that makes support analytics meaningful. Without consistent tagging, ticket volume is just a number — with tagging, you can see exactly what your customers are asking about and where issues are concentrating.
Tags are short labels attached to tickets that describe their content: 'order-status', 'return-request', 'damaged-item', 'discount-code', 'cancel-order', 'product-question'. Tags can be applied manually by agents, automatically by rules (if ticket contains 'track' → apply 'tracking'), or by AI (which reads the full conversation and applies the most accurate classification). A clean, consistent tag taxonomy is foundational for support analytics. When every return request carries the 'return-request' tag, you can track return inquiry volume over time, correlate it with product return rates, and measure the impact of a policy change. Without consistent tagging, those analyses are impossible. For Shopify brands, the tag taxonomy should reflect the actual distribution of ticket types in the store's queue. A typical ecommerce tag set includes: WISMO/tracking, return-request, exchange-request, refund-status, order-modification, product-question, discount-shipping, general-feedback, and escalation. Keeping the taxonomy under 20 primary tags maintains usability — overly granular tag sets lead to inconsistent application. AI auto-tagging dramatically improves tag consistency by applying classifications at ticket creation without relying on agents to remember to tag. Agents who are focused on resolution frequently skip tagging; AI never does.
Why it matters
Tags are the bridge between individual ticket handling and operational intelligence. They enable topic-level routing, segment-level CSAT analysis, trend detection for emerging issues, and accurate volume reporting by category. For stores managing BFCM preparation, tag trends in August and September often reveal which topics will spike and where to pre-position AI training.
How Bookbag helps
AI auto-tagging at ticket creation
Bookbag applies tags automatically when a ticket arrives, classifying it by topic before an agent sees it — ensuring 100% tagging coverage without agent effort.
Tag-based routing and filtering
Use tags as routing conditions (return requests → returns queue) and as inbox filters so agents work the ticket types most relevant to their role.
Tag trend analytics
Bookbag's analytics surface tag volume trends over time, letting you spot rising issue categories early and respond before they become backlogs.
Related terms
Frequently Asked Questions
See Bookbag in action
Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.