> 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-missions/how-to-create-a-kaiya-mission.md).
# How to create a Kaiya Mission
Create a Kaiya Mission in a Kaiya conversation: build, check, publish, schedule and run it, with the Mission pane for its steps, preview, triggers and schedule.
Build a Mission by describing what you need in a Kaiya conversation. Kaiya turns your request into a plan of steps and runs it so you can check the result. A pane beside the conversation shows the Mission's steps, preview, triggers and schedule.
From the same screen you can change the steps, publish the Mission and set it to run on a schedule. You can also decide where each run's briefing is sent. This page walks through the whole flow, from the first request to the first scheduled run.
{% hint style="info" %}
**Coming from an earlier release?** In releases before Tellius 6.4, you built a Mission in Composer, the form-based Classic Editor, and changed it on the Mission Editor's **Last Briefing**, **Configuration** and **History** tabs. In Tellius 6.4, you describe the Mission to Kaiya and change it in the conversation. The Mission pane takes the place of the **Configuration** tab, the briefing on the Mission's page takes the place of **Last Briefing**, and **Run history** takes the place of **History**. Files come from export steps, so there is no separate **Outputs** section. Missions built in the Classic Editor keep running on their schedule. See [Missions built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-missions/missions-built-before-tellius-6-4).
{% endhint %}
{% hint style="info" %}
**When Kaiya Conversational AI is off.** In Tellius 6.4, you build and run a Mission in a Kaiya conversation. When an administrator turns off **Kaiya Conversational AI** for the workspace (**Settings → Intelligence → Kaiya & AI → Kaiya Configuration**), **Create Mission** is hidden in the Mission Library, and the address for a new Mission takes you back to the Mission Library. **Configure** opens a Mission without the chat panel, and **Run** on a Mission's page is unavailable. Users in a Kaiya embed session keep these options. See [The Mission Library and Mission page](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page).
{% endhint %}
### **In this section**
* [The Mission pane](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/the-mission-pane): the pane header and the **Steps**, **Preview**, **Triggers** and **Schedule** tabs.
* [The Mission Library and Mission page](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page): find and filter Missions, manage schedules, and use a Mission's own page, including **More options** and **Delete**.
* [Remix a Mission shared with you](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/remix-a-mission-shared-with-you): make your own copy of a Mission someone shared with you, then publish, run and schedule it.
### **Ways to start a Mission**
* **From the home page.** Select the **Mission** tag below the ask box and describe the Mission you want.
* **From the Mission Library.** Select **Create Mission**. See [The Mission Library](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page#the-mission-library).
* **From an analysis you already ran.** When a set of questions in a conversation is worth repeating, ask Kaiya to turn it into a Mission. Kaiya carries the steps of the analysis over into the Mission.
* **From an App.** Ask Kaiya to build a Mission that does the same analysis as an App, for example to receive it as a PDF every Monday.
* **From Slack or Microsoft Teams.** Ask the Kaiya bot in a thread to create a Mission. See [Slack Integration](https://help.tellius.com/settings/administration/slack-integration) and [Teams Integration](https://help.tellius.com/settings/administration/teams-integration).
* **From an existing Mission.** Open the Mission and select **Configure**. Kaiya usually opens the Mission's conversation, scrolls to the message that built the Mission and opens the Mission pane on the right, so you can keep working on it. If the Mission was shared with you, the pane shows its steps, preview, triggers and schedule as read-only. Select **Remix** to make your own copy that you can change. See [Remix a Mission shared with you](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/remix-a-mission-shared-with-you).
When you ask Kaiya to create a Mission from a conversation, the Mission opens in its own conversation in the Mission builder. That conversation starts with a summary of the context Kaiya carried over. To keep working in the same conversation instead, ask Kaiya to do so. Creating a Mission from a Deep Insight conversation creates a single draft Mission. If you later delete a Mission that was built in a conversation, the conversation stays.
### **Step 1: Describe the Mission**
#### **The ask box on the home page**
The home page opens with an ask box. Below it are four tags: **Deep Insight**, **Mission**, **App** and **Kaiya Architect**. Each tag tells Kaiya what kind of work you want to do. When you select **Mission**, a **Mission** chip appears inside the ask box, and the hint text changes to suggest a scheduled briefing. Select the **x** on the chip to remove it.
The ask box also holds these controls:
* **Kaiya and Search icons (top left):** switch the ask box between asking Kaiya and searching. You can also press **⌘K** to switch.
* **Attach (paperclip icon):** attach a file to your request, such as a document that lists your requirements.
{% hint style="warning" %}
The Attach icon is available when no tag is selected, or when you choose the **Deep Insight** tag. It is not available for **App**, **Mission** or **Kaiya Architect**. To add a file to a Mission, use **Upload File** in the Mission conversation. See [The message box](#the-message-box).
{% endhint %}
* **Auto detect BV:** the Business View selector. Leave it on **Auto detect BV** and Kaiya picks the right Business View from your request. Open the dropdown to choose a Business View yourself. The Business Views you have selected appear at the top of the list. The list also shows your Kaiya Context Models under **Context models**, next to **Business views**. When both a context model and a Business View fit your request, Kaiya uses the context model. See [Kaiya Context Model](https://help.tellius.com/data/kaiya-context-model).
* **Suggest:** fills the ask box with a relevant question you could ask. Select **Suggest** again for a different question. Use a suggestion as a starting point for your request, and edit it before you send it.
* **Microphone icon:** speak your request instead of typing it. Kaiya turns what you say into text in the ask box.
* **Voice mode icon:** converse with Kaiya out loud. See [Kaiya Voice Mode](https://help.tellius.com/kaiya/kaiya-voice-mode).
* **Send (arrow):** sends your request.
Below the tags, **Popular in your workspace** offers example requests that you can use as a starting point. The examples change to match the tag you select.
#### **Write the request**
Describe what the Mission should find, who it is for and how often it should run. Plain business language works best. For example:
* *"Report monthly recurring revenue, churn and churn risk by region for the latest complete week against the week before, with the largest movements."*
* *"Set up a weekly Mission that alerts me every Monday morning when a territory falls below 85% of goal."*
* *"I write this Friday note every week. Turn it into a Mission I can run for whichever region I pick."*
Kaiya reads your request, checks the data and builds the plan. If something is unclear, it asks you a question in the conversation before it goes further. Reply in the same thread. While Kaiya works, the reply shows **Working…** with a **Stop** button, in case you want to stop and rephrase.
{% hint style="info" %}
One request can ask for several things. A short instruction such as *"Build it, schedule it for Fridays at 4 PM and publish it"* covers all three. Kaiya still asks you to confirm before it publishes.
{% endhint %}
#### **What Kaiya builds for you**
Kaiya turns the request into ordered steps. Each step does one job and passes its result to the steps that need it.
| Step type | What it does |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Input** | Asks for a value at run time, such as a region or a territory, so one Mission works for many cases. |
| **SQL** | Pulls and adds up data from the Business View. |
| **Python** | Works on the data in ways SQL handles less easily, such as rankings, shares or performance classification. |
| **Summary** | Writes the briefing: the narrative, the tables and the charts. |
| **Rich Summary** | Writes a visual briefing, with a headline, cards for the key figures and a short explanation. |
| **Export** | Creates a file from the result: a PowerPoint deck, PDF report, Word document, Excel workbook or CSV file. |
| **Connected system** | Reads data from, or writes results to, a system you have connected, such as Snowflake or Slack. |
A few patterns are worth knowing:
* **Run-time values.** When your request leaves a value open, such as "for whichever region I pick", Kaiya adds an input step. When the Mission runs from the conversation or from **Run**, Kaiya asks you for the value and offers the step's default first. Scheduled runs use the value saved with the schedule, or the default.
* **Branches.** Ask for a different summary for each outcome, for example below 70% of goal, between 70% and 90%, and above 90%. A branched Mission can end with its own summary or file for each path, so each branch reports its own finding.
* **Alerts.** Ask for a result only when a condition is met, such as a territory falling below 85% of goal. When a run finds the condition is not met, the step that depends on it is marked **Skipped**, with the condition beside it, and the briefing says no alert was raised.
* **Visual summary by default.** New Missions end with a **Rich Summary** step. When a run finishes, the conversation gives a short summary and a **Visual summary** card that opens the full page. Missions built before Tellius 6.4 keep their text **Summary** step until you change it. See [Missions built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-missions/missions-built-before-tellius-6-4).
* **Several files from one run.** A Mission can include several export steps, so one run can deliver a PDF report together with several CSV files.
* **Export details in the export step.** Write the file's storyline, contents and design, including any logos, in the export step's instructions, so every run produces the same file. The export step comes first: a custom skill, such as a house deck format, applies only to what the export step leaves open.
* **PowerPoint files and house formats.** A .pptx file you attach in the conversation can shape the exports Kaiya makes in that conversation. The Mission doesn't save it as a template, so scheduled runs won't follow an attached file. To get the same format on every run, write the format in the export step's instructions, or use a custom skill. A skill labelled **PPT Export** or **Default** can also supply images and logos. See [Kaiya Skills](https://help.tellius.com/kaiya/kaiya-skills).
* **Dates that move forward.** Each run works out "latest" dates again, from the newest date in the data at the time it runs. If the data hasn't been refreshed since the last run, the briefing says which date its result applies to. For example, a daily alert that runs on 21 October, when the newest data is from 29 September, says that its result applies to 29 September. Steps that read from a connected system also work out dates such as "today" or "the next 7 days" again on every run.
* **Renamed columns.** When a source column is renamed, the Mission re-reads the schema and adapts, or tells you what changed.
* **Writing to a connected system.** Writing is off by default. The Mission owner turns it on for each step in **Manage access** with **Allow it to send, post and create**. **Run as** sets whether the step uses the connection of the person running the Mission or the Mission owner's. In Tellius 6.4, scheduled runs can read from connected systems but can't write to them yet. A step set to run as the owner works only when the owner runs the Mission. When someone else runs it, that step stops. See [Using connected systems in Kaiya](https://help.tellius.com/kaiya/tellius-mcp-server/using-connected-systems-in-kaiya). Each step card shows what was asked, the calls that were made, and whether the write succeeded.
The screenshot below shows an alert Mission on a day when its condition was not met.
### **Step 2: Review the plan in the Mission pane**
The Mission pane opens on the right side of the screen, next to the conversation. In the conversation, an **OPEN MISSION** card shows the Mission's name and version, for example **OPEN MISSION · V1**. Select the card to open the Mission pane.
The pane has a header and four tabs: **Steps**, **Preview**, **Triggers** and **Schedule**. For every control and option in the pane, see [The Mission pane](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/the-mission-pane).
### **Step 3: Change the Mission by asking**
Every part of a Mission can be changed from the conversation, including its name, description, steps, triggers and schedule. Describe the change, and Kaiya updates only the steps that need it. The rest of the plan stays as it was.
Some examples:
* *"Add the two bullet points from my last answer to the Friday Mission."*
* *"Use Gross Sales instead of Sales."*
* *"Change it to run on Fridays instead of Mondays."*
* *"Add a PDF export of the weekly brief."*
When you ask for a new finding, Kaiya adds the steps it needs. It also updates the steps that depend on them, such as the step that writes the summary, so the brief covers the new results.
Kaiya checks each change before it saves it. If it finds a problem, it asks whether to fix it or carry on. If a change cannot be applied, Kaiya explains why and saves nothing. The Mission stays exactly as it was.
{% hint style="info" %}
When one change should apply to several Missions and an App that reads from them, say so in one message, for example *"Update this metric across all three Missions and the App."* Kaiya updates each one, changing only what needs to change.
{% endhint %}
### **Step 4: Publish the Mission**
A Mission you are building is a draft. Publishing makes it the version that runs.
1. Ask Kaiya to publish, for example *"Publish this mission."*
2. Kaiya asks you to confirm with two options: **Publish** or **Not now**.
3. Choose **Publish** to make this version the one every run and schedule uses. Choose **Not now** to leave it unpublished.
After you answer, the conversation shows **Answered · 1 question** with your choice, and Kaiya confirms what happened. A Mission published from the conversation shows as Published in the conversation, in its configuration and in the Mission Library, where its version is marked **Active**.
A few things to know about publishing:
* After a successful preview, an unchanged plan is not run again when you publish.
* Python steps run on scheduled runs too, so they don't hold up publishing.
* Kaiya adds or changes a schedule only when you ask.
* When you publish after editing steps that have already run, Kaiya shows a message about it.
#### **Versions**
A Mission keeps every version you publish. The **Version** selector in the pane header lists each version with its name, a **Published** badge and the date and time it was published. The conversation marks versions with labels such as **V1 · Active Published** or **V5 · Draft**.
* **Active:** the published version that runs. Manual runs and scheduled runs use the active version.
* **Draft:** your work in progress. Changes you make collect in the draft until you publish it.
While you work on a draft, the runs Kaiya makes in the conversation are previews. Every run from **Run**, every trigger and every schedule keeps using the active version until you publish. After you publish, the Mission's existing schedules use the new steps on their next run, so you don't need to create them again.
{% hint style="success" %}
**Edit in a draft, or start a new Mission?** Edit in a draft when you are improving the same job: the change goes live when you publish, and the run history, triggers and schedules stay with the Mission. Start a new Mission, or select **Duplicate** on the Mission's page, when the result answers a different question or serves a different audience and both should keep running.
{% endhint %}
Saved Python steps always run their saved code.
Point to a version in the list and select its three-dot menu for these options:
* **Rename:** give the version a name of your own in place of its label, such as a name that says what changed.
* **Revert to this version:** go back to this version.
* **Delete:** remove this version from the list.
When you switch to a published version, the conversation confirms the switch. If it is the active version, Kaiya also reminds you that your next message creates a draft, so the published version stays as it is.
You choose which version is active. When a version becomes active, Kaiya confirms it, for example *"V1 is now the active version. Manual runs and scheduled runs will use these steps for execution."* Because earlier versions are kept, you can see how a Mission changed over time, and which version produced a given briefing.
{% hint style="warning" %}
A published Mission with no schedule does not run on its own. It runs when someone selects **Run** or asks Kaiya to run it. Add a schedule to have it run automatically.
{% endhint %}
### **Step 5: Run/Schedule the Mission**
You can run a Mission in several ways:
* **From the conversation.** Ask Kaiya, for example *"Run the mission with territory: Kansas City North, MO."* Kaiya confirms that the run has started and shows **Working…** with live progress. Expand the **Steps** panel to follow each step as it finishes.
* **By name.** Ask Kaiya for the Mission by its name.
* **With the Run button.** Select **Run** on the Mission page, or **Run** in a published Mission's card menu in the Mission Library. **Run** opens a new conversation with the Mission details and runs the published Mission straight away. The Mission page shows runs made from Kaiya chat as well as scheduled and manual runs.
* **On a schedule.** The Mission runs at the times set on the **Schedule** tab.
When a Mission has input steps, Kaiya asks you for each value when it runs from the conversation. It offers the step's default as the first option. Selecting **Run** also asks for these values. Scheduled runs use the value saved with the schedule, or the default.
When the run finishes, Kaiya posts the result in the conversation. Files the run created, such as a PowerPoint deck, appear as file cards. Select the arrow on a card to open the file, or the download icon to save it.
### **Debug the Mission from the conversation**
The Debug Assistant helps you work out why the Mission you are building behaves the way it does. Ask a debug question directly in the Mission conversation. There is no separate mode to open.
* Replies in debug mode are not saved to your Mission and do not affect the planner, so you can examine a draft without changing it.
* The Debug Assistant opens with starting questions for the checks most often needed: whether the output is correct and which step is responsible, why a run is slow, whether the figures can be relied on, and how Kaiya approached the analysis. You can also ask your own question about the draft.
* Ask a question about a finished run to see the working behind the reply. Kaiya lists the steps that ran, the query behind each one and what it returned, so you can trace an unexpected result to the step responsible.
### **Working in the Mission conversation**
The conversation is where you talk to Kaiya about the Mission. A few elements help you follow the work.
* **How Kaiya got this:** a collapsible panel on each of Kaiya's replies (named **Thought Process** in earlier releases). It shows the steps Kaiya took and how long they took. Select the arrow to expand or collapse it, and use the **Detailed view** switch for more detail.
* **Based on:** a line under an answer that names the Business View the answer used, for example **Based on bv\_SaaS\_Subscription**.
* **Citation numbers:** small numbers beside figures in an answer. They link each figure to the step that produced it.
* **ACTIONS:** next steps Kaiya offers after a reply, such as **Run the Territory Performance Scorecard now**, **Change it to run on Fridays instead of Mondays**, **Add a PDF export of the weekly brief** or **Build an Insight App from this scorecard**. Some actions say where they lead, such as **Opens the export panel** or **Opens the App builder**.
* **FOLLOW-UP QUESTIONS:** questions Kaiya suggests after a run, such as *"Publish this version so scheduled and triggered runs use these steps."*
* **Show 2 more / Show fewer:** expand or shorten a list of actions or follow-up questions. The number shows how many more are hidden.
* **Message time and copy:** hover over a message to see when it was sent. Use the copy icon to copy a message or one of Kaiya's answers.
* **Response stopped:** shown when a reply was stopped before it finished. Send your next message to carry on.
#### **The message box**
The message box at the bottom of the Mission conversation holds these controls:
* **Upload File:** add a file to the conversation, such as a .pptx file whose format the exports in this conversation should follow, or a document that lists your requirements.
* **Connected apps:** the systems Kaiya can read from and write to in this Mission. See [Using connected systems in Kaiya](https://help.tellius.com/kaiya/tellius-mcp-server/using-connected-systems-in-kaiya).
* **Connect data:** add a data connection from the conversation.
* **Business View selector:** choose the Business View the Mission uses. The Business Views you have selected appear at the top of the list.
* **Dictate (microphone icon):** speak your message instead of typing it.
* **Send (arrow):** sends your message.
#### **The conversation rail**
A rail of short lines runs down the right edge of the conversation. Each line stands for a request or a reply. Hover over a line to see that message, and select the line to jump straight to that part of the conversation. In a long conversation, this is the quickest way to get back to an earlier answer.
When you scroll up, a **Jump to latest** button appears. Select it to return to the newest message.
### **The toolbar on the far right**
A narrow toolbar runs down the right edge of the screen. Each icon opens a panel:
* **Previous Chats (clock icon):** your earlier conversations.
* **Business Views:** the columns of the Business View in use, grouped by dataset. Use **Search Columns** to find a column, and the filter icon to narrow the list. Each column shows its type, such as text or number. Select the back arrow to leave the column list.
* **Artifacts (stacked layers icon):** what this conversation has produced, grouped by kind, such as **MISSIONS** and **FILES**, with a count for each. Files include PowerPoint decks, PDF reports and visual summaries. Select the open icon beside a Mission to open it, or the download icon beside a file to save it.
* **Share:** share the conversation with other people. See [Find and share conversations](https://help.tellius.com/kaiya/kaiya-conversational-ai#find-and-share-conversations).
In releases before Tellius 6.4, the toolbar also had a **Processing Queue** icon.
### **On Tellius Mobile**
You can also start a Mission from Tellius Mobile. In the ask box, choose **Build a mission**, or select the plus icon at the top of the **Missions** tab, then describe what to check and how often. Kaiya builds the Mission in a conversation, the same way as on the web. On a Mission you own, select **Edit with Kaiya** to keep working on it in its conversation. The build options appear only when your role has full access to Missions and can ask Kaiya. See [Tellius Mobile](https://help.tellius.com/getting-started/tellius-mobile).
### **Best practices**
* **Start from an analysis you trust.** Run the questions in a conversation first. When the answers are right, ask Kaiya to turn them into a Mission.
* **Leave values open on purpose.** Say "for whichever region I pick" instead of naming one region. Kaiya adds an input step, and one Mission serves every region.
* **Check before you schedule.** Look at the **Preview** tab, and ask Kaiya to confirm the numbers before the Mission goes live.
* **Use Diagram for complex plans.** It shows which step feeds which, which is the fastest way to understand a branched Mission.
* **Publish on purpose.** Scheduled runs always use the active version, so publish when the draft is ready.
* **Name the versions you may return to.** Use **Rename** in the version menu so a version is easy to find later.
* **Start small or go big.** Begin with one Mission feeding one App, or combine several Missions that each own one part of a larger job. Each Mission saves its output to a table, and the App reads from that table. See [Turn an App into a Mission](https://help.tellius.com/kaiya/kaiya-apps/how-to-create-a-kaiya-app/refine-and-publish-a-kaiya-app#turn-an-app-into-a-mission).
* **Put long requirements in a file.** For a large Mission, write your requirements in a document and upload it to the conversation.
* **Bring older Missions up to date.** Replace a text **Summary** step with a **Rich Summary** step, and put the export details in the export step. See [Missions built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-missions/missions-built-before-tellius-6-4).
* **Use custom skills for house rules.** A custom skill can set the checks a Mission makes, its output format and how it is delivered. Kaiya then asks fewer questions each time you build a Mission. See [Kaiya Skills](https://help.tellius.com/kaiya/kaiya-skills).
### **Related pages**
* [Kaiya Missions](/tellius-6.4/kaiya/kaiya-missions.md)
* [Scheduling Missions](/tellius-6.4/kaiya/kaiya-missions/scheduling-missions.md)
* [Missions built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-missions/missions-built-before-tellius-6-4)
* [Triggering Missions](/tellius-6.4/kaiya/kaiya-missions/triggering-a-kaiya-mission.md)
* [Kaiya Skills](https://help.tellius.com/kaiya/kaiya-skills)
* [Slack Integration](https://help.tellius.com/settings/administration/slack-integration)
* [Teams Integration](https://help.tellius.com/settings/administration/teams-integration)
---
# 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-missions/how-to-create-a-kaiya-mission.md?ask=&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.
