WhatsApp analytics for teams: what you can measure
WhatsApp gives teams per-message receipts and insights on broadcasts and channels. What each proves, what to track for groups and campaigns, and the gaps.
- Written by
- By WavesFlo team
- Last updated
- Updated
- Reading time
- 8 min read
WhatsApp gives a team three sources of numbers: ticks and Message info on each message, insights on paid business broadcasts where available, and insights on channels with 100 or more followers. Nothing totals them across numbers or teammates, or measures reply speed. Team reporting combines receipts, group activity and exports, with read rates treated as a floor.
This guide is for whoever has to answer for a WhatsApp operation: a sales manager with six reps on three numbers, a distributor with dealer groups across Gujarat, an admissions head at a coaching institute. It covers what WhatsApp reports on its own, what receipts can and can't prove, what to review each week, and where reporting runs out. The arithmetic of a single campaign has its own guide.
What analytics does WhatsApp Business give you?
| Source | What it shows | Limits |
|---|---|---|
| Ticks on a message | Sent, delivered to the recipient's phone or a linked device, and read | In a group, the ticks only turn blue once every member has read the message |
| Message info | When your message was delivered, read or played, person by person, including each group member | One message at a time. It keeps listing members who have since left the group |
| Business broadcasts, in the WhatsApp Business app | Per broadcast: deliveries, reads and replies. Across broadcasts: replies and an average read rate | Paid per delivered message and offered in limited countries. Excludes people with read receipts off, and some figures may be estimated |
| Channel insights | Net follows, accounts reached and top regions over 30 days, plus views, reactions and poll votes on each update | Only for channels with at least 100 followers, and figures can lag by about a week |
| Multi-agent, a paid feature | Which agent or device sent each message, and which chats are assigned to whom | Shown per message, not as a report. Up to 10 devices on Meta Verified for Business or Meta One plans |
What's missing is anything a manager would call a report. There are no totals across chats, numbers or teammates, and nothing measures how long a customer waited for an answer. WhatsApp's help centre describes neither for the Business app as of October 2026.
What can delivery and read receipts prove?
Receipts are the only data WhatsApp gives you on every message, so it pays to know exactly what each proves. One grey tick means the message left your phone. Two grey ticks mean it reached the recipient's phone or one of their linked devices. Two blue ticks mean it was read. In a group, the second tick appears only once every member has received the message, so a manager checking a dealer group needs Message info rather than the ticks.
Read figures are a floor, never a census, for reasons WhatsApp's help centre lists itself:
- People can switch read receipts off for one-to-one chats. The switch doesn't apply to groups.
- When someone gets a message from you for the first time, a read receipt might not be sent.
- Someone who reads a notification without opening the chat hasn't opened your conversation, so no receipt arrives.
- If read receipts are off on your own business phone, you can't see anyone else's in one-to-one chats. Check this first when a number's read rate collapses overnight.
- A message stuck on one grey tick may mean the phone is off, or that the person has blocked you. WhatsApp won't tell you which.
So label read rates "at least", compare them only between similar messages, and treat delivered as the sturdier number. Who read your message in a WhatsApp group walks through the Message info screen.
What should a WhatsApp team report each week?
Start from the questions a manager actually asks, then match each to a source that can answer it honestly. For a team running a handful of numbers, a one-page weekly review covers most of it:
| Question | Measure | Where it comes from |
|---|---|---|
| Did our messages land? | Delivered and failed, counted from receipts | Campaign results, or Message info for one-off sends |
| Did people read them? | Read rate, labelled as a floor | Receipts, and business broadcast insights where available |
| How many people did we reach? | Distinct people, not the sum of group sizes | Campaign results, deduplicated across groups |
| Which groups are still alive? | Member messages by hour, joins and leaves | Group analytics, or a monthly read of each group |
| Who is still waiting for us? | Unread chats and the shared queue, checked at fixed times | Inbox filters: a snapshot, not a report |
| What happened to each enquiry? | Chats per label, such as quote sent or order confirmed | Labels set by people, reviewed weekly |
| How fast do we reply? | Time from a customer's message to the first answer | Not reported by WhatsApp. Sample by hand or build it from webhooks |
Two habits keep the numbers comparable from week to week. Take snapshots at the same times, say 11:00 and 17:00 IST, and agree what each label means before anyone uses it. A label called "hot" that means something different to every rep produces a chart nobody can act on; WhatsApp Business labels covers naming that holds up.
How do you measure WhatsApp groups?
Groups need their own view, because a group's health is about its members rather than your sends. WhatsApp shows little here beyond Message info on your own posts and the votes on a poll, which makes group polls the cheapest way to get a number out of a group. WavesFlo's group analytics cover every group your connected numbers belong to:
- Busiest hours: a histogram of member activity in your timezone, so posts go out when people are reading.
- Message mix: how the members' own messages split across text, image and video.
- Top senders: who drives the conversation, and when each was last active.
- Membership: joins and leaves rebuilt into a daily timeline, so a post that drives people out shows up the next day.
- Per-group rates: delivery and read rates for each group on its own, never averaged across groups.
A group whose members stopped talking weeks ago, or one that loses people after every campaign, is telling you something an average would hide. Managing many WhatsApp groups covers what to do with groups that have gone quiet.
What do WhatsApp campaign results show?
WavesFlo campaigns send one personalised message per row of a Google Sheet or CSV, to people on a list or into groups, and the results are counted from delivery receipts rather than from sends: targets, sent, delivered, read and failed. Reach is a floor of distinct people, deduplicated across groups, because the same buyer is often in three of your groups. Time to deliver and time to read are given at the median and the 75th and 90th percentiles, direct, group and channel sends are reported separately, and a message log shows each message's status, receipts, the number it went from and the time.
Eleven reports export as CSV and JSON, so the monthly pack can live in your own spreadsheet or BI tool instead of in screenshots. How to read campaign numbers without overclaiming is covered in campaign metrics that hold up.
Can you track WhatsApp response times?
Not from WhatsApp. Its help centre describes no report of reply times or team workload, and the paid multi-agent feature shows which agent sent a message one message at a time.
If you need the number, two methods give you one you can check:
- Sample by hand. Once a week, open twenty conversations at random and note when the customer wrote and when someone first answered. Twenty is enough to spot a problem, though not a figure to promise anyone.
- Build it from message events. If your numbers run through a service that sends a webhook for every message received and sent, push those events into a Google Sheet through n8n or Power Automate and work out the gaps chat by chat. Webhooks can arrive twice or out of order, so deduplicate on the event id before measuring. The webhooks guide covers the set-up.
Either way, report the sample size next to the figure. A median reply time from twenty chats, labelled as such, is more useful than a precise-looking number nobody can check.
Questions
Does the WhatsApp Business app have analytics?
Some, as of October 2026: ticks and Message info on every message, insights on paid business broadcasts (deliveries, reads and replies) where that feature is available, and insights for channels with at least 100 followers. It has no report across chats, numbers or teammates, and none of reply times.
Why is my WhatsApp read rate so low?
Because a read rate is a floor. People can switch read receipts off in one-to-one chats, a first message may not send a receipt, and a message read only in a notification isn't counted. If read receipts are off on your own phone, you can't see anyone else's in one-to-one chats.
Can I see which team member replied to a customer on WhatsApp?
In the WhatsApp Business app, only with the paid multi-agent feature, which shows which agent or device sent each message. In WavesFlo's shared inbox, each conversation is given a named owner, by hand, or by round-robin within a team on Growth and Enterprise, so you can see who holds it.
Can I measure response times on WhatsApp?
Not with WhatsApp's own tools, as of October 2026. Sample conversations by hand, or log message events from webhooks into a sheet and calculate the gaps yourself.
How do I export WhatsApp reports?
WhatsApp's broadcast and channel insights are read inside the app. WavesFlo offers eleven reports, each exportable as CSV and JSON, so the numbers can go into your own spreadsheet or BI tool.
Sources
- WhatsApp Help Center: How to check read receipts (checked 5 Oct 2026)
- WhatsApp Help Center: How to manage your business broadcasts (checked 5 Oct 2026)
- WhatsApp Help Center: About business broadcasts
- WhatsApp Help Center: How to see channel metrics and insights
- WhatsApp Help Center: About multi-agent
- WhatsApp Help Center: Being blocked by someone