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
  • How burst pricing works
  • Capacity calculations
  • Cost implications
  • Example pricing scenario
  • Configuration
Guides

Burst pricing

Optimize call capacity with burst concurrency to handle traffic spikes.
Was this page helpful?
Previous

Building the ElevenLabs documentation agent

Learn how we built our documentation assistant using ElevenLabs Agents
Next
Built with

Overview

Burst pricing allows your ElevenLabs agents to temporarily exceed your workspace’s subscription concurrency limit during high-demand periods. When enabled, your agents can handle up to 3 times your normal concurrency limit, with excess calls charged at double the standard rate.

This feature helps prevent missed calls during traffic spikes while maintaining cost predictability for your regular usage patterns.

How burst pricing works

When burst pricing is enabled for an agent:

  1. Normal capacity: Calls within your subscription limit are charged at standard rates
  2. Burst capacity: Additional calls (up to a concurrency of 3x your usual limit or 300, whichever is lower) are accepted but charged at 2x the normal rate
  3. Over-capacity rejection: Calls exceeding the burst limit are rejected with an error

Capacity calculations

Subscription limitBurst capacityMaximum concurrent calls
10 calls30 calls30 calls
50 calls150 calls150 calls
100 calls300 calls300 calls
200 calls300 calls300 calls (capped)
For non-enterprise customers, the maximum burst currency can not go above 300.

Cost implications

Burst pricing follows a tiered charging model:

  • Within subscription limit: Standard per-minute rates apply
  • Burst calls: Charged at 2x the standard rate
  • Deprioritized processing: Burst calls receive lower priority for speech-to-text and text-to-speech processing

Example pricing scenario

For a workspace with a 20-call subscription limit:

  • Calls 1-20: Standard rate (e.g., $0.08/minute)
  • Calls 21-60: Double rate (e.g., $0.16/minute)
  • Calls 61+: Rejected

Burst calls are deprioritized and may experience higher latency for speech processing, similar to anonymous-tier requests.

Configuration

Burst pricing is configured per agent in the call limits settings.

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

Open your agent in the dashboard, navigate to the Advanced tab, scroll to Call Limits, and toggle on Burst pricing. Save your changes.