A a service rating message is a feedback request sent after an interaction or defined step to understand how the customer perceived the service received. On WhatsApp Business, it can be a short question with a scale, response options, or an invitation to comment on a specific point.
This guide collects 20 original templates for businesses to adapt to situations such as case closure, technical support, commercial conversation, delivery, post-sale and reopened case. Each text must be adjusted to the moment, the objective, the brand tone and the rules applicable to the operation.
Asking for a score alone produces little value. Before sending the survey, the company must define who will analyze the response, how a complaint will be routed and in which situations the case should be resumed by a person.
What is a service rating message?
The rating message is a request sent after an interaction or a determined step. Its scope must be explicit: service, resolution, effort, product, delivery or another aspect. The clearer the question, the lower the risk of interpreting a product score as if it represented the agent's performance.
| Concept | Correct scope |
|---|---|
| Service rating | Experience with an interaction, team or resolution |
| Product rating | Product, service or delivery purchased |
| Public testimonial | Specific authorization for public use of a statement |
| Complaint | Report of a problem that requires handling |
A high score on an interaction does not, by itself, prove total quality, loyalty or intent to remain a customer. Likewise, a low score is a sign for investigation, not a complete diagnosis of the operation.
When should you send the rating message?
The rating makes more sense after a resolution or a confirmed closure. It can also be sent after technical support is completed, delivery, onboarding, post-sale or a clearly delimited commercial step. The contact should be close enough for the customer to remember the experience, but there is no universal timing or interval that fits all companies.
The sending event should represent what will be evaluated. If the question is about the resolution, confirm the case is actually resolved. If it concerns the clarity of a commercial guidance, the message can be sent at the end of that step even if no purchase occurred.
Do not send the survey:
- during an ongoing unresolved conflict;
- before the need is resolved or the step has been closed;
- repeatedly after the customer does not respond;
- when another agent is still working on the case;
- without a stop condition or without respecting the contact's preference;
- when no one is responsible for analyzing and handling the responses.
If the customer reopens the request, responds with a complaint or asks for a person, the automation must stop. The priority ceases to be collecting the score and becomes understanding what happened.
CSAT, NPS, CES or open question: which to use?
The metric should match the survey objective. CSAT, NPS and CES answer different questions; they are not interchangeable names for any rating scale.
| Metric | Objective | Question format | When it makes sense | Interpretation warning |
|---|---|---|---|---|
| CSAT | Assess satisfaction with an interaction, service or specific step | Numeric scale or textual option choices | After clearly identified service or resolution | Does not represent the entire relationship with the company |
| NPS | Measure willingness to recommend within a defined brand, period and scope | Recommendation scale stated in the question | When the company wants to evaluate the relationship or experience within the chosen scope | Should not be called service satisfaction |
| CES | Understand perceived effort to complete or resolve a need | Scale that specifies lower and higher effort | After a task, request or resolution | The question must make clear what was completed |
| Open question | Obtain qualitative context in the customer's own words | A specific question with an open answer | When the reason matters more than a single score | Comments require reading, categorization and context |
You don't have to use a single scale forever. What matters is explaining the meaning of the endpoints, keeping the definition when comparing periods, and not attributing retention, revenue or overall quality to a single metric.
How to write a good feedback message
A clear message reduces doubts about who is asking, which interaction is being evaluated and how to respond. Use these elements:
- Identify the company: the customer should recognize who is requesting the feedback.
- Contextualize the interaction: mention the support case, ticket or step without exposing unnecessary data.
- Ask one question at a time: avoid combining support, product, price and delivery.
- Indicate the format: explain the scale or the response options.
- Keep the text short: keep the main question visible.
- Don't lead the score: don't ask for a positive response or suggest a desired rating.
- Allow opt-out or refusal: don't turn feedback into an obligation.
- Inform the next step when applicable: explain that a critical response may be reviewed by the team, without promising an immediate reply.
A simple structure would be: “[company] + context of the interaction + one question + response format + optional guidance about follow-up”. This example shows the composition and is not part of the 20 templates below.
20 customer service feedback message templates
Adapt the examples to the company's identity, the event being evaluated and the internal process. Fields in brackets should be replaced only when the information is necessary.
5 short CSAT messages
Template 1. Hi, [name]. This is [company]. On a scale of 1 to 5, how do you rate the support you just received, with 1 very dissatisfied and 5 very satisfied?
Template 2. [company] would like to evaluate this interaction. Reply 1 to 5: 1 means very poor service and 5 means very good service.
Template 3. Your support case has been closed by [company]. How do you rate the experience: poor, fair, good or very good?
Template 4. Hi, [name]. Considering only today's support from [company], what rating would you give from 1 to 5? Use 1 for very dissatisfied and 5 for very satisfied.
Template 5. [company] has recorded the closure of your request. How do you rate the support: 1 very dissatisfied, 2 dissatisfied, 3 neutral, 4 satisfied or 5 very satisfied?
3 messages after technical support
Template 6. Hi, [name]. [company] has completed support for ticket [ticket]. Was the issue resolved? Reply “yes” or “no”; if not, the case may be reviewed again by the team.
Template 7. Regarding technical support for ticket [ticket], how do you rate the clarity of [company]'s instructions? Reply 1 to 5, where 1 is not clear at all and 5 is very clear.
Template 8. [company] wants to confirm the result of the support provided. Do you still have the same need? Reply “yes” if you still need help or “no” if the step was completed.
3 messages after commercial interactions
Template 9. Hi, [name]. [company] would like to evaluate today's commercial conversation. Were the presented details clear? Reply 1 to 5, where 1 is not clear at all and 5 is very clear.
Template 10. Considering only the guidance received from [company], how do you rate the support: poor, fair, good or very good?
Template 11. Did the conversation with [agent] help you understand [company]'s options? Reply “yes”, “partly” or “no”; this question does not require a purchase decision.
3 messages after delivery or post-sale
Template 12. Hi, [name]. Considering only [company]'s support during the delivery stage, how do you rate it from 1 to 5? Use 1 for very dissatisfied and 5 for very satisfied.
Template 13. The [company] would like to evaluate after-sales service, not the purchased product. Were the instructions you received clear? Answer “yes”, “partly” or “no”.
Template 14. Regarding the follow-up for the [stage] step, how do you rate [company]'s service: poor, fair, good or very good?
3 messages for dissatisfied customers or reopened cases
Template 15. Hello, [name]. [Company] recorded that your experience needs further review. Would you prefer to briefly explain what still needs follow-up or speak with a team member?
Template 16. Case [protocol] has been reopened by [company]. What issue remains outstanding for you? If you prefer not to reply here, indicate that you want human support.
Template 17. Thank you for noting that the service did not meet your expectations. What was the main issue that [company] should review? Your response will be forwarded according to the team's process.
3 open messages for qualitative collection
Template 18. Hello, [name]. Which aspect of [company]'s service most helped or hindered your experience? A brief answer is sufficient.
Template 19. Considering the [stage] step, what should [company] review in its service? The comment will be evaluated in the context of this interaction.
Template 20. If you could change one thing about the service you received from [company], what would it be? Answer only if you wish to share this context.
When adapting templates, preserve the original objective. Changing a scale is possible, provided the endpoints are explained and the meaning remains consistent. Use only the necessary fields and adjust the tone without adding pressure, a promise, or a request for a favorable response.
Log internally which version was sent in each period. This identification allows changes to be interpreted more carefully and prevents comparing responses obtained from different questions as if they represented exactly the same experience.
How to automate evaluation without losing context
Automation should start from a reliable event, not only from the time elapsed since the last message. One possible flow is:
- Choose a closing event that represents the step being evaluated.
- Apply the interval defined by the company for that process.
- Confirm that the case remains closed.
- Prevent duplicates by protocol, conversation or step.
- Send a single initial question.
- Pause when there is a reply, complaint, reopening, refusal or human support request.
- Record rating, comment, date, context and owner.
- Escalate critical cases according to internal criteria.
- Review patterns and adjust questions, sources and process.
Available integrations, fields, triggers and messages depend on the platform and the chosen configuration. During a conversation taken over by a person, automation should remain paused. A shared inbox for the team helps preserve history and ownership when human support needs to continue.
It's also important to test the flow before activation: correct closure, reopening, negative response, silence, duplication and request not to receive further messages. The survey should stop when the context changes.
What to do with negative responses?
Start by acknowledging the experience without disputing the rating or trying to convince the customer to change it. Ask only the necessary context, consult history, protocol and step, and identify whether the case needs to be reopened.
When applicable, use tickets for follow-up or another structured process to record the reason, owner and next step. Transfer the conversation to a person with the history available, avoiding making the customer repeat everything. The follow-up should respect the operation's capacity and internal deadline.
An example reply would be: “Thank you for explaining, [name]. We have recorded your comment about [step] and will forward it to the responsible team for review. If we need further information, we will contact you according to our process.”
Do not promise compensation, immediate fixes, or reversals before review. Record the reason without exposing unnecessary personal data and monitor aggregated patterns. When there is evidence, correct the process, rule, or source that contributed to the issue.
Common mistakes when asking for feedback
- asking for the highest score or a positive response;
- sending the survey before resolution;
- mixing service, product, price, and delivery in the same question;
- using a scale without explaining its meaning;
- sending multiple messages after silence;
- ignoring a negative comment;
- treating private feedback as a request for public review;
- publishing a testimonial without specific authorization;
- collecting data without purpose and an accountable owner;
- automating without a stop condition;
- using a single score as isolated proof of retention or quality.
The wording of the question affects the answer. “Did you like our excellent service?” biases perception and mixes affirmation with a question. Prefer neutral wording tied to an identifiable interaction.
How to analyze responses
When there is sufficient data, separate responses by channel, team, service type, and step. Compare equivalent periods using the same question and the same definition. A change in scale, audience, or sending event can prevent a direct comparison.
Consider response rate alongside scores and read comments and reasons, not just averages. Track reopenings, recurrence, and resolution to understand whether a criticism is an isolated case or an operational pattern.
Do not automatically attribute changes to the channel or automation. Team changes, volume, product, and process can also influence results. Avoid exposing personal data in reports when aggregated information is sufficient.
Feedback can support customer retention strategies, but it does not demonstrate retention by itself. It needs to be analyzed alongside context and other indicators defined by the company.
Frequently asked questions
What message should be sent to evaluate a service?
Use a message that identifies the company, contextualizes the interaction, asks a single question, and clearly explains how to respond. Choose the template according to the aspect being evaluated.
How to ask for a 1-to-5 rating via WhatsApp Business?
Relate the question to the specific interaction and explain the ends of the scale; for example: 1 means very dissatisfied and 5 means very satisfied.
When should the satisfaction survey be sent?
After a step is completed or a resolution is confirmed, while the customer can still recognize the interaction and there is a process to handle the response.
What is the difference between CSAT and NPS?
CSAT evaluates satisfaction with a specific interaction or step. NPS measures willingness to recommend within the brand, period, and scope defined by the survey.
Does the customer have to respond?
No. The survey should not be presented as an obligation, and the company should not insist repeatedly after silence or a refusal.
How to automate the survey on WhatsApp Business?
Define a reliable trigger, prevent duplicates, record context and owner, and pause the flow upon response, complaint, reopening, refusal, or human service.
What to do when the score is low?
Acknowledge the experience without arguing about the score, ask for the necessary context, check the history, and forward the case to a responsible person or process when applicable.
Organize the continuity of service
A good review message is short, specific and easy to reply to. The quality of the process, however, mainly depends on what the company does afterwards: recording context, stopping automations at the right time, handling criticism and fixing patterns supported by evidence.
Before enabling the flow, see how Whatsplaid works and how configuration and testing organize knowledge, boundaries and human continuity.