Skip to main content
Customer support automation handles high-volume, repetitive queries at low cost - order status, return policies, FAQs, basic troubleshooting. The key constraint is cost: support tickets can be in the thousands per day, and each one needs to be cheap. Savings on this workload: typically 70–80% vs Claude Sonnet 4.6 baseline.

Step 1 - Create the profile

  1. Go to Playground → Configure
  2. Name it Support Bot
  3. Set tier floor: LIGHT, ceiling: STANDARD
  4. Set cost cap: $0.01
  5. Enable Tool calling if the bot calls APIs (order lookup, account fetch)
  6. Click Save & get API key

Step 2 - Integrate the profile

Node.js - with order lookup tool

Python


How routing looks for support tasks

The cost cap of $0.01 means even if a ticket escalates to STANDARD, you’ll never pay more than $0.01 for a single response. Routor will truncate model selection to stay within the cap.

Handling escalation

For tickets that need a human, detect the intent and route accordingly in your application logic:

Cost estimate

On a support system handling 5,000 tickets/day:

Tips

  • Set max_tokens to 400–600 for support responses - they should be concise, not essays. This also reduces cost.
  • Use a system prompt with explicit guidelines so lighter models can follow your company voice without needing a smarter model to infer it.
  • Pre-filter by intent before calling Routor - if a ticket is clearly “track order,” you can skip the LLM entirely and return a templated response.
  • Monitor the cost cap - if you hit the cap frequently, consider raising the ceiling to COMPLEX for edge cases.