SAP Joule for Sales Cloud V2: A Hands-On Guide

Joule is SAP’s AI assistant, and in SAP Sales Cloud V2 it now does useful work: it answers pipeline questions in plain language, summarises an opportunity before a call and drafts the follow-up email. It does not run your sales process on its own, and switching it on takes more than a toggle.

This guide covers what Joule does in Sales Cloud V2 today, how it is licensed and activated, how it relates to Joule Agents and Microsoft Copilot, and what we have learned rolling it out.

TL;DR: In Sales Cloud V2, Joule answers natural-language questions, summarises opportunities, suggests next steps and drafts emails. It needs a Joule SKU and an SAP-guided onboarding via BTP; AI agents need the separate CX AI Toolkit licence. Start with pre-call briefings, fix data quality first, and treat Joule as an assistant, not an autonomous agent.

What is SAP Joule?

SAP announced Joule in September 2023 as a generative AI assistant for its whole cloud portfolio. SAP planned the first release for SAP SuccessFactors and the SAP Start site in late 2023 and for S/4HANA Cloud Public Edition in early 2024. At the start it was mostly a question-and-answer layer.

Since then SAP has turned it into the entry point for SAP Business AI. According to SAP’s Q1 2026 release highlights, Joule is live across 35 SAP solutions with more than 2,500 skills and over 30 specialised agents. Each skill is one concrete action, such as summarising a case or creating a purchase order.

Two design choices matter for customers. Joule works inside the SAP application, so it knows the data model and respects the user’s roles. And it is not tied to one AI vendor: SAP routes requests to large language models from several providers through its own AI platform on SAP BTP.

What can Joule do in Sales Cloud V2 today?

Natural-language queries. Ask “Show me all open opportunities over CHF 100K closing this quarter” and Joule returns the list. No report builder, no filter syntax. It works better than most users expect.

Opportunity summaries. Select an opportunity and ask for a summary: value, stage, recent activities, key contacts, open tasks. This is most useful before a call or when you pick up a colleague’s deal.

Activity suggestions. Based on the deal stage and patterns in your system, Joule proposes next steps such as “schedule a technical demo” or “send the pricing proposal”.

Email drafting. Joule drafts follow-up emails from meeting notes and opportunity context. The draft always needs editing, but it removes the blank page.

Data entry assistance. When creating leads or opportunities, you describe the situation in plain language and Joule suggests field values.

Beyond the assistant, SAP delivers AI agents for Sales Cloud V2 through the CX AI Toolkit. SAP’s own learning material names, for example, a Quote Creation Agent that turns an email request into a quote, and it notes that the toolkit needs its own licence. We look at which of these are production-ready in our CX AI Toolkit reality check; the service-side counterpart is covered in our post on the Digital Service Agent.

What can’t Joule do yet?

Being clear about the limits prevents the adoption problems that follow inflated expectations.

• Cross-system analysis. Joule can pull basic information from connected SAP systems, such as S/4HANA account data, when the integration is configured. A single question that combines pipeline, service tickets and ERP order history is still limited.
• Autonomous execution. Joule proposes actions and waits for confirmation. It will not move a deal to the next stage or send an email by itself. Multi-step automation is the job of agents, which are licensed separately.
• Your own sales methodology. You cannot train Joule on your qualification framework or internal vocabulary. If your process depends on it, write it into guidance and field definitions instead.
• Offline use. Joule needs a connection and works best in the desktop web client.

We collect the wider list of V2 gaps, with workarounds, in our honest assessment of Sales Cloud V2 limitations.

How is Joule licensed?

SAP distinguishes between AI that comes with the cloud subscription and premium AI that is metered in SAP AI Units. For Sales Cloud V2 the practical picture as of September 2026 is:

• Joule itself requires one of two Joule SKUs (8019544 or 8019164), as listed in SAP’s set-up guide for Sales Cloud V2.
• AI agents from the CX AI Toolkit need a CX AI Toolkit licence on top of Sales Cloud V2.
• Consumption beyond the included allowance is charged in AI Units, so budget for growing usage once adoption picks up.

Licence terms change often and depend on your contract. Confirm them with your SAP account manager before you promise anything to the sales team.

How do you activate Joule in your tenant?

Activation is a sequence, not a switch. SAP’s set-up guide states that Joule can only be enabled in Sales Cloud V2 once it has been onboarded to the tenant through BTP configuration.

Step 1: Secure the licence. Confirm that your contract includes one of the Joule SKUs, and the CX AI Toolkit if you want agents.

Step 2: Register with SAP. The set-up guide (June 2026) asks customers to sign up for SAP’s early adopter programme for Joule in Sales Cloud V2 and then open a support case on component CEC-CRM-JOU.

Step 3: Complete the BTP onboarding. SAP’s programme team guides the onboarding. On the BTP side you need a subaccount, SAP Cloud Identity Services and the Joule entitlement; SAP’s Joule prerequisites list the details.

Step 4: Assign roles to a pilot group. Not everyone needs Joule on day one. Start with a few experienced reps who will give candid feedback.

