12 WhatsApp Business Reply Templates for Enquiries, Quotes and Support
A useful WhatsApp reply helps a customer feel understood, get an answer and take an easy next step. Too many questions, an unexplained price or an unclear handover can leave an enquiry stuck even after a fast acknowledgement.
Use these 12 templates as a starting point. Greeting and away messages can be configured through the corresponding features. Other examples can be saved as quick replies or sent by a colleague when appropriate. Adding a template does not automatically connect order data or create an AI assistant.
Automatic messages, quick replies and AI support
Method | Useful for | Remember |
|---|---|---|
Greeting / away messages | Acknowledgements and availability | Triggered by settings, not a complete answer to every question |
Quick replies | Reusable quote, booking and support text | Staff select and adapt the saved wording |
Integrated / AI support | Classification, retrieval and draft replies | Needs connected data, permissions, testing and human handover |
WhatsApp’s official materials describe greeting messages, away messages and quick replies. Quick replies help staff reuse answers; they should not be mistaken for a CRM integration or an order-checking assistant. Menus can differ by device and app version.
Six ways to apply consumer psychology to replies
Use psychology to make an enquiry easier to understand, compare and answer. These are Allua's message-design recommendations; test their effect with your own enquiries.
1) Reduce cognitive effort. Ask for the most important next detail. If someone asks about price, provide a useful pricing direction before sending a questionnaire.
2) Reduce uncertainty. Replace “as soon as possible” with a response window the team can meet, an owner and a clear next step.
3) Preserve autonomy. Ask which detail would help rather than insisting on a decision today. Allow an open answer or a pause alongside suggested options.
4) Make value comparable. Explain deliverables, additional charges and who an option suits. Give a reason for the recommendation instead of an unexplained total or an inflated reference price.
5) Use relevant evidence. Offer a comparable case or example you have permission to share, explaining its relevance and limits. If none exists, show the process or a demonstration; do not invent popularity claims.
6) Make the next step small and specific. One option, photo or time confirmation can move the conversation forward without implying a purchase commitment.
A useful structure is: acknowledge the need → give a useful answer → clarify the next step. Use only the parts the situation needs.
12 messages to adapt
Replace bracketed fields with accurate details and reuse information the customer has already supplied. “Why this wording” and “Use” are staff notes, not messages to send. Use the customer's language. Numbered choices are text replies; they do not automatically create app routing. Matching Chinese templates appear in the Chinese version.
1｜First enquiry
Hi, thanks for contacting [Brand]! Are you looking for 1) [service A], 2) [service B], or help choosing? Reply with a number or one sentence about what you want to achieve.
Why this wording: Reduce response effort: start with direction rather than a full brief. If the customer has already explained the need, answer it instead of sending them through a menu.
Use: Greeting message or quick reply; suggested name: welcome.
2｜Outside business hours
Thanks for your message! This is an automatic reply. Our business hours are [hours and time zone], and a colleague expects to respond by [realistic response time]. You can leave the [product/service] you are interested in; no need to repeat anything already sent.
Why this wording: Reduce uncertainty: give a realistic human-response window rather than implying that an automated acknowledgement means someone has taken over.
Use: Away message; away.
3｜Quotation details
To suggest a suitable option without adding things you do not need, could you share [the main pricing detail, such as area or quantity]? An estimate is fine; if you do not have one, a reference photo can help us understand the scope.
Why this wording: Explain why the question matters and collect details progressively. Ask for timing and remaining requirements after the key pricing detail; do not ask again for information already supplied.
Use: Quick reply; quoteinfo.
4｜Price enquiry with unclear scope
Of course. For planning: A, [core option], is HK$[range] and includes [core deliverables]. B, [extended option], is HK$[range] and adds [specific items]. For your stated goal of [goal], I would start with [A/B] because [relevant reason]. Which breakdown would be useful, or would you prefer to discuss the scope first?
Why this wording: Make value comparable: explain what the extra spend buys. Two options are a starting format, not a universal optimum. If there is no meaningful difference, give one clear quotation.
Use: Quick reply; price. Check prices, inclusions and additional charges first.
5｜Information received
Got it: you want to [goal] by [timing], and we have received [details]. [Colleague/team] will provide [specific next step] by [time]. Please correct anything I have misunderstood.
Why this wording: Reflect the customer's goal and build shared understanding. A short summary makes corrections easier than another information request.
Use: Quick reply; received.
6｜Appointment confirmation
Please confirm: [date and time], [location/meeting format], with [colleague]. Allow [duration] to discuss [purpose]. Please bring [one essential item, if needed]. Reply “Confirm”, or “Reschedule” and we will find another time.
Why this wording: Turn intention into a concrete plan: specify when, where, preparation and one simple confirmation action, with an easy route to reschedule.
Use: Quick reply; booking. Silence is not confirmation.
7｜Quotation follow-up
Hi [Name], you mentioned wanting to [goal]. Is anything holding up the decision: 1) budget, 2) whether the scope fits, or 3) timing? Reply with a number or tell me in your own words. I can clarify that point first; it is also fine if the project is on hold.
Why this wording: Diagnose the obstacle instead of repeating a sales chase. Offer an easy answer and an honest option to pause, preserving the customer's control.
Use: Quick reply; followup. Use within an existing enquiry at an appropriate follow-up point.
8｜Unavailable product or slot
The [product/slot] you requested is currently unavailable. If your priority is [stated need], [alternative] may fit; the main differences are [actual differences and price difference]. Would you like the alternative details, or an update when the original option becomes available?
Why this wording: Preserve the original goal and explain the alternative's trade-offs. Do not steer solely toward available stock or invent scarcity. Arrange availability updates only when requested.
Use: Quick reply; alternative.
9｜Order update
Order [reference] has completed [verified step] and is now [verified status]. Next is [action]. We will update you by [time], including if there is a delay. For now, [no action is needed / one required action].
Why this wording: Make progress and responsibility visible: distinguish completed work, the next step and whether the customer needs to act, rather than saying only “processing”.
Use: Quick reply or a workflow connected to current order records; order.
10｜After-sales issue
I understand that [specific issue] has caused [actual impact], and I am sorry. To work out the next step, could you send [one missing detail]? We will use the information already provided. [Team] will update you by [time] with [findings / available resolution options].
Why this wording: Acknowledge the specific impact, then explain the response. Avoid generic apologies, invented feelings or an unapproved promise of a refund.
Use: Send after human review; support.
11｜Human handover
I need [team] to review this question. I will pass on [summary of the information collected], and a colleague is expected to reply by [time]. If anything else is needed, they will ask only for the missing details.
Why this wording: Reduce handover effort: explain what context will be passed on, who will respond and when. Use this only when the handover can actually be completed.
Use: Quick reply or a workflow with a working human handover; human.
12｜Close a follow-up politely
We will pause follow-up on [project] now; no reply is needed. If you want to pick it up later, just message “Continue” here. To stop similar follow-ups, reply “Stop” and we will record your preference.
Why this wording: Preserve control and make it easy to return. Close the follow-up without guilt, an ultimatum or an invented deadline.
Use: Quick reply; pause. Record stop requests and end the relevant follow-up.
What to say after a quote: three common objections
These extend template 7. A colleague should choose the relevant response after reading the customer's reply, rather than sending every branch.
“It is too expensive.”
Try: “Understood—you want to keep the budget under control. Would it help to reduce the total, or first clarify what is included? If your priority is [core outcome], we can explore keeping [essential item] and removing [optional item], then show you the difference.”
How to use it: distinguish affordability from uncertainty about value before changing the offer. Do not automatically discount; a smaller scope must still deliver what it promises.
“I will think about it.”
Try: “Of course. Is the main question the outcome, cost or timing? If it is the outcome, I can share a relevant example and explain the approach. If the timing is not right, we can pause here.”
How to use it: fill an information gap with relevant evidence. Not every hesitation needs more chasing, and silence is not an invitation to send multiple follow-ups.
“I need to ask my boss / partner.”
Try: “Of course. I can put together a short summary to forward: the [problem], proposed [scope], total [price and inclusions] and expected [timing]. What would be most useful to clarify for your discussion? We can talk together if that helps.”
How to use it: support a shared decision without making the customer reconstruct the proposal. Do not bypass them to contact another decision-maker or assume a purchase has been agreed.
Follow-up timing: use the time agreed with the customer first. Without an agreed time, one useful follow-up after two to three working days can be an initial team rule, adjusted for the buying cycle. Pause when requested. Mention a deadline and its consequences only when they are real.
Build a first reply set in ten minutes
Choose three common situations, such as pricing, availability and support. Give each message one clear next step instead of asking every possible question at once.
Find the messaging settings or business tools in your WhatsApp Business app. Configure greeting and away messages with the appropriate recipients and business hours, then save common wording as quick replies with names your team recognises.
Test with another consenting number. Check the welcome text, out-of-hours wording and ownership of the next action. Ten minutes is a suggested starting exercise, not an estimate for a full integration or training project.
Assign responsibility for every enquiry and use consistent statuses such as “awaiting details”, “quotation pending” and “replied”. An automatic greeting is not evidence that a colleague has picked up the enquiry.
Do not automate unsupported promises
Order updates need current records; a fixed “dispatched” message is not an order lookup. Refunds, discounts, delivery commitments and special quotations need verified information and defined authority. Route complaints and uncertain answers to a person with the existing context.
Use follow-ups within the appropriate enquiry and consent context, and stop when asked. Before proactive or bulk messaging, check the applicable WhatsApp product, policies and setup. These examples are not permission for unsolicited mass messaging.
What should implementation cost?
You can begin by organising your own wording with no additional setup fee, while allowing for staff time and any paid features you actually choose.
For professional planning of approximately 10–20 reply scenarios, ownership rules and basic training, Allua suggests an initial allowance of HK$3,000–8,000 and around three to five working days. This excludes CRM, order-system and WhatsApp platform integration.
For a single connected workflow, enquiry classification or knowledge-based draft replies, allow approximately HK$8,000–25,000 in setup costs and HK$1,000–5,000 monthly, with a two-to-four-week pilot. Platform messaging, third-party provider fees and complex integrations are additional. Final scope depends on volume, users and systems.
Measure the improvement
For one week, record time to first human response, the proportion of enquiries with complete information, handling minutes per enquiry and the proportion of qualified enquiries reaching quotation. Measure automatic acknowledgements separately from meaningful human responses.
If 300 monthly enquiries each take three fewer minutes, that releases 15 hours of capacity. It becomes financial value only when it reduces overtime or additional staffing costs, or helps generate incremental profitable sales.
A small test: does the new wording make replying easier?
Choose one type of price enquiry and change one element: for example, “Please send the project details” versus “Start with the quantity; an estimate is fine.” Randomly assign eligible enquiries during a comparable period to A or B, with one version per customer. Keep offers, prices and follow-up frequency unchanged.
Define a useful response first, such as enough information for an initial quote within 48 hours. Useful-response rate = enquiries with a useful response / eligible enquiries receiving that version. Also track quotations, sales and gross profit, and stop requests; extra “OK” replies alone are not success.
For illustration, A at 10/40 is 25%; B at 16/40 is 40%, a 15-percentage-point difference. This is a fictional teaching example. Small samples and audience differences can produce unstable results, so it is not proof of a 60% improvement or a sales guarantee. With low volume, examine where customers get stuck and extend observation.
Frequently asked questions
Does every automatic reply need AI?
No. Fixed greeting and away messages can manage basic expectations. Consider advanced tools when you need to understand different questions, retrieve information or work across systems.
Do quick replies send themselves?
They primarily help staff select saved wording. Do not assume they independently interpret and respond to every incoming message; check your actual app and tools.
Should every message be bilingual?
A brief bilingual welcome can help when language preference is unknown. Once established, continue in the customer’s language instead of doubling every long reply.
Can we promise a response within five minutes?
Only if the team can consistently deliver within the relevant operating hours. Set a realistic window and update it for busy periods and holidays.
When should we connect AI or a CRM?
When repeated entry, missed follow-ups and handovers create a clear operational cost. Start with one workflow and organise FAQs, data sources and responsibility before adding tools.
Turn messages into enquiries your team can act on
Choose three conversations that stalled at pricing, quotation or support. Remove customer names, phone numbers and order identifiers, then share them with Allua alongside your tools and monthly enquiry volume. We can help identify response friction and plan wording, handovers and an appropriate AI workflow.
Disclaimer: Some information comes from publicly available third-party online sources. Please verify it before use and adapt templates to your actual service. Budgets are indicative and subject to quotation. Contact Allua if you notice an inaccuracy.
Comments