Your client's sales VP opens the November pipeline review and finds new Stage and Next Step suggestions on six opportunities, drafted from last week's call transcripts. Nobody on the admin team switched anything on. That is Winter '27 in one scene: Salesforce is turning agent features on by default, and the client conversation shifts from "should we try Agentforce" to "who governs what it already does."
This is the consultant's map of Winter '27: what to say about the renames, what demos well, which migrations to staff, and which dates to put in front of every client before they find them the hard way. Release notes first published the week of August 17, 2026. Sandbox preview started the weekend of August 28-29, and production orgs upgraded in waves through the weekend of October 9-10, 2026. Several features roll out monthly, so some of what follows reached orgs in late October and November.
The rename map: what to tell clients
Clients will see new product names in Setup, contracts and Trailhead before they see new features, so lead with the vocabulary.
- Sales Cloud is now Agentforce Sales. The release notes open the Sales section with that sentence and warn that you will still see Sales Cloud named in the app and documentation.
- Salesforce Voice is now Partner Contact Center. Help describes it as "formerly Salesforce Voice with Telephony Providers and Service Cloud Voice." It is the model where a third-party contact center such as Amazon Connect does the telephony.
- Agentforce Contact Center is the fully native option with built-in telephony. Salesforce's Winter '27 Top 10 says it now covers more than 30 countries.
- Data Cloud is Data 360, a rename Help dates to October 14, 2025. Clients who skipped two releases will still say Data Cloud.
- Next Generation DevOps Center is now Lifecycle Center. The DevOps Center managed package keeps its name and can migrate into Lifecycle Center. Expect this one in partner SOWs.
- The Agentforce assistant is now Agent Optimizer (Beta) inside Agentforce Builder. Several industry clouds also carry Agentforce names now, such as Agentforce Education (formerly Education Cloud) and Agentforce Nonprofit.
The practical consulting task is the same as it was for the Summer '26 rename: update proposal templates, solution diagrams and training decks, and tell client steering committees the licences and objects did not change.
Agentforce is on by default: lead with governance
The biggest Winter '27 conversation is not a feature. It is a default. The release note "Agentforce Platform Enabled by Default" says the platform is enabled for all orgs with Agentforce access granted by SKUs, licensing and editions. New orgs are enabled at creation. Existing orgs were enabled on a rolling basis starting the first week of September 2026. Removing the Agentforce setting from the Agentforce Agents page is "planned for later in Winter '27." The note says there is no additional cost and no billing change.
Two things follow for every client. First, the only off switch the note names is the Einstein setting on the Einstein Setup page. Second, enabling the platform does not activate agents: an agent reaches end users only when someone activates it in Agentforce Builder. Use that distinction to calm the security team, then use it to push for a written agent-activation policy.
The same pattern shows up in Sales. Automated field updates for Agentforce Pipeline Management are now auto-enabled. The agent reads recent voice and video call transcripts and suggests updates to Next Step and Stage on opportunities. Orgs qualify with the Agentforce for Sales licence and at least 10 call transcripts, and auto-enablement runs November 14 through November 16, 2026. If your client's reps have never been told this exists, tell them before they see it.
Demo scripts that land
These are the Winter '27 features that hold up in a live demo, ordered by how fast they make the point.
Forecasting Agent. It analyses pipeline changes, flags deals that put quota at risk, and helps reps complete their forecast submission. It starts rolling out October 19, 2026, is configured on the Forecast Settings page, and needs the Agentforce for Sales add-on or Agentforce 1 Edition. Demo it against a real forecast hierarchy, not sample data.
Deal Insights. It processes call transcripts plus opportunity and email signals to flag objections, competitor risk and engagement health. It rolls out in early November 2026, is switched on through Salesforce Go, and its AI-powered insights need an Agentforce edition or the Agentforce add-on. Pair it with Momentum's Executive Briefs, a scheduled summary of team conversation insights delivered in Slack, and the sales-leadership story writes itself.
Agentic Swarming. Service teams get AI-assisted resolution and a single view of Slack conversations and CRM data on a case. It is configured under Setup, Swarming, "Use Agentic Swarming in Slack," and users need the Slack Service User permission set.
Flow Test Mode. Help now lists it as generally available (it started as a beta in September). Admins save reusable test scenarios with assertions for autolaunched and record-triggered flows, and mock outputs stand in for actions and subflows. For clients who distrust automation they cannot test, this is the most persuasive admin demo in the release.
Multi-Agent Orchestration (GA). An orchestrator agent can now call other Agentforce agents in the same org as subagents. Salesforce's Top 10 goes further with Third-Party Agent Orchestration across A2A-compliant ecosystems, so agents from AWS, Azure or Google can join. Demo the in-org version. Treat the cross-vendor version as a roadmap conversation until you have built it yourself.
Contact center positioning
Every Service Cloud Voice conversation now needs a fork in it. Agentforce Contact Center brings telephony, routing and AI into one Salesforce product. Winter '27 adds Bring Your Own Carrier for more than 30 countries, automatic call recording redaction of card numbers and personal data, scheduled callbacks, and an In-Queue Experience flow. Partner Contact Center keeps the Amazon Connect model and adds Voicemail Drop, rep self-service phone numbers and an audit trail of voice call changes (a pilot).
Salesforce's Top 10 also lists Autonomous Scheduling with Agentforce Voice, which it says cuts 15-minute booking calls down to seconds. Field service clients will ask about it. The Field Service release notes cover a related Customer Outreach Scheduling agent for rebooking, reminders, confirmations and cancellations, but we found no Help note for Autonomous Scheduling itself, so confirm scope before you promise it.
Revenue Cloud and industry plays
Revenue Cloud is where Winter '27 removes objections rather than adding features.
- Large transactions. Quotes and orders can reach 15,000 line items, processed asynchronously, and CLM document generation handles up to 1,000 bundles.
- AI setup agents (all Beta). Agents set up Revenue Cloud in a new org in about 15 minutes, build a product catalog from plain language, set up pricing, and author configuration rules. Use them to shorten discovery workshops, not to replace solution design.
- Dynamic Revenue Orchestrator Read-Only permission set. Viewers can watch fulfilment pipelines without a paid seat. That is a direct licence saving you can put in a business case.
- Salesforce Contracts on Lightning Platform Starter or Plus. It previously needed a core CRM licence.
Field Service clients get a quieter shift: the Scheduling Console is now the default for new customers, who can no longer access the classic Dispatch Console. Existing customers keep access, but plan the move. Native mobile flows also change how flow screens look in the Field Service app, so budget a regression pass for custom mobile flows.
Migration projects to staff for FY27
Winter '27 fills the next 18 months with dated work. Put these in your account plans now.
- Integrations off legacy authentication. Salesforce moved the retirement of the OAuth username-password flow for connected apps from the Winter '27 release to February 20, 2027, and the user-agent flows retire the same day. The SOAP API
login()call in API versions 31.0 through 64.0 is scheduled to retire in Summer '27, and connected apps lose bug fixes and support in Summer '27 too. The target for all of it is an External Client App with a supported OAuth flow. Our External Client Apps migration guide covers the order of work. - Salesforce for Outlook. Its retirement date moved twice and now sits at January 30, 2027. The usual landing zone is the Outlook integration, with Einstein Activity Capture for sync, but confirm the replacement path in Help before you scope it.
- Lightning Sync. Its retirement moved to January 28, 2028, which gives Lightning Sync users a calmer runway for the same move.
- Salesforce to Salesforce. It retires in Spring '27 and has had no fixes or enhancements since Summer '26. Help names Partner Cloud, Data Cloud One, MuleSoft Anypoint Platform and MuleSoft for Flow as replacements.
- Tableau Agent V1. Agents built on the legacy V1 template stop working at the end of 2026. New agents must use the Analytics and Visualization V2 template.
- Einstein Bots to Agentforce Service Agent. The Upgrade Agent tool is generally available and leaves the bot in place while it builds the new agent, which makes a phased cutover easy to sell.
- Model reroutes. Salesforce is rerouting several model families on fixed dates, including GPT-4o and GPT-4.1 on April 14, 2027. Every prompt template and agent tied to a retiring model needs a retest.
Risk warnings for every client
These are the items that cause tickets if nobody warns the client first.
- Enable Profile Filtering is enforced. Users cannot view profile names other than their own unless they hold View All Profiles. Anyone testing with that permission will not see the problem, so test with login-as against a standard user.
- SOAP login() needs the Use Any API Auth permission from December 1, 2026. Salesforce enforces it on that date across production and sandboxes alike. Integration users built from stripped-down profiles are the exposed group. Check Login History for SOAP logins before the client finds out from a failed nightly job.
- Idle refresh tokens now expire after 30 days. Enforcement rolled through sandboxes from October 21 and production from November 4, 2026. Quarterly or seasonal integrations are the ones that fail quietly.
- Email verification exception ends December 1, 2026. The release update "Maintain Your Email Verification Exception" removes the Support-granted allowlists that switched off user email verification, and unverified users then cannot send email. Configure an authorized email domain and the new "Require Address Verification to Send Email" field first.
- WhatsApp charges. Service and utility messages inside the 24-hour window start consuming Salesforce Message Credits in early November 2026. Help gives November 1 on one page and November 2 on another. Messaging-heavy clients need a revised cost model either way.
- Commerce access on smaller editions. In Starter, Pro Suite and Freemium, B2B Commerce users without the Commerce Admin permission set lose access to store pages after the upgrade.
- Agent dashboards shift. Agentforce Observability recalculates Success Rate, changes metric names, and moves Quality Score to prompt-based evaluation. Warn anyone who reports agent KPIs to an executive.
Practice growth areas
The release points at four places to build capability now.
MCP and outside AI tools. Salesforce in Claude can now create and update records (Beta), with Lightning field validation, for clients on Claude Enterprise with the Salesforce MCP server connected. The CRM Analytics MCP Server (Beta) lets Claude, Cursor, GitHub Copilot and ChatGPT query governed analytics data over OAuth. Security review and permission design for these connections is new, billable work.
Agent Skills and Plugins. Salesforce's Top 10 says more than 100 prebuilt skills ship at launch and customers can publish their own to the same registry. Plug-ins bundle skills with MCP connectors and configuration. Practices that package repeatable skills will have something to sell beyond hours.
Data 360 zero copy. Microsoft OneLake sharing arrived in beta, Google BigQuery sharing now works in any region, and the Snowflake connector moved to a V2 with OIDC authentication. Architecture assessments that end in "copy the data" are now harder to defend.
Marketing operations. Marketing Planning and Operations brings planning hierarchies, cascading goals, tactic templates and Slack approvals, but only with Marketing Cloud Next Advanced. Qualify the edition before you scope it.
What this release means for consultants
Winter '27 changes the default posture of a Salesforce org. Agentforce is on unless someone turns Einstein off. Pipeline suggestions arrive from call transcripts unless someone governs them. Profile names disappear for standard users unless someone grants the permission. The clients who get value from this release are the ones whose partner walked them through those defaults before the upgrade weekend.
Start with the governance conversation, then demo Forecasting Agent and Flow Test Mode, then staff the integration work behind the December 1, 2026 and February 20, 2027 dates. For the admin-level detail, read Winter '27 for Admins. For the platform view, see the Architect article and the Developer article. The Top 10 Winter '27 features is the short list to send a client sponsor.