Analytics Tools

Overview

From Copilot or a connected AI app, an AI can read four reports: how your agents performed, how one AI agent handled conversations, which countries your website visitors came from, and how many AI credits you used. It looks the actions up with find_actions and runs them with run_read_action (see MCP Server). All four only read, so they work at every access level, including Read only, and Copilot runs them without a Confirm card.

Permission required:Reports for all four actions. The person the connection runs as also needs the Copilot permission, and an app connected through the browser login needs the Analytics area ticked on the login screen.

Visitor statistics have two limits worth knowing before you build a report on them. History only goes back about 120 days — Yaplet deletes raw website-traffic records nightly once they pass roughly four months — and a single request covers at most 90 days. Both limits are applied for you rather than refused, with a warning returned alongside the data. Agent performance and AI credit usage are not affected by either limit.

Actions

Action	Level	What it does
`reports.agent_performance`	Read	Per-agent numbers for a date range: conversations handled, average response time and customer ratings.
`reports.ai_agent`	Read	How one AI agent handled conversations in a date range: per conversation, how much the AI handled on its own and how many of its answers succeeded, were neutral or failed, plus the AI handling rate for the whole period.
`reports.visitors`	Read	Visitor sessions per country for a date range, with the number of countries and total sessions.
`reports.ai_usage`	Read	Daily AI credit usage for up to 12 date ranges at once, so months or weeks can be compared side by side.

How It Works

AI agent results

The figures are counted per AI agent, so the AI first finds the agent with list_records and then asks for its numbers. A brand that has no AI agent produces no numbers here at all.
A conversation can have several parts: a new part starts when the AI has been quiet for more than three hours. A part counts as handled by the AI only when no human agent joined the conversation and nobody asked for one during the period.
The AI handling rate is the AI-handled parts divided by all parts. It tells you how much of the work the AI did without a person stepping in.

Visitor statistics

A range longer than 90 days is shortened. The end date is kept and the start date is moved forward, and a warning saying so comes back with the data.
A start date older than about 120 days is moved forward to the oldest day still held, again with a warning. If the whole range is older than that, you get zero rows and a plain explanation naming the earliest date data exists from — not an error, and not silently empty numbers.

AI usage

Credit usage covers every AI feature: AI agent conversations, Copilot, writing with AI and so on.
To compare periods, the AI asks for several date ranges in one call — for example this month and last month, or the last four weeks.

What an AI cannot do here

Change anything. All four actions only read.
Read the other charts of the Reports page — traffic sources, engagement metrics, custom events, the activity heatmap and chat activity over time. Of the traffic numbers, only sessions by country are available. Open them in the dashboard under Team → Reports.
Read visitor traffic older than about 120 days. Yaplet no longer holds it, in the dashboard or anywhere else.
Top up AI credits or change your plan. Money is human-only in every connection: the organization owner does it under Settings → Organization settings → Billing.

Example Prompts

"How are my agents performing this month, and who has the best customer ratings?"
"What's my AI agent's handling rate for the last 30 days?"
"Where are my visitors coming from this month?"
"Compare our AI credit usage between February and March."
"Give me a complete report for this month: agent performance, AI handling rate, visitors by country and AI credit usage."