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

# Build and Update Agents

> Create versions, translate agents, and manage publishing with AI FDE

AI FDE can create a new agent or make focused changes to an existing version.

## Create a new agent

Tell AI FDE:

* The purpose of the agent.
* The required language.
* Who the agent will speak to.
* The information it should collect.
* The actions it should perform.
* Any important safety or business rules.

**Example:**

```text theme={null}
Create an outbound English lead qualification agent for a real estate company.
It should ask about location, budget, property type, and purchase timeline.
If the lead is qualified, offer to book a call with a sales executive.
Never promise a price or property availability.
```

A successful build creates the agent and saves its first version.

## Update an existing version

Name the agent and version when using the full-page AI FDE. If you open AI FDE inside the Agent Builder, it already receives the current page context.

**Example:**

```text theme={null}
Update version v3 of the Demo Booking Agent.
Make the greeting shorter, add a response for "call me later",
and keep the remaining flow unchanged.
```

<Tip>
  Say what must stay unchanged. This helps AI FDE make a focused update.
</Tip>

## Translate a version

AI FDE can create another language version and adjust language-related settings.

**Example:**

```text theme={null}
Create a Hindi version from the published English version.
Translate the spoken conversation naturally and use a suitable Hindi voice and transcriber.
Keep the same functions and business rules.
```

You can also request several languages:

```text theme={null}
Create Hindi, Marathi, and Gujarati versions from the English sales agent.
Report the result for each language separately.
```

## Apply one change across languages

Use this when several existing language versions need the same update.

**Example:**

```text theme={null}
Add the new refund-policy rule to the existing English, Hindi, and Tamil versions.
Do not change their language, voice, or current call flow.
```

<Warning>
  Clearly name the target versions. Do not assume every language version should receive the same change.
</Warning>

## Convert the agent mode

AI FDE can help convert an agent between Basic, Advanced, Multi-Prompt, and Pathway structures.

**Example:**

```text theme={null}
Convert version v2 into a Pathway agent.
Keep the same customer journey, functions, variables, and closing behavior.
Show me the proposed node structure before building.
```

Use **Plan** mode for conversions so you can review the new structure first.

## Publish or change status

You can ask AI FDE to publish a specific version or update the agent's lifecycle status.

**Examples:**

```text theme={null}
Publish version v4 for English after confirming the exact agent and version.
```

```text theme={null}
Move this agent from In-Progress to Live.
```

<Warning>
  Publishing can affect customer calls. Always name the exact agent, language, and version, and test it before making it live.
</Warning>

## Example prompt template

```text theme={null}
Task: [create / update / translate / convert / publish]
Agent: [agent name]
Version: [version name, if applicable]
Language: [language]
Goal: [what should change]
Keep unchanged: [important existing behavior]
Rules: [must-follow requirements]
```

## After the work completes

Check the result returned by AI FDE, then:

1. Open the new version.
2. Review the prompt, flow, functions, variables, and settings.
3. Run test calls or simulations.
4. Fix any issue in a new version.
5. Publish only after testing.

## Secrets and external services

AI FDE uses organization secret names such as `x_secrets.CRM_API_KEY`; it does not need the credential value in chat. If a required name is not yet in the registry, AI FDE saves it as a non-blocking pending requirement and reports it after saving the version.

Add every reported name at [**Dashboard → Settings → Secrets**](https://callkaro.ai/dashboard/settings/secrets), or ask your organization admin to update the registry. The affected function or integration will not be ready until its pending secrets are configured. See [Secrets for Agents](/agents/configurations/secrets) for complete instructions.

## Related Voice AI documentation

<CardGroup cols={2}>
  <Card title="Agent Versions" icon="code-branch" href="/agents/understanding-the-agent/agent-versions">
    Understand how independent versions support testing and languages.
  </Card>

  <Card title="Basic Mode" icon="lightbulb" href="/agents/prompts/mode-1-basic">
    Configure the agent in one prompt.
  </Card>

  <Card title="Advanced Mode" icon="sliders" href="/agents/prompts/mode-2-advanced">
    Organize instructions in structured fields.
  </Card>

  <Card title="Multi-Prompt Mode" icon="layer-group" href="/agents/prompts/mode-3-multi-prompt-capability-mode">
    Split a long conversation into capabilities.
  </Card>

  <Card title="Pathway Mode" icon="diagram-project" href="/agents/prompts/mode-4-pathway">
    Build a visual flow with nodes and conditions.
  </Card>

  <Card title="Secrets for Agents" icon="key" href="/agents/configurations/secrets">
    Store and use API keys, tokens, and credentials safely.
  </Card>
</CardGroup>