How Avox receives every WhatsApp event, never stores the same message twice, keeps order, retries failures, and shows you what happened.
Every message, delivery receipt, read receipt, and account update for your WhatsApp number reaches Avox as an event from Meta. This page explains what Avox does with each one, so you know what to expect
When Meta sends an event, Avox:
If Avox can't store an event, it doesn't confirm receipt, so Meta sends it again.
Meta sometimes sends the same event more than once - that's normal for WhatsApp. Avox recognises repeats and handles each one once:
You won't see a message twice in your Inbox or counted twice in Analytics.
Events for your account are processed in the order Avox received them, so a delivery status never overtakes the message it belongs to, and a conversation reads in the order it happened.
If processing an event fails - for example during a brief outage - Avox puts it back in line and tries again automatically, up to 5 times. You can follow every event in Logs:
failed, with the reason in its
Error column.A failed event is still kept, with Meta's full payload, so nothing is lost. Contact Support with the event type and time, and Avox can look into it and process it again.
If you turn on Message forwarding for a connection, Avox sends each incoming customer message to your own endpoint. When your endpoint doesn't accept a delivery, Avox retries it for many hours before giving up on it. If your endpoint keeps failing delivery after delivery, Avox pauses forwarding for that connection and emails every Admin a Message forwarding paused notice.
Nothing is lost either way: every message is still in your Inbox, and once your endpoint is working again you turn forwarding back on and resend anything you missed from the connection's delivery log.
Every event Meta sends for your number also refreshes that connection's Last active time. That's the heartbeat you see on Health and on each connection's card - a quick way to confirm events are flowing.
Last updated