Changelog

Notable, user-facing changes to the VoiceDock platform and API, newest first. Dates reflect public availability.

July 2026

• Automatic failover — our first stable release (1.0). VoiceDock now runs active-passive: a warm standby mirrors production continuously and takes over automatically if the primary stops responding, typically within about 90 seconds and with nothing to change on your side. We verified it end to end on production with a controlled outage — a real inbound call was answered on the standby with recording, analysis and billing intact. If a failover ever happens, we are paged automatically.
• Sign in to the MCP server with your account (OAuth 2.1). Connect Claude, Claude Code, Cursor, or any MCP client to the MCP server with just the URL — no API key to copy. Your client opens a browser, you log in with your VoiceDock account and approve access on a consent screen, and it works against your organization. A raw API key still works as a bearer token for CI and scripts.
• Multiple recipients and action buttons for end-of-call reports. Send the post-call report email to up to five addresses per assistant, and choose which buttons the email shows — an "Open in dashboard" link, a direct "Listen to recording" button, both, or neither. Configure it on the assistant in the dashboard. See Call analysis.
• Itemized telephony costs on managed numbers. Calls on platform-managed phone numbers now meter the phone legs as a provider cost at carrier list rates — itemized per call in the cost breakdown next to model usage, on top of the unchanged €0,07/min orchestration fee. A transferred call shows the inbound line and the outbound leg to the destination as separate lines; unanswered transfer attempts cost nothing. Numbers on your own SIP trunk are exempt, exactly like BYOK for models. See Billing.
• No-answer handling for call transfers. Transfers can now wait for the destination to actually answer before connecting the caller (wait_for_answer on the transfer tool). If nobody picks up within the configurable timeout — or the line is busy — the assistant stays with the caller and can take a message, try one of the configurable backup numbers (fallback_destinations, tried in order), or end the call politely. Existing transfers are unchanged: without the flag, transfers connect immediately as before. See Call Transfers.
• Workflows (Beta). Build multi-step call flows on a visual canvas: conversation steps with their own instructions — and optionally their own model, voice, text-to-speech or speech-recognition settings — background tool calls that always run, guaranteed human transfers and clean endings. Global steps such as "back to reception" are reachable from anywhere without drawing lines. One assistant keeps supplying the defaults and call settings; the workflow drives inbound calls on the numbers it is attached to. Attach a workflow to a phone number in the dashboard or via the API. See Workflows and the Workflows API.
• Webhooks per phone number. A webhook can now be set directly on a phone number, alongside per-assistant and account-wide webhooks. For each event, VoiceDock delivers to exactly one endpoint, with precedence assistant → phone number → account: a number's webhook is used when its assigned assistant has none, and takes precedence over the account webhook. See Webhooks overview.

June 2026

• Developer logs. A new Logs page in the dashboard shows what happens on each call — when it starts and ends, and the errors that stop a call, such as an unknown model or an invalid tool definition. Scoped to your own organization, so you can debug an assistant without opening a support ticket.
• More natural call endings. Assistants now finish their closing line cleanly before hanging up, with no mid-sentence cut-off or trailing silence, including on realtime speech-to-speech models.
• End-of-call reports for platform-key assistants. Assistants running on platform-provided keys (without BYOK) now also receive a post-call summary and structured analysis, just like BYOK assistants. See Call analysis.
• Usage-based, at-cost pricing. You pay for actual model usage at cost, plus a flat €0.07 per minute orchestration fee. Vertex AI Live is a flat €0.25 per minute, all-in. See Billing.
• Bring-your-own-key (BYOK) is now optional. Assistants work out of the box on platform-provided keys; add your own provider keys only if you want to. See BYOK setup.

May 2026

• Documentation and full API reference launched — complete guides plus an interactive REST API reference. Start at the Quickstart.
• xAI Grok for realtime voice — low-latency realtime speech, plus a Grok text-to-speech option. See xAI Grok integration.
• Branded end-of-call report emails — per-organization branding, an "Open in dashboard" link, and a recording hint.
• Configurable call duration up to 30 minutes per assistant (max_duration_seconds). See Assistants.

April 2026

• Google Gemini Live added as a realtime speech-to-speech provider, including a Vertex AI option. See Provider pricing.
• Google Gemini text-to-speech added as a provider.
• Email notifications for web calls.

March 2026

• Official Node.js / TypeScript SDK released — install hmsovereign from npm. See Node SDK.
• MCP server for the platform, hosted at mcp.hmsovereign.com. See MCP server.
• Recording consent flow (DTMF) — callers can be asked to press 1 to consent before any processing begins. See Privacy & compliance.
• More providers — Mistral (Voxtral) speech-to-text and Inworld text-to-speech.
• Improved multilingual turn detection and interruption handling.

February 2026

• More provider options — Mistral and xAI Grok as text models, Gladia and ElevenLabs Scribe as speech-to-text.
• GDPR mode for per-assistant data-retention control. See Privacy & compliance.
• Configurable silence timeout with a faster default.

January 2026

• Web calls — browser-based WebRTC calls, with a public embeddable web-calls API and whitelabel support. See Web calls.
• Call recording with signed URLs for secure access.
• Voicemail detection and a configurable voicemail message. See Voicemail detection.
• Autonomous silence handling — recurring prompts when a caller goes quiet. See Autonomous silence handling.
• Outbound campaigns — campaign tracking for outbound calls. See Campaigns.
• Assistants can speak while running a tool, with async tool results fed back into the conversation. See Custom tools.
• Richer webhook events — deterministic end reasons, call timestamps, and phone-number and direction fields.
• Real-time sync webhook API, replacing polling.
• Free local voices for text-to-speech.
• Prompt template variables such as {{ now }}.

December 2025

• Public API foundations — assistants, calls, and phone numbers as first-class resources, with agent configuration separated from phone numbers.
• Webhooks — assistant-request (pre-call config override), status-update, tool-calls (function calling), and end-of-call-report with full transcript. See Webhooks.
• Live Call Control API — inject context, speak, transfer, or end a call mid-conversation.
• Built-in call control — LLM-controlled end_call and call transfer. See Call transfers.
• Outbound call API.
• Post-call structured analysis. See Call analysis.
• Bring-your-own-key (BYOK) providers and SIP trunk support. See SIP trunks.
• xAI Grok realtime speech-to-speech provider.
• Whitelabel support — child organizations, per-organization email domains, and branded summaries. See Whitelabel.
• Usage-based billing in credits, at a flat €0.07 per minute.
• Multilingual emails and call summaries.