Skip to main content
Conversational analytics is Amazon Connect’s speech-analytics feature, formerly Contact Lens: it scores sentiment, detects categories, and produces transcript-level analytics. The Cloud Collector ingests three conversational analytics payloads per Contact — a real-time event (per rule match), a post-call event (when the Contact ends), and a summary (when AWS finishes processing). Collection is optional and requires the conversational analytics integration.
The summary payload below includes the conversation transcript: each utterance’s text, speaker, and sentiment. By default Operata receives the unredacted analysis files. To send only Amazon Connect’s PII-redacted output, deploy the Contact Lens Summary stack with processRedactedOnly set to true. Transcript lines still arrive, with personal data masked. Call recordings never leave your AWS account.

Schema

Amazon Connect emits three distinct conversational analytics payload shapes. The Cloud Collector forwards each to Operata as it arrives.

Real-time event

A real-time event fires every time a conversational analytics rule matches during an active Contact.

Post-call event

A post-call event fires once per matched rule after the Contact disconnects.

Summary

A summary payload arrives once conversational analytics finishes processing the Contact (typically within 15 minutes of disconnect).

Fields

Real-time event and post-call event

Both events share the same outer envelope. The description column flags any per-event differences.

Summary

The summary payload mirrors the AWS conversational analytics output schema. For the canonical output schema, see the AWS conversational analytics documentation. For the upstream Customer Journey Trace concept, see Customer Journey Trace.