Templates
Save a call configuration once and reuse it across many calls.
A template is a saved call configuration. Instead of re-specifying the
objective, outcome schema, voice, and language on every
POST /v1/calls, you save them once and reference the template — useful
when you run the same kind of call (appointment confirmations, lead
qualification) over and over.
What a template captures
| Field | Notes |
|---|---|
name | Human label for the template. |
description | Optional note. |
objective | What the AI should accomplish on the call. |
outcome_schema | The structured fields to extract (the same schema you'd pass on POST /v1/calls). |
voice_engine | Defaults to the workspace default (gemini_25). |
language | BCP-47, defaults to en-US. |
The dashboard's New template form edits name, description, objective,
and the outcome schema; voice_engine and language fall back to the
workspace defaults. The API accepts all six fields if you need to pin a
voice or language to a template.
Endpoints
GET /v1/templates— list templates.POST /v1/templates— create a template.GET /v1/templates/{id}— fetch one.DELETE /v1/templates/{id}— remove one.
See the API reference for full schemas.
Creating one
From the dashboard: Templates → New template. You can also start from any past call in the Inspector — its objective and schema pre-fill the form.
The outcome-schema builder offers a visual editor (field name + type +
optional flag) and a raw-JSON view; both produce the same
outcome_schema object the API expects.