WhatsApp auto reply for teams: away messages, greetings, and quick replies that do not feel robotic

WhatsApp auto reply is not one feature. It is three separate tools in the WhatsApp Business app, each built for a different moment: an away message for when you are closed, a greeting message for first contact, and quick replies for answering common questions fast by hand.

None of the three read the content of an incoming message and react to it. They trigger on timing (are you marked away, is this a first message) or on you manually typing a shortcut. If what you actually want is "when someone types 'pricing', send this," that is a keyword-triggered bot, which is a different category covered later in this post.

Good customer service still moves the needle on whether someone buys from you again. Salesforce's research on customer expectations puts a number on it: 88% of customers say good customer service makes them more likely to purchase again. On WhatsApp, the fastest way to fall short of that is silence. A customer messages, nobody replies for six hours, and the conversation is already lost before an agent even opens the app.

You set up an away message in WhatsApp Business settings by writing the message text, then choosing when it sends: to everyone, to specific contacts, or only during set hours. According to WhatsApp's own away message guide, you can schedule it to turn on automatically during the hours your business is closed, or restrict it to outside business hours only.

That scheduling option is what covers the "business hours" side of auto reply. Instead of manually flipping a message on and off every evening, you set the window once (say, 9am to 6pm) and the away message fires outside it automatically.

A workable away message does three things: confirms the message arrived, sets an honest expectation for when someone will reply, and gives an alternative if the request is urgent.

The WhatsApp greeting message is a fixed message that sends automatically the first time a customer messages you, and again if they message you after 14 days of no contact. Per WhatsApp's greeting message documentation, that 14-day gap is what re-triggers it, not just any new conversation.

Unlike the away message, the greeting message is not tied to your open or closed hours. It fires purely on the relationship: is this person new, or new again after a long gap. That makes it the right place for a warm, simple welcome, not an operational status update.

Quick replies let you save a pre-written message under a short text shortcut, then type that shortcut in any chat to send the full message instantly. WhatsApp's quick replies guide gives the example of typing something like `/hours` or `/pricing` to fire off a saved answer about your hours or pricing in seconds.

Quick replies are not automatic. A person still has to be in the chat, decide the shortcut fits, and send it. What they save is typing time on the questions that come up over and over: hours, location, pricing, return policy.

Use these as a starting point, then adjust the tone and details to match how your team actually talks. The goal is not to sound official, it is to sound like a person who is simply not at the keyboard right now.

**Away messages** set the expectation for when you will be back. Keep them specific about timing rather than vague ("soon", "shortly") since a real time or window is what actually reduces follow-up messages asking "did you see this?"

- "Thanks for reaching out. Our team is offline right now and back at 9am. We will reply as soon as we are online." - "We're closed for the day. If this is urgent, call [phone number]. Otherwise, we'll get back to you first thing tomorrow." - "You've caught us outside business hours (Mon-Fri, 9am-6pm). Your message is in the queue and someone will reply when we're back."

**Greeting messages** are the first thing a new customer reads from you, so they carry more weight than their length suggests. A short, warm line beats a long corporate welcome every time.

- "Hi, thanks for messaging [business name]. What can we help you with today?" - "Welcome back. It's been a bit since we last chatted, let us know what you need and we'll pick it up from here." - "Hi there. A member of our team will be with you shortly. In the meantime, feel free to share details on what you're looking for."

**Quick replies** work best for the handful of questions your team answers on repeat every single day. If you find yourself typing the same three sentences more than a few times a week, that is a quick reply waiting to be saved.

- `/hours` → "We're open Mon-Fri, 9am-6pm. Closed weekends and public holidays." - `/pricing` → "Our plans start at [price]. Want me to send the full breakdown?" - `/location` → "You'll find us at [address]. Here's a map link: [link]."

The three native tools above assume one person, or one shared understanding, is behind the number. That holds for a solo owner. It breaks down fast once a support team of three, five, or ten people is answering the same WhatsApp Business number.

The away message and greeting message still fire the same way for everyone, which is fine, they are not agent-specific. Quick replies are the problem: they live on whichever phone or device set them up, so a new hire does not automatically have the same shortcuts as the rest of the team, and nobody has visibility into which quick reply actually went out on a given chat. A proper customer support playbook for a shared number needs the auto-reply layer to be shared too, not locked to one person's app.

Picture a five-person support team splitting shifts on one WhatsApp number. Each rep set up their own quick replies on their own phone at some point, so three different versions of the "pricing" answer exist, none of them updated after the last price change. Nobody assigned ownership of the away message either, so it still references hours from six months ago. None of this is a native-app bug. It is what happens when a tool built for one person quietly gets used by five.

A Message Bot in Clapvo is a keyword-triggered auto-reply: you set a trigger word or phrase, and when an incoming message matches it, the bot sends one or more response messages in sequence, without a person needing to type anything.

Setup happens from the main menu: open Message Bot, click Create Bot, define the trigger keyword, write one or more response messages (they send in order), and choose the scope: 1:1 chats, specific groups, or all groups. Only an Admin, or a role with Message Bot access, can create or edit one, which keeps the trigger list from turning into an uncontrolled mess as the team grows.

This is where a business auto reply actually differs from the personal WhatsApp Business app. Instead of a static away message that fires on timing alone, a keyword trigger reacts to what the customer wrote: "refund" routes to one flow, "pricing" to another, without an agent having to catch and manually send a message template every time.

The same documentation carries an honest caveat worth repeating: keep triggers specific to avoid unintended matches on common words. A trigger word like "help" or "price" will fire far more often than intended, on messages that have nothing to do with what you built the bot for. If a human agent needs to step in mid-conversation, deactivate the bot for that specific chat rather than leaving it to compete with a live reply.

**Trigger words that are too broad.** "Order" or "help" will catch messages you never intended to auto-respond to. Pick a phrase specific enough that a false match is rare.

**Auto-replies that never hand off to a human.** An away message or bot reply that never mentions when or how a real person will follow up reads as a dead end, not a helpful pause.

**Ignoring the 24-hour customer service window.** Free-form auto-replies work inside WhatsApp's 24-hour messaging window after a customer's last message. Outside that window, only approved template messages can be sent, so an auto-reply flow built purely on free text will silently stop working on older conversations.

**Copy-pasting a generic away message across every channel.** A message written for email support ("we typically respond within 1-2 business days") sets the wrong expectation on WhatsApp, where customers expect a same-day, often same-hour, reply.

**Letting quick replies go stale.** Pricing changes, hours change, and a quick reply shortcut nobody updates becomes a source of wrong information sent at high speed.

Auto reply on WhatsApp starts as three simple, free tools built for one person answering one number. Away messages cover your hours, greeting messages cover first contact, quick replies cover the questions you answer daily. The moment a team shares that number, the gap shows up fast: nobody has the same shortcuts, nobody can see what already went out, and a real keyword-triggered bot with shared visibility and role-based access becomes the next step, not a nice-to-have.