Velaxe
Chat Core — Orchestration Engine for Sessions, Routing, Handoff & Governed AI | Velaxe

Chat Core

Run a post-incident trace review & replay

Inspect decision traces, measure SLA impact, and replay with candidate fixes.

24 min Intermediate Support Lead, SRE/Ops Updated Oct 3, 2025
View App All Guides
Orchestration trace
Which nodes fired & why

Overview

Inspect decision traces, measure SLA impact, and replay with candidate fixes.

Prerequisites

None.

Permissions required

traces:read experiments:write

Steps (3)

Estimated: 24 min
  1. 1

    Open the incident sessions

    Support Lead 6 min Back to top

    From Chronicle, filter by timeframe and queue. Open associated traces.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Identify decision bottlenecks

    SRE 8 min Back to top

    Look for slow tools or low-confidence routes. Note latency & cost outliers.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Replay with fixes

    Platform 10 min Back to top

    Use Replay to test updated routing/prompt settings and compare KPIs.

    Tips

    —

    Validation

    —

    Success criteria

    • Replayed sessions meet SLOs; change list exported to InsightLake.

About this guide

Chat Core decides what happens next in any live conversation. It stitches identity across channels, maintains durable sessions, detects intent and sentiment, calls tools and knowledge bases, and chooses between automated replies or human handoff with clear SLAs. Operators get routing/skills rules, cost & safety guardrails, experiments, and an orchestration trace for explainability.

Tightly integrated with PulseGate for transport, LiveConnect for real-time inbox, Agent Desk for tickets, FlowForge for automation, Chronicle for audit-ready timelines, and InsightLake for analytics—so you can ship omnichannel support that scales safely.