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

# Building your first agent

> Build your first Verbu agent from your website or a short description — then fine-tune its instructions, knowledge, actions, and phone in the editor.

You'll set up an agent that can pick up the phone, answer questions about your business, and follow your instructions. The whole thing takes about ten minutes.

## 1. Build the agent

Create a new agent in the dashboard. Verbu walks you through two steps:

### Tell it about your business

Paste your **website** under **Start with your company website**. Verbu reads through your public pages and automatically pulls in your company name, industry, copy, and logo — and builds a knowledge base from the content. Click **Start setup**.

Don't have a website yet? Click **Skip website** and describe the business instead: what you do, who your customers are, and what the agent should be able to help with.

### Review your agent setup

Under **What will your agent do?** Verbu suggests a draft of the agent's instructions based on what it found. You can also pick a template from the menu:

* **Reception** — answers calls, takes messages, and routes to the right team
* **Sales support** — qualifies leads and answers pricing questions
* **Customer service** — answers customer questions

Edit the text however you like, choose a **Language**, and click **Create agent**. Verbu builds the agent and opens it in the editor — you refine everything else there.

## 2. Find your way around the editor

The agent has a menu on the left. The ones that matter most:

| Section       | What you do here                                                                                                |
| ------------- | --------------------------------------------------------------------------------------------------------------- |
| **AI**        | The agent's instructions and language                                                                           |
| **Knowledge** | Website, FAQs, and documents the agent can draw on                                                              |
| **Actions**   | What the agent can do — take messages, collect leads, send summaries — plus **Integrations** and **Procedures** |
| **Phone**     | Phone number, forwarding, voice, and the first message                                                          |
| **Chatbot**   | Chat on your website                                                                                            |
| **General**   | Name, languages, and deletion                                                                                   |

At the top you'll find **Playground**, where you test the agent, and the conversations list, where calls and chats land.

## 3. Fine-tune the instructions (AI)

Under **AI** you'll find the agent's instructions — what Verbu built in step 1. Read through them and add what makes the agent yours. This is also where you choose the agent's **language**, and you can add more if your callers sometimes switch.

## 4. Add the agent's knowledge (Knowledge)

Under **Knowledge** you add what the agent is allowed to draw on:

* **Your website** — if you started from a website, it's already in. You can add more.
* **FAQ entries** — short question-and-answer pairs for the things callers ask most often
* **Documents** — upload PDFs, price lists, or internal notes

There's a deeper guide in [Agent knowledge and training](/en/agent-behaviour/knowledge-and-training).

## 5. Decide what the agent can do (Actions)

Under **Actions** you switch on capabilities, grouped by when they happen in a call:

<AccordionGroup>
  <Accordion title="Take a message" icon="message-square">
    The agent collects the caller's name and number (and anything else you ask for) and hands the message to you afterwards.
  </Accordion>

  <Accordion title="Collect leads" icon="user-plus">
    The agent asks for contact details when callers show interest in something you sell. You decide which fields are required.
  </Accordion>

  <Accordion title="Conversation summary" icon="mail">
    After each call the agent writes a short summary and sends it to email, Slack, or your CRM. You can route different kinds of calls to different places.
  </Accordion>

  <Accordion title="Custom actions" icon="link">
    Let the agent call your own systems with an API request.
  </Accordion>
</AccordionGroup>

The **Integrations** tab connects your booking system or CRM — see [Integrations](/en/integrations). Switch on only the ones you need today; you can add more later.

## 6. Get the agent on the phone (or your website)

* **Phone** — assign a number. Keep your own (see [PBX & phone setup](/en/pbx)) or get one from us. Forwarding, voice, speed, and the **first message** (what the agent says when a call connects) are set here too.
* **Chatbot** — switch on chat for your website and Verbu gives you a snippet to paste into your site.

Keep the first message short, friendly, and on-brand:

> "Hi, this is Sarah from Acme. How can I help you today?"

## 7. Test it in Playground

Open **Playground** and try a few realistic conversations:

* A typical question your customers ask
* Something the agent shouldn't know — make sure it handles "I don't know" gracefully
* A request to be transferred to a person, if you've set that up

If something sounds off, come back and tweak it. Most teams iterate a few times in the first week.

## 8. Go live

When you're happy with how it sounds, click **Go live**. From that moment, inquiries to your agent's chat and phone number will be answered.

<Tip>
  Most customers use their own phone system to control when the agent answers — e.g. outside opening hours, or when the main line isn't picked up.
</Tip>

## Next steps

* Fine-tune how your agent pronounces tricky words in [Pronunciation](/en/agent-behaviour/pronunciation)
* Add more sources to [Agent knowledge and training](/en/agent-behaviour/knowledge-and-training)
* Connect your booking system in [Integrations](/en/integrations)