Step 5: Test with real data. Check that queries return correct results against your actual records. Custom objects and unusual naming often need guidance.

Step 6: Roll out and train. Show the team what Joule can and cannot do. A short, realistic session prevents weeks of “this AI thing doesn’t work”.

What have we learned from Joule rollouts?

Clean data matters more than configuration. If opportunity stages are used inconsistently, Joule’s summaries are inconsistent too. If half the leads lack a company name, natural-language queries miss them. Fix data quality first.

Set expectations early. Reps who expect an autonomous assistant and get a smart search bar stop using it within a week. Position Joule as what it is: a faster way to find data and handle routine tasks.

Meeting prep is the quick win. The most valuable use case we see is a 30-second briefing before a customer call: opportunity status, last interaction, open tickets. That replaces several minutes of clicking through records, and it is where adoption starts.

Queries need practice. “Show me deals closing soon” works; “show me the ones that are slipping” may not. Collect the phrasings that work and share them with the team.

Measure use, not activation. Track how many reps use Joule each week. If usage drops after the first month, the cause is usually data quality or expectations, and both can be fixed.

Build it into existing routines. Morning pipeline review, pre-call prep, post-meeting follow-up. Joule should feel like part of the day, not an extra task.

How does Joule differ from ChatGPT and Microsoft Copilot?

General-purpose assistants such as ChatGPT or Claude are strong at writing and open-ended reasoning, but they do not know your pipeline or your order history unless you paste it in. Microsoft 365 Copilot works in Word, Excel, Outlook and Teams, and is disconnected from ERP and CRM processes.

Joule works inside SAP: it knows the data model, respects permissions and acts within the process. The trade-off is scope. It will not write your marketing copy, and it is not meant to.

The tools complement each other. With the Q4 2025 release, SAP made the bidirectional integration between Joule and Microsoft 365 Copilot generally available, so users can reach Joule from Copilot and the other way round. Joule is also not the only route to agents on SAP: our MCP Server for SAP Sales & Service Cloud V2 exposes V2 APIs as tools that any MCP-compatible AI can call.

Where is Joule heading?

SAP is moving Joule from assistant to agent platform. The Q4 2025 release made the agent builder in Joule Studio generally available, a low-code environment in SAP Build for creating your own agents. In the Q2 2026 release highlights SAP described a new version of Joule Studio for product teams and developers, still in early adopter care at the time. Treat anything beyond that as roadmap and check SAP’s current announcements before you plan around it.

What does not change is the foundation: clean data, clear processes and deliberate adoption management. Agents amplify a well-run process and expose a messy one. We cover the agent side in more depth in our post on agentic AI in SAP and what it means for sales teams, and SAP’s broader AI portfolio on our SAP Business AI page.

Our practical advice: get Joule running, get your team using the features that work today, and build the data foundation for what comes next.

---

Need help with Joule? We set up SAP Joule for Sales Cloud V2, from licence check and SAP onboarding to adoption coaching, and because we deliver S/4HANA Public Cloud and the CX stack with one team, we also connect Joule to your ERP data (see why one partner for Cloud ERP and CRM). Get in touch.

Frequently Asked Questions

Does Joule cost extra on top of Sales Cloud V2?

Usually, yes. SAP’s set-up guide for Sales Cloud V2 lists dedicated Joule SKUs (8019544 or 8019164), and the AI agents in the CX AI Toolkit need a CX AI Toolkit licence in addition to the Sales Cloud V2 licence. SAP meters premium AI through AI Units. Check your contract with your SAP account manager before you plan the rollout.

How long does it take to activate Joule?

Two parts. SAP’s onboarding (Joule SKU, early adopter registration, a support case on component CEC-CRM-JOU and the BTP onboarding) depends on SAP’s lead time. After that we plan two to three weeks for our own work: data checks, a pilot group, training and the wider rollout. Skipping the data step leads to poor answers and low adoption.

What is the difference between Joule, Joule Agents and Joule Studio?

Joule is the assistant you talk to: it answers questions and runs single actions such as an opportunity summary. Joule Agents work through multi-step tasks on their own, for example classifying cases or turning an email request into a quote. Joule Studio is SAP’s low-code environment for building your own agents; its agent builder became generally available with the Q4 2025 release.

How does Joule compare to Microsoft 365 Copilot?

Copilot works in Word, Excel, Outlook and Teams; Joule works inside SAP applications, knows the SAP data model and respects SAP roles. They complement each other: since Q4 2025 SAP offers a generally available bidirectional integration, so users can reach Joule from Microsoft 365 Copilot and the other way round.

Which languages does Joule support?

Joule supports several languages, including German and French; SAP maintains the current list in its Joule documentation. In our projects English queries were the most reliable, and German worked well for standard questions. Test in your team’s working language before a wide rollout.

What happens to our data when using Joule?

Joule runs in SAP’s cloud and uses your data only as context for your own tenant; SAP states that this context is protected and not reused elsewhere. Joule respects the roles and permissions in your Sales Cloud V2 tenant, so users only get answers from data they may see.