Salesforce Winter '27 Highlights

Keep Household Names Accurate Without the Manual Cleanup

A household groups the people who give, attend, and receive services together. Its name is what appears on acknowledgments and mailings, so when a family changes through marriage, divorce, or a new member, somebody has to remember to rename the record. Usually, nobody does, and an outdated name goes out in front of a donor.

Automatic Household Naming hands that job to Salesforce. You set the naming pattern once, and the system monitors membership changes and updates the name in real time. It maintains greetings the same way, and you can flag individual households to leave alone if you would rather name them yourself. What disappears is the recurring cleanup work and the awkward letter addressed to a family that no longer exists.

See the Entire Recruitment Funnel in One Dashboard

Every institution has recruitment data. It just lives in different places: inquiries here, applications there, enrollment somewhere else. Seeing the whole path as one funnel, with the drop-off between each step visible, has generally meant building that reporting yourself.

The new Recruitment and Admissions Performance Center gives you that view out of the box, tracking volume, conversion rates, and how long students sit at each stage across all six steps from Suspect through Registered. Enrollment teams can see which stages are on track and where outreach will actually move the number. One planning note: the dashboard runs on Tableau Next and Data 360, so confirm you have those licenses and the right permission sets in place before you build a strategy around it.

Let Constituents Apply for Multiple Benefits in One Application

A family that qualifies for both energy assistance and food assistance has traditionally filled out two applications, retyped the same income and household details twice, and often missed a program entirely because nobody told them to apply.

Agentforce Public Sector now supports one combined application across programs. It pre-fills what the constituent has already given you, checks their information against eligibility rules as they go, and reshapes itself mid-application, hiding fields and reordering steps. Hence, people only complete the forms for programs they actually qualify for. Authorized representatives can apply on someone's behalf. Two things to verify before scoping: the LIHEAP and SNAP eligibility rules that ship are samples rather than production logic, and representative access carries its own licensing requirements.

Preview Records From a Report Without Losing Your Place

Everyone knows the pattern. You are working through a report, you click into a record to check one field, and now you are three tabs deep with your filters gone. Getting back to where you were costs more time than the check did.

Record preview opens record details in a side panel, while your report filters, columns, and place in the list all stay put. A fundraiser reviewing a report of lapsed donors can move down the list, checking giving history without ever leaving the report. Worth being clear about the status: this one is beta, which means Salesforce can still change it, and it comes with beta terms, so enjoy it in a sandbox before you build a process on it.

Remove the Page Layout Barriers to Inline Editing in List Views

Editing records directly from a list view is the fastest way to clean up a batch of data, but two longstanding restrictions have always gotten in the way. You could only edit fields that appeared on the page layout, and any list containing more than one record type turned editing off entirely.

Winter '27 adds two optional settings that lift both limits. Users can edit any field they have access to, whether or not it sits on the layout, and mixed record types no longer block editing. Both are off by default, so nothing changes until an admin turns them on. Do that deliberately: once layout restrictions come off, field and object permissions are the only things governing who can change what, so it is worth auditing access first.

Run a Screen Flow Against Every Record You Select

A screen flow is a guided, step-by-step process you build without code, and until now, it has operated on a single record at a time. Handling fifty records meant running it fifty times or asking a developer to build something custom.

Now you can attach a screen flow to a mass action on a list view or a related list, select the records you want, and run the flow once against all of them. Pick twenty volunteers and log their hours in one pass. Select a batch of pledges and update them together. This is the kind of change that quietly removes a category of custom development, since bulk update tools that once required a developer can now be configured.

Handle Bigger Datasets With Higher Processing Limits

Every automation in Salesforce gets a fixed amount of working memory, called a heap. Exceed it, and the process fails outright, which is why so much custom code is written to chop work into small pieces purely to stay under the ceiling.

That ceiling went up meaningfully. Processes that run while a user waits go from 6 MB to 10 MB, and background processes go from 12 MB to 25 MB. It turns on automatically when your org upgrades, so there is nothing to enable. One caveat for whoever maintains your code: if you build against the new limits in a sandbox and deploy to production before production upgrades, it will fail there. Salesforce provides a setting to hold sandboxes to the old limits until the versions line up.

Stop Losing Manual Shares When Records Change Hands

Sometimes, you grant one specific person access to a specific record outside your normal sharing rules. That is a manual share, and it is the standard workaround for accessing your setup when it is not otherwise covered.

Here is the behavior that has burned admins for years: when the record's owner changed, Salesforce deleted those manual shares, and the people who depended on them lost access with no warning. Winter '27 adds a setting that keeps manual shares through an ownership transfer. It is off by default, and the choice deserves a real conversation. Keeping shares means fewer people mysteriously losing access, and also means access can linger after it should have ended.

