A cashier answering phone and register at the same time needs a system, not just a faster pace. The best fix is to give the front counter a short script, a clear priority order, and a backup for busy calls.
For many independent restaurants, the phone and the register collide right when the line builds up. A cashier can only do one thing at a time. That is where an AI phone host like ROAL can help by taking orders, handling common questions, and sending tickets to the kitchen screen while your cashier stays on the guests in front of them.
Key takeaways
- A cashier should serve the guest at the register first and use a short script for phone calls.
- Forward busy calls to an AI phone host so the counter does not stall during rushes.
- Use a clean handoff process so phone orders become readable kitchen tickets.
- Keep the restaurant’s main number and test forwarding with your carrier before a busy shift.
In this post
- What should the cashier do first when the phone rings?
- How do I stop phone orders from slowing the counter?
- What phone script works when the counter is busy?
- When should I forward calls instead of letting the cashier answer?
- How does this affect labor cost and order cost?
- What does a clean handoff to the kitchen look like?
- How do I train staff without making the counter feel more crowded?
- Questions owners ask
What should the cashier do first when the phone rings?
The rule should be simple: the guest at the counter gets first attention, then the cashier handles the phone as soon as they can do it cleanly. That keeps face-to-face service steady and avoids mistakes at the register.
A short script helps. Train the cashier to say: "Hi, thanks for calling. I’m helping a guest right now. I’ll be with you in just a moment." If the line is short, they can pick up right away. If the line is long, the cashier should not try to take a full order while ringing up a pickup, bagging food, and answering questions at once.
Use this quick decision list:
- If a guest is standing at the register, finish that sale first.
- If the phone is ringing and the line is building, let it ring through to your backup.
- If the caller only needs hours, address, or parking, that can be handled fast.
- If the caller wants a full pickup or delivery order, let the phone host take it when the counter is busy.
That last point matters. ROAL can answer common questions and take orders from the restaurant’s live menu, so your cashier is not forced to choose between the line and the phone.
How do I stop phone orders from slowing the counter?
The easiest way is to separate simple calls from order calls. A cashier can answer a quick question in 20 seconds, but a full order can tie up the register, the waiting line, and the kitchen all at once.
Set up a front-counter rule like this:
- Greet the guest in front.
- Check if the caller only needs basic info.
- If the caller wants to place an order, move them to the backup line or phone host.
- Return to the register after the call is handled.
Here is a practical example. Say your cashier is ringing up a $18 lunch order and the phone rings with a $32 pickup order. If the cashier takes the call themselves, the counter line can stall. If ROAL answers, it can collect the items, sizes, modifiers, name, phone, and ready time, then send the ticket to the kitchen screen. Your cashier keeps ringing up the guests in front.
Use a note on the counter or kitchen wall:
- Cashier handles the guest standing here.
- Phone host handles order calls when we are busy.
- Manager handles complaints, catering, allergy-sensitive questions, and special escalations.
That simple split reduces stress fast.
What phone script works when the counter is busy?
The best scripts are short and repeatable. Your cashier should not sound rushed, and they should not promise more than they can do.
Try these lines:
- "Thanks for calling. I’m at the register right now. Can I get you a quick answer, or would you like to place an order?"
- "I can help with hours and address right away. For a full order, our phone host can take it for you while I’m helping the counter."
- "One moment, please. I’m finishing with a guest and then I’ll check that for you."
A quick script table can make training easier:
| Call type | Cashier response | Best next step |
|---|---|---|
| Hours or address | Give the answer right away | Keep at counter |
| Menu question | Answer if simple | Hand off if detailed |
| Pickup order | Keep the line moving | Send to phone host |
| Delivery order | Do not juggle it at the register | Send to phone host |
| Complaint or manager request | Acknowledge and escalate | Staff follow-up |
ROAL is useful here because it can speak the caller’s language, answer common questions, and hand off tricky calls to staff with a summary. That means your cashier is not forced to play phone operator all shift.
When should I forward calls instead of letting the cashier answer?
Forward calls when the front counter is busy enough that the cashier would have to split attention. That can be during lunch rush, dinner rush, weekend peaks, or whenever one person is covering both the till and the phone.
You do not need to change your main number. ROAL gives each location its own phone line automatically, and you forward your existing number to it. You can forward all calls, or only calls when busy or unanswered, depending on your carrier or phone system.
A practical setup looks like this:
- Keep the restaurant number on your sign, website, and receipts.
- Forward calls during rush periods.
- Let the cashier answer only when the floor is calm.
- Turn forwarding off any time if you want to take calls directly.
Common forwarding codes vary by carrier and plan, so confirm with your provider and test it. On many landlines and some carriers, 72 starts call forwarding and 73 turns it off. Some mobile carriers use different codes, and business VoIP systems usually set it in a web portal. The point is not the code itself; the point is having a backup when the counter is slammed.
That backup keeps the cashier focused on the guest in front of them instead of racing between two jobs.
How does this affect labor cost and order cost?
When one cashier is answering the phone and running the register, the real cost is not just labor. It is missed time, lost clarity, and orders that may be rushed or forgotten. The cost of the fix depends on how you handle phone volume.
Here is a simple example you can plug your own numbers into:
- Say your average phone order is $28.
- Say you get 40 completed phone orders in a month.
- That is $1,120 in phone order sales.
Now compare a few common options:
| Option | Common pricing pattern | What to watch |
|---|---|---|
| Delivery apps | Often about 15-30% commission per order | Can take a large cut of each ticket |
| Monthly AI phone plans | Often about $79 to $599 per location | You pay the same even when calls are light |
| Human answering services | Usually per minute or per call | Cost can rise with busy periods |
| ROAL | $0.90 per completed phone order | No monthly fee, no setup fee, no per-minute fee |
With ROAL, the charge is tied to a confirmed order that reaches the kitchen screen. Calls, questions, and test calls are free. If you want to compare it with your own setup, use your average order size and monthly call count, then plug those into the phone host cost calculator or the phone staff cost calculator.
For many owners, the key question is simple: do you want the cashier stuck between two tasks, or do you want a system that handles the phone when the line builds?
What does a clean handoff to the kitchen look like?
A cashier juggling the counter and the phone often creates messy order notes. Someone hears the order while ringing up another guest, then repeats it to the kitchen from memory. That is where mistakes creep in.
A cleaner process is:
- The caller gives the order once.
- The phone host collects items, sizes, modifiers, and notes.
- It confirms the order back to the caller.
- It collects name and phone.
- It gives a ready time.
- It sends a clean ticket to the kitchen screen.
That matters for prep flow. If a guest orders two pizzas, one with extra cheese and no onions, plus a side order and a note about parking, the kitchen should not have to decode a rushed scribble. The ticket should be readable and complete.
ROAL also skips sold-out items, so callers do not get promised something the kitchen cannot make. It does not take card numbers over the phone either. Payment still happens at pickup or however your restaurant already takes it.
A simple manager checklist:
- Review the kitchen screen every shift.
- Check that hours and menu are current.
- Make sure notes are visible.
- Keep an eye on questions that land in the inbox.
That keeps the counter calmer and the kitchen cleaner.
How do I train staff without making the counter feel more crowded?
Training works best when it is short and tied to real work. Do not hand the cashier a long manual. Give them a few lines, a priority rule, and a manager backup path.
Use this 10-minute training outline:
- Show the cashier the one-sentence rule for the phone.
- Practice the busy-time script out loud.
- Explain which calls they can answer and which should be forwarded.
- Show where kitchen tickets appear.
- Review how to escalate complaints, catering, allergies, and manager requests.
For a new hire, you can say: "If the guest is standing here, serve the guest here. If the phone is simple, answer it. If the phone is a full order during rush, let the host take it." That is easier to remember than a stack of policies.
If your team changes often, store the script where everyone can see it. A laminated card by the register works. So does a short note in the back office. You can also share a link to training for new staff to take phone orders so the manager does not have to repeat the same lesson every week.
ROAL can help reduce the amount of phone training needed because the host keeps learning from unanswered questions in the inbox. The staff answers once, and the host knows it from then on.