> ## 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.

# Use cases

> Prompt examples for working with Famulor through an MCP client

Once a client is connected (see [Connect an AI client](/mcp/overview)), plain language reaches every tool it's approved for. These examples are grouped by [tool group](/mcp/tools-and-scopes) so you can see what's possible with the groups you've connected.

## Assistants

* "Create an after-hours support assistant and run a test conversation against it before I go live."
* "Review my sales assistant's prompt and settings, and tell me what's weak."
* "Clone my support assistant, translate it to French, and set it to the same voice family."
* "List every assistant that doesn't have a knowledge base attached."

## Calls

* "Show me last week's calls that didn't succeed, with the transcript for each."
* "Look at my last call and tell me what went wrong."
* "Study my last 30 calls, spot patterns, and suggest prompt changes to improve the next batch."

## Campaigns, audience, and leads

* "Start the Q3 renewal campaign and tell me how many contacts are queued."
* "Add these 50 leads to the outbound campaign and start it."
* "Show me every lead marked do-not-call in the last 30 days, with the reason."

## Knowledge bases

* "Add our refund-policy page as a knowledge source and tell me how many pages it indexed."
* "Which knowledge base hasn't refreshed in over a week?"

## Messaging, WhatsApp, and SMS

* "Draft a WhatsApp template asking a customer to confirm their appointment."
* "Show me every conversation where the AI was paused for a human handoff today."

## Telephony and Famulor Loop

* "List every phone number that isn't assigned to an assistant."
* "Show me the current queue depth and presence status for the support ring group."

## Automations and Milian Missions

* "Build an automation that texts a follow-up 30 minutes after a missed call."
* "Show me the last 10 runs of the lead-enrichment automation, and which ones failed."
* "Set up a Mission that emails me a weekly summary of campaign performance every Monday at 9am."

## Guided setup with the Famulor Skill

If you've installed the [Famulor Skill](/mcp/overview#connect-from-inside-famulor) in a coding agent, you can ask for a fully guided build instead of specifying every step yourself:

* "Set up a new assistant for my dental practice — walk me through it."
* "Help me connect my Google Calendar and configure booking for a consulting call."

## General best practices

<Tip>
  A well-behaved client reads current state before changing it, and asks you to confirm anything hard to reverse — an outbound call, a message send, a campaign start, a purchase.
</Tip>

| Practice                                       | Why it matters                                                             |
| ---------------------------------------------- | -------------------------------------------------------------------------- |
| Use E.164 phone numbers (`+14155551234`)       | Avoids ambiguous or rejected numbers across countries                      |
| Review a generated system prompt before saving | The client drafts it; you decide what actually ships                       |
| Confirm anything hard to reverse               | Outbound calls, sends, campaign starts, and purchases should ask first     |
| Keep one workflow per prompt                   | A multi-step request stays easy to follow and easy to undo                 |
| Read before you write                          | Check current state so changes build on what's actually there, not a guess |