Bring Lightning Reports Into Your Experience Cloud Sites

Experience Cloud sites, the portals you build for donors, volunteers, partners, or students, come in two flavors. The older framework is Aura, and the faster modern one is called LWR. LWR has been the recommended choice for new builds for a while, but it could not display Lightning reports, so anyone needing to show a report in a portal was stuck with the old framework.

That gap is closed. A new component drops a Lightning report onto an LWR page, where users can build charts and tables, apply conditional formatting, and edit records inline without leaving the portal. Dashboards get the same treatment. Both are beta for now, but for anyone weighing a move off Aura, this removes one of the last real reasons to stay put.

Spot Deal Risk Directly in Your Pipeline Forecast

A pipeline forecast sums your open opportunities into a projected total. That number is only as honest as the deals behind it, and judging whether a deal is actually healthy has meant leaving the forecast to dig through activity history and call notes.

New columns bring that context into the forecast itself. Reps and managers can see deal risk alerts, methodology scores, contact insights, and activity heatmaps right alongside the numbers and choose which columns they want to see. Forecast accuracy is not really a reporting problem; it is a qualification problem. Putting risk signals next to the projection prompts the uncomfortable conversation during the pipeline review rather than after the quarter closes.

Write Repeating Content Once With Knowledge Blocks

Knowledge articles are the help content that your team and your constituents search for when they need an answer. When the same paragraph, a legal disclaimer, a refund policy, and an office address appear in two hundred articles, it has been copied two hundred times. Changing it is a find-and-replace project with real compliance exposure.

Knowledge Blocks let you write that content once and drop it into any article as a locked block. Publish a new version and every article using it updates automatically, with full version history showing who changed what and when. If you have Agentforce answering questions from your knowledge base, there is a bonus: content that stays consistent produces answers that stay consistent.

Personalize Every Channel, Not Just Email

Personalization scripting is what makes a message adapt to the person receiving it by pulling in a name, a last gift amount, or an event date, and swapping content based on your data. In Salesforce, that means two scripting languages, AMPScript and Handlebars, and until now, they have only worked in email.

Winter '27 extends to SMS, WhatsApp, RCS, in-app messages, and push notifications. Marketers type the expressions right into the text area of each channel builder and reference the same data they already use in email. For a nonprofit running text-based giving campaigns, that is the difference between a generic appeal blast and a message that acknowledges what someone gave last year. It requires the Salesforce Foundations add-on.

Let Buyers Rebuild a Repeat Order From a Saved Template

B2B buyers are rarely browsing. They are reordering, often the same configured set of products every month, and rebuilding that cart by hand each time is friction that helps nobody.

Order templates let a buyer save a single product or an entire cart and reuse it later to repopulate the cart in one step. The template retains details that are tedious to redo, including bundle options, quantities, and subscription selections, and a buyer can combine several templates into one order. New stores get this automatically. Existing stores need the components added to the product, cart, navigation, and profile pages. Reorder friction shows up directly in revenue, so this tends to pay for the setup time quickly.

Sync Very Large Quotes Without Timing Out

When a quote syncs to an opportunity, Salesforce copies the quoted line items onto the opportunity so your pipeline reflects what you actually proposed. On a small quote, this is instant. On a quote with thousands of lines, the process runs while the rep waits, and it could time out before finishing.

Revenue Management now handles quotes with up to 15,000 line items by moving the sync to the background, so the rep can keep working while the calculation finishes on its own. It covers both standard and large quotes and includes related improvements for generating documents from very large quotes with deeply nested product bundles.

Book Multiday Appointments Without Workarounds

Some fieldwork does not fit into a day. A turbine overhaul or a solar installation runs for a week. Still, Field Service scheduling has treated appointments as single-day events, so dispatchers relied on workarounds to get long jobs onto the schedule at all.

Now, scheduling and optimization fully support appointments that span multiple days, including arrival window commitments, and the optimization engine can shift multiday work to close gaps rather than lock it in place after the first assignment.

Two practical notes: that optimization behavior needs to be configured rather than just appearing, and the scheduling search looks 30 days out, so a job must fit entirely inside that window to show up as an available slot. The payoff is fewer visits per site and lower travel costs on exactly the jobs where those costs hurt most.

Cozy Up with Winter '27

Winter '27 brings plenty to keep your team warm this season, from in-report record previews to reusable knowledge blocks and higher processing limits for bigger datasets. Keep your eye on the calendar to see what's in store for new Salesforce features this season!

For more information on the release, please reference the Salesforce Winter '27 Release Notes.

If you have any questions about Salesforce or would like to see any of the implementations in your own Salesforce organization, please get in touch with Mission in Motion. We would be happy to help you keep the momentum going all winter long!