Start with a well-built FAQ page. Add an AI chatbot only when visitors keep asking questions the FAQ can't answer, and add live chat only when a named person can reply during opening hours. Whichever you pick, give visitors a plain way to reach a human.
The three tools solve different problems. An FAQ answers the questions you already know. A chatbot answers the ones you can't list in advance. Live chat handles the ones that need a person's judgment. Pick by the type of question your visitors ask, not by what is fashionable.
What do the studies say about site chatbots?
Visitors mostly ignore them. In a March 2026 study, Nielsen Norman Group watched nine people use eight site-specific AI chatbots. Participants rarely noticed the bots, even on sites they shop at, and several doubted a site bot could be any good because earlier customer-service bots had let them down.
One detail is worth remembering. On the Scouting America site, a user found an answer through ordinary navigation in about five seconds. The chatbot needed two prompts and long waits for the same answer. Users in the study preferred search, filters and menus when they knew what they were looking for. It is a small qualitative study, so read it as a warning, not a statistic.
Where the bots did help, the pattern was clear. They saved people from reading long specifications on a product page, and they answered multi-part personal questions, such as whether a 14-year-old is too old to join the scouts. No menu or FAQ list anticipates questions like that.
When is an FAQ page the right choice?
An FAQ fits when most visitor questions repeat and you can write the answers once. It works around the clock, costs nothing per conversation, and a visitor can scan it faster than they can type a question. It stops working when it is padded with questions nobody asked.
Nielsen Norman Group's guidance on FAQs, written in 2014, is blunt about this. Build the list from the questions people really ask, in the visitor's words, because "people don't search for your solution, they search for their problem." Chunk a long FAQ by topic so people can rule sections out quickly. Never use an FAQ as a substitute for a way to contact you.
One thing has changed since then. Google restricted FAQ rich results to well-known government and health sites in August 2023, and its documentation now says the feature no longer appears in Google Search from May 7, 2026. If you kept an FAQ for the expandable boxes in search results, that reason is gone. Keep it for the visitors who read it.
When does an AI chatbot earn its place?
A chatbot earns its place when visitors ask many different questions that depend on their own situation, and the answers live in your documents. It is a poor fit when the same ten questions make up most of the traffic. Then an FAQ is faster and can't give a wrong answer.
Two findings from Nielsen Norman Group's April 2026 follow-up shape how to build one. Users typed short, keyword-like queries and wanted the answer first, with detail on request. One bot gave a short, direct fee answer ($85 youth and $65 adult registration), and participants praised it. Others returned long, unformatted text, or vague multi-paragraph replies where a number was needed.
So the test for a chatbot is not whether it can chat. It is whether it can state a specific answer from your own material in two or three sentences, and say plainly when it can't. Our guide to training an AI chatbot on your business documents covers the preparation, and what AI agents can and cannot do covers what to expect beyond answering questions.
When should you offer live chat?
Offer live chat when a person is reliably available to answer within a minute or two. A chat window that goes unanswered is worse than no window at all. It fits high-consideration sales, complaints and anything involving money, where the visitor wants to know a human has understood the situation.
Live chat has a cost the other two don't: someone's time, at the hours your visitors are online. If you can't staff it, don't fake it. A contact form with a stated reply time, or a phone number, is the more honest option until you can.
How do you combine the three without making a mess?
Layer them by the type of question, and make every layer point to the next. The FAQ handles the known questions, the chatbot (if you need one) handles the open-ended ones, and a person handles whatever the bot can't settle. The visitor should never hit a dead end.
The handoff matters most. In its July 2026 article on the qualities of site-specific chatbots, Nielsen Norman Group says a bot should always honor an explicit request for a human, and should offer escalation when it can't answer well or when the user keeps rephrasing the same question. Escalating too quickly can erode trust in the bot and raise labor costs, it adds, but refusing to escalate is worse. You can check this before launch: ask the bot for a person and see what happens.
The same article lists transparency among its five qualities. Say in the chat itself that it is an AI, what it can help with, and what it can't. In the March study, a vague welcome message left users unsure what a bot could do, and one of them lost time before finding out it couldn't help with their request.
How do you decide for your own site?
Take your last fifty support emails or calls and sort them. If most repeat a dozen questions, write the FAQ and stop. If many are different questions answered in your documents, test a chatbot. If many need judgment, such as a refund decision or a quote, you need a person.
That sorting takes an afternoon and costs nothing, which is why it comes before any tool. Then put whatever you choose through one more test: can a first-time visitor find it, and do they know what it does? The March study suggests a small unlabelled icon fails both.
Choosing and wiring up these tools falls under AI integration and automation. onlyspell works on that for business sites, and if you want to talk to us about your project, bring the sorted list of questions.
Frequently asked questions
Is an AI chatbot better than an FAQ page?
Not by default. An FAQ is faster for the questions everyone asks, and a chatbot is better for specific, multi-part questions that depend on the visitor's situation. In Nielsen Norman Group's 2026 study, users preferred navigation and search when they knew what they wanted.
Can a small business skip live chat?
Yes, and it should if nobody can answer quickly. A chat window with no one behind it frustrates visitors. A contact form with a stated reply time, or a phone number, is a better choice until you can staff chat.
Does an FAQ page still help with Google?
Not through rich results. Google limited FAQ rich results to well-known government and health sites in August 2023, and its documentation says the feature no longer appears in Search from May 7, 2026. An FAQ still helps visitors, and plain-language questions can match what people search for.
Sources
- What Is Your Site's AI Chatbot for? Users Can't Tell, Nielsen Norman Group, March 20, 2026
- Less Chat, More Answer: Site AI Chatbots Need to Get to the Point, Nielsen Norman Group, April 17, 2026
- The 5 Qualities of Site-Specific AI Chatbots, Nielsen Norman Group, July 10, 2026
- FAQs Still Deliver Great Value, Nielsen Norman Group, December 21, 2014
- Changes to HowTo and FAQ rich results, Google Search Central, August 8, 2023
- FAQ structured data, Google Search Central documentation
If you still need additional help in developing and designing your website, our magic is here to help. Contact us today, and our wizards will help you immediately with your digital marketing needs!
