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: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:+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:Knowledge bases (RAG)
Connect knowledge so assistants answer from facts. Prompts: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:get_whatsapp_session_status) — outside the window only templates are deliverable.
Phone numbers & SIP
Search, purchase, and manage numbers. Prompts: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:Mid-call tools & automation
Custom HTTP integrations the assistant calls live during a conversation. Prompts: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:End-to-end workflows
The real strength: multiple steps in a single request.General best practices
| Rule | Why |
|---|---|
| Read before write | ”Show me first…” before changes — the model fetches real IDs instead of guessing |
| Confirm destructive actions | Ask for explicit confirmation on delete_*, campaign stops, and number releases |
| E.164 everywhere | Phone numbers always as +49… — other formats fail |
| Preview changes | ”Show me the new system prompt before you save it” |
| One workflow, one prompt | Phrase multi-step jobs as a numbered list — the model works through it in order |
| API key via OAuth only | Never paste the key into configs or prompts — sign-in happens in the browser |
Resources
- MCP Server — all 76 tools at a glance
- MCP Client setup
- Famulor Skill — guided onboarding
- API reference

