Reports

See how much your agent handled, how good its answers were and where it got stuck, and ask it for a written performance review on demand or on a schedule.

Your AI teammate keeps its own numbers: how much it handled, how good the answers were, where it got stuck.

Ask it in the chat. It reads its own figures, explains them, and can write a fuller report on the spot. Or read the charts yourself on the Reports page in the left sidebar.

The top of the Reports page: how much work came in, and which triggers brought it.

Ask your agent for a report

1

Ask in chat

Open the chat in your dashboard and ask for the report you want, for example a performance review for the month. Your agent reads its own setup and activity, picks the right report skill, and saves the report as a file in your agent's Files. In the chat it gives you the short version and offers to act on it.

The chat after a report ask: the linked review and the three changes it recommends.

Check it worked. The report is listed under Files in the left sidebar. From a terminal, eesel files lists it.

2

Open the report

Click the link in the chat, or the file under Files. The report opens as a document beside the chat, with the numbers first.

The health table at the top of the report.

Below the numbers come the recommendations, each with the evidence behind it and the change to make.

The Top Recommendations section of the report.

It ends with a summary table you can hand to your team.

Four prioritised actions, each with the conversations it would improve.

3

Put it on a schedule

Ask for a report every week, here a weekly review of your agent's own results, and your agent creates a schedule, runs it once straight away, and tells you what it found.

The weekly review asked for in chat, with the analysis running.

The schedule appears on your Automations page, switched on. Open it to change the day, the time or what the report covers.

The weekly review schedule, set to Monday at 8:00 AM UTC.

The skills behind these reports:

Skill	What it produces
Analyze ticket trends	The themes that keep coming up across your tickets, with sentiment, volume and how they get resolved
Simulation	A scored report of how your agent handles a batch of your real tickets, with the gaps and the fixes
Analyze and improve replies	The patterns in what your team rejected or edited, and the instruction changes that stop it happening again
Review agent setup	An audit of how your agent is set up and performing, with what to change

The Reports page

Open Reports in the left sidebar. Pick a window at the top: the last 24 hours, 7, 30 or 90 days, or a custom range.

Area	Card	What it tells you
Volume	Total number of tasks	How much work your agent picked up over the window
	Total trigger events by type	How that work reached it, by trigger
Quality	AI CSAT distribution	A quality score for the agent's answers across the window
	AI CSAT over time	The same score day by day
Knowledge gaps	Knowledge gaps	How often it did not have the knowledge to answer
	Knowledge gaps over time	Answered tasks against flagged gaps, day by day
Approvals	Approval / rejection usage per tool	For each action: approved, rejected, or still waiting
	Approval efficiency	How much went through first time
	Review times	How long your team takes to approve or reject
	Approval trend over time	Approvals and rejections day by day

Quality and knowledge gaps, as a snapshot and day by day.

How to read it:

• The trigger breakdown shows which triggers bring the most work, and which bring none.

• AI CSAT is not customer feedback. It is an AI's rating of your agent's answers. Useful as an internal quality signal, not a substitute for asking your customers.

• A knowledge gap is your agent telling you something is missing from your documentation. Rising gaps on one topic show which articles to write, and the Update knowledge base skill can draft them.

• Approvals tell you when to hand over more. An action approved every time without edits is ready to run on its own. One that keeps getting rejected needs an instructions fix. Long review times mean approvals are sitting unanswered.

Activity: the individual runs

Reports show the pattern. Activity in the left sidebar is where you look at one piece of work.

Every task your agent has run is listed there, from every app: a Zendesk ticket, a Slack question, an email and a scheduled run all appear in one history. For each one you can see:

• Where it happened, with a link to the original ticket or thread

• What set it off, the trigger or automation

• What it read, the sources it searched

• What it did, every action, and where a person approved it

• Why, its reasoning step by step

• Whether it hit a knowledge gap

When an answer is wrong, read what your agent searched, found and concluded, then fix the cause. Or point your agent at the run in chat. It walks you through its reasoning, offers the fix, and saves the rule to its instructions when you agree.

Exporting

Task data can be exported for your own analysis. Exports are prepared in the background and emailed to you as a download link when they are ready.

Related pages

• Skills for the reporting skills and how to run them

• Automations and Schedules to have reports arrive on a schedule

• Instructions and Memory for acting on what the reports tell you