1. Why you need a written contingency plan
  2. The six typical failure scenarios
  3. The roles: who decides, who speaks, who switches
  4. What happens in an incident: four escalation steps
  5. Before: what you agree on before the event
  6. During a stream failure: communicating with viewers
  7. After: recording, new date and post-mortem
  8. How MEETYOO Show supports your contingency plan
  9. Your runbook in 6 steps
  10. Conclusion
  11. FAQ

When the stream drops: a contingency plan for live webcasts

Encoder down, line dead, picture frozen: with this runbook, IT and production know who does what in the first 60 seconds. Includes an Excel template to download.

When the stream drops: a contingency plan for live webcasts

Picture this: Thursday, 9:58 am, the earnings call starts in two minutes, and 1,400 viewers are on the web. At 10:07 the CFO's picture freezes. There is no contingency plan for this webcast, and in the control room everyone waits for someone else to decide.

These seconds decide whether a glitch becomes an incident. Usually nobody agreed beforehand who decides, who speaks and when to switch to plan B.

A contingency plan for live webcasts puts these decisions in writing. You download the Excel template with runbook, checklist, roles and message templates for free and adapt it to your setup. It works for IR, internal communications and marketing webcasts.

MEETYOO Show supports the plan with automatic switching to a backup source in the managed service. Chat and Q&A keep running when the video fails.

Why you need a written contingency plan

You cannot rerun an earnings call. You cannot rerun a CEO townhall for 5,000 employees either, at least not without losing face. With price-sensitive content there is another risk: if part of the audience gets information later or not at all, a technical problem can become a compliance issue for IR and legal.

At the same time, live webcasts are distributed systems. Between the camera and the viewer sit the speaker setup, the network at the production site, ingest, the platform, delivery and the viewers' corporate network. Any of these can fail. A contingency plan makes sure you know within seconds which part is affected and which action belongs to it.

Rule of thumb: If you only discuss who decides once something breaks, you lose minutes in which your audience gets no information. Agree on the decision maker, time limits and message templates beforehand, and rehearse them once.

The six typical failure scenarios

ScenarioTypical symptomFirst actionWhere MEETYOO Show helps
Encoder or signal at the production site failsPicture black or frozen for everyoneSwitch to the backup encoder or backup sourceIn the managed service, the platform automatically switches to a backup source. The MEETYOO encoder can use a webcam as a backup.
Internet line at the production site dropsStuttering, then failure for everyoneActivate the second line (different provider or cellular)On request, our team handles technical planning and rehearsals (expert service).
Remote speaker loses connectionOne speaker missing, the rest runsHost bridges the gap, speaker rejoins by phoneSpeakers join by webcam or phone (managed service).
Audio fails, picture runsSilent pictureCheck microphone and mixer, activate audio backup–
Platform or delivery disruptedMany viewers report problems at once, production sends a clean signalEscalate to platform support, inform viewersLive delivery runs via a CDN. Managed production and expert support are available.
Viewers' corporate network blocks the streamOnly one site or network segment affectedInvolve internal IT, offer an alternative (e.g. phone dial-in)Phone dial-in as a workaround (Enterprise plan).

The key diagnostic question is: Is everyone affected, or only some viewers? If everyone is affected, the problem is usually on the sending or platform side. If only one site is affected, it is usually in the viewers' network.

The roles: who decides, who speaks, who switches

A contingency plan needs names for four core roles. In small teams one person can cover two roles, but never decision maker and technology at the same time.

  1. Incident lead (decision maker): decides on switching, pausing or cancelling. For IR this is often the head of investor relations, for internal comms the head of communications.
  2. Technology/production: diagnoses, switches to backup, stays in touch with platform support.
  3. Host: bridges the gap on stage or on the phone and reads prepared messages.
  4. Viewer communication: posts notices via broadcast, in chat or Q&A, emails registrants and updates internal channels (e.g. the intranet).

Note a deputy for each role and a phone number that does not depend on the production site's internet line.

