AI Feedback settings
In the app: Settings → AI Feedback
Needs the 'Edit AI Config' permission.
Decides when teammates are asked to explain why they rejected or heavily rewrote a reply the AI drafted, and whether that feedback must be approved before it is used. It is one policy for the whole organization and every store. The feedback itself is read and moderated on another page: AI → Feedback, which the "Review feedback →" link opens for people who hold the 'Moderate AI Feedback' permission.
Collecting feedback
These settings apply to AI drafts: replies the AI wrote that a teammate approves or rejects in the ticket before anything is sent.
"Rejection feedback" decides what happens when a teammate rejects an AI draft. The default is "Optional".
- "Off": the draft is rejected at once and nothing is asked.
- "Optional": the dialog "Reject AI draft" asks why. The teammate can type a reason and click "Reject draft", or click "Reject without reason".
- "Required": the dialog has no "Reject without reason" button. "Reject draft" only works once a reason is typed.
In both dialogs "Cancel" closes the dialog and leaves the draft in place.
"Rewrite feedback" decides what happens when a teammate sends an AI draft after rewriting most of it. The default is "Off".
- "Off": nothing is asked, however much was changed.
- "Optional": the teammate is asked what was wrong with the draft and can skip the question.
- "Required": the teammate must answer; there is no skip.
The question is only asked when the teammate edited the draft and the change reaches the "Rewrite threshold".
"Block sending until rewrite feedback is given" decides when the rewrite question is asked. It is on by default.
- On: a dialog asks before the reply goes out. With "Rewrite feedback" on "Required", the reply is not sent until the teammate answers.
- Off: the reply is sent immediately, and a small panel asks afterwards.
It has no effect while "Rewrite feedback" is "Off"; the switch is then disabled and says so.
"Rewrite threshold" is how much of the draft must have changed before it counts as a major rewrite. The slider goes from 10% to 100% in steps of 5%, and the default is 70%. A lower value asks for feedback after smaller edits; 100% asks only when almost nothing of the draft is left. The comparison looks at the words of the draft and of the sent reply, not at formatting. It compares which words occur in the two texts, not their order or how often they occur, so moving sentences around does not count as a change. The slider is disabled while "Rewrite feedback" is "Off".
What these settings do not do: they do not change how the AI writes, and they do not stop a teammate from editing, approving or rejecting a draft. They only decide whether a question is asked.
Trust & moderation
"Require approval before feedback reaches the AI Builder" is off by default.
Feedback that teammates write is read by the AI Builder when you ask it about the quality of the AI's replies. Every piece of feedback is Pending until someone approves or dismisses it under AI → Feedback.
- Off: the AI Builder can read all feedback except dismissed feedback. Pending feedback is included.
- On: the AI Builder can read only approved feedback. This also applies to feedback that was collected before you switched it on, so earlier feedback that nobody approved is no longer read.
Dismissed feedback is never read, whatever this setting says.
The setting only covers the text teammates write. Counts of how often drafts were approved, edited or rejected are not held back by it.
No feedback changes a live prompt by itself. A prompt only changes when someone edits it and activates it.
Saving changes
Nothing on this page is saved until you click "Save settings". The new policy applies to the whole organization.
When a change reaches teammates. A change does not reach a ticket that is already open. Each teammate's inbox loads the feedback settings once, the first time they open a ticket with an AI draft, and keeps them until the page is reloaded. If loading fails, the inbox uses "Rejection feedback" on "Optional" and "Rewrite feedback" on "Off". Opening another draft can retry the load; reloading the page also retries it. So after you save:
- a teammate who already worked on a draft since their last reload keeps the old settings, in open tickets and in tickets they open next, until they reload the page or sign in again. This includes you, in your own inbox;
- a teammate who reloads, signs in or has not opened a draft yet gets the new settings.
Two parts do take effect at once, without a reload:
- "Rejection feedback" on "Required" is also checked when a draft is rejected. A teammate whose inbox still has the old setting and who rejects without a reason gets an error, and the draft stays in place so they can reject again with a reason.
- "Require approval before feedback reaches the AI Builder" is applied each time the AI Builder reads feedback.
The rewrite settings ("Rewrite feedback", "Block sending until rewrite feedback is given" and "Rewrite threshold") are only applied in the teammate's inbox, so for them the reload is the only way a change arrives.
Saving needs the 'Edit AI Config' permission.