Was the Message Delivered? Reading Webhook Status Reports

The response you get when sending a message through the API does not mean the customer received it — only that the request was accepted. The real story arrives in webhook status notifications. A setup that does not store them can run for weeks while hundreds of messages quietly fail.

Four Core Statuses

A missing read status does not mean the message went unread — the user may have read receipts disabled, which is why read rate alone is a misleading performance metric.

Where Silent Losses Come From

• The number is not on WhatsApp or is badly formatted — records never converted to international format are the most common cause.
• The user blocked the business, so the message is accepted but not delivered.
• A free-form message attempted while the 24-hour window is closed.
• A template you believed was approved has been paused.
• The daily messaging limit is exhausted.
• Your webhook endpoint returns errors, so notifications retry and can eventually be lost.

The last one is the most dangerous because it is on your side and invisible from outside.

Rules for the Webhook Endpoint

• Respond fast: queue the notification and acknowledge, then process asynchronously.
• Verify the signature before processing anything.
• Expect duplicates and deduplicate by message id.
• Do not rely on ordering — a read status can arrive before delivered; use timestamps.
• Store the error code, not just the failure; without the reason nothing can be fixed.

Retrying Failed Messages

Not every error deserves a retry. Transient infrastructure errors can be retried with backoff, two or three attempts at most. Permanent causes — invalid number, block, closed window — should never be retried; resending only damages your sending quality. Flag the record and pass it to operations instead.

What to Monitor

• Delivered as a share of sent; sudden drops point to list or limit problems.
• Distribution of error codes and the top three.
• Delivery rate per template — a drop can mean that template was paused.
• Webhook processing latency.
• Count of unprocessed notifications; anything above zero needs a cause.

Set Up Alerts

Dashboards do not help if nobody is watching them. Define at least two alerts: delivery rate below your threshold, and repeated webhook processing failures. On busy days these turn hours of blindness into minutes.

What It Means for Customers

Delivery data drives operational decisions. An undelivered appointment reminder means a missed appointment, so critical notifications should be able to fall back to another channel such as SMS or a call. Undelivered order updates similarly forecast the calls your team is about to receive.

With BozLat AI

Delivery notifications are stored and classified by error code, permanent failures land on an operations list, and critical notifications can fall back to an alternative channel. See pricing and, for API fundamentals, what the WhatsApp Business API is.