Intelligence Overview

Per-interaction evidence, workspace analytics, dashboards, metric values, and the boundaries that determine their availability.

Eligible voice and text interactions can produce structured analytical evidence covering operational signals and outcome quality. Intelligence processing is best-effort, projections can lag, and audio-native analysis applies only when a usable recording exists. This section explains where that evidence surfaces and which gaps must remain explicit.

The intelligence layer has three parts that build on each other: per-interaction analysis, workspace-level analytics, and a metric pipeline that turns both into trackable numbers.

Call Intelligence

Voice call intelligence can combine operational profiles derived from call signals, post-interaction quality scoring, and audio-native scoring from the recording. Text interactions use the evidence available to their modality and do not receive audio-native analysis. Composite scores support trend analysis, while transcripts and structural traces show observed states, actions, and tool execution without exposing hidden model reasoning.

Call Intelligence

Analytics and Dashboards

Workspace analytics cover call and production-eval trends, surface outcomes, event composition, connector and pipeline health, and current entity-inspection views. Built-in and custom dashboards and the conversational Insights Agent support analysis, while the unified Runs surface remains the canonical interaction inventory. Each analytical surface has its own evidence source and freshness boundary.

Analytics and Dashboards

Topic Classification

Workspaces can enable automated conversation topic classification. When the setting is active, the platform periodically discovers enabled workspaces, resolves their active taxonomy and service context, and classifies recent conversations against the taxonomy. Each workspace is processed independently - a misconfigured workspace is quarantined for triage rather than blocking classification for other tenants. Workspaces require exactly one active taxonomy and at least one active service with a non-blank name to qualify; workspaces that do not meet these prerequisites are recorded as skipped with a reason so the gap is visible rather than silent.

Metric Store

The Platform API exposes 41 built-in metric definitions across six categories and supports up to 50 workspace custom definitions. Recent and durable values share one response model, but producers, execution schedules, and modality requirements differ. A catalog entry or freshness target does not guarantee that a value exists or will arrive within a fixed time.

Metric Store

Event Streams and Analytics

The workspace SSE stream publishes supported call, surface, pipeline, text, operator, and other workspace events as they occur. It is an operational notification channel, not the durable analytics store, and it includes only events that producers publish. Consumers should reconnect with the last event ID when possible and reconcile important state through the corresponding read API.

A separate per-call observer stream can provide live transcript and tool activity for call monitoring. Stream availability does not imply that the same evidence will be retained indefinitely or that post-call intelligence has completed. See SSE Events in the developer guide for endpoint and payload details.

Developer Guide - For the full analytics endpoint set and metric store details, see Analytics in the developer guide.