eg

Live chat patterns

Live chat is a powerful conversion tool, but the placement decision shapes who uses it and when. The bubble maximises discovery, inline prompts maximise context, and a header link signals chat as part of the experience rather than a widget.

Intercom default

Bottom-right floating chat bubble

A circular bubble pinned to the bottom-right corner across every page, optionally with a teaser tooltip and unread badge. The default behaviour for every off-the-shelf chat platform.

Example of an Intercom-style bottom-right floating chat bubble over a product pagesearchhome · audio · headphonesStudio Wireless Pro$349.00colorsizeSMLAdd to bagAdd to wishlistNeed help?we reply in under 2 min1ecommerceguide.com

> what's good

  • +Always available, shoppers find it without learning the site IA.
  • +Off-the-shelf platforms ship this pattern, no engineering work to deploy.
  • +Teaser copy and unread badges measurably lift session-to-chat conversion when tuned.

> what's risky

  • ·Covers content on small viewports, frequent complaint on mobile carts and PDPs.
  • ·Looks identical across competitors, undermines brand differentiation.
  • ·Tooltip-on-load patterns feel intrusive and train shoppers to dismiss reflexively.
DTC

Inline contextual prompts within the PDP

Chat entry points placed beside the question they answer, ask about sizing near the size selector, ask about care near the material details. Replaces or complements the floater.

Example of inline contextual chat prompts placed within a PDP near sizing and material detailssearchwomen · denimTapered Selvedge Jeans$168.00size2426283032Not sure on size?chat to a fit specialistask →Material12oz Japanese selvedge denim98% cotton, 2% elastaneCare questions?ask about washing and shrinkageask →Add to bagecommerceguide.com

> what's good

  • +Highest-intent placement, the prompt arrives at the moment the question forms.
  • +Routes shoppers to specialists with the right context preloaded into the conversation.
  • +Differentiates the brand, contextual help reads as care rather than support.

> what's risky

  • ·Requires per-page authoring, scales poorly across thousands of products without templating.
  • ·If response times slip, an unused inline prompt looks worse than no prompt at all.
  • ·Hard to instrument cleanly, attribution between inline and floater needs careful tracking.

More trust & conversion patterns