# Composer

To create a custom Mission, click on the **"Compose"** button at the top right under **Kaiya → Missions**. Fill up the following details to set up the Mission.

### **Basic Information**

Set up the foundational identity of your Mission: its name, icon, and a short description of what it does.

**Mission Name & Icon:** Enter a clear, meaningful name in the **Mission Display Name** field and choose a static icon for the Mission.

**Mission Description:** Briefly explain what this Mission is designed to do.

<figure><img src="/files/wDvZjWSEgi6WGwjQaf8o" alt="" width="563"><figcaption></figcaption></figure>

### **Knowledge Sources**

Select the data source for your Mission. Use the dropdown or search bar to select an existing Business View. This becomes the primary input for all agents in the Mission.

{% hint style="warning" %}
At least one Business View should be selected to save the Mission.
{% endhint %}

<figure><img src="/files/3qUI80G7ORgBPIWDBqY6" alt="" width="563"><figcaption></figcaption></figure>

### **Mission Steps**

Define the logic of your Mission in natural language steps. Each step maps to one or more AI Agents (e.g., Planner, Data Prep, Insights). Links to ready-made example flows are available. Click on any sample analysis to view the Mission steps.

<figure><img src="/files/HZeI9UiedjClVA5tUSEN" alt="" width="563"><figcaption></figcaption></figure>

* Break down your Mission into clear, actionable instructions.
* Define one action per step for modular execution.
* Include context, filters, calculations, or user inputs as needed.

{% hint style="info" %}
You can also click **Rewrite with Kaiya** to have Kaiya draft the steps for you from your Mission description, then edit any step inline to tighten the logic, adjust filters, or add context before saving.
{% endhint %}

### **Triggers**

Define the natural language triggers that you might enter in Kaiya Conversational AI to invoke this Mission. Triggers should accurately reflect the goal of the Mission.

* Each trigger should be a standalone phrase or question on a new line.
* Include variations of phrasing to capture different user intents.

<figure><img src="/files/UwIoQ4XYDPH80lKKZEKd" alt="" width="563"><figcaption></figcaption></figure>

For example, for revenue drop, you can say:

* What's causing the revenue drop?
* Explain the decline in revenue
* Why did our revenue decrease?
* Identify reasons for revenue dip
* Breakdown revenue loss

{% hint style="info" %}
You can enter as many variations as you like. This increases the chances your Mission is selected by Kaiya when users input related queries.
{% endhint %}

### **Schedule**

Choose how you want this Mission to run on a recurring basis. Scheduling lets the Mission execute automatically at a defined cadence and deliver its output to a recipient list by email, without anyone having to trigger it conversationally.

You have two options:

* **Subscribe to existing schedule:** Pick from a list of schedules that have already been created in your workspace. Useful when several Missions should share the same cadence.
* **Create new schedule for Mission:** Set up a fresh schedule just for this Mission.

<figure><img src="/files/OATyiz0NydbMWMa0F4Xs" alt="" width="563"><figcaption></figcaption></figure>

#### **Subscribe to existing schedule**

Clicking this option opens the **Available Mission Schedules** view. Each card shows the schedule name, its recurrence pattern, the next scheduled run date, the delivery method, and the author who created the schedule. Use the arrow controls at the bottom to page through schedules if there are more than fit on one screen. Click a card to subscribe the current Mission to that schedule.

<figure><img src="/files/rhUSVafFBPJFwMzCHquP" alt="" width="375"><figcaption></figcaption></figure>

#### **Create new schedule for Mission**

Clicking this option opens a single-page form titled **"Creating schedule for \[Mission Name]"**. You'll configure three things:

<figure><img src="/files/R9STOu2lgFNVm1HNTcOt" alt="" width="563"><figcaption></figcaption></figure>

**Cadence**

* **Start Date:** the date the first run should happen.
* **Start time:** the time of day the run should happen.
* **Cadence:** how often the Mission should run (for example, Daily).

**Mission instructions (optional)**

Provide any runtime inputs this Mission needs — like a brand name, territory, preferred metric, or time frame. Check your Mission Steps to see what inputs are expected.&#x20;

**Email delivery**

* **Email addresses:** pre-filled with your account email. Add more recipients separated by commas. Use the **Cc, Bcc** dropdown to add carbon-copy and blind carbon-copy recipients.
* **Subject:** pre-filled based on your Mission name and cadence. Edit as needed.
* **Email Message:** pre-filled with a default body. Edit as needed.

Once everything is set, click **Schedule Mission** to activate the schedule.

### **Outputs**

Configure the format in which the Mission delivers its final result. Whatever you set up here is what gets attached to the email on every scheduled run, and what you receive when the Mission is triggered on-demand.

<figure><img src="/files/YYLqgirZfUdFOUOYTFHV" alt="" width="563"><figcaption></figcaption></figure>

* **Output Formats:** pick the export format from the dropdown (PPT or PDF).
* **Report Template:** choose a template for the report layout from the dropdown.
* **Report Storyline:** describe the narrative structure of the report in plain language. This is what guides Kaiya on how to organize the slides — section order, what each slide should cover, and the closing recommendation.

### **Save the Mission**

When you've filled in the configuration, click **Save & Publish** at the top right to move the Mission to the **Published Missions** section of the **Mission Library**. Alternatively, click **Save Draft** to save it under **Draft Missions** and finish later.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tellius.com/tellius-6.3/kaiya/understanding-ai-agents-and-agentic-flows/kaiya-missions/composer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.