Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Agent |
The feature is called AI-powered quick reports. You describe the report instead of building it, and the checking is still yours.
Use it
- In Analytics, click the reports icon.
- In the reports library, click Quick report.
- Enter your prompt in the prompt area at the bottom of the panel. The report generates automatically.
- Read what it produced, filters included, and refine with a follow-up prompt.
- Keep it with Edit in report builder, or add it to a dashboard.
The four limits, before you plan around it
| 200 characters | The input query cannot exceed it, so a long, precise question has to be split across follow-up prompts. |
| Support - Tickets only | No other dataset. Anything needing ticket updates, such as status history or backlog development, is not a quick report question. |
| No custom fields | Custom fields, and calculated metrics and attributes, are not supported. Your own vocabulary is exactly what it cannot use. |
| 150 per user per day | The maximum number of reports one person can generate in a day. |
It works on historical data, not live data, and on the languages OpenAI supports. An admin can switch the feature off for the account.
Say the period, or it picks one
If you do not specify a time range, quick reports apply a default range that suits the report. That is convenient and it is also the most likely reason a number does not match what you expected. If you want the whole history, say so in the prompt.
Be specific, inside 200 characters
"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.
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.