On this page
A call flow is the set of decisions made between the phone ringing and the caller hanging up. Who or what answers. What the caller can get done without waiting. When a person takes over, and what happens if that person is busy.
Call centres draw these as diagrams with dozens of branches. A restaurant needs something far smaller, but it still needs deciding on purpose — because the default call flow of most small restaurants is “whoever is nearest picks up, if they can”, and that flow fails at exactly the moments the phone matters most.
Key takeaways
- Most calls to a restaurant are one of five requests. Design for those first.
- Decide in advance which calls must reach a person: allergies, complaints, anything involving money already taken.
- Every handoff needs a fallback. A transfer to a phone nobody answers is worse than no transfer at all.
- Read real calls. A call flow designed from memory describes the calls you remember, not the ones you get.
What a call flow is
A call flow is a map of routes. Each route starts with what the caller wants and ends in an outcome: a booking made, a question answered, a person reached. The design question for every route is the same — what is the fastest correct outcome, and who or what can deliver it?
Older phone systems answered that with a menu — press 1 for bookings — because they could not understand speech. A conversational receptionist skips the menu: the caller says what they want and the flow branches on meaning rather than a keypress. The routes still have to be designed. Only the way a caller chooses between them has changed.
Start with the calls you actually get
Before drawing anything, list your calls. A week of tally marks by the phone works; so does reading call transcripts if you have them. Most restaurants find the same short list:
| Call | What the caller says | Fastest correct outcome |
|---|---|---|
| New booking | “Table for four at seven?” | Booked on the call |
| Change or cancel | “We’re six now, not four” | Changed on the call |
| Fixed question | Hours, the menu, parking | Answered on the call |
| Running late | “Can you hold our table?” | Noted against the booking |
| Needs judgement | An allergy question, a complaint | A person, quickly |
The first three rows are usually most of the calls, and their answers live in a system: the book, the menu, the hours. Those are the routes to automate. The last row is the one to protect.
Map each route in four steps
Name the request
Write it in the caller’s words, not your menu’s. Callers ask whether you have “anything gluten-free”, not for a section of the menu by its name.
Name the source of truth
Where does the correct answer live? The book for openings, the menu for prices, the policy for large parties. If it only lives in someone’s head, write it down first.
Decide who delivers it
The receptionist, a person, or the receptionist first with a person behind it.
Decide what happens when it fails
No opening that suits. A person who does not pick up. A question with no written answer.
Handoffs: when a call should reach a person
The most important decision is the list of calls software should never finish. Keep it short and specific:
- Allergies and health questions. The caller is asking about safety, and the answer depends on today’s kitchen.
- Complaints. An upset caller wants to be heard by someone who can put it right.
- Money already taken. Refunds, disputed charges, deposits.
- Anyone who asks for a person. When a caller asks for a person, that request is the route.
Each handoff has two parts: the transfer itself, and what happens when nobody picks up. A caller transferred to a ringing phone in an empty back room has been dropped, with extra steps.
Busy hours and closed hours
Time is a branch in every call flow. The same request can deserve a different route at 11 AM and at 9 PM:
- Open and quiet. Staff can answer; a receptionist catches the overflow.
- Open and busy. The lunch or dinner rush, a full floor. Every call answered by software is a person not pulled away from a customer.
- Closed. Nobody can answer, but tomorrow can still be booked. This is where most of the lost bookings are.
Two rules keep time-based routing honest: nothing should ever book a time you are closed, and your hours must match everywhere a guest can read them.
How SeasonX fits into a call flow
SeasonX’s receptionist handles the first three routes directly — bookings, changes and fixed questions — against your live book and your menu. The rest is set in the dashboard:
- When it answers. Under When should the AI answer?, choose Always on, Business hours only, or After-hours only.
- Live call transfer. Switch on Live call transfer and set the number calls should go to. The receptionist tells the caller it is transferring them before it does.
- A fallback for failed transfers. Add a business phone, and a caller whose transfer does not connect is given that number to call.
- Every call on record. The Calls tab keeps a transcript of each call, searchable by phone number or by words, so you can check your routes against what really happened.
The setup steps are in the help center: set up live call transfer and choose when the AI answers.
Questions
A call flow is the set of rules that decides what happens to each incoming call: who or what answers, what the caller can do without waiting, when the call is handed to a person, and what happens if nobody is available.