Salesforce Winter ’27 has more to offer than another list of AI announcements. It can change how a rep follows up after a meeting, how a technician completes a job, how a customer uses a portal and how an admin maintains automation.
These are Adaptal’s top 10 picks for teams using Sales, Service, Field Service, Experience Cloud, Flow and AI. We reviewed Salesforce Ben’s roundups alongside Salesforce’s own coverage, then checked feature details against the release notes updated on 6 October 2026. This is our selection for business usefulness, not Salesforce’s official ranking.
Each item explains what changes, why we think it matters and the main availability conditions. The example screens use fictional data and are illustrative, not official product screenshots.
Jump to rollout and preparation Q&A
1. Bring Salesforce deal intelligence into Claude
For sales teams already working in Claude, this is one of the release’s most interesting changes. The Salesforce in Claude beta brings live deal health, pipeline risk and account context into the conversation through Salesforce MCP and a sales plugin. A manager can prepare for a pipeline review without first assembling a series of exports.
Why we picked it: it puts CRM context where people are already asking questions. For example, ask which opportunities need attention, then use the answer to guide a review with the account owners.
Review these records with the account owners. No Salesforce records have been changed.
Who gets it: Claude Enterprise is required, and administrators must configure the connection. This beta is read-only: it cannot create, update or delete Salesforce records. Rollout began on 15 September 2026. Release notes, printed pages 946–947.
2. Build cleaner, faster-to-understand flows
Flow Builder gets a combination that admins can use in real projects: named, collapsible groups and a Collection Filter Criteria resource. Groups organise a complicated canvas into logical stages. Collection filtering can replace a chain of loop, decision and assignment steps used to select matching records.
Why we picked it: a process that is easier to understand is easier to hand over and change. Think of an invoice follow-up flow with one clear group for selecting overdue invoices and another for the next action. Test performance with your own data rather than assuming every flow will improve equally.
Follow up overdue invoices
Select invoices to follow up Click to collapse
Who gets it: supported editions vary by feature. Groups roll out from Winter ’27; collection filtering rolls out from September 2026. Filtering uses a criteria resource with an Assignment, rather than a new standalone canvas element. Release notes, printed pages 262, 268–270.
3. Keep service plans in step with a changing case
Service Assistant for Case can regenerate the current dynamic plan step when a case field changes or a comment is added or edited. Previously, these updates were triggered only by new case emails. That matters when a service rep discovers new information halfway through resolving an issue.
Why we picked it: support is rarely a straight line. If a customer adds a diagnostic detail or the team changes a case field used for grounding, the current plan step can reflect the new context instead of leaving the rep with stale guidance.
Who gets it: this is Service Assistant for Case with dynamic plans, not every case page. Service Planner and Adaptive Experience add-ons are required alongside the specified Service AI entitlements and permissions. Listed availability starts 30 September 2026. Release notes, printed pages 1086–1087.
4. Automate appointment reminders and customer rebooking
The Field Service Customer Outreach Scheduling agent is available in the new Agentforce Builder. It supports rebooking and maintenance scheduling, with interactive reminders, confirmation requests and cancellation handling described in the release notes.
Why we picked it: dispatch teams spend time on routine appointment conversations as well as difficult scheduling decisions. A targeted outreach agent could handle the routine part while the team focuses on exceptions. Start with one appointment type and clear escalation rules.
Who gets it: supported Field Service and Foundations combinations, or Einstein 1 Field Service / Agentforce 1 Field Service editions. Availability is listed from 7 September 2026; reminder setup still requires manual configuration. Release notes, printed pages 376.
5. Give field technicians a better mobile Flow experience
Flows in the Field Service mobile app move to native architecture. Salesforce describes quicker loading, smoother navigation, stronger offline capabilities and lower storage use. Screens also take on the design of standard record forms, so technicians will notice changes to fields and controls.
Why we picked it: the quality of a field workflow depends on what happens at the customer site. A guided inspection or job-completion flow needs to remain usable when connectivity is poor. This is a practical improvement to test on the devices your team actually carries.
Who gets it: supported Android and iOS Field Service apps in Enterprise, Unlimited and Developer editions. Rollout is gradual across 264, 264.1, 264.2 and 264.3 patch releases, depending on the instance. Release notes, printed pages 382–383.
6. Turn meeting transcripts into suggested next steps
AI Suggested Actions brings a meeting summary, key decisions and recommended follow-ups to the event record in the Salesforce mobile app once a transcript is available. Recommendations can include sending requested material, updating an opportunity or arranging another meeting.
Why we picked it: the value of a good customer conversation is often lost in the follow-up. A rep leaving a meeting can review the suggested actions while the context is fresh. These are recommendations to review, not a promise that every action is executed automatically.
Who gets it: users need Einstein Conversation Insights and the Salesforce mobile app on iOS or Android. The notes list availability from 24 August 2026. Release notes, printed pages 789–790.
7. Make sales coaching consistent across the team
Call Coaching lets teams define competencies and review video calls against them. Ratings and notes sit with the call, creating a more structured basis for feedback. With Agentforce for Sales, AI evaluations can support that process.
Why we picked it: managers can focus on specific behaviours, such as discovery or agreeing a clear next step, instead of offering generic feedback. It is useful both for onboarding and for spotting skills the wider team needs to develop.
Who gets it: Einstein Conversation Insights is required. AI evaluations require Agentforce for Sales; eligible orgs without it can rate calls manually. Manual rating is not available in orgs with Agentforce for Sales, and submitted evaluations cannot be edited. Release notes, printed pages 950–952.
8. Put reports and dashboards inside LWR customer portals
Two beta components bring Lightning reports and dashboards to Lightning Web Runtime Experience Cloud sites. Users can work with reporting inside the portal instead of being sent elsewhere. These capabilities previously applied to Aura-based sites.
Why we picked it: a community can become a place where customers understand what is happening, not just where they submit a request. A service portal could surface open requests and booked visits, subject to the user’s report access and record sharing.
Your service requests
Who gets it: Professional, Enterprise and Unlimited editions and their LWR sites, with the relevant beta settings enabled. Validate external-user licences, permissions and sharing before exposing reports. Release notes, printed pages 238–239.
9. Inspect report records without losing your place
Record preview in Lightning reports opens record details in a side panel while keeping the report’s filters, columns and rows visible. A user can move through the records they are analysing without opening a growing collection of browser tabs.
Why we picked it: this is a broadly useful daily improvement. A sales manager investigating a pipeline report can check an opportunity and return to the same analysis. It is less dramatic than an AI agent, but it removes friction from work people already do.
Who gets it: beta in Lightning Experience for Enterprise, Performance, Unlimited and Developer editions. An admin enables record previews in Reports and Dashboards Settings; the report’s eye control then activates preview behaviour. Release notes, printed pages 237.
10. Let the Agentforce assistant help test agent changes
The Agentforce assistant beta can run previews in simulate mode, try variations and refine its proposed changes. You can also ask it to test changes you have made, including different personas and scenarios.
Why we picked it: building an agent is only part of the job. Knowing how it behaves when the conversation changes is just as important. Assisted testing can shorten the feedback cycle, while your team keeps responsibility for acceptance tests and activation.
Who gets it: supported editions with Foundations or Agentforce 1. This beta rolls out to upgraded Winter ’27 orgs from the week of 28 September 2026. Use representative business tests as well as the assistant’s previews. Release notes, printed pages 169–170.
Winter ’27: your questions answered
When is Winter ’27 being released?
Salesforce’s release announcement gives 12 October 2026 as the general availability date. Individual production instances upgrade on their own scheduled maintenance windows, and some features have separate rollout dates. As of this article’s 6 October review, do not assume every organisation has the same release status. Salesforce release announcement.
What is the rollout date for Australia, New Zealand, the UK or the US?
There is no single country-wide date you should use for planning. Find your instance in Setup > Company Information, then search for the instance or domain on Salesforce Trust and open Maintenance. Use the scheduled Winter ’27 window for your organisation. Check the time zone shown before converting it to Sydney, Auckland, London or your local US time zone. Your office location alone does not identify the instance or its schedule.
When do sandboxes get the release?
Salesforce lists preview-instance upgrades on 28–29 August 2026 and non-preview upgrades on 9–10 October 2026. The preview cutoff was 27 August. In Setup, check the sandbox’s Release Type. Refreshing can replace sandbox data and configuration, so preserve work before a refresh. Official sandbox instructions.
Will all ten features be available to us?
Not necessarily. Check each feature’s Where, When, Who and How sections in the release notes. Your edition, product licences, add-ons, permissions, application version and rollout status all matter. For example, Salesforce in Claude requires Claude Enterprise, while the Field Service features require the relevant Field Service setup.
Are these features included, or do they cost extra?
An upgrade does not give every customer every product entitlement. Some platform enhancements apply to supported existing editions; several AI features require extra licences or add-ons. Confirm your contract and any consumption charges with your Salesforce account team before budgeting or enabling a pilot.
What should we prepare before the upgrade?
Test your important flows, approvals, integrations, customer portal access and mobile processes in a suitable sandbox. Review Setup > Release Updates for required changes. Include restricted-user and error scenarios, brief the people who will see UI changes, and record who will check each critical workflow after the upgrade.
Does everything switch on automatically?
No. The release notes distinguish automatic changes from features that need administrator setup, permissions or activation. Report previews and LWR reporting betas, for example, need settings enabled. Make an enablement list so a platform upgrade is not confused with a completed feature rollout.
Should we use beta features with customers?
Treat beta as an evaluation decision, not a general availability guarantee. Review Salesforce’s beta terms, test access and behaviour, and choose a limited use case with an owner. Keep an alternative process for business-critical work until you are comfortable with the feature’s maturity.
Why can a colleague see a feature that I cannot?
Compare permissions, licences, org and app versions, settings and rollout status. Users in different orgs or on different mobile patches may see changes at different times. Native Field Service mobile flows explicitly roll out across several patches; a missing feature is not automatically a configuration error.
Where should we start if we can only tackle two improvements?
Adaptal’s recommendation is to choose one improvement for everyday users and one for the team maintaining Salesforce. Report previews plus a Flow cleanup are a useful starting point for many organisations. A field business may get more value from mobile Flow testing and appointment outreach. Select based on the problem you want to solve, not the size of the announcement.
Turn the release into a practical plan.
We can help identify the updates that fit your licences and processes, test them with your team and roll them out in a manageable order.
Discuss your Winter ’27 prioritiesSources and further reading
Technical details and availability were checked against the Salesforce release notes PDF updated 6 October 2026. Page numbers above are printed page numbers; PDF viewer positions are four pages later.
- Salesforce Winter ’27 release notes
- Salesforce’s release highlights and general availability announcement
- Salesforce Ben: Sales Cloud highlights
- Salesforce Ben: Service Cloud highlights
- Salesforce Ben: Admin highlights
- Salesforce sandbox preview instructions
Feature availability can change after publication. Examples and implementation recommendations are Adaptal’s own.
Need help with secure login? Read our Salesforce passkey guide for multiple devices, temporary codes and password managers.