To answer "did this month go well?" you need to know how many messages arrived, how many conversations were closed, and how many sales your automations brought. The Reports screen puts those numbers on one page, always next to the previous period. This guide explains every card, every chart and every column of every table.
π‘ Reports works on both Instagram and WhatsApp accounts; it is channel-independent. The numbers here come from the panel's own records, not from Meta β for the distinction see Insights versus Reports.
In this article you will find:
Opening the screen and choosing a period
The twelve metric cards
The daily message flow chart
Conversion value
The channel table
The automation table
The agent table
The screen on phone and tablet
Common mistakes
Opening the screen and choosing a period
Click Reports in the left menu. This section has its own row there; its entry point is not buried inside another screen.
The heading reads Reports, with two lines underneath:
The period β The first and last day of the selected period.
Compared with β The equally long period immediately before it, in smaller type.
Five period pills sit to the right: Last 7 days, Last 30 days, Last 90 days, This month, Last month. The default is Last 30 days. There is no custom range on this screen.
Your chosen period stays in the address bar, so you can bookmark the view or send it to a teammate.
There is no Refresh button here, and none is needed: the numbers are read from the panel's own records and are current on every page load.
The twelve metric cards
Twelve cards sit at the top of the page. Each one holds the metric's name, its value for the period, a change badge and a "Previously: {number}" line.
Messages received β Every message that arrived from a contact during the period.
Messages sent β Every message that left the panel during the period. It can exceed the sum of the next two (system messages, triggered notifications).
Was this article helpful?
Sent by automations β The outgoing messages that automations sent.
Sent by agents β The outgoing messages a teammate wrote from the inbox.
New contacts β Contacts added to the list during the period.
Conversations opened β Conversations opened during the period.
Conversations closed β Conversations closed during the period.
Flow runs started β Automation runs that started during the period.
Runs completed β Runs that went all the way through.
Runs failed β Runs that ended with an error. On this card the badge is read the other way round: a fall is green, a rise is red.
Conversions β Conversion events recorded in flows.
First response time β The median wait from the moment a contact starts waiting until an agent's first reply. This badge is also reversed: getting shorter is green, getting longer is red. The value is written in seconds, minutes or hours; with no measurement at all it reads "Not measured".
What the change badge can say
"up 14.2%" / "down 9.7%" β The percentage change against the previous period.
"Unchanged" β The two periods are identical.
"New" β Nothing was recorded in the previous period and something was recorded in this one. No ratio is possible.
The panel does not store a conversation's closing moment separately. So the "closed" figure counts closed conversations that last changed during the period. Adding a note or a tag to a closed conversation moves it into the current period. The same limit applies to the Closed column in the agent table, and it is stated on the screen too.
The daily message flow chart
Below the cards sits a bar chart headed Daily message flow. Two bars are drawn for each day: Received and Sent. The legend below tells you which is which.
Hover a day and its values appear: "18 Sep Β· 47 received, 62 sent".
A day with no records is drawn as an empty bar, not a gap. So a day with zero messages does not vanish from the chart.
Day boundaries follow the account's time zone; the chart's description says so.
Over long periods the chart area scrolls sideways on its own.
The chart is most useful for seeing your weekly rhythm: which days are busy and which are quiet. You can plan your automations and your team's shifts around it.
Conversion value
The Conversion value panel sits to the right of the chart. It is the total of the amounts recorded by the conversion steps in your flows, grouped by currency.
Each currency has its own row: the currency code on the left, the total and a change badge on the right.
A conversion recorded without a currency is treated as the account's currency.
If there were no conversions in the period, the panel reads "Nothing recorded in this period."
The By channel table is only drawn if the account carries more than one channel record. An account is a single Instagram or a single WhatsApp account, so on most accounts this section never appears β it shows up on older accounts that still carry a retired channel record.
Its columns are:
Channel β The connection's name, with the channel type (Instagram / WhatsApp) underneath.
Received β Messages that arrived on that channel.
Sent β Messages that left on that channel.
New contacts β Contacts added on that channel.
Flow runs β Automation runs started on that channel.
Rows are ordered from the busiest channel down. A channel type switched off in the portfolio never appears in the table.
The automation table
The By automation table lists the automations that ran during the period. Its description carries a warning: "Only live runs are counted; draft tests are left out."
Its columns are:
Automation β The automation's name.
Started β Runs started during the period.
Completed β Runs that went all the way through.
Failed β Runs that ended with an error.
Conversions β Conversions recorded in that automation.
Value β The conversion amounts, listed separately per currency. A dash appears when there is no amount.
Rows are ordered from the automation that started the most runs down. With no runs in the period the table reads "Nothing recorded in this period."
The gap between Started and Completed is made up of runs sitting in the middle of the flow: those awaiting a reply, those waiting, and those that were interrupted. To inspect a single automation step by step, look at its own stats tab: Automation stats.
The agent table
The By agent table shows what each teammate did during the period.
Its columns are:
Agent β The person's name (or their email address if there is no name). A count of measurements can appear underneath: "18 measured".
Replies β The messages that person wrote from the inbox.
Conversations in β Conversations opened during the period and assigned to that person.
Closed β Conversations assigned to that person that are closed and last changed during the period.
First response (median) β The median of that person's first response times. With no measurement it reads "Not measured".
Rows are ordered from the person with the most replies down.
How first response time is measured
The wait starts with the message where the contact begins waiting: an inbound message that either follows an agent reply or is the first message in the period. The wait ends with the first agent reply written from the panel.
A message sent by an automation does not count as a reply. This matters: if your greeting is sent by an automation, the clock does not stop β it keeps running until a real person writes.
The median is used rather than the mean: a single overnight message answered in the morning ruins a mean but not a median.
β οΈ Note: This table covers the whole account. Users with the agent role cannot see this section: Reports is closed to them by default, and the role has no report-viewing permission either.
The screen on phone and tablet
The metric cards form two columns on a phone, three on a tablet and four on a wide desktop.
If the period pills do not fit on one line they scroll sideways, with an arrow button at the edge.
The chart and the conversion value panel stack on a phone and sit side by side on a desktop.
The breakdown tables scroll sideways within themselves on a phone; the page itself does not.
Who can see it
Owners and admins always see it.
Editors and viewers see it by default; the portfolio owner can switch it off.
Agents cannot see it: the role has no report-viewing permission.
When the section is closed it does not appear in the menu, and typing the address by hand does not help either. For where the setting lives, see the access policy guide.
Common mistakes and how to fix them
Expecting "Messages sent" to equal "Sent by automations" plus "Sent by agents". Some outgoing messages come from neither source.
Looking for your own test runs in the run counts. Draft and simulator runs never enter any figure.
Reading "Conversations closed" as an exact closing count. The closing moment is not stored; touching a closed conversation moves it into the current period.
Reading first response time as automation speed. Only human replies are measured.
Hunting for the channel table. On single-channel accounts it is never drawn; that is normal.
Reading conversion value as revenue. The amount is whatever the flow recorded; the panel does not take payments.
Looking for reach or follower counts in Reports. Those live in the Insights section.
If the numbers are far from what you expected, read How the numbers are calculated first; if the problem persists, contact our Support team.