A good live chat greeting does not sound the same on every page. It refers to where the visitor is, says honestly when a reply will come, and suggests one concrete question. Below you will find live chat greeting examples for four page types, online and offline versions, and a way to check which variant actually starts conversations.
This guide is about the first sentence, before the customer types anything. What to show once the customer is already waiting is covered in our guide on what to tell customers waiting in chat, and the details you collect up front in our guide on the pre-chat form.
What a chat greeting should do
A greeting has one job: to make the first message easier to write. The visitor does not know whether a person is on the other side, whether the question is too basic, or how long they will wait. A generic “Hi, how can I help?” settles none of this. A sentence that names the typical request on this page works better.
The simplest test: can the customer answer the greeting in one sentence? “Tell us your bike model and we will check whether this rack fits” hands them a ready start. “Got questions? We are here for you” makes them work out where to begin.
- It refers to the page the customer is on right now.
- It suggests one concrete question or detail worth sharing.
- It tells the truth about who replies and when.
- It fits into two short sentences on a phone screen.
- It does not reveal that you are watching the visitor's every move.
Greeting examples by page type
We wrote the copy below for a fictional bike shop with a repair workshop that takes bookings. Swap the examples for your own, but keep the pattern: page context plus a concrete prompt.
Scroll the table sideways to see all columns.
| Page type | Greeting example | What it makes easier |
|---|---|---|
| Product page | “Not sure about the frame size? Tell us your height and we will suggest one.” | Gives the customer the details for a first message |
| Pricing | “Unsure which service package to choose? Describe your bike and the fault, and we will point you to one.” | Turns a comparison into a single question |
| Booking | “Looking for a service slot? Tell us which day suits you and we will check the schedule.” | Leads straight to a specific date |
| Order help | “Question about an order? Add the order number so we can check faster.” | Collects the key detail without a form |
On an order page the greeting usually reaches someone with a problem, so it asks for the order number and promises no solution before anyone has checked. Pricing pages are the opposite: the customer is comparing options, so the greeting offers help choosing, not a discount. For price questions with no details, see our guide on price questions in chat.
In Meetlead you set the start screen copy and the empty chat text in Widget Studio, under Start and Chat, separately for Polish, English and German. These fields apply to the whole widget, so a page-specific version needs the automation rule described below. Before you enter the copy, decide whether you address customers formally or casually, because the greeting sets the register for the whole conversation.
Online and offline versions of the same greeting
A greeting that invites a conversation has to change with your team’s availability. During business hours it encourages a question; after hours it says when someone will read the message and does not pretend anyone is at the chat.
Tell us what you are looking for and we will reply right here. If it is about an order, add the order number and we will check its status straight away.
Nobody from our team is at the chat right now. Leave your question and email address, and we will reply on the next business day before noon. If it is about an order, add the order number.
In Meetlead the widget switches to offline mode when no operator is available according to their schedule and panel connection. You set the offline copy, including the response time promise, in the Offline section. For nights and weekends, see our guide on after-hours messages.
An honest response time instead of “we reply instantly”
A time promise in the greeting is the easiest way to disappoint. It is safer to state what your team actually keeps to: chat staffing hours and when a message left outside them will be answered. If you quote minutes, base them on measured time, not a target; see our article on first response time in chat.
In its study of customer-service chat, Nielsen Norman Group (Raluca Budiu, 2019) recommends clearly stating the hours of a chat that is only staffed part of the day, and opening without filler such as “how are you”. Nielsen Norman Group. These are usability guidelines, not a measurement of how a greeting affects conversation volume.
The same applies to who replies. If an AI assistant gives the first answers, the greeting should not suggest a person with a name and photo. We show how to say this plainly in our guide on labelling an AI chatbot.
Static greeting or proactive greeting based on behavior
Everyone who opens the chat sees the static greeting. It never interrupts reading, but it is generic. A proactive greeting appears on its own once the visitor meets a condition, such as time on the page or scrolling to the prices. It can be tailored to the page, but bad timing feels intrusive.
Scroll the table sideways to see all columns.
| Aspect | Static | Proactive |
|---|---|---|
| When it shows | When the chat is opened | When a rule condition is met |
| Fit to the page | One text for the whole widget | Separate text for a chosen URL |
| Main risk | Copy that is too generic | Interrupting reading and showing too often |
| Where to start | The whole site | Pricing, booking or order pages |
In Meetlead a proactive greeting is the proactive message action in Automations, triggered for example by a URL visit, time on page or scroll depth. A chat status condition skips visitors who are already chatting. Each rule has one message, so English and German need separate rules with a language condition. A lighter option is the teaser bubble above the chat button, with a delay and a show-once setting.
Signals and frequency limits are covered in our guide on live chat automation. If you are tempted by a window in the middle of the screen, check the cost in our article on website popups first.
How to compare greeting variants
How often a greeting is shown says nothing about its quality. Count started conversations, where the visitor wrote the first message, and check whether they are real questions rather than a bare “ok” or “hi”. Meetlead has no built-in A/B test for greetings, so plan the comparison by hand.
- Pick one page.Compare variants on the same page, such as pricing. Different pages carry different intent.
- Change one element.Variant A asks a general question, variant B suggests a specific detail. Keep the rule’s condition and delay unchanged.
- Use equal periods.Run variant A for, say, two full weeks, then variant B for two more, with the same staffing. Note the dates.
- Count conversations, not impressions.Compare the rule’s executions in the automation report with conversations started in the same period, and check which page each customer wrote from.
- Read the first messages.Review a sample from both periods. Fewer conversations with more concrete questions may suit your team better.
In Meetlead displaying a greeting, including an automated one, does not create a conversation in the inbox. A conversation appears only after a customer message or a manual operator message, so the list does not grow just because a rule fires more often. With a few conversations a week, a difference of two or three is chance, so extend the period or judge mainly by the questions.
Questions about chat greetings
Should the greeting ask for a name? Usually not. Asking for details before the customer’s first sentence raises the barrier, and a name is rarely needed to answer. If you need an email address to reply after hours, ask for it in offline mode or a short pre-chat form and explain why.
How many proactive greetings should one visitor see? Ideally one per visit. If the customer ignored it, another on the next page rarely helps. Set rule priorities and conditions so the most specific greeting appears on the highest-intent page and the others do not compete with it.
