Overview
Cap spend per brand/queue, set fallbacks, and alert on anomalies.
Prerequisites
None.
Permissions required
Steps (3)
-
1
Create budgets
Cost Board → Budgets. Set monthly caps per brand and per queue.
Tips
—
Validation
—
Success criteria
—
-
2
Configure fallbacks
For each model, choose a cheaper fallback and a rules-only mode if budget exceeded.
Tips
—
Validation
—
Success criteria
—
-
3
Alerts & anomaly detection
Enable alerts for spend spikes and token anomalies in InsightLake.
Tips
—
Validation
—
Success criteria
- No session hard-fails; graceful degradation in place.
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.