WhatsApp away messages: what the free feature does, and where it stops

If you want WhatsApp to answer automatically when you are closed, the WhatsApp Business app already does it, it is free, and if your hours are fixed that is the end of the job. You set your hours, you write one message, and the app sends it to people who write to you outside them. Nothing to buy, nothing to build. The rest of this page is the part that decides whether it is enough: exactly where that free feature stops.

What the free feature is

The WhatsApp Business app’s features page describes the away message in a single sentence: “Respond automatically to messages received outside your business hours to set expectations and let customers know when you’ll be back.”

Its twin sits at the other end of the conversation. The greeting will “Automatically send a custom welcome message to new customers when they start a conversation with your business.”

Two neighbouring tools are not automatic at all, which matters if you arrived expecting a set of four automations. Quick replies are shortcuts you tap: “Create shortcuts for messages you frequently send to respond to common questions in just a few taps.” Labels are filing: “Organize and filter important customer conversations so you can quickly find and respond to messages that need your attention.” The features page introduces the section holding the away message with one promise, “Easily interact with customers while saving time and energy, using tools to automate, sort and quickly respond to messages”, and part of what sits under it saves time by having you type less, not by answering for you.

This is the product Meta built for a business of one or two people. Its own page leads with that: “The WhatsApp Business app is built with the small business owner in mind”, and it sells the away message as half of a pair, “Greet people the moment they start a conversation and respond to messages even when you’re away so your customers always feel seen and heard.”

Why there are no setup steps on this page

Meta does document the setup, on two Help Centre pages linked from the features page as “For iPhone” and “For Android”. We fetched the iPhone one on 19 September 2026 with full browser headers. It returned a redirect, then about a megabyte of HTML that extracted to 47 characters of readable text, all of them the page title. The steps exist only once a script has run.

We will not retype tap-by-tap instructions we cannot quote or date, so this page describes what the feature does and leaves the menu path to Meta. Both links sit on the features page under the Away Messages heading.

When the free one is the whole answer, and that is the honest version

If a person reads your WhatsApp messages and the only thing you want automated is telling people you are shut, the free feature covers it completely. One line is enough: “Thanks for your message. We are closed now and will reply when we open in the morning.” That example is ours, not Meta’s.

The reason to say so plainly is that we have nothing to sell you at this step, and the free feature is not a lead-in to a paid one. Install the app, set your hours, write the line. If it works, stop there.

Where it stops

Three limits. None of them is a defect, and all three decide whether the free feature is enough.

It is a fixed message on a schedule. The trigger described on Meta’s page is your business hours. The message is one you wrote in advance. A customer who writes at midnight with an urgent question and a customer who writes at midnight to say thank you get the same sentence, because the clock is what fired it.

It does not read the incoming message. Nothing on the pages cited here describes the away message inspecting, classifying or answering the content of what arrived. Meta’s own wording is about when a message was “received outside your business hours”, not about what it said. We have not tested what happens inside the app beyond that, and we are not going to assert capabilities on someone else’s account of their own product.

It exists in the Business app, and not on the Cloud API. This is the one that catches a business mid-migration, because moving to the API sounds like a way to get more automation and here does the opposite. Meta’s onboarding documentation publishes a support table with one column for what happens to a Business app feature after onboarding and one for whether Cloud API supports it at all. All three cells below are Meta’s own text.

Meta’s feature row	In the app after onboarding	On Cloud API
“Messaging tools (for example, marketing messages, greeting message, away message, quick replies, labels)”	“No change.”	“Not supported.”

So the free away message survives the move, inside the app, and does not come with you to the platform.

What the Cloud API equivalent involves

On the API side there is no feature to switch on. There is an interface, and Meta is direct about who it is for: “This documentation is intended for developers using our APIs.”

Incoming messages arrive as data rather than as a notification you can attach a rule to. From the platform overview: “The platform relies heavily on webhooks, as the contents of any message sent from a WhatsApp user to your business phone number is communicated via webhook, and all outgoing message delivery status updates are reported via webhook.”

Meta’s Service messages page sets the boundary anything you build has to sit inside. A timer starts on the customer’s side: “When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts.” And “If the user messages or calls you again before the timer expires, the timer resets to 24 hours.” Inside that window you can write freely, because “Service messages are free-form messages that you can send to WhatsApp users during a customer service window” and “service messages do not require pre-approval”. Outside it: “When the window closes, you can only send pre-approved template messages.”

An away message rebuilt on the API is therefore three pieces you own: a webhook endpoint that receives the inbound, a clock or a rule that decides whether to answer, and a send call made while the window is open. That is a small amount of code and a permanent amount of hosting, monitoring and blame.

What the boundary does not do is stop a tool messaging people first. The window governs free-form messages only, and the sentence quoted above names the route around it: “When the window closes, you can only send pre-approved template messages.” Pre-approved is the whole condition: a template is registered ahead of time and cleared by Meta, and with one in hand a business can open a conversation with somebody who never wrote to it. So answering only what arrives is a decision whoever builds the thing makes, not a limit the platform imposes. The window rule itself is Meta’s, and it is documented in what the 24-hour window actually permits.

The answer

Use the free one. If your hours are regular, your message is the same every time, and a human picks up the thread the next morning, the WhatsApp Business app is the entire solution and Meta wrote it for exactly your case.

Move only when the fixed line is the problem: when the reply has to depend on what was asked, when it has to happen at volume, or when something other than a person has to send it. Then you are building on the Cloud API, and the away message is not a setting you migrate, it is behaviour you now maintain.

Judging a tool by what its platform documents rather than by what its landing page promises is the same exercise as picking review management software.