SquidSupport
Product reference / Settings

Chat Widget

In the app: Settings → Chat Widget

Needs the 'View Widget Config' permission.

The chat widget is the chat button on your storefront. This page installs it on a store's website and sets how it looks, what it says, when it is online, which FAQ buttons it offers and what happens to a chat when the visitor leaves. Every store has its own widget and its own settings.

Store and access

The store picker at the top chooses the store whose widget you are setting up. Colours, texts, FAQ buttons and the install code below all belong to that store. Without any store, the page shows "No Stores Found" with a button to Settings → Stores.

Opening the page needs the 'View Widget Config' permission, and the store list it loads needs 'View Brands'. Saving is split in two:

  • the widget's settings (everything except the FAQ buttons) are stored with the store, and saving them needs the 'Edit Brands' permission;
  • changing the FAQ buttons needs the 'Edit Widget' permission. Without it, "Save Settings" saves the other settings and leaves the FAQ buttons as they were.

Edits are saved with "Save Settings" at the bottom of the settings card, except restoring an FAQ version, which saves immediately. FAQ buttons save first; if the other settings then fail to save, the FAQ changes stay saved. The preview follows your edits before you save. A saved change reaches your storefront on the next page load.

Install the widget

The install card puts the widget on your website. Which steps it shows depends on the store.

Shopify store connected through the Squid Support app: there is nothing to paste. The widget ships with the app as an app embed. "Open theme editor" opens your theme's "App embeds" with "Squid Support Chat" already switched on, and you click Save there. When Squid cannot switch it on for you, the card tells you to switch it on yourself and then save. App embeds are off after installing the app, so this step is needed once. An "Advanced" section still offers a manual snippet for a custom storefront; use one installation method. The current widget prevents a second copy from mounting on the same page.

Any other store: tabs give the steps per platform ("Shopify" for a store that is not connected through the Squid Support app, "WordPress", "Other"). "Copy embed code" copies a small script. Paste it into your site's footer scripts, before the closing body tag, on every page that should show the chat.

Verify installation shows when the widget last loaded on a page: "Last load recorded …" or "Seen on a storefront …", and the most recent address named by a load. That address can be older than the load time shown. A load is recorded at most once every 5 minutes, so on a quiet store the time can be old although the widget is on. To refresh it, open your store in a new tab, wait up to 5 minutes and click "Check installation" or "Check again". "No load recorded for this widget yet" means Squid has no recorded load. It does not prove that the widget was never opened.

Widget Settings

"Enable chat widget" is on by default. When it is off, the widget stays hidden on your storefront even though the embed or snippet is installed. Use it to take chat offline without touching your theme. Like every setting here, it applies once you save.

Appearance

  • "Horizontal Position": "Right Side" (default) or "Left Side" of the page.
  • "Distance from Bottom (px)": how far above the bottom of the page the chat button sits. The field shows a range of 0 to 500 pixels; the default is 20. Entering 0 currently resets it to 20. Raise it when the button covers something on your site, such as a cookie bar.
  • "Primary Color": the colour of the chat button, the widget's header and its buttons and accents. Text on top of it is made light or dark by the widget so it stays readable. Pick it or type a colour code. The default is a purple-blue.

Messages

  • "Greeting Message": shown above the form when a visitor opens the widget, and in the proactive FAQ popup. Default: "Hi! How can we help?".
  • "Offline Message": shown outside your support hours. Default: "We're offline. Leave a message!".

Support hours

"Support hours" is off by default. Off, the widget shows as online around the clock.

On, you choose a timezone and, per day, whether you are open and from when to when. Monday to Friday start as open from 09:00 to 17:00; Saturday and Sunday as closed.

Outside these hours a visitor without a chat in progress sees your Offline Message and a form for name, email address and message instead of a chat. A message left that way becomes an email ticket. A visitor who already has a chat keeps that chat. The proactive FAQ popup is hidden outside these hours too. A storefront page that was opened while you were still open keeps showing chat until it is reloaded.

