Joule Assistants vs Joule Agents explained

In 30 seconds

What it is Assistants coordinate agents by role; agents execute specific business processes.

You use it when You are mapping which assistant a team will talk to and which agents it should be allowed to call.

Next in this section Joule Studio vs Joule Work: one is for using AI, one for building it →

A Joule Assistant is the coordinator who knows your role. A Joule Agent is the specialist who executes one process.

Part 12 of 26 in SAP Business AI, Explained.

People use “assistant” and “agent” as if they meant the same thing. In SAP’s vocabulary they don’t. One coordinates and the other executes, and getting that straight decides who owns what when something goes wrong.

A Joule Assistant understands your role and decides which specialists to call. A Joule Agent is the specialist that carries out one business process.

Coordinator or specialist?

SAP describes Joule Assistants as aligned to business roles and processes, so they can infer what you want and which agents to use.
Joule Agents, in SAP’s words, are AI agents with business process expertise that carry out multistep tasks across SAP and non-SAP systems.
You meet assistants in Joule Work. SAP says they surface there and coordinate agents in sequence or in parallel, behind an agent gateway.

The everyday picture

Think of a hospital ward. The ward coordinator doesn’t operate or prescribe. She knows every patient, knows which specialist to call, and keeps handovers tidy. That’s a Joule Assistant. The cardiologist, the radiologist and the pharmacist each do one thing deeply, and those are the Joule Agents. The front desk where you walk in is Joule Work, and the medical board that licenses each doctor is your governance.

Some leaders prefer an orchestra, with a conductor who decides who comes in and when. I prefer the ward. A conductor never has to check a patient’s consent, and agents, like doctors, must only act within what they’re allowed to do.

From one request to several agents

You state an outcome. In Joule Work you ask in plain words, for example “get my overdue receivables under control this week”.
The assistant reads your role and context. SAP says assistants use deep role and process context to infer intent and choose the right agents.
It plans and calls agents. SAP’s Joule Work page describes orchestration in which assistants coordinate multiple specialised agents, in sequence or in parallel.
Each agent runs its process, connecting the relevant data, tools and applications to analyse, trigger actions or execute workflow steps, per SAP.
Results come back to you. The assistant brings the outputs together, and anything that needs approval waits for a person.

	Joule Assistant	Joule Agent
Main job	Coordinate work for a role	Execute one business process
Knows	Your role, context, which agents exist	Its process, tools and data
You talk to it?	Yes, through Joule Work	Usually not directly
Output	A combined result and next steps	A specific action, analysis or proposal
Owner on your side	Role or process area owner	The owner of that process

Quarter-end cash at NextSAP

NextSAP Utilities, the fictional Dubai utility used across this site’s SAP content, serves about 5 million customers across electricity, water, gas and district cooling on SAP S/4HANA with SAP Utilities and SAP FI-CA (Contract Accounts Receivable and Payable), with a shared services team in India. In the last week of the quarter, Omar, the finance controller, opens Joule Work and types “show me what is stopping cash coming in this week and what we should do”. He’s talking to a finance assistant. I use “finance assistant” as a plain label here, not an SAP product name. The actual assistants depend on what SAP offers and what you enable.

It reads Omar’s role and calls three agents.

The collections prioritiser (prebuilt plus an extension, autonomy L2 Propose; it’s still at L2 at this point, and post 09 covers its later move to L3) reviews about 2,400 overdue open items worth AED 18.6 million (UAE dirhams) and proposes about 150 calls for the day, ranked by amount, age and promise-to-pay history.
A billing anomaly check (prebuilt billing check pattern, L2 Propose) flags 23 commercial bills worth AED 410,000 that rest on unusual consumption or estimated meter reads. Those customers are likely to dispute, so calling them for payment first wastes time.
The payment clarification agent (custom, built in Joule Studio, L2 Propose) reports about 140 unclear incoming payments that arrived overnight, worth AED 2.3 million, and proposes matches for 112.

The assistant then combines the answers. It drops the 23 disputed-risk customers from the call list and adds 9 customers whose cash already arrived but sits unmatched, so Omar sees one plan rather than three reports. Nothing is posted or sent. Each item waits for a clerk’s approval, because all three agents work at L2 Propose on the autonomy ladder.

When a clerk later asks “why was customer 300457 dropped from my call list?”, the trace shows which agent said what. That’s exactly why you separate coordination from execution.

SAP’s own examples follow the same shape. On its Joule Agents page it describes Bosch using a Joule Classification Agent to route customer service cases in real time, replacing rigid rule-based workflows.

