Workflow Inbox

    The operational layer for business processes

    Every step is policy bound. Every state is verified against the Golden Record. Humans, systems, and AI agents operate from the same process, with the same governance and the same audit trail.

    Deterministic. Governed. Built for AI-native operations.

    A Workflow Inbox is a defined business process that runs on verified data, changes state at every step, and delivers the entire experience through messaging - so it feels simple, but executes with the precision of a state machine.

    Think KYC onboarding, order returns, insurance claims, patient referrals. Each is a process with verification steps, approval gates, and a clear objective. The Golden Record is the trusted profile that drives every decision.

    Not a Pipeline. Not a Chat. A Process.

    LLM wrappers send text to a model. Pipelines move data between tools. A Workflow Inbox executes a defined process - with state transitions, verification steps, and parent/child inheritance.

    LLM Wrappers
    Workflow Inbox
    Stateless conversation - no process memory
    Stateful process - every step changes a defined state
    LLM decides the next action
    Company logic decides what is allowed next
    Flat interaction - no structure
    Parent workflows inherit child workflows
    No verified data - works from raw input
    Golden Record - verified, validated, always current
    Wrapper around an API
    Business process with verification steps and state transitions
    AI interprets freely
    Deterministic execution within a defined objective

    How a Workflow Executes

    From trigger to completion. Every step changes state, validates data, and keeps the Golden Record current.

    Step 1 - A Process Starts

    A customer message, an API call, a form submission or a system event starts a workflow. This is not a chat - it is the beginning of a defined business process with a clear objective.

    KYC onboarding requestOrder return initiatedFinancing applicationInsurance claim filedDelivery exception

    Step 2 - The Golden Record Drives Every Step

    The workflow operates on verified, validated data - the Golden Record. Every interaction updates this trusted profile. Child workflows inherit context from the parent, so nothing is asked twice and nothing is assumed.

    Data verified at each stepState transitions loggedParent → child inheritanceSystem of record updated

    Step 3 - State Changes Under Governance

    Each step changes the state of the process. Required fields are validated. Approval gates are enforced. Compliance is embedded. The workflow moves forward only when conditions are met - not when the LLM thinks they are.

    State machine enforcementValidation before transitionApproval gatesAudit trail per step

    Parent & Child Workflows

    Real business processes are rarely flat. An onboarding process contains identity verification. A return process contains warehouse intake. Parent workflows inherit child workflows - context flows down, state flows up.

    Context Inheritance

    Child workflows receive the parent's Golden Record - no duplicate data collection, no repeated questions.

    State Propagation

    When a child workflow completes, the parent's state updates automatically. KYC approved → account setup continues.

    Independent Governance

    Each child workflow has its own validation rules, approval gates, and audit trail - nested but autonomous.

    The Golden Record

    Every workflow reads from and writes to a verified, validated profile - the Golden Record. This is not a cache. It is the system of record that upstream services, internal teams, and external integrations can trust.

    Verified at every workflow step
    Updated in real time by state changes
    Trusted by upstream integrations
    Serves internal and external workflows
    Never exposed directly to an LLM
    Complete audit trail per field

    Workflows in Practice

    Every industry has processes with defined steps, verification requirements, and state changes. The Workflow Inbox turns them into governed, messaging-driven experiences. Swipe to explore.

    Without a Workflow: What LLM Wrappers Miss

    No process definition - the LLM improvises each interaction
    No state management - conversations restart from zero every time
    No Golden Record - works from unverified, scattered data
    No parent/child workflow inheritance - every request is isolated

    Retail & E-Commerce

    Return & Exchange Workflow

    A return request starts a workflow. The Golden Record shows the original order, payment method, loyalty tier and return history. Each step - eligibility check, label generation, refund approval - changes the process state. A child workflow handles the warehouse intake.

    Process States

    Return requestedEligibility verifiedLabel sentItem receivedRefund approved
    Golden Record: Purchase history, preferences, loyalty status - verified and live

    Financial Services

    KYC Onboarding Workflow

    A new customer starts the KYC process via a message. The workflow collects identity documents, runs verification steps, and changes state from 'pending' to 'verified'. A parent onboarding workflow inherits the KYC child workflow - once identity is verified, account setup continues automatically.

    Process States

    Identity submittedDocument verifiedRisk assessedKYC approvedAccount active
    Golden Record: Verified identity, compliance status, risk profile - one trusted record

    Healthcare

    Patient Referral Workflow

    A referral starts a workflow with the patient's Golden Record - insurance status, consent, medical history. Each step validates eligibility, checks coverage, and schedules the specialist. The process state changes from 'referred' to 'scheduled' only when all verification steps pass.

    Process States

    Referral initiatedInsurance verifiedConsent confirmedSpecialist matchedAppointment scheduled
    Golden Record: Insurance eligibility, consent status, treatment history - protected and auditable

    Logistics & Supply Chain

    Exception Handling Workflow

    A delivery exception triggers a workflow. The Golden Record shows the shipment's full journey, SLA commitments and customer priority. The workflow escalates based on state - missed scan, delayed handoff, or failed delivery - each with its own child workflow for resolution.

    Process States

    Exception detectedRoot cause identifiedResolution initiatedCustomer notifiedSLA updated
    Golden Record: Live tracking, SLA status, exception history - sourced from the system of record

    The 30-Second Version

    A workflow is a defined business process - with steps, verification, and state transitions.

    The Golden Record is the verified profile that drives every decision and serves as the trusted source for upstream integrations.

    Parent workflows inherit child workflows - context flows down, completed state flows up.

    The experience is messaging - but the execution is deterministic, governed, and fully auditable.

    Customer Inbox

    Build Golden Records from every customer signal - the trusted foundation your workflows operate on.

    Agent Inbox

    Govern autonomous AI agents with deterministic validation - ensuring agents only execute approved workflow steps.

    Your Business Process, Governed

    Defined process stepsState transitionsGolden RecordParent/child inheritanceMessaging UXFull auditability

    Every business process deserves the precision of a state machine and the simplicity of a text message.