Hybrid event production: production team in the control room during a live webcast
Hybrid event production: production team in the control room during a live webcast

What happens in an incident: four escalation steps

Time limits take the decision off your shoulders under stress. Adapt them to your format, but set them in advance. After the fourth step comes the follow-up.

Time since failureStepWhat happens
0 to 30 secondsDetectTechnology confirms who is affected: check confidence monitor, viewer player and platform status
30 seconds to 2 minutesSwitchActivate backup source, second line or phone dial-in for speakers. Host bridges the gap
2 to 5 minutesInformPost the "short technical interruption" message via broadcast, in chat, Q&A and internal channels
From 5 to 10 minutesDecideIncident lead decides: continue, pause with a new start time, or cancel with a new date

Important for diagnosis: the viewer player runs a few seconds behind the live signal. With MEETYOO Show, latency is at least around 5 seconds, depending on the setup. If you only watch the player, you see a failure later than in the production feed and may think a fixed problem is still ongoing. Always watch both.

Before: what you agree on before the event

  • Second signal path: a backup encoder or backup source, ideally on a second internet line from a different provider.
  • Speaker fallback: for each remote speaker it is clear whether they join by webcam or phone, and there is a phone number as plan B.
  • Phone dial-in for viewers: for IR calls, phone access for analysts is often standard. It is also your audio fallback if the video fails. How to merge phone and web questions into one queue is covered in our article on earnings call Q&A.
  • Pre-recorded content: record intros, statements or whole segments that don't need to be live in advance. What isn't live can't fail live.
  • Message templates: notices for chat, Q&A, email and intranet in every event language, approved by communications and, for IR, by legal.
  • Dress rehearsal with a failure: pull a cable on purpose once during the rehearsal. Only then do you know whether switching and communication work. With MEETYOO's expert service, our team handles technical planning, rehearsals and live direction.

During a stream failure: communicating with viewers

Silence is worse than a glitch. When the picture is gone and nothing happens, viewers drop off. A short notice gives them a reason to stay.

In MEETYOO Show, chat and Q&A keep running even if the video fails. Use that: these channels let you keep your audience informed, answer questions and stop viewers from dropping off. You can also show notices to all viewers manually via broadcast.

Typical message templates:

  • "We have a short technical interruption and will be back in a few minutes. Please stay on this page."
  • "The broadcast will resume at XX:XX. We'll make the full recording available afterwards."
  • "Unfortunately we have to cancel the event. You'll receive the new date and the recording by email."

Careful when ending the session: when the presenter ends the session in MEETYOO Show, attendees see a "Thanks for watching" page and are forwarded to a redirect URL if one is set. So don't end the session too early during an incident if you only want to pause.

After: recording, new date and post-mortem

  • Check the recording: is the part before the failure complete? Is a section missing?
  • Release on demand deliberately: in MEETYOO Show, you always set on-demand release yourself. Make this a fixed step in your runbook, especially after an interruption, and release the recording only after checking it. For IR, agree the release with legal so everyone receives the information at the same time.
  • New date: if you have to cancel, the new date can run as a Pseudo-Live premiere: recorded in advance, with a fixed start time, chat and Q&A live. More in our article on Pseudo-Live.
  • Post-mortem within 48 hours: what happened, when was it detected, how long did switching take, what do we change? Add the findings straight to the runbook.

How MEETYOO Show supports your contingency plan

Meeting tools are designed for collaboration. MEETYOO Show is built for events that cannot be repeated.

