Two kinds of number
Platform health. Whether you can keep using the channel at all.
Business results. Whether it is doing anything useful.
Most companies watch the second and ignore the first, then find their messaging limits reduced and cannot explain why.
Both matter. Platform health matters more, because losing the channel ends the conversation about results.
Platform health
Four numbers. Check them weekly.
Quality rating
Meta’s measure of how recipients react to your messages.
Why it matters: as it falls, your messaging limits reduce. Fall far enough and the number can be restricted.
Why it is the most useful number here: it declines before you lose access. Somebody watching it can act in time.
What to do if it drops: stop sending, find out what changed, reduce frequency, go back to utility-only. Do not push through.
Blocks
People blocking your number.
Rising means you are sending things people do not want. It is the most direct signal available.
Reports
Worse than blocks — an active complaint. A small number of reports does more damage than a larger number of unsubscribes.
If reports appear at all, look at what you sent that week.
Read rate
How many messages get opened.
On WhatsApp this should be high — well above email. If it is not, your content is not wanted, and blocks and reports usually follow.
FIGURE 1: PLATFORM HEALTH, MOST IMPORTANT FIRST
Quality rating
- Falls before you lose access. A warning you can act on.
Reports
- An active complaint. More damaging than any other signal.
Blocks
- People removing you. The most direct measure of unwanted messages.
Read rate
- Should be high on this channel. Low means the content is wrong.
Business results
What the channel is actually doing for you. Which numbers matter depends on what you are using it for.
For order and delivery updates
Support enquiries avoided. Compare “where is my order” volume before and after. This is usually where the whole project pays for itself.
Read rate on updates. Should be very high. These are messages people want.
Delivery failures. Messages that could not be sent — usually a bad phone number. Track it, because it is a data quality problem you can fix.
For appointment reminders
No-show rate, before and after. The clearest measurable outcome in this whole article.
Reschedule rate. People rescheduling rather than not turning up is a win, not a loss.
For support
First response time. What customers feel most.
Resolution time.
Reopened conversations. The honest test. If it rises, you are answering faster and worse.
Volume by topic. What people actually ask. The most actionable number here and the least used — it tells you what to fix in the product or document publicly.
For sales
Conversations started, by source.
Response time. The strongest lever you control.
Conversation to opportunity rate.
Opportunity to order rate.
FIGURE 2: THE THREE MOST USEFUL BUSINESS NUMBERS
Support enquiries avoided
- Order updates usually pay for the project here alone.
No-show rate
- For reminders, the clearest measurable outcome available.
Reopened conversations
- For support, the honest test of whether speed cost you accuracy.
Take a baseline first
Before you send a single message, record:
- Current “where is my order” enquiry volume
- Current no-show rate
- Current first response time on support
- Current enquiry volume by channel
Without these you cannot tell whether it worked, and you will keep the channel running because it feels modern rather than because it earns its place.
Two months of baseline is enough. One is thin.
Numbers to be careful with
Message volume. Sending more is not an achievement. It is often the opposite.
Delivered rate alone. Delivered means it arrived, not that it helped.
Conversation count without outcomes. Lots of conversations going nowhere is activity, not results.
Anything that improves when you send more. If a metric rewards volume, it will encourage the behaviour that costs you the channel.
Reviewing regularly
Weekly: quality rating, blocks, reports. Five minutes.
Monthly: business results against your baseline. Support enquiries, no-shows, response times.
Quarterly: the bigger questions. Is the message mix right? Are templates still relevant? Should anything be retired?
FIGURE 3: A PROGRAMME THAT IS WORKING AND ONE THAT IS NOT
Working
- Quality rating steady or high
- High read rate on utility messages
- Support enquiries measurably down
- Blocks near zero
Heading for trouble
- Quality rating drifting down
- Read rate falling
- Reports appearing at all
- Volume rising while outcomes are flat
Acting on what you see
Quality rating falling. Stop. Reduce frequency. Return to utility-only messaging. Check consent for whoever you have been messaging.
Blocks rising. Look at what changed. New message type? New list? Higher frequency?
Read rate falling. The content is not wanted. Send less, and make what you send more useful.
Delivery failures rising. A phone number data problem. Clean the records.
Support enquiries not falling. Either the wrong updates are being sent, or they are not reaching the right customers. Check both.
The number that tells you most
If you track one thing, track quality rating.
It is the only number that warns you before something goes wrong, and it responds to everything that matters — consent, relevance, frequency, and whether people want what you are sending.
A healthy rating means the programme is working. A falling one means fix it now, while you still can.
The short version
Watch platform health weekly — quality rating, blocks, reports, read rate. These decide whether you keep the channel.
Take a baseline before you start, or you cannot tell whether anything improved.
Measure outcomes, not volume. Support enquiries avoided, no-shows reduced, response times improved.
And treat a falling quality rating as an instruction to stop and fix, not a statistic to note.
Running WhatsApp messaging and not sure whether it is working?
Get in touch. We will set up the measurement — including the platform health numbers that warn you before something goes wrong.
