A webchat greeting script that converts visitors names who is answering, states how fast you will reply, and asks one specific question — all in under 20 words. Skip the generic "How can I help you today?" opener; it reads like a bot and gives the visitor nothing concrete to answer.
- The strongest webchat greeting names the sender, sets a response-time promise, and asks one qualifying question in under 20 words.
- After-hours greetings need a different script than daytime ones — set expectations and mention AI coverage when nobody's at the desk.
- VirtualText combines webchat, SMS, and a shared inbox so the greeting script and every reply after it live in one place in 2026.
- Skip 'How can I help you today?' — it's the most common opener and gives visitors nothing specific to reply to.
Why this matters
A webchat window is the first thing a visitor sees before they call, text, or leave your site for a competitor's. For service businesses — insurance agencies, home services, clinics — that first line either books a job or gets closed without a reply.
Most widgets ship with a default greeting nobody edits. It's vague, it's the same on every page, and it doesn't tell the visitor what happens next. Fixing that is a five-minute edit with a bigger payoff than most redesign work you'll do this year.
A properly set up webchat widget is the foundation — the greeting script is what makes that widget actually convert instead of just sitting there.
How to write a webchat greeting script that converts visitors
Follow these steps in order. Each one fixes a specific reason greetings get ignored.
- Name the sender. "Hi, this is Sarah from [Business]" beats "Chat with us" — visitors reply to people, not brands.
- State a response-time promise. "We typically reply in under a minute" removes the fear of typing into a void.
- Ask exactly one question. Two questions in a greeting split attention and cut reply rates. Pick the one that qualifies fastest — location, service needed, or timeline.
- Match the page, not just the site. A greeting on a pricing page should reference pricing; a greeting on a service page should reference that service.
- Say what happens after they type. "A team member will pick this up right away" or "Our AI agent will get you scheduled" sets the right expectation.
- Cap it at 20 words. Anything longer reads like a policy notice, not a conversation starter.
Greeting templates by page type
| Page type | Target length | Sample opening | Best for |
|---|---|---|---|
| Homepage | 12-18 words | "Hi, I'm here to help you find the right service — what do you need?" | General visitors, first-time traffic |
| Service page | 18-25 words | "Hi, this is [Name] — looking into [service]? I can check availability now." | High-intent, bottom-funnel traffic |
| After-hours | 20-30 words | "We're closed right now, but we typically reply within 60 seconds — tell us what you need and we'll follow up first thing." | Nights, weekends, unstaffed hours |
Homepage greeting: 12 to 18 words
Keep the homepage greeting broad because homepage traffic is broad — some visitors are comparing options, others are ready to book. A short, open question ("What can we help you with today?") outperforms a long pitch here because it doesn't assume intent the visitor hasn't shown yet.
Service-page greeting: 18 to 25 words
A visitor on a specific service page has already told you what they want by clicking there. Reference that service by name in the greeting and skip the generic small talk — you have permission to be direct.
After-hours greeting: 60-second response promise
This is the highest-value greeting on the whole site and the one most businesses never write. A visitor chatting at 9 p.m. is either urgent or about to check a competitor next. Tell them exactly when they'll hear back, and if an AI agent is capturing website leads after hours, say so plainly instead of pretending a human is standing by.
Why greeting scripts vary
- Industry — a plumbing company's greeting needs urgency language; a dental practice's needs reassurance language.
- Page type — homepage, service page, and pricing page all carry different visitor intent.
- Staffing hours — a greeting written for a staffed desk falls apart the moment nobody's watching the inbox.
- Traffic source — a visitor from a paid ad already read your offer; a visitor from organic search hasn't.
- Human vs. AI handoff — the script has to be honest about who (or what) replies next.
- Brand voice — a formal insurance agency and a casual landscaping crew shouldn't sound alike in chat.
See webchat scripts in action
Browse live chat setups built for service business websites.
What's the ideal length for a webchat greeting?
The ideal length is 12 to 25 words, depending on the page. Homepage greetings run shorter and more open-ended; service-page and after-hours greetings run slightly longer because they need to set an expectation, not just open a conversation.
Should the greeting mention AI or a live agent?
Yes — say plainly which one is answering. Visitors don't mind an AI agent replying first as long as the script is upfront about it; what erodes trust is a script that implies a human is there when an AI agent is trained to answer service questions instead.
How fast should the first reply go out after the greeting?
The first reply should go out in under 60 seconds, whether that's a human on a shared inbox or an AI agent covering the gap. A greeting that promises speed and then sits unanswered for ten minutes does more damage than no greeting at all.
VirtualText runs the greeting script, the after-hours reply, and the handoff to a team member from one shared inbox, so the promise made in the greeting is one VirtualText can actually keep in 2026.
FAQ
How to write a webchat greeting script that converts visitors?
Name the sender, promise a response time, and ask one qualifying question in under 20 words. Match the script to the page — homepage greetings stay open-ended, service-page greetings reference the specific service.
What's the best opening line for a webchat widget?
Openers that name a person and ask one direct question outperform generic lines like 'How can I help you today?' A line such as 'Hi, this is [Name] — looking for [service]?' gives the visitor something specific to answer.
Should a webchat greeting be different at night?
Yes, an after-hours greeting should state a response-time promise, typically under 60 seconds, and be honest about AI coverage when no one is staffing the inbox after hours.
How many questions should a webchat greeting ask?
One. A greeting with two questions splits the visitor's attention and cuts reply rates — pick the single qualifier that moves the conversation forward fastest, like service type or timeline.
Does the greeting script change by page?
Yes, a homepage greeting should stay broad since traffic intent varies, while a service-page greeting should reference the exact service the visitor clicked through to see.
Is AI or a human better for the first webchat reply?
Either works as long as the greeting says which one is responding. An AI agent that replies within seconds and hands off complex questions to a person keeps the response-time promise without misleading the visitor.
How long should a webchat greeting be?
Keep it between 12 and 25 words. Anything longer starts to read like a policy notice instead of a conversation starter, and visitors stop reading before they get to the question.
What should a greeting say about response time?
State a specific promise, such as 'we typically reply in under a minute,' rather than leaving the wait unstated. A stated response time is what gets visitors to type a reply instead of closing the tab.
One last thing
The greeting script most businesses skip entirely is the pricing-page one — visitors there have already decided to buy something, and a generic "Chat with us" wastes the highest-intent moment on the whole site. Write that one first, then work backward to the homepage.
