The simplest way to collect reviews for a cloud kitchen is to ask in the same WhatsApp chat the order came from, a few minutes after the food is delivered, and to keep the answer in your own dashboard. A cloud kitchen has no dining room, no waiter asking "how was it", and no face at the counter. The rating request after delivery is the only moment you get to ask, and if you do not ask, the only ratings you will ever have are the ones on the delivery apps.
This post shows how reviews after every order work on Tezzu for a cloud kitchen: what the customer sees, where the rating lands, what to do with a 2-star on a Tuesday night, and how owned ratings turn into Google reviews and repeat orders.
Why a cloud kitchen's ratings live on someone else's app
On an aggregator, the rating is attached to your listing and used by the app to rank you. You can see the number. You usually cannot see which order it came from, cannot message the customer to fix it, and cannot take the rating with you if you delist. A single bad week can drop the number, and the number decides how many people see your listing next week.
That arrangement is fine for the aggregator and poor for you. The case against it is made in full in why owned reviews beat aggregator ratings. The short version: a rating you own is attached to a customer you can contact, an order you can look up, and a dish you can fix.
What an owned rating is worth to a cloud kitchen
Put rupees on it. Suppose your kitchen does 600 direct orders a month at an average of ₹280. A regular who orders three times a month is worth about ₹840 a month in revenue. If 5 percent of orders in a month come back with a low rating, that is 30 unhappy customers you now know about by name and number.
If messaging ten of those thirty with an apology and a fix keeps them ordering, that is roughly ₹8,400 a month in revenue retained, from customers who would otherwise have quietly moved to another kitchen. These are illustrative numbers, and your own will differ, but the shape holds: the rating is worth money because it tells you who to call before they leave.
| Aggregator rating | Rating you own | |
|---|---|---|
| Attached to | Your listing | A specific order and customer |
| Who can see the customer | The app | You |
| Can you reply privately | Rarely, and only inside the app | Yes, in the same WhatsApp chat |
| Used for | Ranking you against other kitchens | Fixing dishes, riders and shifts |
| If you leave the platform | Gone | Stays in your dashboard |
The post-order review request, step by step
Here is the flow from the customer's side when reviews are switched on.
- The customer orders on WhatsApp or your store page and pays by UPI, card or cash on delivery.
- Your staff move the order through accepted, preparing, out for delivery and delivered. Each change sends a WhatsApp status update.
- Once the order is marked delivered, a short message arrives in the same chat asking for a rating.
- The customer taps a rating and can add a line of comment in reply.
- The rating and the comment appear on that order in your dashboard, and against that customer in your customer list.
Two details carry most of the value. The ask is tied to the delivered status, so you never ask about food that has not arrived. And it goes to a chat that already exists, so nobody has to decide whether a link is safe to tap. The design choices behind this, and how to word the ask, are covered in automated feedback collection after every order.
What to do with the ratings each week
A rating you do not read is worth nothing. Set a fixed ten minutes every Monday morning and look at three things.
The low ratings, one by one
Open each order rated 1 or 2. Read the comment, check the items, the time of day and who delivered it. Then message the customer in the same WhatsApp chat: a plain apology, one sentence on what went wrong if you know, and something concrete for the next order. "Sorry about the cold biryani on Tuesday. We have changed the packaging for rice dishes. Your next order is on us up to ₹200." Keep it short and send it within a day.
The pattern
Look at low ratings together. If the same item keeps pulling a 3 while everything else gets 5, that dish has a problem. If the low ratings cluster between 8 and 9 pm on weekends, the problem is the rush, and the fix is covered in peak hour management. If they cluster on one rider's route, you know what to do.
The happy ones
Customers who rated 5 and left a comment are the ones to ask for a Google review, and the ones to message first when you launch a new dish. Neither of those happens automatically; the rating simply tells you who to ask.
What this looks like on Tezzu
Reviews are switched on from the dashboard settings and tied to the final order status. For a cloud kitchen that status is delivered; for pickup orders it is collected. The moment staff mark the order delivered, the rating request goes out on WhatsApp from your own number, so it reads as a message from the kitchen the customer just ate from, in Hindi or English depending on how the customer chose to chat.
In the dashboard, each rated order shows its rating and comment on the order detail. The customer list shows the same ratings against the customer, next to their order history, so when you open a low rating you can see whether this is a first-time customer who had a bad start or a weekly regular you are about to lose. Staff with the right permissions can see ratings; the owner decides who those are through roles and permissions.
Nothing is sent to Google or to an aggregator. The rating stays with the order, and what you do with it is a message from you in the same WhatsApp chat, a coupon for the next order, or a quiet change to a recipe. Ratings sit alongside revenue and customer insights in the live dashboard, so the Monday review is one screen, and the rest of what the dashboard tracks is on the features page. The step-by-step setup, including how to word the ask, is in collecting ratings after every order with Tezzu reviews.
Start collecting ratings you keep
Start the free trial, take a few direct orders, and switch reviews on. Within a week you will have ratings attached to real customers and real orders.
Start your free 7-day trialTurning owned ratings into Google reviews and repeat orders
A cloud kitchen's Google listing is what people see when they search the brand name after seeing it on Instagram or on a flyer. Reviews there matter, and the people most likely to leave a good one are the ones who just rated you 5 on WhatsApp.
So ask them, by hand, a day later: "Thanks for the 5 on Tuesday. If you have a minute, a line on Google helps a small kitchen a lot," with the review link. Only ask the happy ones. Asking everyone sends the unhappy ones to Google too, which is the outcome owned ratings exist to prevent. The wording and timing are in how to get more Google reviews.
The second use is retention. Ratings tell you which regulars are drifting: a customer whose last two ratings were 3 and 2 after a year of 5s is about to stop ordering. A message and a small coupon, sent before the silence starts, is cheaper than any campaign to win them back later. The weekly habits that keep a cloud kitchen's regulars ordering are in cloud kitchen customer retention, and the ordering setup that makes all of this possible starts at Tezzu for cloud kitchens.
Frequently asked questions
How do cloud kitchens collect customer reviews without a dining room?
By asking in the ordering channel after delivery. When orders come in on WhatsApp, the kitchen can send a rating request in the same chat once the order is marked delivered, and the customer taps a rating without leaving the conversation. On Tezzu this is a built-in feature: the request goes out automatically on the delivered status and the rating is stored against the order in your dashboard.
Can I ask for a rating on WhatsApp after an order?
Yes. A rating request after an order is a message the customer expects, because they messaged you first and the order is fresh. Keep it to one line and one tap. On Tezzu the message is sent from your own number after the delivered status, and the customer's reply, including any comment, is attached to that order so you can act on it.
What should I do when a customer gives a low rating?
Reply within a day in the same chat, apologise plainly, say what you will change if you know, and offer something concrete for the next order. Then look at whether the low rating is part of a pattern, by dish, by time of day or by rider, and fix the cause. The rating is only worth having if someone reads it and messages back.
Do owned ratings replace the delivery app ratings?
They do different jobs. An aggregator rating decides how the app ranks you and you cannot take it with you. Owned ratings are attached to customers you can contact and orders you can inspect, so they are the ones you use to fix problems and to decide who to ask for a Google review. Most cloud kitchens on aggregators will keep both for as long as they stay listed.