JivoChat automation · runs weekly
Weekly JivoChat missed chats and agent report
Every Monday someone opens Statistics, picks the dates, waits for a file and opens it just to see how many chats nobody answered.
Cotlet does it in your own JivoChat account with get_aggregated_report, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can JivoChat do this on its own?
JivoChat offers no API for statistics (checked 20 Oct 2026). Its webhooks send each chat_finished event, so a team with its own server can count finished chats, but missed chats and per-agent totals are not in that payload. The report is a manual download for administrators.
How you do it in JivoChat today
- An administrator opens the JivoChat app and goes to Statistics > Aggregated Report.
- The administrator selects an interval of up to 180 days and clicks Download, then chooses Excel or CSV.
- JivoChat shows a notification that the file is being generated. After a few minutes the file is ready, and work in chats can go on meanwhile.
- The file holds three blocks: totals for all channels, the same counts per agent, and agents' statistics separated by each channel.
- The JivoChat help center advises a period of 90 days at most so the download does not get overloaded, so a long period is split by hand.
How to weekly JivoChat missed chats and agent report
Every Monday, pull last week's JivoChat aggregated report and tell me accepted and missed chats for the account and for each agent. - 01
Fix the period
The agent turns "last week" into Monday to Sunday dates and calls get_aggregated_report once. A period longer than 180 days is refused, and the agent splits one over 90 days into several calls, as the help center advises.
- 02
Read the three blocks
The report returns totals per channel, totals per agent and agents per channel. The agent checks that the agents' accepted chats add up to the channel total, so a missing agent shows up.
- 03
Mark the missed chats
A chat is missed when no online agent accepted it and 15 minutes passed after the client left, or when everyone logged out with chats waiting. The agent puts the share of missed chats next to the accepted number for each channel.
- 04
Compare with the week before
A second call for the previous week gives the change. The agent reports a rise in missed chats and names the channel, and says nothing about causes it cannot see in the data.
- 05
Stop on a missing role
Only administrators can generate the report. A call from an agent account returns APP_PERMISSION_DENIED, and the agent says which role is missing instead of retrying.
What you get back
JivoChat, 12 to 18 Oct
Live Chat: 118 accepted chats, 9 missed (7%)
Sam Rivera 71, Priya Nair 47
Previous week: 104 accepted, 5 missed
Missed chats rose by 4 Other ways to ask
- Send me this report every Monday, and flag it when missed chats are above last week's number.
- Show the last 30 days one week at a time, per agent.
- Compare the accepted chats of each agent in the last 90 days.
What JivoChat allows, and what to know first
- Only a JivoChat administrator can generate the aggregated report, and the interval can be up to 180 days.
- The report counts accepted chats, accepted calls, missed chats and missed calls, and it also pulls in telephony and callback data.
- JivoChat counts a chat as missed when no online agent accepted it and 15 minutes passed after the client had left the website, or when all agents logged out while chats were still waiting.
- The Chat Topics statistics are a separate tab in Statistics, so the report does not show why people wrote.
Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.
Sources: JivoChat Help: How to generate an aggregate report · JivoChat Blog: More statistics, telephony and callback reports · JivoChat Help: How to configure Chat Topics · JivoChat Docs: Webhooks API
Call get_aggregated_report from a script
curl "https://cotlet.dev/api/v1/jivochat/aggregated-report?date_from=2026-10-12&date_to=2026-10-18" \
-H "Authorization: Bearer $COTLET_API_KEY" {
"period": {
"date_from": "2026-10-12",
"date_to": "2026-10-18"
},
"by_sites": [
{
"channel": "Live Chat",
"accepted_chats": 118,
"accepted_calls": 0,
"missed_chats": 9,
"missed_calls": 0
}
],
"by_agents": [
{
"agent": "Sam Rivera",
"accepted_chats": 71,
"accepted_calls": 0
},
{
"agent": "Priya Nair",
"accepted_chats": 47,
"accepted_calls": 0
}
],
"by_agents_per_site": [
{
"channel": "Live Chat",
"agent": "Sam Rivera",
"accepted_chats": 71,
"accepted_calls": 0
},
{
"channel": "Live Chat",
"agent": "Priya Nair",
"accepted_chats": 47,
"accepted_calls": 0
}
]
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is jivochat_read → get_aggregated_report. Example data.
Schedule it in n8n, Make, Zapier or cronJivoChat tools this automation uses
| Tool | Parameters |
|---|---|
| get_aggregated_report | date_from, date_to |
Frequently asked questions
Is it safe to connect JivoChat to Cotlet?
Yes. You sign in to JivoChat yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JivoChat once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.
Give your agent access to JivoChat.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with JivoChat.