Restaurant labor cost control without hurting service

Start with the hours when the phone causes the most drag. For many independent spots, that is dinner rush, weekends, and the last hour before close. The hidden cost is not only the person answering the phone. It is the interruption to the cook, cashier, or manager who gets pulled away every few minutes.

Use this simple check for one week:

1. Write down each time someone leaves a task to answer the phone.
2. Mark whether the call was an order, a question, a reservation, a complaint, or a wrong number.
3. Note who answered it and what work they stopped doing.
4. At the end of the week, circle the calls that did not need a manager.

Example: say your shift lead makes $22 an hour and spends 45 minutes total on routine calls during a busy dinner. That is $16.50 in labor for one shift just on phone interruptions. Plug in your own wage and minutes. The point is not the exact number. The point is to see where your labor cost is leaking.

Not every call belongs to the same person. A clear split protects service and lowers labor pressure. A phone host should handle the repeatable stuff. Staff should handle the edge cases.

Use a quick call map like this:

A useful script for staff is: “I can help with the order, but for that question I’m going to hand you to the team.” That keeps the caller from feeling bounced around. ROAL can also pass messy calls to staff with a summary, which saves the team from repeating the basics back to the caller.

Call forwarding is one of the simplest ways to stop the phone from stealing labor during rushes. You keep your restaurant number. You route calls where they need to go. And you can turn forwarding off any time.

Common setup paths look like this:

1. On many landlines and some carriers, dial 72 and then the forwarding number to forward all calls, and 73 to turn it off.
2. On many GSM mobile carriers, *21number# can forward all calls and ##21# can turn it off.
3. On some carriers, *61number# forwards unanswered calls and *67number# forwards busy calls.
4. Verizon Wireless often uses 72 / 73, and *71 for busy or no-answer forwarding.
5. Business VoIP systems usually set forwarding in the web portal.

Codes vary by carrier and plan, so confirm with your carrier and test with a real call. For owner-friendly reference, keep Call forwarding codes by carrier bookmarked.

This matters for labor because you can forward only when busy or unanswered instead of staffing a dedicated phone person all shift. That lets the host stand, counter, or kitchen team stay focused on guests and tickets.

A good phone script saves time because it prevents back-and-forth. It should collect the order, the name, the phone number, and the ready time in one pass. Keep it short. Keep it specific to your menu.

Here is a simple script line you can adapt:

"Thanks for calling. I can take your pickup order now. What would you like, and are there any sizes, modifiers, or notes?"

Then move in this order:

1. Take items.
2. Confirm sizes and modifiers.
3. Ask for the caller’s name and phone.
4. Quote the ready time.
5. Repeat the order back once.

That flow reduces labor because the employee is not asking the same question three times. It also lowers mistakes that create remakes, refunds, and extra kitchen work. If you use ROAL, it follows this kind of flow automatically on the phone, speaks the caller’s language, and does not take card numbers over the phone. Payment happens at pickup or however your restaurant already takes it.

A lot of owners compare phone labor to delivery app commission and see that both can get expensive. Delivery apps commonly charge roughly 15-30% commission per order. Phone labor may not look as obvious, but it adds up when a staff member is paid to answer calls instead of serving guests or cooking.

Here is a simple comparison you can swap for your own numbers:

• Say your average phone order is $28.
• Say your labor cost for handling and interrupting work is $4 per order in real time and distractions.
• Say a delivery app would take 20% on that order, or $5.60.

In that example, the delivery app commission is higher. But the phone still costs something, especially if your team is stretched thin. The goal is not to pretend one cost disappears. The goal is to choose the cheaper way to capture the order while protecting service.

ROAL’s pricing is different from monthly phone tools. It charges $0.90 per completed phone order, with no monthly fee, no setup fee, no per-minute fee, and no contract. For owners who want to compare the options, AI phone host vs hiring phone staff and Pay per order vs monthly AI phone plans are useful starting points.

Short-staffed shifts are where labor control and service usually collide. The trick is to protect the human team from routine calls so they can handle the floor, the line, and the problem calls that need judgment.

A simple short-staffed checklist:

• Forward the restaurant number to the phone host during rushes.
• Make sure the live menu is current, including sold-out items.
• Set a clear policy for allergy-sensitive questions and complaints.
• Decide who handles manager requests.
• Keep a quick way to review call history and tickets after the rush.

That is where the ROAL dashboard helps. It shows live tickets on the kitchen screen, call history with transcripts and recordings, a menu editor, hours, FAQs, upsell suggestions, and multi-location menus. That means the team can check what was ordered without digging through notes while the line is busy.

If your shift is so tight that the phone keeps breaking the flow, Short-staffed shifts is the right companion read. For owners who want to try a setup from their own site or menu, build a free test host.