Part of the planWhat MEETYOO Show offers
Second signal pathIn the managed service, the platform automatically switches to a backup source when the main signal stalls or drops. The MEETYOO encoder can also use a webcam as a backup source.
Support when it countsManaged production and expert support are available. The expert-managed service is optional from the Starter plan and fully managed in the Enterprise plan.
Speaker fallbackSpeakers join by webcam or phone (managed service).
Audio fallback for viewersBrowser access without downloads, plus web and phone dial-in (PSTN) in the Enterprise plan, set up as a managed service. Phone participants start in listen mode and can ask to speak.
Situational awarenessThe viewer curve in analytics runs live during the event. A sudden drop shows you whether everyone or only some viewers are affected.
InteractionChat and Q&A keep running if the video fails, so your audience stays informed. Chat, Q&A and polls work with 10,000+ viewers (Enterprise plan). More on the engagement tools.
Notice to viewersYou show notices to all viewers manually via broadcast. Overlays in the video, by contrast, only work while the stream is running.
DeliveryHosted on EU servers, ISO 27001-certified and GDPR-compliant. Live delivery runs via a CDN. More on the IT & Security page.
Follow-upOn-demand archive with chapters, key moments and transcript, plus AI features for analysis. You decide when on-demand access is released.

Which plan? Phone dial-in, unlimited concurrent viewers and the fully managed service are part of the Enterprise plan. You can add an expert-managed service from the Starter plan as an option. All engagement tools and the AI features (with usage limits) are included in every plan, including the Forever Free plan: permanently free, no expiry date, no credit card required. For events where an outage has consequences, we recommend the Enterprise plan with the fully managed service.

MEETYOO Show does not offer simulcast to YouTube or LinkedIn, and no live DVR to rewind during a running stream. A second, parallel delivery path via social platforms is therefore not part of your contingency plan with MEETYOO Show. In return, backup switching, phone dial-in, chat and Q&A live in one platform.

Your runbook in 6 steps

  1. Download the template and enter the event in the "Runbook" tab.
  2. Assign roles: incident lead, technology, host and communications, each with a deputy and a phone number.
  3. Go through the scenarios: set a first action and an owner for each of the six scenarios.
  4. Set time limits: when do you switch, inform, cancel?
  5. Get message templates approved in every event language.
  6. Dress rehearsal with a failure: switch over once on purpose and time it.

Download: Live webcast contingency runbook (XLSX) with the tabs Runbook, Checklist T-7 to T+1, Roles & contacts, Message templates and How to use.

Conclusion

With a second signal path, fixed roles and prepared messages, you switch over in seconds. Rehearse the process once and you can reuse it for every event that follows.

MEETYOO Show takes part of the work off your hands: in the managed service, the platform handles the switch to the backup source, chat and Q&A keep your audience informed when the video fails, and expert support is available. Companies such as Commerzbank, Mercedes-Benz and Allianz Global Investors rely on MEETYOO Show, and banks and public authorities trust our security and EU servers. We are happy to show you what that looks like for investor relations and for your setup.

FAQ

What should you do when a live stream drops?

First find out who is affected (0 to 30 seconds). Then switch to the backup source or second line (up to 2 minutes) and inform your audience via broadcast, chat and Q&A (2 to 5 minutes). From 5 to 10 minutes the incident lead decides: continue, pause with a new start time, or cancel with a new date. Don't end the session too early.

What belongs in a contingency plan for live webcasts?

Roles with deputies, the typical failure scenarios with a first action, fixed time limits for switching, informing and cancelling, approved message templates for viewers, and a plan for the recording and a new date.

How quickly should you switch to a backup stream?

Set a fixed limit, typically between 30 seconds and 2 minutes. Every minute of waiting costs you viewers, and a fixed limit spares you the discussion under stress.

Is phone dial-in a useful fallback?

Yes. If the video fails, viewers can keep following the audio by phone. In MEETYOO Show, web and phone dial-in (PSTN) is available in the Enterprise plan, set up as a managed service.

What happens to the recording if the stream drops?

In MEETYOO Show, you always set on-demand release yourself. After an interruption, check the recording for completeness and then release it deliberately.

How often should you rehearse the contingency plan?

At least once before every high-risk event, such as earnings calls, CEO townhalls or works meetings. The rehearsal should include a deliberate failure, otherwise you only test the normal case.

Can your next event afford an outage? We walk through backup concept, roles and runbook for your setup.

Request a conversation

You might also find this useful