Campaign reports on WhatsApp: why there and not by email

The monthly PDF report has a read rate nobody measures and everybody knows: low. The weekly email, slightly better. And the alert that lands on WhatsApp gets read within minutes, because it arrives where the person is already looking.

This is not about the channel being magic. It is about friction: open email, find the attachment, open the PDF, hunt for the number — four steps. Reading a message is zero.

What works and what does not

The third line matters most. An automated message repeating "all normal" every day is ignored within a week — and worse, it trains people not to read on the day that is not normal.

The format people read

Yesterday · ACME account
Spend $1,420 · 23 leads · CPL $62

CPL is 38% above the 7-day average.
Likely cause: creative "institutional-03" at
frequency 4.1 with CTR falling since Wednesday.

Suggestion: pause that ad and scale the new
testimonial. Confirm?

Four things happen there and none is accidental:

The number comes first. Whoever reads only line one leaves informed.

The anomaly is named. "38% above average" is information; "high CPL" is opinion.

The cause is likely, not certain. Saying "likely cause" with the signal behind it is honest and leaves room to disagree.

It ends in a question. A report that asks for nothing does not get read twice.

Daily, weekly, and what goes in each

Daily — by exception only. Fires when something leaves the band: CPL above a threshold, spend with no conversions, a campaign stopped, an account not delivering. On a normal day, nothing arrives. That is what makes Thursday's message get read.

Weekly — fixed and short. The five result lines, the comparison with last week, and what comes next. Same day, same time, always.

Monthly — not on WhatsApp. A month's result needs a document, charts and context. What goes on WhatsApp is the note that it is ready.

Team and client get different things

Common and costly mistake: sending the same text to both.

For the team: raw and operational. Numbers by campaign, what is stuck, what needs a decision today. Jargon is fine, because the reader works with it.

For the client: results and consequences. No CPM, frequency or ad set names. The client wants to know whether the money came back and what you will do about it — the same logic as a media report with revenue, in four lines.

Sending jargon to a client feels like competence and produces the question "what does that mean?", which costs more time than the report saved.

Three rules that prevent spam

Only send what has a consequence. If the message changes nothing anyone will do, it should not exist.

Never send two alerts for the same reason. If CPL has been high for three days, that is one alert with the trend — not three identical ones.

Let people turn it off. An alert channel with no mute button becomes a block, and then you lose the channel entirely.

What the platform rule requires

Important, and many discover it late: a business-initiated message outside the 24-hour window requires an approved template.

In practice this rarely blocks internal reporting, because the team replies and the window reopens. For a client who never replies, every send is a business-initiated message — and needs a template.

Worth designing for from the start, instead of finding out when the message does not go through.

Where to start

1. Start with the team, not the client. Two weeks of internal alerts reveal what is noise before anyone outside sees it.
2. One alert only. Pick the anomaly that costs most when it goes unnoticed — usually spend with no conversions — and build just that.
3. Measure whether it is read. If nobody replies or acts within two weeks, the problem is the content, not the channel.
4. Only then offer it to clients. And ask first: not everyone wants work arriving on WhatsApp.

To measure where the conversations WhatsApp itself generates come from, see what WhatsApp coexistence is.