AI Phone Answering for Restaurants: Reservations, Takeout Orders and What It Really Costs

AI phone answering for restaurants

It is 7:15 on a Friday. The host has a line at the stand, a six-top waiting on a table, and the phone has rung four times in three minutes. One caller wants to know if you are open on Monday. One wants a table for eight tomorrow. One wants to order two large pizzas for pickup. The host picks up the one that sounds easiest and lets the rest go to voicemail.

That is what AI phone answering fixes for a restaurant. Every one of those calls is either a simple question an agent can answer in 20 seconds, or a booking or order it can take without pulling anyone off the floor. The catch is that a restaurant phone agent is only as good as what it connects to, and the right product depends on whether your phone makes you money through reservations or through takeout.

The calls a restaurant phone actually gets

Most restaurant calls fall into a handful of buckets. Questions: hours, address, parking, whether you take walk-ins, whether there is a gluten-free menu, whether you are open on the holiday. Reservations: new bookings, changes, cancellations and "are you running late on my table." Takeout and delivery orders. Large parties and private events. And the rest: complaints, lost items, vendors, job seekers.

An AI agent handles the first group well. It handles reservations and orders well only if it can write into your reservation system or POS. Large parties, private events and complaints should go to a person, either by live transfer or a callback the agent schedules.

Before you buy anything, count. Keep a tally sheet at the host stand for one week, or pull call logs from your phone provider. If most of your calls are questions, a cheap agent that answers them and texts a link solves most of the problem. If a quarter of your calls are takeout orders, you need an agent that takes orders into your POS, and that costs more.

Reservation-first and order-first are different products

A reservation agent needs to read live availability and book into OpenTable, Resy, SevenRooms or Yelp, handle party size and special requests, and send a confirmation text. This is Slang AI's home ground. Its pricing page lists integrations with OpenTable, SevenRooms, Yelp and Resy, and it sells per location.

An order agent needs your full menu with modifiers, prices and 86'd items, pushes the order into your POS so the kitchen ticket prints, and ideally takes payment. Maple Pro and Loman's Premium plan are built for this. Maple Pro lists phone ordering into the POS with Toast, Square, Clover and Shift4 Dine, plus OpenTable reservations, secure phone payments and order confirmation texts. Loman lists Toast, Clover, Square, SpotOn, Olo and OpenTable among its integrations and puts takeout ordering, payments and reservations in its Premium plan.

If you run both, a busy brunch spot that also does a lot of pickup for example, buy the product that matches your bigger revenue stream, and check that it handles the other one too.

Your options, side by side

Slang AI starts at $399 a month per location on Core and $599 on Premium, as of October 2026. Core covers reservation management, text confirmations, call recordings and summaries, and the US pricing page lists bilingual support for Spanish. Premium adds 97 languages, private events capture and real-time alerts. No contract length is published, so ask.

Maple is the cheapest on paper. Maple Voice is $150 a month, or $85 a month billed yearly, and answers questions, transfers calls and works in multiple languages, but does not take orders. Maple Pro is $350 a month, or $220 billed yearly, and adds POS ordering, reservations, phone payments and upselling.

Loman does not publish prices. It says there are no per-minute fees, lists up to 50 simultaneous calls on its Starter plan, and puts ordering and payments on Premium. Get a quote and ask which of its listed integrations works with your exact POS.

The DIY route uses a voice platform such as Retell and an automation tool such as n8n. One build documented on this site uses exactly that stack to answer calls and manage reservations, and its creator estimates it saves a restaurant about $3,000 a month in front-of-house labor (builtwithagents.ai/strategy/restaurant-ai-reservation-agent-retell-n8n). That is the creator's own estimate, not checked against a real payroll.

Where a DIY build breaks

A custom agent is cheap and does exactly what you tell it. It struggles in three places.

Reservation systems. OpenTable's booking API is open to approved partners rather than to anyone who signs up, so a one-restaurant DIY build usually cannot write straight into OpenTable. If your book lives there, a vendor that already has the integration is the practical answer.

Orders. Taking an order by voice means the agent must know every modifier, upsell and sold-out item, then push a ticket into the POS. Toast, Square and Clover all have APIs, but menus change weekly, and an agent working from a stale menu takes orders you cannot fill.

Payments. Do not have a DIY agent take card numbers over the phone. Card data brings PCI compliance into scope, and a homemade voice pipeline is the wrong place to learn about it. If you want phone payments, use a vendor that offers them as a feature.

