> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/kaiya-conversational-ai/kaiya-responses.md).

# Kaiya responses

All about working with the responses generated by Kaiya

### Answers in Tellius 6.4

* **Answers in the right shape.** A one-line question gets a one-line answer. Kaiya returns a number, a sentence, a table or a chart, whichever the question needs. When the question calls for it, Kaiya checks the data first.
* **Results first.** Each answer starts with the results. Notes about what Kaiya plans to do next stay out of the answer.
* **Clarifying questions when they matter.** When a question is unclear, such as a quarter with no year, Kaiya asks before it answers, and you reply in the same conversation. See [Clarification questions](#clarification-questions) below.
* **Follow-ups that build on the last answer.** When you push back or add a condition, Kaiya adjusts the answer it already gave, so follow-ups return faster.
* **Repeat an analysis.** Once an analysis is done, ask for the same one on another region or segment. Kaiya runs the same steps and returns the same outputs in the same format. If the value you name is not in the Business View, Kaiya asks which one you mean.

#### How Kaiya got this

Each answer has a **How Kaiya got this** card above it. The card shows the work behind the answer, so you can check where a number came from. In earlier releases, this card was named **Thought Process**.

* **While Kaiya works.** The card stays closed and shows a single status line. The line names the step Kaiya is on, such as **Reading the data's structure...**, **Querying the data...** or **Running an analysis...**, and counts the steps so far, for example **· 6 steps**. The line updates in place as Kaiya moves on, so the conversation doesn't fill up with progress messages.
* **When the answer is ready.** The card reads **Done** with the time the answer took, for example **Done · 2m 19s**. Select the card to open it. Select it again to close it.
* **The steps, in plain words.** When you open the card, its header shows **Took** with the total time. By default, the list shows the steps that matter for the answer, named by what Kaiya did, for example **Finding data sources**, **Reading the data's structure**, **Working out the dates**, **Querying the data**, **Running an analysis**, **Checking the result** and **Reviewing the result**. A query step shows the short name of the query beside it, and **Thinking** rows show Kaiya's reasoning as text. Select a step to expand it.
* **Your skills.** When Kaiya applied one of your custom skills, a **Using your skill** step names the skill. Kaiya's own built-in guidance is not listed in this view.
* **Deep Insights.** A Deep Insight also shows **Investigation** with how many parts of its plan are complete, for example **11 of 11 complete**. Select **Show plan** to see the plan.
* **Detailed view.** Turn on the **Detailed view** switch to list every step Kaiya ran, with the time each one took. This includes the built-in guidance Kaiya loaded and steps such as **Catalog Context**, **Time Window** and **Sql Run**. Turn the switch off to go back to the plain-language steps.
* **Your personalization.** When one of your personalization answers changed an answer, **Detailed view** includes a **Based on your personalization** step that says which preference it was and how it changed the answer. See [Personalization Questions](https://help.tellius.com/settings/kaiya-and-ai/personalization-questions).

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2Fc6V8yeRjKd8pgssIgoJk%2Fkr-how-kaiya-got-this.png?alt=media&amp;token=aeb328cf-34b7-4d90-b423-a0373a898249" alt="The How Kaiya got this card open on an answer, with the Detailed view switch highlighted" width="563"><figcaption></figcaption></figure>

**The review.** For many answers, a separate reviewer checks Kaiya's work before you see the answer. Its **Reviewing the result** step shows a **Verdict**:

* **Pass** with **No issues** means the reviewer found nothing to fix.
* **Regenerate** means the reviewer found something to correct. Kaiya then fixes its work, and the fix is reviewed again before the answer is written.

The verdict also shows how many claims were re-verified. A **Worth verifying** note names anything you may want to check yourself before you rely on it. Select **Read full review** to read the reviewer's notes in full.

{% hint style="info" %}
**When to use Detailed view.** The plain-language steps are enough to see which data Kaiya used and what it checked. Turn on **Detailed view** when you need the exact query behind a number, want to see which step made a slow answer slow, or are sharing the full trace with your administrator or Tellius support.
{% endhint %}

#### Citations

Small numbers beside the figures in an answer are citations. Each one links a figure to the step that produced it.

* **Hover over a number** to see a card that names the step, explains in a sentence what it worked out, and shows how many rows it returned. For many figures, the card also lists the **METRIC** and how it is calculated, the **FILTER** that was applied, the **LEVEL OF DETAIL** (how the data was grouped) and the **SOURCE**: the Business View and table, and any analysis step the figure passed through.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2FtcOIltPuk5E9QMIKtQS9%2Fkr-citation-hover.png?alt=media&amp;token=df892e7f-577b-4889-87c5-cdc3c8a1b65c" alt="A citation hover card beside a figure in an answer, with Read more highlighted" width="563"><figcaption></figcaption></figure>

* **Select Read more** to open the citation in the panel beside the conversation. The panel starts with the plain-language summary, the number of rows and the Business View. Expand **How it was calculated** to see the SQL or Python code behind the figure. **Data** shows the rows the step returned. Select the **X** to close the panel.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2F1wATSfG3TUlpd6Ac4E5L%2Fkr-citation-panel.png?alt=media&amp;token=3e248cab-4a2b-41bd-82b8-a32a3d8f856b" alt="The citation panel beside the conversation, with How it was calculated highlighted" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
**Hover card or Read more?** Hover for a quick check of what a number means and which filter it used. Open **Read more** when you need to confirm the exact calculation or see the rows, for example before you share a figure with others.
{% endhint %}

#### Under each answer

* A **Based on** line names the Business View the answer used.
* In earlier releases, an answer that used your saved preferences showed a note under it, **Answered using your preferences**, with a **View preferences** link. Tellius 6.4 no longer shows this note. To see what your preferences changed, open **How Kaiya got this** and turn on **Detailed view**. See [How Kaiya got this](#how-kaiya-got-this) above and [Kaiya's persistent memory](https://help.tellius.com/kaiya/kaiyas-persistent-memory).
* Files Kaiya created, such as a summary page or an export, appear as cards. Select a card to open it in the panel beside the conversation.
* **Follow-up questions** lists questions that fit the analysis. The first two show at once. Select **Show 2 more** (the number depends on the answer) to see the rest, and **Show fewer** to hide them again. Select a question to ask it.
* Kaiya can also offer actions that fit the answer, such as creating an App from it or setting a schedule for it.

#### Message times and copy

* Hover over a message to see when it was sent, such as **2 hours ago**. Hover over the time to see the exact date and time.
* A copy icon sits beside the time, for your own messages and for Kaiya's answers. Copying an answer copies all of it, and the icon briefly shows a check mark.

#### Other refinements in 6.4

* **SQL.** When Kaiya shows SQL in its answer, it appears in a code block. In **How Kaiya got this**, with **Detailed view** on, each **Sql Run** step lists the **SQL** Kaiya ran, its **Parameters** and its **Output**. Select the copy icon beside any of them to copy it. The icon turns into a check mark when the copy succeeds.

<figure><img src="https://1702728550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC5PhRxmOjkQZJEO6F9Zw%2Fuploads%2Fqc9g38miLzpjbGVf2dOX%2Fsql-run-step.png?alt=media&amp;token=04108e63-836e-4cbf-bae2-9169375aa52a" alt="A Sql Run step in the Thought Process, with the copy icons beside SQL and Parameters" width="563"><figcaption></figcaption></figure>

* **Chart sorting:** chart values follow the measure on the Y-axis, not the alphabetical order of the labels.
* **Previews in the side panel:** Excel and CSV exports, images and HTML files open in a preview in the side panel. Markdown and text files that Kaiya creates also open in a preview, with a download icon.

### Resulting chart

{% hint style="warning" %}
Steps 1 to 7 below, and the hint after them, describe releases before Tellius 6.4. In Tellius 6.4, a chart in Kaiya chat has no **Add to Vizpad**, **Switch Chart** or **Filter** buttons, and answers have no thumbs icons. A completed Deep Insight answer, one built in several steps, shows an export icon. Select it, and Kaiya exports that analysis in the same conversation. The icon isn't shown on an answer that is itself an export, on a conversation someone else shared with you, or on the **Report** tab of a Mission briefing. It is unavailable while an export is running, and when the Kaiya cost limit is used up. For any other answer, ask Kaiya for a file. See [Exporting Kaiya conversations](https://help.tellius.com/kaiya/kaiya-conversational-ai/exporting-kaiya-conversations). A chart's three-dot menu has **View**, with **Chart**, **Data** and **Raw**, and **Actions**, with **Export**, **Copy image to clipboard** and **View in full screen**. To correct an answer, tell Kaiya in the same conversation, and it adjusts the answer it already gave.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/NxcUw2j59oIwx0hNGdTP/Frame%20665.png" alt="" width="563"><figcaption><p>Example of a resulting chart</p></figcaption></figure>

1. Click on the **View Data** toggle button to view the underlying table data of the chart. Alternatively, you can click on the three-dot submenu of a chart and select **Detailed view**.
2. Click on **Add to Vizpad** to add the chart to an existing or a new Vizpad. You can select from the list of available Vizpads displayed.
3. Click on **Switch Chart** to switch the chart to a different type. The list of applicable chart types will be displayed and you can select the required chart type. For more details, check out [this section](/tellius-6.4/search/know-your-charts-in-tellius/switching-to-another-chart.md).
4. Click on **Filter** to apply filters to the chart.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/nOfSkDABWAYjOkG5zeQz/image.png" alt="" width="230"><figcaption><p>Applying filters to a chart</p></figcaption></figure>

5. Click on **Download** and select the required format in which you want the chart to be downloaded.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/zOscNlm4lJhT3mNeKGrS/image.png" alt="" width="255"><figcaption><p>Download format</p></figcaption></figure>

6. If you’re satisfied with the result, click on the **thumbs-up** button. It will be saved and your preferences will be saved for future queries.
7. If you’re not satisfied, click on the **thumbs-down** button. To remediate the results, click on **Fix it**. If you don’t want to resolve the issue, but only want to provide feedback, click on **Give feedback**.

{% hint style="warning" %}
In releases before Tellius 6.4, the thumbs up/thumbs down feedback is available only in a live conversation and not in history. If the thumbs up or thumbs down is once clicked for a chart, it cannot be changed.
{% endhint %}

### Copy and Export Kaiya results

{% hint style="info" %}
**In Tellius 6.4:** use the copy icon beside an answer to copy all of it. See [Message times and copy](#message-times-and-copy) above. A chart's three-dot menu has **View**, with **Chart**, **Data** and **Raw**, and **Actions**, with **Export**, **Copy image to clipboard** and **View in full screen**. A completed Deep Insight answer, one built in several steps, shows an export icon. Select it, and Kaiya exports that analysis in the same conversation. The icon isn't shown on an answer that is itself an export, on a conversation someone else shared with you, or on the **Report** tab of a Mission briefing. It is unavailable while an export is running, and when the Kaiya cost limit is used up. For any other answer, ask Kaiya for the whole answer as a file. See [Exporting Kaiya conversations](https://help.tellius.com/kaiya/kaiya-conversational-ai/exporting-kaiya-conversations). The rest of this section describes copy and export in releases before Tellius 6.4.
{% endhint %}

In releases before Tellius 6.4, alongside the download option, Kaiya provides flexible copy and export actions across all response types (text, charts, and tables) so you can reuse and share results without rework or screenshots.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/4nUhN9uE5gQKwGDgbarS/image.png" alt="" width="375"><figcaption></figcaption></figure>

**Copy to clipboard (per element):** You can copy individual elements from any Kaiya response directly to your clipboard. Text responses are copied as plain text, ready to paste into documents, emails, or chat messages. Charts and tables are copied as PNG images. This lets you grab exactly the piece of the response you need without exporting the entire result.

**Export (per element):** Individual charts can be exported as .png, .jpg, .pdf, or .csv files. Individual tables can be exported as .csv or Excel files. This lets you move data directly into spreadsheets or reporting tools.

**Export Result as Doc:** For complete sharing, Kaiya supports exporting the full result of a conversation response as a single editable Word document (.docx). The exported document contains all text, charts, and tables from the result, formatted with a clean, consistent layout. This is designed for turning Kaiya's analytical output into stakeholder-ready artifacts (reports, decks, and briefs) without manually stitching together multiple screenshots or exports.

### Reflection-based auto verification

{% hint style="info" %}
In Tellius 6.4, this check is the **Reviewing the result** step in **How Kaiya got this**, with its **Verdict**. See [How Kaiya got this](#how-kaiya-got-this) above. The rest of this section describes releases before Tellius 6.4.
{% endhint %}

Kaiya is designed to get you to a usable answer as quickly as possible. When you ask a question, Kaiya begins executing the analysis and renders the first usable output (typically a data table) as soon as it is ready, even while it continues working on the remaining steps in the background (such as chart generation, formatting, and reflection-based validation).

As soon as the initial table appears, you can begin validating the direction of the answer, checking whether the right columns and filters were applied, or deciding on your next follow-up question.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/s8C73KZx1RkqZ6j5yg1p/image.png" alt="" width="563"><figcaption></figcaption></figure>

* After Kaiya generates its initial results, a Reflection agent automatically reviews whether the output actually matches what you asked for.
* The Reflection agent checks for issues such as incorrect grain (the level of detail in the results does not match what was asked), missing constraints or filters that should have been applied based on your question, and partial coverage where only part of a multi-part question was addressed.
* If the Reflection agent identifies a mismatch, Kaiya adjusts the execution plan and re-runs the query or the specific step that produced the incorrect output. The final result you see reflects the corrected analysis.

For straightforward queries, reflection typically confirms the result is correct without any delay. For more nuanced questions (such as those involving multiple metrics, time comparisons, or conditional logic) reflection acts as a safety net that significantly improves first-attempt accuracy.

### Ask Kaiya to summarize conversations

Kaiya can generate a summary of the entire conversation thread on demand. This is designed to consolidate context across a long, multi-step exploration into a single, clean narrative that you can share or use as a reference.

**How to ask Kaiya to summarize?**

At any point during a conversation, type a prompt like "Summarize the entire conversation" or "Summarize what we learned and list the top drivers." Kaiya will process the full thread and generate a consolidated summary.

**What does the summary include?**

The summary incorporates relevant context from across the entire conversation, including results from **Deep Insights**, direct analytical queries, earlier summaries generated within the thread, and metadata queries. Kaiya synthesizes these into a single coherent narrative.

{% hint style="info" %}
This capability is most valuable at the end of a long investigative session where you have explored multiple angles, drilled into different segments, and generated several charts and tables.
{% endhint %}

The resulting summary can be copied or exported (using the copy/export capabilities described in [this](#copy-and-export-kaiya-results) section) and shared directly with stakeholders.

### Preamble

{% hint style="warning" %}
The Preamble describes releases before Tellius 6.4. In Tellius 6.4, Kaiya chat has no Preamble. To see how Kaiya worked out an answer, open **How Kaiya got this** on that answer (named **Thought Process** in earlier releases). See [How Kaiya got this](#how-kaiya-got-this).
{% endhint %}

Kaiya includes a **Preamble,** a short, insightful explanation that appears before each response. This section breaks down exactly how your question was understood and how the answer was derived. It helps you build trust, learn the logic behind the response, and verify that Kaiya correctly interpreted your intent.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/1yMGGjkf5oHD6SnaJv0M/image.png" alt="" width="563"><figcaption><p>Preamble</p></figcaption></figure>

It walks you through how Kaiya:

* Interprets your query
* Identifies key metrics, dimensions, and filters
* Selects the most relevant dataset
* Analyses and applies logic
* Validation & finalization

See exactly how data fields, filters, and groupings were mapped to your question. If you notice a mismatch in what was interpreted, adjust or rephrase your question.

With this preamble-first approach, Kaiya doesn’t just give you an answer—it helps you understand the reasoning behind it. This makes your analysis more reliable, traceable, and smarter with every question.

### Clarification questions

Kaiya is designed to get you the most accurate answers by making sure it understands your question correctly. Sometimes, the way you phrase a question might include words that could mean different things depending on context. In those cases, Kaiya will pause and ask you a clarification question before proceeding with the analysis.

<figure><img src="https://content.gitbook.com/content/C5PhRxmOjkQZJEO6F9Zw/blobs/o92dfDQJO5Xay5wFQbUy/image.png" alt="" width="563"><figcaption><p>Kaiya asking a clarification question</p></figcaption></figure>

A clarification question is a smart prompt that Kaiya shows when your original question could be interpreted in multiple ways. For example, if you say:

*<mark style="color:red;">“Show me sales by product and cost”</mark>*

Cost could mean *“average cost”, “total cost”* etc. Kaiya might ask:

*<mark style="color:green;">“Just to clarify, did you mean to see ‘sales’ by ‘product id’ and ‘average cost’?”</mark>*

This ensures that Kaiya understands exactly what you’re looking for, before it selects columns, generates charts, or calculates results.

#### When Kaiya asks

* **Filters or dimensions are unclear.** *"Compare performance"* without specifying by-region, by-product, or by-period.
* **Aggregations or metrics are ambiguous.** *"Show me growth"* could mean period-over-period, a trend, or a rate.
* **Column names or values need confirmation.** When multiple columns could match what you asked for.

#### How to respond

In Tellius 6.4, Kaiya asks in a card in the conversation, one question at a time:

* **Pick an option** by selecting it or pressing its number key. The card shows the keys you can use, such as **1-4**. On a question with one answer, picking an option moves you to the next question.
* **Type your own answer** in the row below the options when none of them fits.
* **Several choices.** When a question takes more than one answer, select each one, then select **Confirm** to move on.
* **Press Enter** to confirm your answer and move on.
* **Skip** passes over the current question, and Kaiya uses the question's default when it has one. Skipping the last question sends your answers.
* **Submit** appears on the last question and sends your answers once every question is answered or skipped.
* **Move between questions.** When there are several, use the arrows beside the counter, such as **1 of 3**.

{% hint style="success" %}
**Answer or skip?** Answer when the choice changes the result, such as which Business View or which time period Kaiya should use. Skip when any reasonable choice is fine for you, so Kaiya can carry on.
{% endhint %}

When Kaiya asks a clarifying question, you have three options:

* **Pick from the options shown**, or supply the missing detail directly (for example, *"compare by region,"* *"use the revenue column"*).
* **Refine your question** to add context.
* **Ask a new question** to change direction entirely; Kaiya starts fresh.

After you respond, Kaiya runs the analysis with the disambiguated parameters and returns the result the same way as a direct question.

{% hint style="info" %}
Saved memories reduce future clarifications. When you respond to a clarification, Kaiya can offer to remember your choice as a memory. In Tellius 6.4, a saved choice like this is a **Rule** memory (**Preference** memories in earlier releases became Rules). The next time the same ambiguity comes up, Kaiya applies your saved choice without asking.
{% endhint %}

Once you respond to the clarification prompt, Kaiya updates your request using the confirmed terms. This promotes transparency, improves trust, and helps you get more meaningful results from your data conversations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.tellius.com/tellius-6.4/kaiya/kaiya-conversational-ai/kaiya-responses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
