WhatsApp & SMS Review Requests (India)

WhatsApp Review Requests for Indian Businesses: The Complete Tactical Guide

WhatsApp is the review generation channel Indian businesses reach for first, and for good reason: near-universal adoption, high engagement compared with email, and the personal familiarity of a 1:1 message rather than a marketing blast. Almost no Western local SEO guidance covers this properly, because WhatsApp simply isn't the default customer channel in most Western markets the way it is in India.

This is a genuine India differentiator in local SEO execution, and it deserves more than a passing mention. For the broader system this channel sits inside, see Angryturtle's review generation strategy guide; for what happens to velocity once the requests start landing, see the review velocity guide; and for the general, channel-agnostic version of this advice, 21 ways to get more Google reviews.

Why WhatsApp works better than email for Indian customers

Email review requests in India tend to get buried, filtered to a promotions tab, or simply ignored because the customer doesn't check that inbox often. WhatsApp messages arrive on the same screen the customer already checks dozens of times a day, from a number that, if saved as a contact, shows the business name rather than an anonymous sender.

The message also arrives close to the interaction it's about. A patient who just left an appointment, a diner who just finished a meal, a guest who just checked out of a hotel — all of them are more likely to act on a request that lands within a few hours, while the experience is still fresh, than one that lands three days later buried in an inbox they check twice a week.

None of this means WhatsApp guarantees a review. It means the message actually gets seen, which is the precondition for everything else — and it's precisely the kind of reputation management groundwork that a general GBP management programme depends on.

Message templates by category

The best-performing templates share a shape: personalise the name, reference the specific interaction, keep it to two or three sentences, and include exactly one link.

Healthcare (clinic or hospital): "Hi [Name], hope your appointment went well today! If you have a spare 2 minutes, a quick Google review would really help other patients find us. Here's the direct link: [link]. Thank you!" See Angryturtle's healthcare local SEO hub for how this fits into a clinic's broader reputation programme.

Restaurant: "Hi [Name], great to have you with us today! If you enjoyed your meal, we'd love your feedback on Google — it means a lot to our team: [link]. Hope to see you again soon!"

Hotel: "Hi [Name], thank you for staying with us. We hope your stay was comfortable! We'd really appreciate your review on Google: [link]. It would mean a great deal to our team." See Angryturtle's hospitality reputation management guide for the fuller programme this template feeds into.

Coaching institute: "Hi [Name], thank you for joining us today! We hope the class was helpful. If you're happy with your experience, a Google review would help other students find us: [link]. Thank you!"

Retail: "Hi [Name], thank you for visiting [Store] today! We hope you love your purchase. If you have a moment, your review on Google would really help us: [link]."

None of these templates are meant to be used verbatim forever. Rotate the wording every few months so repeat customers don't receive the identical message twice, and adjust the tone to match the brand — a premium hospitality brand and a neighbourhood clinic shouldn't sound the same.

Principles that separate a working template from a dead one

Use the customer's actual name — "Hi [Name]" reads as a real message; "Dear Customer" reads as a mail-merge. Keep it brief; two or three sentences is the ceiling, because long messages get skimmed and the link gets lost in the scroll. Include one link only — the direct review link, with no other links and no paragraph of business information attached. Anchor the timing to the specific interaction — "after your appointment today," "thank you for visiting us today" — because a generic message with no timing reference reads as automated even when it isn't. And don't push for it — phrases like "if you have a moment" or "when you get a chance" keep the request low-pressure, which paradoxically gets a better response than a message that sounds like it's chasing the customer.

SMS as a fallback channel

SMS is worth keeping as a fallback for customers who don't use WhatsApp — a shrinking group in urban India but still meaningful in some demographics and in Tier 2 and Tier 3 markets. SMS has to stay under roughly 160 characters to avoid splitting into multiple messages, so the template has to be tighter: "Thank you for visiting [Business]. Share your experience on Google: [short link]. We appreciate your feedback!" A URL shortener is close to mandatory here to keep the link from eating the character budget.

Manual sending vs. the WhatsApp Business API

A single clinic or shop can run this manually through WhatsApp Business, free, with the owner or receptionist sending individual messages after each positive interaction. It works, but it doesn't scale much past a handful of requests a day before it becomes a chore that gets skipped on busy days.

Beyond that scale, the WhatsApp Business API allows automated, triggered messages tied to events — an appointment completion, a checkout, a POS trigger. This needs a WhatsApp API provider and template message approval from Meta before use; major Indian providers include Gupshup, Interakt, AiSensy, and Wati. Template approval is generally straightforward for a standard review request message, though it does add a short lead time before the automation can go live, so it's worth building into the project timeline rather than assuming it happens instantly. Angryturtle's guide to Google Business Messaging covers the parallel messaging channel inside GBP itself, which some businesses run alongside WhatsApp.

What's compliant and what isn't

A business cannot send unsolicited WhatsApp Business API messages to numbers that haven't opted into receiving messages from it, and cannot send bulk review requests to a purchased or scraped number list — both are against WhatsApp's commerce policy and risk the business's API access being suspended, not just a compliance technicality.

What's fine: sending to a business's own customer database, where the customer provided their number for a genuine service interaction — a booking, a purchase, an appointment. That's the implied-consent context most review request programmes operate in, and it's the only list that should ever feed a review request workflow.

Where this fits with review response and schema

Getting the request right is the first half of the review lifecycle. Once reviews start arriving through this channel, the second half is responding to them consistently — covered in Angryturtle's review response management guide — and, if the business displays reviews on its own website, marking them up correctly, covered in the review schema guide. None of the three works well in isolation; a business that generates reviews well but never responds, or responds well but never generates new ones, is only running half the system. For the step-by-step version of the whole workflow, see Angryturtle's how-to guide on getting more Google reviews.

FAQ

Do I need the WhatsApp Business API to run review requests, or is the free app enough? The free WhatsApp Business app is enough for a single location sending a handful of requests a day manually. Once volume grows past what one person can send by hand — multiple locations, or dozens of interactions a day — the API becomes worth the setup cost, because it removes the dependency on someone remembering to send each message.

Can I send a WhatsApp review request to every customer in my database at once? Only if every number in that database came from a genuine service interaction with your business and the message follows an approved template. Sending to a purchased list, or to numbers collected for an unrelated purpose, isn't compliant.

How soon after the interaction should the message go out? Close to it, while the experience is still fresh — within a few hours works well for most categories. A message that arrives days later, when the customer has moved on mentally, tends to get a weaker response.

Angryturtle sets up and manages WhatsApp review generation flows for all managed clients →