Coverage
In the app: AI → Coverage
Needs the 'View AI Config' permission.
Coverage shows, per customer topic, how many conversations came in, how many the AI answered on its own and how many it handed to your team. It is also where you set a topic to "Human only". Once topic detection is switched on for your organization, the AI hands those messages over instead of answering them; until then the choice is saved but shown as "Not enforced yet" and the AI keeps answering.
Filters
The row at the top chooses what the table counts.
- Store. One store, or "All stores". The page opens on the first store in alphabetical order, because a mode can only be changed for one store at a time. A teammate whose access is limited to certain stores only sees those stores.
- Channel. "Email" or "Chat & WhatsApp". "Chat & WhatsApp" covers every channel that is not email.
- Period. "7d", "28d" or "90d". The default is 28 days. The period ends yesterday: today's conversations are not counted yet. A conversation is counted on the day it was created.
- "%" or "Count". Shows "Handled by AI" and "Handed over" as a share of the topic's conversations or as a number. The "Conversations" column of a topic is always a number.
Changing a filter reloads the table. While the new selection is loading, or when it failed to load, the table still shows the previous selection and the mode switches are locked until the selected store and channel have loaded.
Topic table
Topics come from Squid's standard list of 27 topics in 11 groups, such as "Where is my order" and "Returns and refunds". The list is the same for every organization. Each conversation with a recorded topic is counted under one topic: its first recorded topic. Conversations without a recorded topic are left out, as are deleted, merged and example tickets and outbound tickets the customer never answered.
A group row shows the totals of its topics. Click it to open or close the group; "Problem with the order" and "Returns and refunds" start open. The number after the group's name is how many topics it holds. A "New" label on a group and a "v2" label on a topic mark what was added in the current version of the list. The info button after a topic's name shows what the topic means.
The columns:
- "Conversations": how many conversations were placed on the topic.
- "Handled by AI": conversations with an AI-written reply, no reply attributed to a teammate and no current handover. AI drafts that a teammate approved and sent can count here too. Saved FAQ answers do not count as AI replies. The small bar is green from 80%, blue from 50% and amber below that.
- "Handed over": conversations the AI passed to your team. Conversations that are in neither column were answered by a person, by both the AI and a person, or have no reply.
- "Top handoff reason": the most common reason the AI gave when handing the topic over, with its share of the recorded handoff events for that topic in the selected period. Repeat handoffs count again, and a handoff in the period can belong to an older ticket, so these reasons do not use exactly the same population as the conversation totals. Hover over it to see up to three reasons. A group row shows the top reason of the whole group.
- "Mode": who answers the topic. See "AI and Human only modes".
Every number of a topic that is not zero is a button: it opens the conversations behind it.
The numbers are counted once a night, after 02:00 UTC, and the last few days are counted again each night because conversations keep getting replies. The line "Counted through …" under the table gives the last day that is included. The nightly count runs for organizations that have Squid Agent. Without it the page shows "No conversations yet" with a "Set up your AI agent" button, also when the AI has answered conversations.
AI and Human only modes
Needs the 'Edit AI Config' permission.
Each topic has a switch with two positions.
- "AI": the AI answers the topic, as it does without this page. Under the switch it says "inherits: AI".
- "Human only": the AI hands every customer message on the topic to your team before it writes a reply or runs a tool. Which topic a message is on is decided, for this hand-over, from the category the AI gave that message, using your category mappings. The hand-over reason is recorded as "Topic set to Human only". The row then shows "Handed to your team without an AI reply", and the group row counts it, such as "2 human only".
If a topic-policy lookup fails, the AI continues with its usual behavior instead of enforcing the mode for that run.
What the customer notices of a "Human only" hand-over is the same as for any other hand-over by the AI. The AI itself writes nothing to the customer about the topic:
- Email. The conversation goes to your team with an internal note that names the topic. The customer gets a message only when "Acknowledge escalations" is on for the store under AI → Advanced settings: then the acknowledgment message is sent. On a store where auto-send is off, for a mailbox in "Draft only" mode, while the store cannot send email yet, or when the customer address is one of your organization’s own mailboxes, that message waits as a draft for a person to approve. With "Acknowledge escalations" off, the customer hears nothing until a teammate replies.
- Live chat. The visitor gets the store's "Handoff message" and waits for a person. On a store with "AI-only live chat", the choice under "When the AI would escalate" applies: with "Escalate via follow-up email ticket" the visitor gets the "Ticket confirmation message", an email ticket is created and the chat closes; with "Don't escalate" the visitor gets the "Boundary message", at most once every 6 hours per chat, and the chat stays with the AI. The AI still does not answer a "Human only" topic then, so a visitor who writes again within those 6 hours gets no reply to that message.
- WhatsApp. The conversation goes to your team and nothing is sent to the customer until a teammate replies.
Your team is alerted in the app as for every hand-over.
A mode is not a setting of the store. It is saved on the config set the selected store uses on the selected channel, and the line above the table names that set. A set that also runs for other stores or channels shows "Shared · N stores"; the first time you change a mode on a shared set, a dialog titled "This config set is used by N stores" lists them and asks you to confirm, because the change applies to all of them. The number counts store-and-channel uses: one store using the set for email and chat can count twice. Clicking "AI" on a topic that is "Human only" removes the setting again.
When a change takes effect depends on the config set:
- Version control on (the line shows "Version control on · live: v…"): the change is saved to the set's draft and reaches customers with the next release. Until then the page shows "Unreleased change." with an "Open Version control" button.
- Version control off: the change is live as soon as it is saved.
Not enforced yet. "Human only" only changes what the AI does once topic detection is switched on for your organization. Until then the page carries a "Preview" label and a notice that topic detection is running in shadow, and every "Human only" switch shows "Not enforced yet": the mode is saved, but the AI keeps answering. There is no switch for this in the app; Squid turns it on per organization.
"Human only" can only add a hand-over. It never removes one: escalation keywords, return rules and mailbox modes keep working as before. For a mailbox in "Draft only" mode, a note under the table says that it overrides "AI": the AI drafts and a person sends.
With "All stores" selected the column is read-only and summarizes the config sets in use, such as "AI in all 3 sets" or "Human only in 1 of 3 sets". A store without a config set for the channel shows "No AI config".
Changing a mode needs the 'Edit AI Config' permission; without it the page shows "View only". A teammate whose access is limited to certain stores cannot change modes on a config set that also runs for a store outside their access.
Notices on the page
- "Unreleased change." A topic change is waiting in the draft of the config set. Release the set to apply it.
- "AI is off for …" The AI agent is switched off for the selected store. The table shows past conversations; mode settings are kept and apply once the AI is on.
- "N AI categories aren't mapped to a topic." Some conversations landed on the topic "Other" because your AI uses category names of its own that Squid could not place. "Map them" opens "Map your AI categories".
- A red notice with "Retry": the selection could not be loaded.
Conversations behind a number
Clicking a number opens a panel on the right with the conversations it stands for: all conversations of the topic, the ones handled by the AI, or the ones handed over. Each row shows the customer, how long ago the conversation was created, the ticket number, the subject, the store and whether the conversation was "AI handled" or "Handed over", with the hand-over reason. Click a row to open the conversation in the Inbox.
The list is ordered by when the topic was first recorded, newest first, and loads 25 conversations at a time; "Load more" gets the next 25. The list uses the date the topic was first recorded to select conversations for the period; the table uses the conversation’s creation date. The list reads current AI handling and handover state, while the table uses the nightly count. These differences can make the list and the table disagree. In the list, an "AI handled" badge can also appear on a conversation with human replies; use the "Handled by AI" number to open the narrower list without those replies.
Map your AI categories
The AI gives every customer message a category. When your prompts use category names that are not on Squid's list and Squid cannot place them, those conversations are counted under "Other". This panel lists such category names from the last 28 days, across all channels, largest first and at most 50, each with its number of conversations and an example ticket.
For each name, choose the topic it belongs to and click "Map". Where Squid has a guess, "Suggested: …" fills it in for you. A mapping:
- applies to the whole organization, in every store;
- re-groups the stored table totals at once and updates recorded topics from the last 90 days for the conversation lists;
- applies to new messages from then on;
- wins over the topic Squid would have chosen itself.
When nothing is left, the panel shows "Everything is mapped".
Mapping needs the 'Edit AI Config' permission and access to all stores, because a mapping changes the numbers of every store. Others can open the panel through "See them" and read it.