WhatsApp "Sent" Isn't "Delivered": Monitor Your Delivery Ratio
A 202 Accepted from POST /v1/messages feels like confirmation. It isn't — it only means TextMeFlow has put your message in the queue. Whether the message actually reached the recipient, you only know once WhatsApp sends back a delivery receipt. Teams that ignore that difference only find out something is wrong when customers call to say they received nothing — while their dashboard shows nothing but green ticks for "sent".
This is exactly the problem the delivery ratio in TextMeFlow solves: an early warning, days before a visible error appears.
Why "sent" says nothing about arrival
Between the moment TextMeFlow sends a message to WhatsApp and the moment the recipient gets it, plenty can go wrong: a number that is no longer linked to WhatsApp, a network that responds slowly, or — the scenario this article is really about — a number that Meta quietly throttles. A throttled number keeps reporting "sent" because the API call itself succeeds, but the messages stop arriving. Without delivery data, you can't see that difference.
That's why TextMeFlow records not only that a message left the queue, but also WhatsApp's own delivery and read receipts for every message. Those two data points together give you the confirmed-delivery ratio per number, visible in the portal.
How to read the ratio
A healthy number holds a stable, high ratio. Watch for these signals:
- A gradual decline over several days — the most insidious pattern. Sends keep succeeding, but a growing share doesn't arrive. This is often the first sign that Meta is restricting a number, well before you see an explicit error code.
- A sudden drop on one number while other numbers perform normally — points to a problem with that specific number, not with your account or integration. After all, WhatsApp restricts a number, not an account: an account with three linked numbers can see one throttled while the other two keep working fine.
- A ratio of 0% right after pairing — no reason to panic. The counter only starts at the first confirmed delivery; messages you sent before that moment don't count, and would otherwise give a misleading picture.
How it differs from the risk score
The delivery ratio and the risk score don't measure the same thing, and they complement each other. The risk score reacts to your own sending behavior — identical broadcasts, sending to opted-out recipients, forcing sends outside quiet hours — and is therefore an indicator of what you do that creates risk (see the full list of triggers in the anti-spam guide). The delivery ratio measures the consequence: does the message actually arrive, whatever the cause. A number can have an excellent risk score and still show a falling delivery ratio, for example because of an outdated WhatsApp account on the recipient's side or a network problem at their end. Looking at both metrics together gives the full picture.
Checking delivery status via the API
Besides the portal, you can also query the status of an individual message programmatically with GET /v1/messages/{id}, using the message_id you got back when sending:
curl -s https://api.textmeflow.eu/v1/messages/3fa85f64-5717-4562-b3fc-2c963f66afa6 \
-H "Authorization: Bearer $TEXTMEFLOW_TOKEN"
For production integrations this is mainly useful for reacting automatically to failed deliveries — for example, sending a booking confirmation again by email if the WhatsApp delivery still isn't confirmed after a reasonable period. Combine this with proper handling of 429 responses; that's covered in detail in our guide to rate limits and message status in the API.
What to do when the ratio drops
- First check whether the problem is limited to one number or affects the whole account.
- See whether many new recipients were contacted in a short time from the same number — that triggers extra scrutiny from Meta.
- Slow down bulk sends and spread them over a longer period instead of firing everything off within minutes.
- Keep honoring STOP requests and don't send identical text to many recipients at once — both raise the risk and push the ratio down further.
- If the ratio doesn't recover, get in touch before the account approaches the risk threshold.
A falling delivery ratio isn't an alarm to ignore until it turns into an error message — it is the error message, just earlier and softer. If you check the portal weekly, you'll see problems weeks before a customer calls about it.
Don't have a TextMeFlow account yet? Start free and watch the delivery ratio of your own number from the very first messages you send.
Want to send WhatsApp messages via API yourself?
Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.
Free forever