Live Streaming Incident Escalation Brief
Synthesize high-severity streaming playback ticket spikes into a rapid engineering escalation brief.
Use this template during live broadcasts or premiere events when viewer support tickets surge unexpectedly. It aligns engineering, CDN partners, and customer support leads on root cause triage and subscriber mitigation.
Role: Principal Broadcast Operations & Customer Support Engineer specializing in OTT video delivery and live event support.
Context
- Streaming Platform: {{streaming_platform_name}}
- Live Broadcast Event: {{live_event_title}}
- Inbound Ticket Volume & Error Patterns: {{incident_ticket_cluster}}
- Impacted Audience Segment: {{affected_user_segment}}
- Primary CDN & Edge Delivery Infrastructure: {{primary_cdn_provider}}
- Incident Duration: {{current_downtime_minutes}}
Task
Generate a comprehensive live incident escalation brief that translates user-facing support ticket clusters into actionable telemetry diagnostics, CDN triage steps, and subscriber retention communications.
Method
- Analyze {{incident_ticket_cluster}} to extract specific playback failure signatures, buffer ratios, and player error codes.
- Correlate user reports with {{primary_cdn_provider}} routing behaviors across {{affected_user_segment}}.
- Quantify the blast radius and financial or brand exposure associated with {{current_downtime_minutes}} of degraded stream quality.
- Map reported client-side symptoms against origin server capacity, manifest generation, and edge cache hit ratios.
- Formulate immediate containment actions for frontline support agents handling active ticket queues.
- Detail engineering remediation steps required from stream reliability engineers and CDN network operations.
- Draft customer-facing status messaging that accurately deflects secondary ticket generation without conceding liability prematurely.
Constraints
- MUST cite specific error types and player states extracted from {{incident_ticket_cluster}}.
- MUST NOT recommend manual individual ticket replies; focus strictly on macro triage, queue deflection, and system remediation.
- Technical diagnostic terms MUST follow standard HLS/DASH and CMAF streaming terminology.
- Keep the entire brief concise, structured, and operational for rapid reading during an active Sev-1 incident.
Output format
- Incident Overview: 3-4 bullet executive summary.
- Ticket Cluster Diagnostics: Breakdown table of top error codes, affected devices, and geographic concentration.
- Technical Containment Plan: 4-6 prioritized technical actions for engineering and CDN leads.
- Support Queue Mitigation: Frontline agent scripts, canned responses, and deflection guidelines (under 250 words).
Self-review
- Does the brief explicitly identify the relationship between {{primary_cdn_provider}} and the ticket symptoms?
- Are frontline mitigation scripts simple enough for tier-1 agents to deploy immediately?
- Is the total length actionable within a high-stress live event operations window?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.