Most websites do not need an AI chatbot. The ones that benefit share a specific profile: high volumes of repetitive questions with documented answers. Everyone else is adding a widget that interrupts visitors to offer less than the page itself. Here is the honest decision guide.
When a chatbot genuinely earns its place
Real support volume. Hundreds of similar questions a month, with answers that exist in docs. An AI assistant grounded in that documentation deflects tickets and answers at 3am.
Complex catalogs. “Which plan fits a team of 12 with SSO?” is a navigation problem a conversational layer can solve faster than menus.
Qualification at scale. If sales wastes hours on unqualified calls, a bot that asks three scoping questions before booking has a measurable payback.
The pattern: the chatbot replaces an existing, costly conversation. It does not invent one.
When it hurts more than it helps
Brochure sites. A five-page agency or service site with a chatbot is hiding its content behind an interview. Visitors wanted the pricing page, the clear structure, and a working contact link. A widget popping up “How can I help?” is friction cosplaying as service.
Anywhere it can improvise facts. An ungrounded bot will eventually invent a price, a policy, or a promise, and companies have been held to those inventions. If you cannot constrain answers to approved content, do not ship it.
As a substitute for fixing the site. If people constantly ask where things are, the information architecture is the problem, and a bot is a patch on top of it.
If you build one, the design bar
Ground it in your real content and let it say “I do not know, here is a human” rather than guess: the same trust patterns as any AI feature. Declare it as a bot, make escape to email or a person one tap, log conversations (they are free user research), and keep the launch behind a click instead of an auto-open popup. Performance counts too: chat widgets are notorious Core Web Vitals offenders, so load on demand, never upfront.
What to build instead, usually
For most sites, the conversion problems a chatbot promises to fix are solved better by an FAQ that answers real objections, published pricing, one obvious booking link, and copy that says plainly what you do. Cheaper, faster, and no risk of your website lying on your behalf. When AI does fit the product itself, that is a different, deeper design job.
Want a straight answer for your specific site before buying a widget subscription? hello@beconfidency.agency, we will tell you in one email, including if the answer is no.
These guardrails are the foundation of our AI design and integration service.