You're asking what a new caller to your voicebot will experience when LiveKit Server or an Agent Server is at max load. Here's what happens and what you can do. What the caller experiences • Callers are not automatically placed in a LiveKit-managed queue to wait for capacity. • If all agent servers are at capacity, the dispatcher will not assign the call and the caller will typically see a rejection, timeout, busy/disconnect tone, or be routed according to your SIP/telephony settings (for example to voicemail or an IVR fallback). • The exact behavior depends on your telephony/SIP trunk and dispatch rules. Options you can use to improve CX • Implement external call queuing or a task/ retry queue so callers are held and retried when capacity frees up. • Configure SIP/telephony fallback (voicemail, IVR message, or busy prompt) to present a friendly message when no agent is available. • Scale out agent servers or adjust

load_threshold

and deployment strategy so more capacity is available during peaks. If you’d like, tell me: • How you currently route inbound calls (SIP trunk, provider), and • Whether you prefer a queued wait experience or a fallback message/voicemail, and I’ll suggest concrete configuration or architectural options tailored to your setup. Sources: Agent server options | LiveKit docs | Deploying to custom environments | LiveKit docs | Accepting inbound calls | LiveKit docs