WhatsApp table bookings in India: the honest operator guide

Ask an Indian diner how they booked their last table and the answer is rarely an app. It is a WhatsApp message: "Table for 4 tonight, 8 pm?" This is true at every level of the market. Even Masque in Mumbai, one of the country's most celebrated tasting-menu restaurants, tells guests on its own reservations page to call or WhatsApp to book. No published survey breaks down Indian reservation channels between phone, WhatsApp and platforms, so we will not pretend one exists, but any restaurateur who has worked a Saturday service knows where the bookings come from.

Search for advice on handling those bookings, though, and almost every page that ranks is a chatbot vendor selling its own tool. This guide is different: it is the neutral, operator-side playbook. How to take WhatsApp bookings well with the free tools you already have, where a chat thread genuinely breaks down, what the messaging rules actually say, and how to pair WhatsApp with a proper reservation book without losing the channel your guests love.

Full disclosure before we start: we build a free online reservation system ourselves, and it does not send WhatsApp messages. We will be precise about what it does and does not do, and just as precise about everyone else.

Why WhatsApp became India's default booking channel

India is WhatsApp's largest market, with industry estimates putting it at over 500 million users, and the app long ago stopped being a messenger and became infrastructure. Guests use it to talk to their tailor, their society group and their bank, so messaging a restaurant feels like the normal way to book, not a workaround.

For the restaurant, the appeal is obvious:

• Zero friction for the guest. No app to download, no account to create, no form. One message and the conversation has started.
• Zero commission. Unlike bookings that arrive through an aggregator, a WhatsApp booking costs nothing per cover.
• A direct relationship. The guest has your number, you have theirs, and nobody sits between you.
• It handles the messy cases. "We will be 15 minutes late", "Can you do a Jain thali for my mother-in-law?", "Make it 12 people, not 8": conversations absorb complexity that rigid forms cannot.

Those strengths are real, which is exactly why the channel deserves to be run properly rather than left to whoever happens to be holding the phone during service.

How to take WhatsApp table bookings well

You do not need a chatbot or a paid platform to run WhatsApp bookings professionally. The free WhatsApp Business app, used with discipline, covers a single outlet.

Set up the Business profile completely

Download WhatsApp Business (not personal WhatsApp) and fill in every field: restaurant name, address with a map pin, opening hours, website or booking link, and a one-line description. Add your menu to the catalogue so guests stop asking you to send a photo of it. A complete profile answers half the questions before they are typed, and it signals that messages to this number are read and acted on.

Write quick replies for the booking script

WhatsApp Business lets you save quick replies, short templates you insert with a keystroke. Build the booking script into them so every staff member collects the same details every time:

• Date and time requested
• Number of guests (covers)
• Name and mobile number
• Veg, non-veg, pure veg or Jain preferences, and any allergies
• Occasion and seating request, if any

Add quick replies for the common follow-ups too: directions, parking, your cancellation policy, and a polite line for guests who prepone or postpone their booking at the last minute. The goal is that a booking takes four messages, not fourteen.

Confirm in writing, every time

A booking does not exist until you have sent a confirmation message that repeats the date, the time, the number of covers and the name. That one message prevents most "but I said Sunday, not Saturday" disputes, and it is the natural place to state your policy for large tables: if you take an advance for groups, say so here, before the guest considers the table confirmed. The same logic applies to booking confirmations and reminders on any channel: written, immediate, unambiguous.

Log every booking in one central place

This is the step most restaurants skip. A booking that lives only in a chat thread on one phone is invisible to the host stand, the kitchen and the other phone. Whatever you use as the master record, a paper diary, a spreadsheet or a digital reservation book, the rule is absolute: no booking is confirmed until it is written in the one place everyone can see.

Where WhatsApp-only bookings break down

Run bookings purely in chat threads for a few months and the same failure modes appear. None of them is the guest's fault; they are structural.

No availability grid, so double bookings happen

WhatsApp knows nothing about your floor. It cannot see that table 7 seats four, that the 8 pm slot is full, or that a party of 10 blocks three tables. Whoever answers the message has to reconstruct availability from memory or from a diary that may be out of date, and on a festive Saturday that reconstruction fails. The result is the worst moment in hospitality: two families at the door, one table.

Bookings scattered across phones and staff

The manager's phone has some threads, the owner's has others, and the number on the Instagram bio may be a third. When a staff member leaves, their chat history, and the guest relationships inside it, can walk out with them. Your guest database should not live in anyone's pocket. The problem compounds with the phone itself: we have written about what ringing phones do to a restaurant during service, and a buzzing WhatsApp number is the same interruption in silent mode, demanding answers while your team is plating and serving.

No reminders and no no-show protection

