Key takeaways
- A remote order-taking service answers in your restaurant's name and keys orders into your online ordering or POS, usually through a login rather than a deep integration.
- Bills usually combine a monthly minimum with per-minute, per-call or per-order charges, and agent labor has become more expensive[1].
- Accuracy slips where local knowledge lives: 86s, same-day specials, delivery boundaries and regulars' usual orders.
- If remote agents take card numbers, PCI rules for telephone payments apply, including to call recordings[2].
- Run a two-week pilot on your real peak, with test calls and a daily ticket audit, before signing anything longer.
Why independents look at remote order takers
Owners usually start pricing remote order takers after one bad stretch: the best host quit, the phone rang out three Fridays in a row, or a month of delivery app statements made them want every phone order back. That last motive is reasonable. Two in three restaurants say they pay delivery platforms between 15% and 29.9% of the transaction[3], so an order taken on your own line is worth protecting.
The pitch is simple. A trained person answers every call in your restaurant's name, takes the order, puts it into your system and the ticket prints in your kitchen, while your staff deal with the guests in front of them. What the pitch leaves out is how the order gets into your system, who keeps the agent current on your menu, and what happens when the order is anything but standard. Those three details decide whether it works.
It is also a smaller labor pool than many owners assume. Private US telephone answering services employed about 33,324 people in 2025, down from 52,951 in 2001[4]. Every client restaurant wants those agents at 6 p.m. on Friday, so ask about peak staffing before anything else.
How the order gets from the call to your kitchen
- Caller
- Your team
- System
01Caller
Guest dials your number
Your listed number forwards to the service, all day or only when you are busy.
02Your team
Agent answers in your name
The agent reads your greeting and works from the menu file you supplied.
03Your team
Order keyed in
Entered on your online ordering page or a POS login, then read back.
04System
Ticket prints
Your kitchen sees it like any other online or POS order.
05System
Call record sent
The service logs the call; ask whether you get recordings or only a list.
Example of a common setup. Connection methods vary by service and by POS.
There are three common ways the order reaches you, and they are not equal. The cleanest is the agent ordering through your own online ordering page, exactly as a guest would. The menu, prices, modifiers and 86s are whatever your online system shows, so the agent inherits your accuracy, good or bad. The second is a remote login to the POS or an order-entry screen tied to it, which gives the agent more control and more ways to key things wrongly. The third is the agent writing the order down and sending it to a tablet, email or printer for your staff to re-enter. That last one doubles the work and the error rate, and it should be a deal-breaker for a busy kitchen.
Keep your own number on your listings and forward it. Google's Business Profile guidelines ask for a phone number that connects to the individual location, and a local number rather than a central call center line whenever possible[5]. If the service asks you to publish their number, the guests, the reviews and the call history follow their number, not yours. Call forwarding for restaurants covers forwarding all day, after hours or only when busy.
What you are billed for
Billing models differ, but most combine a few of these lines. Get every one in writing, with a sample invoice built on your real call volume, before comparing quotes.
- A monthly base or minimum, charged whether the phone rings or not.
- Per-minute talk time, often rounded up per call, so a 61-second call bills as two minutes.
- Per call or per completed order, sometimes as a percentage of the order value.
- Setup and menu build, plus a fee for each menu change after launch.
- Holiday, late-night or weekend surcharges, which land exactly on your busiest days.
- Payment handling, if agents take cards on your behalf.
Underneath every model is the agent's time, and that time has become more expensive. Average annual pay at US telephone answering services reached $59,295 in 2025, against $37,308 in 2018[1], and the median customer service representative earned $21.53 an hour in May 2025[6]. Restaurant answering service cost works one month of calls through five billing models.
Source: US Bureau of Labor Statistics, 2025[1]
Show the data
| Year | Average annual pay |
|---|---|
| 2013 | $32,856 |
| 2018 | $37,308 |
| 2025 | $59,295 |
Where accuracy slips
Remote agents get standard orders right most of the time. The errors cluster where your staff rely on knowledge nobody wrote down. Each weak spot below needs either a line in the menu file or a rule in the contract.
| Weak spot | What goes wrong | What to put in writing |
|---|---|---|
| 86s and sold-out items | Agent sells the last of something twice | Who tells the service, how, and how fast they confirm |
| Daily specials | Agent does not know tonight's special exists | A daily specials line, sent before service |
| Unwritten modifiers | Light sauce, well done or extra crispy gets lost | Every modifier your kitchen accepts, by item |
| Delivery boundaries | Out-of-area orders accepted, or good ones refused | Zones by ZIP code or street, with fees |
| Regulars and the usual | Agent cannot see what the guest ordered last time | Caller lookup in your ordering system, if it has one |
| Allergies | Agent reassures a guest it has no basis to reassure | Allergy questions transferred to your manager |
| Pickup time quotes | Agent quotes 20 minutes while the rail runs 45 | A current quote you update during service |
The 86 process matters most because it fails silently. If agents order through your online ordering page and someone marks items unavailable there, the problem mostly solves itself; keeping online menus, prices and 86s in sync covers that habit. If agents work from a PDF menu, every 86 depends on a phone call or text from your busiest person at your busiest moment. Allergy calls need the same clarity; how to handle allergy questions over the phone sets out what staff should and should not say.
Card payments and call recordings
If remote agents take card numbers over the phone, card data is now passing through someone else's people and systems on your behalf. The PCI Security Standards Council's guidance on telephone payments covers exactly this: pause-and-resume tools to keep card numbers out of recordings, deleting sensitive authentication data from any recording that captured it, checking recordings regularly, and restricting access to recordings that hold card data[2]. Ask the service which of these it does, and get it in the contract.
The simpler route is to keep cards off the call. The agent places the order as pay at pickup, or the guest pays through your ordering page. Recording rules apply either way. Federal law lets a party to a call record it, but some states require every party's consent[7], so the greeting needs a recording notice where that applies; call recording laws by state lists the details. Ask who owns the recordings and guest phone numbers when the contract ends.
Do the numbers work?
Put a number on the staff time the service would take over, then set it beside the quote. Accommodation and food services employers paid an average $20.03 per hour worked in wages and benefits in June 2026[8].
| Input | Example |
|---|---|
| Order calls a day | 45 |
| Minutes per order call | 3.5 |
| Share the service would take (%) | 80% |
| Staff cost per hour, with benefits | $20.03 |
| Calls a month | 977 |
| Staff hours on these calls | 57 |
| Hours handed off | 46 |
| Monthly value of that staff time | $913 |
How it is worked out: Calls a day × 21.7 working days × minutes per call ÷ 60 × share handled = hours; hours × hourly cost.
Assumptions
- Hourly cost is the BLS employer compensation figure for accommodation and food services, wages plus benefits.[8]
- Three and a half minutes allows for delivery addresses and a readback; time your own calls.
- 80% assumes the service takes routine orders and passes large orders, allergies and complaints back to you.
Example. Compare the monthly cost with the service's written quote for the same number of calls.
Example: 45 order calls a day at three and a half minutes, with 80% going to the service, is about 780 calls and 46 staff hours a month, roughly $910 at that hourly cost. If the quote for those 780 calls is well above that, the case rests on something else: calls you are currently missing, or a host freed to sell tables. Those can be worth more than the hours, but count them separately and do not let a sales deck blend them together.
A two-week pilot plan
Days 1 to 2: build the menu file together
Every item, modifier, price and nickname guests use, delivery zones, pickup quote rules and the 86 process. Name one person on your side who owns updates.
Day 3: test calls before any guest call
Ten calls from staff phones: a standard order, a half-and-half or build-your-own, an 86ed item, an out-of-area address, an allergy question, a complaint and a large order.
Days 4 to 14: go live on overflow or one daypart
Forward only when your line is busy or unanswered, or only for weekday lunch. Keep your own staff on the phone for everything else as the baseline.
Every day: audit ten tickets
Compare the call or the agent's notes, the ticket and what left the kitchen. Log every error by type.
Day 14: decide on the numbers
Error rate against your own staff, cost per completed order, calls answered at peak and guest complaints. Extend, change the scope or stop.
Write service levels into the agreement, not just the brochure. Restaurants have no standard of their own, but federal rules for Medicare Part D plan call centers offer a concrete benchmark: an average hold of 2 minutes, 80% of calls answered within 30 seconds and no more than 5% disconnected[9]. Ask for a monthly report against numbers like those, measured at your peak hours as well as overall.
Questions to ask before you sign
- How many agents are on at 7 p.m. on a Friday, across all clients, and how many calls can they hold at once?
- Do the same agents handle our account, or anyone in the queue?
- How does an 86 reach the agents, and how quickly is it confirmed?
- Can we listen to recordings of our calls, and how long are they kept?
- Who owns guest names, numbers and order history when we leave?
- What happens to a call the agent cannot handle: transfer to us, a message, or a callback?
- What notice do we need to give to stop, and are there menu-change fees?
If you would rather keep orders in-house
Some independents conclude that the real problem is the calls that are not orders, and the orders that arrive when nobody can pick up. One alternative is to keep order taking with your own staff and your own ordering page, and forward only overflow and after-hours calls to an SI Employee. It answers questions from the details you approve, texts your ordering link to callers who agree, takes catering and large-order details for a callback, and hands allergy questions and complaints to your manager. Because it does not key orders, there is no menu file to keep in sync and no card number on the call; call records can also go to other systems by webhook (see integrations).
The pizzeria Friday rush example models that setup for a single shop. For a side-by-side of staff, a texted link, remote order takers and voice ordering, see four phone ordering setups compared. Groups with several locations have a different calculation, covered in restaurant call centers for multi-unit groups, and what restaurant answering services do covers message-taking services that do not take orders at all.
Frequently asked questions
Do remote order takers connect directly to our POS?
Sometimes, but often they order through your online ordering page or a POS login, as a guest or staff member would. Ask exactly how the order reaches your kitchen and avoid any setup where your staff re-enter it.
Should we publish the service's phone number?
No. Keep your own local number on your listings and forward it. Google asks for a number that connects to the individual location[5].
Can the service take card payments for us?
Some do. If so, PCI guidance for telephone payments applies to their agents and recordings[2]. Pay at pickup or payment through your own ordering page avoids the issue.
What service levels should we ask for?
Put numbers in writing and measure them at your peak. Medicare Part D call center rules use an average hold of 2 minutes, 80% answered within 30 seconds and at most 5% disconnected[9], which is a useful reference point.
How long should a pilot run?
Two weeks covers four peak nights and enough calls to compare error rates. Start on overflow or one daypart so your own staff remain the baseline.
References
US Bureau of Labor Statistics (2025). Quarterly Census of Employment and Wages: Average Annual Pay in Private NAICS 561421 Telephone answering services, U.S. total (opens in a new tab) ↑
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑
National Restaurant Association (2026). National Restaurant Association comments to the FTC on the Food Delivery Fees ANPRM (Project No. P267101) (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Quarterly Census of Employment and Wages: All Employees in Private NAICS 561421 Telephone answering services, U.S. total (opens in a new tab) ↑
Google Business Profile Help (2026). Guidelines for representing your business on Google (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025 national estimate: Customer service representatives median hourly wage (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code § 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑
US Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: private industry workers by occupational and industry group, June 2026 (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text (2026). 42 CFR 423.128 - Dissemination of Part D plan information (opens in a new tab) ↑