Myth: you have to be online around the clock
This is the belief that stops more teams from starting than any other. It assumes chat is
a promise of constant availability, so anything less is a broken promise. In practice the promise
is set by what your widget says, not by the medium. A widget that states your hours and takes a
message outside them is honest, and visitors treat it as such.
The costly version of this myth is not switching chat off — it is leaving chat on with no
stated hours, so visitors assume somebody is there. The failure is the mismatch, not the absence.
Decide your hours, display them, and let the offline path do the rest. Our own
pricing starts free for a single agent precisely because most teams
should begin with narrow, well-covered hours rather than an ambitious schedule they cannot
hold.
Myth: chat will bury you in messages
The fear is that adding a chat widget opens a floodgate and the existing team drowns.
What usually happens is a shift in where contacts arrive rather than a large increase in how many
there are. Some questions that would have become emails become chats, and some that would have
become nothing at all become chats — and that second group is the one worth having, because
it contains people who would otherwise have left.
Volume is also controllable in ways email is not. You decide where the widget appears, whether
it appears at all on some pages, whether it invites proactively, and how many conversations an
agent handles at once. If volume genuinely exceeds capacity, those are dials you can turn the same
afternoon.
A reasonable worry, since a widget is third-party code on every page. The part that
matters is how it loads. Our install snippet is a single script tag marked async and defer, placed
before the closing body tag, so the browser continues parsing and rendering the page rather than
waiting for it. The widget arrives after your content, not in front of it.
That is a fact about how the snippet is written rather than a claim about your particular site,
and it is worth verifying yourself rather than believing either way. Measure your own pages with
and without the tag; do not accept a vendor's number, including ours. What you should not do is
reject chat on a general theory about third-party scripts without checking whether it applies to
the one you are considering.
Myth: chat only pays off for big support teams
The assumption is that chat is a volume tool and therefore pointless below some threshold
of traffic. It gets the economics backwards. On a low-traffic site each visitor is worth
proportionally more, and the conversation that saves one sale can outweigh the entire cost of
running chat that month. Small teams also have an advantage larger ones spend money trying to
recreate: the person answering usually knows the whole product.
What genuinely does not work at small scale is pretending to be big — broad hours, instant
response promises, and a queue nobody is watching. Narrow the hours until you can actually cover
them, and the size of the site stops being the deciding factor.
Myth: visitors find chat annoying
What visitors find annoying is being interrupted, which is not the same thing. A widget
sitting quietly in the corner asks nothing of anyone; a message that slides over the content three
seconds after arrival, before the person has read a sentence, is an interruption and earns the
irritation.
The distinction is entirely under your control. Proactive invitations are a setting, not an
inherent property of live chat, and they behave very differently depending on timing, page and
wording. If you believe your visitors dislike chat, check whether they dislike your invitation
rules first. The quiet, always-available version is the one most people mean when they say they
like chat on a site.
Myth: an AI bot can take the whole queue
The current enthusiasm inverts an older myth without improving on it. An
AI chat answering from your own documented material handles
repetitive, well-covered questions well and frees people for the rest. What it does not do is
absorb the conversations that carry the most value — the ambiguous ones, the angry ones, the
ones where the customer has not yet said what the real problem is.
Teams that deploy AI as a replacement usually discover the handoff is the whole design problem,
and that a bot which cannot gracefully admit its limits damages more goodwill than it saves. Teams
that deploy it as a first layer with a clean route to a person tend to be satisfied. Same
technology, different expectation.
Myth: more chats is always better
Chat volume is a seductive metric because it goes up and feels like progress. But a
rising number can mean your product got harder to use, a page stopped explaining itself, or a
release broke something. Celebrating the increase means celebrating the symptom.
The healthier reading pairs volume with cause. If chats about shipping doubled, the useful
question is what changed on the shipping page. A team that treats every repeated question as an
indictment of some page will steadily reduce the volume of avoidable chats while increasing the
share that are worth having — which usually looks like a flat or falling total and a rising
conversion rate.
Myth: chat and email are the same conversation
They are handled by the same team and often the same tool, so it is tempting to treat them
as one channel with different delivery. The expectations are not the same. Chat is synchronous and
the visitor is on the page right now, with the context in front of them; email is asynchronous and
the context has to be rebuilt at both ends. A reply that is perfectly good in email —
thorough, formal, sent in four hours — fails completely in chat.
The mistake costs most in tone and structure. Pasting email-shaped paragraphs into a chat
window reads as evasive, and writing chat-shaped fragments in email reads as careless. Train them
as related but distinct crafts.
What the myths have in common
Every one of these is a claim about live chat in general standing in for a decision about
your configuration. Chat is not inherently always-on, interruptive, expensive, or high-volume; it
is those things only if you set it up that way. The costly pattern is rejecting the tool on a
property you could have changed in the settings.
If you are weighing chat now, the useful exercise is to write down the specific belief stopping
you, then check whether it describes the medium or a default you are free to change. In most cases
it is the second, and the answer is a setting rather than a strategy.