From chat to agents: skills, agents and assistants

Contoso's finance team has used Joule's questions and answers since go-live. The next step is different in kind: Dan, the finance process owner, wants to pilot Joule Agents in accounts receivable, where an agent prepares collection calls and creates dispute cases. Before he signs anything, he needs to understand what an agent is, how it differs from a skill and an assistant, and what SAP's own documentation says about each. This course follows his pilot from definition to a decision to scale. Statuses are as of 17 October 2026; SAP TechEd (27 to 29 October 2026) may change details.

Skills: predefined, deterministic operations

SAP's Joule Studio documentation is precise about the difference. A Joule skill executes "atomic single operations that are predefined and often repetitive", based on structured inputs and deterministic logic: retrieve data, trigger a transaction, start a workflow, navigate. Its logic flow is static and its outcome is predictable. Joule's natural language understanding decides which skill to trigger, however the user phrases the request, but the skill itself doesn't reason. SAP reported more than 2,500 Joule skills in early 2026.

Agents: multi-step, adaptive, tool-using

A Joule agent, in the same documentation, is "an autonomous, multi-tool system that solves complex problems by selecting and executing appropriate tools dynamically." It uses a large language model to plan, chooses among tools (which can include skills and APIs), and adapts as it goes. SAP is candid about the consequence: agents are "more resource-intense", results "are not always the same for the same input", and building a reliable one "usually takes a few iterations". SAP even notes that in some cases a skill may be the better fit.

Assistants: the role-aware layer users talk to

A Joule Assistant is what a user addresses. SAP's documentation calls assistants "the primary user interaction and orchestration layer", role-aware and business-context-aware, while agents "work behind the scenes". The relationship is many-to-many: an assistant may coordinate several agents, and one agent may be shared by several assistants for reuse and central governance. Configuration happens on the assistant: enable it and its agents become available, then role-based permissions decide which agents each user may use.

Why SAP separates the two

Splitting the user-facing assistant from the working agents has practical benefits that show up in a pilot. One agent, such as dispute creation, can serve several assistants without being rebuilt. Access is configured once, on the assistant, and refined per agent with permissions. And the agents can be changed or added behind an assistant without retraining users on a new entry point. For a test lead, it means the same agent may be reached through more than one assistant, so test the paths users will really take.

SAP-delivered, partner and custom agents

Joule Studio's glossary distinguishes LoB agents, delivered by SAP for a business domain (its example is an AP invoice agent), from custom agents, built in Joule Studio for a need no SAP agent covers. Partners build agents too, supported by the €100 million partner fund SAP announced at Sapphire 2026. The new Joule Studio was described by SAP on 8 October 2026 as "soon to be generally available"; Joule Studio, classic edition, in SAP Build, is the current production tool and loses its design-time generative AI features after 31 December 2026. Whatever the source, SAP AI Agent Hub (announced generally available in October 2026) is where an enterprise inventories and governs them.