Recommended Profile Settings
Step 1 - Create the profile
- Go to Playground → Configure
- Name it
Support Bot - Set tier floor: LIGHT, ceiling: STANDARD
- Set cost cap: $0.01
- Enable Tool calling if the bot calls APIs (order lookup, account fetch)
- 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_tokensto 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.