What DIY does well: answering questions from a knowledge sheet, transferring large parties and complaints, and texting callers a link to your online ordering page or reservation widget. For many independents, "text me the link" is enough. The caller orders through the system you already have and the agent never touches the POS.

A worked example: a 70-seat neighborhood bistro

Take a 70-seat bistro that gets about 900 calls a month. A week of tallies shows 55 percent questions, 30 percent reservations on OpenTable, 10 percent takeout orders and 5 percent everything else. These are illustrative numbers.

Reservations are the money calls, and they live in OpenTable, so a DIY build is out for booking. The owner compares Slang Core at $399 a month with Maple Pro at $220 a month on annual billing, since both list OpenTable. Takeout is a small share, so POS ordering is a nice-to-have rather than the deciding feature. The bistro books demos with both and asks each to show a live booking into its OpenTable account, a party of nine being routed to the manager, and a caller asking whether the risotto is safe for a nut allergy.

Here is what a good call looks like. At 6:40 pm a caller asks for a table for four on Saturday at 7:30. The agent checks availability, offers 7:15 or 8:00 because 7:30 is full, books 8:00 with a birthday note, and texts a confirmation. Next caller: a party of 12 for a rehearsal dinner. The agent takes the name, date and phone number, says the events manager will call back by noon tomorrow, and posts the details to the manager's phone. Next caller: the nut allergy question. The agent says the kitchen handles allergy questions directly and transfers to the host stand, or takes a number for a callback if no one answers.

If the bistro went DIY for questions only, the cost would be about 900 calls at 1.5 minutes each, or 1,350 minutes. At Retell's $0.11 example rate plus $0.015 telephony, that is about $169 a month, plus a $2 number and an n8n plan. That is not much cheaper than Maple Pro on annual billing, and Maple Pro also books. For this bistro, buying beats building.

How to set it up

Step 1: Count a week of calls

Tape a tally sheet to the host stand with five columns: question, reservation, takeout, large party or event, other. Every person who answers the phone makes a mark. Also note calls that rang out. At the end of the week you know your volume, your mix and your busiest hours.

Step 2: Pick by your biggest call type

Mostly reservations: shortlist products that integrate with your reservation system, starting with Slang and Maple Pro. Lots of takeout: shortlist Maple Pro and Loman and confirm your POS by name. Mostly questions: Maple Voice or a DIY agent that texts links. Ask every vendor for a live demo booking into your own account, not a canned video.

Step 3: Write the knowledge sheet

One page: hours including holidays, address, parking, dress code, corkage, walk-in policy, large party rules, deposit policy, the link to your online ordering and gift cards, and which dietary menus you have. Add the rule that matters most: the agent never promises a dish is safe for an allergy. It says the kitchen will answer and transfers or takes a number.

Step 4: Set the handoff rules

Decide which calls go to a person and how. Typical rules: parties above eight, private events, complaints, allergy questions, press, and anyone who asks for a manager. During service, route them to a callback list rather than ringing the host stand. Outside service, take a message and text it to the right person.

Step 5: Choose when the agent answers

Do not hand it every call on day one. Start with overflow and closed hours: forward calls that ring four times unanswered, plus every call outside opening hours. Most phone systems can do this with a forwarding rule. After two weeks of clean transcripts, move it to answering first during service.

Step 6: Test, then keep the menu current

Call it yourself with ten scenarios: a booking, a change, a cancellation, a full time slot, a party of 12, an allergy question, a takeout order with modifiers, a caller who speaks Spanish, a complaint about last night, and a caller asking for a person. Fix and repeat. After launch, update the agent every time the menu, hours or specials change. A stale agent is worse than voicemail.

What it costs

As of October 2026: Slang AI from $399 a month per location on Core and $599 on Premium. Maple Voice at $150 a month or $85 billed yearly, and Maple Pro at $350 a month or $220 billed yearly. Loman by quote, with no per-minute fees. A DIY Retell agent runs $0.07 to $0.31 a minute depending on the model and voice, with $0.11 as Retell's default example, plus $0.015 a minute for telephony and $2 a month per number. Add n8n or Make for the logic, and your time.

The hidden cost is the menu and knowledge sheet. Budget an hour a week for the first month and 15 minutes a week after that to keep it accurate.

When it is not worth it

If your phone rings fewer than 10 times a day and your host answers almost every call, you do not need this. Put your hours and ordering link on your Google Business Profile and move on. If your reservation system is not supported by any vendor you can afford, an agent that only takes messages will frustrate callers who expect a booking. And if your regulars are mostly older guests who call to talk to someone they know, start with closed hours only and let the agent prove itself before it ever answers during service.

Frequently Asked Questions