Skip to content

Blog · Business automation

Restaurants: which part of an order or a booking an agent can take over WhatsApp

What an agent can take in a restaurant: bookings, orders and order status, against the venue's own system and without inventing availability or prices.

Equipo editorial de Meteor Published 2 min read

Can an AI agent take restaurant orders and bookings over WhatsApp?

Yes, as long as the agent checks the venue's system before committing to anything. It can take a booking against real table availability, build an order from the menu and prices that are loaded, answer where an order stands and say when something is unavailable. What it cannot do is promise a table that does not exist, apply a price that is not on the menu or settle a complaint about the food: that goes back to a person at the venue, with the full conversation.

A full restaurant has a problem that never shows up at the till: the phone. It rings while somebody is taking an order, while a delivery app sends another one through, and while two people wait at the door. Almost all of those calls ask the same things: is there a table, what is on the menu, how much is it, where is my order.

Booking against the tables that exist

A booking confirmed over chat without checking real availability is a table somebody will have to invent at nine on a Friday night. The agent checks before confirming, exactly as the person holding the reservations book would, except it does not stop answering everything else.

The order, without double entry

When an order is taken over chat and then retyped into the system, two costs appear: the time and the mistakes. In the order-from-chat recipe the order lands directly, with the menu and prices the venue has loaded.

It is the least impressive part and the one that pays for itself fastest on a busy night.

Orders arriving through other apps

A venue with three channels does not have one problem per channel: it has the problem that nobody sees all three at once. Handling Rappi orders from the same place is not about saving tablets, it is about no longer having three separate queues competing for the same kitchen.

What it must not touch

The menu rules. If a dish sells out and nobody marks it, the agent will keep offering it, because it reads what is there: that is not a flaw in the agent, it is a venue task made visible.

And complaints about the food go back to a person. The support Met hands over the full conversation so nobody has to ask again what happened.

Where to start

With the question that arrives most. In a restaurant that is usually “is there a table?” or “where is my order?”, and both have an exact answer in a system the venue already uses. The restaurant solution builds the rest on top of that.

The limits

What this article does NOT answer

We would rather say it here than leave you hunting for something that is not there.

Keep going

What this article mentions, in detail

The integrations, the Mets and the automations named above, each with its own page.

Frequently asked

Questions on this topic

From the system where the restaurant already maintains them. If a dish sells out and somebody marks it, it stops being offered; if nobody marks it, the agent will keep offering it, because it reads what is there.

It helps by putting them in one place. The real problem of a venue with three channels is not each channel on its own, it is that nobody sees all three at the same time.

Yes, and it is the case where the difference shows most: the order lands in the system without anybody retyping it, which is where mistakes creep in on a busy night.

Keep reading

Other articles on the same thing

Want to see it running on your operation?

We show it with your own accounts connected, not with a canned demo.