For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Connect
BlogHelp CenterAPI PricingSign up
OverviewElevenCreativeElevenAgentsElevenAPIReception AIAPI referenceChangelog
OverviewElevenCreativeElevenAgentsElevenAPIReception AIAPI referenceChangelog
  • Get started
    • Overview
    • Quickstart
  • Configure
    • Overview
    • Voice & language
    • Knowledge base
    • Tools
    • Personalization
    • Authentication
  • Deploy
    • Overview
    • Environment variables
    • WhatsApp
    • Batch calls
  • Monitor
    • Overview
    • Users
    • Testing
    • Experiments
    • Versioning
    • Conversation Analysis
    • Analytics
    • Real-time monitoring
    • OpenTelemetry traces
    • Privacy
    • Cost optimization
    • CLI
  • Advanced
    • Events
    • Custom models
    • LLM cascading
    • Post-call webhooks
  • Resources
    • UI components
  • Guides
    • Chat Mode
    • Burst pricing
    • ElevenLabs' docs agent
    • Scaling user interviews
    • Simulate Conversations
LogoLogo
Login
Login
Connect
BlogHelp CenterAPI PricingSign up
On this page
  • Overview
  • Creating Text-Only Agents
  • Runtime Overrides for Text-Only Mode
  • Important Notes
  • Key Requirements
  • Example: Handling Agent Responses
  • Sending Text Messages
  • Concurrency Benefits
  • Use Cases
  • Troubleshooting
  • Agent Not Responding
  • Next Steps
Guides

Chat Mode

Configure your agent for text-only conversations with chat mode

Was this page helpful?
Previous

Burst pricing

Optimize call capacity with burst concurrency to handle traffic spikes.
Next
Built with

Chat mode allows your agents to act as chat agents, ie to have text-only conversations without audio input/output. This is useful for building chat interfaces, testing agents, or when audio is not required.

Overview

There are two main ways to enable chat mode:

  1. Agent Configuration: Configure your agent for text-only mode when creating it via the API
  2. Runtime Overrides: Use SDK overrides to enforce text-only conversations programmatically

This guide covers both approaches and how to implement chat mode across different SDKs.

Creating Text-Only Agents

Configure an agent for text-only mode to make it the default for every conversation with that agent.

Update via the dashboard
Update via the CLI
Update via the API

Open your agent in the dashboard, navigate to the Advanced tab, and enable the Text only toggle. Save your changes.

For complete API reference and all available configuration options, see the text only field in Create Agent API documentation.

Runtime Overrides for Text-Only Mode

To enable chat mode at runtime using overrides (rather than configuring at the agent level), you can use the textOnly override in your conversation configuration:

1from elevenlabs.client import ElevenLabs
2from elevenlabs.conversational_ai.conversation import Conversation, ConversationInitiationData
3
4# Configure for text-only mode with proper structure
5conversation_override = {
6 "conversation": {
7 "text_only": True
8 }
9}
10
11config = ConversationInitiationData(
12 conversation_config_override=conversation_override
13)
14
15conversation = Conversation(
16 elevenlabs,
17 agent_id,
18 requires_auth=bool(api_key),
19 config=config,
20 # Important: Ensure agent_response callback is set
21 callback_agent_response=lambda response: print(f"Agent: {response}"),
22 callback_user_transcript=lambda transcript: print(f"User: {transcript}"),
23)
24
25conversation.start_session()

This configuration ensures that:

  • No audio input/output is used
  • All communication happens through text messages
  • The conversation operates in a chat-like interface mode

Important Notes

Critical: When using chat mode, you must ensure the agent_response event/callback is activated and properly configured. Without this, the agent’s text responses will not be sent or displayed to the user.

Security Overrides: When using runtime overrides (not agent-level configuration), you must enable the conversation overrides in your agent’s security settings. Navigate to your agent’s Security tab and enable the appropriate overrides. For more details, see the Overrides documentation.

Key Requirements

  1. Agent Response Event: Always configure the agent_response callback or event handler to receive and display the agent’s text messages.

  2. Agent Configuration: If your agent is specifically set to chat mode in the agent settings, it will automatically use text-only conversations without requiring the override.

  3. No Audio Interface: When using text-only mode, you don’t need to configure audio interfaces or request microphone permissions.

Example: Handling Agent Responses

1def handle_agent_response(response):
2 """Critical handler for displaying agent messages"""
3 print(f"Agent: {response}") # Update your UI with the response
4 update_chat_ui(response)
5
6config = ConversationInitiationData(
7 conversation_config_override={"conversation": {"text_only": True}}
8)
9
10conversation = Conversation(
11 elevenlabs,
12 agent_id,
13 config=config,
14 callback_agent_response=handle_agent_response,
15)
16
17conversation.start_session()

Sending Text Messages

In chat mode, you’ll need to send user messages programmatically instead of through audio:

1# Send a text message to the agent
2conversation.send_user_message("Hello, how can you help me today?")

Concurrency Benefits

Chat mode provides significant concurrency advantages over voice conversations:

  • Higher Limits: Chat-only conversations have 25x higher concurrency limits than voice conversations
  • Separate Pool: Text conversations use a dedicated concurrency pool, independent of voice conversation limits
  • Scalability: Ideal for high-throughput applications like customer support, chatbots, or automated testing
PlanVoice ConcurrencyChat-only Concurrency
Free4100
Starter6150
Creator10250
Pro20500
Scale30750
Business30750
EnterpriseElevatedElevated (25x)

During connection initiation, chat-only conversations are initially checked against your total concurrency limit during the handshake process, then transferred to the separate chat-only concurrency pool once the connection is established.

Use Cases

Chat mode is ideal for:

  • Chat Interfaces: Building traditional chat UIs without voice
  • Testing: Testing agent logic without audio dependencies
  • Accessibility: Providing text-based alternatives for users
  • Silent Environments: When audio input/output is not appropriate
  • Integration Testing: Automated testing of agent conversations

Troubleshooting

Agent Not Responding

If the agent’s responses are not appearing:

  1. Verify the agent_response callback is properly configured
  2. Check that the agent is configured for chat mode or the textOnly override is set
  3. Ensure the WebSocket connection is established successfully

Next Steps

  • Learn about customizing agent behavior
  • Explore client events for advanced interactions
  • See authentication setup for secure conversations