Collects as they arrive, acts daily

Get a daily WhatsApp delivery and read report

Each morning you see how many messages were sent, delivered, read and failed the day before.

Runs: Collects as they arrive, acts daily
Apps: WhatsApp Business
AI: Not needed
Access: whatsapp_business_messaging

Send this to your assistant

Create a ClickRuntime automation: every morning at 8, email me yesterday's WhatsApp sent, delivered, read and failed counts with the delivery and read rates.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A business that sends order updates, appointment reminders or promotions on WhatsApp has little idea whether those messages arrive. Meta's tools show campaign numbers only in aggregate and after the fact, so a quiet delivery problem, such as a sudden jump in failed sends or a drop in read rate after a template change, can run for a week before somebody looks. Meanwhile customers miss their reminders and the marketing budget is spent on messages nobody saw.

WhatsApp Business sends a status event for every message: sent, delivered, read or failed. The automation counts those events per day as they arrive. At 8:00 the next morning it works out the delivered and read rates from yesterday's counts, emails you the totals, and resets the counters for the new day.

It suits shops and clinics that treat WhatsApp as an operational channel and want one small number to check each morning.

What you get out of it

A failure spike shows up the next morning
If yesterday's failed count jumps from three to ninety, you know before lunch. That points to an expired token, a blocked number or a broken template, and you can fix it the same day instead of next week.
Read rate shows whether wording works
After you rewrite a reminder, the read rate in the next few emails tells you whether people respond better. You learn from real results rather than from opinions in a meeting about which version sounds nicer.
Delivered versus sent exposes bad numbers
A wide gap between sent and delivered usually means outdated phone numbers in your list. Seeing it daily gives you a reason to clean the list before it harms your sender reputation with WhatsApp.
Evidence for a cost conversation
Business messaging is billed per conversation, so knowing how many messages actually reached customers helps you judge whether a campaign was worth its cost, and helps justify or cut the next one.
Nobody builds a spreadsheet by hand
The counts and rates arrive as a finished email, so the person who used to copy numbers from several screens each morning gets that time back for work that needs a human.

How it works

What happens, step by step

Throughout the day, ClickRuntime counts each message you send on WhatsApp as sent, delivered, read or failed.
Every morning at 8, it adds up yesterday's numbers and works out the delivery and read rates.
You get an email such as "Sent 1,240, delivered 1,198 (97%), read 902 (73%), failed 14".

Before it runs live

Connect WhatsApp Business
Paste your automation's link into the other app's webhook settings

What you get

RunsCollects as they arrive, acts daily

Get a daily WhatsApp delivery and read reporttoday, 9:00Succeeded

Email · WhatsApp yesterdaySent 1,240, delivered 1,198 (97%), read 902 (73%), failed 14

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other WhatsApp Business steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

daily_delivery_and_read_rate_report.pyexample

from clickruntime import on_event, on_trigger, state, notify

STATUSES = ["sent", "delivered", "read", "failed"]

@on_event
def count(event):
    value = event.json["entry"][0]["changes"][0]["value"]
    for s in value.get("statuses", []):
        if s["status"] in STATUSES:
            state.increment_metric(f"wa_{s['status']}", ttl_days=30)
    return {"ok": True}

@on_trigger
def report(event):
    totals = {}
    for s in STATUSES:
        points = state.query_metric(f"wa_{s}", bucket="day")
        totals[s] = int(points[-2]["value"]) if len(points) >= 2 else 0  # yesterday's bucket
    sent = totals["sent"] or 1
    notify.email_me("WhatsApp yesterday",
                    f"Sent {totals['sent']}, delivered {totals['delivered']} ({totals['delivered'] / sent:.0%}), "
                    f"read {totals['read']} ({totals['read'] / sent:.0%}), failed {totals['failed']}")
    return totals

FAQ

Common questions

How are the rates calculated?

The delivered rate is delivered messages divided by sent, and the read rate is read divided by delivered. The email shows the raw counts as well, so you can check the arithmetic and see how large the sample was on a quiet day.

Why does the report use counters instead of querying WhatsApp?

WhatsApp does not offer a simple daily summary of message statuses on request. Status events are pushed to a webhook, so the automation counts them as they arrive and stores totals per day, which makes the morning calculation instant.

Are read receipts always available?

No. Customers who turned off read receipts in WhatsApp privacy settings never generate a read event, so the read rate is a lower bound. Delivered counts are not affected, and they remain the more reliable measure of reach.

What permissions does it need?

whatsapp_business_messaging. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Collects as they arrive, acts daily