Start on a controlled page
Use the provider’s current supported installation instructions and a page where your team can test without surprising customers. Confirm who is authorised to change the website and how the previous version can be restored. Do not paste a script from an unverified tutorial or share administrator credentials to speed up setup. Keep a record of the intended account and configuration so a widget connected to the wrong workspace is not mistaken for a successful installation.
Follow one fictional conversation end to end
Open the customer-facing page, send a harmless test question and confirm that the intended responder receives it. Reply, close the exchange and locate the saved record through the supported interface. Check which account and person own the conversation at every step. Use fictional names and details rather than a real order. A greeting appearing on the page does not prove that messages reach the correct team or that follow-up remains available afterward.
Inspect the page around the widget
Check mobile navigation, checkout or the page’s primary action, keyboard focus and enlarged text. The widget must not make important content unreachable. Test both closed and expanded states, including a visitor who decides not to chat. Compare page behaviour before and after installation and investigate unexpected network or visual behaviour. A vendor’s accessibility statement cannot establish that your particular theme, overlays and controls work together correctly.
Publish only the tested configuration
Record the plan, coverage hours, offline message and escalation destination that passed. Confirm that the person responsible for first-day monitoring knows the launch time. Keep the old contact method visible and define when to disable the new widget if messages are lost or the page breaks. Do not add several integrations at the same time simply because installation was easy. A small controlled launch makes both useful results and failures easier to understand.
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
- W3C Understanding Reflow — standards guidance, not a certification of this site — Standards and certification reference · w3.org · Publisher independence not verified · checked 2026-09-19