A visitor lands on a car dealer's site and wonders whether a certain model is in stock. Another is searching for an accounting firm and wants to know whether you take on new clients. A third has a leaking roof and needs help today. All three are in touch with your site, but they do not need the same channel.
So the question is not whether chat or phone is best. It is when each channel suits, and how you avoid making the visitor start over when they switch.
When chat suits
Chat works well when the visitor is still reading and comparing. The questions are small and concrete: what does delivery cost, what are your hours, do you take jobs in my municipality. The visitor wants answers without talking to anyone, and may be somewhere they cannot call from.
Chat also suits when you want to find out something structured. A few questions in a row, which service, which area, how urgent, give you a basis before anyone gets in touch.
There is a limit. Chat is good at what is already written somewhere: on the site, in your terms, in a knowledge base. If the answer has not been written down, it should not make something up.
When a call suits
A call suits when it is urgent and when the matter is hard to write down. Someone with a broken heat pump does not want to describe the problem in a text box. They want to talk to someone who understands. The same goes for sensitive matters and for purchases where the visitor wants to feel trust before deciding.
High purchase intent is a third situation. Someone who has read your pricing page and then opens the chat to ask about a quote is often ready to talk. Then every extra message is a detour.
The problem with choosing one channel
If the site only offers chat, you lose those in a hurry. If it only offers phone, you lose those who cannot or do not want to call right now. Both groups exist at most companies.
A more common mistake is that the channels live separately. The chat answers, the visitor wants to talk, and is given a phone number to call themselves. Everything already said in the chat is gone. The visitor explains the same thing again, to a person who does not know what was written.
Connect them in one flow
It is better to let chat be the first step and the call the next, in the same flow. The chat answers what it can. When the question needs more, it offers a call, and the visitor does not have to phone in. The person who takes the call can also see what has already been said.
Decide which questions should trigger the offer. A few examples: the visitor asks for a quote, wants to book a time, is annoyed, or asks something that cannot be answered from your material. Write the rules down and test them yourselves. Ask the chat the ten most common questions and see what happens.
Follow up in a simple way. Which questions led to a call? Which calls could have been solved in the chat? That shows where the line should be for your business.
How it looks in Leadcaller
In the Leadcaller widget, chat is one of four modes. It answers from your site and your knowledge base, with a source, in nine languages. If the answer is missing it offers a call instead of guessing, and it hands over to a person when the question is not in the material. The widget is set up with one line of code on the site.
Key takeaways
- Chat suits visitors who compare, read and want a quick answer from your material.
- A call suits urgency, sensitive matters and high purchase intent.
- Let the chat offer a call instead of making the visitor start over.