What a restaurant answering service costs

Most restaurant answering services use one of three pricing models.

• Per minute: common with human answering services.
• Per call: some services bill for each answered call or each handled call.
• Monthly fee: many AI phone tools charge a fixed monthly amount per location, often roughly $79 to $599 whether or not orders come in.

Here is a simple way to think about it:

For owners, the key number is not the monthly sticker. It is the cost of one real order that reaches the kitchen. If you get lots of menu questions, reservation requests, or wrong-number calls, paying for every minute can feel expensive fast. If your phone is often busy at dinner, a flat monthly plan can feel simpler, but you still pay even when the phone is quiet. That is why many owners compare services by what a finished phone order actually costs, not by the headline price.

Use one busy week as your test. Count the calls that mattered, then plug in your own numbers.

Say you take 120 calls in a week and 40 become completed orders. If a service charges by the minute, the bill depends on how long each order call runs. If it charges by the call, the bill depends on every handled order. If it charges a monthly fee, you pay the same amount whether those orders come in or not.

A simple comparison worksheet:

1. Write down how many calls came in.
2. Write down how many became orders.
3. Estimate average call time for each order.
4. Add any monthly base fee.
5. Divide the total by completed orders.

Example you can swap for your own:

• Say your average order call is 4 minutes.
• Say you have 40 completed orders in a month.
• A per-minute service can grow quickly if calls run long.
• A monthly plan might look easier, but you still pay during slow periods.

If you want a deeper pricing breakdown, see per-minute vs per-order pricing and what counts as a completed order. The best choice is the one that matches how your phone really works: short questions, long orders, after-hours calls, and busy dinner rushes.

Restaurant owners get burned by the extras, not just the headline price. Ask these questions before you agree to anything:

• Is there a setup fee?
• Is there a monthly minimum?
• Do I pay for test calls?
• Are after-hours calls priced differently?
• Do transfers, voicemail, or reservations cost extra?
• Is there a contract or cancellation fee?
• Do I pay even when no order is placed?

A practical phone script for sales calls:

> "Can you tell me the total monthly cost for one location, including setup, per-minute or per-call charges, and any other fees? I want to know what I would pay in a normal month and in a slow month."

For a small restaurant, the smallest line items can matter. A fee for each transferred call, a fee for each extra location, or a fee for simple questions can change the bill fast. That is why hidden fees to look for in restaurant software is worth reading before you buy anything tied to the phone.

ROAL keeps this simple: $0.90 per completed phone order, billed monthly, with no monthly fee, no setup fee, no per-minute fee, and no contract. Calls, questions, and test calls are unlimited and free. If you are comparing plans, that makes the math easier because you are paying for confirmed orders that reached the kitchen screen, not for every minute of chatter.

Here is a worked example you can swap with your own numbers.

Say you run a family pizza shop and the average pickup order is $28. In a month, your phone host completes 200 orders.

Now add your own reality:

• If your orders are larger, the service cost may be a smaller share of the ticket.
• If many calls are just menu questions, a per-minute service can waste money on time that does not become revenue.
• If your phone is quiet on weekdays, a monthly fee may feel too high for the slow days.

A restaurant owner usually cares about two things: what the phone costs, and whether the order reaches the kitchen cleanly. ROAL sends a clean ticket to the kitchen screen and can take items, sizes, modifiers, notes, name, phone number, and a ready time. It also skips sold-out items and sends tricky calls to staff with a summary, which helps keep mistakes down at the counter.

This is where phone cost and missed revenue meet. A service can look cheap until you realize it is only useful when it can actually catch the call.

For a lot of independent restaurants, forwarding matters more than fancy features. You can usually forward calls from your existing line to another number, and the method depends on your carrier or phone system. Codes vary, so always confirm with your carrier and test with a call.

Common examples:

• Many landlines and some carriers use *\72 to forward all calls and \73* to turn it off.
• On some GSM mobile carriers, *\\21number# forwards all calls and ##21#** turns it off.
• *\\61number#** can forward unanswered calls.
• *\\67number#** can forward busy calls.
• Verizon Wireless often uses *\72 / \73, and \71** for busy/no-answer forwarding.
• Business VoIP systems usually set forwarding in the web portal.

A useful checklist before dinner rush:

1. Forward the line you want to protect.
2. Test a live call from your cell phone.
3. Make sure the greeting sounds right.
4. Make sure the caller can order, ask hours, and get the address.
5. Turn forwarding off when you do not need it.

ROAL gives each location its own phone line automatically when you claim the host, and you can forward your existing number to it all the time, or only when busy or unanswered. You keep your own number, and forwarding can be turned off any time.

It depends on what kind of work you need done.

Human phone staff usually bill per minute or per call, and you also deal with scheduling, training, and coverage gaps. Delivery apps commonly charge restaurants roughly 15-30% commission per order, which can take a big bite out of a phone order if the customer would have ordered directly.

Try this side-by-side thought exercise:

• Say your average phone order is $30.
• If a delivery app takes roughly 15-30%, that is about $4.50 to $9.00 per order.
• If a phone service costs less than that and sends the order to your kitchen cleanly, the direct order can keep more margin in your restaurant.
• If a human answering service bills by the minute, one long call can cost more than a short order should.

This is why many owners compare phone orders vs delivery apps and phone staff cost before they decide. A phone answering service is not just about answering. It is about whether the phone becomes a clean order, a reservation request, a complaint, or a simple question that staff can handle later.

If your restaurant gets a lot of allergy questions, catering requests, or calls in another language, the right answer may be different from a simple message service. ROAL can hand those harder calls to staff with a summary, while still taking routine pickup and delivery orders from the live menu.

Start with your busiest week, not your best sales week. The right choice should fit the way your phone actually works.

Use this quick checklist:

• Do most calls become real orders, or just questions?
• Do calls come in during rushes, after hours, or both?
• Do you need pickup, delivery, reservations, or all three?
• Do you want to keep your existing number?
• Do you need the kitchen to see the ticket immediately?

A simple owner test:

1. Estimate monthly completed orders by phone.
2. Estimate average order value.
3. Estimate what you currently lose when the line is busy.
4. Compare that with the service fee.
5. Decide whether you want predictable monthly pricing or pay-per-order pricing.

ROAL is built for owners who want a low-friction way to try this. You can paste your restaurant website, Google Maps link, or "Name, City" at /try, let ROAL read the menu, prices, hours, and address from public pages, and test-call it in the browser with no sign-up needed. If it fits your workflow, you can build a free test host and see how the phone sounds before you forward anything.

For a deeper look at budgeting, see budgeting for restaurant technology and the ROI of an AI phone host.