Website Live Chat for Small Business: Setup, Scripts and Response Rules

A live chat widget is one of the few things on a small business website that can start a real conversation with a stranger at the moment they are interested. It is also easy to get wrong. Set up badly, it is a pop-up that interrupts people, a box nobody answers, or a stream of questions that vanish when the visitor closes the tab.

This guide treats chat as a lead-capture and sales channel, not a support desk. It covers where chat helps, when to greet, what to say and ask, out-of-hours behaviour, response times, who answers, canned responses, privacy and measurement. Nothing here needs a large team. It needs a few clear decisions made once.

Key takeaways

When live chat helps, and when it annoys

Chat works when a visitor has a question that is cheaper to ask than to work out. It annoys when it gets in the way of someone who just wants to read.

Where it helps

• Pricing pages. Visitors here are weighing a decision, and the questions are predictable: what is included, how long it takes, whether there is a minimum.
• Contact and booking pages. A visitor who opened the contact page but has not filled in the form is hesitating. Chat is a lower-effort start than a form with eight fields.
• Service pages with real questions. “Do you cover my area?” and “can you do weekends?” are easier to ask than to look up.

Where it annoys

• A pop-up on every page. It teaches visitors to dismiss the widget before reading.
• Blog posts and reference content. A sales greeting mid-article is noise.
• Checkout and payment steps. Anything that distracts from finishing can cost you the sale.
• Unstaffed pages. If nobody is ever available, a widget is a promise you cannot keep.

Imagine a shop assistant doing the same thing. Greeting someone who has studied a product for a minute is good service. Following every customer from the door is not.

Where to place the widget and when to greet

Placement and timing are separate decisions, and most businesses make only the first.

The bottom corner is the convention because people know where to look and it does not cover content. Check it on a phone first: a widget that covers the call-to-action button or the cookie banner costs more than it earns. A quiet launcher on most pages costs the visitor nothing. A proactive message costs attention, so spend it only where it is likely to pay off.

Tie a greeting to a signal of interest, not to the page loading. Reasonable signals include time spent on an intent page such as pricing, a return visit to the same service page, or scrolling to the bottom of a page. Show one greeting at a time, keep the number low, and treat a dismissal as an answer.

The opening message

The first line decides whether the visitor types anything. A good opening is specific to the page, asks nothing heavy and offers a way out.

• Specific. “Questions about what is included in each plan?” on the pricing page beats “Hi! How can I help today?” everywhere.
• Low pressure. Offer help; do not demand a reply. Skip fake urgency and never pretend a person is typing.
• A way out. “No need to reply if you are just browsing” makes people more willing to engage, because they know they will not be chased.

What to ask first

The most common failure in chat lead capture is a good conversation with no way to continue it. Visitors close tabs and lose signal. Without an email or phone number, the conversation ends there.

Ask early, and give a reason: “What is the best email in case we get cut off?” frames the request as practical. Then answer their question. Do not hold the answer back until they give details; people notice and resent it. A sensible order is:

• Their question. Let them say what they came for.
• Their name. It makes the rest more human.
• Email or phone. Let them pick whichever they prefer.
• One qualifying question, only if relevant, such as the job location or timeframe.

Do not turn chat into a form. If you need five answers before you can help, send the visitor to the form instead.

Out-of-hours behaviour

Most small businesses cannot staff chat around the clock, and visitors know it. They expect you to do what you say.

• Say when you will reply. “We are away until 9am and reply to every message in the first hour” is useful. “We will be in touch soon” is not.
• Promise only what you can keep. Missing a stated time costs more than honesty would have.
• Collect contact details and the question, so whoever opens it has everything needed to reply.
• Follow up first thing. Overnight chats should be the first thing read in the morning, before the general inbox.

Response time: the target is minutes

Email can wait hours. Chat cannot. The visitor opened the conversation while sitting on your site, perhaps with competitors in other tabs. The longer the gap, the likelier they have left.

