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

# Manage your agent

> Manage and edit your AI voice agent by chat. Edit instructions, add tools and knowledge, change the voice, run test calls and pull analytics, all in plain language from Studio.

Once your agent exists, you keep working on it the same way you built it: you tell Alex what you want, Alex proposes the change, and you approve it. There are no forms to hunt through and no settings to memorize. Studio is your agent's home, and the chat is the control surface.

<Info>
  New to Studio? Start with the [Studio overview](/studio/overview), or follow [Create your first agent](/studio/create-agent) if you do not have an agent yet.
</Info>

## The quick actions

Most day-to-day work is one sentence. Type it (or dictate it with the microphone), and Alex shows you a review card before anything changes.

| You ask Alex to...                                 | What Alex does                                                    |
| -------------------------------------------------- | ----------------------------------------------------------------- |
| "Add a line that we're closed on public holidays." | Proposes an edit to the agent's instructions on a review card.    |
| "Turn on appointment booking."                     | Proposes switching a built-in tool on.                            |
| "Connect my calendar."                             | Walks you through linking the app, then confirms it is connected. |
| "Add our refund policy to what the agent knows."   | Adds the text to the agent's knowledge base after you approve.    |
| "Use a warmer, slower voice."                      | Proposes a voice change you can preview and accept.               |
| "Call my phone so I can hear it."                  | Starts an outbound test call to your number.                      |

<Tip>
  The composer has shortcut buttons for the two you will use most. **Talk to your agent** starts a live test call right in your browser, and **Call my phone** places an outbound test call. Both let you hear a change the moment you approve it.
</Tip>

## Alex reviews, never acts silently

This is the rule that makes Studio safe to work in quickly: Alex proposes, you approve. Every change Alex is about to make appears on a review card first, in plain language, so you always see what will happen before it happens. Nothing is edited behind your back.

<Steps>
  <Step title="You ask">
    Describe what you want in the chat. You do not need to know the exact field or setting.
  </Step>

  <Step title="Alex explains and proposes">
    Alex restates what it understood and shows a review card with the exact change.
  </Step>

  <Step title="You approve">
    Approve the card to apply the change, or refine your request and try again. Nothing changes until you approve.
  </Step>
</Steps>

<Note>
  Destructive actions ask for more than a click. To delete an agent, you type **confirm** to go ahead. This is deliberate friction, so nothing important disappears by accident.
</Note>

## Your agent's North Star

Every agent has one objective it always keeps in view. This is its North Star: the single thing the agent is there to do, such as "book qualified demos" or "answer support questions and hand off anything it cannot resolve."

The North Star is the lens Alex checks new instructions against. When you ask to edit the instructions, Alex weighs the change against the objective, so later tweaks refine the agent without quietly pulling it off mission. You can restate the North Star at any time by telling Alex the agent's goal has changed, and it becomes the new lens for everything after.

## The full menu of what you can ask

Anything you can do to an agent, you can ask for in plain language. Here is the fuller set, grouped by what you are trying to get done.

<AccordionGroup>
  <Accordion title="Build and edit">
    | You ask Alex to...                                | Result                                        |
    | ------------------------------------------------- | --------------------------------------------- |
    | "Rewrite the greeting to mention our free trial." | Proposes an instructions edit.                |
    | "Make it shorter and less formal."                | Proposes a tone and length edit.              |
    | "Rename this agent to Front Desk."                | Proposes a name change.                       |
    | "Change the voice to something calmer."           | Proposes a voice change you can preview.      |
    | "Add our opening hours to what it knows."         | Adds to the knowledge base.                   |
    | "Upload this PDF as reference material."          | Adds the file to knowledge after you approve. |

    Instructions and knowledge are how you shape what the agent says and knows. Both go through a review card, and instruction edits are always weighed against the North Star.
  </Accordion>

  <Accordion title="Tools and connectors">
    | You ask Alex to...                             | Result                              |
    | ---------------------------------------------- | ----------------------------------- |
    | "Turn on call transfer."                       | Proposes enabling a built-in tool.  |
    | "Switch off voicemail detection."              | Proposes turning a tool off.        |
    | "Connect my calendar so it can book meetings." | Guides you through linking the app. |
    | "Connect my email."                            | Guides you through linking the app. |

    Tools are the built-in abilities you switch on or off. Connectors link the agent to your apps, such as your calendar and email, so it can act on your behalf during a call.
  </Accordion>

  <Accordion title="Campaigns and automations">
    | You ask Alex to...                          | Result                           |
    | ------------------------------------------- | -------------------------------- |
    | "Start calling this list of leads."         | Proposes an outbound campaign.   |
    | "Follow up with anyone who did not answer." | Proposes a follow-up automation. |
    | "Send a text after every booked call."      | Proposes a follow-up step.       |

    Campaigns put the agent to work outbound, and automations handle the follow-up. As with everything else, you see the plan on a review card before it runs.
  </Accordion>

  <Accordion title="Testing">
    | You ask Alex to...                | Result                                       |
    | --------------------------------- | -------------------------------------------- |
    | "Let me talk to it now."          | Starts a live test call in your browser.     |
    | "Call my phone so I can hear it." | Places an outbound test call to your number. |
    | "Test the booking flow."          | Runs a test call so you can try that path.   |

    After a test call you get an automatic summary, a quality score, and recommended next steps, so you know exactly what to tune before going live.
  </Accordion>

  <Accordion title="Analytics">
    | You ask Alex to...                        | Result                           |
    | ----------------------------------------- | -------------------------------- |
    | "Show me today's calls."                  | Pulls up the call logs.          |
    | "How did the agent do this week?"         | Surfaces the relevant analytics. |
    | "Pull the transcript for that last call." | Brings up the call detail.       |

    You can review performance and call history from the chat, in the same place you build and edit.
  </Accordion>

  <Accordion title="Delete">
    | You ask Alex to...   | Result                                           |
    | -------------------- | ------------------------------------------------ |
    | "Delete this agent." | Asks you to type **confirm** before removing it. |

    Deleting is the one action that asks you to type **confirm**. It cannot happen from a single stray click.
  </Accordion>
</AccordionGroup>

## When to open the settings drawer

The chat handles almost everything, and for most people it is all they ever need. When you want to edit fields directly, a settings icon opens a drawer with everything about the agent in one place, organized into sections for power users.

<CardGroup cols={2}>
  <Card title="Profile">
    The agent's name, voice, and phone numbers, edited as fields.
  </Card>

  <Card title="Tools">
    The full list of built-in tools, each toggled on or off directly.
  </Card>

  <Card title="Connectors">
    The apps the agent is linked to, managed in one view.
  </Card>

  <Card title="HTTP Tools">
    Custom tools for teams wiring the agent into their own systems.
  </Card>

  <Card title="Knowledge">
    Everything the agent knows, added, edited, or removed directly.
  </Card>

  <Card title="Widget">
    The settings for embedding the agent on your website.
  </Card>
</CardGroup>

<Note>
  Instructions are not a section in the drawer. You always give the agent its instructions in the chat, so every wording change stays weighed against the North Star.
</Note>

<Info>
  On the free plan you work with a single ongoing chat and shape your agent entirely through it. Paid plans add multiple saved chats, the ability to create more agents, and the in-browser and phone test tools.
</Info>
