Solution · Restaurants
AI agent for restaurants: it takes the order, accepts the delivery and books the table
The Met builds the order inside the conversation from your menu, accepts Rappi orders with the real prep time, switches off whatever sold out before anybody orders it, and books the table.
What does an AI agent do in a restaurant?
Meteor connects the channels your customers write to with your delivery operation and with the diary for your tables. On top of that, an AI agent works around the clock: it builds the order inside the conversation from your menu, confirms the items, checks the address falls inside the zones you serve and gives the total before the order reaches the kitchen, then generates the payment link and confirms the money landed. On the Rappi side it sees new orders come in, accepts them with the real prep time and marks them ready for the courier, switches off by SKU whatever sold out before somebody orders it, and closes the storefront when the kitchen gets swamped instead of stacking up orders nobody can fill. Table bookings come from the slots that are genuinely free and get confirmed, moved or cancelled right there in the chat, with the reminder scheduled. What it does not do is manage couriers or delivery times, change prices or edit the menu: that stays in your operation and in your portal.
How many orders do you lose during the rush?
These are the bottlenecks costing your restaurants operation the most sales and time.
The order taken, accepted and paid for without going near the tablet
The Met builds the order inside the conversation from your menu, accepts Rappi orders with the real prep time, switches off whatever sold out before anybody orders it, and books the table.
Before and after
From the same old bottlenecks to a real advantage
During the rush, the order nobody gets to accept cancels itself.
The Met accepts it the moment it lands, with the real prep time, and marks it ready.
An ingredient runs out and the item stays listed until somebody switches it off.
It goes off by SKU at once, price untouched, and back on when the ingredient arrives.
WhatsApp orders typed out by hand and totals worked out on the side.
The order is built in the conversation, with the zone checked and the total confirmed.
Table bookings confirmed by message and written down nowhere.
Genuinely free slots, the booking tied to the contact and the reminder scheduled.
The solution
How Meteor automates your restaurants operation
The order built inside the conversation
The Met walks your menu with the customer, confirms each item, checks the address falls inside the zones you serve and gives the total before the order reaches the kitchen.
No order lost for not accepting it
A Rappi order that is not accepted in time cancels itself, and the store pays for that cancellation. The Met sees it land, accepts it with the real prep time and marks it ready when the kitchen finishes.
Whatever sold out, switched off at once
It switches sold out items off by SKU without touching their price, and switches them back on when the ingredient arrives. That is what prevents accepting an order for something you do not have.
The swamped kitchen, protected
It closes the storefront when the queue gets away from you and reopens it once the location catches up. Rejecting twenty orders in a row costs reputation; closing for twenty minutes does not.
The table booked inside the chat
Times come from the slots that are genuinely free, the booking is tied to the contact, and it gets moved or cancelled right there, with the reminder scheduled.
Payment taken and the customer on file
A payment link inside the conversation, confirmed before anything ships, and every customer on file with their preferred location, their tags and their notes.
Integrations
The systems your restaurants operation already runs
Delivery, the dining room and the payment run through different systems and at the same hours. The Met operates them from one conversation.
Rappi
10 toolsYour Rappi storefront, run without the tablet. The Met receives the order the moment it lands, accepts it with the real prep time, marks it ready for pickup, switches off by SKU whatever sold out and closes the whole storefront when the kitchen gets swamped. It never touches prices or edits the menu.
See the Rappi spec sheetMeteor Scheduling
7 toolsThe table booking as a service with its own duration and hours: genuinely free slots, the booking tied to the contact in the conversation, moved or cancelled in one step. There are no credentials to obtain.
See the Meteor Scheduling spec sheetCal.com
6 toolsIf your bookings or events already live in Cal.com, the Met checks availability and books from the chat; several connected accounts cover several locations.
See the Cal.com spec sheetMeteor CRM
24 toolsEvery customer on file: their preferred location and their usual order in fields of their own, tags, internal notes, reminders that go out over WhatsApp, and a handover to a person when the order gets complicated.
See the Meteor CRM spec sheetMercado Pago
7 toolsCharge for the delivery or the deposit on an event with a payment link inside the conversation, and confirm the money landed before the order reaches the kitchen.
See the Mercado Pago spec sheetFacebook and Instagram
7 toolsPublish the day’s menu, the promotion or the reel to Facebook and Instagram from the same workspace, across several brands or locations if you run more than one.
See the Facebook and Instagram spec sheetEach spec sheet lists the tools the connector really exposes, the credential you need and what it does NOT do. They are published in Spanish. See the full catalog .
The limits
What Meteor does NOT do in restaurants
We would rather say it here than have you find out during implementation.
-
It does not change prices or edit the menu on Rappi. It only turns availability on and off for items that are already published.
-
It does not manage couriers, delivery times or routes. The zone you serve and the delivery fee are the ones you declare, and the dispatch itself stays with your operation or with the platform.
-
It does not resolve marketplace disputes or refunds, and it does not reject orders on its own: rejecting notifies the buyer, so it always goes through a person.
-
The Rappi integration is written on their Colombian operation: their API domain changes by country.
-
It publishes to Facebook and Instagram, but it does not read or reply to comments on your posts. Direct messages it does handle, because there it is a conversation channel.
-
Meteor’s diary does not sync with Google Calendar or Outlook, and it does not book on someone else’s behalf: the booking stays tied to whoever is writing.
-
It does not send bulk messages. Reminders go out one at a time and as an approved template, because outside the conversation window WhatsApp only allows templates.
-
It does not store or process card details, and it does not issue tax documents. It generates the link and reads the result.
The right team
The Mets that work best in restaurants
Combine these Mets to cover the full cycle of your operation.
Customer support
Answers questions, resolves issues and looks after your customers on WhatsApp, Instagram, Messenger and web chat, at any hour.
View Met Appointments and bookingsScheduling
Handles bookings and appointments on its own, in sync with your calendar and availability.
View Met MarketplacesIgor
Publishes your catalog on Mercado Libre, Rappi, Éxito and HomeCenter, and keeps price and stock current on each one. Holds back whatever does not comply before the marketplace rejects it.
View MetFAQ
Questions about Meteor in restaurants
Yes. The Met works from the menu you load into it: it walks the options with the customer, confirms each item and quantity, checks the address falls inside the zones you serve and gives the confirmed total before the order goes to the kitchen. What that removes is the typing by hand, which is where order errors come from.
Rappi notifies Meteor the moment the order lands, not on a schedule, because the window to accept is minutes wide and a periodic check arrives late exactly during the rush. The Met accepts it stating the real prep time, which is what Rappi uses to dispatch the courier at the right moment, and later marks it ready for pickup. Marking it early leaves the courier waiting; marking it late means the food arrives cold.
It checks the address falls inside the zones you declare and builds the order total with that fee. What it does not do is connect to courier platforms or calculate a route: that connector does not exist. If you also ship packaged product to another city, there is real carrier quoting for that, and it lives in the e-commerce solution.
Yes, and it comes from real availability, not from a list typed by hand: you declare the booking as a service with its duration and its hours in Meteor’s diary, or connect it to the event types you already have in Cal.com. The booking is made in the name of the contact in the conversation, it is moved or cancelled in the same chat, and the reminder is scheduled when it is confirmed.
No, and it is worth knowing before you buy: the Facebook and Instagram connectors publish (photo, carousel, story and reel), they do not read comments. What the Met does handle are direct messages on Instagram and Messenger, because there it is a conversation channel like WhatsApp or the chat on your site.
Yes. The Rappi operations take a store identifier, so each location is run separately from the same workspace, and a single registration can subscribe several stores at once. With one location you set it as the default and never mention it again. The customer’s preferred location is also kept as a field on their contact.
Other industries
Meteor also fits…
Ready to automate your business?
Book a live demo and watch the Mets of Meteor working on your own operation.