Skip to main content
Open Agents, select the correct project, and choose a saved agent. The console and Agents REST API edit the same profile. Save changes, then start a new test call to check the effective configuration.

Find a setting in the console

Instructions and role

Put identity, business policy, conversation flow, and boundaries in Agent prompt (persona_system_prompt in the REST API). The response’s prompt_limit_characters gives your current character allowance. Knowledge documents belong in Knowledge; keep the prompt focused on how to use them. role selects a starting operating standard. Your instructions remain authoritative for identity and business policy. Choose custom for a workflow outside the built-in roles. Use persona_perspective: "caller" for a simulated caller or training partner; the default "agent" represents the business. Write for me, Improve, and Generate variations produce drafts. Review them before applying and saving. They do not configure the tools needed to perform bookings, transfers, or other business actions.

Voice and language

Select an Omni-compatible voice in the voice picker. The API field is voice_id; inspect configured.voice_id to see the canonical served voice. Set language explicitly for a known language, and check configured.language_active and language_fallback before assuming it is active. The language reference owns the current roster. Voice delivery is under Advanced & compliance. Current Omni routes support neutral delivery only: leave it blank or set voice_instruct to null in the Agents REST API. For a realtime configure reset, send an empty string. A saved custom direction can be rejected when the call configures. Tone and business instructions in the prompt are separate from this voice control. For a custom voice, follow Voice cloning, then select the ready voice in the agent. A voice available for TTS is not automatically available for every realtime language or product.

Conversation behavior and vocabulary

Some controls are available through the API even when the editor has no dedicated field: Vocabulary is sanitized and fixed at session start, including across transport reconnects. Omni does not inherit organization Hear vocabulary and has no inline vocabulary override. Keep terms specific; biasing one name can make unrelated recognition worse. barge_sensitivity, ack_mode, and keyterms are stored compatibility fields that do not change the current Omni runtime. Use vocabulary instead of keyterms. In your media client, interruption handling still requires clearing queued playback on the documented control event; see the browser guide. Turn on Record calls only when your application should retain audio. Set Recording disclosure (consent_line) when enabling recordings_enabled. The spoken order is disclosure, opening greeting, then conversation. Recording defaults to off. Greeting variants never rotate the consent line. See Greetings and recording disclosure for examples and Security and data for retention. Transcript storage must preserve speaker roles.

Saved settings and per-call overrides

To load a saved profile, connect to Omni with session_label equal to its agent_id. A different opaque label does not select that profile. For fields supported by the realtime protocol, inline configure values override saved settings for that session. REST uses persona_system_prompt; realtime uses persona. Do not copy an entire Agent object into configure. Update only the fields you want to change with POST /v1/agents/{id}. Omitted fields stay unchanged; null clears fields that permit it. Read the profile back, then check the new session’s configured acknowledgement. Updates do not rewrite an active call.
Use the Agents API guide for creation and updates, and the Omni protocol for supported session fields. Tools and knowledge bindings have their own dedicated setup guides above.

Test your changes

Save, then open Review & test and start a fresh browser call. Check the opening line, voice, language, knowledge answers, and any setup warnings. Browser calls can test conversation behavior; phone transfers and other carrier actions require the actual phone transport. Check the call-control requirements before enabling those actions. If a setting appears ineffective, check the selected project and agent, saved values, session_label, inline overrides, and the configured response in that order. A stored field is not proof that the current runtime applies it.