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

# Save and switch agent versions

> Save a version of your Brilo agent before you change it, publish a new one when it is ready, and switch back in one click when a change makes things worse.

Versions let you change a live agent without gambling. You save what works, edit a draft, publish it when
you are happy, and switch back to the previous version the moment a caller complains. Everything happens
in your agent's **Version** tab.

<Note>
  Versioning is enabled per agent and is not switched on for every account. If you do not see a **Version**
  tab on your agent, it is not available to you yet. Email [support@brilo.ai](mailto:support@brilo.ai) if you
  want it.
</Note>

## Before you start

* An agent that is live, or about to be. Versions matter most once real callers are involved.
* Ten minutes.
* A change you actually want to make. Save a version first, then make it.
* You will be working in your agent's **Version** tab.

## Steps

<Steps>
  <Step title="Open the Version tab">
    Open your agent and go to **Version**. You get a list of every version with its status: **Draft**,
    **Published**, or **Live**.
  </Step>

  <Step title="Create a version from what you have now">
    Create a new version, give it a **Version Name**, and use **Description** to say what is different.
    Write the description for yourself in three months, not for yourself today.

    Use **Copy from** to start from an existing version rather than from scratch, which is what you want
    almost every time.
  </Step>

  <Step title="Edit the draft">
    A draft is a full copy of the agent, so you can change instructions, knowledge, actions, voice, and
    model settings on it without touching the version answering your phone.
  </Step>

  <Step title="Test the draft before you publish">
    Call the draft and run your real scenarios. A version you have not called is a guess. See
    [Test your agent yourself](/go-live/test-your-agent-yourself).
  </Step>

  <Step title="Publish it">
    Publish the version, then make it live. Callers get the new version from that point, and the previous
    one stays in the list ready to switch back to.
  </Step>
</Steps>

## You will know it worked when

Your **Version** tab shows the new version as live, your test call reflects the change, and the version you
were on before is still sitting in the list untouched.

## What a version holds

A version is a complete snapshot of the agent: its instructions, its configuration, its actions, its voice
and language, and its model settings. Switching version switches all of that at once.

Two things are worth knowing:

* **Your knowledge folders live in the workspace, not the version.** Edit a document and every version
  reads the new document. Versions do not give you a frozen copy of your prices.
* **Your phone number does not move.** It stays pointed at the agent, and the agent decides which version
  answers. See [Assign a number to an agent](/phone-numbers/assign-a-number-to-an-agent).

## How to use versions well

* **Save before you touch anything.** The version you want to go back to is the one you did not think to
  save.
* **One change per version.** A version that changes the prompt, the voice, and the model tells you nothing
  when it goes wrong.
* **Name them after the change.** "Shorter answers" beats "v4".
* **Write the description.** In a month you will not remember why you made this one, and version history
  shows you what changed but not why.
* **Keep the last known good version.** Do not tidy it away. It is your rollback.

## Naming that survives contact with reality

| Bad name | Better name                      |
| -------- | -------------------------------- |
| v3       | Shorter answers, concise setting |
| New      | Adds transfer to reception       |
| Test     | Testing higher thinking effort   |
| Final    | Prices updated for January       |

## What else you can do here

* Run two versions side by side on real traffic instead of guessing. See
  [A/B test two versions of your agent](/agents/ab-test-your-agent).
* Compare two versions to see exactly what differs, using version history.
* Rename or delete versions you no longer need, keeping the one you would roll back to.
* Change models safely, since the model is part of the version. See
  [Choose your AI model](/agents/choose-your-ai-model).

## If it did not work

**You cannot publish.** Drafts have to be published before they can go live. If a version shows **Publish
first**, publish it and then set it live.

**You published and callers still hear the old agent.** A call already in progress finishes on the version
it started with. Make a fresh call to check.

**A change you made is not in the version.** Check which version you were editing. It is easy to edit the
live one when you meant to edit the draft, and the tab tells you which is which.

**Your prices did not roll back with the version.** They would not. Knowledge lives in the workspace and is
shared across versions. See [Organise material with folders](/knowledge/organise-with-folders).

**You deleted the version you wanted.** Deleted versions do not come back. Keep your last known good one.

**There is no Version tab.** Versioning is not enabled for that agent. Email
[support@brilo.ai](mailto:support@brilo.ai).

## FAQ

<AccordionGroup>
  <Accordion title="Can I undo a change to my Brilo agent?">
    If you saved a version first, yes: switch back to it and callers get the old behaviour on the next call.
    Without a saved version there is nothing to roll back to, which is why saving one before you edit is the
    habit worth forming.
  </Accordion>

  <Accordion title="What is the difference between a draft, a published version, and a live version?">
    A draft is being worked on and takes no calls. A published version is finished and ready. The live
    version is the one answering your phone. You publish first, then set live.
  </Accordion>

  <Accordion title="Does switching versions change my phone number?">
    No. The number stays pointed at the agent, and the agent decides which version answers. Nothing about
    your numbers changes when you switch.
  </Accordion>

  <Accordion title="Do versions include my knowledge documents?">
    No. Knowledge folders belong to your workspace and are shared by every version, so editing a document
    affects all of them. Only the agent's own configuration is versioned.
  </Accordion>

  <Accordion title="How many versions should I keep?">
    Your live version, your last known good version, and whatever you are currently working on. Delete the
    rest once you are confident, but never delete the one you would roll back to.
  </Accordion>

  <Accordion title="Can I test two versions on real callers at the same time?">
    Yes, by splitting traffic between them. See
    [A/B test two versions of your agent](/agents/ab-test-your-agent).
  </Accordion>

  <Accordion title="Why can I not see the Version tab?">
    Versioning is enabled per agent and is not on for every account. Contact
    [support@brilo.ai](mailto:support@brilo.ai) to have it turned on.
  </Accordion>
</AccordionGroup>

## Related

* [A/B test two versions of your agent](/agents/ab-test-your-agent) to compare on real traffic
* [Choose your AI model](/agents/choose-your-ai-model) for a setting worth versioning
* [Test your agent yourself](/go-live/test-your-agent-yourself) before publishing anything
* [Organise material with folders](/knowledge/organise-with-folders) for what is not versioned
* [Turn your agent on](/go-live/turn-your-agent-on) to take a version live