Answering KPI questions in natural language
Turn a quarterly KPI question into a governed, cited answer: inspect the schema, run the query, verify the metric and source.
You have a vetted product and a key performance indicator (KPI) question: "what was quarterly revenue by customer segment?" This recipe turns that into a governed answer, with the metric and source model cited, so you can trust and reproduce the number. The journey is inspect schema → run the governed query → slice further → confirm it was governed.
What this enables:
Steps
Example responses below are illustrative: exact wording, fields, and figures depend on your catalog, your data, and your permissions.
1. Inspect the schema
Before asking for numbers, find out what the product can answer, so you ask for measures that exist and slice by dimensions it supports:
What metrics and measures does orders360 expose?The assistant returns the queryable surface: the measures, the dimensions you can slice by, and which models join to which. Think of it as the menu before you order. This is the schema part of Understand in natural language.
2. Run the governed query
Ask the business question in plain language:
Example response:
Q1 2025
Platinum
$842,300
Q1 2025
Gold
$511,200
Q2 2025
Platinum
$901,150
Q2 2025
Gold
$529,800
The assistant translates it into a governed query against the semantic layer, applies the joins and access policies, and returns the result. Because it goes through the semantic layer, the number uses the product's own definition of revenue, not an ad-hoc recalculation. If the underlying result set is larger than the platform's row limit, the response states that output was capped, so you know to slice further rather than treat it as the full set.
3. Slice further
Follow up to refine, without rebuilding anything:
Example response:
Q1 2025
Electronics
$410,900
Q1 2025
Home & Garden
$267,400
Q1 2025
Apparel
$164,000
Same measure and joins as before, now filtered to
orders.CUSTOMER_SEGMENT = 'Platinum'and grouped byorders.PRODUCT_CATEGORY.
Each follow-up reuses the same governed measures and joins, so the numbers stay consistent across slices.
4. Confirm it was governed
Trust comes from knowing where the answer came from. Ask the assistant to cite it:
Example response:
orders.TOTAL_REVENUE = SUM(orders.TOTAL_AMOUNT), from theorderssemantic model, joined tocustomersoncustomer_idfor the segment dimension. Filters applied:order_datein 2025,customer_segment = 'Platinum'.
A governed answer names the measure and the source model, so you can reproduce it.
Troubleshooting
The assistant returns a limitation instead of a number
The question cannot be answered from the product's semantic surface rather than a wrong number being invented. Re-check step 1's measures and dimensions and rephrase around what is actually exposed.
A measure or dimension you expect is missing
It is not exposed on this product's semantic model. Ask What metrics and measures does <product> expose? again to confirm the current list, or check a different product with Discovering the right Data Product in natural language.
Slicing by a dimension gives an error or no result
That dimension may not join to the measure you asked for. Ask Which dimensions can I use with <measure>? before slicing.
The number doesn't match a figure from another source
Ask step 4's citation question. Differences usually trace to a different metric definition, filter, or time window, not a broken query.
The response says output was capped
The result set exceeded the platform's row limit. Narrow the question (a shorter date range, a specific segment) or slice further as in step 3, rather than treating the capped response as the complete answer.
The assistant returns an authentication or authorization error
Ask your administrator for the mcp-tool-read grant under use-mcp-service, or a tenant role such as data_consumer or data_developer. See Governance and trust.
Outcome
You turned a KPI question into a governed answer, computed from the product's own metric definition and cited to its source model, so you can slice it further and reproduce the number.
Outcome
You turned a KPI question into a governed answer, computed from the product's own metric definition and cited to its source model, so you can slice it further and reproduce the number.
References
Understand in natural language: the full range of schema, quality, lineage, and run questions you can ask before querying
Save as Perspective: save this query for reuse
APIs: wire the governed answer into an application
Last updated
Was this helpful?