signalisys
Readiness glossary

Flow & Automation Depth

How much of the customer journey runs on documented, automatable Flows and invocable actions — versus tribal knowledge and manual steps.

Why this score moves

  • Coverage of Flows / invocable actions vs. manual handoffs
  • Coverage of exception and edge-case paths
  • Whether decision rules are codified or live in people's heads

Reading the four bands

EMERGING

Most steps are tribal — handoffs and decision rules aren't written down, so an agent has nothing reliable to invoke.

DEVELOPING

Core flows are mapped but exceptions and decision logic are inconsistent — an agent can only handle the happy path.

ESTABLISHED

Most processes run on Flows and invocable actions, with clear KPIs and exception paths an agent can call.

OPTIMISED

Flow telemetry, decision logs and exception taxonomies are continuously refreshed — agents are deployed against operational reality.

What good looks like

  • End-to-end journeys built as Flows with owners and SLAs
  • Live cycle-time and exception telemetry, not just diagrams
  • Invocable actions an agent can call instead of bespoke glue
  • A regular cadence for refreshing flows when reality drifts
More dimensions
Data Cloud
Data Cloud Readiness
Agentforce
Agentforce Fit
Core Cloud
Core Cloud Foundation
HITL
Human-in-the-Loop Design
Trust
Trust & Governance
Exec
Executive Alignment