AI chatbot for restaurants on WhatsApp: takes orders, books tables and confirms payments

It covers the service companies usually search for as a restaurant chatbot, but implements it as a Met: an AI agent that not only answers, but also uses the menu, takes the order, calls authorized integrations and hands exceptions to the team. Its exact scope depends on the connected systems and keeps the operational limits described on this page.

With Fudo, yes, and that is what ends the typing by hand: the Met reads your menu with its prices, looks at the tables in the dining room and creates the ticket on a table, which is what gets the order to the kitchen. After that it answers for the state of each dish. Two things worth knowing before you buy: the scope is dine in service, because Fudo only accepts creating that kind of sale through this API and requires the table, so delivery and takeaway stay outside; and the integration is still being finished against the first real accounts, so today it comes with hands on support. For other points of sale there is no connector.

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.