Sorting support requests: give every case an owner
Requests from different channels can be grouped and assigned, while refunds, promises and unclear messages stay with a person who can decide.

The workflow illustrates a possible design and is not a client case study.
- Group enquiries
- Suggest routing
- Assign an owner
Receiving a message is only the start
A customer sends the same question by email and chat. Two tickets appear, but nobody is clearly responsible for answering. Automatic classification can help route them; it cannot, by itself, authorise a refund or a promise to the customer. Each case still needs a person responsible for the reply.
Check the tools already in your support platform
Check the routing, categories and response rules already available in Zendesk or your current help desk. Add AI where it helps with varied messages, and test its suggestions against real examples before using them to assign work.
Route a few common enquiry types
Choose two or three common request types. Keep the original message with the ticket, suggest a category and assign a person to handle it. Make uncertain cases easy to find for review. Use approved wording for automatic acknowledgements, with separate approval for actions such as refunds.
Will staff notice incorrect routing?
Try messages with mixed languages, sarcasm or a missing order number, then duplicate requests and reassignment. Check overdue replies too. Staff should be able to read the original message, correct the category and take over without losing track of the case.
Bring representative support messages
Bring representative messages with personal details removed, your categories, escalation rules and the channels staff use. Include examples that experienced staff find difficult to classify.