> 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.md).
# Kaiya Missions
Create Kaiya Missions to set up analytical steps, trigger them with natural-language phrases, and deliver consistent, governed outputs.
### **What is a Mission?**
A Kaiya Mission is a **named, reusable analytical workflow**. A user authors it once through conversation with Kaiya: describing the analysis they want, refining Kaiya's proposed plan, and publishing it. Once published, the Mission can be run on demand by anyone with access, or set up to run automatically on a recurring schedule. The same analytical methodology applies on every run, regardless of who triggers it or when.
You can also schedule a Mission to run on a recurring cadence instead of waiting for someone to trigger it conversationally. Each scheduled run's briefing goes to the people and places you choose: email, Slack or Microsoft Teams. A Mission can also include export steps, so a run can deliver files such as a PDF report, a PowerPoint deck, a Word document, an Excel workbook or CSV files.
All Missions can be found in the **Mission Library**. Select **Missions** in the left navigation, then use the **Published Missions** and **Draft Missions** tabs.
### **What are the ways to interact with a Mission?**
* **Authoring** is a one-time setup. The author describes the workflow, refines Kaiya's proposed plan, tests it, and publishes. As part of authoring, the author also decides whether the Mission runs only on demand, or runs on a recurring schedule with output delivered automatically to a list of recipients.
* **Running** happens on demand by anyone with access to the published Mission. The runner triggers the Mission, and provides any inputs Kaiya asks for at runtime (region, quarter, segment, etc.), and receives the output.
* **Receiving on a schedule** is a third interaction mode for recipients who don't actively run the Mission themselves. Once an author sets up a schedule, each scheduled run's briefing goes to the email recipients, Slack or Microsoft Teams that the schedule names. When the Mission has export steps, a run can also produce files: a PDF report, a PowerPoint deck, a Word document, an Excel workbook or a CSV file. Recipients get a finished result without opening Tellius.
* **Remixing** lets someone a Mission is shared with, whose role can create Missions, make their own editable draft copy with **Remix**. They can then publish the copy, run it and schedule it, while the owner's Mission stays as it is. 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).
{% hint style="info" %}
User-defined Missions let you hard-code the exact analytical steps Kaiya should run (SQL pulls, Python methods, visualizations, and the final summary), instead of letting the planner assemble them on the fly. You describe the steps in natural language, optionally add required parameters, and map a trigger phrase to the Mission (for example, "*quarterly payer deep dive*").\
\
When a user's question contains that trigger, Kaiya executes your governed sequence in that order, applies your defaults, and asks only for missing inputs.
{% endhint %}
### **How to build a Mission?**
In Tellius 6.4, you build a Mission by describing it to Kaiya in a conversation. Kaiya drafts the steps, asks clarifying questions when it needs to, and refines the plan with you in the same thread. The Mission sits beside the conversation across four tabs: **Steps**, **Preview**, **Triggers** and **Schedule**. You can also change the name, description, triggers and schedule by asking Kaiya. See [How to create a Kaiya Mission](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission).
New Missions end with a **Rich Summary** step by default. It builds a visual summary page, and the run's reply in the conversation gives a short summary with a card that opens the full page.
### **Missions built before Tellius 6.4**
Missions built in a Kaiya conversation before Tellius 6.4 keep working without being rebuilt. Their steps, run history and schedules carry over. To change one, open it and select **Configure**. The Mission opens in the Unified Chat with its earlier conversation, and your changes go into a draft while the published version keeps running. See [Missions built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-missions/missions-built-before-tellius-6-4).
{% hint style="success" %}
**Worth doing for older Missions:** replace the text **Summary** step with a **Rich Summary** step, so readers get a visual page instead of a long text briefing. If the Mission produces a file, write the file's storyline, contents and design in its export step, so every run produces the same file.
{% endhint %}
{% hint style="info" %}
The form-based Classic Editor is retired in 6.4. Missions built in it remain in place and keep running on their schedule. Opening one shows its name, description, Business View, triggers and steps as read-only reference. These Missions are hidden from the Mission Library by default. Use the **Type** filter and choose **Classic** to show them.
{% endhint %}
### **How to schedule Missions?**
While building the Mission, the author chooses whether the Mission runs only on demand or on a recurring cadence.
* **In the Mission conversation:** open the **Schedule** tab, set the start date, start time and frequency, choose where each briefing goes, and select **Create Schedule**. You can also ask Kaiya, for example *"Schedule it to run every Monday at 8 AM."*
* **From a Mission's page:** open the three-dot menu and select **Create Schedule**. **Scheduled Missions** opens, filtered to that Mission, with the schedules it already has. Select **Schedule** to add one.
* **From the Mission Library:** select **View Schedules**, then **Schedule**, and pick the Mission in the form.
See [Schedule tab](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/the-mission-pane#schedule-tab) and [Scheduled Missions](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page#scheduled-missions).
{% hint style="info" %}
A Mission can have more than one schedule, but each schedule runs one Mission. To run several Missions on the same cadence, create a schedule for each Mission.
{% endhint %}
### **Two ways to consume a Mission**
* When a Mission runs on demand, the result appears as a briefing on the Mission's page. The briefing shows how Kaiya got the result, the Mission steps that ran, a short summary and, when the Mission has a **Rich Summary** step, the visual summary page. The runner scrolls the narrative, drills into citations on any numeric result, and selects **Continue this conversation in Kaiya** to ask follow-up questions without restarting the Mission. Briefings appear for manual runs as well as scheduled ones.
* When a Mission is assigned a schedule, it runs automatically on every scheduled run, and the briefing goes to the configured email recipients, Slack or Microsoft Teams. Files from the Mission's export steps go with it. The same Mission can drive both modes simultaneously: interactive runs for analysts who want to investigate, and scheduled deliveries for executives who want the finished briefing.
{% hint style="info" %}
A Mission's files come from its export steps. Export steps produce PowerPoint, PDF, Word, Excel or CSV files, and a Mission can include several of them, so one run can deliver a PDF report together with several CSV files.
{% endhint %}
### **Where Missions live in Tellius**
Missions are organized in the **Mission Library**, accessed via **Missions** in the left navigation. The library has two tabs and a schedules page:
* **Published Missions:** Missions that are live and available for users to run. Each card shows the Mission name and description, its latest run, its owner and when it was last updated.
* **Draft Missions:** Missions an author has saved but not yet published.
* **Scheduled Missions:** Select **View Schedules** to open a page listing every Mission schedule, with columns for Mission name, schedule name, frequency, next run, last run, and creator. From here, authors can create new schedules, edit existing ones, and review run cadence across the workspace. 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).
---
# 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.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.
