Agentforce
Dreamforce 2026 for service leaders: Casey, Fin, the Connect handoff, and what is dated
Service got the most Dreamforce minutes of any cloud: two named service agents, a rep assistant whose plan rewrites itself, a contact centre product in 30 countries, and a voice handoff with Amazon Connect due this fall. This is what a service leader can use now, what is dated, what the customer numbers do and do not say, and the decisions to make before the October upgrade weekends.
If you run a service operation, Dreamforce 2026 gave you more to decide than anyone else in the building. Two agents with names, both generally available. A rep assistant that replans mid-case. A native contact centre now sold in more than 30 countries. And a voice handoff with Amazon Connect, dated for the fall, that changes the migration question for anyone on AWS telephony.
The recap covers the whole event. This post takes the service items on their own and sorts them into what you can switch on, what you should wait for, and what the numbers on stage were measuring.
Two service agents with names, and the choice between them
Salesforce’s September 11 announcement gave the service agents names. Casey, formerly the Help Agent, resolves customer issues across voice, SMS, WhatsApp and web chat, with prebuilt support for FAQs, returns, account management and escalation. It is generally available, and Engine reports 50% of chat inquiries fully resolved by it.
Fin came with the Intercom acquisition and is also generally available. Salesforce positions it as the agent for organisations with multiple CRM systems, running on the Operator and Fin Apex models it inherited, and cites Anthropic resolving 79% of conversations with it. I covered what the acquisition meant when it was announced and what a named agent is under the hood last week.
The choice is simpler than the marketing makes it. If your service data, knowledge and cases live in Salesforce, Casey is the agent that inherits your sharing model, your knowledge articles and your Flows without integration. If your customers’ history is spread across two or three systems and Salesforce is one of them, Fin was built to sit across them. Turning on both for the same queue is the mistake to avoid.
The rep assist is a plan that rewrites itself
Adaptive Experiences and Dynamic Plans led the Winter ‘27 announcement and got keynote time again. The Service Rep Assistant watches a live case and regenerates the resolution plan as the conversation changes, without the rep re-prompting it.
I wrote up what a dynamic plan is when it shipped. The point to hold onto is that it is rep assist, not autonomy. The plan rewrites itself, the human executes it, and a plan that re-plans on every turn has a credit and latency profile you should model on one queue before switching it on for the floor.
The contact centre, and the handoff that changes the migration question
Two announcements land on the same decision.
Agentforce Contact Center is now available in more than 30 countries, which reopens the native-CCaaS question for multinationals that were excluded on geography. The call on going native still comes down to routing, recording, and the cost of moving the channel stack you already own.
The second announcement makes that call harder to rush. Salesforce and AWS described an Agent2Agent handoff between Amazon Connect Customer and Agentforce Voice, with real-time two-way audio over WebSockets, dated for Fall 2026. A call on Connect can move to an Agentforce Voice agent, or back, without restarting. If that ships as described, a contact centre that runs telephony on Connect and CRM on Salesforce can keep both and build the seam, rather than replacing one to get the other. My AWS post has the rest of that announcement.
Vivint demonstrated live voice observability in the keynote, per Salesforce Ben’s roundup: session logs, response quality, action traces and latency on a live call. That is the instrumentation a voice agent needs before it takes a queue, and it exists today.
What the numbers on stage were measuring
Service produced most of the headline percentages. All of them are the customers’ or Salesforce’s figures, and all of them are worth reading twice.
Live Nation’s Venue Agent resolves 95% of fan inquiries without a human, on parking, accessible seating, door times and event logistics. The TSA’s Ace agent resolves 96% of routine questions, on packing rules and medical device procedures, across roughly 100,000 conversations a month. Engine’s 50% and Anthropic’s 79% are the Casey and Fin figures above.
Notice the denominators. Ninety-five and ninety-six percent are resolution rates on intents that were FAQ-shaped to begin with. They are real, and they tell you what a narrow agent does on routine volume. They do not tell you what happens on a refund dispute or a complaint.
For that, the more useful example was Southwest Airlines, which showed a structured Agent Router with dedicated subagents for intake, document validation, reimbursements and ticket refunds on a customer name change. That is the subagent and topic design I keep recommending, and it is the shape Agent Optimizer needs. The Optimizer demo traced a spike in escalated refunds over $200 to a router gap, proposed the fix and wrote the tests. It goes GA in October, and what to enable before then is mostly a service leader’s decision, because the traces come from your queues.
Field service and IT service got their own items
Field Service gets an always-on Scheduling Agent built on your business rules, and Voice to Form, where a technician fills a form by talking to a phone, now described as multi-language. Both extend what I mapped in Agentforce for Field Service, and the line I drew there still holds: the agent can book and rebook inside the rules, and a dispatcher still owns the exceptions.
Siemens gave the field side a concrete shape in its own release: Agentforce connected to its Teamcenter service lifecycle system, so a technician can identify a spare part and validate a quote from engineering data during the visit. That integration is the work. The agent on top of it is the easy part.
IT Service Management adds a CMDB and a service graph, per the keynote. The coverage is thin, and I could not find documentation yet, but it addresses the gap I flagged in the IT Service post, where the employee-agent story was strong and the configuration data underneath it was not.
What is dated
Casey, Fin, the Contact Center expansion and Adaptive Experiences are available now. The Connect handoff is Fall 2026. Agent Optimizer is October. AI Skills for Coworker, which let a service rep teach the assistant a task, are in pilot with GA in October. Nothing on the service list waits for 2027.
The Monday list for a service leader
Pick Casey or Fin by counting systems, not by reading feature lists. One system of record, choose Casey. Several, evaluate Fin. Do not run both on one queue.
Define resolution before you measure it. Decide whether a contained conversation the customer abandoned counts, because the vendor numbers do not say, and yours should.
Hold any telephony migration that was justified by “we cannot get Agentforce Voice without leaving Connect” until the fall handoff ships or slips. Ask both account teams for the preview timeline.
Turn on session tracing and the Trust Layer audit collection this month, so October’s Optimizer has September’s escalations to read.
Trial Adaptive Experiences on one queue with credit tracking on, and set the outbound controls to confirm before send.
Understanding the basics
What is Casey in Agentforce?
Casey is the named version of the Agentforce Help Agent, generally available since September 2026. It resolves customer service issues across voice, SMS, WhatsApp and web chat using Salesforce knowledge, cases, workflows and permissions, with prebuilt handling for FAQs, returns, account management and escalation.
Should I use Fin or Casey?
Casey if your service data lives in Salesforce, because it inherits your knowledge, cases and sharing model without integration. Fin if customer history is spread across several systems, since Salesforce positions it as the agent that overlays multiple CRMs. Avoid running both on the same queue.
Is Agentforce Contact Center available in my country?
Salesforce says it is now available in more than 30 countries as of the Winter ‘27 release. Check the current country list with your account team, and weigh it against the Amazon Connect handoff due in Fall 2026 if you already run telephony on AWS.
What is the Amazon Connect and Agentforce Voice handoff?
A planned Agent2Agent connection that carries real-time, two-way audio over WebSockets between Amazon Connect Customer and Agentforce Voice, so a call can move between them without restarting. Salesforce and AWS have dated it for Fall 2026. Nothing has shipped yet.
The decisions are cheaper than the migrations
Most of what Dreamforce offered a service leader is a switch: turn on Casey, trial the rep assistant, enable tracing. The expensive decisions, which agent family and which telephony, got easier to defer, because Fin and Casey are both GA and the Connect handoff is dated.
Make the cheap decisions this month. Make the expensive ones when the fall items ship and you can test them against your own queue.
If you want the Casey-or-Fin call made against your own systems, and the tracing and scorers in place before Optimizer arrives, talk to us, or start with the Agentforce readiness assessment.
