"Just add a chatbot" was never a strategy. Here's the argument for why.
A chat widget is a human-interface metaphor, a text box someone types into, bolted onto a business that hasn't changed underneath. It answers the question "how does a person talk to us" when the real question is whether the facts behind the widget are the ones an AI agent can act on.
5 min read
What a chat widget fixes
A cottage-letting agency adds a chat widget to its homepage, trained on its own FAQ pages, and reports the project as done. Visitors can now type a question and get an answer instead of scrolling to find it. That's a genuine, if modest, improvement for a person on the site. It has almost nothing to do with an agent booking on someone else's behalf.
A chat widget shortens the distance between a person's question and an answer already sitting somewhere on the site. That's real, and worth having. But it's a convenience layer over the same underlying facts the site already contained. If the cancellation policy was vague before the widget, it's still vague, now with a friendlier front door.
What it doesn't touch
An agent booking on someone's behalf isn't a visitor typing a question into a widget. It's a system checking specific facts, directly, often without any conversational interface involved at all. A chat widget answers the question "can a person ask us something in plain language." It says nothing about whether the underlying fact that answer depends on is accurate, current, or reachable by something other than the widget itself.
Why "just add a chatbot" keeps getting suggested anyway
It's an easy thing to sell and an easy thing to point at: a business can demo it, screenshot it, show a board member. Fixing the underlying facts, making sure the cancellation policy, the dog policy, the actual room count are accurate and connected everywhere they're checked, is less demoable and more of the real work. The widget is the visible part of a project that skipped the invisible, harder part underneath it.
Where this shows up for a business
Selfe fixes the layer underneath the widget: a cottage agency's real facts, connected and current, reachable by an agent directly rather than only through a chat window built for a person typing a question.
So a chat widget is a waste of time?
Not for the people using it. It's a separate project from agent-readiness. A useful one, just not the same one.
What should a business do instead?
Check whether the facts a chat widget would answer from are accurate and connected everywhere they're needed, not just inside the widget's own FAQ.
A lot of what you've heard about agentic commerce isn't quite right.
Every myth in this hub comes from the same mistake: judging the future by how well it fits today's tools, a page, a widget, a chat window, a markup file, instead of asking what would make sense if you were starting clean. The actual destination underneath all of it is simpler than any of the myths: AI agents talking directly to data, not reading pages built for people.
"We've set up MCP, so we're agent-ready." That covers your own team's tools. It's a different job from the one a stranger's agent needs done.
MCP is genuinely useful, just not for the case most businesses think it covers. It's strong for an operator's own tools, a chat assistant working against your booking system, less so for a stranger's AI agent trying to book or buy from you. Both are real, but only one of them is what "agent-ready" usually means.
"AI agents just means ChatGPT." It's a much wider, more personal category than that.
Most people picture one thing when they hear "AI agent": a chat window they open and type into, the way they'd open a search tab. That's one shape among many, and probably not the shape that ends up mattering most for buying and booking.