Before you start
- An Operata account with Admin role.
- The contact center platform you operate (Amazon Connect, Genesys Cloud, or NICE CXOne) administered by you or a team you can reach.
Contact center platforms
Pick the platform that hosts your contacts.- Amazon Connect — Stream Contact Trace Records, Contact Lens, Contact Flow Logs, and Lex data into Operata through the Cloud Collector in your AWS account.
- Genesys Cloud — Stream conversation analytics and platform events through Amazon EventBridge plus a read-only OAuth client; the Operata Fetcher Service handles enrichment.
- NICE CXOne — Stream interaction records and softphone telemetry into Operata. (Overview and install scope landing now; full runbook coming in a later release.)
Browser-side data collection
Every contact center integration pairs with the Agent Experience Collector — the browser extension that captures machine, network, and agent-side telemetry per contact.- Agent Experience Collector — Overview and installation paths for Chrome and Edge.
- Chrome extension — Install on Google Chrome.
- Edge extension — Install on Microsoft Edge.
- VPN bypass URL — Configure when agents work behind a corporate VPN so Operata sees the true ISP and network location.
Observability backends
Forward Operata signals to your existing observability stack.- Observability backends — Datadog, Splunk, New Relic, and other destinations Operata can ship Amazon EventBridge events to.
Verify
In the Operata console, open Group Settings > Integrations. The integrations you have installed appear with statusActive. Each installed integration also lists its current Group ID binding and the AWS region it streams from.
Related
- Architecture overview — How the pieces fit before you commit to a deployment shape.
- Concept: Cloud Collector — The AWS-side ingestion service Amazon Connect integrations deploy.
- Concept: Customer Journey Trace — How Operata links contacts across integrations into one trace.
- Overview — Start here for a full-product orientation.