Streaming Broadcast Incident Triage Matrix

Role: Senior Streaming Operations Tier-3 Support Lead specializing in high-concurrency OTT live event incidents.

Context

• Streaming platform architecture: {{platform_name}}
• Geographic regions experiencing degradation: {{affected_regions}}
• Broadcast profile and stream delivery format: {{stream_type}}
• Current concurrent viewer audience: {{concurrent_viewers}}
• Inbound support ticket volume surge rate: {{ticket_volume_spike}}
• CDN telemetry and client error codes: {{error_codes}}

Task

Construct an incident triage and escalation matrix that maps incoming user-reported playback failure tickets against technical telemetry to determine immediate tier routing, customer response macros, and engineering escalation paths.

Method

1. Correlate user ticket clusters against telemetry logs identified in {{error_codes}} across {{affected_regions}}.
2. Evaluate audience scale threshold using {{concurrent_viewers}} to assign baseline operational urgency.
3. Segment playback failures by {{stream_type}} to isolate encoder origin issues from edge CDN delivery drops.
4. Calculate containment urgency based on the velocity reported in {{ticket_volume_spike}} on {{platform_name}}.
5. Formulate rapid-response macro templates for Tier-1 frontline agents for each major error profile.
6. Determine explicit routing boundaries for handing tickets over to network operations versus playback engineering.
7. Establish SLA turnaround targets and customer status update cadences for each severity tier.

Constraints

• MUST classify tickets into exactly four severity tiers (P1 to P4).
• MUST NOT prescribe generic device troubleshooting for verified platform-wide CDN outages.
• Every severity tier must include an assigned engineering routing target and a subscriber-facing macro snippet.
• Table columns must remain consistent across all triage categories.

Output format

• Executive Summary (max 100 words summarizing primary failure surface)
• OTT Incident Triage Matrix (Markdown table with columns: Severity Level, Error Profile, Engineering Routing, SLA Target, Tier-1 Response Directive)
• Incident Communication Protocol (3 actionable operational rules for frontline teams)

Self-review

• Confirm all context variables ({{platform_name}}, {{affected_regions}}, {{stream_type}}, {{concurrent_viewers}}, {{ticket_volume_spike}}, {{error_codes}}) are actively integrated into the matrix logic.
• Verify table markdown formatting is valid and all required columns are populated.
• Ensure P1 through P4 escalation rules differentiate between individual client bugs and broad stream delivery degradation.