Widget placement, and when not to show a chat launcher

Almost every website assistant ships with the same default: bottom right corner, every page, always visible, sometimes with a proactive message after a few seconds. Most teams never change it, which means the configuration on their site is a vendor default rather than a decision.

It is worth deciding, because the default has real costs on some pages and real value on others.

Where a launcher earns its place

• Pricing pages, where hesitation is highest and the question is usually specific.
• Documentation and help pages, where the visitor has already failed to find something.
• Feature and comparison pages, where evaluation questions surface.
• Checkout or signup flows, where an unanswered question ends the session.

Where it usually does not

• The blog, where visitors are reading rather than evaluating and a launcher is an interruption.
• Legal pages, where the visitor wants to read a document.
• Landing pages built for a single conversion action, where any competing element costs something.
• The homepage above the fold on mobile, where screen space is scarce.

That last one deserves emphasis. On a 390 pixel viewport a floating launcher occupies a meaningful share of the visible area and frequently sits on top of a primary CTA. Check this specifically. It is the most common mobile problem with any widget and it is invisible on a desktop screenshot.

Proactive messages

A message that opens itself after a delay converts better in some contexts and annoys reliably in others. The distinguishing factor is whether it is relevant to the page.

A generic "Hi, how can I help" that fires everywhere reads as automated and gets dismissed. A page specific prompt on a pricing page that names the actual common question can genuinely help. If you cannot write a page specific prompt worth reading, do not enable a generic one.

The accessibility floor

Whatever placement you choose, three things are not optional:

• The launcher is reachable and operable by keyboard.
• Opening the dialog moves focus into it, and closing returns focus to the launcher.
• The dialog can be dismissed with the escape key.
• It does not obscure content in a way that makes any part of the page unreachable, at any viewport width.

The brand argument

There is a reason premium software sites tend to use restraint here. A widget that shouts, follows and interrupts communicates something about how the company treats attention. A widget that waits until it is wanted communicates the opposite.

That is not a measurable argument and I will not pretend it is. But if you are building a product whose entire pitch is that it listens, the way it behaves on your own site is the first demonstration a visitor gets.