WhatsApp for restaurants and cloud kitchens: direct orders, reservations and regulars
The delivery apps take a 20–30% cut and keep the customer's number. WhatsApp is how you take the repeat order yourself — and actually own the people who love your food.
Here's the uncomfortable math every restaurant owner already feels: a customer finds you on Zomato, loves your paneer, orders again next week — and the aggregator takes a 20–30% cut of every one of those orders, forever. Worse, that customer isn't yours. You don't have their number. The app does. So the second time they order, and the tenth, you're still paying the toll on a diner you earned fair and square.
WhatsApp changes that quietly. It doesn't replace the apps — it sits next to them. The apps bring the stranger in the door. WhatsApp is how you take the repeat order directly, keep the margin, and turn a one-time delivery into a regular.
WhatsApp becomes your restaurant's direct-ordering line. Customers browse your menu as a catalog, place the order inside the chat, and pay by UPI. On top of that you handle table reservations, send today's specials to opted-in regulars, and ask for feedback right after the meal — so you catch a bad experience before it turns into a one-star review.
The commission problem, said plainly
Nobody's telling you to quit the aggregators. For a new kitchen or a new dish, that discovery is worth paying for — the apps put you in front of people who've never heard of you, and that's genuinely hard to do on your own. The first delivery through an app is money well spent.
The problem is the tenth. Once someone has ordered from you five, ten, twenty times, you're still handing over 20–30% on food they'd happily order direct — if only they had an easy way to. They don't have your number saved. They don't know you have a WhatsApp line. So they open the app out of habit, and you pay again.
The fix isn't dramatic. It's just giving your regulars a direct line and a reason to use it: faster, the same food, sometimes a small perk for ordering direct. The first order can be theirs. The repeat should be yours.
Take direct orders on WhatsApp
Start with the menu. In the WhatsApp Business Platform you can load your dishes into a catalog — name, photo, price, a line of description — and customers browse it inside the chat, the same way they'd scroll a delivery app. They tap what they want, it builds a cart, and the order lands in your inbox.
From there you confirm and take payment. Send a UPI pay-link right in the conversation so the customer pays before the kitchen fires the order — that alone kills the cancelled-cash-order problem that eats into cloud kitchen margins. If you still want to offer cash on delivery for regulars, a gentle prepaid nudge often flips them to paying upfront anyway.
The whole flow — browse, order, pay — happens in one thread the customer already has open all day. No app download, no login, no "your order is being assigned to a delivery partner." We walk through the catalog-and-payment setup end to end in the WhatsApp catalog and payments guide.
Reservations and waitlists
Dine-in has its own version of the same idea. Instead of a phone call that goes to voicemail during the dinner rush, let people book a table right in WhatsApp. A no-code Flow asks the three things you actually need — date, time, party size — inside the chat, and drops a clean booking into your inbox.
Then automate the two messages that protect the table. A confirmation the moment they book, so they know it's real, and a reminder a few hours before, so they don't forget. No-shows are pure lost revenue for a full-service restaurant, and a one-line reminder — "See you at 8, table for 4 is ready. Reply CANCEL if plans changed" — quietly recovers a chunk of them. The ones who can't make it now tell you in time to give the table away.
Daily specials and bring-back campaigns
This is where restaurants either win or get themselves blocked, so be careful with it. To people who've opted in — anyone who ordered from you, booked a table, or asked to be on the list — you can send the things that actually bring them back. Today's thali. The weekend biryani that sells out by 9pm. A quiet-Tuesday offer to fill slow tables.
Done right, this is welcome. Done wrong, it's the reason people mute you. The rules are simple: only message people who asked, keep it occasional, make every send genuinely useful, and give an easy way out. Get consent the honest way — our opt-in best practices cover exactly how — and structure the sends so they read like a favour from your kitchen, not a blast. The mechanics of building and sending these are in the broadcast campaign guide.
One honest note on cost: these promotional sends go out as marketing templates, which Meta charges for per message by category and country, so treat them as a paid channel and send them like you mean it. A once-a-week special to people who love your food pays for itself many times over. A daily blast to a scraped list gets you muted and reported.
Run ordering, reservations and regulars in one place
QuickWA connects your WhatsApp number in about two minutes with Login with Facebook, then gives you a catalog with payments, no-code booking Flows, broadcasts and a shared inbox. Start on the free plan.
Start free →Catch problems before they hit your Zomato reviews
A bad meal doesn't have to become a public one-star. The trick is to reach the diner before they reach the review page. Twenty minutes after a dine-in bill or a delivery drop, send one short message: "How was everything today? 👍 or 👎".
Now branch on the answer. A thumbs-down routes straight to the manager — someone calls or messages back, fixes it, maybe sends a small make-good. That's a save you'd never get from a review site, where the first you hear of it is the rating. A thumbs-up gets a warm thank-you and a gentle nudge: "So glad! If you have a minute, a review on Zomato really helps a small kitchen like ours 🙏".
You're steering the same honest feedback two different ways — unhappy diners into a private fix, happy ones into public praise. Over a few months that quietly lifts your rating and cuts the angry surprises.
WhatsApp across the restaurant day
Here's the whole thing on one page — the moments that matter and who handles each. Some of it runs on autopilot; some of it wants a human. Get the split right and one person can run all of it during service.
| Moment | What to send | Automate or human |
|---|---|---|
| New customer | Welcome + menu catalog + "save our number for direct orders" | Automated |
| Order | Confirm items, prep time, and pack/delivery details | Automated, human for special requests |
| Payment | UPI pay-link, then receipt in the same thread | Automated |
| Reservation | Booking Flow → instant confirmation → reminder before the slot | Automated |
| After the meal | "👍 or 👎?" — bad routes to manager, good invites a review | Automated trigger, human on complaints |
| Bring-back | Today's thali, weekend offer — to opted-in regulars only | Human-scheduled broadcast |
The pattern holds whether you're a 40-cover dine-in or a delivery-only cloud kitchen: automate the predictable messages, keep a person on the moments that need judgement, and let the shared inbox make sure nothing sits unanswered mid-rush.
The bottom line
You worked hard to earn every regular. Paying an aggregator a cut on their tenth order — when they'd happily order direct — is money left on the table. WhatsApp lets you take that repeat order yourself: menu in the chat, UPI payment, a table booked without a phone call, a special that brings people back, and a feedback message that catches trouble early. Keep the apps for discovery. Keep your regulars on WhatsApp. That's the margin, and the relationship, back in your kitchen where it belongs.