Process Intelligence in the flow of work

The Process Explorer, rendered inside the conversation

The end-user never operates the explorer. The agent does the analysis and returns the case's path as evidence — in the channel they already work in.

A Who is the user

An operations owner — e.g. an AP / Procurement specialist accountable for DPO. They handle individual cases all day and never open Celonis; the process context behind a recommendation isn't available at the point of work.

B The user flow

They ask the agent in their channel → it queries Celonis via MCP (discovered process + conformance, PAM) → returns the case's path against the standard flow → they read it and decide — no Celonis session.

C What they do after

They confirm, and the agent reports the deviation to the process owner and triggers the Action Flow (human-in-the-loop / write-back) — recorded for audit and tracked against the KPI.

Addressing the concern

Why this is a real operational use case

"…we haven't had real use cases where end-users actually need the process explorer in their operational tasks."
They don't need to operate it. At the moment of a decision they act on its evidence — the case's path — which makes the agent's recommendation trustworthy and turns it into action. Concretely, that delivers:

Operational gains

at the point of work
  • A recommendation arrives with its process evidence — interpretable and auditable, which matters where decisions carry compliance weight (SOX).
  • The operator sees the root cause, not just an instruction — better, faster decisions.
  • Removes the analyst round-trip: "why is this happening?" is answered on demand.
  • Insight → decision → write-back stay in one thread, logged.

Commercial gains

adoption & differentiation
  • Process intelligence reaches users in their working channel — adoption without a new tool, login or training.
  • More recommendations acted on → more realized value → stronger renewal & expansion.
  • Surfaces the Process Intelligence Graph as a shared, visible asset — not a back-office report.
  • A concrete product differentiator for the proposal.

Possible uses

beyond this example
  • P2P: blocked invoices & payment-term breaches (DPO).
  • O2C: disputes, blocked / delayed orders (DSO).
  • Any conformance / deviation explanation, on demand.
  • Proactive alerts (agent-initiated) with the path attached.
  • Across Teams, Slack, WhatsApp & Telegram — card or image per channel.
Built on Celonis MCP + PAM → a rendered slice in an Adaptive Card / Block Kit (Teams, Slack) or an image (WhatsApp, Telegram), plus a deep link to the live explorer. Illustrative example — not real data.
Interaction