Reseller desk
Plan support for a high-demand live event
Prepare a support response for a busy live event around the authorized feed, expected audiences and known failure symptoms.
Define what customers can actually watch
Start with the competition, start time, territory and confirmed carrying service. Check the current broadcaster or rights-holder listing for the named event. A general sports bundle can contain several channels with related branding. Write the actual service and feed on the preparation sheet, and record which customers have confirmed access.
Next write the time in the event's local zone and the zone used by your support desk. A single event across several territories can have different authorized viewing routes. Prepare support responses for each published route and avoid promising a carriage decision until you can identify the exact edition.
Measure demand in simultaneous sessions
Imagine you support 34 households that each usually open one screen during a game. Eight expect a second screen. That makes 42 potential simultaneous sessions if the affected customer agreements include both screens. The number is a planning estimate. Check the actual allowance at the account level and use the supplier’s documented escalation route for capacity questions.
| Signal near kickoff | First action | Evidence to keep |
|---|---|---|
| Several viewers lose the same channel | Open one incident and verify the named edition | First failed time and a healthy reference feed |
| One device cannot start at all | Check supported version and playback mode | Device, app version and error |
| One household loses the first screen when the second joins | Check the confirmed concurrent-stream limit | Account allowance and order of device starts |
| Video works but the event is absent from guide | Match the programme row and time zone | Guide ID, programme name and broadcaster time |
Set up the desk before the first ticket
Give one person the live status note and a second person the individual queue. Draft a short update with the named service, timestamp and what works. Put the next update time in the note even when a fix depends on the supplier. A real availability example is one authorized stream from the intended region on a supported screen.
After the event, keep a timeline from first report to recovery and note the work that changed the outcome. Use that to improve the next event’s setup sheet. If you had three unrelated device problems plus one shared incident, keep those counts separate so the next preparation addresses the right issue.
Agree on escalation and customer communication before the event. Test the same lawful viewing route that customers will use.
How it works
Separate connection limits, source outages and device problems when a peak-time incident arrives. A written escalation plan identifies who receives a report, what evidence they need and when to publish a customer update.
What to do
- Record event, territory, supported feed and start time.
- Write a customer evidence checklist that excludes account tokens.
- Confirm the escalation contact and how to distinguish partial and whole-service incidents.
- Track response and recovery time separately.
Sources and further reading
- RFC 8216 · HTTP Live Streaming · Playlist and segment behavior where HLS is the transport.