Reports

A report is a question phrased the way you would ask a colleague, saved so you can ask it again.

It runs through the agent, which means it can only reach data the agent can already reach, and it is subject to the same checks. A report whose question asks for something destructive will stop for approval and be recorded as incomplete — which is strange for a report, and the right thing to happen.

Tables and charts

The result table is pulled from what the tools returned. If a report produces nothing useful, rewording the question usually fixes it — asking for "revenue by month" rather than "how are we doing" gives the agent something to return as rows.

Exports

CSV to feed another system, Excel for someone who will pivot it, PDF to send to a person. PDF is capped at 500 rows on purpose; if you want everything, take the CSV.

Exporting is a separate permission from viewing, and every export is recorded. Taking a table of customer data out of the platform is a different act from looking at it on screen.

Getting it sent to you

A scheduled report can be delivered to Telegram, Slack or WhatsApp as well as waiting in the dashboard. Pick the channel when you create the report and give it the chat to send to — the numeric chat id on Telegram, the channel id on Slack, the phone number on WhatsApp.

What arrives is the agent's own summary and a link, not a picture of the chart. A chart can only go into a chat window as an image, and rendering one on the server would mean running a browser in the background for every scheduled report. The link is better anyway: it opens the real report on whatever device you are holding, with the chart live and the numbers underneath it.

Anyone with that link can read that one result. It is a single run rather than the report or the workspace, and it stops working after seven days, but treat it the way you would treat the numbers themselves. If that is not acceptable for a particular report, leave it as dashboard-only and read it signed in.