A chat confirmation on Tuesday does nothing on Saturday. Nobody on the team has time to scroll back through threads and manually remind every booking, so reminders simply do not happen, and the table that was booked ten days ago quietly becomes a no-show. There is no published Indian no-show statistic from any primary source, so we will not invent one, but the mechanics are universal: unreminded bookings fail more often, and a chat thread offers no way to attach a deposit or any other commitment to the booking. We cover the full India playbook, advances via UPI payment links included, in our guide to reducing no-shows in Indian restaurants.

Outbound messages have rules

Replying to a guest who messaged you is unrestricted. Messaging guests first is not. Meta's policy requires an explicit opt-in before business-initiated messages, the opt-in must name your business, and on the WhatsApp Business API, promotional messages use marketing templates that Meta reviews and that carry a one-tap unsubscribe. Blast your chat list with Diwali offers without consent and you risk your number's standing on the platform. SMS is stricter still: any commercial SMS in India requires DLT registration under TRAI's rules, tightened by the February 2025 amendment. Transactional confirmations are fine on both channels; marketing needs consent, and the distinction is enforced.

The hybrid setup: WhatsApp front door, reservation book behind it

Here is the part the chatbot vendors will not tell you: you do not have to choose between WhatsApp and a reservation system, and you do not need to pay for automation to connect them. The hybrid setup keeps WhatsApp as the front door your guests already use, and puts a booking link behind it.

It works like this:

1. Keep your WhatsApp number everywhere it already is: Google Business Profile, Instagram bio, menu cards, the sticker on the door.
2. Answer booking requests with a link. A saved quick reply does it: "We would love to have you. Pick your table here and you will get instant confirmation: [link]. Or tell me the date, time and number of guests and I will book it for you." Guests who like self-service click; guests who prefer chatting keep chatting, and you enter their booking yourself.
3. Every booking lands in one reservation book. Online bookings, WhatsApp bookings you typed in, phone bookings and walk-ins all sit on the same grid, with real availability, so double bookings stop being possible.

This is where our own tool fits, so here is the honest version. ViteUneTable's free version gives you exactly that back end: your own booking page, unlimited bookings, 0% commission, custom questions (so the page itself asks about veg, Jain or allergy preferences), and guest pages in 37 languages, which matters in Goa and the metros where international tourists book. The free version has no time limit and no cover cap.

Now the limits, stated plainly. ViteUneTable does not send WhatsApp messages, and it does not send SMS. Automated reminders exist in the Standard pack at 29 € per month excluding tax (about ₹3,150 at October 2026 rates) and they go by email. If automated WhatsApp reminders are the one feature you refuse to live without, a platform that offers them, such as Eat App, meters WhatsApp messages per plan on paid tiers, 200 to 1,500 messages a month depending on the tier, priced in US dollars. We would rather tell you that than pretend. Our Anti No-Show pack at 49 € per month (about ₹5,300 at October 2026 rates) adds a card guarantee on bookings, a bank imprint rather than a charge; given how India pays, that is strongest for premium rooms and international guests who book with cards, while for most Indian tables an advance collected over a UPI payment link remains the practical commitment tool, and you can run that alongside the booking system today. Billing is in euros, with no INR or UPI payment for the subscription itself; the free version is the risk-free way to find out whether any of that bothers you.

Frequently asked questions

Can guests book a table on WhatsApp?

Yes, and in India millions do: the guest messages the restaurant, the restaurant confirms the date, time and number of covers in writing. The booking is only as reliable as the restaurant's record-keeping behind the chat, which is why the confirmation message and a central reservation book matter more than the channel itself.

Do I need a WhatsApp chatbot to take table bookings?

No. A single outlet can run WhatsApp bookings on the free WhatsApp Business app with a complete profile, quick replies and a strict confirm-and-log routine. Chatbots and API platforms automate the conversation, at a price; the cheaper fix for most restaurants is a booking link sent as a quick reply, with every booking landing in one reservation book.

Can I send booking reminders on WhatsApp?

Replying inside an open conversation is always fine. Business-initiated reminders through the WhatsApp Business API use Meta-approved utility templates and require the guest's opt-in, which a booking form can collect. Some reservation platforms bundle metered WhatsApp reminders on paid plans; ViteUneTable does not send WhatsApp messages, its automated reminders are email-based.

Is WhatsApp marketing to past guests allowed in India?

Only with consent. Meta's policy requires a clear opt-in naming your business before promotional messages, and marketing templates carry a one-tap opt-out. India's DLT registration regime applies to SMS rather than WhatsApp, but the direction of travel is the same everywhere: transactional messages are safe, promotions need permission.

What should a WhatsApp booking confirmation include?

Date, time, number of guests, the name the booking is under, and your cancellation terms if you have any, including any advance required for large tables. One message, sent immediately, repeated back in full. It is the cheapest no-show insurance there is, and it protects both sides if plans change.