What's New in SAP Sales Cloud V2 — Q1 2026 Update

SAP’s Q1 2026 release for Sales Cloud V2 landed this month. Three changes stand out: Joule Studio hits general availability, deal intelligence gets sharper risk scoring, and forecasting views were redesigned from the ground up. The rest is incremental — mobile, CTI, guided selling — but worth knowing about.

This is the first in a quarterly series where we break down what actually shipped, what it means for your team, and what to do about it. We implement Sales Cloud V2 for customers across Switzerland, Italy, Austria, and Estonia. These aren’t release notes — they’re practitioner notes.

TL;DR: Q1 2026 brings three headline features: Joule Studio general availability (build custom AI agents), enhanced deal intelligence with activity-based risk scoring, and redesigned forecasting views with multi-level drill-down. Plus incremental improvements to mobile performance, CTI embedding, and guided selling playbooks. If you’re on V2, these arrive automatically. If you’re on V1, none of this is coming your way.

Joule Studio — General Availability

This is the biggest update since Sales Cloud V2 launched. Joule Studio, SAP’s agent builder, moves from limited availability to GA (SAP Community, SAP UX Q1/2026 Update Part 1).

To understand why this matters, consider what Joule was before: a copilot. You asked it questions. It answered. You asked it to draft an email. It drafted. Useful, but reactive. We covered the details in our Joule hands-on guide.

Joule Studio changes the model. You now build custom AI agents that execute multi-step workflows autonomously — connecting Sales Cloud V2, S/4HANA, third-party systems, and external data sources in a single agent flow. This is the shift from “AI copilot” to “AI workforce” that SAP has been telegraphing since Sapphire 2025. We unpacked the broader implications in what agentic AI means for sales.

What you can build today

Delivery timeline emails. An agent that, when triggered by a deal reaching “Won” stage, pulls stock availability from S/4HANA, calculates estimated delivery dates based on the customer’s ship-to address, and drafts a personalised confirmation email with the timeline. The rep reviews and sends — the research and drafting happen automatically.

Pre-call briefings. Before a scheduled meeting, an agent compiles the account’s open opportunities, recent service tickets, last quarter’s order history from S/4HANA, and any competitive mentions from call notes. It produces a one-page briefing delivered to the rep’s inbox or displayed in the opportunity sidebar. No more spending 10 minutes clicking through four systems.

Lead enrichment and scoring. An agent that takes a newly created lead, queries external firmographic data, matches it against your ideal customer profile parameters, and assigns a qualification score. High-scoring leads get auto-routed to the right territory owner with context already attached.

What to know before you start

Joule Studio agents require the AI Foundation licence on BTP — the same prerequisite as basic Joule functionality. If you’ve already activated Joule, the infrastructure is in place. The agent builder itself uses a low-code visual canvas for defining steps, triggers, and data connections. You don’t need to write code for standard integrations, though custom API calls are supported for edge cases.

Data quality is the real gating factor. Agents are only as good as the data they connect to. If your S/4HANA product master is a mess, the delivery timeline agent will produce garbage. If your call notes are empty, the pre-call briefing agent has nothing to work with. We strongly recommend a data hygiene review before investing in agent development.

Our advice: pick one high-value, repetitive workflow — pre-call briefings are a good starting point — and build your first agent there. Learn the platform on something contained before attempting complex multi-system orchestrations.

Enhanced Deal Intelligence

Sales Cloud V2’s deal intelligence has been incrementally improving since launch. Q1 2026 brings a meaningful step forward with more granular risk scoring and activity-based warning signals.

What changed

Activity-based risk signals. The system now monitors engagement patterns at the deal level and flags specific risks. If there’s been no customer contact in 14 days on a deal scheduled to close this quarter, you get a warning. If the primary contact hasn’t opened any of your last three emails, that surfaces too. These aren’t based on AI inference alone — they’re based on concrete activity gaps that correlate with deal slippage in historical data.

Improved risk scoring models. The underlying scoring model now considers more signals: email engagement, meeting frequency relative to deal stage, stakeholder breadth (are you only talking to one person?), and deal velocity compared to your average. Each factor contributes to a composite risk score visible on the opportunity record and in pipeline views.

Pipeline hygiene recommendations. This is more subtle but practically useful. The system now surfaces specific recommendations for cleaning up your pipeline — deals that haven’t moved stages in X days, opportunities with stale close dates, prospects with no scheduled next steps. This moves pipeline reviews from “gut feel” to data-driven conversations between reps and managers.

Forecasting integration. At-risk deals now flow directly into the forecasting module, giving managers visibility into how much of their committed forecast sits on shaky ground. More on this in the forecasting section below.

Why this matters

Most CRM systems tell you what happened. A few tell you what might happen. The best ones tell you what to do about it. This update pushes Sales Cloud V2 further toward the third category. When a manager opens their pipeline view and sees three deals flagged as high-risk with specific reasons — “no customer meeting in 21 days,” “single-threaded into a mid-level contact,” “close date already pushed twice” — the coaching conversation writes itself.

Forecasting Improvements

Forecasting in Sales Cloud V2 has been functional but not particularly flexible. Q1 2026 addresses this with a redesigned interface and new structural capabilities.

Redesigned views

