> 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/settings/kaiya-and-ai/personalization-questions.md).

# Personalization Questions

Set the short questions Kaiya asks each user, such as their role or the accounts they cover, so it can tailor how it writes answers for them.

Under **Settings → Intelligence → Kaiya & AI → Personalization Questions**, administrators set the short questions Kaiya asks each user, such as their role, the accounts or regions they cover and what they track most. Kaiya uses each user's answers to tailor how it writes answers for that person.

### How personalization works in Tellius 6.4

* **Background context for the whole conversation.** A user's answers are loaded when a conversation starts and stay in effect for the whole conversation, including follow-up questions. Personalization is separate from skills and memory. Kaiya applies it in the background, and it doesn't appear as a message in the conversation.
* **Two groups of questions.** Questions in the **How answers are written** group shape wording, depth, formatting and charts. They never change which rows or values Kaiya computes. Questions in the **What Kaiya assumes** group hold defaults that Kaiya uses when a question leaves the choice open, such as a time frame, so they can change what Kaiya computes. A value the user names in the question always wins over a default. A group appears on the page only when it holds at least one question, so a workspace whose questions are all in **How answers are written** shows only that group.
* **See what personalization changed.** Open **How Kaiya got this** on an answer and turn on **Detailed view**. A step labelled **Based on your personalization** says what changed. See [How Kaiya got this](https://help.tellius.com/kaiya/kaiya-conversational-ai/kaiya-responses#how-kaiya-got-this).
* **Users answer when it suits them.** Users answer from a card in Kaiya chat, or on the **Context** page: open the **Skills** tab and select **Personalization**, the last item in the list on the left. Every user can see it. This page in Settings is for administrators only. See [How users answer](#how-users-answer) below.

{% hint style="info" %}
**Personalization, skills or memory?** Use personalization for who the user is and how they like answers written, such as their role, their region or a preference for short summaries. Use a skill for a way of working that should apply to everyone or to a team, such as a house report format. Use memory for business rules and definitions, such as what "active customer" means. See [Kaiya Skills](https://help.tellius.com/kaiya/kaiya-skills) and [Kaiya's persistent memory](https://help.tellius.com/kaiya/kaiyas-persistent-memory).
{% endhint %}

### The question list

The page lists the questions in the order Kaiya asks them. A question that depends on an earlier answer sits under a label such as **If they pick "Regional Sales Director / RVP"**, so you can see which answer leads to it.

Each row shows:

* the question, and its header as a tag, such as **Role**, **Scope**, **Focus** or **Context**
* **Asked of everyone** when the question doesn't depend on an earlier answer
* a summary of the answer type, for example how many options there are, whether users pick one or several, and whether they can type their own answer
* when the question was last updated

Each row has these controls:

* **Drag handle** (the dots at the left): drag the question to change the order in which Kaiya asks it.
* **Arrow:** expand or collapse the question's details.
* **Switch:** shows whether the question is asked of users. It matches **Asked of users** in the editor.
* **Edit** (pencil): open the question editor. See [Edit a question](#edit-a-question).
* **Delete** (trash can): remove the question.

{% hint style="warning" %}
**Turn off or delete?** To stop asking a question for a while, turn it off with its switch, and turn it back on when you need it again. Delete a question only when you no longer need it.
{% endhint %}

### Add a question

At the bottom of the list, describe the preference you want to capture in your own words, for example *ask which region they cover*, and select **Add**. **Add** becomes available once you type a description. Tellius turns the description into a question. Select **Edit** on the new question to check its wording and options.

### Edit a question

Select **Edit** (the pencil) on a question to open its editor.

* **Question:** the wording users see.
* **Header:** the short label for the question, shown as a tag in the list.
* **Helper text:** a line shown with the question to help users answer, for example to explain why it is asked.
* **They choose from:** the options users pick from.
  * Tick **Pre-ticked** to select an option in advance. Users can still change it.
  * Use the up and down arrows to change the order of the options.
  * Select the trash can to remove an option.
  * Select **Add option** to add another one.
* **Users can pick more than one:** turn on to let users select several options. Leave it off for a single choice, such as a role.
* **Users can type their own answer:** turn on to let users answer in their own words when no option fits.
* **Asked of users:** turn off to stop asking the question without deleting it.
* **Group:** choose **How answers are written** or **What Kaiya assumes**. The question appears under that group on the page.
  * **How answers are written** changes wording, depth, formatting and charts, never the rows or values Kaiya computes.
  * **What Kaiya assumes** holds defaults for choices a question leaves open, such as a time frame. These can change what Kaiya computes. A value the user names in the question wins over the default.
* **Asked only after:** choose the question that must be answered first, so this question is asked only as a follow-up. **Asked of everyone** means the question doesn't depend on another one.
* **Kaiya is then told:** a preview of the instruction Kaiya receives when a user picks an answer. Check it to make sure the question has the effect you expect.
* **Key:** the name that answers are stored under. It can't be changed, so existing answers stay linked to the question.

Select **Save** to keep your changes, or **Cancel** to close the editor without saving.

{% hint style="info" %}
**Which group?** Choose **How answers are written** when the answer should only change how Kaiya presents results, such as a preference for short summaries or for tables over charts. Choose **What Kaiya assumes** when the answer should fill a gap in a question, such as the time frame or region a user usually works with. Users can still name a different value in a question, and that value is used instead.
{% endhint %}

{% hint style="success" %}
**Pre-tick or not?** Pre-tick an option when most users would choose it, so they can confirm with one click. Leave all options unticked when the answer differs from person to person, such as a role or a region. A pre-ticked answer that doesn't fit a user can steer Kaiya the wrong way for them.
{% endhint %}

### How users answer

Users answer the questions in two places. The **Personalization Questions** page in Settings is for administrators only, so users don't answer there.

**In Kaiya chat.** If a user hasn't answered yet, a card titled **Tailor Kaiya to how you work** appears in the conversation after a few turns.

* **Start** begins the questions. **Not now** skips them for now, and Kaiya asks again later. **Don't ask again** stops the card for good.
* The card shows one question at a time with its place in the list, for example **2 of 5**. Select **Next** to go on, **Back** to return to the previous question, or **Skip this one** to leave a question unanswered. At the end, **Review** takes the place of **Next**.
* **Here's what I'll remember** shows the answers before they are saved. Select **Save** to keep them, or **Back** to change an answer.
* After saving, the answers apply from the user's next question. Select **View Personalization** to see the saved answers, or **Done** to close the card.

**On the Context page.** Users can also find their answers on the **Context** page. Open the **Skills** tab and select **Personalization**, the last item in the **Context layers** list on the left. Every user can see it. The answers are grouped under **How answers are written for you** and **What I assume when you don't say**, and each answer has a **Remove** button to drop just that answer.

* **Set up:** answer the questions for the first time.
* **Retake setup:** go through the questions again to change the answers.
* **Clear all:** remove all of the user's answers.

{% hint style="success" %}
**Card or Context page?** The card in Kaiya chat is the quickest way to answer for the first time, right where the user is working. Use **Personalization** on the Context page to check what Kaiya remembers, to change answers later with **Retake setup**, or to start over with **Clear all**.
{% endhint %}


---

# 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/settings/kaiya-and-ai/personalization-questions.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.