Skip to main content

Use Cases & Prompts

The Famulor MCP server and the Famulor Skill let you control the entire platform in plain language. This page shows what that looks like in practice — grouped by use case, with copy-paste prompts.
All prompts work in ChatGPT, Claude, Cursor, and any other connected MCP client. Setup: MCP Client.

Creating & optimizing assistants

The most common starting point: create, test, and iterate on voice agents — without opening the platform UI. Prompts:
Best practice: Have the model call get_voices, get_languages, and get_models first instead of guessing IDs — e.g. “Show me the options first, then create…”.

Outbound campaigns & lead management

Set up campaigns, import leads, and control them — at scale. Prompts:
Best practice: Always pass phone numbers in E.164 format (+49170…). Lead variables must match the variables defined on the assistant — you can’t invent new variable names per lead.

Call analysis & reporting

Query and analyze call data — the model filters, aggregates, and summarizes. Prompts:
Best practice: Combine analysis and action in one prompt: “Analyze this week’s calls and adjust the system prompt accordingly — show me the change before saving.”

Knowledge bases (RAG)

Connect knowledge so assistants answer from facts. Prompts:
Best practice: Use function_call mode (default) for on-demand facts, prompt mode when the bot needs content permanently (menus, delivery services). For multimodal/dualplex assistants, function_call is required.

Conversations, WhatsApp & SMS

Run chat channels — including human takeover. Prompts:
Best practice: Before freeform WhatsApp, have the model check whether the 24h session window is open (get_whatsapp_session_status) — outside the window only templates are deliverable.

Phone numbers & SIP

Search, purchase, and manage numbers. Prompts:
Best practice: Number purchases cost money and release_phone_number is irreversible — ask for a confirmation step before both.

Folders & organization

Folders and labels keep agencies and teams organized — especially with many assistants. Prompts:
Best practice: An assistant lives in exactly one folder but can carry multiple labels — use folders for clients/projects, labels for status or environment.

Mid-call tools & automation

Custom HTTP integrations the assistant calls live during a conversation. Prompts:
Best practice: Write tool descriptions from the bot’s perspective (“Call this tool when the customer asks about…”) — they control when the LLM uses the tool.

Guided onboarding with the Famulor Skill

The Famulor Skill complements the MCP server with industry knowledge and a structured 4-phase flow — ideal when a complete assistant needs to be built for a new client. Runs in Cursor, Claude Code, Codex, OpenCode, and Gemini CLI. Prompts:
Best practice: Let the skill drive the flow — it asks phase by phase (discovery → tech → industry → system prompt) and proposes the right defaults per niche (voice, ambient sound, guardrails). Always have the system prompt confirmed before deployment.

End-to-end workflows

The real strength: multiple steps in a single request.

General best practices

Resources