Releases / Admins / Service Cloud

Service Cloud: Top 10 Salesforce Spring ’26 Features

By Mariel Domingo

Updated January 09, 2026

With 2025 coming to an end, Salesforce is already setting the tone for what’s next with the Spring ’26 release. Service Cloud (oh wait, it’s now Agentforce Service) sees a mix of usability improvements, updates, and new capabilities designed to help service teams deliver faster and more consistent support.

Here are the Spring ’26 Service Cloud features that admins and service teams should know about as they head into the new year.

1. Case Timeline

Starting strong with the new Case Timeline, a new way for agents to quickly understand what’s happened on a case without having to dig through related lists, feeds, or multiple tabs. Case Timeline presents key case events in a clear, chronological view, with events marked as milestones, helping agents see the full story at a glance.

This is especially useful for complex or long-running cases, where understanding previous interactions, updates, and changes is critical before taking the next action.

Source: Salesforce

Note that this change applies to orgs that have Industries Service Excellence enabled.

2. Quick Text in Case Comments

If the previous releases gave Case Comments rich text, this one extends Quick Text to Case Comments. It’s now easier for reps to add consistent and reusable responses without repetitive typing. Reps can insert predefined text snippets (including dynamic merge fields!) directly into case comments, helping standardize both internal notes and customer-facing communication.

For admins, this means better control over messaging and fewer variations in how cases are documented. Quick Text messages are centrally managed and can dynamically pull in data from the related case, such as the contact’s name, ensuring comments stay accurate and personalized.

To enable this, make sure “Rich Text for Case Comments” is already enabled from Setup > Support Settings, as well as Quick Text from Setup > Quick Text Settings.

3. View Original Case Attachments

If you’re a service rep who’s ever worked on a long-running case with plenty of back-and-forth and attachments along the way, you know how quickly it becomes difficult to figure out which files were part of the original issue. This new feature aims to remove that pain point.

Original case attachments (meaning any files added by the customer in the initial message when the case was created) are now easier to access directly from the case. This eliminates the need for reps to dig through the Attachments related list to find the files that matter most.

4. Rule-Based Milestone Pause

Spring ’26 introduces rule-based milestone pauses, removing the need for service reps to manually stop milestones when a case moves beyond their control.

Admins can now define rules that automatically pause milestones when specific conditions are met, such as when a case status changes to Waiting for Customer or Escalated. While a milestone is paused, the SLA timer stops running and resumes only when the pause conditions no longer apply. When the milestone unpauses, the target date is recalculated, resulting in more accurate SLA tracking and reporting.

Go to Setup > SLA Policies > select your milestone > configure from the Pause tab.

Note that SLA Policies will not appear in Setup unless you enable “Simplified SLA Setup” from Setup > Entitlement Settings.

5. Bidirectional Milestone Visibility

Milestones were largely isolated to individual records, which meant teams working on related or child cases, tasks, or escalations may lack visibility into how SLA or OLA timelines were tracked elsewhere. If a resolution involved multiple departments or external vendors, it was easy for milestones to drift out of sync or worse, go unnoticed.

Spring ’26 introduces bidirectional milestone visibility, allowing milestones to be viewed across parent, child, and related records. This provides real-time insight into milestone status wherever work is happening, making it easier for service teams, supporting departments, and partners to stay aligned on commitments and timelines.

To enable, just go to Setup > SLA Policies > select the option above for new milestones.

6. Service Setup and Service Setup Assistant Retirement

…but only for new orgs created in this release or later. 

Existing orgs will continue to have access to Service Setup and Asisstant, so there’s no immediate impact if you’re already relying on them.

That said, this change is a clear nudge toward using Salesforce Go instead. Like Service Setup and the Service Setup Assistant, Salesforce Go provides guided onboarding and setup support for new Salesforce orgs, offering a similar experience for getting Service Cloud up and running.

7. New Command Center for Service?

Gotcha! It isn’t really a new feature, but a rename. Omni-Channel Supervisor is now Command Center for Service. No tools or functionalities were removed, but Command Center for Service does offer a lot more, and is meant to be the ultimate visibility tool for support managers.

READ MORE: Service Cloud No More? Salesforce Unveils Agentforce Service at Dreamforce ’25

8. Smarter Call Routing and Automatic Voice Call Linking

Spring ’26 brings a pair of improvements for Service Cloud Voice users! Voice interactions are now more flexible and less manual thanks to Unified Routing transfers that can now be routed through an Omni-Channel Flow. This allows admins to use more advanced business logic  (such as skills, case context, or custom conditions) to determine where a call should be transferred. 

At the same time, Salesforce now automatically links VoiceCall records to their source records when outbound calls are initiated using Click-to-Dial, including from custom objects. Before this update, automatic linking was only available for a limited set of standard objects, forcing teams to rely on custom Flows or Apex to keep call data connected.

9. More Flexible and Branded Survey Experiences

There are several improvements to Salesforce Surveys, particularly for orgs that have Feedback Management – Starter or Feedback Management – Growth enabled. It’s now easier to capture feedback and present it in a more polished, on-brand way. 

Partially completed survey responses can now be saved for up to 999 days, a significant increase from the previous 15-day limit. Admins can configure this window anywhere between 1 and 999 days, giving customers far more time to return and finish a survey without losing their progress.

Building on this, partial survey responses from guest users are now saved automatically as well. Previously, only authenticated users benefited from this behavior, which meant feedback from external or anonymous respondents was often lost if they didn’t complete the survey in one sitting.

Finally, Spring ’26 introduces Custom CSS for surveys, allowing admins to go beyond the default Survey Builder styling. With Custom CSS, surveys can be fully aligned with brand guidelines by customizing fonts, colors, spacing, layouts, and icon styles. 

Source: Salesforce

10. Knowledge Maps (Generally Available)

Knowledge Maps are now generally available in Spring ’26, making it easier to organize knowledge articles into a clear, hierarchical structure. Instead of relying on flat lists or loosely connected articles, teams can group related content in a way that’s easier for both agents and customers to navigate.

Source: Salesforce

When you enable this, it creates Article Relationship records.

Summary

This release continues to refine the service experience by smoothing out everyday workflows like helping teams resolve cases faster, meet SLA commitments more accurately, and deliver more consistent support across channels. 

From better case visibility and smarter milestone management to improved voice routing and richer survey experiences, these updates aim to reduce manual effort while giving agents and managers the information they need at the right time. Which feature are you most excited to let your service teams use? Leave your answers in the comments below!

Read More

The Author

Mariel Domingo

Mariel is a Technical Content Writer at Salesforce Ben.

Leave a Reply