Reports glossary: counting and response times
What each Analytics report answers and how conversations, reply times, reopens and waiting customers are counted.
- Plan
- Depends on your plan · Which plan do I need?
- Who can use this
- Account owner, Manager
What each Analytics report answers and how conversations, reply times, reopens and waiting customers are counted.
This page explains what each report in Analytics answers and how conversations, reply times, reopens and waiting customers are counted. Use it when two reports seem to disagree. SLA terms are in SLA Report terms, and spend and ad terms in WhatsApp Spend and Ads Performance terms.
Sidebar → Analytics. Which reports you see depends on your role. See Analytics overview.
| Report | What it answers | Plan feature |
|---|---|---|
| WhatsApp Spend | What Meta bills for your WhatsApp messages, what was free, and how to pay less | Every plan |
| Ads Performance | Which Facebook and Instagram ads bring customers to chat, what each chat costs, and where money or chats are wasted | ads_report |
| SLA Report | Whether your team keeps its reply and resolution promises during business hours, and who needs support | sla_report (plan or SLA add-on), and SLA switched on |
| Staff Report (basic) | Conversations, closes and first response per staff member | Every plan |
| Inbox Health | Who is waiting for a reply right now | advanced_analytics |
| Closing & Reopens | Why conversations end and which ones come straight back | advanced_analytics |
| Contact Reports | Contacts created in a date range, with their latest conversation | Every plan |
| Term | Starts | Stops | Business hours? | Bot replies count? | Kind |
|---|---|---|---|---|---|
| Avg first response (SLA Report) | The chat is first assigned to a person | A person's first reply | No, wall-clock | No | Mean |
| Own 1st reply (SLA Report, per staff) | This person got the chat | This person's first reply | No | No | Mean |
| First response (Staff Report (basic)) | First assignment in the period | First reply by the current assignee | No | No | Average, Median and "90% within" |
| Avg resolution (SLA Report) | The episode opened (or reopened) | The episode closed | No | – | Mean |
| Median time to close (Closing & Reopens) | The episode opened (or reopened) | The episode closed | No | – | Median |
| Avg time to assignment (Assignment Delay) | The episode opened | First assignment to a person | No | – | Mean |
| Median wait (Inbox Health) | The customer's last unanswered message | Now | No | – | Median |
| First reply (Ads Performance) | The customer's message from the ad | First reply from staff or bot | No | Yes | Median (average as fallback) |
"A person's reply" means a message sent by a staff member. Bot, quick-message bot, broadcast, system and failed messages don't count. A template that a staff member sends from the inbox does count.
Replies sent before the chat was assigned can't be measured for first response, so they are left out.
Average response time: no report has an "average response time" across all replies. The reports show first response, the SLA next-reply clock and resolution time.
Missed chats: no report has a "missed chats" metric. The closest are Untouched (closed with no reply) and Never assigned (Assignment Delay).
The Reports table above lists each report's plan feature. Check yours in Billing → Current Plan. A generated report covers at most 366 days.
Do it with Copilot
Do it with Copilot
| What you see | Why | What to do |
|---|---|---|
| Avg first response is empty ("No replies yet") | No person replied after assignment | Check Answered before assignment |
| SLA Report "Reopens" is higher than Closing & Reopens | One has no time window, the other uses N days | Compare like with like |