Per-minute answering service pricing usually works best when you want a broad phone coverage bill that is tied to call length. Per-order pricing usually works better when your main goal is to pay only when a confirmed order comes in.
For a restaurant, that difference matters. A long menu question, a busy caller, or a caller who changes their mind can make a per-minute bill climb fast. ROAL uses per-order pricing, so you can compare cost against actual completed orders instead of minutes on the phone.
Key takeaways
- Per-minute pricing charges for time on the phone, even when no order is placed.
- Per-order pricing is easier to tie to restaurant revenue because you pay only on completed orders.
- For restaurants with long menu questions, per-order pricing is usually easier to predict.
- ROAL charges $0.90 per completed phone order with no monthly fee, setup fee, or per-minute fee.
- Before you switch, compare real call patterns, not guesses.
In this post
- What does per-minute answering service pricing really mean?
- How does per-order pricing work for a restaurant phone line?
- Which pricing model is easier to predict for a takeout shop?
- When does per-minute pricing make sense, and when does it not?
- How do you compare phone pricing against delivery apps and staffing?
- What should you ask before you switch your restaurant phone line?
- Questions owners ask
What does per-minute answering service pricing really mean?
With per-minute answering service pricing, the restaurant pays for the time someone spends on the call. That can include a quick order, a long question about toppings, a delivery address check, or a caller who takes a while to decide.
For a busy pizza shop or deli, that can make the bill swing around month to month. A short call might cost little, but a 6-minute call costs more even if the caller never orders. Human answering services usually bill this way, or sometimes per call.
Use this quick check:
- Ask how they start the clock
- Ask whether hold time counts
- Ask whether transfers count
- Ask whether after-hours calls count
- Ask whether order-taking time is priced the same as questions
Example to plug in your own numbers: if a service charges a per-minute rate and your average call is 4 minutes, then a 50-call month is 200 billable minutes. If your busy Friday pushes the average to 6 minutes, that same month becomes 300 billable minutes. The caller behavior changes the cost, not just the call count.
How does per-order pricing work for a restaurant phone line?
Per-order pricing charges only when a call turns into a confirmed order. ROAL charges $0.90 per completed phone order, meaning a confirmed order whose ticket reaches the kitchen screen. Calls, questions, and test calls are unlimited and free, and there is no monthly fee, setup fee, per-minute fee, or contract.
That model is easier to map to food sales because the cost attaches to the thing you are trying to sell. If the caller just wants hours, parking, or menu details, you do not pay for that call. If the caller places an order, you pay the order fee.
Worked example with simple numbers:
- Say your average phone order is $28
- Say you get 100 completed phone orders in a month
- Per-order cost at ROAL: 100 × $0.90 = $90
- Your food revenue from those orders: 100 × $28 = $2,800
Plug in your own average ticket and order count. That is the cleanest way to compare phone pricing to your actual margins.
Which pricing model is easier to predict for a takeout shop?
For most independent restaurants, per-order pricing is usually easier to predict than per-minute pricing because orders are the business outcome you care about. Minutes can vary a lot depending on caller mood, menu size, modifier questions, and whether the caller needs help deciding.
Here is a simple comparison table you can use with your own numbers:
| Model | What you pay for | What changes the bill | Best when |
|---|---|---|---|
| Per-minute | Talk time | Call length, hold time, transfers | You want coverage and do not mind variable usage |
| Per-order | Completed orders | Number of confirmed orders | You want costs tied to sales |
| Monthly flat fee | One set bill | Usually nothing during the month | You want predictability over usage |
A practical owner test:
- Look at your last 2 weeks of calls.
- Count how many were actual orders.
- Estimate how many calls were questions only.
- Compare a per-minute bill against a per-order bill using those real counts.
If you already know your phone gets lots of menu questions, per-order pricing can be easier to live with because questions do not trigger charges.
When does per-minute pricing make sense, and when does it not?
Per-minute pricing can make sense if your calls are very short and consistent. It can also work if you want a traditional answering service to handle a wide mix of calls and you are okay with usage changing month to month.
It is usually a tougher fit when callers spend a lot of time asking about specials, substitutions, delivery zones, or allergy questions. That is common for pizza shops, family restaurants, and delis.
Use this restaurant-specific checklist before you sign:
- Ask whether menu questions count the same as order calls
- Ask whether the service can quote ready times
- Ask whether it can take item modifiers and notes
- Ask whether it can handle sold-out items
- Ask whether it passes allergy-sensitive calls to staff
ROAL handles those restaurant details and can send tricky calls to staff with a summary. It also reads a live menu, so it does not offer items marked sold out. It does not take card numbers over the phone, either; payment stays with your normal process. If you want the basics of the setup flow, see How it works.
How do you compare phone pricing against delivery apps and staffing?
A phone line is not the same as a delivery app, but the math is worth comparing because both affect your margins. Delivery apps commonly charge restaurants roughly 15-30% commission per order. Phone pricing is usually much smaller than that, but the billing model still matters.
If you hire staff to answer phones, you are paying for hours, not just orders. That can make sense in a busy store, but it is not always cheap for a few rush periods a day. For a rough comparison, use your own numbers and compare these three lines:
| Cost type | What to plug in |
|---|---|
| Delivery apps | Your average order value and commission rate |
| Phone staff | Hourly pay, payroll cost, and hours covered |
| Phone host | Per-order fee or monthly plan |
If you want to compare usage-based pricing models more broadly, usage-based pricing for small businesses, explained is a good follow-up read. For phone costs specifically, ROAL’s per-order model keeps the bill tied to completed kitchen tickets, not minutes sitting on the line.
What should you ask before you switch your restaurant phone line?
Before you switch, make sure the pricing model matches how your restaurant actually works. A good phone setup should answer common questions, take orders, and keep staff from getting buried during rushes.
Here is a simple owner checklist:
- Confirm whether you are charged per minute, per call, per order, or monthly.
- Ask what counts as a billable event.
- Ask what happens with questions, test calls, and busy signals.
- Make sure the system can take your live menu and hours.
- Confirm how tricky calls get handed to staff.
For call forwarding, confirm the exact code with your carrier or phone system before you change anything. Codes can vary by carrier and plan, and it is smart to test with a call after setup. If you want a carrier-by-carrier reference, see call forwarding codes by carrier.
ROAL gives each location its own phone line automatically once you claim the host, and you can forward all calls or only busy and unanswered calls. If you want to test the setup from your own website or menu, Build a free test host.