Prompt Templates

Whitelabel Admin → Prompt templates is where you build the catalog of starting points your customers see when they create a new assistant. A template is a reusable draft — name, description, picture, system prompt, first message, and classification tags — that a customer can preview and apply as a copy. Open Whitelabel Admin → Prompt templates → New template. Start with Name, Category and Description, then add classification tags. Scroll within the editor to add the prompt and first message before selecting Save. The screenshot shows the initial, unsaved form.

New template — picture, basic details and classification fields

What a template holds

Field	Purpose
Picture	Studio portrait shown in the template catalog; copied onto new assistants that use the template
Name / Category	Shown in the template browser, e.g. “Receptionist” / “Inbound”
Description	Short explanation of what the template is for
Content	The assistant’s system prompt
First message	The assistant’s opening line
Languages	Platform language codes for filtering, including two- and three-letter codes (e.g. `de`, `en`, `gsw`)
Themes	Use-case tags — receptionist, lead qualifier, appointment booker, support, call screener, survey, sales, personal assistant, and more
Branches	Industry tags — general, healthcare, dental, real estate, home services, SaaS/B2B, hospitality, legal, automotive, e-commerce, education
Sort order / Active	Where it appears in the catalog, and whether it’s currently offered

Most templates hold a plain system prompt. A template can also carry a saved flow — when a customer applies one of these, Famulor seeds the assistant’s Flow Builder canvas instead of a plain prompt. The platform catalog offers reception, appointment-request intake, customer support, lead-enquiry qualification and callback-request intake as both flows and single prompts across the available language catalog. Templates introduce the assistant as AI and use Famulor mascot pictures. Replace business variables and add your verified information before use. Appointment requests, messages and tickets are confirmed only when an assigned tool reports success.

Where customers see it

A customer picks a template while creating a new assistant, or later from the system-prompt card on an existing assistant. They preview it, then apply a copy. Later changes to the template never overwrite an existing assistant — applying a template copies its content once; it does not create a live link back to the template.

Scope

Templates you create in Whitelabel Admin are available to your own reseller team and to your customer workspaces. Delete or deactivate a template to remove it from the catalog; existing assistants that already applied it are unaffected.

API, MCP and CLI

The customer-visible catalog is read-only through GET /api/v1/prompt-templates, the MCP list_prompt_templates tool and famulor list-prompt-templates --language gsw. Create an assistant from a catalog item with famulor create-assistant --template-id <template-id>. Creating and editing templates themselves is a Whitelabel Admin dashboard action; there is no write API for template management. See also White Label Program for how visibility and other white-label customizations work together, and Flow builder for how flow-based templates behave once applied. The catalog returns pages of up to 100 templates (50 by default). Use limit and offset with the API or MCP, or famulor list-prompt-templates --limit 100 --offset 100 for the next CLI page.

White Label Program

White Label Platform

White Label Setup