Skip to main content

Creating a Voice Agent

Voice Agents have their own area in SimplAI Studio, separate from standard Agents.

Finding Voice Agents in Studio

A dedicated Voice Agents entry appears in the left navigation. Clicking it opens the Voice Agents list page for the current workspace.

The list shows these columns:

  • Name
  • Mode — Sync, Async, or Realtime API
  • Last Modified
  • Runs — total runs across all versions
  • Status

The list table looks and works like the standard Agents list, but it is backed by a separate data model. A voice agent never shows up in the Agents list, and a standard agent never shows up in the Voice Agents list.

Working the list

From the list page you can:

  • Search by name.
  • Filter by execution mode.
  • Duplicate a voice agent to a new draft.
  • Archive a voice agent (hides it from the active list; can be restored).
  • Delete a voice agent (subject to deletion-protection rules if it is published or has dependents).

Creating a new Voice Agent

Click Create Voice Agent in the top-right of the list page. This launches a voice-specific creation flow that takes you directly to the Voice Agent configuration screen.

The configuration screen is organized top-to-bottom in this order — match the order when you build:

  1. Identity — name, description.
  2. Environment Variables — keys, values, masked secrets. Same model as standard agents.
  3. Mode Selection — Sync, Async, or Realtime API.
  4. Model Configuration — LLM, Transcriber (STT), Text-to-Speech (TTS).
  5. Voice Configuration — voice settings: speed, stability, similarity, fallback voices, multilingual.
  6. Knowledge & Tools — knowledge bases and tools (tool selection enforces Sync mode).
  7. Additional Features — voice-compatible features only.

Each section is documented in detail under Configuration.

Versioning, run history, and deployment

Once a voice agent is configured:

  • Save creates a new draft version. Publish when ready. See Versioning for the shared version model — voice agents follow the same draft/publish/diff/restore pattern.
  • Calls land in Run history with transcripts, traces, and audio playback synced to spans.
  • Expose the agent to users via the Deployment tab — JS SDK, embed widget, or telephony.