Add Adaptive AI's Chat Widget to Your Squarespace Website

Are you looking for an easy way to connect with your website visitors and convert them into customers? Adaptive AI Webchat for Squarespace is the perfect solution for you! In this article, we'll walk you through the steps to start with Adaptive AI Webchat for Squarespace.

Covered in this article:

How to obtain the embed code for web chat for the website:

Here are detailed steps on how to add a custom chat widget to a

Squarespace website using different methods:

How to obtain the embed code for web chat for the website:

Copy the embed code from Sites > Chat Widget > Get Code

Here are detailed steps on how to add a custom chat widget to a

Squarespace website using different methods:

• Obtain code for the Chat widget as shown above.
• Log in to your Squarespace account and navigate to the website to which you want to add the chat widget.
• Click on "Settings" in the main menu.
• Select "Developer Tools" in the "Website" section.
• Click on "Code Injection"
• Paste the chat widget code in the "Header" or "Footer" fields.
• Click on "Save" to save the changes.
• Preview your website to make sure the chat widget appears correctly.

Method 2: Add a custom chat widget using an Embed Block

• Log in to your Squarespace account and navigate to the page where you want to add the chat widget.
• Click on the page editor and select the section where you want to add the chat widget.
• Click on the plus icon to add a new content block and select "Embed" from the drop-down menu.
• Paste the chat widget code in the "Code Snippet" field.
• Click on "Apply" to apply the changes.
• Preview your website to make sure the chat widget appears correctly.

Before you begin

“Add Adaptive AI's Chat Widget to Your Squarespace Website” is part of the Automation → Workflows area in Adaptive AI. Create and manage active, inactive, and draft workflows. Conversation, phone, SMS, chat, and messaging changes affect customer contact and consent. Test routing in both directions and confirm that messages land on the correct record and owner. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the phone number, inbox, social account, personal inbox, or chat channel is connected and assigned to the intended business.
• Verify user permissions, routing rules, forwarding destinations, business hours, voicemail behavior, and notification settings.
• Use an internal test contact with permission to receive the chosen channel and with do-not-disturb status set appropriately.
• Prepare the exact test message or call scenario, including the expected owner, reply, disposition, and follow-up action.
• Review registration, template, consent, opt-out, and service-window requirements before testing SMS or regulated messaging channels.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Initiate the test from the same direction a customer would use and confirm it appears in the correct conversation thread.
2. 2Verify assignment, notifications, sender identity, timestamps, contact matching, and message or call status.
3. 3Reply through Adaptive AI and confirm the recipient receives the response once from the expected number or account.
4. 4Test after-hours, missed-call, voicemail, forwarding, or automated follow-up behavior when those rules are part of the setup.
5. 5Confirm opt-out or do-not-disturb behavior stops restricted communication without blocking unrelated permitted channels.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Check channel connection status, number assignment, user availability, and routing rules before changing message content.
• Compare the contact's normalized phone number or email address when activity appears in a duplicate or unexpected thread.
• Review delivery, call, forwarding, or conversation logs for the first failed handoff and its provider response.
• Confirm business hours, quiet hours, service windows, approved templates, and opt-out status when a send is blocked or delayed.
• Test without overlapping workflows to determine whether duplicate replies come from routing, automation, or a second connected channel.

Best practices

• Use clear ownership and escalation rules so every inbound conversation has one accountable responder.
• Keep automated replies transparent, concise, and able to hand the conversation to a person when the request falls outside scope.
• Honor channel consent and opt-outs immediately and preserve the conversation history needed for support or compliance review.
• Use internal test records for routing changes and avoid sending experimental messages to active customers.
• Review missed, failed, unassigned, and long-waiting conversations as an operating metric, not only when a customer complains.