Agentforce
Amazon Connect and Agentforce Voice: planning for the fall handoff
One line in the Dreamforce AWS announcement changes the contact centre decision: an agent-to-agent handoff between Amazon Connect and Agentforce Voice, with live audio over WebSockets, dated for fall 2026. This post separates what already works from what is new, lays out the three topologies it makes possible, and lists what to prepare before it ships, without rebuilding your telephony on a promise.
Buried in the AWS and Salesforce announcement on September 15 is a sentence contact centre teams should read twice. Agent2Agent support will enable real-time, bidirectional audio over WebSockets between Agentforce Voice and Amazon Connect, and it is dated for fall 2026.
A small sentence with a large consequence. For years the choice for a Salesforce shop with an AWS contact centre was to run Connect for the phones and Salesforce for the CRM, or to move the whole thing to Salesforce’s own contact centre. A live handoff between two AI agents on two platforms makes a third shape possible. This post is about what that shape looks like and what to do between now and the day it ships.
What already works today
Nothing in the announcement changes the integration you may already run. Amazon Connect is the telephony partner Salesforce provisions natively for Agentforce Voice, and I described the stack in the voice post: Connect carries the call, Salesforce Voice brings it into the org, the Agentforce agent is the first responder, and an Omni-Channel Flow decides where the call goes when the agent cannot finish it.
In that model, “handoff” means one thing: the Agentforce agent gives up and the call goes to a human queue. The agent on the Salesforce side is the only AI on the call. Whatever Connect can do with its own AI features is not part of the conversation once Salesforce has it.
Keep that picture in mind, because the new item is about the case where both platforms have an agent.
What the fall handoff adds
The announcement describes agent-to-agent communication, not agent-to-human. An agent running in Amazon Connect and an Agentforce Voice agent will be able to hand a live call between them, in either direction, with the audio streaming over WebSockets rather than the call being dropped and redialled.
Two words separate that from a transfer. Audio continues, so the caller does not hear a click and a hold tone.
Context travels too, because the mechanism is the Agent2Agent protocol, which carries a task and its state between agents rather than only a phone leg. The Connect agent that verified the caller and understood the intent can pass both to the Agentforce agent that has the CRM record. The Agentforce agent that finished the CRM action can pass the caller back for whatever the Connect side does better.
The announcement stops there. Salesforce has not published which Connect features are in scope, whether the handoff needs Agentforce Contact Center or works with a plain Agentforce Voice licence, or how it is billed. Fall 2026 covers a lot of weeks. Treat the rest of this post as planning, not procurement.
The three shapes it makes possible
Once two agents can hand a call between them, there are three ways to arrange them, and the right one depends on where your investment already sits.
Connect-first. The Connect agent answers every call, handles identification and the generic intents, and hands to Agentforce only when the caller needs something that lives in Salesforce: a case update, an order, a refund under policy. This suits an estate where Connect is deep and mature and Salesforce is the system of record for a subset of intents.
Agentforce-first. The Agentforce Voice agent answers, grounded on the CRM and knowledge, and hands to a Connect agent for work that lives on the AWS side, such as a specialist flow or an integration Connect already owns. This suits an org where the customer’s history is the main thing the caller needs and Connect is mostly the carrier.
Both, by intent. The IVR or the first agent classifies, and each intent is routed to whichever platform’s agent owns it, with handoff available mid-call when the intent changes. The third is the most powerful shape and the hardest to operate, because two teams now own halves of one conversation.
My suggestion is to pick the first or second for the pilot and earn the third. The contact centre post framed the choice as native versus best-of-breed. The handoff does not remove that choice. It makes “keep both” a design rather than a compromise.
What stays where
A live handoff raises questions that a transfer never did, because the call now has two homes. Decide these before the preview, not during it.
Recording and compliance. One platform has to be the system of record for the call recording, and your retention and consent rules have to hold across the handoff. If Connect records and Agentforce does not, the Salesforce side of the conversation may exist only as a transcript. I mapped where conversation data lives for the Salesforce side. Do the same for the Connect side.
Routing and queues. Omni-Channel Flow is the brain on the Salesforce side. Connect has its own routing. When a handoff fails or the second agent escalates, which queue does the caller land in, and does that queue see the whole history or half of it.
Measurement. CSAT, containment, time to first audio and abandonment are measured by both platforms and will disagree. Choose the one that reports to the business and reconcile the other to it. Agentforce observability covers the Salesforce leg.
Escalation to a person. Two agents can hand to each other all day, and the caller still needs a route to a human that both sides honour. The escalation design should be one policy, not one per platform.
What to prepare before it ships
Five things, none of which need the feature to exist.
Identity propagation. Decide where the caller is verified and how that verification travels. A2A carries context, but the policy about what counts as verified is yours, and it has to satisfy both platforms’ compliance teams.
The context payload. Write down what must cross the boundary for a handoff to be useful: verified identity, the intent, what has already been said, what has already been done. If the Agentforce agent has to ask the caller to repeat themselves, the handoff has failed even if the audio was flawless.
The latency budget. Voice lives or dies on time to first audio. A handoff adds a hop. Set a budget for it and design the fallback for when it is exceeded, which is usually “stay on the current agent and finish there” rather than “try again”.
The credit model. On the Salesforce side a voice action costs 30 Flex Credits, per the pricing mechanics. On the AWS side Connect bills its own way. Nobody has said how a handed-off minute is metered. Ask.
The test set. Build voice test cases that cross the boundary: a caller who changes intent mid-call, one whose verification fails, one who asks for a human at the wrong moment. You will run them the first week of the preview, and writing them now is free.
What to ask both account teams
Ask Salesforce for the preview timeline by region, whether the handoff requires Agentforce Contact Center or works with Agentforce Voice on its own, and how the handed-off leg is billed. Ask AWS which Connect agent capabilities are in scope, whether there is a Connect-side licence implication, and what the WebSocket path means for your network and security review.
Then ask both the same question: what happens when the other platform is unavailable. The answer tells you how each side has designed the failure mode, and that is the answer you will care about at two in the morning.
Why not migrate on the promise
The temptation, if you run Connect, is to read this as a reason to move everything to Salesforce’s contact centre now that the two will talk. The opposite reading is stronger. If the handoff ships as described, a Connect estate keeps its value and gains a governed path into Agentforce for the intents where the CRM matters. That argues for staying put and building the seam.
It also argues against building anything on the feature until it is generally available with documentation. Plan the topology, prepare the five items above, and run the pilot when the preview opens. Rebuilding telephony on a fall date is how a contact centre ends up with two half-finished platforms instead of one seam.
Understanding the basics
What is the Amazon Connect and Agentforce Voice handoff?
A planned capability, announced on September 15, 2026 and dated for fall 2026, that uses the Agent2Agent protocol to hand a live call between an agent running in Amazon Connect and an Agentforce Voice agent, in either direction, with real-time, two-way audio carried over WebSockets and the conversation context passed along.
Does Agentforce Voice already work with Amazon Connect?
Yes. Amazon Connect is the natively provisioned telephony option for Agentforce Voice today, alongside partner platforms such as Genesys, Five9, NICE and Vonage. What is new is a handoff between two AI agents on the two platforms, rather than Connect carrying a call to a single Agentforce agent.
Do I need Agentforce Contact Center for the handoff?
Salesforce has not said. The announcement describes the handoff in terms of Agentforce Voice and Amazon Connect and does not mention a licence requirement. Ask your account team before planning around either answer.
When will the handoff be available?
Salesforce and AWS have dated it for fall 2026. No preview dates, regions or pricing have been published as of September 20, 2026.
Build the seam, keep the platforms
The most expensive contact centre decisions are the ones made to remove an integration. This announcement is Salesforce and AWS saying the integration is the product, and that two agents on two clouds can share one call.
If that lands as described, the winning move for a Connect shop is not a migration but a well-designed seam, with identity, context, recording and escalation decided before the first handed-off call.
If you run Amazon Connect alongside Salesforce and want the topology, the context payload and the failure modes designed before the preview opens, talk to us, or start with the Agentforce readiness assessment.
