Overview

Conversation Intelligence is built from a small set of primitives. Each one is explained here on its own terms; the workflow guides and the API reference link back to these pages rather than re-explaining them.

The primitives fall into three groups: what you define to analyse a conversation, the policy that composes those definitions, and what runs and what you get back.

Define what to analyse

OperatorsA single, reusable unit of analysis: a prompt paired with a typed output. Detects, classifies, scores, extracts, or tags one thing about a conversation.TemplatesPlatform-maintained, read-only starting points for a configuration, pre-populated for a use case such as fraud detection or contact centre.

Compose a policy

ConfigurationsThe policy a conversation is analysed under: which operators run and how, and the actions that fire on their results. The unit you select per call.ActionsDelivery instructions defined within a configuration: webhooks and whispers that fire when operator results meet a condition.

Run and retrieve

SessionsAttach a configuration to a single live call and run it in realtime — turn by turn as the conversation unfolds, and once when it ends.ConversationsThe durable record of everything that happened across one or more sessions on the same call — the unit you query and report on afterwards.