So which one do you reach for?

Situation	Reach for	Why
A user asks a broad question spanning several processes	Assistant	It knows the role and which agents to call
A clear, repeatable process step needs doing	Agent	It owns that process and its tools
A result needs input from three teams’ processes	Assistant calling several agents	It sequences and combines them
A step moves money, pay or legal outcomes	Agent at L2 Propose or L3 Act with approval	A person stays the checker
You want a new specialist capability	Agent, prebuilt or built in Joule Studio	See post 13

The line between them

Per SAP, an assistant turns one request into a coordinated set of agent tasks, and an agent executes a defined process with the data and tools it’s allowed to use. The person gets one answer instead of several screens.

An assistant doesn’t widen anyone’s permissions, though. SAP says agents only execute what the end user may do directly. An agent doesn’t set your policy either, since thresholds and approval rules are yours. And neither replaces the process owner, because someone still owns each outcome.

Explain it to your CFO

The coordinator understands your job and decides which specialist to ask. Each specialist handles one task, such as chasing overdue payments or checking bills.
Anything that moves money still waits for one of our people to approve it.

Before you switch on an assistant

Which agents may each assistant call? I’d start with an explicit list per role, reviewed by the process owner, rather than “all available agents”.
Who owns each agent? The owner of the underlying process, recorded in SAP AI Agent Hub. SAP News describes the Hub inventorying agents and mapping them to capabilities and owners.
What autonomy does each agent get? My default is L2 Propose for anything touching cash, billing or customer balances, until you have three months of clean evidence.

Go deeper

Technical detail for architects and developers

SAP’s Joule Work page describes agentic thinking as orchestration that manages multistep tasks and connects actions across processes, with assistants coordinating agents in sequence or in parallel. A member post on SAP Community, written after SAP TechEd 2026, describes the same pattern as planning steps, choosing assistants and agents, and coordinating across SAP and non-SAP systems. Treat that member post as secondary.

On agent capabilities, SAP’s Joule Agents FAQ says agents choose from a large set of tools, including Joule skills, other agents and third-party applications. They plan, act, reflect on results and make recommendations. Prebuilt agents use MCP (Model Context Protocol) and A2A (Agent2Agent) for cross-system work.

SAP says Joule Agents are grounded in SAP Knowledge Graph and SAP Business Data Cloud, which give them data and process relationships to reason over.

For identity and control, SAP states each agent gets a unique identity for reauthentication at every step, and all traffic flows through one agent gateway. High-risk processes require explicit approval and agent activity is logged, per SAP’s Joule Agents page.

My own design note: assistants route work, and each agent owns one process with one owner. If an “agent” needs to coordinate three others, it’s probably an assistant-shaped problem. Keep the routing logic in the assistant and the business rules in the agents, so you can test each on its own.

SAP News (September 2026) describes SAP AI Agent Hub inventorying agents, models and MCP servers and mapping them to business capabilities and owners. See post 06 and post 25 for conflicts between agents.

Words you’ll hear

Joule Assistant: an SAP AI assistant aligned to a business role that coordinates agents to complete a request.
Joule Agent: an SAP AI agent that executes a specific multistep business process using tools and data.
Orchestration: planning and sequencing several agents’ work so they add up to one outcome.
Joule Work: SAP’s AI workspace where assistants surface and people ask, act and approve.
Agent gateway: the runtime checkpoint enforcing identity, access and policy on every agent call.
Multi-agent system: a network of agents that split complex work into coordinated tasks.
MCP (Model Context Protocol): an open standard for connecting agents to tools and data.
A2A (Agent2Agent): an open protocol for agents to hand work to each other.

Keep going

Independent explainer, not affiliated with or endorsed by SAP SE. SAP, Joule and other SAP product names are trademarks of SAP SE.

Frequently asked questions

What is the difference between a Joule Assistant and a Joule Agent?

SAP describes Joule Assistants as aligned to business roles, coordinating agents to complete what a user asks. Joule Agents execute specific multistep business processes using tools, data and applications.

Do I talk to agents directly?

Usually you talk to an assistant in Joule Work. SAP says Joule Assistants surface through Joule Work and direct the agents, which then do the specific tasks.

Can an assistant call agents in sequence and in parallel?

Yes. SAP's Joule Work page describes orchestration in which assistants coordinate multiple specialised agents in sequence or in parallel.

Which assistants and agents exist today?

SAP lists them by line of business on its Joule Agents and Assistants page. Availability changes often, so check the current status in the Joule capability watch on this site.