Customer Support
Customer Support Scheduling
This guide shows how to build an AI support agent that handles most tickets autonomously but escalates complex issues — billing disputes, technical troubleshooting, account recovery — to a human callback.
The problem
Your AI support agent resolves 80% of tickets. But the other 20% need a human. Today, the agent says “a team member will reach out” and the customer waits. Sometimes for hours. Sometimes they never hear back.
With Slotflow, the agent books a specific callback time while the customer is still engaged. The customer knows exactly when they’ll get help. No uncertainty, no ghosting.
Architecture
Setup
1. Create your support team
2. Set staggered availability
Support teams often have overlapping shifts for coverage:
Agent escalation flow
The core function your agent calls when escalating a ticket:
Booking the selected slot
After the customer picks a time:
Webhook handler for support system
Cross-timezone handling
When your support reps span multiple timezones, Slotflow handles it automatically. Each human has their own timezone — the slot engine computes availability in their local time and returns slots in UTC.
Your agent just needs to present times in the customer’s preferred format:
Cancellation flow
If a customer needs to cancel, your agent can free up the slot:
The slot becomes immediately available for other customers.
Key takeaways
- Route by issue type — billing issues to billing specialists, technical issues to engineers
- Use short durations — 15-minute callbacks for quick issues, 30-minute for complex ones
- Pass ticket context in metadata — your webhook handler has everything it needs to update the support system
- Offer multiple time slots — let the customer choose from 2-3 options
- Handle slot conflicts — re-query slots if the customer’s chosen time was already booked