Blog · · 4 min read
Should your website chat answer questions? Why Supr Chat only asks
A chat that answers can be wrong about a deadline, a price or a treatment, and lets the visitor leave without a phone number. Why an intake chat only asks.
No. A website chat on a service business site should not answer questions. It should ask them. That is the whole design of Supr Chat, and it is a deliberate choice rather than a missing feature. This post explains why, what the chat does when a visitor asks something, and where the answering belongs instead.
What an answering chat costs you
A chat that answers has two jobs it cannot do well.
The first is being right. On a law firm site, a visitor asks how long they have to file. On an HVAC site, they ask what a repair costs. On a med spa site, they ask whether a treatment works on their skin. An answering chat produces something plausible, because that is what it is built to do, and plausible is not the same as true. A wrong deadline, a price that does not exist or a treatment you do not offer costs you the lead and sometimes a complaint.
The second is producing a lead. A visitor who gets an answer feels finished. They read it, nod, and close the tab. Nothing in that exchange asked for a phone number. The dashboard shows a conversation. Your inbox shows nothing. Chatbot vs live chat vs intake chat covers this in more detail.
What visitors actually ask
The questions visitors type into a chat are not hard. They are the same handful every business hears on the phone, and each one is better handled by asking back.
| The visitor asks | The chat asks instead |
|---|---|
| “Do you handle custody cases?” | “What do you need help with?” with custody as a tap |
| “How much does a repair cost?” | “What needs fixing?” then “Is it an emergency right now?” |
| “Are you open on Saturday?” | “When would you like someone out?” |
| “How long does a green card take?” | “Is there a deadline or a court date?” |
| “Does it work on my skin?” | “Which area are you thinking about?” then “When would you like to come in?” |
Look at what each swap does. The visitor who asked about custody sees custody as a choice and knows you handle it. The visitor who asked about cost gets asked about urgency, which is what the callback needs to know first. Nobody is told something wrong. Everybody ends at name, phone and email.
Every answer is information
The hidden value of asking is that every answer is a data point. A question about the age of a roof tells the crew lead whether this is a repair or a replacement. A question about an existing court order tells the attorney what kind of case this is. A question about whether the visitor has spoken to an insurance company tells the firm how much time there is.
An answering chat collects none of this. It is too busy talking. An intake chat collects all of it, and Supr Chat reads the finished chat and adds a 1 to 5 score and a one-line summary on top, so the morning list is already sorted. How to write intake questions that qualify leads walks through which questions earn their place.
Where the answers belong
Answering is still part of the job. It just belongs in two places that are not the chat window.
Your pages. The general questions, what you do, where you work, what to expect, should be answered in plain words on the site itself. That is also what search engines and the assistants people now ask for recommendations read.
The first call. The specific questions, the ones that depend on the visitor’s situation, are answered by a person who can ask follow-ups and be accountable for the answer. The chat’s job is to make that call happen, and to make it short, because the facts arrived with the lead.
The two things the chat should say
An intake chat does say two things that are not questions.
The first is the path for everything else. Every flow has a “Something else” choice that asks the visitor to describe what they need in a sentence and then collects their details. Nothing falls through because it did not fit a category.
The second is the closing line: “Thanks, Maria. Someone from the team will be in touch shortly.” That line is the only promise the chat makes, and it is the one that keeps the visitor from opening the next site. It is also a promise you have to keep, which is why the lead arrives by email and by text the moment the chat ends.
Getting it on your site
Supr Chat reads your website, writes one flow per service in English and Spanish, and goes live with one line of code in your site’s footer. It asks, collects and hands off. It never answers. Every question is yours to edit in the app. Start a free trial: 14 days, no credit card, no contract.
Related: Website chat vs contact form and Website chat for law firms.
Frequently asked questions
Should a website chat answer questions?
Not on a service business website. A chat that answers can state a deadline, a price or a treatment detail that is wrong, and it lets the visitor leave feeling finished without leaving a phone number. A chat that asks produces a lead every time.
What happens when a visitor asks the chat a question?
A good intake chat asks one back. 'Do you handle custody?' becomes 'What do you need help with?' with custody as one of the taps. The visitor gets the answer by seeing the choice, and you get the lead.
Does an intake chat use artificial intelligence?
Supr Chat uses a small language model to read each finished chat and write a 1 to 5 score and a one-line summary. It never generates an answer for the visitor. Every line the visitor sees was written for your business and can be edited in the app.
Is a chat that only asks annoying for visitors?
No, when the questions are short and the answers are taps. The visitor came to find out whether you handle their problem and whether someone will call. Two to four questions and a clear 'someone will be in touch shortly' answer both.
Who answers the visitor's questions, then?
Your pages, for the general ones, and your staff on the first call, for the specific ones. The chat's job is to make sure that call happens, with the facts already in hand.