WhatsApp marketing for cloud kitchens: rules, a campaign plan and costs
WhatsApp is where a cloud kitchen's customers already read their messages — which is exactly why Meta polices it more tightly than email. Done right it brings people back without annoying them. Here are the rules, a campaign plan built around how cloud kitchens actually work, and what it costs.
Key takeaways
- A cloud kitchen's best campaigns are timed to meals: lunch deals before noon, dinner combos before 7 pm.
- Direct-order customers are worth keeping; offers should reward ordering direct.
- New dishes and brands are news — with a real photo.
- A lunchtime message to 3,000 opted-in customers costs about ₹2,589 on the July 1, 2026 rate card.
On this page (31 sections)
- 1.The rules cloud kitchens have to follow
- 2.Consent for direct customers
- 3.A campaign plan for a cloud kitchen
- 4.Meal-time campaigns
- 5.What it costs
- 6.Rewarding direct orders
- 7.New dishes and new brands
- 8.Where campaigns go wrong
- 9.Measuring what a cloud kitchen's campaigns earn
- 10.Segments a kitchen already has
- 11.Writing a meal-time message
- 12.What campaigns cost
- 13.Frequency
- 14.Meal plans as a campaign
- 15.Launching a new virtual brand
- 16.Photos that make people hungry
- 17.Lapsed direct customers
- 18.Consent and quality rating
- 19.Measuring
- 20.Match days and festivals
- 21.Writing for a hungry reader
- 22.Offices and corporate lunches
- 23.Rainy-day and late-night messages
- 24.Segmenting by brand
- 25.Timing and frequency together
- 26.Welcome for new direct customers
- 27.Offers that protect margin
- 28.What campaigns should never do
- 29.Pre-orders for busy slots
- 30.Photos per brand
- 31.Frequently asked questions
1.The rules cloud kitchens have to follow
Meta allows promotional messages only to people who agreed to receive them, only as approved marketing templates, and only with an easy way to stop. For a cloud kitchen the practical question is where consent comes from. Direct orders — through your own link or WhatsApp catalogue rather than a delivery app — are where you finally get the customer's number and consent. A number printed on an invoice is not consent.
2.Consent for direct customers
Collect marketing consent from customers who order directly — a button on the order confirmation — and from QR codes in packaging. Never import aggregator customer data for marketing.
3.A campaign plan for a cloud kitchen
Build campaigns on moments that already happen in your customer's relationship with you, not on a calendar of generic promotions. The goal is moving repeat customers from aggregators to direct orders: a direct-order menu, a combo only available on WhatsApp, a reorder of their usual.
In practice, for a cloud kitchen:
- Customer orders directly on WhatsApp — Bot takes the order, generates invoice, and collects payment — zero commission. (service reply)
- Live delivery updates sent automatically — Order confirmed, out for delivery, and delivered — each update sent on WhatsApp. (utility template)
- Post-delivery re-order prompt — After delivery, an automated thank-you with a one-tap re-order link. (utility template)
- Win-back for 7-day inactive customers — Customers who haven't ordered in 7 days get a personalised re-order offer. (marketing template)
Order and dispatch updates in real time; promotions just before lunch and dinner decision windows, when people open food apps. Half of this plan is not "marketing" in Meta's sense. Confirmations and updates are utility messages — cheaper, and they build the trust the promotional ones depend on.
4.Meal-time campaigns
| When | Campaign | Who |
|---|---|---|
| Weekdays 11:30 am | Office lunch combos | Customers who order at lunch |
| Evenings 6:30 pm | Dinner combos, family meals | Dinner regulars |
| Friday and Saturday | Weekend feasts, party packs | Families and groups |
| Match and festival days | Party platters | All opted-in |
| Monsoon evenings | Comfort food specials | All opted-in |
5.What it costs
Meta charges each delivered marketing message. A campaign to 1,000 opted-in customers in India costs about ₹863 plus GST in Meta fees; the same send elsewhere:
| Market | Marketing message | Utility message |
|---|---|---|
| India | ₹0.8631 | ₹0.115 |
| United States | $0.0250 | $0.0034 |
| United Kingdom | $0.0635 | $0.0220 |
| UAE | $0.0499 | $0.0157 |
Meta list rates, July 1, 2026. India in INR, plus 18% GST.
Reputoo does not add a per-message markup; you pay Meta's rate and your plan.
6.Rewarding direct orders
Discounts on aggregators cost commission on top. On direct orders, a loyalty stamp, a free dessert on the fifth order, or a direct-only combo rewards customers for ordering direct without training them to wait for discounts. Tell them about it in the order confirmation and in occasional campaigns.
7.New dishes and new brands
A new dish or a new virtual brand from your kitchen is news for your direct customers. One real photo, the price, and "order now" at meal time. Existing customers are the fastest way to get the first orders a new brand needs.
8.Where campaigns go wrong
These are the problems cloud kitchens are usually trying to fix with WhatsApp:
- Zomato/Swiggy commissions eat your margin.
- Customers order once, platforms own them. Zomato knows your customers. You don't. They can recommend competitors on your next order.
- Repeat orders leak to the aggregator. A customer who ordered direct last week orders through Zomato this week, because nothing reminded them you exist.
A broadcast fixes none of them on its own. Segment first — recent customers, lapsed ones, people who asked about a specific thing — and send each group the one message that matters to it. Smaller, relevant sends get more replies and fewer blocks than one big blast.
9.Measuring what a cloud kitchen's campaigns earn
Reads show a message arrived; replies, bookings and orders show it worked. Reputoo attributes revenue to the campaign that brought each customer back, so you can drop the sends that only produce reads.
10.Segments a kitchen already has
- Lunch regulars — offices nearby.
- Dinner families.
- Weekend party orders.
- Brand-specific customers — biryani buyers, pizza buyers.
- Lapsed customers.
11.Writing a meal-time message
Lunch sorted? 🍛 Chicken biryani + raita + drink, ₹249, delivered by 1 pm. Order before 12:15. [Order now]
(Dish and price are an example.) Food, price, deadline, one tap.
12.What campaigns cost
At ₹0.8631 per marketing message on Meta's July 1, 2026 India rate card, a lunchtime message to 3,000 opted-in customers costs ₹2,589, plus GST. Compare with the commission those orders would have cost through an aggregator.
13.Frequency
Two or three meal-time messages a week at most, to the right segment. Daily messages to everyone get kitchens blocked — and a blocked number cannot send order updates.
14.Meal plans as a campaign
Customers who order lunch three times a week are paying delivery each time. A weekly or monthly meal plan — lunch delivered daily at a set price — suits them and gives the kitchen predictable volume. Offer it to regular lunch customers who opted in, with the menu and price.
15.Launching a new virtual brand
When you add a new brand from the same kitchen, your existing direct customers are the fastest way to its first orders. A launch message with a real photo and an introductory combo, sent at meal time to customers whose orders suggest they would like it, gets the brand going before aggregator ratings exist.
16.Photos that make people hungry
Photograph the dish as delivered — in your packaging, not on a styled plate — so what customers see is what arrives. Overhead shots of a full meal box work well on a phone.
17.Lapsed direct customers
A customer who ordered direct every week and stopped may have gone back to the aggregator for a discount, or had a bad order. One message — "We haven't cooked for you in a while; here's a free dessert with your next order" — brings some back. Send it once.
18.Consent and quality rating
Blocks lower your quality rating, which can limit how many messages you can send — including order updates. Send marketing only to opted-in customers, at meal times, a few times a week at most.
19.Measuring
Count direct orders from each message and compare their margin with what the same orders would earn through an aggregator after commission. That is the real return on a kitchen's WhatsApp marketing.
20.Match days and festivals
Cricket match evenings, festival nights and New Year's Eve drive group orders. A message a day before with party platters, a group price and a pre-order option lets the kitchen plan quantities and customers plan their evening. Pre-orders also protect you from being overwhelmed on the night.
21.Writing for a hungry reader
Short, specific and at the right time: the dish, the price, the delivery window, one button. Nobody reads a long message when they are hungry.
22.Offices and corporate lunches
Offices nearby are steady lunch customers. A message to office admins who have ordered before, with team lunch packages and a weekly schedule option, turns occasional orders into recurring ones.
23.Rainy-day and late-night messages
Rain and late nights are when people order in. A message on a rainy evening — comfort food, delivered hot — or to late-night regulars when you are one of the few kitchens open, reaches people at exactly the moment they want food. Keep these to customers who order at those times.
24.Segmenting by brand
Customers of your biryani brand may not want your salad brand's offers. Keep marketing lists per brand, and cross-promote only with a clear reason — a combo that pairs both, or a launch they would plausibly like.
25.Timing and frequency together
A message 30 minutes before a customer's usual order time is useful; the same message at 3 pm is noise. Use each customer's order history to time sends, and keep the total to two or three a week.
26.Welcome for new direct customers
A customer's first direct order is the moment to make the second one likely. A welcome after delivery — thank you, how to reorder in one tap, and the loyalty reward they are one step closer to — to customers who opted in, turns a trial into a habit.
27.Offers that protect margin
A free dessert, a direct-only combo or a loyalty stamp keeps customers ordering direct without cutting the price of every order. Test discounts on a small segment before offering them widely; kitchens run on thin margins.
28.What campaigns should never do
Never message people who ordered only through an aggregator and did not opt in with you, never send daily blasts, and never promise delivery times you cannot keep on a busy night. Each of these costs more in blocks and bad reviews than it brings in orders.
29.Pre-orders for busy slots
Encouraging pre-orders for peak slots — lunch at 1 pm, dinner on Saturday — smooths the kitchen's load. A message in the morning offering lunch pre-orders until 11:30, with a small incentive, fills the slot early and lets the kitchen prepare.
30.Photos per brand
Each virtual brand needs its own look — photos, colours and tone that match what customers see on the aggregator listing — so a direct-order message is instantly recognisable as the brand they already order from.
31.Frequently asked questions
How often should a cloud kitchen send WhatsApp promotions?
Less often than email — a relevant message every week or two to an engaged segment beats daily sends to everyone. Watch your quality rating in WhatsApp Manager; if it drops, send less and segment more.
Can cloud kitchens send WhatsApp broadcasts to customers who never opted in?
No. Meta requires opt-in before a business starts a conversation, and messaging people who did not ask is the fastest way to get a number restricted. Collect opt-in at the moments customers already give you their number.
When should a cloud kitchen send offers?
Just before meal decisions — around 11:30 am for lunch, 6:30 pm for dinner — to the customers who order at those times.
How can a cloud kitchen reward direct orders?
With loyalty stamps, a free item on a set order count, or direct-only combos — rather than deep discounts.
Can a cloud kitchen message aggregator customers?
Only customers who opted in directly, for example through a QR code in the packaging. Aggregator data should not be used for marketing.
Should a cloud kitchen offer meal plans on WhatsApp?
Yes, to regular lunch customers who opted in — a daily lunch plan at a set price gives them convenience and the kitchen predictable volume.
Should each cloud kitchen brand have its own marketing list?
Yes. Keep lists per brand and cross-promote only with a clear reason, such as a combo that pairs both.
What should a cloud kitchen send new direct customers?
A welcome after the first delivery with a one-tap reorder and their loyalty progress — to customers who opted in.
Can a cloud kitchen encourage pre-orders on WhatsApp?
Yes — a morning message offering lunch pre-orders until a cut-off smooths the kitchen's load and fills peak slots early.
Can I send offers to my past customers?
Yes. Build your direct customer list from WhatsApp orders and send broadcast campaigns — new dishes, weekend combos, loyalty offers — with zero platform involvement.
Do I need a separate WhatsApp number for order management?
Ideally yes — a dedicated WhatsApp Business API number for your cloud kitchen. Reputoo helps you set one up or connect your existing number in under 5 minutes.
Set up WhatsApp marketing for your business
1,000+ businesses onboarded · Member of NVIDIA Inception · Official WhatsApp Business API, no per-message markup.