> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa Agent Templates

> Understand DialNexa agent templates, when to start from a template, what to review after template creation, and why templates still need testing.

DialNexa agent templates help users create agents faster by starting from a prebuilt configuration. A template can speed up setup, but users still need to review the prompt, voice, model, transcriber, variables, settings, phone routing, and post-call fields before publishing.

<img src="https://mintcdn.com/dialnexa/O6bVvssz6DpTKOa0/images/documentation/screenshots/create-agent-setup-step.jpg?fit=max&auto=format&n=O6bVvssz6DpTKOa0&q=85&s=d52eaa354118ff1855a48e464bad89a4" alt="DialNexa Create Agent modal showing industry filters and template counts for agent templates." style={{ width: '100%', maxWidth: '1100px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="1710" height="985" data-path="images/documentation/screenshots/create-agent-setup-step.jpg" />

<img src="https://mintcdn.com/dialnexa/O6bVvssz6DpTKOa0/images/documentation/screenshots/create-agent-template-step.jpg?fit=max&auto=format&n=O6bVvssz6DpTKOa0&q=85&s=8f138daba9152839e7b38e46551ee12d" alt="DialNexa Create Agent modal showing Start from blank and available agent template cards." style={{ width: '100%', maxWidth: '1100px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="1710" height="985" data-path="images/documentation/screenshots/create-agent-template-step.jpg" />

<Note>
  A template is a head start, not a signed contract with reality.
</Note>

## Before You Begin

Choose a template that matches one call objective. Prepare your business name, caller context, required questions, boundaries, and success criteria before applying it.

## What To Review After Using A Template

Templates can carry useful structure, but your use case owns the details.

| Area               | Review question                                                                           |
| ------------------ | ----------------------------------------------------------------------------------------- |
| Prompt             | Does it match your actual product, caller, tone, compliance rules, and success condition? |
| Welcome message    | Does the first sentence sound natural for your caller and language?                       |
| Dynamic variables  | Do all placeholders have call-time values or safe defaults?                               |
| Functions          | Should every tool still be available to this agent?                                       |
| Post-call analysis | Are extracted fields named and described for your reporting needs?                        |
| Phone routing      | Is the correct published version attached to the correct phone number?                    |

## When Templates Help Most

Use templates when structure is more valuable than blank-page freedom.

<CardGroup cols={2}>
  <Card title="Known use cases" icon="sparkles" href="/docs/common-use-cases">
    Lead qualification, reminders, support intake, and surveys often share repeatable structure.
  </Card>

  <Card title="Fast prototyping" icon="rocket" href="/docs/agents/testing-agents">
    Create a draft quickly, then edit it into your real script and settings.
  </Card>

  <Card title="Team consistency" icon="users" href="/docs/agents/prompts-and-welcome-messages">
    Give teams a common starting point for tone, fields, and safety rules.
  </Card>

  <Card title="Training new builders" icon="graduation-cap" href="/docs/agent-settings/overview">
    Show new users what a complete agent setup looks like.
  </Card>
</CardGroup>

## Template To Production

<Steps>
  <Step title="Create from template">
    Pick the closest starting point.
  </Step>

  <Step title="Rename immediately">
    Give the agent a name that identifies the specific use case.
  </Step>

  <Step title="Replace placeholder content">
    Update prompt examples, variables, and field names.
  </Step>

  <Step title="Publish after testing">
    Do not route real traffic until a tested version is published.
  </Step>
</Steps>

## Template Misuse Patterns

<AccordionGroup>
  <Accordion title="Leaving sample variables">
    A caller should never hear generic sample values.
  </Accordion>

  <Accordion title="Keeping unused functions">
    Unused tools increase confusion and may allow actions the agent should not take.
  </Accordion>

  <Accordion title="Not changing post-call fields">
    Exports become hard to use when fields do not match the real outcome.
  </Accordion>
</AccordionGroup>

## Verify The Template-Based Agent

Remove sample values, confirm provider and variable settings, publish a test version, and review one normal and one difficult conversation in Call History.

## Related Reading

<CardGroup cols={2}>
  <Card title="Agents Overview" icon="sparkles" href="/docs/agents/overview">
    Return to the agent list.
  </Card>

  <Card title="Testing Agents" icon="phone-call" href="/docs/agents/testing-agents">
    Test template-based agents.
  </Card>

  <Card title="Prompts" icon="message-square" href="/docs/agents/prompts-and-welcome-messages">
    Rewrite the caller-facing behavior.
  </Card>

  <Card title="Agent Template Video" icon="circle-play" href="/docs/tutorials/platform-videos/create-single-prompt-agent-from-template">
    Watch how to create a single prompt agent from a template.
  </Card>
</CardGroup>