> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Milian Mission examples

> Copy a prompt for call quality, knowledge gaps, campaign progress, automation alerts, or a weekly email report.

Use these prompts to set up recurring checks and reports with Milian. Each example explains what to attach and which actions to allow.

## Set up a mission from an example

1. Open **Milian Missions**, select **New mission**, and replace the prefilled text with a prompt below.
2. Replace each bracketed placeholder. Use `@` in Milian to attach the assistant, campaign, or automations from your workspace.
3. Review the draft in Mission Studio. Set the schedule and time zone under **Trigger** and check the permissions under **Access**. A workspace owner or admin can publish the version.
4. Select **Run now** and review the output under **Runs**. For the email example, use your own address for the first run.

Read-only examples leave their findings in the mission run. Each run uses Milian credits. [Set up and manage Milian Missions](https://docs.famulor.io/assistants/routines.md)

## Improve a booking assistant's prompt

Run daily with **Read** access. Attach the assistant that handles bookings.

![A Milian prompt for booking quality, the daily schedule in Mission Studio, and a run with a suggested prompt change.](https://mintcdn.com/ouraicall/tvSrdxy9k0qnh-OY/images/guide-ui/mission-booking-quality-en.webp?fit=max\&auto=format\&n=tvSrdxy9k0qnh-OY\&q=85\&s=02a9b72dd606c9923dcd138f587a7005)

Example from the Famulor app using sample calls.

```text theme={null}
Set up a daily Milian Mission with Read access.

Review up to 20 completed calls from [assistant] in the last 24 hours.
Find cases where the assistant confirmed an appointment and the booking tool
returned an error or gave no confirmation. Check the transcript and tool
results. Mark missing evidence separately.

Report how many calls you reviewed and link the examples you can verify.
If the issue repeats, suggest a specific change to the current prompt and
describe a simulation scenario with an expected result. If the cause is a
tool error, report it separately. Leave the suggestion in this run.
```

Use the proposed scenario to compare the change with the current prompt in [assistant simulations](https://docs.famulor.io/assistants/simulations.md).

## Find questions your knowledge base should cover

Run weekly with **Read** access. Attach the assistant whose calls you want to review.

```text theme={null}
Set up a weekly Milian Mission with Read access.

Review up to 20 completed calls from [assistant] in the last seven days.
Group recurring questions the assistant couldn't answer with the available
information. Search its linked knowledge base when available.

Separate topics you couldn't find in the knowledge base from topics that
are documented but were missed in the conversation. For each recurring
question, report how many reviewed calls showed it, link examples, and
suggest what the team should document. Flag facts the team needs to verify.
```

## Review campaign progress

Run daily with **Read** access. Attach the outbound campaign.

```text theme={null}
Set up a daily Milian Mission with Read access.

Report the current progress of [campaign]. Include total leads, completed
leads, and the number of calls made. Review up to 20 leads with no answer
and up to 20 failed leads. For each group, report how many of the reviewed
leads already have a next attempt scheduled.

Keep campaign totals separate from the sample. Suggest which group the
team should review first and explain why.
```

## Find failed automation runs

Run hourly with **Read** access. Attach the automations you want to monitor. Under **Access**, you can enable **No-failures check** with a 60-minute window so the mission can finish without generating a report when all checks succeed and find no failures. [Set up the no-failures check](https://docs.famulor.io/assistants/routines.md#skip-empty-automation-alerts)

```text theme={null}
Set up an hourly Milian Mission with Read access.

Check [automations] for failed runs in the last 60 minutes. For each
affected automation, report how many failures you found, when the latest
failed run started, the recorded error, and one next step.

Report any automation you couldn't check separately. Leave the report
in this mission run.
```

## Email a weekly call report

Run weekly with **Read** and **Communicate** access. Attach the assistant and use an address you control. The workspace needs an available email sender.

```text theme={null}
Set up a weekly Milian Mission with Read and Communicate access.

Prepare a seven-day report for [assistant] with its total calls, completed
calls, and calls rated successful or unsuccessful. Show calls without a
success rating separately. If you sample call details, give the sample size.

Send one email to [team email] with the subject "Weekly call report".
Include aggregate counts and one suggested follow-up. Keep names, phone
numbers, and transcript excerpts out of the email. Report any delivery
error in the mission run.
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.