What is Live Chat?

Live chat is a synchronous messaging channel inside a shop that connects visitors with support staff or an automated assistant. A launcher in the page corner opens a window in which messages are exchanged in real time while the current page stays open. Typical placements are product pages, cart, checkout and order tracking. Live chat differs from asynchronous channels such as email because responses are expected within seconds or minutes, and the conversation context stays tied to the running session rather than to a ticket queue.

Definition

Implementations range from staffed chat during service hours to chatbots answering scripted questions and hybrid models that escalate from automation to a human agent. A widget loads a script, opens a persistent connection and passes context such as page URL, cart content or order status to the agent console. Routing rules, canned responses and queue handling belong to the operational side. Further considerations include data protection for transcripts, clear labelling when an automated system answers, availability windows that match the promise on the page, and the performance cost of a third party script on every template.

Why it matters

In a decoupled storefront, the chat widget is one of several third party scripts competing for main thread time. Loading it lazily after the first interaction or on an idle callback keeps initial rendering fast and protects Core Web Vitals. Session and cart context travel through the storefront API rather than through server rendered markup, so the component can pass a cart identifier or a customer segment to the chat service. Consent handling decides whether the widget loads at all. Because frontend and commerce backend are separated, chat can be embedded once as a shared component and reused across locales and channels.

Use cases

On product detail pages, chat answers questions about sizing, materials or compatibility before an item reaches the cart. In the cart and during checkout it addresses shipping costs, payment options and delivery dates, which are frequent reasons for abandonment. Post-purchase pages use the channel for order status, returns and invoice questions. Proactive triggers can open an invitation after a defined dwell time, although intrusive triggers on every template tend to irritate. Transcripts provide qualitative input on content gaps, and recurring questions often justify new FAQ blocks or clearer product data.

Related

Explore Conversational Commerce · Customer Journey.