Short network drops no longer end a voice conversation
October 8, 2026 · release
@voicethere/client 0.11.6
A Wi-Fi hiccup or a switch from Wi-Fi to mobile data used to end a voice conversation. Now the platform keeps the conversation open for a reconnect window, 15 seconds by default, and the client reconnects inside it. Noticing the drop and reconnecting take about five seconds of that, so with the default an outage of around 10 seconds is ridden out.
What users see
The widget status line shows "Connection lost. Reconnecting…" a couple of seconds after the connection drops, and "Reconnected." when it is back. If the connection does not return in time, the widget says so and goes back to Connect. If you build your own UI, onConnectionStatus carries a recovery state (interrupted, restored or lost), and every message can be replaced with your own text.
Hanging up on purpose ends the session at once: disconnect() tells the platform first, and closing the tab or the connection does the same, so billing stops right away.
A longer window if you need it
The reconnect window is a project setting in the dashboard (Advanced voice settings), from 15 to 30 seconds. The client picks it up automatically. A longer window can bill more: a conversation that comes back is billed in full, including the interruption. One that never comes back stops billing at the moment it dropped, but it holds its place for the whole window. Details are in Reconnect window.
Busy speech servers
A speech server that is restarting or full used to be able to end the conversation. Now the agent's reply waits for up to 30 seconds. If a reply still cannot be spoken, only that reply is skipped and the conversation goes on.
Try it
npm install @voicethere/client@0.11.6
The status states, message overrides and the two error codes (WEBRTC_RECONNECT_EXHAUSTED, SESSION_ENDED_DURING_RECONNECT) are in Connection drops and reconnect.