Squarespace live chat plugin: embed options and setup

Choose a Squarespace live chat plugin or hosted service

Tidio and LiveChat are candidates for a staffed chat workflow. Elfsight is a candidate for supported widget entrances. Compare what each actually supplies: a human inbox, automation or a button leading to another service.

Use the live chat selection guide before installing. A widget that loads successfully may still be the wrong choice if nobody can answer or if it sends users to a channel the business does not monitor.

Check permissions for a Squarespace live chat plugin

Use the current Squarespace code injection guidance for your plan and account. Code blocks and site-wide code injection have distinct jobs. Do not assume a block accepting basic HTML accepts the vendor's required script.

Choose the narrowest supported placement. A page-specific feature should not load across the whole site without a reason. A site-wide chat entrance may need a distinct location from an embedded page panel.

Keep a copy of the prior code and record where you add the new snippet. If a freelancer sets it up, make the installation location part of the handover. Future editors should not need to search every page to find the source.

Add the supported embed

Generate the current installation snippet from the chosen vendor's own account and guide. Avoid copying code from another site's source or an old tutorial. It can contain the wrong account identifier or an obsolete installation pattern.

Save the change and open the live site while signed out. Editor preview is not the final acceptance check. Confirm that the correct account, greeting and position appear on the public page.

Use Tidio help or LiveChat help for the exact snippet and supported route. If your plan does not permit that route, use a documented alternative or a plain contact path. Do not work around a platform restriction by hiding code in an unrelated field.

Set hours and human handoff

Choose the hours when someone can answer. Explain how a message is handled outside those hours. Keep the greeting clear about whether a user is reaching a person, a bot or a later reply.

If the service uses a bot, define its knowledge source and a no-answer route. A bot should not promise a refund, booking or stock state that it cannot verify. The chatbot comparison helps separate those tasks.

Decide who watches unread work and who covers absence. A launcher can stay visible while the inbox is ignored. The website's promise should follow the team process rather than the script's loading state.

Check mobile, privacy and failure states

Open the panel on a narrow screen. Confirm the close control, message field and reply remain visible. Check that the launcher does not cover another key action or trap keyboard focus.

Inspect the vendor's data terms and the site's consent setup for the real installed service. A chat vendor can receive message content and technical data. Update your own privacy explanation to match what you load, not a list of fictional tools.

Test an offline state and a blocked external request where a safe preview allows it. Keep a plain contact link available. A user should not lose all support routes because an external widget fails.

Remove or replace cleanly

Disable the connection at the recorded placement, then inspect the live page. If it remains, look for another supported installation such as a second snippet. Remove the known duplicate rather than repeatedly pasting new code.

Preserve the vendor account's records as needed before closing a service. Removing a website script and deleting conversation data are distinct actions. Plan the data handover separately when you replace the chat product.

Return to website widgets if the real task is a form, booking or review display. Those features need their own workflow and should not be disguised as live chat.

Record the exact placement

Keep a short note of the page block or code area that loads chat. If the site changes theme or editor later, that note makes the route easier to find. A second editor should not need to add another snippet just because the first installation is hard to locate.

After removal, open the public page and confirm the result.

Continue with the right task

• tidio alternatives