How to set up feedback and NPS (with timing and message examples)

What it is and when to use it

Done well, feedback and NPS feels helpful to the customer and quietly adds revenue in the background. Done badly, it feels like being chased. The difference is mostly timing and restraint.

One-tap ratings that route unhappy customers to a person before they post a review. It starts when after a visit, delivery or ticket.

The flow, step by step

1. After: One-tap rating. Example: “How likely are you to recommend us? 0 to 10”
2. Detractor on Voice: Manager callback. Example: “A manager calls within 2 hours.”
3. Promoter on WhatsApp: Ask for a review. Example: “Would you share this on Google?”
4. Weekly on Email: Report to the team. Example: “NPS 62, up 4 this week.”

Stop the flow the moment the customer does what you wanted, whether that is buying, booking or replying. Nothing hurts trust faster than a reminder about something they already did.

Timing cheat sheet

Treat these as starting points. Your own data will tell you within a few weeks whether a step should move earlier or later.

Writing the messages

• Lead with the specific thing: the item, the date, the order number. Generic copy gets ignored.
• One message, one action. If you want a reply, ask a question. If you want a click, give one button.
• Write like a person at your company would. Short sentences, no capital-letter urgency.
• Use the channel the customer answered last time, and only fall back to another one if they have not seen the first.

Mistakes we see often

• Sending the same message on every channel at once. Pick an order and wait between steps.
• Forgetting to exclude people who already converted, or who have an open support ticket.
• Measuring opens instead of outcomes. Track the feedback and NPS result itself, then revenue or meetings per step.
• Skipping consent. WhatsApp and SMS need explicit opt-in, and in India SMS also needs DLT-registered templates.

How to measure success

Decide on one success event before you launch, for example a paid order, a booked slot or a reply. Then report three things per step: how many people reached it, how many completed the success event after it, and how many opted out.

If a step adds opt-outs without adding results, remove it. Shorter flows usually win.

Tools you need

At minimum you need something that can watch for the trigger, send on more than one channel, stop when the goal is met, and show results per step. In Hypermoat this uses Flows, Reports and dashboards and Skills-based routing. See the Feedback and NPS playbook for a ready-made version you can switch on.

Choosing the right channel mix

Most teams start feedback and NPS on the channel they already use, which is fine for a first test. Over time, the better question is which channel each customer answers. Someone who replied on WhatsApp last month is far more likely to see your next WhatsApp message than an email. Someone with no WhatsApp opt-in should go to email first, and SMS only for genuinely urgent or transactional updates.

A simple rule that holds up well: lead with the channel the person used most recently, wait long enough for them to see it, and only then fall back to the next one. Never send the same message on three channels at once. It feels efficient from the inside and like being chased from the outside.

How to improve it after launch

1. Read the first fifty replies yourself. Patterns jump out quickly.
2. Change one thing at a time: timing, the first line, or the call to action.
3. Remove any step that adds opt-outs without adding results.
4. Segment by behaviour, not demographics. First-time buyers and regulars need different messages.
5. Revisit the exit rule. Most flows that underperform simply keep going too long.

Give each change at least a week, or a few hundred sends, before judging it. Small samples lie, especially in the first days after launch.

Setting this up in Hypermoat

You do not need to build set up feedback and NPS from nothing in Hypermoat; start from the template and change what does not fit. Test it on your own number, switch it on for a small segment, then widen it once the replies look right. Replies come into one shared inbox, the customer record shows every step they went through, and the report shows the orders, bookings or deals that followed. See the feedback nps playbook.

How it connects to the rest of your stack

On its own, feedback and NPS solves one problem. Its real value appears when it shares data with the rest of your tools. A support agent who can see the last campaign a customer received writes a better reply. A marketer who can see open tickets avoids sending a promotion to someone who is already upset. A sales rep who sees recent orders knows when to call and when to wait.

That is why we recommend keeping conversations, orders, deals and tickets on one customer record. It removes the copy-paste work between tools and makes every number easier to trust.

Frequently asked questions

How long does it take to set up feedback and NPS?

With the trigger data already connected, a first version usually takes an afternoon. Most of the time goes into writing and approving the message templates.

What results should I expect from feedback and NPS?

It depends on your audience and offer. Judge it against your own baseline after two to four weeks, and look at revenue or meetings per step rather than open rates.

Which channel should feedback and NPS start on?

We usually start on WhatsApp, because that is where the first step is most likely to be seen quickly. Then fall back to other channels only for people who did not respond.