Skip to content

Creating agents

Build the first agent

Start with one narrow job. A callback assistant that answers a number, collects details, and closes cleanly is easier to test than a broad assistant that tries to do everything.

The first version should be simple enough to route, call, and improve safely.

Create your first agent with one narrow job. For most teams, that should be the Nuvoca Callback Assistant: answer a phone number, collect the callback details, and end the call cleanly.

Do not start by modeling every use case. A single reliable voice flow is easier to test, easier to route, and much easier to improve.

What to create first

For the first production-like setup, use:

  • Single Agent
  • Voice
  • one primary language
  • one professional voice
  • one clear callback outcome

If the wizard offers more advanced orchestration or multiple agent paths, skip that for now. The right first milestone is a stable callback assistant, not a complex automation graph.

The fields that matter on day one

When you create the assistant, focus on the fields that change caller behavior:

  • Title: the internal label your team sees in the workspace
  • Agent Name: the spoken identity callers hear during the call
  • Persona: one short sentence describing the assistant's role
  • Morning / Afternoon / Evening greeting: a short opening for each time window
  • Recognition language: one primary language only
  • Voice: one clear, professional voice

Everything else can wait until the first call works.

Use values like these as your first version:

  • Title: Callback Assistant V1
  • Agent Name: Ava
  • Persona: You are a friendly, professional callback assistant for our company.
  • Morning greeting: Thanks for calling Acme. This is Ava, the Nuvoca callback assistant. I can collect your details and arrange a callback from the team.
  • Afternoon greeting: same structure, adjusted for the time of day if needed
  • Evening greeting: same structure, adjusted for the time of day if needed
  • Recognition language: the main language your callers actually use

If the UI exposes an interruption setting for the greeting, enable Do not allow interruption for the first pass so callers hear the introduction fully once.

What a first agent should actually do

The callback assistant should be able to do five things reliably:

  1. Greet the caller professionally.
  2. Ask for the caller name.
  3. Ask for the company name.
  4. Ask for the reason for the call.
  5. Confirm the callback number and close the conversation politely.

That is enough for a real first rollout. Tools, knowledge base content, and advanced tuning come after that flow is stable.

Common mistake

The most common setup mistake is adding too much too early. Teams often start changing prompts, tools, and voice settings before the basic callback conversation is even working.

Keep the first version narrow. If the assistant cannot collect the four callback facts in a clean test call, stay in the core setup flow until that works.

Read this next

  • Go to Agent Options to configure the prompt, memory, and model settings that make the callback flow work
  • Go to Voice Configuration to tune speech recognition, greetings, and voice behavior
  • Go to Common Issues if the first call feels stateless, repetitive, or incomplete