Analytics
Analytics gives a plain summary of messaging activity. It is deliberately small; everything on it is a real count, not an estimate.
Who can do this
- Owner
- Admin
- Agent
What is on the page
Overview
Four totals for the workspace:
| Card | Counts |
|---|---|
| Conversations | Every conversation |
| Contacts | Every contact |
| Messages | Every message, both directions |
| Campaigns | Every campaign |
Conversations
A bar split by status (Open, Pending, Closed) with the count under each.
Read it as a queue health check. A growing Open count with a flat Closed count means work is arriving faster than the team is finishing it. A large Pending pile usually means somebody is waiting on a third party and nobody is chasing it.
Campaign performance
Aggregate delivery across all campaigns: Sent, Delivered, Read and Failed.
- A gap between Sent and Delivered points at bad numbers or people who are not on WhatsApp with that number.
- A gap between Delivered and Read is about the message, not the plumbing.
- Failed rising sharply usually means the Meta payment method, the messaging limit, or a template that has been paused.
Per-campaign numbers are on the campaigns list and each campaign's own page.
Message activity
A 14-day bar chart of Inbound against Outbound messages, one pair of bars per day. Hover a day for the exact counts.
Useful for staffing: the days and volumes here are when your customers actually write to you.
What analytics does not show yet
To be straight about it:
- No per-agent performance, response time or resolution time.
- No per-template performance breakdown.
- No date-range picker; the chart is a fixed 14 days.
- No CSV export of reports.
If you need numbers that are not here, export your contacts and campaign results and work from those, or tell us what you need. That is how this page grows.
Related
- Campaigns
- Per-campaign delivery and read counts.
- Automation run logs
- Per-run detail for automations.