When Messaging Channels Go Quiet: Monitoring WhatsApp, Instagram, and Web Chat Delivery
A quiet WhatsApp inbox can mean a slow day or a broken connection. Learn the common failure modes, how to spot them fast, and a simple runbook for getting back online.

In this article
It's Monday morning and your WhatsApp queue is empty. That feels great until a customer emails to ask why nobody answered the three messages she sent on Saturday. The channel didn't crash with an error page. It just went quiet.
That's why channel health monitoring matters. Messaging channels rarely fail loudly: a token expires, a permission is removed, or a card on the WhatsApp account is declined, and messages stop flowing without anyone noticing. The fix is to monitor delivery itself, not just whether your software is "up," and to keep a short runbook ready for when something breaks.
Here are the common failure modes, how to detect them early, and what to do in the first hour.
Key takeaways
- Most channel outages are silent: expired tokens, revoked permissions, billing problems and broken webhooks don't announce themselves.
- Monitor for missing traffic and failed deliveries, and send alerts to someone who can actually fix the connection.
- A one-page runbook turns a stressful outage into a routine fix, and a few habits prevent the usual causes.
Why messaging channels fail silently
A website either loads or it doesn't. A messaging channel is a chain: your Meta business account, the app permissions you granted, an access token, a webhook subscription, your messaging platform, and the API call that sends your reply back. If any link breaks, inbound messages never reach your inbox, or your replies never reach the customer.
Nobody gets a clear error. The customer's message looks sent; your team sees a calm day. That's the core problem: silence looks like low demand, so good monitoring treats unexpected silence as a possible incident.
Common failure modes by channel
| Failure mode | Channels | Typical cause | What you notice |
|---|---|---|---|
| Expired or invalidated token | WhatsApp, Instagram | Password change, token rotation, the person who connected the channel lost access | Inbound stops, or replies fail |
| Revoked permissions | WhatsApp, Instagram | App access removed in Meta business settings, roles changed during a cleanup | Inbound stops entirely |
| Payment method issue | Expired or declined card on the WhatsApp Business account | Paid template messages fail to send | |
| Webhook problem | All API-based channels | Subscription removed, endpoint changed, certificate or configuration error | No new conversations arrive |
| Account or number status | WhatsApp, Instagram | Number restricted after quality problems, Instagram switched away from a professional account | Sending limits or blocked messages |
| Widget missing or blocked | Web chat | Site redesign, new theme, consent banner or script blocker, strict content security policy | Web chats drop to zero |
WhatsApp and Instagram
Both run through Meta, so many problems start in Meta's business settings rather than in your chat tool. Staff changes are a classic trigger: if the channel was connected with a personal account and that person leaves, the integration can go with them.
WhatsApp adds billing and quality risks. A declined card can stop template messages, and a falling quality rating can lead to restrictions. Our guide to the WhatsApp quality rating covers how to protect your number.
Web chat
Web chat usually breaks during website changes: a new theme drops the widget script, a consent tool blocks it, or caching serves an old page.
How to detect delivery problems before customers do
You don't need a complex observability stack. You need a few signals and a clear owner.
- Know your normal. If a channel usually gets messages every hour, half a day of silence should raise a flag.
- Track failed sends. Replies that error out are an early warning, especially if they cluster on one channel.
- Run a test message. Message each channel from a personal account on a fixed schedule, such as every Monday morning.
- Alert the right person. Alerts should reach someone with admin access to the Meta business account, not a shared alias nobody reads.
- Watch change events. Password resets, offboarding, card replacements and website deployments are when channels break, so check right after them.
If your engineering team pipes conversation events into its own monitoring, Conviro's webhooks are HMAC-signed with retries and delivery tracking, and the Public API now supports conversation discovery with read-only keys. The developer documentation covers both.
Channel health monitoring in Conviro
Conviro has monitored WhatsApp channel health since August, and this week we added two improvements.
- Email alerts to owners and admins. When a channel stops delivering, owners and admins get an email within about ten minutes, so a weekend outage doesn't wait until Monday.
- Pending replies after recovery. Replies that couldn't go out are delivered once the channel recovers, as long as the customer's messaging window is still open.
The window matters. On WhatsApp, you can send free-form replies for 24 hours after the customer's last message. If an outage outlasts that window, you'll need an approved template to restart the conversation. Our post on WhatsApp message templates explains the categories and approval rules.
Because every channel feeds the same Live Inbox, your team can see which customers waited during the gap and follow up in order.
A simple runbook for when a channel goes quiet
Print this, or paste it into your team wiki.
- Confirm the problem. Send a test message from an outside account and check both directions.
- Check the alert details. Note which channel, when delivery stopped and any error shown.
- Check the Meta side. In your business settings, confirm the app is still connected, permissions are granted, the payment method is valid and the number or account is in good standing.
- Reconnect with a durable account. Re-authorize the channel using an admin account that belongs to the business, not to one employee.
- Verify end to end. Repeat the test message and confirm a reply arrives on the customer side.
- Catch up. Review conversations from the gap. Reply to anyone still inside the messaging window; use an approved template for WhatsApp customers outside it.
- Write it down. Record the cause, when it started, when you noticed and one step that would have prevented it.
For prevention, connect channels with a business-owned admin account, add messaging channels to your offboarding checklist, renew the WhatsApp payment card before it expires, and make a test chat part of every website release.
Frequently Asked Questions
Why is my WhatsApp API not delivering messages?
The usual causes are an expired or revoked access token, permissions removed in Meta's business settings, a payment method problem that blocks paid template messages, a broken webhook, or a number restricted after quality issues. Also remember that free-form messages only work inside the 24-hour customer service window; outside it you need an approved template.
How fast should messaging outage alerts arrive?
Within minutes, not days. The goal is to hear about a broken channel before customers start complaining through another channel. Conviro emails owners and admins within about ten minutes when a channel stops delivering. Pair automated alerts with a manual test message after any account, billing or website change.
What happens to messages sent while a channel was down?
It depends on where the chain broke. Replies your platform couldn't send can often go out after recovery; Conviro delivers pending replies once the channel is back, while the messaging window is still open. If the WhatsApp window has closed, reopen the conversation with an approved template message.
Do I need to monitor web chat as well?
Yes. Web chat rarely fails because of tokens, but it often breaks during website changes: a theme update removes the widget, a consent tool blocks the script, or caching serves an old page. A quick test chat after each release, plus a check on daily chat volume, catches most of these early.
Next steps
Write your runbook while nothing is broken, and decide who receives channel alerts. Start free with Conviro and get WhatsApp, Instagram and web chat in one monitored inbox.
Published by
Conviro
Sharing insights on AI-powered customer support, chatbot automation, and SaaS growth strategies.
Build on Conviro
Connect conversational workflows to your stack
Review developer resources and integration patterns before you design the implementation.
Related articles
More Posts


Engineering
7 Ways to Use a Chatbot API: Building on Your Support Conversations
7 min read
Read article