By the Onsites AI team · Last updated · 5-minute read
LiveChat, the product, is excellent at its namesake: a polished chat experience for storefronts, with routing, canned responses and a report suite that made "chat" a legitimate channel rather than a gadget. The model around it is the classic two-tool combo: chat here, everything else — CRM, quotes, invoicing — in whatever the team has assembled from spreadsheets and other vendors. The combo works for a while, and the failure is never dramatic; it is a tax paid per handoff. "Can you quote the 40ft container?" gets answered in chat, retyped into a quoting template, emailed as a PDF, awaited as a PO, entered as an order in a spreadsheet, invoiced by finance, and chased — from the chat again, which is the only place that saw the whole story. This guide is the case for owning the whole funnel in one queue: chat, CRM record, quote, order and invoice in one thread — at three seats free, $15 beyond, instead of per-seat chat pricing plus the spreadsheet.
Four taxes describe it. The retyping tax: every commercial fact crosses tool boundaries by copy-paste, carrying typos with it — price lists drift between the quote template and the real catalog. The memory tax: the chat tool knows the conversation but not the order; the spreadsheet knows the order but not the conversation; "what did we promise them?" needs both and gets neither. The ownership tax: a pre-sales chat followed by a PO followed by a delivery complaint touches three owners in two tools, and nobody owns the thread end-to-end — handoffs lose a field each time. The channel tax: chat is the product, so email, WhatsApp and the rest fall to inboxes it cannot count; the customer's chosen channel becomes the desk's blind spot. Each tax is small monthly; together they are the reason funnel reviews find revenue leaking between tools nobody audits.
Because "small monthly tax" is easy to wave away, price it once. A trading team's audit: every quote retyped into a template costs about six minutes against selecting items from a catalog (three quotes a day — ninety minutes a month); every requote — the 20ft that became a 40ft — costs another four minutes of spreadsheet edits and two emails of version-checking (a dozen per month — an hour); invoice #1041 disputed because the PDF carried last month's price costs an afternoon of reconciliation it never would have cost inside the thread (twice a quarter — another hour). Add the memory tax's worst case — ten minutes a week per teammate hunting "which email had the PO?" in the wrong tool — and the ledger lands near a working day per month, per team, spent moving facts between tools instead of using them. Nobody budgets that line; it lives in the gaps between apps. The hidden-costs guide calls this the invoice behind the invoice, and the chat-plus-spreadsheet combo is its friendliest host.
One queue where every stage shares state. A visitor asks about freight; the answer drafts with AI in the thread; their contact record grows from the conversation automatically. They ask for a price; the quote is written in the same editor — the product catalog shared, so the 40ft requote corrects itself everywhere at once. They accept; the quote converts to an order, the order to an invoice — numbered, tracked and paid without leaving the thread. Delivery slips; the delay note appears on the same thread the PO was written in. Nothing retyped, no handoff without memory, and every teammate with permission sees the whole funnel in one scroll. That is the entire pitch — the chat bubble remains the front door, but everything behind it is now the desk rather than the gap between two tools.
LiveChat's published model is per-seat, tiered, monthly or annual — a clean meter for a clean product. The comparison is not the rate but the footprint: the seat bill buys the chat channel, while the funnel's other stages carry their own costs in other tools, and those are the lines that hide. The metered desk folds the stages into one product: three seats free forever removes the entry bill entirely; $15 per seat beyond, billed annually and prorated daily, keeps growth legible; storage starts at 100 MB with $1 per GB beyond; AI runs on prepaid credits (draft 3, reply 6, translate 3, summary 6 — about a cent each) that never expire. For a team where the funnel matters — quotes, orders, invoices — the honest comparison is stack versus stack: chat tool + quoting template + spreadsheet + accounting tool against one desk. The worked pricing models and the ten-person math carry the derivations.
The chat tool exports its transcript history; the desk imports conversations and connects email by IMAP for anything older (the setup guide covers the choices). The widget snippet swaps in minutes — same bubble, now writing into the queue. The spreadsheet's product list becomes the desk's catalog in an import, and this is the step that pays the migration: prices, SKUs and units stop drifting because one catalog feeds quotes and invoices. The first live funnel — inquiry to quote to invoice inside one thread — is the demo that convinces the team; give it two customers in week one. The habits that lag are the old ones: retyping by reflex, cc-ing finance by reflex. Both die within a month, and the quarterly review is where the taxes visibly disappear.
The fair-loss column: high-traffic storefronts whose support is genuinely pre-sales — short chats, no purchase documents, answered by a rotating team — get the industry's most polished chat product and a reporting suite built for exactly that job; the funnel may belong to e-commerce platforms behind the desk, in which case the queue adds little. Teams with heavy, complex chat routing needs that the chat product specializes in will find its depth real. The case for owning the funnel arrives with the first proforma invoice a support thread has to chase — the moment the desk stops being a chat window and becomes the place commerce lives. When that moment lands, compare stacks by the whole bill: seats and cents on one meter, or subscriptions and spreadsheets on several. Most teams past that point find the one-queue shape cheaper and far calmer.
How is Onsites different from LiveChat?
LiveChat is a polished chat product priced per seat; Onsites is a full desk — chat as one of seven channels, with CRM, quotes, orders, invoices and contracts written in the same thread from a shared catalog. Three seats free forever, $15 beyond, AI at published prepaid credits.
What does "owning the whole funnel" mean?
Inquiry, quote, order and invoice live in one thread with shared state: no retyping between chat, spreadsheets and accounting tools, no handoffs that lose fields, and every teammate seeing the whole funnel in one scroll.
What does a five-seat team pay on each stack?
LiveChat's per-seat tiers cover the chat channel while quoting, CRM and invoicing come from other tools at other prices. Onsites folds the stages into one desk: three seats free (five seats = two paid, $30/mo billed annually) plus prepaid AI credits at about a cent each.
Is migrating from LiveChat hard?
No: export conversations, import them, swap the widget snippet, turn the spreadsheet's product list into the shared catalog, and run the first full funnel in week one. Email history continues via IMAP.
When is LiveChat the better choice?
High-traffic storefronts with pre-sales-only, chat-centric support answered by rotating teams — its polished chat and reports are genuinely specialist. Migration pays once support must carry quotes, orders and invoices in the thread.