The question comes up almost every week now. Someone has a Squarespace or Wix site, they've watched their competitors put a chat bubble in the corner, and they want to know how much it costs to add AI to their site. Fair question. The honest answer is that you can add something. You just can't add the thing you're actually picturing.
What you're picturing is an assistant that knows your business. It answers a question about your Tuesday availability by checking your actual calendar. It takes a job request and drops it into the system you already use. It recognizes a returning customer and doesn't ask them to repeat themselves. That's a useful thing to want. It's also the thing these platforms are built to prevent.
What you can add, and what it actually is
Squarespace and Wix both let you drop a third-party widget onto a page. Intercom, Tidio, whatever the current one is. It shows up, it looks fine, and it will answer general questions if you feed it your pages ahead of time.
Underneath, though, that widget is a rented box sitting on top of your site. It runs on someone else's servers. It can read whatever you pasted into its settings, and nothing else. It doesn't know your site is your site. It has no way to look anything up, no way to write anything down, and no way to hand a conversation off to another part of your business.
So it can tell a visitor your hours. It cannot tell them whether you have a slot at 2pm on Thursday. It can say you offer roof inspections. It cannot book one.
I wrote a whole piece on adding an AI chatbot to a small business site, and everything in there still holds. But a chatbot answering FAQs is a small slice of what people mean when they say AI. Most of the value is in the part that requires access, and access is exactly what you don't have.
The reason is architectural, not a settings problem
This trips people up because it feels like something that should be fixable. There should be a toggle somewhere. There isn't, and it's worth understanding why.
A website that can do real work needs a back end. Something running on a server that can receive a request, check a database, call your calendar, decide what to do, and send something back. That's where an AI assistant actually lives. The chat window on the page is just the doorway.
On Squarespace and Wix, you don't get a back end. You get a page builder and a hosting plan. You cannot run your own code on their servers, you cannot reach your own database because you don't have one, and you cannot install anything that touches the parts of the platform they've walled off. This isn't an oversight. The whole business model depends on every site being close enough to identical that the platform can maintain all of them at once.
Wix has been adding its own AI features, and Squarespace has too. Those work, in the sense that they do what the platform decided they should do. They also stop exactly where the platform decided they should stop, and you don't get a vote on where that line sits.
The workarounds are worse than they look
The usual next move is to duct tape around it. Embed a booking tool in an iframe. Route the form to Zapier. Add a scheduling widget from a fourth vendor.
I've inherited these setups and they're rough. Every handoff between the pieces is a place where something silently fails, usually a lead that never lands anywhere. And none of it makes your site smarter. It just moves the work to a different tab.
The cost is the part people underestimate. Four widgets at twenty to sixty dollars a month, on top of the platform fee, for a stack that still can't answer a simple availability question. Over a few years that's real money for something that was supposed to be the cheap option. I ran that math in detail on the real cost of a Squarespace site over five years.
What changes when the site is yours
When a business owns its site, the AI question stops being about what the platform allows and starts being about what's worth building. Those are very different conversations.
An assistant on a site you own can check the calendar, because it's your calendar and your code. It can pull up a customer record, file an inquiry where your team will see it, send the confirmation, and follow up three days later if nobody responded. It works like a person you hired for one narrow job, and it's on duty at 9pm on a Sunday when a homeowner with a leak is looking for whoever answers first.
None of that is exotic. It's ordinary software any developer could have built ten years ago. It just cost too much to be worth it for a business doing a couple million a year, which is why platforms like Squarespace won in the first place.
That's what's actually different now. Building this is far cheaper than it was even two years ago, because the tools I use have collapsed the hours it takes. A rebuild that agencies used to quote in the tens of thousands lands in a range a small business can justify, and the ongoing cost is hosting instead of a subscription that never ends. I've written more about what AI changed about website rebuild costs and what owning your website actually means. The flexibility is what people appreciate later. Once the code is yours, adding the assistant next year, or the customer portal the year after, is a project instead of a migration.
So what should you do
If a chat widget answering common questions is genuinely all you need, add one to your Squarespace site and don't overthink it. Plenty of businesses are fine there, and I'm not going to tell you to rebuild a site that's doing its job.
But if you keep running into the wall, if the thing you want always turns out to be something the platform won't let you do, that's not a tools problem you can shop your way out of. It's the platform. Better to know that before you spend another year adding widgets.
If you want to talk through what this would look like for your business, the audit is free and takes 30 minutes. Get in touch