WhatsApp Customer Feedback and NPS Surveys That Actually Get Replies

WhatsApp surveys work when they are short, tied to something that just happened, and answerable with one tap. Send one question soon after a delivery, appointment or support chat, using quick-reply buttons for the score, then ask a single open follow-up only to people who answered. For longer surveys, use a WhatsApp Flow so the customer fills a short in-chat form instead of replying to five messages. The value comes from what you do next: call back every low score within a day, and review the comments weekly.

Which survey, when

Timing matters more than wording

• E-commerce: a day or two after delivery, once the customer has opened the box. Not at dispatch.
• Clinics and labs: the same evening as the visit or report.
• Salons, gyms, restaurants: within a couple of hours.
• Support: right after the ticket is marked resolved, ideally while the customer service window from their last message is still open, which lets you send a normal message instead of a template.
• B2B and SaaS: relationship NPS every six months, plus CSAT after onboarding.

Avoid late nights, early mornings and major festival days. A survey that arrives at 11 pm gets ignored or muted.

Writing the survey

The first message

One line of context, one question, buttons. For example:

"Hi Priya, your order #4821 was delivered yesterday. How was your experience?" with buttons Loved it / It was okay / Not happy.

Three buttons beat a 1-to-5 scale typed as text: tapping is effortless, and the answers arrive clean.

The follow-up

Once the customer taps, their reply opens a 24-hour customer service window, so the follow-up can be a free-form message rather than another template. Branch it:

• Positive: "Thank you! Anything we could do even better?"
• Neutral: "Thanks for telling us. What's one thing we could improve?"
• Negative: "We're sorry. Could you tell us what went wrong? Someone from our team will call you today."

Then keep the promise: the negative branch should create a task for a person, not just file an answer.

NPS on WhatsApp

Standard NPS uses 0 to 10, which is too many for reply buttons. A list menu does not work either, because it holds at most 10 rows and NPS needs 11. The clean option is a WhatsApp Flow with a 0-10 rating question and an optional comment box on one screen. Our WhatsApp Flows guide covers how to build that form. Calculate NPS as usual: percentage of 9-10 scores minus percentage of 0-6 scores.

Template rules to keep in mind

• A survey sent outside the 24-hour window needs an approved template.
• A survey about a specific order, visit or ticket is often accepted as utility if it contains nothing promotional. Add "10% off your next order" and it is likely to be categorised as marketing.
• Name the transaction ("your order #4821", "your visit on 12 March") so the context is clear to the customer and the reviewer.
• Don't send surveys to people who haven't agreed to hear from you on WhatsApp.

More on categories in our utility messages guide.

Close the loop, or don't bother

A survey programme without follow-up teaches customers that feedback disappears. A simple operating rhythm:

1. Same day: every "Not happy" or NPS 0-6 goes to a named owner, who calls or messages within 24 hours.
2. Weekly: someone reads all comments and tags them: delivery, product quality, staff, price, app. Count the tags.
3. Monthly: pick the top complaint and fix one thing. Tell customers who raised it that you did.
4. Quarterly: compare scores by branch, agent, courier or product line to find where the problem really sits.

In a WhatsApp CRM like ZupiChat, survey replies arrive in the shared inbox alongside the rest of the conversation, so the person following up can see the order, previous chats and the score in one place. Tags on the contact make the weekly count simple.

Turning happy customers into reviews

People who just told you they loved the experience are the most likely to leave a Google review. Put the direct review link in the thank-you message that goes to every respondent, not only the happy ones: selectively asking only satisfied customers (review gating) goes against Google's policies. Our Google review collection guide covers the link format and Google's rules.

Mistakes that kill response rates

• Five questions in the first message. Nobody starts a quiz from a notification.
• Surveying after every interaction. Set a cooldown so each customer is asked rarely.
• Sending a link to an external form. Every extra step loses people; keep it in WhatsApp.
• Anonymous-sounding messages. Use the customer's name and the specific order or visit.
• No response to complaints. One ignored "Not happy" is worse than no survey.

The short version

• One question, one tap, shortly after a real interaction.
• Branch the follow-up by answer; route every low score to a person.
• Use a Flow for NPS, buttons for CSAT.
• Keep survey templates free of offers so they stay transactional.

Frequently Asked Questions

Is a feedback survey a utility or marketing template?

A survey about a specific recent order, appointment or support ticket is often accepted as utility, provided it contains no offers or promotion. Generic surveys not tied to a transaction, or surveys that include a discount for the next purchase, are likely to be categorised as marketing. Meta decides the category at review, so write the template plainly and check the result.

What response rate should I expect from WhatsApp surveys?

It varies widely by industry, timing and question design, so measure your own baseline. A single-tap first question sent soon after a real interaction usually does far better than a long form sent weeks later. Track the reply rate per template and per trigger, and change one thing at a time.

Should I offer a discount for filling a survey?

Usually not in the first message. An incentive pushes the template toward marketing, attracts rushed answers and trains customers to expect payment for feedback. If you want to thank people, do it after they answer, in a separate message inside the customer service window.

Can I ask for a Google review in the same survey?

Yes, but offer the review link to every respondent, not only those who gave a high score. Asking only satisfied customers is review gating, which Google's policies do not allow. Happy customers will still be the ones most likely to use the link.

How often can I survey the same customer?

Keep relationship NPS to once or twice a year per customer, and transactional CSAT to one question after meaningful interactions, not after every tiny message. Set a rule in your system that skips anyone surveyed recently. Survey fatigue shows up as falling response rates and rising blocks.