Plan requirement
| Subscription | Suite Professional or higher |
| Also required | Copilot |
| Access | Agent |
Asking questions about your data in plain language instead of building a report. Fast, and it needs checking.
What it does
You ask a question; it produces a report or an answer. No dataset to choose, no metric to find, no filters to assemble.
Where it earns its place
- A question asked once. Somebody in a meeting wants a number now.
- Finding a metric you know exists and cannot locate in a long list.
- Getting started when you do not yet know how a report should be built.
Where it does not
Anything reported to the business regularly. Those deserve deliberate construction with the definitions written down, because people will act on them for a year and the definitions need to hold.
It knows Explore, not your business
It can find the metric for solved tickets. It cannot know that your team excludes one brand from every figure, or that "escalation" means something specific here.
Those conventions live in your head and in your dataset, and they are exactly what makes a number right or wrong.
Read the answer as a report
Metric, grouping, filters, period. If any of those four is not what you meant, the number is answering a different question, and it will look just as confident.
Treat it as a draft
Good for getting to eighty per cent in a minute. The last twenty per cent, which is where the correctness lives, is still yours.
Comments
0 comments
Article is closed for comments.