If your WhatsApp Business API stops working, the first step is to confirm whether the problem is a general Meta outage, a failure on the provider that connects you to the WhatsApp Business Platform, or something on your own connection or integration — and to activate a backup channel right away so your customers aren't left without a response. A real WhatsApp outage (one that affects all users at the same time, not just your number) usually lasts minutes to hours and resolves on Meta's side with nothing you can do to speed it up; what is in your control is having a contingency plan ready before it happens, so you don't lose sales or support while it lasts.
Not every interruption is the same
Before reacting, it helps to tell the cause apart, because the fix is different in each case:
- General Meta outage: affects WhatsApp (and often Instagram and Messenger too) for businesses and users in different countries at the same time. It doesn't depend on your provider or your setup; it only resolves once Meta restores the service.
- Provider (BSP) incident: your specific number stops sending or receiving messages because the Meta Business Partner that connects you to the WhatsApp Business API has its own technical issue, even though the rest of WhatsApp works normally for other businesses.
- A problem on your end: your integration, your internet connection, or your webhook stopped responding, while the API and the provider are operating normally.
- A restricted or blocked account: this isn't a service outage but a decision Meta made about your specific number over quality or policy — a different case we cover in what to do if your WhatsApp Business API is blocked.
How to quickly spot which case you're in
A couple of minutes of checking is usually enough to know what you're dealing with, and more importantly, who to notify first.
| Cause | How to spot it | Typical duration | What to do |
|---|---|---|---|
| General Meta outage | Other businesses report the same issue at the same time; your status in the dashboard still shows "connected" | Minutes to a few hours | Wait it out, activate the backup channel, notify your customers |
| Provider incident | Only your account is affected; your provider confirms the incident or posts a status notice | Minutes to hours | Contact your provider's support; activate the backup channel |
| Your own issue (integration/connection) | The dashboard shows a connection or webhook error; other numbers on the same provider work fine | Variable, depends on your technical team | Check logs, restart the integration, escalate to your IT team |
| Restricted or blocked account | The dashboard marks the account as restricted or disabled, with a reason stated by Meta | Until the appeal is resolved | Follow Meta's appeal process |
How reliable is the service
Meta does not publish a public status dashboard or uptime guarantees (SLA) for WhatsApp's overall availability, so an outage — even if infrequent — is always a possibility outside your business's or your provider's control. Some providers do offer their own SLA over their connection and integration layer, but that doesn't cover an outage on Meta's side. That's why a contingency plan isn't meant to prevent the interruption, but to reduce the impact it has on your sales and support while it lasts.
Contingency plan: before, during, and after
Before it happens
A contingency plan only works if it exists before the emergency, not improvised in the moment:
- Decide with your team which backup channel you'll use (email, Instagram, Messenger, web chat, phone line) and who activates it.
- Document your provider's support contacts and the steps to follow somewhere accessible to the whole team.
- If you use an omnichannel platform, confirm the other channels are already active and that your team knows how to handle them — this isn't something to configure once the outage has already started.
- Decide ahead of time what message you'll use to notify customers, so it isn't written under pressure.
During the interruption
- Confirm the scope using the table above: is it your issue, your provider's, or Meta's?
- Communicate internally with your team so they stop trying to reply through a down channel without telling customers who are waiting on a response.
- Activate the backup channel: with a platform like LiveConnect, your team can keep helping customers over Instagram, Messenger, email, or web chat from the same inbox, without losing each customer's conversation history.
- Notify your active customers through whichever channel is working (social media, a notice on your website, email) that WhatsApp is temporarily affected and how to reach you in the meantime.
- Don't open a new number or account to "get around" the problem: if it's a Meta outage, a new number has exactly the same issue; if your account is the one restricted, opening another can be read as an attempt to dodge the review.
After it's resolved
- Check the messages that were queued up: on the WhatsApp Business API, incoming messages aren't lost — they're delivered as soon as the service is restored.
- Do a short debrief with your team: how long it lasted, which backup channel worked best, and what was left undocumented for next time.
- If the cause was your provider, ask for the incident report; if it was your integration, prioritize fixing it before your next big campaign.
Why an omnichannel platform with a CRM lowers the risk
Depending on a single channel for sales and support means any interruption — minutes or hours — stops the entire conversation with your customers. A platform with a CRM for WhatsApp and omnichannel support like LiveConnect brings WhatsApp, Instagram, Messenger, email, and web chat into one inbox with multi-agent support, so if one channel goes down, the team keeps helping customers through the others without switching tools or losing customer context. This doesn't remove a Meta outage — nobody can — but it does remove the single point of failure for your whole business, something we cover in why a platform with a CRM beats the API alone.
The real cost of not having a contingency plan
The cost of an outage is rarely in its duration — which tends to be short — but in what piles up while it lasts: unanswered customer messages, unconfirmed carts, unbooked appointments. Once the channel is back, your team has to process everything that built up all at once, which drags down your first-response-time metrics for that day. Keeping a backup channel active avoids that spike, because the conversation never fully stopped — it just moved to a different channel.
Common mistakes when facing an outage
- Waiting without telling customers, who end up assuming you blocked or ignored them.
- Keeping ads live that send traffic to WhatsApp without temporarily redirecting them to another channel.
- Not having any backup channel configured and tested ahead of time.
- Blaming your provider before confirming whether the problem is actually a general Meta outage.
How to prepare with LiveConnect
If a recent outage made it clear you need more than a single channel, LiveConnect brings WhatsApp, Instagram, Messenger, email, and web chat into one inbox with a CRM, multi-agent support, and automation, so your business never depends on a single point of failure. Check out our plans and pricing or message us on WhatsApp to plan a contingency setup with a backup channel already in place.
