WhatsApp chatbot for restaurants in Mexico City

Your customers already message you on WhatsApp to book a table, ask about your hours or order takeout. This guide explains what a chatbot can answer, what rules WhatsApp sets, what Mexico's personal data law requires and how to tell if it's right for your restaurant.

Updated November 3, 2026

What it is and what it isn't

A WhatsApp chatbot for restaurants is a program that answers the messages that come in to the restaurant's number. The simplest ones reply with a menu of options. The ones that use artificial intelligence understand what the person writes in their own words and reply in a normal conversation, using the information the restaurant gave it.

It runs on the WhatsApp Business API, the business version of WhatsApp that lets you connect a system to your number. It's not the WhatsApp Business app on your phone, but it can work alongside your team: the chatbot answers the repetitive questions and passes to a person whatever needs a person.

What it isn't: a replacement for your reservation system, your point of sale or the people working the floor. It's the first reply, at any hour, with the right information.

What it should answer

In a restaurant, most messages repeat. Before installing anything, it's worth going through a month of conversations and pulling out what people always ask. Usually it's this:

A typical conversation, at the hour when nobody is looking at the phone:

WhatsApp's rules

WhatsApp treats two situations differently, and it's worth being clear on them before choosing a provider.

When the customer messages you first

Each customer message opens a 24-hour customer service window. Within that window you can reply with free-form messages, which is what the chatbot does. If the customer writes again, the window resets for another 24 hours.[1]

When the restaurant messages first

To message someone outside that window, for example to confirm a reservation the next day or announce a new menu, you have to use templates approved by WhatsApp, and the person has to have agreed to receive messages from the restaurant.[1] WhatsApp Business policy also requires that permission to be clear and that you respect anyone who asks to stop receiving messages.[2]

Personal data in Mexico

A chatbot that stores names, phone numbers and reservations handles personal data. In Mexico that's governed by the Ley Federal de Protección de Datos Personales en Posesión de los Particulares (Federal Law on the Protection of Personal Data Held by Private Parties), a new version of which was published in the Diario Oficial de la Federación (Official Gazette) on March 20, 2025, replacing the 2010 law.[3]

For a restaurant, the key piece is the privacy notice: telling the person what data you keep and what you use it for, before or at the moment you ask for it. A link to the notice in the chatbot's first message is a simple way to comply. If you later want to use that data for something else, like sending promotions, you need to have said so in the notice.[3]

This guide doesn't replace a lawyer. If your restaurant handles data for a lot of customers or shares it with other companies, it's a good idea to have one review your notice.

How it connects with what you already use

The chatbot is only as useful as it is informed, and it needs to know what your team knows. So before thinking about the conversation, get three things in order:

• Availability. If you use a reservation system, the chatbot has to check it or write to it. If you take reservations in a notebook or a spreadsheet, the first step is moving that to a place the chatbot can read.
• Information about your place. Hours for each day, the current menu, group policies, parking, pets. Whatever isn't written down, the chatbot doesn't know.
• Who it alerts. A name and phone number for each type of case: events, complaints, suppliers.

With that in place, every conversation is saved as a contact, and the restaurant starts to have something it didn't have before: a list of who booked, when and how many times they came back.

How to tell if it's working

Replying fast matters. In a study published in Harvard Business Review, companies that contacted a lead within the first hour were almost seven times more likely to qualify them than those that waited one more hour.[4] The study looks at business sales in general, not restaurants, but the logic holds: someone asking for a table at eleven at night usually books wherever they get an answer first.

For your restaurant, it's enough to look at four numbers before and after installing it:

1. Time to first response.
2. Messages that arrive outside business hours.
3. Conversations that end in a reservation or an order.
4. Reservations that don't show up.

If you don't have those numbers today, that's your first finding.

Mistakes to avoid

• A chatbot with no way out. There always has to be an option to talk to a person, and the chatbot has to recognize when to offer it.
• Hiding that it's an AI. Saying so in the first message avoids misunderstandings and doesn't cost you bookings from people who just want a table.
• Promising what it can't see. If the chatbot isn't connected to real availability, it shouldn't confirm tables: it should take the request and say someone will confirm it.
• Using the number for promotions without permission. Besides going against WhatsApp policy,[2] it's the fastest way to get blocked.
• Installing it and forgetting about it. The menu changes, and hours change by season. Someone on the team has to check once a week what the chatbot couldn't answer.