Reports and management
Support numbers live in two places: the Support overview, a live dashboard for whoever supervises the operation, and the Reports screen, with volumes, team performance, customer ratings and CSV export. This page explains each indicator, how it is calculated and why average times only count business hours.
Where the numbers are
| Place | What it is for | Periods | Permission |
|---|---|---|---|
| Support overview (Conversations screen, first item in the sidebar) | Follow the operation live: queue right now, who is handling conversations, times for the period, team, peak hours. Refreshes on its own. | Today, 7 days (default), 30 days, 90 days | Supervise all conversations |
| Reports (Administration menu) | Closing and analysis: volumes, by agent, by department, by connection, reasons, breaks, spelling and CSV export. | Last 7 days, Last 30 days (default), Last 90 days | Reports |
| AI consumption (button in the Audit log) | How much the artificial intelligence consumed and cost, ticket by ticket. | 7, 30 or 90 days | Audit log |
Both dashboards use the same calculation criteria, so the numbers match when the period is the same. Periods count whole calendar days including today: "last 7 days" starts at midnight six days ago and runs until now.
The numbers cover the whole operation, with no breakdown by department or connection: anyone with access to the reports sees everything. To give a supervisor access, use the permissions in Access profiles.
Times counted only during business hours
ChatISP average times only count what falls within the configured business hours. Both screens say so right above the numbers: Times count only the configured business hours.
Example: the internet service provider (ISP) works from 08:00 to 18:00. A customer writes at 19:50 and the conversation is closed at 08:10 the next day. On the wall clock that would be more than 12 hours; in ChatISP this conversation counts as 10 minutes, which was the time actually spent within working hours. Without this rule, nights and weekends would inflate everyone's average.
Rules
- The schedule of the conversation's department applies when it has one; otherwise, the system's general schedule. Schedules are set up in Departments and in Settings.
- With no schedule registered at all, the clock runs nonstop (24 hours a day, 7 days a week).
- A conversation that started and ended entirely outside business hours counts as 0 seconds.
- Overlapping time ranges on the same day are merged, so no minute is counted twice.
- In the duration of conversations, the periods in which the conversation was marked as awaiting reply from the customer are also deducted: time when "the ball is in the customer's court" does not count against the agent.
- There is no option to turn this off: it is the standard way to measure support times.
What stays on the wall clock
- The timeline of each conversation, in the chat, shows the real times.
- Waiting on customer (how long, on average, conversations stayed awaiting reply) is the real wait, on the wall clock.
- Longest wait, in the Overview, shows how long the oldest customer in the queue has been waiting, in real time.
- Agents' time on break.
In the CSV export, the Handling within business hours (s) column holds the useful duration of each closed conversation, already applying the rules above, so you can check it or build your own average.
Support overview
For users with the Supervise all conversations permission, the Conversations screen opens by default on the Support overview: "Numbers, results and team performance in one place." It is the first item in the screen's sidebar (Overview); clicking any queue goes back to the conversations, and a direct link to a conversation opens the chat without going through the overview.
Period and refresh
- Buttons at the top: Today, 7 days (default), 30 days and 90 days.
- Today runs from midnight until now, the chart switches to hourly (from 0h to the current hour) and the comparison is made against all of yesterday.
- The screen refreshes on its own every minute while it is visible. With the tab in the background or another queue open, it does not query the server.
- The charts adapt to the light or dark theme and to the screen size.
Support activity
The main block shows the total number of conversations received in the period, the sentence "X received · Y closed in the period" and an area chart with two lines: Received and Closed, per day (or per hour, in Today).
Next to the total is the change compared with the immediately preceding window of the same length (for example, the 7 days before the last 7), with an up or down arrow and the text vs previous period (or vs yesterday, in Today). If the previous window had no conversations, the change is not shown.
How conversations end
Donut chart of the conversations closed in the period, with the percentage solved by the AI in the center:
| Slice | How it is counted |
|---|---|
| Solved by the AI | Closed with no agent assigned and with at least one message from the AI assistant. |
| By the agents | Closed with an agent assigned. |
| Automation and others | The rest: closed by the automated flow, by inactivity before reaching anyone, and similar cases. |
Overview: Right now
The cards in the Right now strip (with the Live badge) show a snapshot of the moment and do not depend on the chosen period:
| Card | What it counts |
|---|---|
| In queue now | Conversations in the queue waiting for an agent. |
| Longest wait | How long the customer who has been in the queue the longest has been waiting (counted from the conversation's last message, or from when it was opened). Only shown when someone is in the queue. |
| Being handled | Conversations with a human agent right now. |
| Awaiting reply | Open conversations marked as awaiting reply from the customer. |
| With the AI | Conversations being handled by the AI assistant. |
| In automation | Conversations in the automated flow (menus, self service). |
| Agents in action | How many different agents have at least one conversation in service right now. |
| Agents on break | How many agents are on break at this moment. |
| Closed today | Conversations closed since midnight. |
Overview: In the period
The cards in the In the period strip follow the selected period button. Times follow the business hours rule.
| Card | How it is calculated |
|---|---|
| Time to pick up | Average, across conversations opened in the period, of the time between opening and the first moment an agent picked up the conversation or automatic distribution handed it to someone. |
| First reply | Average time between the customer's first message and the first reply sent (by the AI or by an agent). Automated flow messages do not count as a reply. The opening of the conversation is not used as the starting point because history synced from the phone may arrive with old dates. |
| Average duration | Average useful duration of conversations closed in the period, from opening to closing, deducting time outside working hours and the periods awaiting reply from the customer. |
| Waiting on customer (avg) | Among conversations closed in the period that stayed awaiting reply, how long on average they waited for the customer (wall clock). In parentheses, how many conversations had a wait. |
| Average rating | Average of the 1 to 5 scores from satisfaction surveys sent in the period (see Satisfaction survey). |
| Solved by the AI | Conversations closed in the period with no agent and with AI participation, and in parentheses the percentage of all closed conversations. |
| Closed by inactivity | Conversations the system closed because the customer stopped replying. |
| Messages received | Messages received from customers in the period. |
| Messages sent | Messages sent in the period, adding up AI, agents and automations. |
When there is not enough data for an average time in the period, the card shows "-".
Overview: panels
When customers reach out
Heat map of 7 days of the week by 24 hours, with the number of conversations opened in the period for each day and hour combination. The stronger the color, the more activity. The Peak appears in the corner, for example "Peak: Mon at 9h". Use it to size the team's schedule.
Support flow
Funnel of conversations opened in the period, with the percentage of each stage over the total received:
| Stage | What it counts |
|---|---|
| Conversations received | All conversations opened in the period. |
| Handled by the AI | Those with at least one message from the AI assistant. |
| Reached an agent | Those picked up by someone, distributed to someone or currently with an agent. |
| Closed | Those already closed. |
Team
"Each agent's performance in the period", with up to 30 active agents who had conversations or messages in the period. At the top, three highlights:
- Most conversations: who closed the most conversations (in a tie, who handled the most).
- Fastest to pick up: lowest average time to pick up, among those who handled at least 3 conversations.
- Best rated: highest average score, among those who received at least 2 ratings.
| Column | What it shows |
|---|---|
| Agent | Name, with the On break label if the agent is on break right now. |
| Handled | Conversations opened in the period that are (or ended) with the agent. |
| Closed | Of those, how many have already been closed. |
| Time to pick up | Average time between opening and the moment the agent picked up or received the conversation. |
| Avg. duration | Average useful duration of the agent's closed conversations. |
| Customer wait | Average reply wait in the agent's conversations that had a wait. |
| Messages | Messages the agent sent in the period. |
| Breaks | Total time on break in the period. |
| Score | Average of the ratings answered in the period, with the number of replies in parentheses. |
The best value of Closed, Time to pick up and Score is highlighted in the table.
Departments, Closing reasons and Channels
- Departments: conversations opened in the period by department, with "wait time · N in queue": the average time to pick up in that department (on its own schedule) and how many conversations are in its queue right now.
- Closing reasons: how many conversations closed in the period received each reason.
- Channels: conversations opened in the period by connection, indicating whether it is WhatsApp (QR) or Official API.
Service orders
Only shown to users with the Manage service orders permission. Shows Open, Unassigned, Overdue and Solved today; each card and the Open board link lead to the Service orders board.
AI assistant
The percentage "of closed conversations solved by the AI", followed by Conversation turns (how many times the AI processed a reply in the period), Errors (turns that failed), Average latency (average AI response time) and Solved by the AI.
Reports screen
Open Reports in the menu (Reports permission): "Support volumes and results". At the top are the period selector (Last 7 days, Last 30 days, Last 90 days) and the Export CSV button. Changing the period reloads the whole screen and also adjusts the export.
Top indicators
| Indicator | How it is calculated |
|---|---|
| Conversations opened | Conversations opened in the period. |
| Conversations closed | Conversations closed in the period. Below, "N by inactivity" when there are any. |
| In progress now | All conversations not closed at this moment (queue, human service, AI and automation), regardless of the period. |
| Resolved by the assistant alone | Closed in the period with no agent assigned and with AI participation. |
| Handed to agents by the assistant | Conversations transferred in the period by an automatic decision (by the AI or the flow), with no manager involved. |
| Messages received | Messages from customers in the period. |
| Messages sent | Messages sent in the period, with the detail "X by the assistant, Y by agents" (the rest are automations). |
| Time to first reply (average) | From the customer's first message to the first reply from the AI or an agent, within business hours. |
| Queue wait (average) | From opening until an agent picks up or distribution hands over the conversation, within business hours. It is the same calculation as Time to pick up in the Overview. |
| Average duration | Useful duration of conversations closed in the period, deducting time outside business hours and reply waits. |
| Waiting on customer (average) | Average reply wait of closed conversations that stayed waiting on the customer (wall clock). |
| Satisfaction | Average score from 1 to 5, with "X replies out of Y surveys". |
Report charts and tables
| Card | What it shows |
|---|---|
| Conversations opened per day | Bars with the total number of conversations opened on each day of the period. Hover to see the date and the number. |
| Assistant | Turns processed, Failures, Average latency, Tokens (input / output) consumed in customer service and Suggestions generated for agents. |
| By agent | Up to 30 agents with conversations or messages in the period (including those already deactivated), with Handled, Closed, Messages, Duration (average useful duration of the agent's closed conversations) and Score (average rating, with the number of replies). |
| By department | Conversations opened and closed by department. |
| Closing reasons | How many conversations closed in the period received each reason. |
| Breaks | Per agent: how many Times the agent went on break and the total Time on break in the period (a break still open counts up to now). |
| By connection | Conversations opened and closed by WhatsApp connection, indicating WhatsApp (QR) or Official API. |
| Spelling by agent | "Messages sent to the customer from the panel, checked by the spell checker at send time. Errors per 100 words is the fair measure for comparison." Columns: Messages, Words, Errors, Errors / 100 words and Most misspelled words (correction), with each agent's five most misspelled words, the suggested correction and how many times they appeared. The list starts with whoever has the highest error rate. |
In the per agent tables, conversations count for whoever is (or ended up) handling each one. A conversation transferred from Ana to Bruno counts for Bruno. Messages, on the other hand, count for whoever sent them.
Satisfaction survey
When the Send the survey when closing handled conversations option is turned on in Settings, the customer receives the configured question at the end of each conversation handled by a person (default: "How would you rate today's service? Reply with a score from 1 to 5."). The reply is only recognized as a score if it contains a number from 1 to 5, and a customer who replies with a score receives an automatic thank you message. Details in Settings.
| Where it appears | How it is counted |
|---|---|
| Satisfaction (Reports) and Average rating (Overview) | Average of the scores from surveys sent in the period. The detail shows how many were answered out of how many were sent: that is the response rate. |
| Score per agent | Average of the ratings answered in the period in that agent's conversations, with the number of replies. |
| CSV export | Score and Comment columns for each conversation. |
When comparing agents, always look at the number of replies next to the score: a 5.0 average from a single reply says little. That is why the Best rated highlight requires at least two ratings.
Export CSV
The Export CSV button on the Reports screen downloads a spreadsheet with one row per conversation opened in the selected period. The file is named chatisp-conversas-30d-AAAA-MM-DD.csv (with the number of days in the period, followed by the date as year, month and day) and opens directly in Excel, LibreOffice or Google Sheets with correct accented characters.
| Column | Content |
|---|---|
| Ticket | The conversation's ticket number. |
| Opened at / Closed at | Opening and closing date and time (empty if still open). |
| Status | Current status: In queue, In service, With AI, Closed and so on. |
| Channel | Name of the WhatsApp connection. |
| Department | The conversation's department. |
| Agent | Who is handling (or ended up handling) the conversation. |
| Reason | Closing reason. |
| Score / Comment | Reply to the satisfaction survey. |
| Messages | Total messages in the conversation. |
| Customer wait (s) | Seconds during which the conversation stayed awaiting reply from the customer. |
| Handling within business hours (s) | Useful duration in seconds, only for closed conversations (see business hours). |
| Tags | The conversation's tags, separated by " | ". |
With the system in Portuguese or Spanish, columns are separated by semicolons, which is the default for spreadsheets configured for Brazil; in English, by commas. Column names follow the system language.
CSV times are in seconds to make spreadsheet calculations easier. To see them in hours, divide by 3600 (or by 86400 and format the cell as time).
AI consumption
On the Audit log screen, the AI consumption button opens the "Cost audit: what the AI consumed in each ticket and how much it cost". Access is the same as for the Audit log (Audit log permission), and the period can be 7, 30 or 90 days.
Period summary
- Cost in the period, in Brazilian reais, with the dollar exchange rate used and its date. With no exchange rate available, the amount appears in dollars with the notice No exchange rate available: amounts shown in US dollars (US$).
- Calls made to the AI, Input tokens and Output tokens.
Table by ticket
One row per conversation (ticket number and customer name), from most recent to oldest, showing what the AI was Used for and how many times (Customer service, Ticket summary, Service order summary, Translation, Menu titles, Menu interpretation, Agent text, Copilot), the calls, the tokens and the Cost. Usage that does not belong to any conversation (for example, the Copilot outside a conversation) is grouped as Outside tickets. The list loads more rows as you scroll.
Tokens are the exact numbers returned by the AI provider on each call, with no estimates. The cost is calculated from the official price table for each model.
To understand what the assistant does and how to configure it, see Artificial intelligence. The Assistant card on the Reports screen shows the volume of turns and tokens in customer service; the AI consumption screen is the one that shows the cost.