WhatsApp Restaurant Table Booking for India

Sixty seconds for a single-outlet restaurant that picks one of our four preset onboarding cards (Fine Dining, Casual Dine, Cafe, Banquet Hall). You add tables once, define merge groups (which tables combine), set the advance amount (default ₹500), and drop the Restaurant Booking node into any flow. Done. No code.

Smallest-fit single table first — if a guest party of 4 books and a 4-seater is free, that wins. If no single table fits (party of 7, no 8-seater free), the allocator scans active merge groups and picks the smallest combined-capacity group that still satisfies the party size. You configure which tables can be merged in the admin panel — the system never invents combinations you have not approved.

₹500 is large enough to filter no-shows (the single largest revenue leak in Indian dine-in) but small enough that customers will pay without thinking on WhatsApp. The advance is fully configurable per restaurant — banquet halls typically set ₹2,000, cafes set ₹200, fine dining stays at ₹500. The advance can be set to adjust against the final bill automatically.

Yes. The flow captures only the fields you actually need to seat a guest — name, phone (already inside WhatsApp), party size, date, time, optional special requests. No marketing opt-in is bundled into the booking flow itself. Customer consent is explicit and scoped to the booking purpose. Retention is configurable. All processing happens on India-resident infrastructure with audit logs.

Yes. We never see or store the customer card / UPI ID — the payment leg is handled end-to-end by Razorpay, which is PCI DSS Level 1 certified. We receive only the payment ID and capture status via Razorpay webhook. The funds settle directly to your Razorpay account on Razorpay’s standard T+2 cycle.

In MVP, the customer messages your number and your manager updates the booking row from the admin panel (cancel / reschedule / mark no-show). Refunds for cancellations are processed manually from your Razorpay dashboard. Automated refund flows and customer self-serve reschedule are on the Phase 2 roadmap.

MVP supports one restaurant per tenant (one outlet, multiple tables and merge groups). Multi-outlet support — where each outlet has its own table inventory and the customer picks an outlet first — is the Phase 2 add-on (Chain plan at ₹2,499/mo). If you already run a chain, talk to us first — we are prioritising the Phase 2 build by inbound demand.

Two pre-approved Meta WhatsApp template messages fire on successful booking — one to the customer (booking summary + advance receipt) and one to the manager number you configured (heads-up with party size, time, table name or merge group, special requests). Template names are configurable per tenant in the Restaurant Settings panel.

Bookings are written to a structured database row with all the fields a POS or analytics tool needs (customer, date, time, guests, advance, table). You can export to CSV from the admin panel. Optional Google Sheets sync writes each booking to a shared sheet you configure (gsheet_id + service-account JSON). POS integrations (PetPooja, Posist, Limetray) are on the Phase 2 roadmap.

Bundled free on the Pro plan (no extra charge). Stand-alone Add-on for tenants on Starter is ₹999 / month — covers one restaurant, unlimited tables and merge groups, unlimited bookings, both WhatsApp templates, Razorpay advance, admin panel. Multi-outlet Chain plan is ₹2,499 / month and ships in Phase 2 (Q3 2026).