The timezone starts as the store's timezone and is stored with this schedule. Changing it here does not change the store's own timezone or any other store.

These hours only decide whether the widget offers chat. They are not the schedule an SLA policy counts in; that is set per policy under Settings → SLA Policies.

FAQ buttons

FAQ buttons are questions shown in the widget before the visitor types. Each has a question and, optionally, a saved answer.

  • With a saved answer ("Saved FAQ"): clicking it before a chat exists shows the answer at once. No ticket is created. Clicked inside a chat that is already going on, the question is sent as the visitor's message. The saved answer comes back unless a person last replied or the visitor is waiting for the team; in those cases, the question follows normal chat handling. Saved answers are public, fixed text that anyone can read before giving contact details, so do not put customer-specific information or template variables in them.
  • Without an answer ("Starts a chat"): clicking it starts a chat with that question, handled like any other chat. If the visitor has not filled in name and email address yet, the question is put in the message box first.

"Add question" adds a button; a store can have up to 10. A question can be up to 120 characters and an answer up to 2,000. Drag a row to change the order, use the switch on a row to hide a button without deleting it, and the bin to remove it. Each row shows how often the button was clicked and when it was last clicked. That counts clicks, not solved tickets.

With no FAQ buttons, visitors start by filling in their name and email address.

"History" on a saved question shows earlier versions, who changed them and when. With the 'Edit Widget' permission, "Restore" brings back an earlier question, answer and on/off state immediately, without clicking "Save Settings".

Proactive FAQ popup

"Show the FAQ popup" is off by default. On, your FAQ questions appear in a small bubble above the chat button, without the visitor opening the widget. It appears about a second and a half after the page loads. A visitor can dismiss it for the rest of their visit in that browser tab; clicking one of its questions dismisses it too. It needs at least one FAQ button; without any, nothing is shown. A visitor who already has a chat does not get it.

  • "Show on home page": the popup appears on your storefront's front page.
  • Other pages: add page paths, one per row, starting with a slash. A path without an asterisk matches that exact page; end a path with an asterisk to match everything under it, for example every page under your policies. Only the path counts, not what follows a question mark. Up to 20 paths of up to 200 characters.

The popup only shows on the pages you chose, and only during your support hours when those are on.

Behavior

"Require email address" is on by default. The switch is saved with the store, but the widget does not read it: a visitor always has to fill in a name and an email address before starting a chat or leaving an offline message, whether the switch is on or off.

Auto-close inactive chats

"Close chats when the visitor leaves" is off by default. On, an open chat is closed when the visitor has left your site and has neither come back nor written within the grace period. If the visitor types again later, the same chat is reopened. One exception: when the AI had asked whether the issue was solved and still handles the chat, the chat is marked resolved instead of closed, and no follow-up ticket is made. Turning the switch off also stops chats that were already waiting to be closed.

"Grace period (minutes)": how long to wait after the visitor leaves. 1 to 1440 minutes (one day); the default is 5.

"Follow-up ticket" decides what happens when such a chat closes. It needs the visitor's email address and a mailbox of the store that can send email; without those the chat closes without a new follow-up ticket. Billing restrictions can also prevent a new ticket. A previous follow-up ticket is reused rather than creating another; one in the trash stays there.

  • "Off — just close the chat": nothing more happens. This is the default.
  • "AI writes and sends the first email": Squid creates an email ticket linked to the chat, with the chat's transcript, and queues the AI to write and send the first email. If queuing fails, the ticket stays open for your team. This needs the AI agent to be enabled for the store with automatic sending and an active prompt. Until that is the case, the tickets are created for your team to answer instead, with a note saying why.
  • "Your team writes the first email": Squid creates the linked email ticket and leaves it for your team.

Preview

The card on the right shows the widget with your current edits, before saving. Switch between "Desktop" and "Phone" to see both sizes; the phone view is 393 pixels wide. Click the chat button in the preview to open the widget and see the form a visitor fills in, including your FAQ buttons. The preview is a picture of the widget, not a working chat.