Salesforce's Spring '26 release is here. As a Salesforce implementation partner, what matters to us — and to our clients — isn't always what's new. It's what will materially affect daily operations inside Salesforce six, 12, and 18 months from now.
This article isn't intended to be a comprehensive overview of everything in the release. Instead, we're focusing on the meaningful (and potentially overlooked) features that improve workflows, retirements that require planning, and shifts that change how your organization operates.
Service Cloud updates
Case Timeline
Salesforce has offered Timeline as a component within Industries products (Financial Services Cloud, Health Cloud, etc.) for viewing related records in a consolidated, chronological feed. Spring '26 extends this capability to Case objects for broader Service Cloud implementations.
Historically, service reps spend too much time reconstructing case history, jumping between emails, chats, notes, and activity feeds to figure out what happened before they can decide what to do next.
Case Timeline consolidates everything into a single chronological view: emails, chats, messages, owner changes, escalations, and SLA events. Key moments are marked as milestones so reps can see the full story at a glance.
Why it matters: Faster context means faster resolution. When reps aren't piecing together fragmented data, they can focus on solving the problem. But this requires intentional setup and user enablement; it's not automatic.
What to consider: Map how many screens your reps currently touch during case resolution. If they're switching between records to understand context, Case Timeline creates a centralized timeline of events.
Real-time email translation
Global service teams have always faced a choice: hire multilingual staff, use external translation tools, or accept slower, less consistent support.
Spring '26 introduces real-time translation directly into the case feed. Incoming emails translate into the rep's language, and outgoing responses translate back to the customer's language before sending — all without leaving Salesforce. Custom terminology can also be applied to preserve business-specific language.
Why it matters: Teams can route cases by expertise and availability instead of language coverage, and reps can offer better, faster support.
What to consider: Before broad deployment, it’s worth identifying which language pairs matter most and testing translation quality with real support scenarios. Custom terminology is especially important for organizations with technical products or regulated language, and validating accuracy early helps verify translation supports quality outcomes, not just faster response times.
Sales Cloud updates
Sales Workspace (replacing Seller Home)
Salesforce has always shown sellers what exists: pipeline, tasks, and activities. But prioritization was left to the individual.
Sales Workspace surfaces priorities, insights, and recommended actions in a single workspace shaped by deal momentum, engagement signals, and objectives. Instead of interpreting dashboards, sellers now get guided daily execution.
Why it matters: This shifts coaching conversations from "Did you log your activities?" to "Do the system recommendations align with your judgment, and why?"
What to consider: Recommendations rely on clean data. Inconsistent engagement tracking or vague opportunity stages will surface quickly when recommendations don't match reality. Address data hygiene before rollout so the workspace builds trust and adoption, not skepticism.
Product sunsets
Salesforce to Salesforce retirement
Salesforce to Salesforce is officially on a retirement path and cannot be enabled in new organizations. Support ends in Summer ’26 and full retirement will arrive in Spring ’27.
Why it matters: Organizations still using Salesforce to Salesforce need to evaluate recommended alternatives: Partner Cloud, Data Cloud One, MuleSoft Anypoint, or MuleSoft for Flow. Each carries different architectural and operational implications.
What to consider: Start early. Replacing legacy integration patterns involves more than feature comparison. You'll need to plan for data mapping, vendor contracts, integration design, testing, and user adoption. Compressed timelines lead to reactive decisions instead of strategic ones.
Sales Dialer is unavailable to new customers
Sales Dialer is no longer available to new Salesforce customers. Telephony investment is now consolidated into Service Cloud Voice.
Why it matters: If you're currently using Sales Dialer, you're fine for now. But if you're evaluating telephony options or planning new implementations, Service Cloud Voice is the path forward.
What to consider: Evaluate Service Cloud Voice capabilities against your current telephony needs. Migration planning for existing Sales Dialer users should begin before forced timelines arrive.
Need help planning your Salesforce roadmap?
At Acquis, we help organizations evaluate Salesforce changes through an operational lens. We focus on the features that materially affect day-to-day work, the retirements that require real planning, and the decisions that will matter long after a release cycle ends.
If you're reassessing your Salesforce roadmap and want a practical perspective on where Spring '26 creates real leverage and where it introduces risk, connect with us.