Redesigns quietly delete chat
The chat snippet lives in the site template — exactly the file a redesign replaces. Nobody decides to remove chat; it simply is not in the new layout, and the team discovers it weeks later as an unexplained quiet spell. Treat chat as a first-class item on the redesign checklist, not something to re-notice after launch.
Before launch: the carry-over list
- The snippet goes into the new base template on day one of the build — before-</body>, same as the original install — so every staging review happens WITH the widget present. A layout reviewed without the launcher will collide with it later.
- Remap page-based triggers. Proactive invitations and routing rules keyed to URLs break silently when /pricing becomes /plans. Export your trigger list, walk it against the new URL map, and fix each rule as part of the redirect work you are already doing.
- Refresh the widget's look deliberately. A redesign changes your palette; the launcher configured three years ago may now clash or vanish against the new ground. Re-pick launcher color and label with the new design system — keeping contrast and placement rules intact.
On the staging site, run the full loop once per key template: launcher visible and tappable at 375px, panel opens and fits, pre-chat form submits, offline state renders. The widget reports the URL it loads from, so staging traffic is distinguishable from production in your visitor log — test freely.
Launch week: chat is your error console
Whatever the redesign broke, visitors will report it in chat before your analytics flag it: the missing page, the button that does nothing on Safari, the form that eats input. Staff launch week like a product launch — spike-window coverage, tag-everything, escalate patterns same-day. The redesign retro should cite transcripts, not hunches.
After: re-audit the knowledge base
Help articles are full of "click the menu, then Settings" instructions that the redesign just falsified. Sweep the knowledge base for navigation references and screenshots of the old design — every stale one is now actively misleading, and an AI assistant trained on stale articles gives confidently stale answers. Retrain the AI after the sweep, not before.
The pre-launch checklist in detail
Chat breaks during redesigns for mundane reasons, and nearly all of them are catchable before
launch if someone owns the check. The failure is almost never that people forgot chat existed
— it is that they verified it on one page and assumed the rest.
Confirm the snippet is present on every template, not every page. Sites typically have several
— homepage, article, product, checkout, help, landing pages — and each is a separate
opportunity to lose it. Checkout and landing pages are the most commonly missed and the most
expensive to lose.
Check the content security policy if the site has one. A policy that does not allow the chat
provider’s domain blocks the widget entirely, and the failure is silent: the page looks
perfect, no error is visible to a casual look, and the widget simply never appears for anyone.
This is the single most common cause of chat vanishing after a technical relaunch.
Verify placement on a real phone. New layouts frequently introduce sticky headers, cookie
banners and floating buttons that overlap the widget on small screens, and a widget hidden behind
another control is functionally absent.
Finally, re-check the settings that live in the widget rather than the site: office hours,
routing, the pre-chat form, and any page-targeted invitations, since invitations are usually
configured against URLs that the redesign has just changed.
Redirects, URLs and the invitations that follow them
A redesign usually rewrites the URL structure, and anything configured against a URL quietly
stops matching. Proactive invitations targeted at the old pricing path, rules that route
checkout-page chats to a particular team, reporting that groups conversations by page — all
of it silently degrades rather than failing loudly.
Make a list of everything keyed to a URL before launch and re-point it after. This list is
short and nobody ever has it, which is why the same problem recurs at every relaunch.
Watch the transcripts in the first week specifically for navigation confusion. Chat becomes an
excellent usability instrument immediately after a redesign: visitors asking where something went
are reporting a real regression, and they will tell you within hours, long before analytics shows
a trend. Treat the first week’s chats as launch telemetry and read them daily.
Keep the old knowledge current too. Canned responses and help articles that reference the old
navigation — “click Account in the top right” — become wrong the moment
the new design ships, and agents will send them confidently for months unless someone sweeps
them.
What to measure
Compare chat volume for the fortnight after launch against the fortnight before. A sharp drop
is almost never reduced demand; it is a missing snippet, a blocked domain, or a widget hidden
behind new page furniture. Treat any fall over about a fifth as a technical fault until proven
otherwise.
Watch the mix of questions rather than only the count. A rise in “where do I find”
questions is the clearest signal that the new navigation is not working, and it appears
immediately. Track it by page as well, since the drop is often confined to one template that
everybody assumed was covered.