The forecasting UI has been rebuilt with drill-down support along three dimensions: territory, product line, and time period. Previously, you could view a forecast rollup by owner or by period. Now you can slice by any combination — “show me the DACH territory forecast for our CPQ product line, broken down by month.” This is table stakes for larger sales organisations, and V2 now delivers it without requiring custom reports.

Multi-level rollup

Better support for hierarchical forecasting: rep rolls up to manager, manager rolls up to VP, VP rolls up to CRO. Each level can apply adjustments, and the system tracks the delta between the bottom-up number and each level’s adjusted figure. Nothing revolutionary, but the execution is cleaner than what was available before.

Inline adjustments with audit trail

Managers can now adjust forecast numbers inline — directly in the forecasting view — with a required comment explaining the adjustment. Every change is logged with timestamp, user, original value, adjusted value, and reason. This creates the audit trail that finance teams have been asking for: “Why did the Q2 forecast drop by CHF 400K between Monday and Friday?” You can now answer that question with specific, traceable data.

Integration with deal intelligence

The forecasting views now pull risk indicators from the enhanced deal intelligence module. A committed deal flagged as high-risk shows a visual indicator in the forecast, and managers can filter to see only at-risk committed revenue. This closes the gap between “here’s what we committed” and “here’s what we’re likely to actually close.”

Mobile and UX Updates

Sales Cloud V2 was built mobile-first, and each release continues to refine the experience for field sales teams.

Faster load times. SAP has optimised the initial load and navigation transitions on mobile devices. In our testing, the improvement is noticeable on list views and opportunity detail pages — roughly 20-30% faster rendering compared to last quarter. Not dramatic, but it compounds across a day of field work.

Improved offline sync. For reps working in areas with unreliable connectivity — warehouses, factory floors, rural customer sites — the offline sync mechanism now handles larger data sets more reliably. Previously, syncing a large territory’s worth of data after an extended offline period could stall. That’s been addressed with incremental sync improvements.

Quick-action cards. New configurable quick-action cards appear on the mobile home screen for common tasks: log a visit, create a follow-up task, update an opportunity stage. Admins can configure which actions appear. The intent is to reduce the number of taps between opening the app and completing the most frequent field activities.

CTI Framework Enhancements

For teams using computer telephony integration with Sales Cloud V2, Q1 2026 brings improvements to the softphone embedding framework. We’ve covered CTI integration architecture in detail previously. Here’s what changed.

Enhanced softphone embedding. The shell plug-in framework for embedding CTI widgets now supports more layout options and better state management. The softphone panel can maintain its state across page navigations within Sales Cloud V2, meaning an active call doesn’t lose context when a rep navigates from an account to an opportunity.

Better call logging. Automatic activity creation from call events has been streamlined. Call duration, direction (inbound/outbound), and outcome are now captured with less manual intervention. The mapping between telephony events and Sales Cloud V2 activity types is more configurable.

These are incremental improvements, but they reduce the integration effort for teams deploying CTI — whether using our Engage CTI product or a third-party adapter.

Guided Selling Updates

Guided selling — Sales Cloud V2’s playbook engine for standardising sales processes — gets two practical improvements.

New playbook templates. SAP has added templates for common B2B scenarios: new business acquisition, account expansion, and competitive displacement. These aren’t meant to be used as-is — they’re starting points that you adapt to your methodology. But they dramatically reduce the time to set up guided selling for a new team compared to starting from a blank canvas.

Step completion tracking and analytics. Managers can now see which playbook steps reps complete, skip, or abandon. If your “discovery” step has a 90% completion rate but your “technical validation” step sits at 40%, that tells you something about where your process is breaking down — or where the playbook doesn’t match reality.

What This Means for Your Team

The practical implications depend on where you are in your Sales Cloud journey.

If you’re already on V2. These updates arrive automatically through SAP’s zero-downtime quarterly release model. There’s nothing to install, nothing to migrate. Our recommendation: prioritise evaluating Joule Studio. Pick one workflow — pre-call briefings or lead enrichment — and build a pilot agent. Then review the enhanced deal intelligence signals with your sales managers and incorporate them into your weekly pipeline reviews.

If you’re still on V1 (C4C). None of these capabilities will reach Cloud for Customer. V1 is in maintenance mode. Every quarter, the gap between V1 and V2 widens. If you haven’t started planning your migration, this is another data point for the business case. We’ve laid out the C4C to V2 migration strategy and can help you assess the timeline.

If you’re evaluating Sales Cloud V2. V2’s quarterly release cadence is one of its structural advantages over competitors with annual major releases. You’re always on the latest version. The features shipping today — particularly Joule Studio and the deal intelligence improvements — are competitive differentiators that aren’t available in V1 or in many competing platforms.

Wherever you are, we’re here to help. Talk to our SAP CX team about what these updates mean for your specific situation.

What’s Next: Q2 2026

We’ll publish the Q2 2026 update in June, covering whatever SAP ships in the next quarterly release. Based on SAP’s published roadmap and what we’re hearing at customer advisory events, expect continued investment in Joule Studio agent templates, deeper S/4HANA integration for quote-to-cash scenarios, and further analytics improvements.

This is the first post in our quarterly SAP Sales Cloud V2 update series. If you want to stay current with what’s shipping and what it means for practitioners, subscribe to our newsletter or follow us on LinkedIn.