Get started

An AI phone agent for the calls that ring during service

A restaurant phone has terrible timing. It rings hardest exactly when the team can least afford to answer it: Friday at 7 p.m., when the host stand is triple-parked with walk-ins, the runner is carrying plates, and the kitchen wants a word. The caller on the other end is often the easiest revenue the restaurant will see all week—a two-top asking for 8:15, a regular ordering the usual, a company planning a forty-person holiday dinner—and the choice in that moment is to strand a guest at the door or strand a guest on the line.

ThunderPhone gives a restaurant or restaurant group an AI phone agent that answers those calls, follows the house's own policies, uses connected reservation and ordering tools where they are available, and transfers to a person the moment a call needs one. It works from instructions and documents the restaurant approves, so it explains your corkage policy and your large-party rules rather than inventing plausible-sounding ones.

Turn the ring storm into a workflow

A restaurant agent can be configured to:

  • answer reservation requests, and book, modify, or cancel through a connected reservation system or calendar API;
  • explain the waitlist and quote the house's stated wait policy, or read the current estimate from a connected system when one exposes it;
  • answer approved questions about hours, address, parking, dress code, patio seating, corkage, and gift cards;
  • answer menu and dietary questions—gluten-free, vegan, allergen, halal—from menu PDFs and website pages in the knowledge base;
  • take simple takeout requests and relay them to staff, or transfer complex orders to a person or an existing ordering line;
  • capture private-dining and catering inquiries with date, headcount, occasion, budget range, and dietary notes, then schedule a follow-up with the events manager;
  • state large-party policies such as party-size limits, deposit requirements, and cancellation windows, and hand the caller to staff for anything involving payment;
  • place outbound confirmation calls the day before a booking so no-shows cancel early enough to reseat the table; and
  • route callers across a restaurant group to the right location, the events team, or the corporate office.

The agent does not quote a wait time it has no source for, does not promise a table the system will not confirm, and never takes payment-card details over the phone. You define what it may say, what it must collect, and when it must hand off.

Sample restaurant call flow

Agent: Thank you for calling Meridian Kitchen. Are you calling about a reservation, a takeout order, or something else?

Caller: A reservation—six of us, this Saturday around 7.

Agent: I can help with that. For parties of six or more, the restaurant asks for a card hold at booking, which a team member handles. First let me check the table. May I have your name and a callback number?

Caller: Priya Raman, 617-555-0184.

Agent: Thank you, Priya. For six on Saturday I have 6:45 and 8:30 available. Which do you prefer?

Caller: 6:45. Also—one of us is celiac. Is that workable?

Agent: The menu marks gluten-free options, including the roasted branzino and the polenta, and the kitchen asks that you mention the allergy to your server. I have reserved 6:45 p.m. Saturday for six under Priya. I will now transfer you to a team member to complete the card hold—the hold details are handled by staff, not by me. One moment.

The booking happened through a connected system, the dietary answer came from the restaurant's own menu documents, and the payment step went to a person. If no one had been free to take the transfer, the agent could return to the caller, hold the booking as tentative if the house allows it, and arrange a callback.

Features that matter in a restaurant

Peak-hour overflow, not replacement

Many restaurants route the phone to the agent only when it matters: after two rings, when the line is busy, outside service hours, or during known crush windows. The host stand keeps taking the calls it can, and the agent catches the ones that would otherwise hit voicemail. Because ThunderPhone supports SIP trunks and bring-your-own numbers, the existing published phone number stays exactly as it is—the overflow rule lives in the telephony setup.

A knowledge base built from the menu you already publish

Attach menu PDFs, wine lists, event packets, and policy documents (up to 5 MB per text file and 50 MB per PDF or DOCX), or import pages straight from the restaurant's website by URL so the answers track what the site says. The agent searches those sources mid-call. When the seasonal menu changes, update the documents and the phone answers change with them—no retraining a rotating cast of hosts on which desserts contain nuts.

Reservation actions through connected tools

Agents can call HTTP APIs and MCP tools during a conversation. If the reservation platform, table-management system, or a simple calendar exposes an action—check availability, create, modify, cancel—the agent can use it and confirm the result back to the guest. Where no integration exists, the agent still collects a complete, structured request and delivers it to staff by webhook, so nothing arrives as a half-heard voicemail.

Takeout intake without touching a card

For a focused menu, the agent can capture the order—items, quantities, modifications, pickup name and time—and relay it to the kitchen through a webhook or connected system, with payment taken at pickup or through the restaurant's existing ordering flow. For long or heavily customized orders, configure a transfer to a person instead. In either mode the boundary is the same: the agent never asks for or accepts card numbers.

Event and catering inquiries captured while they are warm

Private-dining and catering calls are high-value and easy to lose. The agent can run a structured intake—date, guest count, occasion, room or off-site, budget range, dietary requirements—answer questions from the events packet, and book a follow-up call with the events manager through a connected calendar. The full intake arrives as structured data, not a sticky note.

Outbound confirmation and reminder calls

