Order and delivery updates for restaurants and cloud kitchens in India
Order and delivery updates for an Indian restaurant means pushing each stage of the ticket — accepted, in the kitchen, ready, picked up, delivered — into the customer’s WhatsApp thread automatically, with the rider’s name and the delivery OTP. It removes the “how long more?” call that arrives during peak service, when the kitchen can least afford to answer it.
Built for Indian businesses 🇮🇳 · Plans from ₹1,999/month · 0% markup on WhatsApp messages
What the customer actually sees
Not a mock-up of a feature — the real message shape for a food & beverage business, in the price band and language this vertical works in.
WhatsApp Business
WhatsApp Business API
- Business: Order #AK-2214 accepted. In the kitchen now — ready in about 25 minutes.
Triggered on KOT acceptance
- Customer: How long more?
- Business: About 8 more minutes — it’s plating now. Rider Suresh is already at the outlet.
AI agent answered from live ticket state · no staff time used
- Business: Picked up. Suresh is on the way, arriving in roughly 12 minutes. Delivery OTP 4417.Track rider ↗
Triggered by rider assignment · OTP delivered in-thread
- Business: Delivered. Hope the Paneer Butter Masala was good — one tap tells us how we did.Rate this order ↗
Hands off to the CSAT flow
How it works
Trigger off the ticket, not a timer
KOT acceptance, ready-for-pickup and rider assignment in Petpooja, Dotpe or the WatEase kitchen view each fire their own update, so what the customer is told matches what the kitchen is actually doing.
Answer the impatient question automatically
A customer who asks “how long more?” gets an answer generated from the live ticket state instead of interrupting the pass. If the ticket has slipped, the message says so before the customer has to complain.
Hand over cleanly
Rider name, live tracking and the delivery OTP arrive in the thread, so the handover happens without a call. On delivery the thread hands off to the feedback flow.
What the kitchen gets back
No invented ROI percentages — these are the mechanisms and the market facts behind them. Your numbers depend on your volume, and the dashboard measures each one.
~₹0.115
Meta’s published India price for a utility-category WhatsApp conversation (order/payment/delivery updates) — what a recovery or reminder nudge actually costs to send.
Source: Meta for Developers — WhatsApp pricing500M+
WhatsApp users in India — Meta has cited India as WhatsApp’s largest market worldwide.
Source: Meta NewsroomJuly 1, 2025
The date Meta transitioned WhatsApp Business Platform billing from per-conversation to per-message for template messages.
Source: Meta for Developers — WhatsApp pricingPeak-hour calls the outlet does not take
The “how long more?” call always arrives during the exact window when the kitchen has least capacity to answer it. Pushing the status first, and answering the follow-up from live ticket state, removes it.
If 120 orders on a Friday night generate status calls on even 15% of tickets, that is 18 calls landing in a three-hour window, each pulling someone away from the pass at the worst possible moment.
Complaints downgraded to expectations
A delay the customer was told about is an inconvenience; a delay they discovered by waiting is a one-star review. Proactive delay messaging changes which of the two you get.
Every late ticket that is flagged proactively rather than discovered by the customer is one fewer refund conversation and one fewer public review written in frustration.
Cleaner handover at the door
The rider’s name and the delivery OTP in the thread mean the customer knows who is arriving and what to say, so the doorstep exchange does not need a phone call.
Removing the pre-delivery call from every order removes a step that fails whenever the customer is on another call, in a lift, or has the phone on silent.
A 120-order Friday night, two ways
| Without WatEase | With WatEase | |
|---|---|---|
| Who answers “how long more?” | Whoever is nearest the phone, mid-service | An automated answer drawn from the live ticket |
| When the customer learns about a delay | When they call to complain | Before they call, from the outlet |
| How the rider handover works | A phone call from an unknown number | Rider name, live tracking and OTP already in the thread |
| Where the ETA comes from | An optimistic fixed promise set at order time | Kitchen state, updated as the ticket moves |
| Cost per update | Staff time during peak service | One Meta utility conversation, billed at cost |
Order volumes and call rates above are an illustrative scenario for working the arithmetic, not a claim about your outlet or an average across WatEase customers. Use your own ticket and call logs.
Set this up in WatEase
Five steps, each pointing at the actual screen you do it on. Most teams have this running the same day.
- 1
Connect the kitchen system
Link Petpooja or Dotpe, or use the built-in kitchen view, so KOT acceptance, ready and pickup events reach WatEase as real triggers rather than manual updates.
Settings → Integrations → POS
- 2
Submit the status templates
Submit utility templates for accepted, ready, picked up and delivered, with variables for order number, ETA, rider name and OTP.
Marketing → Templates
- 3
Set realistic prep times
Configure per-item or per-category prep times and let the ETA move with live kitchen load, rather than promising a fixed number the kitchen misses at peak.
Orders → Kitchen settings
- 4
Turn on the delay rule
Add a rule that messages the customer automatically when a ticket passes its promised time, so a slip is communicated rather than discovered.
Automation → Journeys
- 5
Point the AI at ticket state
Enable the AI agent for order-status questions so “how long more?” is answered from the live ticket without interrupting service, and route anything else to the inbox.
AI → Agents
Why status updates matter more in Indian food delivery
Indian food delivery runs on tight promise windows, dense traffic and last-mile handovers that frequently depend on a phone call. The notification layer is doing operational work here, not decoration.
- The delivery OTP is standard practice in Indian last-mile handover. Putting it in the thread ahead of arrival removes a call that fails whenever the customer cannot pick up.
- Traffic variance in Indian metros makes a fixed ETA promise unreliable. An ETA that moves with kitchen and rider state is more honest and generates fewer complaints.
- Order status messages are utility-category conversations about the customer’s own order — no marketing consent required, and priced below marketing sends.
- Regional language matters at the doorstep: the person receiving the food is often not the person who ordered it, and the rider handover message may be read by either.
- A refund driven by a missed promise is worse than a delay that was communicated, because Meta scores your number on user feedback and repeated complaints can cap your messaging tier.
Frequently asked questions
Which order updates are worth sending?
Accepted with an ETA, ready or picked up with rider details and OTP, and delivered with a rating prompt. Intermediate kitchen stages usually add noise rather than information the customer can act on.
Can it answer “how long more?” without a staff member?
Yes. The AI agent answers from the live ticket state in your POS or kitchen view, so the question is handled without pulling anyone away from the pass. Anything it cannot answer routes to the shared inbox.
How does the rider OTP reach the customer?
It is delivered in the same WhatsApp thread when the rider is assigned, alongside the rider’s name and a tracking link, so the doorstep handover does not depend on a phone call connecting.
What happens if the kitchen falls behind?
A delay rule messages the customer automatically once the ticket passes its promised time. A communicated delay produces a very different reaction from one the customer discovers by waiting.
Does this work if I have no POS?
Yes. The built-in WatEase kitchen view provides the same accepted, ready and picked-up triggers, so you can run the full notification sequence without buying a POS first.
Do these messages need marketing consent?
No. They are utility-category conversations about the customer’s own order. Marketing consent under the DPDP Act is required for promotional sends, which these are not.
What does the sequence cost per order?
Three or four Meta utility conversations, billed by Meta at cost — WatEase adds 0% markup on WhatsApp messages. On a ₹500 order that is a rounding error against aggregator commission.
What return can a food & beverage business expect from kitchen & delivery updates on WhatsApp?
Through specific mechanisms rather than a single ROI number: peak-hour calls the outlet does not take; complaints downgraded to expectations; cleaner handover at the door. If 120 orders on a Friday night generate status calls on even 15% of tickets, that is 18 calls landing in a three-hour window, each pulling someone away from the pass at the worst possible moment. WatEase publishes no invented ROI percentages — your numbers depend on your volume, and the dashboard measures each mechanism.
Go deeper
Other jobs food & beverage businesses run on WhatsApp
Kitchen & delivery updates in other industries
The capabilities behind this
Zoom out to WhatsApp commerce for food & beverage, or read order & delivery updates across every industry.
Capabilities and competitor comparisons reflect what we could verify as of June 2026. Worked examples on this page are illustrative scenarios, not averages across WatEase customers.