Plan requirement
| Subscription | Suite Professional or higher |
| Also required | Copilot |
| Access | Agent |
Describing the report you want instead of building it. Good for a first draft, and the checking is still yours.
Use it
- Start a new report.
- Describe what you want in a sentence.
- Read the report it produces, including the filters.
- Adjust and save.
Be specific about the period and the grouping
"Tickets solved per month for the last year, by group, excluding spam" produces something close to right. "Show me ticket numbers" produces something, and you will spend longer correcting it than building it.
Check the filters before the chart
The generated report usually gets the metric right and the filters approximately. A date range or an exclusion you did not ask for changes the number without changing how convincing it looks.
Check the dataset
Some questions can only be answered from ticket updates rather than tickets. A generated report on the wrong dataset answers a nearby question, plausibly.
Where it is most useful
Getting to a rough report quickly on something you build rarely, and finding the name of a metric you know exists but cannot locate in the list.
Where it is not
Anything that will be reported to the business regularly. Those deserve to be built deliberately, with the definitions written down, because people will make decisions on them for a year.
Read it back as a sentence
Metric, grouping, filters, period. If that sentence is not what you asked for, adjust the report rather than the description.
Comments
0 comments
Article is closed for comments.