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

# Agents

> Your AI workforce — specialized agents you recruit, brief, and configure to work on your business.

An **agent** is a specialized AI worker. Instead of one general assistant, Erdo
gives you a team you assemble from a gallery and brief in plain language. You tell
an agent the outcome you want; it connects to your data, does the work, and
reports back — asking before anything consequential.

## Recruit an agent

Open **Agents** to browse the gallery, organized by area (marketing, sales,
e-commerce, personal assistant, and more). Each agent describes what it's good at
and which connections it needs.

<Steps>
  <Step title="Pick an agent">
    Find one that matches the job — a data analyst, a document analyzer, a
    security checker.
  </Step>

  <Step title="Recruit it">
    Recruiting enables the agent for your organization. You can bind specific
    [datasets](/data) and [skills](/knowledge) so it starts with the right
    context.
  </Step>

  <Step title="Put it to work">
    Start a [conversation](/concepts#conversations) and brief it. Results appear inline.
  </Step>
</Steps>

## Build a custom agent

When no standard agent fits, create your own. A custom agent takes:

* **Instructions** — what it should do, how to behave, what to prioritize.
* **Reference documents** — files it should always have on hand.
* **Pinned skills** — reusable [skills](/knowledge) it can call.

Custom agents keep a **version history**, so you can change instructions freely
and restore a previous version if a change doesn't work out.

## One agent, many deployments

An agent is the durable worker: its name, instructions, knowledge, skills, and
run history live in one place. A **deployment** is a way for people to reach that
agent. The same agent can work in Erdo, talk on a phone call, or appear on a
website through chat, voice, and video without becoming several disconnected
copies.

Open **Agents → Deployments** to see every website, voice-runtime, and phone
deployment. Website deployments own only channel settings such as greeting,
voice, appearance, allowed origins, usage limits, and meeting scheduling. Edit
the agent to change its name or instructions; every attached deployment picks
those changes up automatically. External website visitors can search only
knowledge your organization has explicitly marked **Public** — an agent's
private memories and internal skills are never exposed just because it is
deployed.

* Choose **Website** to attach an existing agent to an embeddable chat, voice,
  or video surface. See [Website Widget](/voice-widget).
* Choose **Voice or phone** to open a guided chat that casts the voice and can
  assign a dedicated inbound number. See [Voice Calls](/voice).

Deleting a deployment leaves the agent intact. Deleting the agent disables its
attached deployments.

## Configure and teach

Every agent has a **Knowledge** panel where it accumulates what it learns about
your business — useful findings, known limitations, and optimizations — and
reuses them on future runs. See [Knowledge](/knowledge) for how this works across
your workspace.

<Note>
  Some agents need a specific [connection](/data) to do their job — for example, an
  agent that books meetings needs Google Calendar connected. The agent will tell
  you what's missing if a connection is required.
</Note>

## What agents can do

Agents use **tools** to act: query a dataset, run code, search the web, build a
[page](/pages), send an email, or place a [phone call](/voice). They choose the
tools a job needs — you don't wire them up. Anything that changes your data or
reaches outside Erdo goes through [review and approval](/concepts#review-and-approvals).