Set a target you can meet and measure it. For many small businesses a first reply within a few minutes during staffed hours is reasonable. If that is not achievable, reduce exposure rather than miss the target: show the widget only on the pages and during the hours where someone is watching. Speed matters most for the first message; once a conversation is under way, short gaps are normal.

Who answers: rotas, assignment and handoffs

In a team of three, “everybody” answers chat, which in practice means nobody does. Decide ownership explicitly.

• A rota. Name who is on chat for each part of the day, even if it is usually the same person.
• Automatic assignment. Share new conversations across the team or route them by topic, so each has an owner from the start.
• A clear handoff. When a chat needs someone else, say so and introduce them by name. Do not make the visitor repeat themselves.
• A backup for when the person on chat is on a call or off sick.

Canned responses for the ten most common questions

Most small businesses get the same questions repeatedly. Writing the answers once, carefully, saves time and improves accuracy. The risk is sounding scripted, so treat a canned response as a starting point, not the whole reply.

Do not guess the list. Read the last few weeks of enquiries from email, calls and chat. For many businesses it covers price and what is included, how soon you can start, whether you cover their area, how the process works, booking a call or visit, guarantees or trials, what they need to send you, how and when they pay, and who they will deal with.

• Use the visitor’s name. A merge tag takes a second and changes the tone.
• Write short. Two or three sentences fit a chat window; a paragraph does not.
• Answer first. Put the substance in the first sentence, then add detail.
• Add one line of your own that refers to what they said.
• End with a next step, such as a link to book a call.

Review the list each quarter. Delete the replies you never use and add one when a question has come up three times.

Turning chats into leads

A conversation is not a lead until it is recorded where you will see it again. Four habits make the difference.

• Every chat has a contact. Once you have a name and an email or phone number, link the conversation to a contact so history stays attached if they return next month.
• Tag by intent. A handful of labels, such as pricing question, ready to book and support, make follow-up and reporting easier. Use ones you will actually apply.
• Put a booking link in the chat. If someone is interested, getting a time into the diary while they are engaged beats “let us know when you are free.” Every back-and-forth over times is a chance to go cold.
• Follow up even when the chat ended early. If a visitor shared an email and vanished, send a short personal note the same day that answers their question. A generic marketing email is not welcome.

Support questions versus sales questions

A website widget attracts both, and they need different handling.

• Sales. Price, availability, fit or next steps: reply fast, ask for contact details, offer a booking link, tag as a lead.
• Support. An existing order or problem: help or hand over, and tag it so it does not distort lead numbers.
• Noise. Spam and wrong numbers: close and mark them.

Keeping these apart matters for measurement as much as service. If support chats count as leads, conversion looks better than it is.

Privacy: say what you store

Chat transcripts are personal data, and visitors sometimes type things you did not ask for. Treat the widget as you would a contact form.

• Disclose that conversations are stored. A line near the window, such as “Messages are saved so we can reply and follow up,” sets expectations.
• Link your privacy policy, and make sure it mentions chat, what you keep and for how long.
• Do not collect sensitive data in chat. Never ask for card numbers, passwords, ID numbers or health details. If someone volunteers them, say not to share them here and move to a secure channel.
• Know how to delete. Be able to find and remove a person’s conversations if they ask.

Rules differ by country and business type, so check your own obligations rather than relying on general advice.

Logged-in visitors and identity

If your site has accounts, a signed-in customer should not be asked for their name and email again. It is irritating and creates duplicate records for someone you already know.

The safe approach is for your own server to vouch for the visitor. When a customer is logged in, your server creates a short-lived signed token that identifies them, and the chat uses it to recognise the existing contact. Two points matter:

• Create the token on your server, never in the browser. Anything made in the browser can be forged, and an exposed signing secret would let anyone pose as any customer.
• Keep it short-lived, so a leaked token does limited damage.

Asking visitors to type an email and trusting it is fine for anonymous prospects, but not for showing private account details.

