Explain service performance
Move from a trend or exception to the interactions, routing, automation, and cases behind it.
Platform · Analytics & Voice of Customer
Connect service performance, customer feedback, and the evidence behind each outcome
Search interactions, inspect routing and automation traces, review governed recordings, analyze cases and quality, and export authorized evidence without separating metrics from the work that produced them.
Analytics & Voice of Customer operating journey
- 01
Detect
Identify a trend, exception, or service risk across the operating model.
- 02
Explain
Trace the condition to the customer work, configuration, provider, and decision path.
- 03
Act
Create governed follow-up and retain the evidence used to make the decision.
For 01
CX executives
For 02
Operations analysts
For 03
Governance teams
Where it fits
Own a clear part of the customer journey.
Connect this responsibility to the customer context, work, knowledge, policy, and evidence shared across OCXCenter.
Investigate decisions
Trace customer work to configuration versions, provider actions, human decisions, and outcomes.
Connect customer feedback
Review survey funnels, scores, comments, and operational correlations within privacy and cohort controls.
- A common operational narrative across channels and teams
- Faster investigation with evidence connected to each outcome
- Authorized reporting without losing policy and audit context
Product evidence
Historical investigation and customer feedback share governed context
Analytics owns retained search, traces, reports, exports, and retention while Live Monitor owns realtime state. Survey Metrics adds privacy-aware feedback trends and correlations without presenting relationship as causation.
Current product boundary
Historical investigation and customer feedback share governed context
Analytics owns retained search, traces, reports, exports, and retention while Live Monitor owns realtime state. Survey Metrics adds privacy-aware feedback trends and correlations without presenting relationship as causation.
Evidence to review
- Policy-aware retention
- Redacted support evidence
- Authorized export
- Correlated audit and trace context
- 01Connected analytics
- Conversation, routing, automation, case, quality, and workforce events share common context.
- 02Traceable decisions
- Investigators can move from an aggregate condition to the version, action, and outcome behind it.
- 03Governed evidence
- Playback, export, retention, and support access remain role- and policy-scoped.
- 04Operational observability
- Structured logs, traces, metrics, and health signals support accountable operation.
Operating capability
Everything needed to move this responsibility forward.
Capabilities connect to the same customer journey rather than operating as isolated add-ons.
- 01Connected analytics
- Conversation, routing, automation, case, quality, and workforce events share common context.
- 02Traceable decisions
- Investigators can move from an aggregate condition to the version, action, and outcome behind it.
- 03Governed evidence
- Playback, export, retention, and support access remain role- and policy-scoped.
- 04Operational observability
- Structured logs, traces, metrics, and health signals support accountable operation.
How work moves
Follow the work from entry to accountable outcome.
Every stage has a clear owner, transition, and retained evidence.
- 01
Detect
Identify a trend, exception, or service risk across the operating model.
- 02
Explain
Trace the condition to the customer work, configuration, provider, and decision path.
- 03
Act
Create governed follow-up and retain the evidence used to make the decision.
Give leaders a defensible path from service performance to the work, policy, and action that shaped it.
Role-specific workflows
Give each team the workflow it actually operates.
Keep responsibilities clear while the customer journey remains connected.
CX executives
01Detect
Identify a trend, exception, or service risk across the operating model.
- 1Detect
- 2Explain
- 3Act
Operations analysts
02Explain
Trace the condition to the customer work, configuration, provider, and decision path.
- 1Detect
- 2Explain
- 3Act
Governance teams
03Act
Create governed follow-up and retain the evidence used to make the decision.
- 1Detect
- 2Explain
- 3Act
Adoption path
Start with one workflow. Expand without fragmenting the experience.
Sequence configuration, integration, testing, and rollout around measurable service outcomes.
- 01
Define the questions
Choose operational decisions, audiences, metrics, dimensions, evidence, and permitted drill-down.
- 02
Connect the events
Map versioned sources, identities, timestamps, correlation keys, retention, and reconciliation behavior.
- 03
Certify the decisions
Validate metric definitions, tenant scope, freshness, exports, recovery, and report delivery with owners.
Evaluation questions
Resolve these before rollout.
- 01Which operational decisions must each dashboard, search, or report support?
- 02How are interaction, routing, automation, case, quality, and customer events correlated?
- 03Which roles may inspect, export, schedule, or retain each class of evidence?
Enterprise integration and governance
Define authority, dependencies, and controls before launch.
Review integration boundaries and governance controls together so deployment assumptions remain explicit.
Integration boundaries
- Analytics sources publish through versioned event contracts
- Content classes retain independent policies
- External BI export remains explicitly authorized
Governance controls
- Policy-aware retention
- Redacted support evidence
- Authorized export
- Correlated audit and trace context
Connected product family
Continue the customer journey.
Evaluate it as one system