The short answer
Live chat helps when visitors have quick questions at the moment they are deciding or stuck, and you can reply within a minute or two. It backfires when nobody is there to answer. Staff it with people who know the answers, place it on pages where people hesitate, and write a greeting that says who answers and when.
A small chat bubble in the corner of a website looks like a free upgrade. Add one line of code, and visitors can talk to you. Then reality arrives: a message at 9 pm, three at once on Monday morning, a visitor who types “hello?” after forty seconds of silence.
Live chat is a promise of speed. It is worth having when you can keep that promise, and worse than having no chat at all when you cannot. This guide helps you decide, and then run it so it stays useful.
When live chat helps your website
Chat works best for questions that are short, specific and urgent to the person asking. A visitor on a hotel’s booking page wonders whether breakfast is included. A parent on a school’s admissions page wants to know the deadline. Someone is halfway through a software trial and cannot find the export button. In each case, an answer in two minutes keeps them on the page, and a form that promises a reply tomorrow loses them.
- Questions that block a decision: price, delivery, opening hours, availability, what is included.
- Pages with a form or a checkout where people stall.
- Customers who are signed in and need help with their account right now.
- Businesses where visitors expect a person, such as a clinic, a garage or a language school.
Chat also gives you something email rarely does: the exact words visitors use when they are confused. Read a month of chats and you will find the page that is unclear, the fee nobody noticed and the question your FAQ forgot to answer.
When it does not help
Chat is a poor fit when the questions are long and need research, when the answer needs a document or a case history, or when nobody can watch it during the hours the site is busiest. A solicitor’s office that needs a day to check a file does better with a clear contact form and an honest promise about timing. A one-person bakery that is at the oven from 4 am to noon should not show “online now” at 7 am.
A chat that goes unanswered teaches visitors that you do not reply. That reputation costs more than a missing chat button ever would. If you cannot staff it, do one of three things: show it only during hours when someone is there, let it say plainly that answers come by email, or leave it out and make your email address and phone number easy to find.
How to staff it
The first decision is who. The best chat agents are rarely the most senior people. They are the ones who know the product or the service well, type quickly, and can say “I do not know, let me check” without panic. Someone from the front desk, the workshop or the customer team beats a manager who answers once a day.
The second decision is hours. Pick them from your real traffic, not from a wish. Look at when visitors arrive and when they leave without buying or booking, and cover that window first. Two hours a day, honestly staffed, is better than nine hours of half attention.
The third is how many conversations one person can hold. A person can usually follow a few chats at once if the questions are short, and far fewer if they need to look things up. Start low. If people are waiting, it is a staffing problem, and adding more bubbles will not solve it.
Behind the scenes, a few habits keep chat from becoming chaos. Write saved answers for the questions you meet every day, and edit them so they sound like you. Leave notes on the conversation so the next person does not ask the customer to repeat themselves. And agree when a chat becomes an email or a call: anything that needs a file, a refund decision or a long explanation should move off chat politely, with a promise of when.
If several people share the work, use a shared inbox so each chat has one owner and the history is visible to whoever covers the next shift. Our guide on shift planning for support teams goes deeper on covering hours fairly.
Where to place it
The usual default is the bottom right corner of every page. It is a fine default, but it is worth choosing deliberately. Think about where visitors hesitate and where they are simply reading.
- Pricing, booking and checkout pages: yes, almost always. This is where a quick answer changes the outcome.
- Help and contact pages: yes. People who arrive there want a person, or have just failed to find an answer.
- Blog posts and long reading pages: usually no, or quiet. A bubble that pops open while someone reads feels like a shop assistant talking over you.
- Mobile screens: keep the button small and out of the way of menus and “buy” buttons, and check that it does not cover anything tappable.
Resist the urge to open the chat by itself on every page after five seconds. A proactive message works when it is specific: a visitor who has spent a minute on the pricing page might welcome “Questions about which plan fits? Ask me here.” A generic “Hi, can I help?” on the home page is noise. Keep these messages for a few pages that matter and watch whether people answer them.
What to write in the greeting
The greeting is the first thing a visitor reads, and it sets the whole mood. It has three jobs: say who is there, say what the chat is for, and set an honest expectation about the reply.
Compare two openings. “Welcome! How can we help you today?” says almost nothing. “Hi, this is the front desk of Harbour Dental. Ask about appointments, opening hours or prices, and we usually reply within a few minutes until 6 pm” tells the visitor exactly what to expect. The second takes longer to write and gets better first messages, because people know what to ask.
- Name a person or a team, not a faceless “we”. A first name and a photo help.
- Name two or three things the chat is good for, so people ask something you can answer.
- Give your hours, and what happens outside them.
- If an AI answers first, say so. People feel cheated when they find out late.
Write an away message with the same care. “We are offline. Leave your email and a clear question, and we will answer by 10 am tomorrow” respects the visitor’s time. A silent bubble does not. Our piece on away messages and after-hours support has more wording to borrow.
Tone and speed in the conversation
Chat is written like speech, so keep sentences short and answer the question first. Do not paste a paragraph of policy when a sentence and a link will do. Use the visitor’s name once they give it, and avoid scripts that sound like a bank’s hold music.
Speed matters, but the right measure is the time to a useful first answer, not just any answer. “One moment please” buys you a minute. Use it, and say what you are doing: “I am checking the stock in the shop now.” If a chat will take a while, offer to continue by email so the visitor can leave the page. When it is over, a simple thumbs up or down at the end tells you how it went. The figure to watch is response time, alongside how many chats were actually solved.
Privacy and consent
A chat collects personal data: names, email addresses, sometimes details people should not share at all. Tell visitors what you keep and why, link to your privacy policy from the chat, and do not ask for passwords, card numbers or medical details in a chat window. If you serve customers in Europe, check how long you keep transcripts and who can read them. Our guide to privacy basics for support teams covers the habits that matter.
Review it after a month
Give the chat a month, then read the transcripts. Count how many were answered quickly, how many were questions your site should have answered, and how many visitors left unanswered. If many chats ask the same thing, fix the page. If few visitors write at all, move the button or change the greeting. If your team is overwhelmed, narrow the hours or the pages where chat appears before you hire anyone.
Chat should shrink the questions you get over time, not grow them. When it works, you answer fast, you learn what confuses people, and your site gets clearer. For a view of how chat sits next to email, WhatsApp and the rest, see support channels compared.
Frequently asked questions
Does every website need live chat?
No. It suits sites where visitors have short, urgent questions and you can answer within a minute or two during set hours. If your questions are long, need research, or nobody can watch the chat, a clear contact form with an honest reply time works better.
How many agents do I need for live chat?
Start from your traffic, not a ratio. One trained person can follow a few short chats at the same time, and far fewer if each needs a look-up. Staff the busiest hours first, watch how long visitors wait, and add cover only where the wait grows.
Should live chat open automatically?
Only on a few pages where a specific message helps, such as pricing or checkout, and after a delay. A generic greeting popping up everywhere reads as noise. Test it on one page, see whether people reply, and keep it off long reading pages.
What should I do when nobody is online?
Say so in the chat, and let visitors leave an email address and their question, with a clear time by which you will answer. Do not show a cheerful “online now” you cannot honour. Some tools also let an AI agent answer from your own content, with a handover to a person.
Is live chat free?
It can be. Hivenza includes a website chat on every plan, Free included, for one website with a fair-use limit on new chats each month. Other tools have their own prices, and costs usually rise with seats and with advanced features, so check what you actually need before you commit.
