Skip to main content
Every event type Operata publishes to your partner event source. Each entry covers the detail-type, trigger condition, and an example payload.
Post-contact events arrive between 30 seconds and 5 minutes after the contact ends. Build consumers that key off detail.contact.id.current rather than wall-clock order.

Call summary

The enriched contact record — one event per completed contact. detail-type: CallSummary When it fires: After a contact completes, once Operata finishes joining the CTR, agent-side telemetry, and WebRTC session metrics. Payload:

Insights summary

The insights Operata established for a contact. Fires alongside CallSummary when at least one insight applies. detail-type: InsightsSummary When it fires: When Operata establishes one or more insights for a completed contact. Contacts with no insights produce no InsightsSummary event. Payload:

Agent reported issue

An issue submitted by an agent through Agent Messenger, including the surrounding device and browser context. detail-type: AgentReportedIssue When it fires: When an agent submits an issue through Agent Messenger. Independent of contact lifecycle — agents can report issues with or without an active contact. Payload:

Headset summary

Per-contact headset telemetry, delivered when headset stats collection is enabled for the group. detail-type: HeadsetSummary When it fires: When the group has headset stats collection enabled and a contact ends. Contacts without an attached headset produce no HeadsetSummary event. Payload:

Heartbeat workflow

The result of a Heartbeat synthetic test, scored across each link in the call path. Operata delivers the payload as a JSON array — one entry per agent or routing profile in the test. When it fires: When a Heartbeat test triggers its workflow. Configured per Heartbeat schedule; see the Heartbeat integration docs for cadence options. Payload:

CCP log files

CCP log lines streamed off the agent desktop as they appear. Scope: ERROR and WARN level log lines, plus INFO for ICE Connect Error only. When it fires: As log lines at those levels appear in the CCP. Operata does not buffer to contact boundaries — log events flow continuously while agents are signed in.