Website live chat for sales teams: catch the buyer while they are still on the page

Somebody is on your pricing page right now with one question. Is the course available on weekends? Do you deliver to their area? Is the price inclusive of tax? They are not going to fill in a form and wait for a call, and they are not quite ready to ring you. If there is a chat bubble in the corner and somebody answers it while they are still on the page, you have a conversation with a buyer. If there is not, they open the next tab.

That is the case for website chat in a sales team, and it comes with a condition: chat only works if it is answered quickly. An unanswered chat is worse than no chat at all, because the visitor asked and was ignored. This post is about meeting that condition with a team that spends its day on the phone, not at a desk watching a browser tab.

Who uses chat, and what they want

People who start a chat are rarely browsing idly. Typing a question takes more intent than reading a page. In practice, chat visitors tend to fall into a few groups, and each needs a slightly different response.

All four are leads. The mistake is to treat chat as a customer support channel that sales occasionally dips into. Route it to the people who sell, and measure it the way you measure any other enquiry.

Ask for the number before the first message

There is a real trade-off here. Every field you ask for before a visitor can type puts a few people off. But a chat with no contact details is a dead end the moment the visitor closes the tab: you cannot follow up, cannot call, and cannot tell whether they were already a customer.

For a sales team, the number is worth the friction. A visitor who will not share a mobile number to ask about price was unlikely to buy this week anyway, and every visitor who does share it becomes a lead you can call back tomorrow even if the chat goes quiet. LumaKol’s chat widget takes this view: the visitor gives their name, mobile number and first message to start the chat, the number is checked as a valid mobile number, and every chat is saved as a lead with the source “Website chat”.

Answering fast when nobody sits at a desk

A chat has a much shorter life than a form. Someone who filled in a form expects a call later; someone who typed into a chat is waiting for a reply now, often with the page still open. A reply within a minute or two lands while they are still there. A reply after twenty minutes usually lands in an empty tab.

For a calling team, that means chats have to reach the phone, not just a browser. In LumaKol, a new chat, a message on a chat nobody has read yet, and a chat handed to you arrive as a notification on the phone, and the Android app has the full inbox under More → Website chats, where the team can read, answer and close chats, and managers can hand them to someone else. The Home screen also shows how many website chats are waiting, with a reminder that visitors are still on your website.

A few rules make the first reply count:

1. Reply within a minute with a human line, even if the full answer needs checking. “Hello, let me check the weekend batch for you, one moment” keeps the visitor on the page.
2. Answer the question they asked before asking your own. A visitor who asked about price and got “May I know your requirement?” feels processed.
3. Look at where they wrote from. The chat thread shows the page the visitor was on, which often tells you exactly what they are comparing.
4. Keep messages short. A chat is not the place for a brochure in five paragraphs; offer to send it, or better, offer a call.

Out of hours, honesty beats a fake “we will be right with you”. LumaKol’s widget shows your greeting while someone who answers chats is online and your away message when nobody is, and visitors can still write either way. A good away message says when you will reply and that you will call on the number they gave, then the team keeps that promise first thing the next morning.

Deciding who answers

Unrouted chats tend to be answered by whoever happens to be least busy, which in a calling team often means nobody. Decide in advance where chats go. LumaKol offers three choices under Who answers, and each suits a different team.

Whichever you choose, a visitor who is already a lead goes to that lead’s owner, so a returning customer talks to the person who knows them rather than starting again with a stranger. The existing lead is not duplicated; it gets a note that they enquired again through the chat.

Routing also needs a way to fix mistakes. In the Chats inbox, Answer this chat takes an unassigned chat, and simply replying does the same. Owners, admins and team leads can hand a chat to someone else, who is told straight away, or use Take over to move a chat someone else is answering to themselves. The Mine and Unassigned boxes show at a glance what is yours and what is still waiting for someone.

Turning a chat into a call

Chat is a good opening and a poor place to close. Detailed questions, price discussions and anything involving a decision go faster and better on the phone. The skill is knowing when to suggest the switch and asking rather than assuming.

• Suggest a call when the questions become specific to the visitor’s situation, when price comes up for the second time, or after a few back-and-forth messages that are not converging.
• Ask permission and give a time: “Would it be easier if I called you on this number in five minutes?” Most people who have already shared a number say yes.
• Call when you said you would. A chat that ends with “calling you now” and is followed by a call twenty minutes later undoes the good start.
• If they prefer to stay in the chat, respect it, answer properly, and set a follow-up so the lead does not go cold.

Because every chat is tied to a lead, the switch is short. Open lead takes you from the chat to the lead, where you call from the app as with any other lead, and the conversation is summarised on the lead’s timeline, so whoever calls can see what the visitor already asked. When the conversation is over, Close chat ends it: the visitor sees that the chat was closed, and if they write again, it opens again.

What to watch each week

Chat is easy to switch on and easy to neglect. A short weekly look keeps it honest.

• How long the first reply takes, and how many chats waited with nobody answering. If chats sit in Unassigned, the routing is wrong, not the people.
• How many chats became a call. Chat should feed the phone, not replace it.
• What happened to the leads. Each widget’s leads go into a lead list named after the widget, so you can open that list and see how many moved forward and how many went quiet.
• What people ask. The same three questions every day belong on the page itself, in plain sight, which frees chat for the questions that need a person.