You are helping me build the following AI agent workflow.

## Goal
Auto-Categorize Support Tickets: New Zenes tickets auto-sort instantly into Sales, Engineering, or Customer Support buckets.

## Specification
- What it does: Sort incoming Zenes tickets automatically into three specific buckets: Sales, Engineering, or Customer Support. This saves manual sorting time and ensures every request reaches the correct team immediately upon arrival.
- Trigger: Triggered by an event (Event · on new Zenes ticket)
- Autonomy: Fully hands-off
- Expected setup effort: under an hour
- Tools/services involved:
  - Zenes: ticket ingestion source
  - LLM: classify ticket intent into Sales, Engineering, or Support buckets

## Known pitfalls, handle each one explicitly in your implementation
1. Costs will spike if you process every raw character of long tickets, truncate input text to a reasonable token limit before sending.
2. Ambiguous requests like general inquiries may get misclassified, so implement a human-in-the-loop review step for low-confidence scores.

## Reference implementation
https://www.youtube.com/watch?v=4fgqkZi8CEY (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/auto-categorize-support-tickets/ via usecasesforagents.com