Glossary
Last updated:
November 2026

What is Customer Care Module?

Definition - Customer Care Module

Conviva's Customer Care Module lets support teams, and the AI agents working with them, see the details of a single viewer's streaming experience across the sessions they watched in a given time period, up to the last 30 days. Built on the quality of experience (QoE) data in Streaming Experience Insights (SEI), it gives each viewer one experience score and can open straight from a support case or over MCP (the protocol that lets an AI agent query a system directly). It lets your agents see what that viewer saw.

Why customer care needs viewer-level experience data

Aggregate dashboards tell you how the service is performing overall. They can't tell a support agent what happened to the one person on the other end of the ticket. That viewer might have watched three titles on three devices, and only one of those sessions went wrong. Finding it means knowing which session failed, why it failed, and whether anyone else was affected.

That last question matters most. If the problem belongs to this viewer alone, the fix is a device or home network conversation. If other viewers in the same city or on the same ISP are hitting it too, the ticket is a symptom of something bigger, and it belongs with your operations team. Customer Care Module answers both questions in one view, so agents resolve tickets faster and escalate only what needs escalating.

How Customer Care Module works

Customer Care Module starts with one score. Each viewer gets a Streaming Performance Index (SPI), a single number that shows the share of their streams that played well in the selected time period, with a count of the sessions that were impacted. Alongside it sit the metrics behind the score: plays, video start failures (VSF), connection-induced rebuffering ratio (CIRR), and video startup time (VST).

Below the score are the viewer's sessions, each marked as impacted or not. Drill into any session to see startup time, bitrate, error codes, CDN, ISP, and device. An AI summary then answers the question every agent needs answered: is this issue limited to this viewer, or shared across others in their city or on their ISP? For example, it might report that issues are limited to one viewer's Smart TV while other viewers in the same city and on the same ISP look healthy.

Teams can reach any viewer from wherever the work starts:

  • From a spike. Select a spike in Trends and see the impacted viewers for analysis.
  • Via a support case. Deep-link or embed into Salesforce, Jira, or your own tool, so agents open Customer Care Module straight from the ticket.
  • With Nexa. Ask Nexa to show a session's video, ads, CDN, and errors on one timeline.
  • From your AI agent. AI support agents pull the same view of a viewer's experience over MCP.

What Customer Care Module delivers

Answers inside the help desk. Agents shouldn't have to leave the ticket to understand it. One streamer links Salesforce cases to Customer Care Module and launches it from its own support tools, so the viewer's sessions are one click from the case.

Lookups at real scale. Customers use Customer Care Module to look up thousands of viewers every month, with full detail on each video session.

The failing ad, found. Ad problems are some of the hardest tickets to trace. In one session, Nexa tied five failed ad breaks to their creatives, right next to a CDN switch, on a single timeline.

Support that scales with AI agents. Because the same viewer view is available over MCP, AI agents handling first-line support work from the same session data as your human team.

This is the same experience expertise behind 10 Olympic Games, 20 Super Bowls, and 5 FIFA World Cup tournaments, now applied to every support ticket, one viewer at a time.

Getting started with Customer Care Module

Customer Care Module is built for streaming publishers, broadcasters, and the customer care teams that support their subscribers, especially those handling high ticket volumes around live events or running AI agents in their support queue. It runs on the Conviva platform alongside SEI, so publishers already measuring QoE with Conviva have the viewer and session data in place. From there, teams connect Customer Care Module to their help desk through a deep link or embed, or give their AI agents access over MCP.