Skip to content
Meta Business PartnerGlossary term

Deliverability (WhatsApp Business API)

Deliverability is the proportion of the WhatsApp messages you send that are actually accepted by Meta and delivered to a recipient's device — the gap between what you send and what lands. It sits between two other metrics people often confuse it with: send success (did the API accept the request?) and read rate (did the person open it?). On the WhatsApp Business API, high deliverability is the baseline that makes every other number — open rate, click-through, conversions — worth measuring. If a message never reaches the handset, nothing downstream can happen. This page explains what deliverability really measures, the signals that raise or sink it, and the practical habits that keep your delivered rate healthy at scale.

Delivered messages ÷ sent messages
What it measures
Double grey tick on WhatsApp
Delivered status
Bad numbers, low quality rating, blocks
Main killers
Meta bills per delivered message, by category
Billing link
Message status webhooks (sent/delivered/read)
Tracked via

In one line

Deliverability is the percentage of sent WhatsApp messages that Meta accepts and delivers to a recipient's device. It's driven by valid opted-in numbers, template approval and category, your quality rating, and messaging limits — not by how much you spend. Because WhatsApp bills per delivered message by category, poor deliverability wastes both reach and money.

What deliverability actually measures

Deliverability is a ratio: the number of messages that reach the recipient's device divided by the number you attempted to send. On the WhatsApp Business API, every message moves through a chain of statuses reported back to you via webhooks — accepted, sent, delivered, read, or failed. 'Delivered' is the state that counts here: it means Meta successfully handed the message to the recipient's WhatsApp client (the familiar double grey tick). It is distinct from 'sent' (Meta accepted your request but hasn't confirmed handset delivery) and from 'read' (the person opened it, a separate engagement metric). A message can be sent yet never delivered — the number isn't on WhatsApp, the device has been offline for days, or the recipient has blocked your business. Deliverability isolates exactly that leakage so you can see, campaign by campaign, how much of your intended reach is real.

  • Accepted / sent — Meta took the request but delivery is unconfirmed
  • Delivered — reached the device (double grey tick); this is your deliverability numerator
  • Read — recipient opened it (engagement, not deliverability)
  • Failed — rejected for an invalid number, block, or policy reason

Why deliverability matters — and how it ties to cost

Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message, priced by category — marketing, utility, or authentication. That single change makes deliverability a financial metric, not just an operational one. You are billed on messages that land, so a clean, well-targeted list means the messages you pay for are the messages real people receive. Poor deliverability hurts you twice: undelivered marketing sends waste your reach with no cost recovery, while repeated failures and user blocks drag down your quality rating, which in turn tightens your messaging limits and can shrink how many people you're even allowed to message per day. Deliverability is therefore the leading indicator of account health. Watch it drift down and you can act before Meta throttles you; ignore it and you discover the problem only when your daily limit drops.

  • Meta bills per delivered message by category (marketing / utility / authentication)
  • Undelivered marketing sends waste reach without recovering cost
  • Failures and blocks lower your quality rating over time
  • A falling quality rating tightens your messaging (tier) limits

What drives your delivered rate

Deliverability is the sum of several independent signals, and any one of them can cap the rest. First is list hygiene: WhatsApp can only deliver to numbers that are registered, active, and — for business-initiated messages — have opted in to hear from you. Scraped, stale, or landline numbers fail outright. Second is template state: business-initiated messages must use a template that Meta has approved, and the template's category (marketing vs utility vs authentication) must match its actual content, or Meta may reject or re-categorise it. Third is your quality rating and messaging tier, which reflect how recipients react to you; too many blocks or 'report' taps and Meta limits your throughput. Fourth is timing and frequency — bombarding a list, or messaging people who never engage, invites blocks that then depress future delivery. The 24-hour service window matters here too: inside it you can send free-form service replies, but once it closes you're back to approved templates, and using the wrong message type simply fails.

  • List hygiene — valid, active, opted-in numbers only
  • Template approval and correct category for business-initiated sends
  • Quality rating and messaging tier limits set by Meta
  • Send frequency and relevance — over-messaging drives blocks
  • Respecting the free 24-hour service window vs template requirements

Common deliverability mistakes

Most deliverability problems trace back to a handful of avoidable habits. The biggest is treating a WhatsApp list like an SMS or email list — importing an old CRM export and blasting everyone, when many of those numbers have no WhatsApp account or never consented. Another is confusing 'sent' with 'delivered' in your dashboards and celebrating a 99% send rate while a chunk of it never actually lands. Teams also mis-categorise templates to save money — labelling a promotional message as utility — which Meta catches and penalises, hurting both approval and quality. Sending marketing to disengaged contacts who then block you is a slow-motion deliverability killer, because the damage shows up later as a lower quality rating and reduced limits. Finally, many businesses only look at deliverability after a campaign underperforms; by then the failed sends are already spent and the account signals already logged. The fix is to monitor delivered-vs-sent continuously, prune numbers that repeatedly fail, and keep templates honest.

  • Blasting unverified or non-opted-in numbers imported from old lists
  • Reading 'sent' as 'delivered' and overstating real reach
  • Mislabelling marketing templates as utility to lower cost
  • Over-messaging until recipients block or report you
  • Reviewing deliverability only after a campaign, not during

See InfiQ pricing

Talk to InfiQ

See how this works on InfiQ

Tell us your use-case — we’ll show it running in a sandbox, usually within a working day.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

What is a good WhatsApp deliverability rate?+
On a clean, opted-in list with approved templates, delivered rates are typically very high — often well above 90% of accepted sends. The exact figure depends on list quality and how many recipients are offline or have blocked you. Rather than chasing a single benchmark, watch the trend: a delivered rate that steadily drops campaign over campaign is a signal to clean your list and review your quality rating before Meta tightens your limits.
What's the difference between sent, delivered, and read?+
'Sent' means Meta accepted your request but hasn't confirmed the message reached the device. 'Delivered' means it reached the recipient's WhatsApp (the double grey tick) — this is what deliverability measures. 'Read' means the person opened it, which is an engagement metric, not a delivery one. A message can be sent but never delivered, so always measure against delivered, not sent.
Does poor deliverability cost me money?+
Indirectly, yes. Since 1 July 2025, WhatsApp bills per delivered message by category, so undelivered messages aren't charged — but poor deliverability still wastes the reach you planned for and, worse, the failures and blocks behind it lower your quality rating. A lower rating tightens your messaging limits, which caps how many people you can reach and can slow revenue-driving campaigns.
Why do some of my WhatsApp messages fail to deliver?+
The most common reasons are that the number isn't registered on WhatsApp, the recipient has blocked your business, the device has been offline for an extended period, or — for business-initiated sends — you used an unapproved template or the wrong message type outside the 24-hour service window. Reviewing the failure reasons returned on the message status webhook tells you which of these applies.
How does the 24-hour window affect deliverability?+
The 24-hour service window is a free window that opens when a customer messages you first; inside it you can send free-form replies. It is not a billing unit. Once it closes, business-initiated messages must use an approved template. If you try to send a free-form message after the window has closed, it simply won't go through — a deliverability failure caused by message type, not by a bad number.
How can I improve my deliverability?+
Keep your list clean and opted-in, remove numbers that repeatedly fail, use approved templates in their correct category, and avoid over-messaging disengaged contacts. Monitor your quality rating and your delivered-vs-sent ratio continuously so you can act on a downward trend early. InfiQ's onboarding team can review your setup, templates, and list practices to help you keep delivered rates high.
Is deliverability the same as my quality rating?+
No, but they're closely linked. Deliverability is the share of messages that reach devices right now. Your quality rating is Meta's longer-term assessment of how recipients react to you — based on blocks, reports, and engagement. Poor deliverability signals (failures and blocks) feed into a worse quality rating over time, and a worse rating tightens the limits that then constrain your future deliverability.