Ask for feedback right after the outcome the customer cares about (the parcel delivered, the refund issued, the problem fixed), on the channel they already used, with one question they can answer in a tap. Name the order or conversation you are asking about, ask about each issue once, and make sure someone replies to every low score.
That is how to ask for customer feedback at a consumer brand, where most contacts are about orders, deliveries, returns and refunds. This guide covers when to ask, what to ask, which channel to use, Meta's rules for WhatsApp feedback templates, and requests you can copy for deliveries, resolved tickets, returns, refunds, cash-on-delivery orders and phone calls.
In short
- Send each request when something happens: the order is delivered, the issue is resolved, the refund is issued, the call ends. Not on a weekly schedule, and not when a ticket closes because the customer went quiet.
- Ask one question per request: satisfaction (CSAT) after a support issue, a product question after delivery, and Net Promoter Score only about the relationship.
- On WhatsApp, a feedback template counts as a utility message only when it names a specific order or conversation. A generic "tell us what you think" is a marketing message.
- Treat every low score as a new support contact: reply, fix what you can, and tell the customer what changed.
When to ask: after the outcome, not the ticket
A rating describes whatever just happened. Ask the day a parcel arrives and you learn about the delivery; ask when a ticket closes and you learn about the conversation. So tie each request to an event in your store, courier or helpdesk data, the same events that drive the rest of your ecommerce customer service.
| Moment | What to ask | When to send | Don't send it if… |
|---|---|---|---|
| Order delivered | Did it arrive as expected? | The day of delivery | Another issue on the same order is still open |
| Product in use | How is the product working for you? | A few days after delivery, once it has been used | The customer has already raised a problem with it |
| Support issue resolved | How was the help you got? (CSAT) | Straight away, in the same conversation | The ticket closed because the customer stopped replying |
| Refund issued | Has the money reached you? Then: how easy was the return? | After the date you told the customer the money would arrive | The refund failed or is disputed |
| Replacement delivered | Is everything right this time? | The day the replacement arrives | The original complaint is still being handled |
| Cash-on-delivery order delivered | How was the delivery? | The day of delivery, once payment is collected | The parcel was refused or returned |
| Call ended | Did the call solve your problem? | Within the hour | The call ended without a fix; ask after the fix |
| Relationship | Net Promoter Score | After a repeat order, or once a quarter | The customer had a survey in the last few weeks |
Three rules keep the timing honest:
- One request per issue. A customer who reported a damaged order on Instagram and then by email should get one survey, not two. That is only possible when the issue sits on one ticket, which is what omnichannel customer service is for.
- Hold requests while something else is open. A customer still waiting for a refund who receives "How was your delivery?" will answer about the refund.
- Cap how often one customer is asked. Pick a limit, such as one request a fortnight, and apply it across channels, or your most loyal customers get asked the most.
Event-triggered WhatsApp automation does most of this without anyone remembering to send anything. In Flowcall, WhatsApp Marketing sends the right message when an order is confirmed, shipped, delayed or delivered, triggered by events from Shopify, ClickPost or your own systems, and follows up for feedback and reviews. When the AI Agent finishes a workflow, such as an exchange or an address change, it can schedule a feedback request for afterwards. And when a ticket is resolved in Flowcall's AI Helpdesk, the CSAT survey asks for a rating on WhatsApp, email or Live Chat. We built it this way so the request follows the outcome, not the calendar.
What to ask: CSAT, NPS or one open question
Three standard questions cover most needs, and each suits a different moment. Pick one per request.
| Question | What it measures | Ask after | Scale that fits one tap |
|---|---|---|---|
| "How was the help you got with order 1234?" (CSAT) | One support issue | A resolved issue | Good / Okay / Poor, or 1–5 |
| "How likely are you to recommend us to a friend?" (NPS) | The whole relationship | A repeat order, or once a quarter | 0–10 |
| "How easy was it to return your order?" (customer effort) | The effort a process took | A return, exchange or self-service task | Easy / Okay / Difficult |
A CSAT score tells you whether one issue went well, so it belongs after support contacts. Net Promoter Score moves with the product, the price and the delivery as much as with service, so asking it after a ticket mostly measures the ticket. Our guide to NPS vs CSAT covers the difference, and customer effort score fits processes the customer does themselves, such as booking a return.
Add an open question only after the rating, and only for low or middling scores. "What could we have done better?" gets vague answers. Offering two or three likely reasons ("Took too long", "Had to repeat myself", "Problem not fixed") gets specific ones, and still leaves room to type. Keep longer question sets for a customer feedback form after delivery, not for a support rating.
Which channel to ask on
Ask on the channel where the conversation or the order updates already happen. A customer who spent ten minutes with you on WhatsApp shouldn't get the survey by email the next day. Each of your customer service channels has its own way of asking:
| Channel | How to ask | Watch for |
|---|---|---|
| Buttons in the conversation while it is open; an approved template after that | Meta's 24-hour window, template categories and button limits (next section) | |
| Put the rating in the email itself: each option is a link that records the answer in one click | A long survey behind a "take our survey" button loses most people | |
| SMS | A short message with a link to a one-question page | In India, business SMS must use a registered sender ID and a content template registered on the operator's DLT platform |
| Live chat | A rating in the chat window when the chat ends | The visitor may already have left; ask before closing |
| Instagram DMs | In the same DM thread, after the outcome | Complaints made in public comments never get surveyed; count them separately |
| Phone | A question at the end of the call, or a message straight after | Covered in its own section below |
For many brands, especially in India, WhatsApp is the main channel for order updates and WhatsApp customer support, so it gets the most detail here.
WhatsApp surveys and feedback templates: Meta's rules
Three rules from Meta's developer documentation decide how a WhatsApp feedback request has to be built. We checked them on 30 September 2026; Meta changes them from time to time.
1. The 24-hour window. When a customer messages or calls you, a 24-hour customer service window opens, and it restarts every time they write again. While it is open you can send any message, including interactive buttons. Once it closes, you can only send pre-approved templates. So the easiest time to ask is straight after the agent or the AI confirms the outcome, while the conversation is still open. A customer's reply to your question, even a button tap, starts the window again, which leaves room for a proper follow-up.
2. Buttons have limits. A message can carry up to three reply buttons of 20 characters each, which fits a three-point scale. A list message holds up to 10 options, which fits a five-point scale at the cost of one extra tap. Net Promoter Score has 11 options (0 to 10), so it fits neither: ask the customer to type a number, link to a one-question page, or use a WhatsApp form inside the chat. Templates can carry up to 10 quick-reply buttons, but when there are more than three, WhatsApp shows two and hides the rest behind "See all options". For a one-tap rating in a template, use three buttons.
3. Feedback templates are utility only when they are specific. Meta sorts WhatsApp message templates into marketing, utility and authentication. Its guidance on feedback surveys allows utility templates that collect feedback on a previous order, transaction or conversation, and says the order or interaction must be specific: "A general/generic survey or request for feedback will not be approved as utility." A template that mixes feedback with a promotion, such as a discount code for the next order, is classed as marketing. Meta also re-checks approved templates on a recurring basis: a utility template it decides is marketing is moved after one day's notice, you can ask for a review within 60 days, and repeated miscategorisation can bring restrictions on your templates.
The category matters because it changes the cost. Since 1 July 2025 Meta charges per delivered template, at rates that depend on the category and the customer's country. Since 1 October 2026, utility templates delivered inside an open customer service window are charged too, and marketing templates always are. Our guide to WhatsApp API pricing has the details.
A feedback template that stays utility:
- names the order number, product or conversation date;
- asks about that order or conversation only;
- has no offer, discount code or "shop again" line;
- gives one clear action: buttons, or one link.
An NPS question about the brand as a whole isn't about one order, so expect it to be classed as marketing. Send it to a chosen segment as a WhatsApp broadcast, less often than your service surveys.
In Flowcall, you create WhatsApp templates, submit them for approval, and send or schedule them to a segment built from order history or to an uploaded list, from Flowcall's WhatsApp Marketing tools. Admin Copilot drafts a template from a plain-English description, such as "a utility template asking about order delivery, with three buttons", and shows it to you to approve. A template's button can also open a form inside WhatsApp, so a longer survey doesn't send the customer to a web page.
Copy-ready feedback requests for consumer brands
Each request below says when to use it and, for WhatsApp templates, the category it is written for. Numbered fields such as {{1}} are filled in when the message is sent; square brackets are for you to replace. Button labels are shown in brackets after the message.
After an order is delivered
WhatsApp template (utility), the day of delivery. A delivery check doubles as a support prompt, and it is close to the example Meta itself gives for a utility feedback template.
Hi {{1}}, your order {{2}} was delivered today. Did everything arrive as expected? [Yes, all good] [Something's wrong]
Send "Something's wrong" straight to your support queue; it is a support request, not a rating. For the delivery updates themselves, see our WhatsApp order templates.
WhatsApp template (utility), a few days later, about the product.
Hi {{1}}, you've had your {{2}} from order {{3}} for a few days now. How is it working for you? [Love it] [It's okay] [Not happy]
Email, the day of delivery. Each option is a link that records the answer.
Subject: How did order #[number] arrive?
Hi [first name],
Your order #[number] ([product]) was delivered on [date]. How was it?
[Great] [Okay] [Not good]
If anything arrived damaged, wrong or missing, reply to this email and our team will sort it out.
[Brand] customer care
SMS, the day of delivery (India: register the template on DLT first).
[Brand]: Your order [number] was delivered. How was it? Tap to rate: [short link]. Something wrong? Chat with us on WhatsApp: [link]
After a support issue is resolved (CSAT)
WhatsApp, inside the 24-hour window (buttons, no template needed).
Glad we could sort out your refund for order [number]. How would you rate the help you got today? [Good] [Okay] [Poor]
Follow-up for "Okay" or "Poor".
Sorry it wasn't better. What let you down most? [Took too long] [Repeated myself] [Problem not fixed]
WhatsApp template (utility), after the window has closed.
Hi {{1}}, you chatted with us on {{2}} about order {{3}}. How was the help you got? [Good] [Okay] [Poor]
Email, in the message that confirms the resolution.
Subject: Your request about order #[number] is sorted
Hi [first name],
[Agent name] here. Your [replacement / refund / address change] for order #[number] is done: [one line on what happens next and when].
How was the help you got? [Good] [Okay] [Poor]
If anything still isn't right, just reply and it comes straight back to me.
Our support email template collection has the rest of the emails around it.
Live chat, at the end of the chat.
Before you go: did we sort out what you came in for today? [Yes] [Partly] [No]
Instagram DM, after the outcome.
Thanks for your patience, [first name]. Your exchange for order [number] is booked and the pickup is on [date]. If you have a second, how did we do? Just reply with a number from 1 (poor) to 5 (great).
After a return, exchange or refund
WhatsApp template (utility), after the date you gave for the refund to arrive. Checking the money arrived first stops the rating becoming a complaint about a refund that hasn't landed.
Hi {{1}}, your refund of {{2}} for order {{3}} was issued on {{4}}. Has it reached your account? [Yes, received] [Not yet]
If "Yes, received" (inside the window now, so no template needed).
Good to hear. How easy was the return overall? [Easy] [Okay] [Difficult]
WhatsApp template (utility), when an exchange is delivered.
Hi {{1}}, the new size of {{2}} from order {{3}} arrived today. Does it fit? [Fits well] [Still doesn't fit]
Route "Not yet" and "Still doesn't fit" to your returns management queue, not to a report.
After a damaged or wrong item was replaced
WhatsApp template (utility), the day the replacement arrives.
Hi {{1}}, your replacement {{2}} for order {{3}} arrived today. Is everything right this time? [Yes, all good] [Still a problem]
If "Yes, all good".
Thanks for bearing with us. How would you rate the way we handled it? [Good] [Okay] [Poor]
After a cash-on-delivery order
Cash on delivery (COD), common in India, means the customer pays the courier at the door, so delivery problems on COD orders tend to reach support before anyone else.
WhatsApp template (utility), the day of delivery.
Hi {{1}}, your order {{2}} was delivered and paid for today. How was the delivery? [Smooth] [Some issues] [Not happy]
If "Some issues" or "Not happy" (list message).
Sorry about that. What went wrong? Options: Late delivery · Damaged packaging · Courier's behaviour · Wrong amount collected · Something else
Net Promoter Score after a repeat order
WhatsApp template (marketing), to a chosen segment.
Hi {{1}}, thank you for shopping with {{2}} again. One quick question: how likely are you to recommend us to a friend? Reply with a number from 0 (not at all) to 10 (definitely).
Email.
Subject: One question from [Brand]
Hi [first name], how likely are you to recommend [Brand] to a friend?
[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
Not at all likely ← → Extremely likely
Our guide to NPS survey questions has follow-ups for each score group.
One reminder, then stop
WhatsApp template (utility), 24 to 48 hours after the first request.
Hi {{1}}, just checking you saw our question about order {{2}}. One tap is enough. [Good] [Okay] [Poor]
Send one reminder at most. A second one tells the customer the survey matters more to you than their time.
How to ask a customer for feedback on the phone
There are three ways to ask for feedback on the phone, and they don't give the same answers:
- The agent asks at the end of the call. It feels personal, but agents tend to skip the calls that went badly.
- The call is transferred to an automated survey. Callers press 1 to 5. If agents decide whom to transfer, they decide who is surveyed.
- A message follows the call. A WhatsApp or SMS question goes to every logged call, whoever handled it, and leaves a written record.
The third is the most complete. The agent's job is then to set it up, not to ask for a score. A call center script for the close of the call can be as short as this:
Agent: Before you go, [first name], is there anything else I can help with on order [number]?
Customer: No, that's all.
Agent: Great. In a few minutes you'll get one question from us on WhatsApp about how this call went. It's one tap, and an honest answer really helps.
If the problem wasn't solved on the call, don't ask for a rating. Say what happens next instead:
Agent: I've passed this to our warehouse team, and you'll hear from us by [day]. Once it's sorted, we'll check it worked for you.
Post-call WhatsApp template (utility), within the hour.
Hi {{1}}, thanks for speaking with {{2}} today about order {{3}}. Did the call solve your problem? [Yes] [Partly] [No]
For surveys run on the call itself, our customer satisfaction survey script guide has the wording.
With Flowcall's phone integration, calls from Exotel, Ameyo, Ozonetel or Contaque open with the customer's context and are logged, recorded and transcribed on the ticket, and a follow-up message can go out after the call. Each call also gets an AI summary linked to the right order, so whoever picks up a "No" can see what was said and promised.
Asking for a public review without breaking the rules
Reviews on Google, marketplaces or your own product pages are feedback too, but public, and the rules are stricter. We checked these on 30 September 2026:
- Google's review policy forbids offering incentives (payment, discounts, free goods) for reviews, and forbids discouraging negative reviews or asking only happy customers for positive ones. Sending your Google review link only to customers who rated you "Good" breaks it.
- In the US, the FTC's Consumer Reviews and Testimonials Rule, in force since 21 October 2024, bans rewards that depend on a review being positive. It has no specific ban on asking only happy customers, but the FTC says that could violate the FTC Act.
- In India, IS 19000:2022, a voluntary standard from the Bureau of Indian Standards, covers any organisation that publishes consumer reviews online, including sellers collecting reviews from their own customers.
So ask everyone whose order arrived, not only the customers who rated you well, and never tie a reward to a good review. A request for a public review serves your marketing as much as your service, so plan for Meta to class it as a marketing template.
WhatsApp template (marketing) or email, a week after delivery, to every customer whose order arrived.
Hi {{1}}, how are you finding your {{2}}? If you have a minute, a review helps other shoppers decide: {{3}}. Good or bad, we read every one.
When the answer is bad: reply, fix, close the loop
A low score is a customer telling you something is still wrong. Treat it as a new support contact with a deadline, not a data point.
- Reply on the same channel, quickly. On WhatsApp, the customer's rating starts the 24-hour window again, so an agent can reply freely without a template.
- Read the conversation first. Don't ask the customer to explain again what they have just rated.
- Fix what you can, then say what you did. Check the refund, arrange the replacement, give a date. Don't ask them to rate again.
- Tag the reason (delivery, product, policy, or how the team handled it) so patterns show up across hundreds of ratings.
- Close the loop. When feedback leads to a change, tell the customers who raised it.
WhatsApp, reply to a low rating (inside the window).
Hi [first name], this is [agent name] from [Brand]. I'm sorry order [number] let you down. I can see [what happened]. I've [what you did], and you'll [get the refund / receive the replacement] by [date]. Is there anything else I should know?
Email, closing the loop after a change.
Subject: You told us, and we changed it
Hi [first name], last month you told us [the problem, in their words]. Because of feedback like yours, we've [the change]. Thank you for taking the time to tell us.
For angrier replies, our guides to how to handle customer complaints and writing a response to a complaint go further.
In Flowcall, a customer's reply to a WhatsApp template can start an AI workflow. A "Not happy" tap can open a conversation with Flowcall's AI Agent that asks what went wrong, checks the order in your systems and fixes what your rules allow. When an agent is needed, it creates a ticket with the conversation, a summary, the customer and order details and what's left to do, and routes it to the right team. Customers at risk of escalating can skip the queue.
Mistakes when asking for customer feedback
- Asking before the outcome: after the first reply, or when a ticket closes because the customer went quiet.
- Asking twice about one issue because it came in on two channels.
- Sending a generic template. "We'd love your feedback" is classed as marketing, costs more and says nothing about what you are asking.
- Linking a long form when you wanted one rating.
- Letting agents choose who gets surveyed, whether by transferring calls or sending links by hand.
- Rewarding good ratings or reviews.
- Collecting low scores that nobody answers.
How to tell if your feedback requests are working
Look beyond the average score. These checks show whether the asking works:
- Response rate by moment and channel: answers ÷ requests sent. Compare WhatsApp and email for the same moment before deciding one "doesn't work".
- Coverage: rated issues ÷ resolved issues, by channel and request type. Compare customers whose request was approved with those whose request was declined; if the declined group rarely answers, your score flatters you. Our guide on how to measure customer satisfaction explains why.
- Low-score follow-up time: from the rating to an agent's first reply, and the share answered within a working day.
- Repeat contact after a good rating: customers who rated an issue "Good" and contacted you about the same order within seven days. The fix didn't hold.
- Template categories: feedback templates Meta has moved from utility to marketing.
A CSAT calculator turns the ratings into a score; the checks above tell you whether the score can be trusted. Our guide to customer service metrics covers the rest of the dashboard.
Flowcall reports CSAT for the AI Agent and human agents separately, by channel, team and agent, in Flowcall's analytics dashboards next to first response time, resolution and the AI automation rate. AI Auto QA can audit the conversations behind low scores, and its conversation insights show which issues are growing and why, with the conversations behind each trend. That covers the customers who never answer a survey.
How Flowcall helps you ask for feedback
Flowcall puts the asking, the answering and the reporting in one place. Requests go out when an order is delivered or an issue is resolved, on WhatsApp, email or Live Chat, and a low score starts a conversation instead of sitting in a spreadsheet. When the same customer writes on another channel while their issue is open, Flowcall keeps it on the same ticket, so the rating that follows the resolution covers the whole issue. More guides like this one are in our customer service resources.
If you'd like to see Flowcall send a feedback request when an order is delivered, follow up a low score, and report CSAT for the AI Agent and human agents separately, book a demo.
Frequently Asked Questions
How do I ask a customer for feedback?
Ask right after the outcome they care about, such as the order delivered or the problem fixed, on the channel you were already using. Name the order or conversation, ask one question with a tap-to-answer scale, and say why you are asking. Reply to every low score.
How do I politely ask for feedback?
Keep it short, specific and optional: "Hi Priya, your order 4821 was delivered today. Did everything arrive as expected?" Thank the customer, don't push, and send one reminder at most. Being specific is also polite: it shows you know who they are and what they bought.
What are some examples of asking for feedback?
After delivery: "Did everything arrive as expected?" After a resolved issue: "How was the help you got today?" After a refund: "Has the money reached your account?" After a call: "Did the call solve your problem?" Each works best with two or three buttons the customer can tap.
Can you do a survey on WhatsApp?
Yes. Inside the 24-hour customer service window, ask with reply buttons (up to three) or a list (up to 10 options). Outside it, send an approved template; it is a utility template only when it asks about a specific order or conversation. Longer surveys can run as a form inside WhatsApp, which also suits an 11-point NPS question.
How do I create a feedback form in WhatsApp?
With the WhatsApp Business Platform, you can build a form that opens inside the chat, with several screens, choices and text fields, and attach it to a template button. The WhatsApp Business app has polls in chats and groups, but a poll isn't linked to an order or a ticket.
Should I offer a reward for feedback?
For a private survey, a small thank-you for answering can work, as long as it doesn't depend on what the customer says. For public reviews, Google forbids incentives altogether, and in the US a reward that depends on a positive review breaks the FTC's rule.




