Skip to main content
The Agents tab is where you manage the people your callers will speak to. Each agent contains the conversation behavior, language, model, voice, transcriber, functions, call settings, post-call fields, webhooks, and published version that live traffic can use. DialNexa Agents list showing language filter, status filter, search, create agent, phone number, call type, status, and row actions. DialNexa Create Agent modal showing Single prompt agent and Conversational flow agent type choices.
Treat an agent like a hire for a very specific job. A booking agent, support intake agent, and payment reminder agent should not be the same person with a different name tag.

What The Agents List Owns

AreaWhat users can do
SearchSearch by agent name and agent id. Some links can also prefill search through the URL.
Language filterFilter agents by the language saved on the current version.
Status filterShow all, active, or inactive agents based on publish and availability state.
FoldersCreate folders, rename folders, delete folders, and move agents between folders.
Agent rowsOpen an agent, inspect version context, and use row actions.
Create agentStart from a blank agent or a template where available.

Row Actions

Test call

Starts a phone test using the latest published version. If no published version exists, publish before testing from the list.

Duplicate

Creates a copy so users can experiment without changing the original agent.

Export

Exports an agent configuration for reuse or backup.

Move

Moves the agent into a folder for use-case, customer, team, or environment organization.

From Draft To Live Traffic

1

Create or import the agent

Choose a blank agent, a template, or an imported configuration.
2

Choose the conversation stack

Set voice, language, LLM model, transcriber, and voice model.
3

Write behavior

Add prompt, welcome behavior, variables, functions, and knowledge references where needed.
4

Connect useful actions

Add custom functions, dashboard integrations, workflow actions, or webhooks only when the call outcome needs them.
5

Set operational controls

Configure speech settings, call settings, post-call analysis, fallback behavior, and webhooks.
6

Publish a version

Published versions are what live routes should use.
7

Assign a route

Attach the version to a phone number, batch call, workflow call node, web call, or test call.

Why A Test Call May Not Start

The list action looks for a published version first. Publish the draft before using row-level test call.
The modal validates country code and expected digit length. Remove formatting and check the selected country.
If the agent prompt or flow expects variables, provide test values so the call does not sound incomplete.
Conversational flow transfer destinations can require valid dynamic values before the test call starts.
KYC, wallet, or outbound readiness can block some outbound behavior. Follow the readiness prompt in the dashboard.

What Not To Change From The List

The Agents list is for navigation and operations. Change detailed behavior inside the agent builder.
NeedOpen this page
Prompt, welcome message, or model behavior.Agent builder.
Voice, language, transcriber, or voice model.Agent builder top selectors.
Speech timing, Audio Cache, or Hinglish Map.Agent Settings, Speech Settings.
Silence timeout, duration, voicemail, keypad, or transfer behavior.Agent Settings, Call Settings.
Extraction fields.Agent Settings, Post-call Analysis.

Languages Voices Models And Transcribers

Choose the conversation stack.

Single Prompt Agents

Use one prompt for one clear objective.

Conversational Flow Agents

Use explicit branching for scripted calls.

Testing Agents

Place safe test calls.

Dashboard Integrations

Connect agent outcomes to WhatsApp, email, workflows, and external systems.