AutomationIntermediate

How to Auto-Categorize and Route Support Tickets with AI and Paths

Let an AI step tag each incoming ticket so Zapier Paths sends it to the right team automatically.

9 minIntermediate

Manually sorting incoming support requests wastes time. Here you will have an AI step classify each ticket into a category like Billing, Bug, or Sales, then use Zapier Paths to branch the workflow so each category reaches the right channel or owner.

What you need

  • A Zapier plan that includes Paths (Professional or higher)
  • A ticket source: a shared inbox, a form, or a help desk app
  • Destinations such as Slack channels or assignees
  • An AI option (AI by Zapier or your own key)

Step 1: Trigger on a new ticket

Pick the trigger that matches where tickets arrive, for example Gmail New Email or a form New Entry. Connect and test so you have a real ticket sample with subject and body fields available.

Step 2: Classify with a constrained prompt

Ask the AI to return exactly one category word from a fixed list. Constraining the output to a known set is what makes the next Paths step reliable, since Paths matches on exact text.

Classifier prompt
Classify this support message into exactly ONE of:
Billing, Bug, Sales, Other

Reply with only that single word, nothing else.

Subject: {{Subject}}
Message: {{Body Plain}}
AI step output
Prompt sent...
Output:
Billing
A single clean label the Paths step can match on.

Step 3: Add Paths and set rules

Add a Paths step. Create one path per category. In each path's rule, set the condition to the AI output field Exactly matches the category word. This is where the constrained output pays off.

Zapier - Paths rules
Path A: AI Category (Exactly) = Billing -> #billing
Path B: AI Category (Exactly) = Bug -> #engineering
Path C: AI Category (Exactly) = Sales -> #sales
Path D: AI Category (Exactly) = Other -> #triage
Each path matches one exact AI label.

Step 4: Add an action to each path

Inside each path, add a Slack Send Channel Message action (or assign in your help desk) pointed at the right team. Include the original ticket text so the receiving team has full context.

Always handle Other
Give the model an Other category and a path for it. Without a catch-all, tickets the model is unsure about can silently fall through and never reach anyone.

Example: A message asking about a double charge gets labeled Billing, Paths matches that exact word, and the ticket lands in the #billing channel within seconds, no human sorting required.

Watch related tutorials

Tags
#zapier#ai#paths#support#routing