For a programme lead, the useful question after Dreamforce 2026 is simple: what is available now, what is in pilot or beta, and what only has a date. Salesforce answered it product by product in its September 2026 announcements. This note sorts the main items by that status and lists what to check before a plan depends on any of them. Every status and date below is Salesforce-stated (Slack-stated for Slack items) at announcement time. A press release is not a clause in your contract.
Status as Salesforce stated it
AIforce, the headline of the first day, is an umbrella. Salesforce describes it as a layer that brings Salesforce data, workflows, business logic, permissions and governance into Claude, Slack and Lightning, and says it works with existing permissions and business rules, with no new permissions model. Its availability is the availability of its companions: Agentforce Coworker, Claudeforce and Slackforce.
| Announcement | What it is | Status and date (Salesforce-stated) |
|---|---|---|
| Agentforce Coworker | AI teammate in Lightning that calls the Agentforce agents an org already has | Available, activated with a button |
| Slackforce Surfaces | Slackbot builds a dashboard, report or tracker that a channel pins and works from | Available now; live-data refresh rolls out from October 2026 |
| Big Mode | Full-screen Slackbot workspace for research, writing and analysis | Available now (Slack-stated) |
| Slackbot in Lightning | Slackbot panel beside Salesforce records | Available now on Slack Business+ and Enterprise+, Flex Credits for other Salesforce customers (Slack-stated) |
| Claudeforce | Salesforce inside Claude through a prebuilt MCP, sales skills and a Development plug-in | Beta, open to all customers |
| Koa | Salesforce’s first CRM reasoning model for Agentforce, built on NVIDIA Nemotron | Select pilots; GA expected Winter 2026 in U.S. regions |
| Hunter | Outbound sales agent on a long-horizon runtime, with human approval gates | Pilot; GA November 2026 |
| Slackbot in Channels | Slackbot tagged into a channel so the team builds on one answer | Early pilot (Slack-stated) |
| Agent Optimizer | Build, test and refine agents from session traces | GA October 2026 |
| Campaign Agent | Marketing Cloud Next agent that assembles audience, content and channels from goals | GA October 2026 |
| Hyperforce on Google Cloud | Salesforce infrastructure running on Google Cloud | North America GA November 2026; phased 2027 expansion including Germany |
| Slack Frontline, two-way Voice, video generation | Slack roadmap items | Preview or “later this year”, no firm date (Slack-stated) |
Around the Google Cloud announcement, Salesforce also named several Gemini pieces, each with its own status, from GA now to private preview. On Koa, Salesforce states that it controls the model weights, keeps post-training and inference inside its trust boundary, and did not train the model on customer data.
Agents that run for weeks change who is on call
The item that changes delivery most is the runtime behind Hunter. Salesforce describes an agent that pursues a goal across days and weeks, with human approval gates, instead of finishing one prompt and stopping. The failure mode shifts with it. An agent can stay quiet for days, then act. Someone still owns the approval gate, the exception path and the stop, and that person needs a name before the pilot starts.
Agent Optimizer points the same way. Improving an agent from session traces after go-live means someone is assigned to read those traces on a schedule. That is a run cost to put in the operating model, next to licences.
Coworker is the other quiet change. It calls the agents an org already has and, per Salesforce, relies on existing permissions. The new interface therefore inherits whatever the current permission sets allow, so the permission review comes before the activation button. The ownership questions are the ones in the Agentforce operating model note.
Before you plan around it
- Who owns the approval gate. For a long-running agent, name the approver, the delay allowed for an answer, and what the agent does when nobody answers. Write the stop procedure before the pilot starts.
- Region. Koa’s GA is announced for U.S. regions. Hyperforce on Google Cloud starts in North America and reaches Germany in a 2027 phase. An org hosted elsewhere should get its own date in writing from the account team rather than infer it from a keynote.
- Licensing and editions. Slackbot in Lightning depends on the Slack plan or on Flex Credits, Surfaces depend on the workspace plan, and rollout timing or extra licences can still change who gets access. Ask for the SKU and the consumption model before the business case is signed.
- What beta and pilot commit the vendor to. A beta open to all customers (Claudeforce) and a select pilot (Koa, Hunter) are different things, and neither is GA. Ask in writing what support, data handling and path to GA apply, and read the beta terms in your own agreement. Keep any milestone that depends on an announced GA date off the critical path, or give it a fallback.
- Vendor figures. Salesforce reports Koa results on its own CRM Benchmark. Treat it as a vendor benchmark and plan your own evaluation on your data and processes.