What's New in SAP Sales Cloud V2: Q1 2026 Update
Customer Engagement Executive, Spadoom AG
SAP shipped the first 2026 release for SAP Sales Cloud V2 in February, and we worked with it in customer tenants from the first weeks. Three changes mattered: the agent builder in Joule Studio became generally available, deal intelligence gained activity-based risk signals, and the forecasting views were reworked. Everything else (mobile, CTI, guided selling) was incremental, though some of it is useful in daily work. Our Joule navigator shows which Joule assistants are available and which SAP has only announced.
These are field notes rather than rewritten release notes: what shipped, what it means if you run V2 in production, and what to do about it. We implement Sales Cloud V2 for customers in Switzerland, Germany, Austria and Italy.
TL;DR: The Q1 2026 release made the Joule Studio agent builder generally available (build your own AI agents), added activity-based risk signals to deal intelligence and reworked forecasting with drill-down and tracked adjustments. Mobile performance, CTI embedding and guided selling playbooks improved incrementally. On V2, all of this arrives automatically; on V1 (C4C), SAP’s new AI such as Joule agents is not coming, because SAP’s innovation goes into V2.
Status note, September 2026: this post describes the release as we saw it in March 2026. The agent builder’s general availability is documented by SAP in the SAP Discovery Center. Feature scope and licensing have moved on since, so check SAP’s current Sales Cloud Version 2 documentation and the SAP Road Map Explorer before you plan around any detail below.
Joule Studio: General Availability
For Sales Cloud V2 users, this is the most important change since launch. The agent builder in Joule Studio, SAP’s tool for building AI agents, moved from limited availability to general availability. Which AI features SAP offers today, how they are licensed and where they already run in production is summarised on our SAP Business AI page.
Some context on why it matters. Before Joule Studio, Joule was a copilot: you asked, it answered; you asked for an email draft, it drafted one. Useful, but reactive. We described that side in our Joule hands-on guide.
Joule Studio works differently. You build agents that run multi-step workflows on their own and connect Sales Cloud V2, S/4HANA, third-party systems and external data in one flow. It is the shift from “AI copilot” to “AI workforce” that SAP had been signalling since Sapphire 2025. We covered the broader picture in what agentic AI means for sales.
What you can build
Delivery timeline emails. A deal moves to “Won”. An agent pulls stock availability from S/4HANA, estimates delivery dates for the customer’s ship-to address and drafts a confirmation email with the timeline. The rep reviews and sends. A prototype of this is a matter of days, not weeks, 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 orders from S/4HANA and any competitor mentions from call notes, and produces a one-page briefing in the rep’s inbox or in the opportunity sidebar. It replaces the minutes a rep spends clicking through several systems before each call.
Lead enrichment and scoring. An agent takes a new lead, queries external company data, compares it with your ideal customer profile and assigns a qualification score. High-scoring leads are routed to the right territory owner with the context attached. If you already subscribe to a data provider such as Dun & Bradstreet, the agent can use that data.
What to know before you start
Joule Studio agents need the Joule and SAP BAIP (formerly BTP) entitlements your scenario requires; clarify licensing with SAP before you plan, because the packaging has changed more than once. The agent builder itself uses a low-code canvas for steps, triggers and data connections. Standard integrations need no code; custom API calls are possible for edge cases.
The real gating factor is data quality. Agents are only as good as the data they read. If your S/4HANA product master is a mess, the delivery timeline agent will produce nonsense. If your call notes are empty, the pre-call briefing has nothing to work with. Run a data hygiene review before you invest in agent development; in our projects, this is where early agent pilots stumbled.
My advice: pick one valuable, repetitive workflow. Pre-call briefings are a good start. Build your first agent there, learn the platform on something contained, then move to complex multi-system orchestration.
Enhanced Deal Intelligence
Deal intelligence in Sales Cloud V2 had improved in small steps since launch. Q1 2026 was the first release that felt like a real step forward: more granular risk scoring and activity-based warnings that mean something.
What changed
Activity-based risk signals. The system watches engagement at deal level and flags specific risks. No customer contact in 14 days on a deal due to close this quarter? Warning. Your main contact hasn’t opened your last three emails? That surfaces too. The signals are based on concrete activity gaps, not on AI guesswork alone. Simple in principle, and well executed.
Improved risk scoring. The model takes more signals into account: email engagement, meeting frequency relative to deal stage, stakeholder breadth (are you single-threaded into one person?) and deal velocity compared with your average. Each factor feeds a composite risk score on the opportunity and in pipeline views.
Pipeline hygiene recommendations. Less visible but practical. The system recommends specific clean-ups: deals stuck in one stage too long, opportunities with stale close dates, prospects without a next step. Pipeline reviews move from gut feeling to data. Many sales managers will find this more immediately useful than the AI scoring.
Forecasting integration. At-risk deals flow into the forecasting module, so managers can see how much of the committed forecast rests on shaky ground. More on this below.
Why this matters
Most CRMs tell you what happened. Some tell you what might happen. The good ones tell you what to do about it, and this update moves Sales Cloud V2 into that third group. When a manager opens the pipeline 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”), the coaching conversation writes itself.
Forecasting Improvements
Forecasting in Sales Cloud V2 had been functional but not flexible enough. Q1 2026 addressed that.
Reworked views
The forecasting UI now supports drill-down along territory, product line and time period. Before, you could view a rollup by owner or by period, and that was it. Now you can combine them: “show me the DACH forecast for our CPQ product line, by month.” Larger sales organisations need this, and V2 now delivers it without custom reports.
Multi-level rollup
Hierarchical forecasting improved: rep to manager, manager to VP, VP to CRO. Each level can apply adjustments, and the system tracks the difference between the bottom-up number and each level’s adjusted figure. Not revolutionary, but cleaner than before, and a real relief for organisations with three or more management layers.
Inline adjustments with audit trail
Managers can adjust forecast numbers inline, in the forecasting view, with a mandatory comment. Every change is logged: timestamp, user, original value, adjusted value, reason. That is the audit trail finance teams keep asking for. “Why did the Q2 forecast drop by CHF 400K between Monday and Friday?” now has a traceable answer. Customers have asked us for exactly this.
Integration with deal intelligence
The forecasting views pull risk indicators from deal intelligence. A committed deal flagged as high risk shows an indicator in the forecast, and managers can filter for at-risk committed revenue. That closes the gap between “what we committed” and “what we will likely close”, and it is where deal intelligence becomes part of daily operations.
Mobile and UX Updates
Sales Cloud V2 was built mobile-first, and each release refines the field sales experience.
Faster load times. SAP optimised the initial load and navigation on mobile. In our testing the improvement was noticeable on list views and opportunity detail pages. Not dramatic, but it adds up over a day of field work.
Improved offline sync. For reps working with poor connectivity (warehouses, factory floors, rural customer sites), offline sync now handles larger data sets more reliably. Syncing a large territory after a long offline period used to stall; incremental sync improvements address that. Test it with your own territory sizes before a rollout.
Quick-action cards. New configurable cards on the mobile home screen for common tasks: log a visit, create a follow-up task, update an opportunity stage. Admins decide which actions appear. Fewer taps between opening the app and getting work done.
CTI Framework Enhancements
For teams running computer telephony integration with Sales Cloud V2, Q1 2026 improved the softphone embedding framework. We covered CTI integration architecture in depth before; here is the update.
Better softphone embedding. The shell plug-in framework for CTI widgets supports more layout options and better state management. The softphone panel keeps its state across page navigation, so an active call doesn’t lose context when a rep moves from an account to an opportunity. It sounds minor, but it was a real annoyance for customers on live calls.
Improved call logging. Automatic activity creation from call events is cleaner. Duration, direction (inbound or outbound) and outcome are captured with less manual work, and the mapping between telephony events and Sales Cloud V2 activity types is more configurable.
Incremental, but it reduces integration effort for teams deploying CTI, whether with our own Engage CTI product or a third-party adapter.
Guided Selling Updates
Guided selling, Sales Cloud V2’s playbook engine for standardising sales processes, got two practical improvements.
New playbook templates. SAP added templates for common B2B scenarios: new business acquisition, account expansion and competitive displacement. They are starting points to adapt to your own method, not finished playbooks, but they shorten the setup for a new team considerably.
Step completion tracking and analytics. Managers can see which playbook steps reps complete, skip or abandon. If “discovery” has a 90% completion rate and “technical validation” sits at 40%, that tells you where your process breaks down, or where the playbook doesn’t match reality.
What This Means for Your Team
What to do depends on where you are.
If you’re already on V2. These updates arrive automatically with SAP’s quarterly releases, without downtime. Nothing to install, nothing to migrate. Our recommendation: start with Joule Studio. Pick one workflow (pre-call briefings or lead enrichment) and build a pilot agent. Then review the new deal intelligence signals with your sales managers and build them into the weekly pipeline review. The forecasting changes are worth a look too, especially if your current setup relies on spreadsheet overlays.
If you’re still on V1 (C4C). SAP’s new AI capabilities, Joule agents included, are delivered on V2. V1 still receives releases, and SAP has not announced an end-of-maintenance date as of September 2026, but the gap between V1 and V2 widens with every quarter. 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 timeline and effort.
If you’re evaluating Sales Cloud V2. The quarterly release cadence is one of V2’s structural advantages: you are always on the latest version. For a balanced picture, read our assessment of what Sales Cloud V2 can’t do yet alongside this post, and our implementation guide for timelines and costs.
Wherever you are, talk to our team about what these updates mean for your situation.
What Came Next
We originally planned this as the first post in a quarterly series. Instead of separate quarterly posts, we now fold release changes that affect projects into our guides: the 2026 release section of the SAP Sales Cloud V2 implementation guide tracks what changes scoping, and What’s New in SAP Service Cloud V2 covers the service side. For the official view of what is planned, the SAP Road Map Explorer is the reference.
To stay current with what ships and what it means for the people who implement it, browse our blog or follow us on LinkedIn.
Ask Spadoom
Answers drawn from what Spadoom has published on this site, with links to the pages they come from.
Try one of these
AI-generated answers. Verify before acting. Questions are stored anonymously, without your IP address, so we can improve our content. Please do not enter personal data.
SAP Sales Cloud V2 implementation partner
Spadoom is the SAP Sales Cloud V2 implementation partner across Switzerland, Germany, Austria and Italy. 14-week median go-live. Live customers across DACH.
Related articles
What's New in SAP Service Cloud V2 in 2026
The 2026 SAP Service Cloud V2 releases through Q3, sorted by what matters in practice: Agent Inbox, the Digital Service Agent handoff, approvals, item-level complaints, analytics, the Q2 additions from the new email editor to sales objects in the service workspace, and the Q3 Joule AI Units billing change.
SAP CX AI Toolkit: What's Available, What's Announced, What's Still Roadmap
Which AI features in SAP Sales Cloud V2, Service Cloud V2, SAP Engagement Cloud, Commerce and CDP run in production today, which SAP has announced with a date, and how to roll them out and measure the return.
SAP Joule for Sales Cloud V2: A Hands-On Guide
What Joule does in SAP Sales Cloud V2 today, how it is licensed and switched on, how it differs from Joule Agents and Microsoft Copilot, and where it still falls short.