What belongs in a template
A useful template can combine:- the Agent’s base instructions and workflow
- approved model, voice, language, functions, and apps
- reporting fields and escalation behavior
- onboarding questions for customer-specific values
- integration requirements and defaults
Build and test a template
- Create a new disabled template and give it a clear internal name.
- Configure it with the same Agent editor concepts used for an individual Agent.
- Define only the onboarding fields customers or your team must provide.
- Test the template on a designated Agent or customer organization.
- Verify the resulting prepared and live Agent configurations.
- Run representative channel and integration tests.
- Enable the template only after the complete onboarding path passes.
Control onboarding visibility
An enabled template can be available for customer creation. Its onboarding visibility determines whether it appears as a selectable option in supported flows. Keep experimental or internal templates hidden until they are ready for customer use.Update a template carefully
A template revision does not make every existing customer identical. Before migrating changes:- identify which sections should change
- preserve approved customer overrides
- run a dry run when using the API migration workflow
- review the affected Agents
- test representative customers after migration
Managing templates programmatically? See
Reseller Agent templates.