Measuring whether chat is working

Chat can feel productive without producing anything. Four numbers from your own data tell you the truth.

Look at these by page and time of day, not just in total. A pricing-page greeting that produces most of your meetings is worth keeping; a home-page greeting that produces none is worth removing. Also read ten transcripts a month: they show which questions your website fails to answer. Use the numbers to compare one setup with another, not to prove a return, since a chat that preceded a sale did not necessarily cause it.

Common mistakes

• Greeting everyone immediately. It trains visitors to ignore the widget.
• Leaving it unattended. A widget that looks live and is not does more harm than none.
• Faking a human. Invented names and typing indicators wear away trust once discovered.
• Counting support chats as leads. It flatters the results and hides the problem.

How Scalry handles this

Scalry has a live chat widget you add to your website. Chat conversations appear in the shared inbox alongside your other channels, and each chat becomes or links to a contact in the CRM, so the history stays attached to the person.

Conversations can be assigned by round robin, by channel or by keyword, so each has an owner without anyone having to claim it. You can reply with canned responses, which have a title, a shortcut and merge tags, and mark conversations with labels. Each conversation has a status: open, snoozed, resolved, archived or spam.

For logged-in visitors, your own server can generate a short-lived signed identity token so the chat recognises the existing contact securely. The token must be created server-side, never in the browser, and it expires after about an hour by default.

To be clear about scope: Scalry gives you the channel, the routing and the record. The rota, response targets, wording and follow-up habit are still yours to decide, and they matter more than any feature.

Questions to ask before you commit

Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.

• On which pages does chat appear, and on which does it speak first? If the answer is “all of them”, start there.
• How long does the first reply take? Use real timestamps, not an estimate.
• What happens at 8pm on a Saturday?
• Who is responsible for chat today? A name, not “the team”.
• Does every chat end up as a contact? Check a handful from last week.
• Do we tell visitors that chats are stored?

If you cannot answer the first three, you are not ready to choose between Scalry and your current website chat yet — you are still deciding what you need, which is a cheaper problem to solve first.

A two-week plan

In the first week, pick the pages where chat speaks first, write an opening message for each, name the person on chat, write your canned responses and add the privacy line. In the second week, test on a phone and out of hours, go live, and read every conversation. Change one thing, then measure again after another two weeks.

Frequently asked questions

Is live chat worth it for a small business website?

It can be, if someone will actually answer. Chat pays off most on pricing, contact and service pages, where visitors have questions and are close to a decision. If nobody can reply within minutes during opening hours, a simple form with an honest response time may serve you better.

When should the chat widget show a greeting?

Not as soon as the page loads. Tie a proactive greeting to a sign of interest, such as time spent on a pricing or contact page, and keep greetings few. Leave the widget quiet on blog posts and checkout pages, and do not repeat a greeting the visitor has dismissed.

What should I ask a visitor first in live chat?

Let them state their question, then ask for their name and an email or phone number, explaining it is in case you get cut off. Add one qualifying question only if it is relevant. Do not turn the chat into a long form.

What should live chat do outside business hours?

Tell visitors honestly when you will reply, collect their contact details and their question, and follow up first thing in the morning. Only promise a reply time you can meet.

How fast should I reply to a website chat?

Aim for minutes during staffed hours, because the visitor is on your site right now. If you cannot manage that, treat the chat as out of hours: say so, take contact details and follow up, rather than leaving an open window nobody answers.

Do I need to tell visitors that chats are stored?

Yes, it is good practice and often a legal requirement. Say briefly near the chat window that messages are saved, link your privacy policy, and avoid collecting sensitive details such as card numbers or passwords in chat. Check the rules where you operate.

How can chat recognise customers who are logged in?

Your own server can create a short-lived, signed identity token when a customer is signed in, and the chat uses it to recognise the existing contact. Create it server-side, never in the browser, so it cannot be forged.