Templates
A template is a complete, publishable flow you copy instead of starting from an empty canvas: agents with written prompts, transitions between them, an End Call on the right agents, and a working provider set. Copying one is the fastest way to see what a well-structured flow looks like, and most production flows start as a template with the prompts rewritten for the business.
The templates
All five ship with the same baseline providers — Deepgram nova-3-general, OpenAI gpt-4o-mini, ElevenLabs eleven_flash_v2_5 — so they’re comparable, and so the first thing you change is the prompts, not the plumbing. You choose the voice when you create the flow.
The outbound templates lean on {{contact.*}} variables — the contact’s name, the appointment, the invoice — so they only make sense on calls with a contact attached: campaigns, schedules, or POST /calls with a contactId. Write prompts explains the variables.
Using one
Create a flow from the template
Flow Builder → Create Flow, pick the template (or Blank Flow), name it. The template is copied into a new draft — nodes, transitions, prompts, providers. Nothing links back; it’s yours.
From the API: POST /flows/from-template/{templateSlug} with the slug from GET /flow-templates (appointment-reminder, customer-support, customer-survey, lead-qualification, payment-reminder).
Rewrite the System Prompt
It carries a placeholder persona. Put your business, tone and hard limits in.
Walk each agent's prompt
Keep the structure — goal, what to collect, when to move on, when to end — and replace the specifics.
Add your functions
The templates capture information in conversation; to act on it (check a calendar, create a ticket), attach an HTTP Request.