SquidSupport
Product reference / AI

Proposal review

In the app: AI → Squid Agent → Proposals → a proposal

Needs the 'Use Squid Agent' permission.

This page shows one Squid Agent proposal in full: what would change, the checks that were run on it, and the buttons to approve or reject it. It is the same card you see in the thread, with the full review above it for a change to your AI configuration.

What this page is for

A proposal is a change Squid Agent prepared and that waits for a person. Nothing changes until someone clicks "Approve". You get here from the "Proposals" tab of Squid Agent, from a notification, or from a link on another page, such as the history of a product knowledge entry or a QA rubric version.

You can open a proposal when one of these holds:

  • you asked for it;
  • it is pending and you are one of the people who can approve it;
  • you have the 'View Everyone's Squid Agent Threads' permission, the permissions of the area it changes and access to every store it touches;
  • you continued its draft in the Builder and still have access to its stores.

A suggestion to remember something for one person is only visible to that person, also not to the Owner. A proposal you may not see, and one that does not exist, shows "Not found". "Proposals" at the top left goes back to the list.

Opening the page needs Squid Agent for your organization and the 'Use Squid Agent' permission. Whether you may approve depends on the change itself; see "Approve, Reject and Cancel request".

Proposal header

The header shows the area of the change, the proposal's number and title, who asked for it and when, and its status. "Open the thread" opens the Squid Agent conversation the proposal came from, at its card.

For a pending change to a knowledge item, "Test in Playground" opens the Playground with the proposed text applied, so you can replay real customer messages against it before you decide.

The statuses are:

  • "Pending · You can approve", "Pending · Needs your check" (a box must be ticked first), "Pending · Not ready" (a requirement is not met yet) and "Waiting for approval" (someone else has to approve);
  • "Executing" while the change is being made, then "Executed";
  • "Needs attention" or "Failed" when a step stopped;
  • "Rejected", "Cancelled", "Expired", "Out of date" (what it changes was edited after it was proposed), "Replaced" (another proposal for the same thing was approved instead) and "Rolled back" (its roll back was approved and has run).

Builder review of an AI change

For a change to your AI configuration, the page first shows what the AI Builder made of it, read-only:

  • "Diff": what the draft changes against the live version.
  • "Coverage check": whether the draft covers the situations it should, as "Covered", "Partly covered" or "Not covered", or a line saying that no check was run, that it had not finished when the change was proposed, or that it failed.
  • "Test replies per channel": replies the draft wrote to test messages, per channel. They are run on the draft now and again on the exact version when it is approved. A line says so when no test reply was run or when the replies are older than the draft.
  • "What runs when it's approved": the steps, in order. Each step runs with the approver's access.

Pinned when the proposal was made are the draft, the live version it replaces, the stores and channels it is assigned to and the test plan. If any of these change before approval, the proposal goes out of date.

"Ready to go live?" lists, for a go-live change, whether each part passed a test on this exact version in the last 30 days.

"Open in Builder (read-only)" at the bottom opens the Builder session behind the draft. Nothing can be edited from this page.

The proposal card

The card shows:

  • the area, the stores it touches (or "Organization" for a change to all of them), and the status;
  • who asked and when, and for a pending proposal the day it expires;
  • the change itself as before and after;
  • for an automation rule: how many recent conversations it would have matched, and its matches while it ran in dry-run;
  • after approval, the steps of the change and how far each one got.

Stores you may not see are counted as "1 store you can't see" or the corresponding number, with "Outside your access" on hover. Their names are hidden.

Checks before Approve

Some proposals carry a warning and a box you must tick before "Approve" turns on.

  • "This conversation read customer-written text." Squid Agent read messages from customers while it prepared the change, so the wording may repeat what a customer asked for. Wording that Squid's checks recognise as the same as, or close to, customer text is highlighted. Text without a highlight can still come from a customer, so read all the proposed wording. Then tick "I've checked the wording and want to go ahead".
  • "Decision check." The change goes against, or touches, a decision or constraint that Squid Agent has in memory. When you may read that memory, the card quotes it, says who decided it and when, and links to the memory. When you may not, the card says the decision is outside your access and shows no text, name or link. Either way, tick "I've read this decision and want to go ahead".
  • "Not ready." A requirement is not met, for example a version without a passing test, a store whose FAQ list is full, or an A/B test whose variant has not been saved and tested yet. "Approve" stays off until it is.
  • A temporary change, such as one made for an incident, says when it ends. "Revert automatically at the end" lets Squid roll it back by itself at that time. Without it, Squid proposes the roll back and someone who may approve it clicks once, or keeps the change.

Approve, Reject and Cancel request

Who may approve. This is fixed when the proposal is made:

  • If you asked for the change and at that moment held every permission it needs, in every store it touches, only you can approve it.
  • Otherwise, and for a proposal Squid made by itself, anyone with 'Use Squid Agent' who holds those permissions and stores can.
  • A schedule and a memory for one person run as their owner, so only that person approves them.

Permissions and stores are checked again at the moment of the click. When you cannot approve, the card says "You can't approve this" with the reason and names up to three people who can. When a proposal is open to everyone with the right access, those people get an in-app notification when it is made.

"Approve" starts the change. Each step runs with your access and is recorded under your name. You can leave the page; it keeps going. Before every step Squid checks again that Squid Agent is on and not paused and that you still hold the permissions and stores. If not, the change stops at that step; a step that already ran stays.

Approving is refused when:

  • a box above the button is not ticked yet;
  • what the proposal changes was edited since it was proposed. The proposal then turns "Out of date";
  • the proposal has expired;
  • Squid Agent is paused by Squid.

The change itself cannot be edited on this page. To change it, ask Squid Agent for a new proposal. The one exception is a suggestion to remember something, which can be edited and approved in one step.

