Niches · Conversational voice agents

Keep a call alive past the model's connection limit

Four or more companies' docs show a full fit.

4companies, full fit
13companies, fit with a limit
29companies carry the tag
7share of the category's work
4first-hand accounts

What counts as done

The call continues past 30 minutes with context carried over, and no tool result replayed or re-executed after the reconnect.

Measured, for our own tests: no audible gap over 1 second. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: calls drop at 10 minutes, the session ends after 8 minutes, resume the conversation without the caller noticing

Does the job 4

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Deepgram Voice Agent API BB
Deepgram, Inc.
Sessions last 2 hours with a MAXIMUM_SESSION_LENGTH_APPROACHING warning 5 minutes ahead; a new session can be seeded with agent.context messages including function calls. KeepAlive every 8 seconds holds idle sockets. source
Retell AI API + MCP B
Retell AI Inc.
max_call_duration_ms defaults to 1 hour and goes to 2 hours, end_call_after_silence_ms defaults to 10 minutes (minimum 10 s); the platform holds the call, so no client reconnect is needed. source
Rime Prism B
Rime Labs, Inc.
The limits table states no conversation time limit; only 5 minutes idle closes it, and context beyond 65,536 tokens drops the oldest turns. source
Vapi API + MCP B
Vapi Inc.
A cascaded pipeline with no provider socket limit exposed; maxDurationSeconds runs 10 to 43,200 s (default 600) and silenceTimeoutSeconds 5 to 3,600 s, so a call can be configured past 30 minutes. source

Does the job, with a limit 13

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Nova 2 Sonic B
Amazon Web Services, Inc.
Connections end at 8 minutes; continuation means a new session with chat history sent once, implemented by the client from samples. Reconnects can replay tool calls. source
AssemblyAI Voice Agent API C
AssemblyAI, Inc.
session.resume keeps context for 30 seconds after a drop, but the session ends at max_session_duration_seconds with close 1008 and no warning event; behaviour of pending tools across a resume is not documented. source
Bland AI API + MCP B
Intelliga Corporation
A phone call has no socket lifetime to manage, but max_duration defaults to 30 minutes and ends the call; it must be raised per call or agent. source
Bolna API + MCP D
Voxlabs Private Limited
Phone calls have a configurable total call timeout rather than a socket lifetime, but hang-up on user silence (6 to 10 seconds suggested) ended calls at about 12 seconds in a reproduced account. source
ElevenLabs Agents API + MCP BB
Eleven Labs Inc.
max_duration_seconds defaults to 600 (10 minutes) and can be set from 60 to 7,200, so a long call needs the setting raised; no reconnect is needed within that limit. source
Gemini Live API C
Google LLC
Connections last about 10 minutes with a GoAway warning; resumption handles valid 2 hours and context compression are documented but off by default. Calls dropped where the client only logged GoAway (acc-15), and Pipecat replayed settled tool results on resume (acc-24). source
GPT-Live BB
OpenAI OpCo, LLC
Connected SIP calls last up to 2 hours and context over 90 per cent is summarised into a replacement engine inside the same session. After a drop, continuation is only by forking a finalised stored recording, unavailable under ZDR. source
LiveKit Agents BB
LiveKit Incorporated
A pipeline session has no socket lifetime and WebRTC reconnects automatically, and user_away_timeout only marks the user away; with a realtime model plugin, the provider's session limit and rotation depend on the plugin (one documents a 60-minute close with no rotation). source
Pipecat B
Daily
A pipeline session has no socket lifetime, but the Gemini Live service resends every settled tool result to the new session after a resumed reconnect (open issue), and the worker's idle timeout defaults to 300 seconds. source
Synthflow API + MCP D
AgentFlow AI GmbH
With Limit Call Duration off no fixed cap applies (the slider tops out at 30 minutes), and Max Idle Duration is configurable, but its default is not stated and no 30-minute account exists. source
Ultravox Realtime API C
Theai, Inc. dba Inworld AI
maxDuration defaults to 3600 s on one call, which covers 30 minutes; beyond that, priorCallId starts a new call with the old history, which is a new call rather than a smooth reconnect. source
Vaani Developer Platform E
Vaani AI Research Private Limited (Bengaluru, India, CIN U62099KA2025PTC201212)
A cascaded pipeline with max_call_duration configurable from 1 to 60 minutes and idle hangup timeouts configurable, so 30 minutes is reachable, but 60 minutes is a hard ceiling and WebRTC sessions default to a 30-minute TTL. source
Vogent API E
Monoid, Inc.
maxDurationSeconds is set per agent with HANGUP or TRANSFER at timeout, and silence hangup can be DISABLED, but no allowed range or default is stated. source

Couldn't check 7

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
fone.me F
Fone
No call length limit is stated in any page that loaded.
Fresha AI Concierge F
Fresha.com SV Ltd
No call length limit is published.
Harmony.ai E
monday.com Ltd.
No call length limit or reconnect behaviour is documented.
Hume EVI (Empathic Voice Interface) C
Hume AI, Inc.
EVI docs withdrawn: every EVI page, including the overview and tool-use guide, redirects to the Audio Decisions overview, and the EVI AsyncAPI file returns 404. The last assessment recorded EVI access ending 13 November 2026. source
Inworld Realtime API B
Theai, Inc. dba Inworld AI
The session object has a read-only expires_at but no page read gives a maximum session length or a reconnect and resume procedure. source
OpenAI Realtime API BB
OpenAI OpCo, LLC
The guides read state no Realtime session lifetime and document no resumption or reconnect; whether a call passes 30 minutes was not established.
PlaceCall C
VOYGR Tech, Inc.
No maximum call length or hold time limit is stated in the repository docs, and the API docs are closed to our crawler by robots.txt.

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
CueLight D
sshah03 (individual GitHub account, no name or organisation stated)
CueLight is an end-of-turn detector only: no call handling, telephony, tools or speech output. source
Pipecat PhoneLLM B
Daily
No session or connection of its own; a text model only. source
Vocily AI C
VOCILY AI PRIVATE LIMITED
max_duration_minutes has a maximum of 30, so a call cannot continue past 30 minutes. source

What stops agents finishing

  • GoAway or 8-minute close with no client reconnect logic
  • resume refused with 1011 after a silent connection loss
  • settled tool results re-sent to the new session
  • inactivity timeout ends the call at 10 seconds of silence

Around it

Before: voice-agents.inbound-receptionist.

Where this comes from

Weight 7 of 100 in Conversational voice agents: 4 of 31 accounts (acc-13, acc-15, acc-23, acc-24)

The same as data: /api/v1/use-cases/voice-agents.long-call-session.json, or the MCP tool get_use_case with id voice-agents.long-call-session. Other jobs in this category: /api/v1/niches?category=voice-agents.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.