Why Every WhatsApp Support Team Needs a Canned Response Library
In chat support, speed is satisfaction. Study after study finds that first-response time is the single biggest driver of how customers rate a support interaction - often ahead of whether the issue was even fully resolved. But speed can't come at the cost of quality: when five different agents type five different versions of your refund policy, customers get five different answers, and at least one of them is wrong. Canned responses solve both problems at once. The answer to "where is my order?" or "what's your return policy?" gets written well once - accurate, on-brand, properly formatted - and every agent sends that same great answer in two seconds instead of two minutes.
Canned responses are fundamentally different from the WhatsApp message templates you may have submitted to Meta for approval. Approved templates are for *business-initiated* messages - broadcasts, reminders, and re-engagement sent when the customer hasn't written to you recently. Canned responses live inside the *24-hour customer service window*: once a customer messages you, you can reply with completely free-form text for 24 hours after their last message - no approval, no template categories, no per-template review. That's why canned responses can be shorter, faster, and more conversational than marketing templates. They're just saved text that a human fires at the right moment.
There are two ways to deploy them. The free WhatsApp Business App lets you save up to 50 quick replies and trigger them by typing "/" in the chat - fine for a solo founder, but the library lives on one phone and caps out fast. Support teams outgrow that quickly. On a WhatsApp Business API platform with a shared team inbox - like Whautomate - the whole team works from one unlimited canned response library: every agent sees the same shortcuts, updates roll out to everyone instantly, and variables like the customer's name are auto-filled from the contact record so agents aren't find-and-replacing placeholders under pressure. The 60+ responses below are organized the way real support queues are: copy the groups you need, adapt the policies to yours, and save them under consistent shortcuts.
Canned Responses
Click the Copy Message button on any template to copy it to your clipboard. Replace the {{variables}} with your actual business details.
Greetings & Opening Responses 7
How a conversation opens sets the tone for everything after it. These openers acknowledge fast, set expectations, and get the customer talking about their actual problem.
Your default opener for any brand-new conversation - greets, confirms a human is on it, and invites detail in one short message. Suggested shortcut: /greet-new
Recognizing a repeat customer builds loyalty in one line. Use when the contact history shows previous orders or visits. Suggested shortcut: /greet-back
For when a chat sat unassigned during a busy period. Owning the wait upfront defuses irritation before it grows. Suggested shortcut: /greet-wait
A named human on the other end changes the tone of the whole conversation. Use when taking ownership of a chat mid-thread. Suggested shortcut: /greet-intro
Bridges the bot-to-human transition and reassures the customer they won't have to repeat themselves. Suggested shortcut: /greet-handover
A fast acknowledgment that buys you 2β3 minutes to investigate without leaving the customer staring at "online". Silence feels like being ignored; this doesn't. Suggested shortcut: /greet-ack
For sale days and festival rushes when replies are slower than usual. An honest timeframe beats an optimistic one that gets broken. Suggested shortcut: /greet-busy
Order Status & 'Where Is My Order?' Replies 6
WISMO is the highest-volume question in e-commerce support. These replies answer with specifics - status, location, date - because "it's on the way" satisfies no one.
The workhorse WISMO reply - current status plus expected delivery date in a scannable block. Suggested shortcut: /order-status
Confirms dispatch and hands over the tracking link so the customer can self-serve future WISMO checks. Suggested shortcut: /order-tracking
For the "will it come today?" follow-up when the package is on the last mile. Sets a window and a fallback. Suggested shortcut: /order-today
When tracking shows a slip, say so before the customer discovers it. A reason, a new date, and ownership - no excuses. Suggested shortcut: /order-delay
For customers checking in before dispatch. Explains where the order is in the pipeline so "processing" doesn't feel like a black hole. Suggested shortcut: /order-processing
A stressful moment for the customer - this reply takes it seriously, gives quick self-checks, and commits to an investigation with a deadline. Suggested shortcut: /order-notreceived
Shipping, Returns & Refund Replies 7
Policy questions answered wrong cost real money and trust. Write these once from your actual policy, and every agent quotes it correctly - timelines, conditions, and fine print included.
The full policy in a scannable block - window, condition, and exclusions. Longer than most canned responses because precision here prevents disputes later. Suggested shortcut: /return-policy
Numbered steps the customer can follow without asking anything else. Ends with the pickup timeline so they know what happens next. Suggested shortcut: /return-steps
The exact "when will I get my money?" answer, broken down by payment method - the detail customers actually want. Suggested shortcut: /refund-timeline
Closes the anxiety gap between "courier took my parcel" and "refund initiated". Confirms receipt and states the next milestone. Suggested shortcut: /return-received
The good-news message - amount, destination, timeline, and a reference ID the customer can quote to their bank. Suggested shortcut: /refund-done
A gentle save attempt for size or variant issues - offers the swap without blocking the refund path. Suggested shortcut: /return-exchange
Answers the shipping-cost question and nudges the free-delivery threshold in the same breath. Suggested shortcut: /shipping-charges
Payment & Billing Replies 6
Money questions demand precise, calm answers. These replies reassure first, then give exact steps and timelines - because a vague answer about a double charge makes everything worse.
Reassures that no money is lost, explains the auto-reversal rule, and offers a working alternative. Suggested shortcut: /pay-failed
For the alarmed "I was charged twice!" message. Acknowledge, explain the likely cause, and commit to a checked resolution with a date. No emojis - this needs a steady tone. Suggested shortcut: /pay-double
Handles the common invoice ask, including the B2B GST-details case that trips up untrained agents. Suggested shortcut: /pay-invoice
For expired or lost payment links. States the fresh amount and expiry so there's no confusion about what's being paid. Suggested shortcut: /pay-link
Answers the "can I pay in EMI?" question with eligibility, tenures, and where the option appears at checkout. Suggested shortcut: /pay-emi
Closes the loop after a manual payment - confirms the amount landed and states what happens next. Suggested shortcut: /pay-confirm
Product & Availability Replies 6
Pre-sale questions are sales conversations in disguise. These replies answer accurately and keep the purchase moving - an out-of-stock answer without an alternative is a customer handed to a competitor.
Never end at "sorry, out of stock". Offer the two closest alternatives and a restock alert in the same message. Suggested shortcut: /stock-out
Confirms the customer is on the restock list and sets an honest expectation on timing. Pairs well with an automation that actually sends the alert. Suggested shortcut: /stock-notify
Turns the vague "will it fit me?" into two concrete measurements you can answer from, plus the safety net of easy exchange. Suggested shortcut: /product-size
A clean price answer with what's included - delivery, taxes - so there's no surprise at checkout. No emojis; straight and businesslike. Suggested shortcut: /product-price
For the open-ended "what do you suggest?" ask. Three quick questions narrow the field so your recommendation actually lands. Suggested shortcut: /product-recommend
When a customer is torn between two options, a one-line verdict for each decides it faster than a spec sheet. Suggested shortcut: /product-compare
Appointment & Booking Replies 6
For clinics, salons, studios and consultants, most WhatsApp chats are booking chats. These replies answer the standard booking questions completely, so a slot gets filled in one exchange instead of five.
The complete booking-instructions reply - both the self-serve link and the "just tell me here" path, because customers split evenly between the two. Suggested shortcut: /book-how
Makes rescheduling feel welcome rather than penalized - customers who fear a lecture just no-show instead. Includes the free-reschedule cutoff. Suggested shortcut: /book-reschedule
Answers "do you have anything tomorrow?" with actual pickable slots - the difference between one reply and four. Suggested shortcut: /book-slots
A tidy price list for your most-asked services, with a pointer to the full menu. Update it in one place when prices change and every agent quotes correctly. Suggested shortcut: /book-pricing
The pre-visit preparation answer - items to carry and any do/don't before the appointment. Especially useful for clinics and diagnostics. Suggested shortcut: /book-prep
For the "I'm stuck in traffic" message. Thanks them for warning you, states the grace window, and offers the reschedule path without judgment. Suggested shortcut: /book-late
Apologies & De-escalation Responses 6
These are starting points, not scripts - an angry customer can smell copy-paste from a kilometre away. Fire the shortcut, then personalize with one specific line about their situation before sending.
The core apology structure: name the failure specifically, own it without excuses, state the fix and its deadline. No emojis - sincerity needs a plain voice. Suggested shortcut: /sorry-own
For the all-caps message. Do not defend, do not explain yet - validate the frustration and show you've actually read what they wrote. Suggested shortcut: /sorry-listen
When an apology alone isn't enough, pair it with a concrete gesture. Keep the make-good proportional to the failure. Suggested shortcut: /sorry-makegood
Owns the picking error and removes all effort from the customer - correct item ships now, wrong one collected later, no return-first condition. Suggested shortcut: /sorry-wrongitem
For repeat failures, a normal apology reads as hollow. Acknowledge the pattern explicitly and escalate the fix beyond what was done last time. Suggested shortcut: /sorry-repeat
When your own team dropped the ball on response time. Brief, honest, and straight into solving - a long apology for slowness is its own irony. Suggested shortcut: /sorry-slow
Hold, Transfer & Escalation Responses 6
The moments between answers are where trust is won or lost. These replies keep the customer informed while you check, transfer, or escalate - with names, reasons and timeframes instead of dead air.
A hold message with a real timeframe. "One moment" that becomes twenty minutes destroys trust; a stated window you beat builds it. Suggested shortcut: /hold-check
Names who's taking over and why they're better placed, and promises no repetition - the thing customers dread most about transfers. Suggested shortcut: /transfer-specialist
Confirms a formal escalation with a reference number and a committed response time. The reference number alone signals the request is being taken seriously. Suggested shortcut: /escalate-manager
Some issues untangle faster on a call. Offer it as a choice, not a deflection - and let them pick the time. Suggested shortcut: /callback-offer
Asks for everything you need in one numbered list - one complete ask beats four back-and-forth messages. Suggested shortcut: /info-request
For when a promised deadline is approaching and you don't have the answer yet. An update with no news still beats silence - send it before they ask. Suggested shortcut: /hold-update
Business Info Replies 5
Hours, location, contact options - the questions every business answers dozens of times a week. Save them once with your real details and stop typing your own address from memory.
The complete hours answer, including the weekly off and holiday note that follow-up questions always ask about anyway. Suggested shortcut: /info-hours
Address plus a tap-to-navigate maps link plus the landmark locals actually use. Suggested shortcut: /info-location
The full contact card - phone, email, website - with WhatsApp positioned as the fastest lane. No emojis needed; the structure does the work. Suggested shortcut: /info-contact
For "any discounts going on?" - points to what's live right now with the end date, without turning a support chat into a sales pitch. Suggested shortcut: /info-offers
Saved for agents wrapping the queue at night, or set as an automated away message. Promises a specific reply time, not a vague "soon". Suggested shortcut: /info-afterhours
Closing & Wrap-Up Responses 7
How a conversation ends is what the customer remembers - and what they rate. These closings confirm the resolution, leave the door open, and end warm without dragging on.
States exactly what was fixed so there's a written record in the chat, then checks the customer agrees it's done. Suggested shortcut: /close-resolved
The pre-closing check that catches the "actually, one more thing" before the ticket closes instead of after. Suggested shortcut: /close-anything
For chats that went quiet mid-conversation. Closes gracefully without guilt-tripping, and makes reopening effortless. Suggested shortcut: /close-silence
The formal closure - reference number for their records, and a clear "reply to reopen" so closure never feels like a locked door. No emojis; clean and administrative. Suggested shortcut: /close-ticket
For wrapping up a case that took longer than it should have. Credits the customer's patience specifically rather than a generic thank-you. Suggested shortcut: /close-thanks
Bridges from a resolved chat to your CSAT flow while the good experience is fresh. Keep it one tap - a link to a long form kills the response rate. Suggested shortcut: /close-feedback
The simple happy-path sign-off for a smooth conversation. Short and human - not every closing needs a summary block. Suggested shortcut: /close-warm
Best Practices for WhatsApp Canned Responses
Personalize Before You Hit Send
A canned response should be the skeleton, not the whole message. Add the customer's name and one situational line - "I can see this is your third order with us" - before sending. Ten seconds of personalization is the difference between "fast and helpful" and "I'm talking to a robot". Platforms like Whautomate auto-fill the name and order variables from the contact record, so your ten seconds go into the human line, not find-and-replace.
Keep One Shared Library With Owners and Review Dates
Canned responses rot: prices change, policies change, links die. Assign each group an owner (returns β whoever runs logistics, pricing β whoever sets prices) and review the library monthly. A shared team-inbox library beats fifty copies on fifty phones - update once, and every agent sends the corrected version from the next chat onwards.
Name Shortcuts Consistently: /category-topic
Adopt a naming convention like /order-status, /order-delay, /refund-timeline - category first, topic second. Agents can then guess a shortcut they've never used, and typing "/order" surfaces every order-related response at once. Random names like /wismo2 or /newrefundmsg become unfindable by the time you have forty responses.
Never Paste Canned Text Into an Emotional Situation
An angry or upset customer can detect a template instantly, and it reads as "your problem is routine to us". Use the apology responses in this library as structure - acknowledge, own, fix, deadline - but rewrite the specifics in your own words every single time. The de-escalation group above exists to remind agents of the shape, not to be sent verbatim.
Measure Which Responses End Conversations
A great canned response resolves the question in one send; a weak one triggers three follow-up questions. Watch what happens after each response fires: if /return-policy is always followed by "but how do I actually return it?", the response is missing a step. Prune or rewrite the responses that generate follow-ups - your library should shrink in friction over time, not just grow in size.
Pair Canned Responses With a Chatbot for After-Hours
Canned responses still need a human awake to fire them. For nights, Sundays and festival rushes, promote your five most-used responses - hours, location, order status, how to book, return policy - into chatbot answers so customers get them at 2 AM too. On Whautomate, the same content powers both: the bot handles the repetitive 80% around the clock, and agents fire canned responses for everything that needs judgment.
Frequently Asked Questions
Do canned responses need approval from Meta like WhatsApp templates?
No - and this is the key difference. Canned responses are free-form replies sent inside the 24-hour customer service window, which opens every time a customer messages you. Within that window you can send any text you like, instantly, with no review process. Meta approval only applies to business-initiated template messages - for example, if a customer stopped replying and you want to re-open the conversation after the 24-hour window closes, that follow-up must be a pre-approved template. Rule of thumb: replying to an active chat needs no approval; starting or re-starting one does.
How many canned responses can I save on WhatsApp?
The free WhatsApp Business App supports up to 50 saved quick replies, and they live on a single device. That ceiling arrives faster than you'd expect - the library on this page alone has 60+. WhatsApp Business API platforms with a team inbox, like Whautomate, support unlimited canned responses shared across every agent, with variables auto-filled from the contact record. If more than one person answers your WhatsApp, the shared library is the real upgrade - everyone sends the same, current version of every answer.
How do "/" shortcuts for quick replies work?
You save each response under a short keyword - say, /refund-timeline. When an agent types "/" in the message box, the list of saved responses appears; typing a few more letters filters it. Select one and the full message drops into the composer, ready to personalize and send. A well-named library means an agent answers a policy question in under five seconds. Use a consistent /category-topic naming pattern so shortcuts are guessable - typing "/order" should surface every order-related response.
What is the difference between a canned response and a chatbot?
A canned response is human-triggered: an agent reads the message, judges the situation, picks the response, personalizes it, and sends. A chatbot is fully automatic: it detects the question and answers with no human involved. Use a chatbot for the questions with one correct answer regardless of context - business hours, location, order-status lookups, booking links. Keep humans (armed with canned responses) on anything needing judgment: complaints, refund exceptions, negotiations, anything emotional. Most strong support teams run both - on Whautomate, the chatbot absorbs the repetitive traffic and hands anything nuanced to an agent in the shared inbox.
Can I use variables like the customer's name in canned responses?
Yes, and you should - it's what stops a canned response from feeling canned. In the WhatsApp Business App this is manual: the saved text is static, so agents edit the name in by hand each time. In a team-inbox platform like Whautomate, responses support placeholders that auto-fill from the contact record - name, order number, appointment time - the moment the response is inserted. The templates on this page use numbered variables ({{1}}, {{2}}) so you can map them to whichever fields your platform provides.
How many canned responses should a support team maintain?
Start with your top 20 - pull last month's chats and save a response for every question that appeared more than a handful of times. Most teams find 40β80 covers 70β80% of their inbound volume; the 60+ on this page are a ready-made starting set. Beyond ~100, findability becomes the constraint, so prune as you add: merge near-duplicates, delete responses nobody fires, and rewrite the ones that always trigger follow-up questions. A tight, current library of 60 beats a stale archive of 200.