SquidSupport
Product reference / Settings

Organization settings

In the app: Settings → Organization

Needs the 'General Settings' permission.

Settings that apply to your whole organization and every store in it: the report timezone, the starting language for new stores, capacity limits, auto-assign on reply, explanations for manual takeovers from the AI, and whether you share improvement data with Squid. A store's own name, web address and language are not here; they are under Settings → Stores.

Organization Details

"Organization Name" shows the name of your organization. You can type a different name, but it is not stored yet: the new name shows until you reload the page and then goes back to the old one. Saving a change to the name alone tells you this. If you change the name together with another setting, the message says "Organization settings saved", but the name is still not stored.

"Organization ID" is the identifier of your organization. You cannot change it. It is the id to give when someone needs to know exactly which organization you mean, for example Squid support.

Regional Settings

"Report timezone" is the timezone your reports are grouped in. A day or a week in a report starts and ends in this timezone. Reports that let you switch to your browser's timezone use that instead while you have it selected. It is one setting for the whole organization, and a change applies as soon as you save. Until a timezone is saved, reports use UTC. If the timezone cannot be loaded, the page shows "Report timezone could not be loaded" with a "Retry timezone" button, and saving leaves the stored timezone as it was.

"Default language for new stores" is the language a store starts with when you create it in Squid. The store gets it unless you pick another language during setup. A store that is created while you connect a shop from the Squid app in Shopify does not use this setting: it starts in English.

The setting is used only at the moment a store is created:

  • It does not change the language of stores you already have. Change an existing store's language under Settings → Stores.
  • It does not set the language customers are answered in.

The default is English. The list has 13 languages.

Capacity Management

Capacity limits are a per-person ceiling on open work, kept for automatic assignment.

Each teammate has a "Max Capacity": the highest number of tickets they should hold at once. You set it per person under Settings → Team, when you edit a member. It can be any whole number from 1 to 100, and the default is 10. You cannot set it lower than the number of tickets the person holds right now. The Team page shows each person's current load next to their limit.

"Enable Capacity Limits" is on by default.

What the switch changes today is the Team page. When it is on, Settings → Team shows a capacity bar for every teammate and the "Max Capacity" field when you edit a member. When it is off, the bars and the field are hidden. Each person's limit is kept and comes back when you turn the switch on again. The Team page can only read this switch for someone who also has the 'General Settings' permission; for everyone else it shows the bars and the field whether the switch is on or off.

The switch does not change who gets a ticket today, on or off. Capacity limits are only looked at when Squid itself picks a teammate for a ticket, and at the moment nothing does that:

  • A ticket that the AI hands to your team goes to a department, or to no department, and stays unassigned until a person takes or assigns it, or an automation rule assigns it.
  • The assignment method and "Auto-assign new conversations" of a department are saved but not acted on. See Settings → Departments.

Everything that does assign tickets ignores the limits. Whether the switch is on or off:

  • It does not stop a person from assigning a ticket to a teammate who is at their limit.
  • It does not stop a teammate from claiming a ticket, or taking one over from the AI, when they are at their limit.
  • It does not stop an automation rule from assigning a ticket to a teammate who is at their limit.
  • It does not stop "Auto-Assign on Reply" from assigning the ticket to the teammate who replied.

So a teammate can hold more tickets than their "Max Capacity". The text under the switch, "Agents cannot be assigned more conversations than their max capacity.", does not describe what happens today.

The setting applies to the whole organization and takes effect when you save.

Auto-Assign on Reply

"Enable Auto-Assign on Reply" is off by default.

When it is on, a teammate who sends a reply to the customer in a ticket becomes that ticket's assignee. This also happens when the ticket was assigned to someone else: it moves from that person to the one who replied. It happens even when the teammate who replied is away, offline or at their capacity limit. The ticket's timeline gets the line "Auto-assigned to" with the teammate's name and "on reply".

It does not apply to internal notes, to replies written by the AI, to an AI draft that a teammate approves, or to a WhatsApp re-engagement template. A ticket that is already assigned to the person replying stays as it is.

When it is off, sending a reply does not by itself change who a ticket is assigned to.

The setting applies to the whole organization and takes effect when you save.

AI Handoff

This section is about how tickets move between the AI and your team.

"Require an explanation on manual takeovers" is off by default.

A manual takeover is when a teammate takes a ticket away from the AI themselves, to work on it or to pass it to another teammate, without the AI having handed it over.

When it is on, the teammate must fill in a short form before the takeover goes through: they rate how the AI handled the ticket so far, as good or bad, pick a reason from the list for that rating, and write a short explanation. Every reason needs the explanation. The collected reasons appear under AI → Performance, on the "Manual Takeovers" tab.

When it is off, the takeover only asks the teammate to confirm. No rating, reason or explanation is asked.

The setting applies to the whole organization and takes effect when you save.

Squid improvement data

"Share anonymised improvement data with Squid" is on by default.

Squid always counts two things for every organization, whatever this setting says: what Squid could not do for you, and the Squid bugs your tickets or Squid Agent chats ran into. Those counts help Squid fix problems.

When the setting is on, Squid also receives anonymised examples of what went wrong, and the text of Squid Agent chats that went wrong.

When you turn it off and save, Squid stops receiving examples and chat text, and the examples your organization already shared are deleted. The counts stay.

The switch stays disabled until the saved value has loaded. If it cannot be loaded, the page says so and offers "Try again".

Saving changes

Nothing on this page is saved until you click "Save Changes" at the bottom. The button is only shown to people who may change these settings.

Each setting is saved on its own. If one of them fails, the message names the setting that was not saved, and the others are kept. Leaving the page with unsaved changes asks you to confirm first.