Store setup guide
In the app: Home → Continue setup
Needs the 'Edit Brands' permission.
The store setup guide walks one store through what it needs before Squid's AI can answer its customers: the store's basics, the Shopify connection, the AI agent, an email address or live chat, and a test. Everything it sets belongs to that one store, except the few things marked below as shared by the organization. Each setting can also be changed later on its own page in Settings or under AI; the guide is a faster route through them, not a separate set of settings.
How the guide works
Where it opens from. As a page: from "Continue setup" and the row buttons on the "Can Squid answer your customers?" card on Home, from "Store setup" in the Help menu, from "Start setup", "Continue setup" and "Open setup guide" on a store's card under Settings → Stores, and from the "Finish setup" bar. That bar is shown under the header on every page except the guide itself, to people with the 'Edit Brands' permission, while a new organization on a trial or active plan has not yet had a store pass all five checks; it can be hidden until the page is reloaded. On the first page opened in a browser session, such a person is taken to the guide if that page is Home or the Inbox with no extra address parameters or anchor. Opening another page first uses up that automatic redirect for the session. "Add store" under Settings → Stores opens the same guide for a new store in a window over the page; it works the same way.
The header shows "Set up" and the store's name, and once the store exists a meter, "N of 5 ready". It counts the same five checks as the card on Home: store connected, AI agent created, a channel receiving, tested, and the AI switched on in drafts or auto-send. The checks are read from the store's real state, so skipping a screen never ticks one.
The steps on the left (on a wide screen) are the screens of the guide. The first pass has six: "Store basics", "Connect Shopify", "AI agent", "Support email", "Live chat" and "Test & go live". "Continue" walks them in that order. The return address, the return portal and other integrations are optional; they are listed on the last screen and on the store card, and appear in the list while you are on one.
- A step you have not reached yet is greyed out and cannot be clicked. "Support email" and "Live chat" are the exception: they can be opened at any time once the store exists.
- For the connection, AI, email, portal and chat steps, a tick normally means the saved answer is also confirmed by the store’s current state. If that state cannot be read, the guide keeps the saved tick. Store basics, return address and other integrations use the saved answer. An answered step whose current state is known to be unconfirmed keeps its number in an amber ring.
- "In progress" means you continued past the step before its proof arrived, for example before the email forwarding test passed. "Skipped" means you skipped it. "For later" means it was set aside.
- A label says what a step waits for: "Needs Shopify first" on the AI agent, "Needs Shopify first" or "Needs the AI agent first" on "Test & go live", and "Needs a verified email first" on the return portal.
The buttons at the bottom:
- "Continue" saves the screen you are on and goes to the next. On "Connect Shopify" and "Other integrations" it saves nothing, because connections are made with the buttons on the cards. On the last screen it reads "Finish".
- "Back" goes to the previous screen without saving.
- "Skip for now" leaves a screen unanswered and saves nothing from it. It is on every screen except "Store basics", "Connect Shopify" and "Test & go live". If you changed something on a screen that "Continue" would have saved, the guide asks "Skip this step?" first: "Skip without saving" or "Stay on this step". Skipping a step that was already saved earlier does not undo what was saved.
- "Finish later", at the top, leaves the guide and goes to Home when it is open as a page, or closes the window when it is over Settings → Stores. What you saved with "Continue" is kept, and the guide reopens at the first step you have not answered or skipped.
- "Finish" leaves the guide and goes to Home when it is open as a page, or closes the window when it is over Settings → Stores. It starts the product tour if you have not had it. It changes nothing on the store: the AI is on or off as you left it on the screens before.
What you typed is kept. Text you typed on a screen without saving is kept in your browser for 7 days, for you and that store only. When the guide brings it back it says so. "Continue" saves the form answers; connection, email verification and domain verification buttons can save changes immediately. Passwords and API keys are never kept in the browser draft. "Discard and start fresh" throws the kept text away, and so does "Finish".
Permissions. Opening the guide needs the 'Edit Brands' permission. Each step also needs its own permission, named in its section below. On a step your role cannot change, the guide shows a notice with the permission it needs instead of the step; "Continue" then moves past it without saving anything, so you can finish the rest and ask an administrator for that part. A person without 'Edit Brands' who opens a setup link sees one sentence on the store's state instead of the guide.
Store basics
Three answers that the rest of the guide starts from. For a new store, "Continue" creates the store; for an existing one it saves the name, the store ID, the language, the timezone and the store URL. Saving the URL is a separate action: if it fails, the other details stay saved, the guide continues, and a warning asks you to add the URL later. This step cannot be skipped, and "Continue" stays unavailable until there is a full domain, a name and a free store ID; a line under the form says which is missing.
- "Store URL": your storefront's web address. Squid takes the domain from it and uses it to suggest the email, return portal and live chat setup.
- "Store name": the name your team sees in Squid. It is suggested from the URL until you type one yourself.
- "Store ID": filled in from the name and folded away under the name; open it to change it. Lowercase letters, numbers and hyphens only. It tells your stores apart inside Squid and must be unique in your organization; when it is taken, the field opens and offers a free one. It is not your return portal's address, which is shown on the return portal step.
- "Primary store language": for a new store it starts on the organization's default language for new stores. It sets the language of the return portal and of the other places listed under Settings → Stores. It does not decide the language customers are answered in; the AI follows the conversation.
- "Timezone": the store's timezone. On a store still on UTC whose basics have never been saved in the guide, the guide proposes your browser's timezone. Reopening saved basics keeps the stored timezone, including UTC. The store's chat support hours start on it; you can pick a different one for them on the live chat step.
All of these can be changed later under Settings → Stores. Needs the 'Edit Brands' permission.
Connect Shopify
Needs the 'Edit Integrations' permission.
The AI reads the store's orders through this connection. Until a shop is connected, the AI agent step shows "Connect your store first" instead of its choices, and its "Continue" is unavailable.
"Connect with Shopify": type the "Store domain", your .myshopify.com address, and approve Squid Support in the Shopify tab that opens. There are no keys to copy. Back in the guide, "Check connection" re-reads the state if it still says not connected.
"Advanced (developers)" is only for a store that connects through its own custom Shopify app:
- "Dev Dashboard App": the "Client ID" and "Client Secret" of an app made in the Shopify Dev Dashboard.
- "Legacy Custom App": the "Admin API Access Token" of an app made before January 2026, and optionally its "API Secret Key".
- The screen lists the API scopes to set on the app. "Connect store" saves the connection.
Once connected, the card shows the shop and how many of the order lookups the AI can use. If it says the agent can use none, finish the connection on the Shopify card under Settings → Integrations. If it says the configuration has no active instructions, the agent is not answering yet; that is fixed on the AI agent step.
ParcelPanel is on this screen as well, marked as recommended: paste the "ParcelPanel API key" and click "Connect". The key is saved and then tested; with it the AI can look up shipment tracking. If the test fails, the card says why and the key stays saved.
If your organization signed up through the Shopify App Store, a new shop must be added by installing Squid Support from that shop’s Shopify admin. Typing a domain here can only reconnect a shop already linked to the organization. A successful Shopify connection also starts loading order history in the background.
"Continue" is available once a shop is connected. It saves nothing; it records the step as done.
"I can't connect Shopify right now" is shown while no shop is connected. It carries on with the rest of the setup. The step is recorded as left for later, not as done: the store keeps counting as not set up, and its card keeps asking, until a shop is connected.
Needs the 'Edit Integrations' permission. A role without it is moved past this step by "Continue", and nothing is recorded for the step.
AI agent
Needs the 'Edit AI Config' permission.
How the store's AI configuration starts. The step opens once Shopify is connected. There are up to four routes:
- "Keep the current configuration": shown when the store already has one. Continuing changes nothing about it.
- "Use our template": a ready-made support agent for order status and delivery, cancellations, address changes, returns and refunds, damaged or wrong items and product questions, with everything else handed to a person. You answer a short form, below. "Continue" prepares and assigns the template configuration. It can reuse the untouched starter configuration or resume an interrupted setup instead of creating another one.
- "Discuss in Builder": describe your policies and tone in a conversation and the Builder drafts the configuration. "Continue" opens the Builder in the same tab with this store as its target, and the Builder brings you back to the guide at the next step. The screen says "a new tab"; that is not what happens. The two switches below cannot be used on this route: this route leaves the store’s current switches and configuration in place until you deploy another configuration.
- "Copy settings from an existing store": shown when your organization has another store. Pick a "Source store". This store takes over that store's AI settings and agent name and runs the same configuration as that store, not a copy of it: editing the configuration later changes both stores.
Replacing a configuration. On a store that already has one, the template and the copy route point the store at another configuration. The guide asks you to confirm: "Build a new configuration" goes ahead, "Keep" cancels. The old configuration is not edited or deleted; it stays under AI → Settings and can be switched back to. The Builder route does not ask.
The template form. Policy and offer boxes left empty use the grey suggestions shown in them, and the agent quotes that to customers: 14 days, 30 minutes, "1–2 business days", "5–10 business days after dispatch" and "the EU and the UK".
- "Agent name": what replies are signed with. Required when the store has no agent name yet, because the agent cannot be switched on without one. On a store that has one, an empty box leaves the name as it is.
- "Return window (days)": a whole number from 0 to 3,650, counted from delivery. It is also written to the store's return policy.
- "Cancellation window", in minutes or hours: how long after ordering a customer may still cancel. Use a whole number from 0 to 43,200 minutes, or 0 to 720 hours. A blank uses 30 minutes even when hours are selected.
- "Order processing time" and "Delivery estimate": in your own words; the agent quotes them.
- "Countries or regions you ship to".
- "Who pays for return shipping?": the customer, or you. When you pay, the agent hands the return to a colleague to send a prepaid label.
- "Keep-the-item offers": on by default. On, the agent may offer a partial refund or a discount to settle a return without the item being sent back, with the percentages you fill in; percentages must be whole numbers from 1 to 100; an empty percentage uses the suggestion in the box. Off, ordinary returns follow the return-for-refund route. Approved damaged or wrong-item claims can still be handed to a person to arrange a replacement or refund. The offers can be changed later under AI → Offers.
- "Advanced template": a much longer configuration with separate flows for delivery disputes, refused parcels, fit, sealed-product and wrong-item returns.
After "Continue", the step shows "What the agent will tell customers" when you come back to it, with "Suggested" on the answers filled in for you. They can be changed later under AI → Settings.
The two switches show the store's current state and are saved when you press "Continue", only if you changed them:
- "AI agent": on, the AI answers this store's customers. Each reply uses an AI message from your plan. Switching it off also switches auto-send off.
- "Auto-send": on, replies are sent without review. Off, replies wait in the Inbox as drafts for a person to approve. Switching auto-send on needs a passed test, the same as on "Test & go live"; without one the change is refused and the screen says so. A new store therefore starts in drafts here and switches auto-send on from "Test & go live".
When the agent cannot be switched on yet, the switches are greyed out and the screen lists what is missing: no configuration, no active instructions, no agent name, or settings that could not be read. The server also refuses activation when the configuration calls specialists that are not ready.
Needs the 'Edit AI Config' permission.
Support email
Needs the 'Edit Email Config' permission.
How customer email reaches this store. The last screen requires at least one receiving channel before it offers activation: email, live chat, or a verified WhatsApp connection. The switches on the AI agent step do not make that channel check. The step can be skipped and finished later under Settings → Email, which explains every part in full.
Where both routes are offered, choose one; "Continue" asks you to choose if you have not:
- "Forward to a Squid address": keep the address your customers already use and forward its mail to the store's Squid address. You change no DNS to start receiving. Add each address customers write to, forward it, and test it; each of these is saved as you do it, not by "Continue".
- "Receive on my own domain": fill in the "Email domain", which starts from the store URL; the "Support email address" that replies are sent from; and the "Support subdomain (for receiving)". "Continue" creates the mailbox. Some DNS records are shown before that, the rest once the mailbox exists, so come back to this step to see them all under "DNS records to add". "Verify DNS" checks them; DNS can take up to an hour, and you can leave and come back. Once the records verify, the step shows how to forward your address and runs a test that proves customer mail arrives.
The step counts as done only when it is proved that customer mail arrives: the forwarding test passed, or real mail reached the store. If you continue before that, the step is marked "In progress" and "Test & go live" lists what is still missing.
"Sign-off" is the signature under the store's emails, with suggestions per language. "Continue" saves a non-empty sign-off only if it differs from the saved one. Clearing the box does not clear an existing sign-off. Settings → Email explains how the agent-name variable in it is filled in.
Needs the 'Edit Email Config' permission.
Live chat
Whether the chat widget shows on your storefront, and when. It comes after the email step; it can be skipped.
- "Live chat": on, the widget shows on your storefront once it is installed. The switch starts on, unless the widget was switched off for this store before. Live chat counts as a receiving channel only after the widget has been seen on your storefront.
- The install panel puts the widget on your site, and the support hours set when it is online. Both are the same as under Settings → Chat Widget, which explains them. A store that never set support hours stays online around the clock.
"Continue" saves the switch and the support hours. Needs the 'Edit Brands' permission.
Test & go live
The last screen of the first pass. It tests the AI agent, switches it on, and lists what is left.
"Try it on sample questions". Pick a sample question or type your own under "Customer question" (up to 500 characters) and click "Run the test". The agent answers as the store would, with your real orders and policies. Nothing is sent to a customer and nothing changes in Shopify. The screen shows the reply, and says so when the agent would hand that question to a person. A test passes when the agent wrote a reply without an error; a passed test on the agent's current configuration ticks the "tested" check. A store whose AI is on and auto-sent a reply to a real customer in the last 30 days also counts as tested; drafts a person approved do not count. A test is charged like a run in the AI Playground, except for up to 25 free setup tests shared by the organization, available before its setup has been completed. Testing needs the 'View AI Config' permission and an AI agent.
"Start in drafts". No test is needed for this. The agent writes a reply and it waits in the Inbox for a person to send, so nothing reaches a customer without you. The rows show whether "Email" and "Live chat" are receiving. The button needs an AI agent and at least one receiving channel; "Go to AI agent" and "Connect email or live chat" jump to those steps. Once on, the screen shows "On · drafts" and "Turn off", which switches the AI off for the store.
"Auto-send". The agent sends replies to customers without waiting for you. It is one switch for the whole store and unlocks when one test answer has passed on the agent's current configuration. "Turn on auto-send" asks you to confirm. When email or chat runs a configuration that has not passed a test rehearsed as auto-send, the screen asks for one more test on that channel first. If the configuration changes after the test, test again before switching on.
"Back to drafts" returns to drafts. If AI-only live chat is enabled, turn it off under AI → Settings first; otherwise the server refuses the change. When leaving auto-send, it also disables tools marked as changing external systems for this store and for configurations only this store uses. If that changes the tested setup, a fresh test is needed before switching auto-send on again.
Switching the AI on or off here needs the 'Edit AI Config' permission.
"Your setup" lists the first steps with their state in a few words, for example the connected shop, the assigned configuration and whether the agent is on, and what is still missing from the email address. Steps that are still open are marked, and "Set up" beside a row reopens that step.
"Optional steps" and "Set up later" list the optional steps the guide has not saved yet: the return address, the return portal, other integrations and live chat. They are not needed to answer customers. "Set up" opens one now, and "Set up extras now" walks through them in turn. They stay listed on the store card under Settings → Stores. The list follows the guide only: something you set up on its own Settings page instead stays on the list.
Return address
Needs the 'General Settings' permission.
Where customers send returned parcels, and where supplier returns are filed. Optional.
- "Return address": pick an existing address, "+ Create a new return address…" or "Don't assign yet". A new address needs at least a street, a city and a country. It is created for the whole organization, so other stores can use it. A store uses one fixed return address at a time. Addresses are managed under Settings → Suppliers.
- "Basecamp config set": shown for organizations that use Basecamp, and usable once Basecamp is connected and a config set exists. Pick the config set that approved supplier returns of this store are filed under, or "Don't assign yet". Config sets and their routing rules are made under Settings → Basecamp.
"Continue" assigns the selected address or creates the new one. "Don't assign yet" leaves an existing return address assigned. When Basecamp is connected, "Continue" also saves or clears its selection; that part additionally needs the 'Edit Integrations' permission and can fail after the address was saved. The address part needs the 'General Settings' permission.
Return portal & refund review
Needs the 'General Settings' permission.
Two things: whether the AI may refund, and the page where customers start a return themselves. Optional.
"Refunds" applies to refunds from email and chat, whether or not the return portal is on. "Continue" saves it even when the portal stays off:
- "Disabled": the AI does not submit refunds for this store. It hands the ticket to your team. This is where a new store starts.
- "Enabled (human review required)": refunds the AI submits wait in the Refund Hub for a person to approve.
- "Enabled (approved automatically)": the AI refunds through Shopify without a person. Settings → Refund Hub explains which refunds still wait for a person, and what enabling the first store changes for the organization.
"Enable return portal" is off by default. With it on, "Continue" saves the portal's settings, but the portal only turns on if the store has an email address that can send, because its confirmation emails have nowhere to send from otherwise. Until then, finish the email step and switch the portal on under Settings → Return Portal. Switching this box off in the guide leaves an already-enabled portal on; use Settings → Return Portal to disable it.
- "Portal language" cannot be changed here: it follows the store language from the first step. A language the portal has no translation for falls back to English.
- "Portal URL": a hosted address based on the store name. No DNS is needed. Buttons copy it and open it.
- "Custom domain" (optional): serve the portal on your own subdomain. A bare domain is refused. "Verify" saves the domain and checks the DNS records listed under it; the record for the certificate appears after the first verify. The hosted address keeps working throughout.
- "Portal settings": "Copy from another store" copies that store's reason template, return policy and order-age rule into the fields, where you can still change them; "Set them myself" leaves them to you.
- "Reason template": the reasons customers pick from. Required when the portal is on.
- "Return policy": the return window and checks this store follows. Policies are edited under Settings → Return policies.
- "Minimum order age", from 0 to 365 days: the portal refuses every return until an order is this old. 0 turns the check off, and an empty box counts as 0.
Needs the 'General Settings' permission.
Other integrations
Needs the 'Edit Integrations' permission.
All optional. "Continue" saves nothing here; each card connects with its own button.
- "Klaviyo": paste the Klaviyo private API key and click "Connect". The key is saved and then tested; if the test fails, the card says why and the key stays saved. It lets the agent look up marketing profiles and subscription status. The step counts as done once Klaviyo is connected; otherwise it is marked "In progress" and stays on the optional list.
- "Basecamp" (shown for organizations that use Basecamp): "Connect with Basecamp" opens Basecamp in another tab to approve the connection; "Check connection" re-reads it when you come back. Basecamp is connected once for the whole organization, not per store, and is disconnected under Settings → Integrations. It files supplier returns as Basecamp to-dos.
More integrations are under Settings → Integrations. Needs the 'Edit Integrations' permission.