Squarespace Live Chat Plugin: Check Your Plan Before You Pick One

Nearly every guide to this topic opens with a ranked list of chat apps and never mentions the plan requirement. Then people buy a widget, go to install it and find the menu item is missing. So this page starts with the install path, then covers the apps, then the things that go wrong on Squarespace specifically.

Squarespace does not have a plugin directory

This is the first thing to unlearn if you have come from WordPress. Squarespace has no plugin repository, no marketplace of installable add-ons that extend the platform, and no equivalent of the WordPress admin plugin screen.

What people call a Squarespace live chat plugin is one of three things:

• A script in Code Injection. You paste a snippet from the chat vendor into a settings box and it loads on every page. This is how almost every chat tool is added, and it needs Business or higher.
• A code block on one page. Advanced code blocks also require Business or above, and only cover the page you put them on, which is rarely what you want for chat.
• A Squarespace Extension. A short, curated list of approved partner integrations. Very few of them are chat tools, and the ones that exist connect data rather than inject a widget.

So the practical answer is Code Injection, and the practical constraint is your plan.

The plan requirement, and what it costs

The Asyntai column is ours, so read it as a disclosure. The Personal plan limit is Squarespace's rule and it applies to every chat tool equally, so any article implying one product gets around it is wrong. From Business upward the install is one line in Code Injection and the free tier starts immediately.

Squarespace renamed its tiers and both naming schemes are still in circulation, so Personal and Basic are the same plan, as are Business and Core. Custom CSS is on every plan. Code Injection and advanced code blocks are not.

Work out the real cost of adding chat on a Personal plan:

That is not a reason to avoid chat. It is a reason to include the upgrade in the comparison, because a $0 widget on a Personal site is really an $84 a year decision, and a $19 widget is really $103.

How to install it, in four steps

1. Confirm your plan. Settings, then Billing. If it says Personal or Basic, the next step will not be there.
2. Copy the snippet from your chat vendor. Every tool gives you a short script tag. Take the whole thing including the tags.
3. Paste it into Settings, Advanced, Code Injection, Footer. Use Footer rather than Header. Chat widgets load themselves after the page, and a script in the header can delay your content rendering for no benefit.
4. Save, then open the live site in a private window. Not the editor preview. Code Injection does not run inside the Squarespace editor, and this is the single most common reason people think the install failed.

That last point deserves emphasis because it wastes a lot of afternoons. The widget will not appear while you are editing. Open the published URL in a browser where you are not logged in.

Which chat app to put in the box

The install path is identical for all of these, so the choice is about price model and what happens when nobody is at a desk.

We make Asyntai, so treat that row as a disclosure. Every app here installs the same way through Code Injection and every one of them needs the Business plan or higher.

The question that decides it for most Squarespace sites

Squarespace sites are usually run by one person, or a very small team, who also do the actual work of the business. That changes the answer.

A staffed chat widget assumes somebody is watching it. If you are a photographer, a consultant, a studio or a shop owner, you are not watching it during a shoot, a client call or a delivery. The widget then does one of two things: it sits offline, which looks worse than having no chat, or it collects messages you answer six hours later, which is email with extra steps.

On a one-person site, the real comparison is not between chat apps. It is between a chat widget you can actually staff and one that answers without you.

So ask it plainly: at 9pm on a Saturday, when somebody is looking at your services page and wants to know whether you travel to their area, what happens? If the honest answer is nothing, pick the option that answers, or do not add the widget.

Squarespace Extensions, and why chat is not in there

Squarespace does have an official extensions library, reachable from your dashboard. It is worth understanding what it is for, because people go looking for chat in it and conclude the platform cannot do chat.

The library is a curated list of approved partner services, weighted heavily towards commerce operations: accounting, shipping, inventory, dropshipping, email marketing, product feeds. These connect to your store data through an authorised connection. They are not front-end components and they do not inject code into your pages.

A chat widget is the opposite kind of thing. It is a front-end component that has to load on every page and render over your content. That is exactly what Code Injection is for, and it is why chat lives there rather than in the extensions library. So do not judge a chat tool by whether it appears in Squarespace's directory. Nearly none of them do, including the biggest names in the category.

Choosing by the kind of Squarespace site you run

Squarespace covers a wide range of sites and the right answer differs sharply between them.

Two more cases worth calling out. If you run member areas or sell courses, your chat questions will be about access and billing, which are account-specific and often need a person. If you use Squarespace Scheduling, the highest-value thing a chat widget can do is send people to the booking page at the right moment, so check the tool can link out cleanly rather than just collecting a message.

How to check it actually works

Ten minutes, and it catches nearly every problem people report weeks later.

1. Open the published site in a private window. Not the editor, not a logged-in tab. The widget should appear within a few seconds.
2. Ask it a real question from your own pages. Something a customer would type, not "test". If it cannot answer that, nothing else matters.
3. Do the same on a phone. Check the bubble does not sit on the buy button, the booking button, or your cookie banner.
4. Check a second page type. Code Injection applies site-wide, but templates differ. Look at a product page, a blog post and a gallery page.
5. Come back at 9pm and ask again. This is the test that decides whether the tool suits how you actually work.

Five things that go wrong on Squarespace

1. The widget does not show, because you are looking at the editor. Code Injection does not run in the editor. Check the published site in a private window.
2. The menu item is missing. You are on Personal. Settings, Advanced will not offer Code Injection at all, and no amount of pasting CSS will substitute.
3. The bubble sits on top of something. Squarespace templates often have their own fixed elements in the bottom corners, including cookie banners and back-to-top buttons. Most chat tools let you move the bubble or set an offset. Do that rather than living with the overlap.
4. It slows the site down. Squarespace pages are already heavy. Put the script in Footer, not Header, and check your page speed before and after so you know what it cost you.
5. It covers the checkout on mobile. If you sell, open your own checkout on a phone with the widget live. A bubble sitting over the pay button is a real and common problem, and it is worth hiding chat on checkout pages entirely.

The real first-year cost, three ways

Add the plan upgrade to the chat tool and the picture changes from what the app's pricing page suggests. Here are three realistic paths for a site currently on the Personal plan, over twelve months.

That reframes the choice. Once you have paid to unlock Code Injection, the marginal cost of a better chat tool is small, and picking the free one to save $19 a month while carrying someone else's branding on your site is rarely the right trade for a business.

Two caveats keep this honest. If you were going to upgrade to Business anyway for other reasons, the $84 is not a chat cost at all. And if you are already on Commerce or Advanced, none of this applies: you have Code Injection and the comparison is purely between the chat tools.

Does it work with a cookie banner?

If you serve visitors in the EU or UK and use Squarespace's cookie banner, a chat widget usually sets cookies of its own. That puts it in scope for consent.

Two practical consequences. First, ask your chat vendor which cookies the widget sets and what they are for, because you need that for your cookie notice. Second, check whether the widget still loads when a visitor declines non-essential cookies, and whether you are comfortable with that behaviour. Neither question is hard, but neither is on the vendor's pricing page.

What to do next

• Check your plan first. On Personal, budget $7 to $11 a month for the upgrade before you compare a single widget.
• Decide who answers. If the honest answer is nobody after 6pm, filter to the options that answer without a person.
• Install through Footer, test on the live site. Private window, real URL, and on a phone as well as a laptop.
• Watch the bottom right corner. Cookie banner, back-to-top and chat bubble all want the same square of screen. Sort that out on day one.