WhatsApp Cloud API Message Statuses Explained

Cloud API message status updates arrive asynchronously through webhooks. A successful send request gives you a message ID, while later webhook events tell your application whether that message moved through sent, delivered, read, or failed states.

Store status changes against the exact WhatsApp message ID and keep the event timestamp when available. This gives you a reliable audit trail for customer support, campaign reporting, automation decisions, and debugging.

A sent status means WhatsApp accepted the outbound message into its delivery process. It is useful as an intermediate state, but it does not prove that the recipient's device received the message.

Always match this status to the original outbound message ID rather than updating the latest message for a customer. Multiple messages can be in flight at the same time, and status events can arrive asynchronously.

A delivered status indicates that the message reached the recipient's device or another delivery endpoint recognized by WhatsApp. It is a stronger delivery signal than sent, but it is still different from read.

Always match this status to the original outbound message ID rather than updating the latest message for a customer. Multiple messages can be in flight at the same time, and status events can arrive asynchronously.

A read status indicates that WhatsApp reported the message as read when read receipts and the message context allow that status to be produced. Your application should treat it as an engagement signal, not as proof that a customer understood or acted on the message.

Always match this status to the original outbound message ID rather than updating the latest message for a customer. Multiple messages can be in flight at the same time, and status events can arrive asynchronously.

A failed status means the message did not complete delivery. The webhook status object can include error information that should be stored with the message record so support and retry logic can distinguish temporary failures from configuration or policy problems.

Always match this status to the original outbound message ID rather than updating the latest message for a customer. Multiple messages can be in flight at the same time, and status events can arrive asynchronously.

Webhooks are the event input for a WhatsApp integration. Meta verifies a public HTTPS callback URL, then sends incoming messages and message status events to that endpoint. Your app also needs the correct WhatsApp Business Account subscription so events reach the callback.

Match Statuses to Message IDs belongs to the delivery tracking layer. Status events should update the exact outbound message identified by the WhatsApp message ID, not simply the most recent message for a customer.

Keep both the current status and enough history to explain how the message progressed. In reporting, distinguish API acceptance from device delivery and reading, and keep failed messages visible with their error details instead of dropping them from the dataset.

Store Status Updates belongs to the delivery tracking layer. Status events should update the exact outbound message identified by the WhatsApp message ID, not simply the most recent message for a customer.

Keep both the current status and enough history to explain how the message progressed. In reporting, distinguish API acceptance from device delivery and reading, and keep failed messages visible with their error details instead of dropping them from the dataset.

AI works best in a WhatsApp chatbot when it handles language understanding or flexible answers while deterministic business rules control sensitive actions. Do not let a model decide whether to refund an order, change account data, or move a high value lead without explicit application checks.

Build the AI layer around bounded context. Give it the minimum business information required for the current request, define what it can and cannot answer, and provide tools or API functions only for approved actions. When confidence is low or the request is outside scope, hand the conversation to a human or a structured fallback flow.

Build Delivery Reporting belongs to the delivery tracking layer. Status events should update the exact outbound message identified by the WhatsApp message ID, not simply the most recent message for a customer.

Keep both the current status and enough history to explain how the message progressed. In reporting, distinguish API acceptance from device delivery and reading, and keep failed messages visible with their error details instead of dropping them from the dataset.