AI Config Sets
In the app: AI → Advanced → Config Sets
Needs the 'View AI Config' permission.
A config set is one complete AI setup: the prompts, specialists, tool settings and variables an AI agent runs on. This page lists the config sets of your organization and lets you create, copy, export, import and delete them. Config sets belong to the organization; stores are assigned to them.
What a config set is
A store's AI agent does not have its own prompts. It answers from the config set the store is assigned to. Several stores can share one set, so a change can affect every store that uses it. When version control is on, ordinary draft edits wait until a release is published; return shipping fees are an exception and remain on the editable set. Keeping separate sets is how one store can answer differently from another.
A store can use one set for everything, or separate overrides for email and for chat and WhatsApp together. A configured store with no assignment falls back to the organization’s default set. A store whose AI settings have never been created currently gets no config set from this fallback.
Seeing this page needs the 'View AI Config' permission. Creating, importing, cloning, deleting, setting the default and opening the Builder need 'Edit AI Config'; without it those buttons are not shown.
Config set list
The page loads up to 50 config sets, with the default set first and the rest by name. There is no control here to load further sets. Newly cloned sets are appended until the page is reloaded.
- "Name": the set's name, a "Default" badge and star on the default set, and its description. Click the name to open the set.
- "Resources": what the set contains: the number of distinct prompts and of prompt versions, specialists, tool overrides and variables. Both prompt counts exclude the categorizer. "Tool overrides" counts the tools whose on or off setting was changed for this set, not the tools the agent can use.
- "Stores": how many stores explicitly assign the set as their default or as a chat and WhatsApp or email override. Stores that inherit the organization’s default without an explicit assignment are not counted. Open the set to see its stores.
- "Actions": the buttons described below.
Releases of a set that uses version control are not listed as rows of their own; they are inside the set.
With no config sets, the page shows "No config sets yet" and, for people who may edit, "Create your first config set". If the list cannot be loaded, "Couldn't load config sets." offers "Try again".
The buttons in a row:
- "View details" opens the set.
- "Export" downloads the set as a file.
- "Discuss & improve in Builder" starts a Builder session for this set and opens it. The session edits a draft; saving that draft does not change the set. Applying the Builder’s changes to the config set is a separate step.
- "Set as default", "Clone" and "Delete": see below.
Create Config Set
Needs the 'Edit AI Config' permission.
"Create Config Set" opens "Create New Config Set".
- "Name" is required and can be up to 200 characters.
- "Description" is optional, up to 2,000 characters. Use it to say what the set is for.
"Create" makes a set with an active categorizer already added, but no other prompts, specialists or variables. No store is assigned to it. Open it to add its content, or use "Discuss & improve in Builder" to have the Builder write it. A new set has no effect on customers until a store is assigned to it.
Clone, default and delete
Needs the 'Edit AI Config' permission.
"Clone" opens "Clone Config Set" and asks for a "New Name". The copy holds what the original holds: its prompts and their versions, specialists, tool settings, non-system variables and offers. System variables are supplied by Squid rather than copied. It is independent from then on, and no store is assigned to it. Cloning is the safe way to try a change: edit the copy, test it, then assign stores to it.
"Set as default" (the star) makes a set the organization's default: the set a store falls back to when it has no assignment of its own. Only one set is the default, so the previous one loses the mark. A set tied to a single store cannot become the organization’s default. The change can also be refused if recorded policy checks failed for newly affected stores and those failures have not been reviewed. Changing the default can change which set answers for stores without their own assignment, at once. A teammate whose access is limited to certain stores cannot change the default, unless the stores they have access to are all the stores of the organization.
"Delete" removes a set after you confirm. It cannot be undone. The page blocks it in these cases:
- The default set cannot be deleted: its bin is switched off and says "Cannot delete the default config set". Make another set the default first.
- A set that stores still use cannot be deleted; a message says how many stores are still assigned. Assign those stores to another set first.
- A set with version control switched on cannot be deleted. Turn version control off first; the message has an "Open Version control" button that goes there.
Export and import
"Export" opens "Export Config Set" and downloads the set as a JSON file that can be imported again, also into another organization.
- "Include store AI behavior settings" adds the AI behaviour settings of one store you pick under "Store", such as escalation rules, disclosure, reply delays and image reading. The file also records whether that store’s AI is on and sends automatically, despite the dialog saying these are never carried over. Importing does not apply those two switches.
Exporting needs only the 'View AI Config' permission.
"Import", at the top of the page, opens "Import Config Set" and creates a new config set from an exported file. An existing set is never overwritten.
- "File": the exported JSON file, at most 5 MB. Export keeps one current version per prompt, preferring the active version; it does not carry full prompt history.
- "Name" is optional. Fill it in to give the imported set a different name than the one in the file.
- "Apply store AI behavior to a store" copies the store behaviour settings from the file onto the store you pick, if the file contains them. It never switches the AI on or off and never changes automatic sending.
After the import, a message names the new set. If parts of the file could not be used, the message says how many warnings there were and shows the first one. The imported set is not assigned to any store.