Replace the daily report with one saved question
Write it once in plain English. Caterfli runs it every morning — through the same agent, the same checks and the same audit trail.
Every morning, someone opens the admin panel, filters yesterday's orders, notes the total, does the same for revenue, refunds and unpaid orders, then repeats the whole thing for the same day last week so the numbers mean something. It is never a long job, but it is every single day. It is nobody's favourite part of the day, and it stops entirely the week that person is on holiday.
The question behind it is short: *how did yesterday go?*
Write it once
In Caterfli a report is a saved question, phrased the way you would ask a colleague. For the report pictured above:
How did yesterday go? Give me orders, revenue, refunds and orders still waiting for payment, each compared with the same day last week.
Save it, set it to run daily at 8:00, and the work is done. The agent runs it on schedule and the result is waiting before anyone gets in. Weekly and monthly work the same way, and any report can also be run on demand.
Specific beats vague here. Asking for named figures gives the agent something it can return as rows; "how are we doing" gives it room to ramble. If a report comes back thin, rewording the question is usually the fix.
It is not a second way in
The important property of a report is what it is *not*. It does not carry its own SQL or its own endpoint. It runs through the agent, using the same tools, the same policy checks and the same audit trail as anything typed into chat.
That is deliberate. A report with its own query would be a second route to your database, one that skips every check, and a scheduled report would be an *unattended* second route. A saved sentence can only reach what the agent can already reach.
It follows that reports inherit the approval gate. A report whose question asks for something destructive stops and is recorded as incomplete. That would be a strange report to write, and stopping is the right thing to happen.
Results, kept
Each run's result is stored, not just the latest. "Revenue was flat" only means something next to what it said last week, and the history is what lets you check.
The table is drawn from what the agent's tools actually returned, and a chart is offered from the numeric columns without anyone configuring one: table, bar, line or pie.
Real exports
Three formats, because they do three different jobs:
| Format | For |
|---|---|
| CSV | Feeding another system |
| Excel | Someone who will pivot it, with numbers kept as numbers |
| Sending to a person to read, capped at 500 rows |
Exporting is its own permission, separate from viewing. A viewer can read a report but cannot export it; a member can do both. Taking a table of customer data out of the platform is a different act from looking at it, so every export is audited with its format and row count.
Sent where people already are
A scheduled report can also be delivered to Slack, WhatsApp or Telegram. What arrives is the agent's own summary and a link to the full result, not a picture of a chart. The link opens that one run's result, chart and numbers included. Anyone holding it can read that result, and it stops working after seven days, so treat it the way you would treat the numbers. Where that is not acceptable, keep the report in the dashboard.
Someone spends every morning copying numbers into a spreadsheet covers the same idea from the other side of the desk.
One question, asked well, once. Then every morning it answers itself.
0 comments
Sign in to join the discussion.