Live Broadcast Streaming Outage Ticket Resolution Script

Role: Principal Live Operations Support Engineer specializing in broadcast OTT streaming platforms.

Context

• Live Broadcast Event: {{streaming_event_name}}
• Observed Technical Failure: {{error_symptom}}
• Impacted Audience Segment: {{affected_user_tier}}
• Engineering Triage Update: {{root_cause_status}}
• Projected Incident ETA: {{turnaround_time_estimate}}
• Approved Goodwill Concession: {{compensation_offer}}

Task

Draft a phased, empathetic customer support script for tier-1 and tier-2 agents responding to high-priority tickets during a live media broadcast disruption, preventing churn while managing viewer expectations.

Method

1. Review the specific live event context {{streaming_event_name}} and categorize ticket volume spikes by {{error_symptom}}.
2. Formulate an immediate, human-centered opening empathy statement that validates the viewer's frustration without admitting unconfirmed liability.
3. Translate engineering telemetry from {{root_cause_status}} into clear, non-jargon viewer updates.
4. Structure a primary diagnostic step to eliminate client-side hardware, app cache, or local bandwidth constraints.
5. Provide a vetted, secondary platform workaround (e.g., web fallback, bitrate cap override) while engineering works on the core fix.
6. Integrate policy-approved goodwill messaging regarding {{compensation_offer}} tailored strictly for {{affected_user_tier}}.
7. Establish transparent expectation timing using {{turnaround_time_estimate}} and outline follow-up notification triggers.

Constraints

• MUST maintain an apologetic yet authoritative tone aligned with broadcast entertainment brand guidelines.
• MUST NOT guarantee exact restoration minutes if engineering status remains unconfirmed.
• Content MUST provide distinct variations for live chat, asynchronous email, and SMS macro formats.
• Technical steps MUST be executable within 60 seconds by a non-technical end user.

Output format

• Section 1: Immediate Opening Macro (3 variations: Chat, Email, SMS; under 60 words each).
• Section 2: Interactive Troubleshooting Flow (Numbered agent-caller dialogue script with 3 branching responses).
• Section 3: Concession & Closing Script (Exact wording for applying {{compensation_offer}} and sign-off).

Self-review

• Does the script explicitly address {{error_symptom}} without using internal engineering jargon?
• Are all 6 context variables seamlessly incorporated across the sections?
• Is the concession gate correctly scoped to {{affected_user_tier}}?