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

SAP shipped the Q1 2026 release for Sales Cloud V2 a couple of weeks ago. We’ve had our hands on it since day one. Three things actually matter: Joule Studio is GA, deal intelligence got real risk scoring, and the forecasting views were rebuilt from the ground up. Everything else (mobile, CTI, guided selling) is incremental. Still worth covering, because some of it is genuinely neat.

This is the first post in a quarterly series. The idea: we break down what shipped, what it means if you’re running this thing in production, and what to do about it. We implement Sales Cloud V2 across Switzerland, Italy, Austria, and Estonia. Ergo, these aren’t rewritten release notes. They’re field notes from the people who configure, deploy, and support this platform for a living.

TL;DR: Q1 2026 brings Joule Studio general availability (build custom AI agents), proper 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 thing that’s happened to Sales Cloud V2 since launch. Joule Studio, SAP’s agent builder, moves from limited availability to GA (SAP Community, SAP UX Q1/2026 Update Part 1).

Let me give you some context on why this is a big deal. Before Joule Studio, Joule was a copilot. You asked it things. It answered. You asked it to draft an email. It drafted one. Solid, but reactive. We wrote about the details in our Joule hands-on guide.

Joule Studio is a different animal. You build custom AI agents that run multi-step workflows on their own. They connect Sales Cloud V2, S/4HANA, third-party systems, and external data sources in a single flow. This is the shift from “AI copilot” to “AI workforce” that SAP has been telegraphing since Sapphire 2025. We unpacked the broader picture in what agentic AI means for sales.

What you can build today

Delivery timeline emails. A deal hits “Won” stage. An agent 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. We built a prototype of this in about two days for a client last month. Not complicated if your product master data is in decent shape.

Pre-call briefings. Before a scheduled meeting, an agent compiles 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. Our reps were spending 10-15 minutes clicking through four systems before calls. This collapses that to zero.

Lead enrichment and scoring. An agent 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. We tested this with a client’s existing Dun & Bradstreet subscription and the results were spot on.

What to know before you start

Joule Studio agents require the AI Foundation licence on BTP: 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 steps, triggers, and data connections. No code needed for standard integrations, though custom API calls are supported for edge cases.

Here’s the honest bit. 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 you invest time in agent development. We’ve seen this trip up two clients already during the limited availability phase. A stitch in time saves nine here.

My advice: pick one high-value, repetitive workflow. Pre-call briefings are a good starting point. Build your first agent there, learn the platform on something contained, then go after the complex multi-system orchestrations.

Enhanced Deal Intelligence

Deal intelligence in Sales Cloud V2 has been getting better in small increments since launch. Q1 2026 is the first release that feels like a proper step forward. More granular risk scoring. Activity-based warnings that actually mean something.

What changed

Activity-based risk signals. The system now monitors engagement patterns at the deal level and flags specific risks. No customer contact in 14 days on a deal scheduled to close this quarter? Warning. Your primary contact hasn’t opened any of your last three emails? That surfaces too. These aren’t based on AI guesswork alone. They’re rooted in concrete activity gaps that correlate with deal slippage in historical data. Prima vista it seems simple, but the execution is crisp.

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

Pipeline hygiene recommendations. More subtle but practically useful. The system surfaces specific recommendations for cleaning up your pipeline: deals stuck in one stage for too many days, opportunities with stale close dates, prospects with no scheduled next steps. This moves pipeline reviews from gut feel to data-driven conversations. I reckon most sales managers will find this more immediately useful than the AI scoring.

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

Why this matters

Most CRMs tell you what happened. A few tell you what might happen. The good ones tell you what to do about it. This update puts Sales Cloud V2 solidly in that 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 pushed twice already”), the coaching conversation writes itself.

I showed this to a sales director at one of our Swiss clients last week. Her reaction: “finally.” The proof is in the pudding, I suppose.

Forecasting Improvements

