Google Review Collection Bot for restaurants

What is included in the setup

• Post-visit review request flow
• Unhappy-customer catch before they post
• Review link with QR for the counter
• Monthly review growth report

What you need before the call

• The accounts the setup connects to (WhatsApp, Google or Meta)
• Your services, prices, timings and address
• Who receives alerts and reports
• Approval for the content the setup will send in your name

A normal day at a restaurant with this setup

1. Guest pays the bill at the counter around 9 PM (dinner rush) — the cashier or the captain asks for the mobile number while handing over the printed bill, or the guest scans the QR code stuck near the billing counter.
2. Within 10-15 minutes of the table being cleared, the bot sends a WhatsApp message: 'Thank you for dining with us today. How was your experience?' with a 1-5 tap-to-rate option.
3. If the guest taps 4 or 5, the bot replies instantly with the Google review link and a one-line message like 'Glad you enjoyed it! A quick review helps us a lot' — guest taps and posts from their own phone.
4. If the guest taps 1, 2 or 3, the bot does NOT send the Google link. Instead it says 'Sorry to hear that. Could you tell us what went wrong?' and routes the reply to the manager's WhatsApp or a shared number, so it never turns into a public 1-star review.
5. Manager or owner checks the flagged replies each morning before opening (around 11 AM) and calls back unhappy guests directly — table wait, food temperature, and billing mismatch are the usual complaints that come in.
6. The printed QR code stays at the billing counter and on takeaway/Swiggy-Zomato packaging inserts for walk-ins and delivery customers who weren't captured at the table.
7. On the 1st of every month, the care plan sends a report to the owner's WhatsApp or email: number of requests sent, reviews posted, average rating trend, and how many unhappy guests were caught before posting.

Rules and platform limits it works within

WhatsApp Business policy: review requests are sent as a template message triggered by a genuine transaction (the bill), which keeps it within WhatsApp's business-initiated conversation rules — it is not bulk marketing.

TRAI/DLT rules for SMS: if a restaurant asks for an SMS fallback for guests without WhatsApp, the sender ID and message template are registered on the DLT platform first, as required for any transactional SMS from India.

DPDP Act 2023: the phone number is collected only for the review request, stored against the visit record, and not shared with any third party. Guests who reply 'stop' are removed from future messages.

The setup does not offer legal advice — it only follows the platform and telecom rules that apply to sending these messages.

What the leak costs: a worked illustration

Assume a restaurant serves 60 covers a day and 6-8 unhappy tables go unnoticed each week — a wrong order, a long wait, a cold dish — because the guest doesn't complain at the counter, just leaves and posts a 2-star review later. One bad public review can sit on the listing for months and put off other diners searching nearby.

At Rs 7,000 setup plus Rs 1,500/month, the care plan costs about Rs 50/day. If catching even 2-3 unhappy guests a week before they post, and converting a few more happy guests into 5-star reviews, keeps the average rating from slipping below 4.0, the plan pays for itself against the cost of one lost weekend's walk-in footfall from a poor rating. This is an illustration, not a guaranteed outcome.

Questions restaurant owners ask

Will this bot ask for a phone number and then message people about table bookings or menu questions?

No. It only sends the post-visit review request after a bill is paid. It doesn't handle table bookings or menu queries — those still go through your front desk or captain as usual. This setup is focused only on reviews.

What happens to the 1-star ratings — does the bot hide them from Google?

The bot never touches Google directly. It simply doesn't send the review link to guests who rate their experience poorly in the WhatsApp message. It's the guest's choice not to post, same as any restaurant asking 'how was everything?' before someone leaves.

Do we need a smartphone or POS integration for this to work?

No POS integration needed. Numbers can be collected manually at billing or through the QR code at the counter. It works with a basic WhatsApp Business number — no new hardware, no software installed on your existing billing system.