On an eligible production number, the agent can place individual outbound calls or run campaigns: day-before reservation confirmations, large-party reminders, or a callback when a waitlisted table opens. Voicemail detection lets each call follow your policy—leave a configured message, hang up, or let the prompt decide—and campaigns retry voicemail outcomes on a schedule. The restaurant remains responsible for consent, identification, calling windows, do-not-call requests, and other applicable outbound-calling laws.

Multilingual guests on one number

ThunderPhone supports 47 voice languages. Set a primary language and additional languages, and the agent switches mid-call when a guest changes to one of the configured languages, provided the selected voice supports the set. A restaurant in a tourist district or a multilingual neighborhood can serve callers in their own language without staffing for it.

Multi-location routing for groups

A restaurant group can run one front-door agent that identifies which location the guest wants, answers location-specific questions from location-scoped documents, and books against the right system—or transfers to the right host stand. Keypad-menu navigation and hold handling mean the agent can also work outbound through a location's existing phone tree when it needs to reach staff. Catering calls from any location can route to one central events team with the location attached.

Transfers that respect the rush

Cold transfers route a caller immediately. Warm transfers, available on eligible production VoIP or SIP numbers, keep the guest on hold while the agent privately briefs the host or manager—"party of six Saturday, card hold needed"—and connect only if the person accepts. If nobody picks up mid-rush, the agent returns to the guest, takes a message, or follows the configured fallback instead of dumping the call.

Every call reviewable, every change testable

With recording enabled, calls produce recordings, transcripts, and grading, so a manager can skim how the agent handled Saturday night. Before any prompt change goes live, run simulations—an indecisive large party, a caller disputing the cancellation policy, an allergy question the menu does not answer, a non-English speaker, a takeout order with five modifications—and gate changes behind regression suites with minimum pass rates. A/B experiments can compare two greetings or booking flows on live traffic.

Webhooks into the systems you already run

Every completed call can post structured results to your endpoints—signed with HMAC-SHA256—so reservations, takeout relays, and event leads land in the POS back office, a spreadsheet, or a group's CRM automatically. The same web widget that powers phone agents can also take voice conversations from the restaurant's website.

What the agent should not do

Guardrails are part of the configuration, and some are platform policy:

  • No payment-card details, ever. Deposits, card holds, and takeout payments are completed by staff or by the restaurant's existing payment and ordering systems. The agent collects everything else and hands off.
  • No invented availability or wait times. If no connected system or approved document answers the question, the agent says so and offers the configured alternative—a transfer, a callback, or the waitlist policy as written.
  • No off-menu medical claims. For allergy questions, the agent relays what the restaurant's own documents state and repeats the house instruction (for example, "please tell your server"), rather than guaranteeing that a dish is safe.
  • Compliance stays configurable. ThunderPhone's public posture is GDPR and HIPAA compliant; the restaurant still controls recording settings, retention, guest notices, and where call data is sent, and remains responsible for its own obligations.

What would this cost each month?

Suppose a busy restaurant handles 2,500 AI-assisted calls per month, averaging 2 minutes each:

2,500 calls × 2 minutes = 5,000 minutes per month

  • Spark: 5,000 × $0.02 = $100/month
  • Bolt: 5,000 × $0.05 = $250/month
  • Storm: 5,000 × $0.09 = $450/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

The arithmetic is illustrative. A counter-service spot fielding mostly hours-and-directions calls will run shorter; a group taking event inquiries and running confirmation campaigns will run longer.

Frequently asked questions

Can a ThunderPhone agent book and change reservations?

Yes, when connected to a reservation system, table-management API, or calendar that exposes those actions. The agent can check availability, book, modify, or cancel, and confirm the result to the guest. Without an integration, it collects a complete structured request and delivers it to staff.

Can it take takeout orders?

It can capture simple orders—items, modifications, pickup name and time—and relay them to staff or a connected system, with payment handled at pickup or by the restaurant's existing ordering flow. For complex menus, configure it to transfer order calls to a person. It never takes card numbers over the phone.

Can it handle a deposit or card hold for a large party?

No. The agent explains the policy, books the table where the system allows it, and transfers the caller to staff or points them to the restaurant's existing payment flow. Payment-card details are never collected by the agent.

Can it tell callers the current wait for a table?

It can state the house's wait policy and typical ranges from approved material, or read a live estimate when a connected system provides one. It is configured not to invent a number when no source exists.

Can it answer menu and allergy questions?

Yes, from the menu documents and web pages the restaurant attaches or imports by URL. It relays what those sources say and repeats the house's allergy instructions; it does not guarantee that a dish is safe for a specific condition, and it routes unanswered questions to staff.

Can it call guests to confirm reservations?

Yes—individual outbound calls or campaigns on an eligible production number, with voicemail detection and campaign retries. The restaurant is responsible for consent, identification, calling windows, and other applicable outbound-calling laws.

Can one agent cover several locations?

Yes. It can identify the location the guest wants, answer from location-scoped documents, book against that location's system, and transfer to the right host stand—or route all catering calls to a central events team with the location attached.

What languages can it speak with guests?

ThunderPhone supports 47 voice languages. Configure a primary language plus additional languages, and the agent can switch mid-call when a guest changes language, provided the selected voice supports the configured set.