Architecture
Existing systems in. Outcome out.
Journey Guru sits above the systems you already run. It receives the business state you define, maintains a persistent Journey, and coordinates the work between them.
Existing Systems
JOURNEY GURU
Outcome Orchestration Layer
Signal
Tenant-defined data changes / business events
Journey Run
Goal · Context · Current State · Journey History
Decisioning
Eligibility · Gates · Timing · Consent · Rules
Execution
Communications · AI · Transfer · Verification · Human Escalation · Connected System Action
Outcome
Success · Achieved · Transfer · Exit · Cost · Journey History
Connected system actions depend on available integrations and permissions.
"The systems stay authoritative. Journey Guru carries the process between them."
Your customer doesn't care which system owns the data. They care whether your business knows what to do next.
Journey Guru connects the operational state scattered across your stack into one accountable Journey toward an outcome.
Platform Capabilities
Six capabilities that turn customer state into business progress.
Business Signals & Custom Data
Bring tenant-defined customer, account, application, loan, case, and operational data into the Journey layer through supported data ingestion.
Example
PastDueAmount = $742 · Updated via tenant API
Journey State & Memory
Maintain why a Journey began, what has already happened, where the customer is now, and the context that should carry forward.
Example
Entry reason: Past due balance · Current stage: Awaiting borrower response
Journey Definitions & Runs
Define reusable business processes while maintaining a persistent, individualized Journey Run for each customer and relevant business context.
Example
Definition: Payment Resolution · Run: #128394
Decisioning & Orchestration
Use eligibility gates, changing data, timing, consent, rules, and Journey state to determine the appropriate next step.
Example
Quiet hours active · Next permitted outreach: 8:00 AM
Coordinated Execution
Coordinate communications, AI, verification, Journey transfers, and human intervention while allowing external business systems to remain authoritative.
Example
SMS → Response → Human Escalation
Outcomes & Economics
Record how the Journey ended, whether the intended result occurred, what Journey Guru contributed, and what the process cost.
Example
Outcome: Achieved · Contribution: Assisted · Cost: $X.XX
How a Journey Runs
From qualification to confirmed outcome.
The tenant's authoritative business state confirms whether the defined outcome condition occurred.
Qualify
PastDueAmount > 0
Tenant-defined data determines whether this customer currently qualifies for the process.
Start
Payment Resolution Journey Run begins
Goal: Resolve Past Due Balance
Journey Guru starts an individualized Journey Run that carries the goal, customer context, current state, and Journey history.
Orchestrate
Message → Wait → Evaluate → Branch → Escalate → Transfer
Journey Guru follows the tenant-defined process and adapts as customer responses, timing, and business state change.
Observe
PastDueAmount becomes $0
External systems remain authoritative.
The authoritative business system sends Journey Guru updated state through the configured data or integration path.
Prove
Outcome: Achieved · Contribution: Assisted · How It Ended: Data change · Cost: Recorded
Journey Guru records whether the intended condition changed, how the Journey ended, and the activity involved.
"Journey Guru does not need to own the underlying business system. It needs to know when state changes, which Journey it belongs to, and what should happen next."
Same Goal, Different Path
One outcome. Different paths.
Every customer can pursue the same tenant-defined outcome through a different Journey Run based on account state, prior actions, consent, risk, responses, and changing context.
Fast Resolver
Needs Help
High-Risk Escalation
Advanced / human-assisted execution
Every path produces one auditable record of entry state, Journey history, outcome, and disposition.
Outcome Integrity
Finishing a Journey isn't the same as achieving the goal.
Journey Guru separates whether the intended business outcome occurred from how the Journey Run progressed or ended.
Business Outcome
Success
The goal was achieved through the designed Journey path.
Achieved
The tenant-defined goal occurred, but outside the designed success path.
None
The goal has not yet been achieved.
Run Disposition
Terminal
Completed
The Journey reached its natural end.
Exited
Changing customer or business state removed the customer from the Journey.
Cancelled
A human intentionally stopped the Journey.
Transferred
The customer moved into another defined Journey or stage.
Non-Terminal
Escalated
Human intervention became necessary while the Journey remained active.
A Journey can escalate without ending. The outcome can still be achieved later.
Business Outcome × Run Disposition
Journey Guru does not automatically take credit for every positive outcome that happens while a Journey is active.
Outcome attribution should be earned—not assumed.
Architecture
Built above the stack you already have.
Journey Guru does not require rip-and-replace. Your existing systems remain authoritative while Journey Guru maintains the goal, context, state, and orchestration needed to move the customer between them.
Model-Agnostic
Use the appropriate AI model for the task while Journey Guru preserves Journey state, rules, permissions, and accountability.
Channel-Agnostic
Continue the same Journey across messaging, voice, email, chat, applications, AI interactions, and human conversations.
Data-Stack Agnostic
Work with tenant-defined business state from the LMS, CRM, warehouse, servicing platform, or other system of record.
Workflow-Aware
Coordinate across systems and teams while preserving one persistent Journey history and intended outcome.
Journey Guru connects with
"Journey Guru does not replace your systems. It gives them a shared Journey state and a common outcome to work toward."
Trust & Control
Control is part of the architecture.
Outcome orchestration requires the business—not the model—to remain authoritative.
Tenant-Defined Logic
You define what the data means.
Tenants determine which business conditions trigger Journeys, how customers progress, and what represents the intended outcome.
Permissioned Verification
Verify without unnecessary exposure.
Sensitive verification values can be compared without requiring Journey Guru or the AI interaction to expose the underlying value.
Authoritative Business State
Your systems remain the source of truth.
Journey Guru reacts to tenant-provided or integrated customer and account state rather than inventing domain truth.
Human Intervention
Automation should know when to stop.
Journey logic can identify situations where human judgment, approval, or intervention is the appropriate next step.
Auditable Execution
Know why the Journey moved.
Entry, decisions, communications, transfers, outcomes, and ending conditions can be captured as part of the Journey history.
Move faster with AI without surrendering control of the customer, the process, or the outcome.
Platform Direction
Built for what comes next.
The same architecture becomes more important as AI becomes more autonomous.
Today, Journey Guru coordinates changing customer data, communications, AI, systems, and people around a persistent Journey.
As AI agents increasingly interact with systems and other agents, the same Journey layer can preserve the goal, context, permissions, state, and audit history around that work.
"Agents can talk. Journey Guru makes sure the business moves."