Forecasting in Sales Cloud V2 has been functional but, let’s be fair, not flexible enough. Q1 2026 addresses this properly.

Redesigned views

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

Multi-level rollup

Better support for hierarchical forecasting: rep rolls up to manager, manager to VP, VP to CRO. Each level can apply adjustments, and the system tracks the delta between the bottom-up number and each level’s adjusted figure. Not revolutionary. But the execution is cleaner than what was there before, and for organisations with 3+ management layers, this was a real pain point.

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: timestamp, user, original value, adjusted value, reason. This creates the audit trail finance teams have been asking for. “Why did the Q2 forecast drop by CHF 400K between Monday and Friday?” You can now answer that with specific, traceable data. Neat feature. We’ve had three clients request exactly this in the past year.

Integration with deal intelligence

The forecasting views now pull risk indicators from the 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.” In practice, this is where deal intelligence stops being a nice-to-have and becomes genuinely operational.

Mobile and UX Updates

Sales Cloud V2 was built mobile-first, and each release keeps refining the field sales experience.

Faster load times. SAP has optimised initial load and navigation transitions on mobile. 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 full day of field work. One of our reps in the Ticino region noticed it immediately on his iPad.

Improved offline sync. For reps working in areas with dodgy 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 fixed with incremental sync improvements. We’ve confirmed this works with territories of up to about 2,000 accounts.

Quick-action cards. New configurable quick-action cards on the mobile home screen for common tasks: log a visit, create a follow-up task, update an opportunity stage. Admins configure which actions appear. Fewer taps between opening the app and getting work done. Simple idea, solid execution.

CTI Framework Enhancements

For teams running computer telephony integration with Sales Cloud V2, Q1 2026 brings improvements to the softphone embedding framework. We’ve covered CTI integration architecture in depth before. Here’s the update.

Better softphone embedding. The shell plug-in framework for CTI widgets now supports more layout options and better state management. The softphone panel maintains its state across page navigations within Sales Cloud V2, so an active call doesn’t lose context when a rep moves from an account to an opportunity. Sounds minor. It was a genuine annoyance for our clients running live calls.

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

Incremental stuff, but it reduces 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 added templates for common B2B scenarios: new business acquisition, account expansion, and competitive displacement. They’re not meant to be used as-is. They’re starting points you adapt to your own methodology. But they cut the setup time for a new team significantly. Fair enough approach from SAP. Don’t reinvent the wheel if you don’t have to.

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 “technical validation” sits at 40%, that tells you something about where your process is breaking down (or where the playbook doesn’t match reality). We’ve been asking for this since V2 launched. Glad it’s here.

What This Means for Your Team

What you should actually do depends on where you are right now.

If you’re already on V2. These updates arrive automatically through SAP’s zero-downtime quarterly release. Nothing to install, nothing to migrate. My recommendation: prioritise Joule Studio. Pick one workflow (pre-call briefings or lead enrichment are good candidates) and build a pilot agent. Then sit down with your sales managers and review the new deal intelligence signals. Work them into your weekly pipeline reviews. The forecasting changes are worth a look too, especially if your current setup relies on spreadsheet overlays. You know who you are.

If you’re still on V1 (C4C). Nota bene: none of these capabilities will reach Cloud for Customer. V1 is in maintenance mode. Every quarter, the gap between V1 and V2 widens, and it’s getting harder to justify staying put. 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 figure out the timeline and effort.

If you’re evaluating Sales Cloud V2. The quarterly release cadence is one of V2’s structural advantages over competitors shipping annual major releases. You’re always on the latest version. The features landing today (particularly Joule Studio and the deal intelligence improvements) are de facto differentiators that aren’t available in V1 or in most 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 next. Based on the 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. I’m particularly interested in what happens with the quote-to-cash pieces. That’s where a lot of our clients feel the friction today.

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 people who actually implement this, subscribe to our newsletter or follow us on LinkedIn.