Changelog

Call log filters used to show only calls that met every condition. You can now combine filters with and/or in groups, pick several values per filter, and search transcripts for what the caller said. For example, you can find failed calls from two agents, or any call where the caller mentioned a refund.

Select Add filter or press F to start, or Query to edit your filters as text. Share the page link to give someone the same view. Learn more about advanced filters.

Subaccount IDs used to be long numeric strings, such as 1787331136169x116288779214334560. New subaccounts now get a shorter ID, such as test_subaccount_hO0KX.

Existing subaccounts keep their current IDs, so nothing changes for them. If your integration checks the ID format, update it to accept both.

Attaching or detaching an action in the agent editor used to change the live agent right away. Restoring an older version also kept your current actions. Action changes now wait in your draft until you publish, and restoring a version brings back the actions it had.

Each action’s own setup, such as its URL or transfer destinations, is still shared by all versions. Through the API or the MCP server, attaching or detaching an action still goes live right away. Learn more about editor and API changes.

One agent can now use several phone numbers, and you manage them all from its deployment settings. Add or remove numbers there, and pick which number calls you when you test a call. See Number Pooling.

Revert a version into your draft

If a revert put the wrong configuration live, you had to publish again to undo it. Restoring a version now offers Revert, which loads it into your draft so you can test and edit it first. Revert and publish still makes it live right away. See Restore this version.

If you lose track of what you edited since the last publish, you no longer have to open Publish or Compare changes to find out. Select Draft · N changes in the agent editor header to open the Changes panel. Select a setting’s name in the panel to jump to it in Global Settings.

If you build agents that speak German, you now have ten more native German voices to choose from. They are in the recommended voices, with a new German accent that marks native German speakers.

In the voice list, set the language to German and the accent to German to find Ben, Heidi, Susi, and the seven others.

Until now, you could only see what changed between a version and the one right before it. Now you can compare any two versions of an agent, including your draft.

Select Compare changes in the agent’s version history to pick the two versions.

When a warm transfer failed, you only had the caller’s recording. With Save Recordings and Continue recording after the transfer on, warm transfers now get their own recording, including ones that failed after they were answered.

List agent versions via API

An agent’s version history could only be viewed in the app. Through the API, List agent versions now returns every published version, newest first, with who published it, when, and which version is live.

Expressive delivery with one toggle

Getting an agent to sound warm or reassuring meant writing audio tags into the prompt. Turn on Expressive mode and the agent picks its own delivery, and transcripts stay free of tags.

New MCP server tools

The MCP server can now read a single knowledge base item and create post-call email actions. get_agent also returns the agent’s business hours.

The recording_url field in the calls endpoints becomes unavailable on January 10, 2027. It keeps working until then. Use Get a recording instead: ask for a download link whenever you need the audio, instead of storing one.

Follow our guide to switch.

Reconnect Salesforce by November 30

We changed how Synthflow connects to Salesforce. To keep your Salesforce custom actions working, reconnect Salesforce in each workspace by November 30, 2026.

Follow these instructions to reconnect.

Subaccount webhooks went out unsigned, so you couldn’t confirm they came from Synthflow. You can now share your workspace’s secret key with your subaccounts, so their webhooks carry the same HTTP_SYNTHFLOW_SIGNATURE header you already validate.