Retell Workflows: Orchestration for AI Cold Calling

Retell just shipped Workflows, a new layer that handles what a voice agent does before a call connects and after it hangs up. For anyone running AI calling campaigns, this is the part that usually breaks: the call itself is fine, but the routing, the CRM write-back, and the handoffs around it are held together with duct tape. Workflows moves that glue inside Retell.

We build and run Retell agents for clients every week, so here's a plain read on what changed and where it actually helps.

What Retell shipped

Retell Workflows is, in their words, "native orchestration for all of your voice agent's work." The point is that a live conversation is only one piece of a calling campaign. There's setup before the phone rings and follow-through after it ends, and until now a lot of that lived in outside tools.

The launch (dated August 24, 2026) includes:

• Integration Library — connect Slack, Google Drive, Salesforce, and other platforms directly inside the Retell dashboard.
• Tool Store — a central place to discover and add integrations and capabilities to an agent.
• Preset Functions — common actions come predefined instead of being hand-built each time, which makes agent behavior more predictable.

Alongside Workflows, the same release cleaned up several things that matter more than they sound:

• Transfer handling — ASR phrase splits no longer break transfer confirmation, and failed transfer or agent-swap paths are no longer silently dropped.
• Duplicate actions — each action now fires once per call instead of occasionally running twice.
• Call screening — iOS and Google call screening is now recognized properly, so agents stop mistaking a screened call for voicemail.
• Spanish transcription — Soniox high-accuracy Spanish speech recognition now covers every call.
• Model support — GPT-5.6 and GPT Realtime 2.1 are also named in the release's platform updates.

Why this matters for outbound teams

Most AI calling failures aren't the conversation. They're the seams. A call books a callback but the CRM never records it. A warm transfer to a human fails and nobody notices because the failure path was silent. An action fires twice and a lead gets double-logged or double-texted. None of that shows up in a demo, but all of it shows up in a live campaign at volume.

Pulling orchestration into Retell means fewer of those seams live in a separate automation tool that can drift out of sync. The transfer and duplicate-action fixes are the quiet headline here. If you run booked-callback or transfer-to-owner plays — which most of our client campaigns do — a silently dropped transfer is a lost lead you can't even see in the logs. Closing that gap is worth more than any new feature.

The Spanish transcription and call-screening fixes matter for real dialer conditions too. Screened calls read as voicemail meant wasted retries and bad disposition data; getting that right tightens your cadence math. And for bilingual markets, high-accuracy Spanish on every call is the difference between a usable transcript and a guess.

How we'd use it

Here's how we'd wire Workflows into the outbound systems we run, not in theory but in the campaigns we operate today:

1. Kill silent transfer failures on callback plays. Our voice agents are meeting-first — the goal is a booked callback or a live handoff to the owner. With failed transfer paths no longer dropped, we'd route every failed transfer into a follow-up action: log it, flag the lead for a human callback, and fire a text so the prospect isn't left hanging. That's a lead saved that used to vanish.

2. Move CRM write-back inside Retell. The Integration Library's direct Salesforce (and Slack) connection lets us push call outcomes — captured name, number, intent, disposition — straight from the agent instead of through a middle layer. Fewer hops means fewer places for a lead to fall out of the pipeline before a rep sees it. For HubSpot or GoHighLevel shops we'd still bridge through our own layer, but the direction is clear.

3. Standardize the boring actions with Preset Functions. Every campaign we build repeats the same handful of moves: capture and confirm a phone number, mark a callback window, escalate to the owner, drop a voicemail on no-answer. Presets let us stop rebuilding those per agent and get more predictable behavior across a client's whole fleet — which also makes our QA sim-suites cleaner to grade. (Retell's Conductor testing layer pairs directly with this.)

4. Trust the disposition data again. With duplicate actions fixed and call screening recognized, the numbers coming out of a campaign get more honest. That feeds our dialer pacing — attempts per number, retry windows, rest logic — which only works if the underlying dispositions are accurate. Better inputs, better cadence, better contact rates.

Our read: Workflows is less a flashy feature and more Retell admitting that the campaign around the call is where teams actually lose money. That's the right thing to fix.

FAQ

What is Retell Workflows?

It's Retell's native orchestration layer for everything a voice agent does before a call connects and after it ends — integrations, a tool store, and preset functions — so the setup and follow-through don't have to live in a separate tool.

Does Retell Workflows replace my CRM or automation platform?

No. It connects to platforms like Salesforce and Slack directly and standardizes common actions, but you'll still use your CRM as the system of record. For HubSpot or GoHighLevel you'll likely bridge through your own layer.

Is Retell good for AI cold calling and appointment setting?

Yes — it's one of the platforms we build client outbound agents on. The August 24 update specifically improved transfer handling, duplicate-action reliability, and call-screening detection, which are exactly the things that matter for booked-callback and transfer-to-owner campaigns. (We also compared the platforms in Bland AI vs Vapi.)

Source: Retell changelog, August 24, 2026.