"Reject" needs a reason of 1 to 500 characters. The person who asked gets a notification with the reason. Nothing is changed. On a fix for failed QA checks, someone with 'Edit QA Settings' can also tick "These tickets were fine", which dismisses the QA findings behind the fix so they leave the QA score. Only someone who could approve the proposal can reject it, so a proposal that only its asker can approve cannot be rejected by anyone else. You cannot reject your own proposal; use "Cancel request".

"Cancel request" is for the person who asked: it withdraws a pending proposal. Rejecting and cancelling still work while Squid Agent is paused.

For a draft of an AI change, "Continue in Builder" opens an editable copy of the draft that is yours. For a Builder draft, it needs the 'Edit AI Config' permission and access to every store the draft touches and every store that uses its configuration set. For a direct configuration edit, it also needs the permissions the change itself needs, including 'Edit AI Tools' when it switches tools. A draft from a conversation that read customer text needs the same tick as approving. A roll back cannot be continued. Every pending proposal for that draft is cancelled with "Continued in the Builder by" and your name, and the change can only go live from the Builder from then on. A draft can be continued once. It is refused while an approval of the draft is running and after the draft went live.

A pending proposal expires 7 days after it was made. A suggestion to remember something expires after 30 days. An expired proposal cannot be approved; ask for a new one.

Expected and measured impact

"Simulate it first" is shown on a pending change to your AI configuration or to a knowledge item, to the person who asked for it and to other people who can see it and meet its permission, store-access and readiness requirements, while Squid has simulations switched on. Those other people can simulate even when approval is reserved for the person who asked. It replays up to 40 recent opening customer turns on the proposed change, in a test sandbox, and grades the replies with your QA rubric. The button's own line says 30 to 50; the number that runs is at most 40, and at least 10 are needed. The same person or people can start it again when a simulation failed or the proposal changed since. The card then shows the "QA pass rate" and "Handed to a person" as they are live and as simulated, with the difference and its range, and "See the conversations side by side" opens the simulation. Each replay combines the customer messages before the first AI reply, limited to 4,000 characters. Later turns are not simulated. Nothing is sent and no customer-support change is made. If the proposal changes after a simulation ran, the card says so.

Measured impact appears after a change went live, for AI configuration drafts, direct configuration edits, go-live changes and redeployments; knowledge changes (a knowledge item, widget FAQ entries, product knowledge); and rule creation, updates and go-live changes. Mailbox mode changes and changes that only turn a rule off or into dry-run are not measured. Neither is a roll back.

  • For an AI or knowledge change Squid measures the AI hand-over rate and the average QA score. For a rule it measures the first response time and first-response SLA compliance.
  • Checks are due 7 and 14 days after execution; the second reading is final. The baseline uses the 14 whole UTC days before the execution day. QA is an exception when its baseline is read on the execution day: its 14-day window includes that day. The comparison starts the day after execution and ends the day before the check, or on the check day for QA. A delayed check uses the day it actually runs.
  • Each metric is marked "better", "worse", "no clear change" or "not enough data". A small difference that could be chance counts as no clear change.
  • The numbers are read with the approver's access. Numbers of a report you may not open are hidden.

This shows that the numbers moved after the change, not that the change caused it. When a metric got worse, the person who approved and the person who asked get one notification, and Squid tries to prepare a roll back as a new proposal. If it cannot, the card says so. Nothing is rolled back until someone approves that one.

After a decision

  • Executed: the card says who approved it and when. "Roll back" creates a new proposal that undoes the change; nothing changes until that one is approved. The button can read "Roll back (turn it off)" for a new rule, "Roll back (back to drafts)" for a go-live, "Restore the earlier version" for a skill, and "Undo the roll back" on a roll back.
  • Needs attention: a step stopped on something that may pass, and the card shows which steps finished. "Retry" starts again at the step that stopped; finished steps do not run again. The person who approved retries. Someone else can only retry when that person has left or lost the access the change needs, and then becomes the approver.
  • Failed: a step stopped for good. There is no "Retry". For the person who asked, "Ask Squid to try again" puts a question in the box that asks for the change anew. If part of the change ran, "Roll back" is offered.
  • Rejected, Cancelled, Expired, Out of date, Replaced: nothing was changed. Ask Squid Agent for a new proposal if you still want the change.

Roll back

"Roll back" is offered on an executed proposal, and on one that stopped after at least one step changed something. It needs the same permissions and stores as approving the change, and it is refused while Squid Agent is paused. It never undoes anything by itself: it creates a new proposal, asked by whoever clicked, that goes through approval like any other. When that one has run, the original shows "Rolled back". A proposal has one pending roll back at a time.

Some changes cannot be rolled back. For some, the card hides the button and says why. For others, "Roll back" is still shown and the request is refused when clicked:

  • a change that has no earlier version to bring back, or that put nothing live that Squid can undo;
  • an AI configuration that was changed again after the proposal ran;
  • an A/B test change: stop the test instead;
  • a new skill or a shared skill: delete it from the Skills list instead;
  • a paused schedule: click "Resume" on the schedule;
  • a closed goal: set a new goal instead;
  • a created task: close the task on the Goals tab with a note;
  • translated wording: restore an earlier version from the entry's history. A change to which original an entry translates can be rolled back here;
  • a rule that no longer exists or is already off.

A temporary change shows "Temporary: ends …". At the end Squid prepares the roll back with the access of the person who approved the change and notifies them; they approve it with one click or keep the change. Squid approves the roll back itself only when "Revert automatically at the end" was ticked at approval. When the roll back cannot be prepared, for example because that person lost access, the card says "The roll back needs you" or the reason, and nothing is reverted.

Every approval, rejection, cancellation, retry, roll back request and "Continue in Builder" is recorded in the audit log under Settings → Audit Log.