WhatsApp Business away message doesn't work with the API: what happens and how to fix it

If you connected your number to the WhatsApp Business API and the away message stopped working, you're not doing anything wrong: it's expected. The away message is a feature of the WhatsApp Business app (the one installed on the phone), not of Meta's API. When the number moves to the API, the app stops managing conversations and that setting becomes inactive. It's not an error you can fix with a button: you have to replace the feature with something else. The good news is that it can be done, and in this guide we show you how.

What exactly this problem means

The WhatsApp Business app and the WhatsApp Business API are two different Meta products, even though they share the same number. The app is the free version with ready-to-use features: catalog, welcome message, away message, quick replies. The API is the programmatic route, designed for software (a CRM, a chatbot, a support platform) to receive and reply to messages.

When a number is migrated to the API, the WhatsApp Business app on the phone stops working for that number. That includes the away message: there is no switch that turns it on, because the app is no longer in the middle. If no one on the team replaces it with equivalent logic on the software side, messages that arrive outside business hours are left without an automatic reply.

Why it happens: the real causes

There are three reasons why you run into this problem. It's almost always the first one, but it's worth ruling out the other two before touching anything.

• The number is on the API and the WhatsApp Business app no longer controls it. This is the most common cause. The away message lives in the app; if the app doesn't manage the number, the feature doesn't exist.
• The number was migrated recently and was left halfway. Sometimes the app is still installed on the phone and shows the away message as active, but messages already come in through the API. The setting looks configured and does nothing.
• Someone on the team expected the API provider to configure it on its own. The API doesn't come with an away message built in: if your software doesn't have it, it doesn't appear out of thin air.

In all three cases the diagnosis is the same: the absence message, as an app feature, no longer applies. What comes next is replacing it.

How to fix it, step by step

There is no "enable absence message" button inside the API. What you have to do is rebuild that logic on the side of the software that receives the messages. These steps can be carried out by a non-technical business owner, as long as they have access to the dashboard of the tool they use with the API.

1. 1Confirm what state the number is in. Open the WhatsApp Business app on the phone and check whether the number is still linked there or whether it already appears as migrated. If the app no longer manages it, the app's absence message will never work again.
2. 2Define your real business hours. Before configuring anything, write down on a piece of paper (or in a note) which days and in which time slots you're open, and what happens on holidays. Without that information, any automation will respond incorrectly.
3. 3Look in your tool for the auto-reply by schedule option. Most platforms that work with the official API have a section for automatic replies or business hours. That's where the replacement for the absence message is configured.
4. 4Write the out-of-hours message. It has to say three things: that you received the message, when you're going to reply, and whether there's anything the person can do in the meantime (for example, leaving the details of what they need). Avoid long texts: they read poorly on WhatsApp.
5. 5Also configure the welcome message and the waiting message if your tool offers them. The absence one alone isn't enough: if someone writes at 3 in the morning and gets a reply at 9, the experience is still bad.
6. 6Test the out-of-hours flow. Write to the number from another phone when you're outside the configured time slot and see what arrives. Repeat the test on a holiday if your hours are different on those days.
7. 7Let the team know what changed. If the absence message used to be handled by a single person from the app, now it lives in the software dashboard. Make sure everyone knows where it's edited and who can edit it.

If your tool doesn't have auto-replies by schedule, there's a plan B: use an approved WhatsApp template and send it manually when you close, or leave a welcome flow that always triggers and states the business hours. It's not the same, but it covers the case.

How to keep the problem from coming back

The absence message doesn't come back on its own. What can happen is that you configure it once, the business hours change, and nobody updates the automation. To keep it from happening again:

• Write down in a visible place (an internal note, a shared spreadsheet) where the auto-reply by schedule is configured and who can edit it.
• Review the configuration every time the hours change: vacations, long holidays, opening a new location.
• If you have several numbers or several branches, check that each one has its own configuration. It's common for one number's configuration to be copied to another and end up out of sync.
• Add at least two people with access to the dashboard. If the only person who knew how to edit that goes on vacation, the absence message goes down with them.

When the real problem is something else and this symptom is misleading

Sometimes the absence message "doesn't work" but the cause is different. Before reconfiguring everything, rule out these situations:

• The access token expired or was revoked. If the software can't send messages, no automation works, neither the absence one nor any other. Typical sign: no automatic message goes out, not even the welcome one.
• The number got disconnected from the API. If the connection dropped, messages don't reach the panel and there's nothing to trigger the response. Typical sign: messages come into the phone but don't appear in the software.
• The template your automation uses was rejected or paused. If the after-hours message is sent as a template and that template isn't approved, it won't go out. WhatsApp template approval can take up to 48 hours.
• The configured schedule is wrong due to time zone. This happens a lot when the panel is in UTC and the business operates in local time. Typical sign: the message goes out at 3 in the morning or never goes out.
• The message goes out but the customer doesn't see it. Check that you're not sending from a different number than the one the customer wrote to, or that there's no spam filter on the recipient's side.

If after checking all this the message still doesn't go out, the problem is probably in your API provider's configuration and not in your business. In that case it's best to escalate to support with as much data as possible: screenshots of the panel, the exact time you tested, the number you wrote from and what you expected to receive.

What to look at in the tool you use with the API

Not all platforms that connect to Meta's official API offer auto-replies by schedule. Before choosing one or sticking with the one you have, it's worth checking three things:

• That it has auto-replies configurable by time slot, not just a fixed welcome message.
• That it lets you edit the text without depending on technical support.
• That it shows somewhere which automatic messages were sent and when, so you can audit whether they work.

Wando, for example, includes auto-replies by schedule among its features and works with Meta's official WhatsApp API. But the point isn't the tool: it's that the absence message, as such, no longer exists when the number is on the API. You have to replace it with equivalent logic on the software side, and that's done once, tested and maintained.

What you should not do

• Don't try to reactivate the WhatsApp Business app in parallel. A number cannot be in the app and on the API at the same time; forcing it can disconnect the API and leave you without service.
• Don't promise your team that it "will be fixed in a bit". It depends on the tool, on the accesses and on whether new templates need to be approved. The time varies case by case.
• Don't copy another number's configuration without checking the time zone and schedules. It's the fastest way for the message to go out at the wrong time.
• Don't use the away message to sell. If the customer writes outside business hours, what they need is to know when you will reply, not to receive a promotion.

In summary

The WhatsApp Business away message does not work with the API because it is an app feature, not an API feature. Nothing is broken or misconfigured: it must be replaced with time-based auto-replies inside the software that manages the messages. It is set up once, tested outside business hours and kept up to date when the business hours change. If the message does not go out even after configuring it, the problem is usually somewhere else: expired token, unlinked number, rejected template or wrong time zone.