The first line has one job
A welcome message is not a decoration; it is an opening move. Its only job is to make replying feel easy and worthwhile. "Hi, how can I help you today?" technically does this, but it is so generic the visitor's brain filters it out like a banner ad. The greetings that earn replies are specific, low-effort to answer, and tied to where the person actually is.
"How can I help you?" puts all the work on the visitor: they have to formulate the whole problem from scratch before they type anything. A better opener does some of that work for them — it proposes a starting point they can accept or redirect. Lowering the cost of the first reply is the entire game.
Match the message to the page
- Pricing page: "Comparing plans? I can help you figure out which one fits." You already know the intent — meet it.
- Docs or help center: "Looking for something specific? Tell me what you're trying to do." Assume a task, not a browse.
- Checkout: keep it minimal and reassuring — "Any questions before you finish? I'm right here." Do not add friction at the finish line.
- Homepage: a soft, open greeting is fine here; intent is genuinely unknown.
Proactive is not the same as pushy
A proactive greeting that fires the instant someone lands feels like a salesperson pouncing at the door. Give the visitor a moment, tie the trigger to a signal of interest — time on a key page, a scroll depth, a return visit — and let the message reflect that context. A well-timed proactive invitation converts; a reflexive pop-up trains people to close the widget.
Set expectations in the greeting itself
If a human answers instantly, great. If not, say so in the opener: "Thanks for the message — an agent will jump in shortly, and I can try to help in the meantime." Honesty about timing in the first line prevents the silent-wait frustration that makes people leave.
Test the opener like a headline
Your welcome message is the most-seen sentence in your support operation — treat it like ad copy. Try a specific opener against a generic one and watch reply rate, not impressions. In MyLiveChat, greeting text and proactive rules are configurable per deployment, so testing a new opener is a settings change you can measure against next week's chats.
Openers for the pages that matter most
A single greeting across an entire site is a compromise everywhere. Different pages carry
different intent, and the opener that respects that intent outperforms a general welcome without
being any more clever.
On a pricing page the visitor is comparing and calculating, so the useful opener offers to answer a
specific comparison question rather than asking how it is going. On a documentation or support page
they are usually stuck on one thing, and an opener that invites them to describe it gets a useful
first message instead of a greeting exchange.
On a checkout or cart page, brevity is the whole strategy: they are mid-task and any interruption
competes with the purchase. On a landing page from a campaign, the opener can safely reference what
brought them, which reads as attentive rather than intrusive. And on the home page, where intent is
genuinely unknown, a short open question is the honest choice.
The opener when you are busy or away
Most welcome message advice assumes an agent is waiting, and the harder cases are the other two:
when the team is swamped and when nobody is there at all. The same warm greeting used in both places
is how a helpful widget becomes a broken promise.
When busy, say so in the opener rather than after they have typed. A visitor told up front that
replies are taking a few minutes will usually wait; the same visitor who waits blind after a cheerful
greeting will not, and will conclude they were ignored.
When offline, the greeting should say when someone will actually be back and what happens to their
message, in that order. Vague reassurance produces a second contact; a specific answer does not. Our
guide on after-hours support strategy covers
the wider setup this fits into.
Where the greeting actually lives
The opener is not stored with your conversations. It is one of the widget's interface strings, alongside the launcher label and the offline notice, and it is edited on the screens that hold your custom text rather than anywhere near your chat history.
Two things follow from that, and both are useful. The first is that your edit is an override rather than a replacement: the shipped wording stays underneath, and a string you never touch keeps it. The second is the practical consequence of the first, which is that reverting is done by clearing the field, not by typing the original text back in. Empty the box and save, and the built-in wording returns.
The greeting is also not the only writing on that first screen. If your visitors land on the messenger home rather than straight into a conversation, there is an announcement card and a short row of links there too, and they carry a real share of the first impression — see announcements and quick links on your messenger home.
Overrides are held per language, so writing a German greeting leaves your English one alone. If you have already translated the text in your chat widget, the greeting sits in the same catalog and is edited the same way.
Changes take effect on the live widget within seconds rather than needing a deploy or a restart, which makes the opener genuinely quick to iterate on. That is worth knowing before you plan an elaborate testing process for a change you can make, see, and undo inside a minute.
Why a new greeting can miss some visitors
Here is the behaviour that catches people out when a site serves more than one language.
Your overrides and the shipped translations are layered, and the layering runs from general to specific. The default wording is applied first, then your default override, then anything defined for the broad language, then your override for it, then anything for the exact regional locale, and finally your override for that.
The last one to be applied wins. So a visitor whose browser reports a specific locale that already has a shipped translation will see that translation rather than the greeting you wrote in the default box, because the more specific shipped string is applied after your more general override.
The fix is not subtle: set the override at the language you actually mean. If you want every French visitor to see your wording, write it under French rather than expecting the default to reach them. If your audience is English-speaking and you have never touched languages, none of this affects you and the default box is exactly right.
One more detail worth carrying: editing the string under US English is the same as editing the default, because that pairing is treated as the base rather than as a regional variant. If you edit there and expect it to apply only to American visitors, it will not.
What to measure
Test one opener against another rather than debating them. Engagement rate — the share of
visitors who reply at all — is a fast, honest signal and needs no elaborate tooling.
Look past engagement to what happens next. An opener that produces many replies and few resolved
conversations is generating traffic rather than value, which is easy to miss if you stop at the
first number.
Watch the opener's effect by page separately. A greeting that lifts engagement on the home page
can easily depress completion on checkout, and a blended figure will show you neither.