Build an agent in the builder
Creating an agent opens a persistent conversation with the builder. Tell it who the agent serves, what it should know, and where it will talk to people. The builder asks for the decisions it cannot infer, writes the configuration, and keeps the conversation for later changes.
Describe the job
Start with the audience, the outcome you want, and the limits that matter.
Answer the gaps
The builder asks only for information it cannot safely infer, such as the opening message or the channel you plan to use.
Review what changed
Configuration changes appear alongside the conversation. Test the agent in Preview before you connect a live channel.
The builder is itself a Duvi agent, built with the same prompts, tools and page context available to you. The conversation stays attached to the agent, so returning to it later continues the same thread.
What the builder can change
The builder writes these parts of an agent:
| Area | Fields |
|---|---|
| Identity | Name, system prompt and first message |
| Conversation | Chat mode, model, voice and transcriber |
| Knowledge | Website addresses |
| Access | Allowed domains |
Agent sections
The agent sections give you exact control over the same agent the builder creates: Configure, Appearance, Knowledge, Tools, Integrations, Preview, Channels, Security, Analytics, Insights, Conversations, Leads and Builder. Changes there update the same agent, so there is no second copy to keep in sync and no import step.
Files, custom tools, customer identity, widget appearance, channel setup and the disclaimer are edited in those sections. Appearance is where you set the launcher, color, logo, label and starter prompts. Integrations is where you connect services Duvi already supports. Tools is where you define your own HTTP actions and MCP servers.