Skip to main content
The Templates library holds configurations worth reusing across five kinds — messages, SMS agents, voice agents, flows, and follow-up sequences — with one property that makes it valuable: fixing a template fixes every copy made from it.

​
Templates are saved from real work

There’s no blank “new template” form. A template is a snapshot of something you already built — you save it from the builder that made it:

​
Use a template

From the library, Use a template to create real, editable work from it — a new agent or flow, prefilled from the snapshot and linked back to the template. The library shows, for each template, what it’s made of, where it’s used, and (for agents and flows) how its clones perform.

​
Divergence — why the library is worth it

A copy created from a template stays in sync with it until you change the copy; then it’s diverged and stops receiving the template’s edits. So a fix to the template reaches every in-sync clone automatically, and the detail page tells you exactly which copies diverged and need updating by hand. That’s the whole point: fix once, propagate everywhere that hasn’t intentionally changed.

​
Over the API & MCP

Save reusable messages and reference templates through the builders; saved messages are also available via the MCP server.