Best Live Chat for Ecommerce: Order Status, Live Stock, Exact Returns

The other thing specific to a store is seasonality. Your volume triples in November, and three of the five pricing models in this market bill you for that. This page covers the requirements, the meters, what peak does to each, and the questions to ask before you install.

What your conversations are actually about

Sample fifty of last month's chats before you shop. The mix is remarkably consistent across stores and it decides which product suits you.

The Asyntai column is ours, so read it as a disclosure. We answer from what your store publishes, which covers the returns, sizing and delivery rows outright. The last row routes to a named person by design: a customer whose order has gone wrong should reach your team, not a machine.

The pattern that matters: the top two groups are almost entirely answerable from data and pages you already have, and they are also the ones that arrive at 11pm. That is the whole ecommerce chat argument in one sentence.

If your widget cannot answer "where is my order" without a login, it is not deflecting the thing you needed deflected.

What the tools cost

We make Asyntai, so read that row as a disclosure. Note the spread of meters: nothing, tickets, conversations, workspace, agents and messages. Six products, six different things being counted, and that difference matters more on a seasonal store than anywhere else.

What peak season does to each meter

This is the ecommerce-specific arithmetic and it is worth doing before you sign in March.

Then ask the follow-up question people forget: can you move back down in January, or does the upgrade lock for the term? Some plans flex and some do not, and that single answer can be worth more than the difference between two products.

The Gorgias detail worth knowing

Gorgias prices on monthly ticket volume rather than per agent, which is genuinely good for a small team with high order volume. Its AI Agent is a separate charge of roughly $0.90 to $1.00 per resolved conversation.

The part that catches people: an automated resolution also counts against your ticket allowance. One conversation handled entirely by AI is billed twice, once as an AI resolution and once as a ticket. None of that is hidden, but it inverts the usual assumption that automation reduces your plan cost, and it is worth modelling before you turn deflection up.

The three requirements, tested properly

Order status without a login

Most customers asking where their order is are not logged in and will not log in to ask. Test this in a trial with a real order number and no session. If the answer is "please log in to your account", your largest conversation group still reaches a person.

Ask also what identifiers it accepts. Order number, email, postcode. The more paths in, the fewer conversations bounce.

Live stock, not a cached page

A shopper asking about a size needs an answer from current inventory. Ask every vendor whether the tool reads live product data or a periodic snapshot, and how often the snapshot refreshes. A confident "yes we have that" on an out-of-stock item is a cancelled order and an angry email.

Your exact returns policy

Pick a period just outside your window and ask. "Can I return this after 40 days?" A tool that answers from your actual policy page says no and explains the exception. A tool that guesses an industry standard says yes, and you either honour it or start the conversation you were trying to avoid.

This is the single highest-risk failure in ecommerce chat, because a wrong policy answer is a commitment your customer service team then has to unpick.

The hours question, for stores

Look at when your orders are placed. On most consumer stores a large share of sessions land in the evening and at weekends, which is precisely when nobody is staffing chat.

Most stores need both, in that order: automation answering the top two conversation groups, and a person for the fifth group where something has gone wrong. The mistake is buying only the second and wondering why it does not scale in November.

Where to put the widget, and where not to

• Product pages: yes. This is where questions block orders. Trigger on time on page or a second visit rather than immediately.
• Delivery and returns pages: yes. Somebody reading your returns policy has a specific question the page did not answer.
• Checkout: probably not. Test it before you assume. A bubble over the pay button on mobile costs more than any conversation it starts.
• Order confirmation and tracking: yes. The natural home of your highest-volume question.
• Homepage: rarely worth it. Generates volume and very little revenue, which is how proactive chat gets its bad reputation.

How to choose, by platform

Where your store runs changes the install path and sometimes the shortlist, even though the chat service behind it is usually the same product at the same price.

Multilingual stores

If you ship internationally, check your analytics for the share of sessions that are not in your default language. Stores that never planned to be international routinely find a quarter of visitors are, and that single number eliminates several tools immediately.

Ask three things of any multilingual live chat option: does it detect the visitor's language automatically, does it answer from your translated content or only the default version, and does each additional language cost extra. The third question catches people, because languages are commonly an add-on rather than a feature.

The Asyntai column is ours, so read it as a disclosure. It says the same thing on nearly every row for a reason: it is a script tag, so there is no app, plugin or extension to buy. On Magento that saves the $49 to $349 plus the edition surcharge. On Squarespace it still needs the Business plan, because that constraint belongs to Squarespace, not to the chat tool.

Two platform-specific points worth acting on. On Shopify, implementing live chat means trying the free native app first, because it changes what you need to buy. On Magento and Squarespace, there is a cost simply to be allowed to install anything, and it belongs in your comparison.

Live chat and conversion, honestly

You will meet a statistic saying chat users convert 2.8 times better, and another saying chat lifts site conversion by 10% to 30%. Both are recycled through vendor marketing and both have the same problem: people who start a chat were already closer to buying. The chat did not necessarily cause the purchase.

Rather than budgeting on somebody else's number, work out your own ceiling. Three inputs, one sum:

Run it with your own three numbers before you shortlist. On a small store the honest conclusion is often that only the free option and the cheapest paid tier can pay for themselves, which saves you four demos.

If you want to know whether chat actually moved your number rather than estimating it, split by page: show the widget on half your product page traffic for four weeks and compare conversion for the whole group, not for the people who chatted. Comparing chatters to non-chatters is exactly the mistake that produced the 2.8 figure.

Five questions before you install

1. Can it look up an order without a login, and with which identifiers? Test it with a real order number in a trial.
2. Live inventory or a snapshot, and how often does the snapshot refresh? Ask for the number, not a reassurance.
3. What is metered, and what does peak cost? Multiply by three and check whether you can move back down in January.
4. Does an AI resolution also count as a ticket? On ticket-priced plans this changes the economics of automation entirely.
5. What does it do with a question it cannot answer? A confident invented returns policy is worse than no chat at all.

What to do this week

• Sample fifty conversations. Sort them into the five groups in the first table. That mix tells you what to buy.
• If you are on Shopify, turn on Inbox first. It is free and it establishes what you actually lack before you spend anything.
• Run the three tests on any trial. Order lookup without a login, an out-of-stock size, and a returns question just outside your window.
• Price November, then ask about January. Seasonality is the thing that makes ecommerce chat pricing different from everyone else's, and it is the question vendors are least keen to volunteer.