A good WhatsApp customer service message identifies the company, explains the reason for the contact or response, requests only the necessary information, and guides the next step. The text should change according to the moment: greeting, triage, question, absence, transfer or closure. Templates help maintain consistency but must be adapted to the customer and context.
What does a good customer service message need?
Before saving or sending a template, confirm it contains the necessary elements for that conversation:
- Clear identification: introduce the company or agent when this is not yet evident.
- Context: show why the message is being sent or which request is being answered.
- Specific objective: address one main topic at a time.
- Minimal information: ask only the data required to move forward.
- Next step: indicate what the customer or the team will do next.
- Realistic deadline: state a measurable expectation only when it can be met.
- Appropriate language: adapt formality, terms and length to the brand and situation.
- Alternative: offer human support, another department or an exit when necessary.
Not every company needs to use informal language, emojis or a personal signature in every message. Consistency does not mean uniformity: a simple question, a complaint and an absence require different tones.
How to adapt a template without sounding generic
Replace fields inside brackets only with verified data. Use the name when available, correct and appropriate. If the conversation relates to an order, product or question, mention only the reference needed to situate the customer, without exposing unnecessary personal data.
Remove any part that does not apply. Check the history to avoid repeating questions already answered and keep one main action per message. Before sending, review tone, spelling, link, time, deadline, stock and responsible person.
A template does not authorize promising a solution, discount, availability or date. If the data depends on another department, say the team is checking and present a realistic expectation. If the situation goes off-script, forward it for human review.
25 WhatsApp customer service message templates
The examples below use fields such as `[nome]`, `[empresa]`, `[pedido]`, `[produto]`, `[horário]`, `[prazo]`, `[atendente]` and `[link oficial]`. Adapt them to the history and company policies; do not copy and paste without checking.
Greeting and start of service
1. General greeting during business hours
Scenario: first reply during the service period.
Hello, [nome]. You are speaking with [empresa]. How can we help today? If you prefer, briefly say whether your question is about [opção 1], [opção 2] or another topic.
Caution: use categories that actually exist and do not request data before understanding the need. Expected action: the customer identifies the topic.
2. Greeting with agent identification
Scenario: a person takes over the conversation.
Hello, [nome]. I’m [atendente] from the [setor] team at [empresa], and I’ll continue your service. I’m checking the history to understand your request. Can I confirm the main topic is [assunto]?
Caution: read the history before asking for confirmation. Expected action: the customer confirms or corrects the context.
3. First contact initiated by the customer
Scenario: the customer sent a message without explaining the reason.
Hello, [nome]. Thank you for contacting [empresa]. To direct your request correctly, tell us which product, order or service you would like to check. Do not send passwords, authentication codes or full financial data.
Caution: do not assume purchase intent or a problem. Expected action: the customer presents the need.
4. Company approach after authorized request
Scenario: the company initiates contact in response to a legitimate request or context.
Hello, [name]. This is [agent] from [company]. You requested contact about [subject] on [channel/context]. Can we continue here? If you do not recognize the request or do not want to receive this message, please let us know.
Careful: mention the actual source and do not use this template for indiscriminate prospecting. Expected action: the customer authorizes continuation or requests interruption.
5. Follow-up to a previously started conversation
Scenario: the team resumes a support interaction with recorded context.
Hello, [name]. Picking up our conversation about [subject], the team found [objective update]. The next step is [action]. Would you like to continue here or do you need to clarify anything first?
Careful: confirm the update and do not reopen a closed conversation without reason. Expected action: the customer proceeds or asks for clarification.
Triage and understanding the need
6. Question to identify the subject
Scenario: the initial message does not make it clear which team should handle it.
To route your request, which option best describes the subject: [order], [product], [payment], [exchange/support], or [other]? If you choose other, write a short sentence about what you need.
Careful: offer options compatible with operations and always allow “other.” Expected action: classify the request.
7. Request for the order number
Scenario: the inquiry depends on locating a purchase.
To check the purchase, provide only the order number [expected format]. Do not send full CPF, passwords, card details, or bank codes. If you cannot find the number, tell us the email used for the purchase via [defined secure channel].
Careful: ask for the minimum necessary and provide a secure alternative. Expected action: locate the order.
8. Confirmation of the product or service of interest
Scenario: it is necessary to distinguish versions or similar items.
To confirm the correct information, are you inquiring about [product/service] in the [variation] option? If available, send the name or the official link to the item on our website.
Careful: do not assume variant, availability, or price. Expected action: identify the exact item.
9. Request for additional information
Scenario: objective data are missing to analyze a request.
I understand your request about [subject]. To verify it, we need [information 1] and [information 2]. Send only these details; if any document is required, we will indicate the appropriate channel.
Careful: explain why the data is needed and do not request documents by default. Expected action: complete the triage.
10. Confirmation of understanding before proceeding
Scenario: the team summarizes a situation with multiple details.
To confirm we understood correctly: you need help with [subject], related to [reference], and expect [requested outcome]. Is that correct? After confirmation, we will proceed with [next step].
Careful: do not turn the summary into a promise of a solution. Expected action: validate understanding.
Quick replies for recurring questions
11. Business hours
Scenario: the customer asks when the team is available.
Our support operates on [days], from [start time] to [end time], considering [timezone]. Messages received outside this period are reviewed at the next opening of business hours.
Careful: check holidays, timezone and schedules before saving. Expected action: align availability expectations.
12. Estimated response time
Scenario: the request has been received and is awaiting analysis.
We received your request about [subject]. The current estimated time for analysis is until [deadline/date]. If there is an update before then, we will notify you via this channel. The reference number is [protocol], when applicable.
Careful: use only timeframes the team can measure and meet. Expected action: the customer waits for the analysis.
13. Availability or stock subject to confirmation
Scenario: the information may change and must be checked.
The availability of [product/variation] needs to be confirmed against current stock. I will check with the team and get back to you by [realistic timeframe]. Confirmation only occurs after that verification.
Warning: do not reserve, sell or promise stock before confirmation. Expected action: wait for the check.
14. Sending official link
Scenario: the customer needs to access a page, form or document.
You can consult [subject] at this official [company] address: [official link]. Before providing any data, check that the displayed domain is [domain]. If the address does not open or looks different, do not proceed and inform us.
Warning: validate the link and explain any required redirects. Expected action: access securely or report an issue.
15. Guidance to contact the correct department
Scenario: another team is responsible for the matter.
The topic [subject] is handled by the [department] team. I will forward the conversation with the context already provided. The expected time for the next update is [timeframe]. You do not need to repeat the information unless the agent requests something additional.
Warning: confirm that history and data will actually be transferred. Expected action: wait for the responsible department.
16. Notice of ongoing inquiry
Scenario: the agent needs to verify information before replying.
I am checking [information] with the responsible team. I will return here by [realistic timeframe], even if the estimate still needs updating. If any new data appears, you can send it in this conversation.
Warning: do not use “one moment” when the inquiry may take hours or days. Expected action: wait for the update or provide additional context.
Absence, queue and forwarding
17. Out-of-hours absence message
Scenario: the customer writes when the team is not available.
Hello. You contacted [company] outside our support hours, which are [days and times, with timezone]. Your message has been received and will be reviewed starting [date/time]. If you’d like, leave the subject and any reference needed, without sending sensitive data.
Warning: keep hours up to date and do not promise an immediate response. Expected action: record the request and wait.
18. Queue message with realistic timeframe
Scenario: the team is handling other conversations.
Your message is in the queue for the [department] team. The current estimate for the first reply is up to [timeframe]. To avoid duplicates, keep the information in this conversation. If the urgency is related to [expected situation], provide [minimum data].
Warning: only state timeframes based on current capacity. Expected action: wait without opening duplicate requests.
19. Temporary unavailability of the department
Scenario: a department is temporarily unavailable.
The [department] team is unavailable at the moment and will resume service on [date/time]. We can record your request now or forward it to [available alternative], if the matter falls within that team's scope.
Warning: do not offer an alternative that cannot resolve the case. Expected action: choose between waiting or using the appropriate channel.
20. Transfer to another agent
Scenario: another person will continue the same conversation.
I will transfer your service to [agent/team], who will continue the matter [context]. The history of this conversation will be kept according to our capabilities. The expected return time is [timeframe].
Warning: check whether the platform preserves history and whether the correct recipient is available. Expected action: wait for continuity.
21. Escalation to specialized support
Scenario: the case requires technical knowledge or specific authority.
Your case requires analysis by the specialized team for [topic]. I recorded [summary] and the protocol [protocol], when applicable. The next update is expected by [timeframe]. If there is new evidence, send only the material requested through the indicated channel.
Warning: do not request files or sensitive data without necessity and an appropriate channel. Expected action: wait for the specialist or supplement the case.
Follow-up and closure
22. Follow-up after guidance sent
Scenario: the team checks whether the customer was able to follow a procedure.
Hello, [name]. Following up on the guidance about [subject]: were you able to complete [step]? If any message or different result appeared, describe what happened so we can adjust the next step.
Warning: do not assume failure or send follow-up unnecessarily. Expected action: report the result.
23. Request for confirmation of resolution
Scenario: the team completed an action but needs to confirm the effect for the customer.
The team completed [action performed] regarding [subject]. Can you confirm whether the situation is working as expected? If there is still an issue, explain the remaining point so we can continue the analysis.
Warning: do not declare satisfaction or resolution before confirmation. Expected action: confirm or detail the remaining issue.
24. Closure with the channel open for new questions
Scenario: the customer confirmed they do not need further action.
Thank you for the confirmation, [name]. We will close this support case about [subject]. If a new question arises, you can start another conversation in this channel and provide the reference [order/protocol], if needed.
Warning: close only after confirmation or a clear internal criterion. Expected action: none, unless a new need arises.
25. Closure due to no response
Scenario: the team needs to close an inactive conversation without pressuring the customer.
As we have not received a reply about [subject] since [date], we will close this support case for now. This does not prevent a new contact: when you want to continue, reply in this channel and provide [reference], if applicable.
Warning: respect the interval defined by the operation and do not use threats of loss of rights or benefits. Expected action: resume only if there is still a need.
Greeting message, absence message and quick reply: what’s the difference?
| Type | When it is used | Who or what starts it | Objective | Common risk | Example of forwarding |
|---|---|---|---|---|---|
| Greeting | First contact or return after a set period, according to configuration | App replies to the received message | Receive and guide | Promise immediate support | Ask the main subject |
| Absence | Outside configured availability | App or system replies automatically | Align expectations | Using a vague or outdated deadline | Provide real hours and an accurate estimate |
| Saved quick reply | During an ongoing conversation | The team chooses and sends the text | Reduce repetition | Sending without adapting | Edit fields and check context |
| Automatic reply | When a configured condition occurs | App or system | Reply without manual action at that moment | Prevent access to a person | Offer escalation |
| Manual message | When the case requires analysis | Agent | Handle context and exceptions | Repeat questions from the history | Summarize and confirm understanding |
| Event or campaign | Commercial event or scheduled content for an audience | Rule, integration or campaign | Communicate according to the defined purpose | Confuse marketing with support | Forward responses to the team |
How to configure greeting, absence and quick replies in WhatsApp Business
Verification performed on August 20, 2026. The WhatsApp Business app offers greeting, away message and quick replies. Paths may vary depending on Android, iPhone, version and features enabled for the account.
At an introductory level, look for the area Business tools or Company tools in the app. There, greeting lets you set a reception text; away lets you define message, recipients and availability; and quick replies let you save texts with shortcuts.
To use a quick reply, open the conversation, type /, choose the shortcut and review the text before sending. The official guidance emphasizes that the message can be edited. Do not treat the shortcut as automatic send.
If the menu name does not appear, consult the help within the installed version instead of following an old path. Those resources belong to the app. Automations from an integrated platform, WhatsApp Business Platform templates and event-triggered messages follow a different configuration.
Are quick replies the same as automation?
No. A quick reply is a saved text that the team selects and sends during a conversation. An automatic reply can be triggered by a setting, such as greeting or away. An event-based automation depends on data, rules, conditions and closure, while a campaign has its own audience, purpose and timing.
Availability varies depending on app, connection and system. A WhatsApp platform can organize automations and campaigns, but it does not turn every saved text into an automatic flow. When the company uses the WhatsApp Business Platform, messages initiated by it may require approved templates and must follow the applicable policy.
Templates by customer journey stage
- Initial support: use the greeting, triage and quick reply templates from this article.
- Abandoned cart: “Your cart is still available at [link]” is just a starting point; consult the abandoned cart recovery flow.
- Pending payment or billing: use specific language and verified data; see the payment reminder message templates and the automation for pending payment via WhatsApp.
- Order: “Order [order] status has been updated to [status]”; learn about order notifications.
- Campaign: “We selected [content] based on [context]”; campaigns require their own audience and purpose. See segmented campaigns.
- After-sales: “Were you able to use [product] as expected?”; deepen the after-sales and repurchase flow.
- Question or reply: continue the conversation with proper history and routing.
How to organize messages within a team
Assign a person or role responsible for reviewing templates. Use consistent names and categories, such as saudacao_horario, triagem_pedido and encerramento_sem_retorno. Document when each reply should be used, which fields are mandatory and which data must never be requested.
Periodically review links, schedules, policies, deadlines and department names. Preserve history before replying, route exceptions and remove outdated templates. Repeated questions may indicate the need for a new quick reply or to fix information on the website.
When multiple people share support, a team inbox on WhatsApp can help distribute conversations, check context and organize routing according to contracted features. It does not replace the team's responsibility to read the history and adapt the message.
Errors that harm WhatsApp support
- generic message without explaining the context;
- company or agent without identification;
- repeated question despite the answer existing in the history;
- multiple topics and actions in a single message;
- made-up or vague deadline;
- link without a verifiable domain;
- promise the team does not have authority to fulfill;
- automation without a path to human support;
- excessive exposure or request for personal data;
- unexpected commercial approach without legitimate context;
- insistence after a request to stop;
- casual language in complaints or sensitive situations.
The WhatsApp Business Messaging Policy requires correct identification, opt-in for contacts initiated by the company, respect for opt-out and clear escalation paths when automation is used. Review the policy before deploying templates at scale.
Frequently asked questions
What should you write in the WhatsApp Business greeting message?
Identify the company, welcome the contact, and ask for the main subject. Do not promise immediate assistance if the team is not available.
How to create a professional away message?
State that the team is unavailable, provide days, hours and time zone, and give a realistic timeframe for reviewing the message. Advise which minimum details can be left.
What are Quick Replies in WhatsApp Business?
They are saved texts with shortcuts for recurring questions. The team selects, reviews and sends the reply during the conversation.
How do I save a Quick Reply?
Look for Quick Replies in the app's business tools, create the message and shortcut, and save. The path may vary by system and version.
Is it possible to schedule messages in WhatsApp Business?
The app offers settings like greeting and away messages. Scheduled campaigns and event-driven automations depend on the features, connection and platform used; you cannot assume any message can be scheduled.
Is a Quick Reply an automation?
No. A Quick Reply is a saved text triggered by the team. An automation performs an action when a configured condition is met.
How to serve multiple customers without losing history?
Define owners, categories, routing rules and logging. In larger teams, consider a shared inbox and confirm how history, permissions and distribution work.
Can I use the same message for all customers?
A template can serve as a base, but it must be adapted to the context, verified data and conversation stage. Not every customer should receive the same text.
Official sources consulted
- WhatsApp: how to use Quick Replies — how they work and shortcuts; consulted on 08/20/2026.
- WhatsApp Business: messaging tools — greeting, away and Quick Replies; consulted on 08/20/2026.
- WhatsApp Business: initial setup and tools — current guidance from the app; consulted on 08/20/2026.
- WhatsApp Business app features — away messages and Quick Replies; consulted on 08/20/2026.
- WhatsApp Business Messaging Policy — identification, opt-in, opt-out and escalation; consulted on 08/20/2026.
Conclusion
A consistent service message follows a sequence: identify the context → choose the template → verify the data → guide the next step → log the response. The 25 examples help structure the text, but the history and the concrete situation determine what should be sent.
If your team needs to organize conversations, routing and continuity between agents, get to know the WPP Marketing inbox for WhatsApp support and evaluate the features appropriate for your operation.