WhatsApp mailing metrics: dashboard, benchmarks, and red flags
AndySendy academy
← All posts

📊 What numbers to track after every WhatsApp broadcast

Most operators watch one number - how many sent. Sometimes they add open rate. And stay blind: no delivery, no replies, numbers burning - while the report says "campaign launched." WhatsApp gives a full status funnel; ignoring it means running broadcasts blind.


Minimal dashboard: five funnel stages

Every outbound message moves through a chain of events; each stage tells its own story.

Sent - packet accepted by Meta server (one gray tick). Doesn't mean the client received anything.

Delivered - message reached the device (two gray ticks). Phone on, app installed, internet available.

Read - chat physically opened (blue ticks). But: 15–25% of users disable read receipts - some real reads stay "delivered" forever - see read vs delivered segmentation.

Replied - user sent a message back. Only status that opens 24h Customer Service Window in WABA and shifts the thread to safe two-way mode - see WABA overview.

Sale - dialog ended in target action. Heavily niche-, offer-, and process-dependent - no universal benchmarks here.


Metric benchmarks: cold vs warm list

Ranges below are market practice guides, not official Meta norms. Meta doesn't publish segment benchmarks. Segment difference - see warm vs cold base.

Metric Warm list Cold list (validated)
Delivered Rate 92–98% 80–90%
Read Rate 75–90% 45–65%
Response Rate (hard offer) 15–35% 1–5%
Response Rate (soft question) 15–35% 10–25%

Industry data: quality API infrastructure delivers 95–98%; 70–85% of messages read within 2 hours of send.


Three red flags: when to stop the campaign

🔴 Delivered Rate below 80%

Not a warning - emergency threshold. Shouldn't happen with quality list and normal infrastructure.

Check: list quality (many numbers without WhatsApp), proxy status, account limits, webhook error codes. Switching software without fixing root cause changes nothing.

🔴 Response Rate below 5% on warm list

Warm list knows you or interacted before. If they read and stay silent - problem is text, offer, or CTA - see read no reply and first-message structure. Content audit signal, not infrastructure.

🔴 Complaint Rate above 1%

Very late and dangerous signal. For WABA, safe guide is ≤ 0.1% - monitor that in real time. At 1%, template may already be Flagged or near Disabled. For gray setups, 1% complaints often means immediate number ban risk - see ban mechanics.

Additional technical thresholds: Bounce Rate ≤ 2%, Quality Rating > 0.80.


Mini case: WABA red flag that saved the template

E-commerce store launched Marketing template to 5000-client list. After 15 minutes analyst saw: delivery 96% - fine, but Response Rate dropped to 2% vs 15% norm for segment. Template Quality Rating went green → yellow.

Broadcast stopped immediately. Audit found broken link in copy. Template rewritten - WABA account avoided Tier Downgrade.

Forum case - no public methodology verification.


Why Read Rate is unreliable

High Read Rate without replies - false success signal - see four reasons for silence after read. Read doesn't start dialog. Doesn't open service window. Doesn't move funnel.

If Read Rate keeps falling campaign to campaign on same list - audience fatigue marker, not tech failure. Time to change content or frequency.

Response Rate is the more reliable operational KPI - reply is the only event that turns broadcast into real dialog.


Decision table

Metric Normal Red flag Check first
Delivered Rate 90–98% < 80% List quality, proxy, error codes
Read Rate 45–90% Falling trend Audience fatigue, send time
Response Rate (warm) 15–35% < 5% Text, CTA, segmentation
Response Rate (cold) 1–25% < 1% Relevance, question format
Complaint Rate ≤ 0.1% > 0.5% Content, relevance, list
Bounce Rate ≤ 2% > 5% List quality and validity

What not to treat as normal

Claims that need caveats:

"Complaints above 1% = red flag" is valid as emergency threshold, not control boundary. Control from 0.1%.

"80% delivery minimum" is emergency floor. For warm list with normal infra, even 90% warrants investigation.

Read Rate above 80% doesn't mean success - unless Response Rate backs it.


🎯 Next step

Export last broadcast funnel across five stages: sent → delivered → read → replied → sale. Find biggest drop. That's where next optimization starts - test hypotheses via A/B testing.

Conclusion

Practical rule:

A broadcast doesn't end at send - it ends when you've closed the funnel to sale and know which stage you lost people.