Every restaurant has the same unmeasured loss: the phone rings at half past seven on a Friday and nobody can answer it. That call was a table for four. It goes to the place down the street, and nothing about it appears in any report, because a booking that never happened leaves no record. This is the clearest case for agents in hospitality, and it has nothing to do with replacing staff. It is about the work that currently does not get done at all.
§ 01The phone during service
A voice agent answers on the first ring at any hour, including the hours when the kitchen is closed and the calls are still coming. It takes the reservation, checks availability against the booking system, confirms by message, and handles the changes and cancellations that otherwise arrive as voicemail nobody plays back.
It also answers the same four questions it will answer forever: are you open on Sunday, where exactly are you, do you have parking, do you have vegetarian options. Those calls interrupt service every night and none of them need a human.
What matters in the design is the handover. When a caller wants something unusual, a private event, a complaint, a large group with conditions, the agent should recognise the boundary and pass the call to a person rather than improvise. An agent that tries to handle everything produces exactly the frustration people already associate with automated phone systems.
§ 02Beyond the phone
- Messages across channels. Bookings and questions arrive by WhatsApp, Instagram, Facebook, and web form. One agent covers all of them with consistent answers, instead of three people checking three apps between services.
- Supplier ordering. Recurring orders based on par levels, confirmations, and chasing deliveries that did not arrive. Low glamour, high frequency, and it happens at the worst hours of the morning.
- Review responses. Every review deserves a reply, most owners write none. An agent drafts responses in the venue's voice and holds negative reviews for a person to approve, which is where the judgment belongs.
- Shift coordination. Absences, swaps, and coverage requests are constant messaging work that manages itself once the rules are written down.
- Multi-location consistency. For a group, the same agent answers identically for every venue while respecting each venue's hours, menu, and capacity. This is where the economics stop being marginal.
§ 03The one thing an agent must never do alone
Allergies and dietary safety. This is not a policy preference, it is the line between a service problem and a medical one. A guest asks whether the sauce contains nuts. The correct system behaviour is to recognise the topic, say plainly that a member of the team will confirm, and escalate immediately, every single time, with no exceptions for a confident-sounding answer.
Recipes change, suppliers substitute ingredients, and a kitchen improvises on a Tuesday. No model can know what is in tonight's sauce, and a confident wrong answer here is a hospitalisation and a lawsuit. If a vendor demonstrates an agent answering allergy questions autonomously, that demonstration is the reason not to hire them. The general principle, that agents prepare and humans approve wherever consequences are physical or legal, runs through everything we build and is documented in our engineering notes.
§ 04Where the economics actually work
Honest scoping matters here more than in most sectors, because restaurant margins do not tolerate optimistic projects. A single small restaurant with a quiet phone and a well drilled front of house may not need this. The build cost is real and the return depends entirely on how many calls currently go unanswered.
It becomes clear economics in three situations: venues where the phone rings through service and nobody can reach it, groups with several locations sharing one agent, and operations already paying someone to manage bookings and messages across four channels. If you cannot estimate how many calls you miss on a Friday night, that number is the first thing to measure, before any build.
On price: a single agent covering one process end to end costs 3,000 to 5,000 USD over 2 to 3 weeks. Voice sits at the upper end because real-time speech adds latency handling and failure paths that text does not have. The full breakdown of what moves the price is in our cost guide.
§ 05How to start without risking service
Start with the calls that arrive when you are closed, because there is no service to disrupt and no comparison to a human being who would have answered better. Let the agent take those bookings for a few weeks and read the transcripts. You will learn what people actually ask, which is never quite what you expected, and you will see how often the agent should have escalated but did not.
Only then extend it into service hours, and keep the handover to a person one step away at all times. Comparable staged deployments are described across our production cases.
──
If you want to know whether the phone is costing you more than an agent would, that is a 30 minute discovery call. We will also say when the answer is that your volume does not justify it, which is a cheaper thing to hear now.