Define what counts as a channel failure
Examples include messages not reaching the intended workspace, a widget breaking page controls or responders being unable to access unresolved conversations. Distinguish those from a single missed phone alert. Record what was observed and when without assuming the cause. The person responsible for the website and the person responsible for support should know who can change the customer-facing message or disable the widget if the failure prevents a usable service.
Keep the alternative visible and independent
Publish an appropriate contact route outside the widget so a customer can still find it when the widget does not load. State a realistic response expectation. Do not rely on a button inside the broken component as the only fallback. Test the contact information during ordinary operation, using a harmless internal exercise where authorised. A fallback is only useful if somebody owns the incoming work and knows how it will be reviewed.
Preserve unresolved promises
At the point of interruption, identify conversations already awaiting action through whatever supported records remain available. Avoid inventing a successful delivery state or blindly duplicating messages when the outcome is unknown. When access returns, reconcile the original records before sending new follow-ups. Keep the customer’s last promise and original context together. This reduces the chance of both silence and multiple conflicting replies after the same outage.
Restore in a small controlled step
Verify one fictional conversation, the correct recipient and the alternative route before announcing normal service. Record the configuration that passed and any remaining limitation. Review whether the incident exposed an avoidable dependency, such as one phone or one administrator, but do not redesign the whole stack without evidence. The goal is a trustworthy reduced mode and a tested return, not a promise that the selected vendor will never fail.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LiveChat manager handbook — Merchant documentation · livechat.com · Merchant-controlled · checked 2026-09-19
- LiveChat mobile notifications — Merchant documentation · livechat.com · Merchant-controlled · checked 2026-09-19