# Studio overview (/en/ai/studio)

> For AI agents: see the complete documentation index at [llms.txt](/llms.txt).

Agent Studio is a visual workspace in the Agora Console for building and operating conversational AI voice agents. You configure agent behavior, connect telephony, and monitor production calls from a single interface, without writing integration code.

Studio abstracts the underlying AI stack. You configure your ASR, LLM, and TTS providers; Studio handles the orchestration between them. Instead of managing API integrations across multiple services, you focus on what your agent should say and do.

## How Studio is organized [#how-studio-is-organized]

Studio is structured around three areas that map to the agent lifecycle:

**Build:** Create and configure agents. Start from a use-case template or a blank template, then define the system prompt, greeting, voice, and behavior. Connect credentials, knowledge bases, and MCP servers through the **Integration** interface. Studio stores these resources centrally so they can be reused across multiple agents. See [Customize your agent](build/customize-agent) and [Manage integrations](build/integrations).

**Deploy:** Connect agents to telephony. Assign phone numbers using Elastic SIP Trunk and configure inbound routing or outbound campaigns. Studio supports providers such as Twilio, Exotel, and Telnyx. See [Publish your agent](deploy/deploy-agent), [Phone Numbers](deploy/import), [Handle inbound calls](deploy/inbound), and [Campaigns](deploy/campaign).

**Observe:** Monitor production usage. Review call history, transcripts, and analytics to understand agent performance and debug issues. See [Analytics](observe/analytics) and [Call History](observe/call-history).

## How it works [#how-it-works]

Studio sits between your telephony provider and the AI models that power your agent. For inbound calls, Studio receives the call from your carrier via Elastic SIP Trunk, processes the conversation through your configured ASR, LLM, and TTS providers, and delivers the agent's response back to the caller. For outbound calls, Studio initiates the call through the same SIP trunk, connects to the recipient, and handles the conversation in the same way.

In both cases, Studio manages the full call lifecycle. No SIP servers to manage, no voice recognition to train, no telephony protocols to debug.

## Key concepts [#key-concepts]

### Agents [#agents]

Agents are the primary objects in Studio. You create an agent from a template or from scratch, then configure it across the following areas:

* **Live Audio Input**: Voice Activity Detection (VAD), turn detection, and interruption mode
* **LLM**: The provider and the prompt that defines conversational behavior
* **ASR**: The speech recognition provider and language settings
* **TTS**: The voice synthesis provider and voice parameters

After configuring, test the agent in the built-in playground and activate it when ready.

### Integration [#integration]

The **Integration** section provides a centralized resource library for your Studio workspace. Store API credentials, knowledge bases, and MCP server connections here once, then attach them to any agent. This eliminates repeated setup when you create new agents or update provider settings.

### Phone numbers [#phone-numbers]

Import phone numbers from your SIP trunk provider and assign them to agents for inbound calls or use them as caller IDs for outbound campaigns.

### Campaigns [#campaigns]

For outbound use cases, create campaigns with contact lists and scheduling. See [Set up a campaign](deploy/campaign).

## Who should use Studio [#who-should-use-studio]

Studio is designed for developers and technical users who want to build and operate voice agents without managing the underlying AI infrastructure. If you need capabilities beyond what Studio exposes, such as advanced API parameters or custom orchestration logic, you can use the [Conversational AI REST API](/en/api-reference/api-ref/conversational-ai) for full programmatic control.

## Get started [#get-started]

To get started, follow the [Quickstart](quickstart), which walks you through creating and testing your first agent in about 10 minutes using a pre-built template.