Compile a new draft from newer conversations and your team’s review decisions, without changing anything for customers.
A retrain compiles a new Brain draft. It reads your past imports, your team’s
review work, and, if you allow it, your live conversations. It produces a draft
next to the version you run today.Nothing changes for customers until you review and publish the new draft.Open it from Retrain in the Brain header, or go to /brain/retrain.
Retraining is limited to owners and admins.
Kai never learns from its own unreviewed output.A reply Kai sent enters the training corpus only when a person acted on it:
a reviewer marked it Good output, or
a reviewer wrote a Corrected reply, and then the reviewer’s words replace
what Kai actually sent.
An AI reply nobody rated is dropped. Internal notes are dropped. A conversation
marked Needs follow-up is excluded completely, including the customer’s own
messages, because the outcome of that conversation is not yet known.What customers wrote, and what your team wrote, is always usable. Only Kai’s own
words need a human decision first.
This is why turning on All live conversations is safe. Kai reads the
customer side and the human side of every thread, and still ignores its own
unvetted replies.
Reuses everything already understood, and keeps only well-attested patterns. The quick, conservative option.
Standard
Reuses prior understanding and re-derives every answer, flow and rule. The right choice most of the time.
Deep
Re-reads every conversation from scratch and surfaces rarer patterns. The slow, thorough option.
The cost sits in one place: reading a conversation for the first time. Light and
Standard reuse what Kai already understood about a conversation, so a retrain
over a mostly unchanged history is cheap. Deep ignores that and reads every
conversation again, so it costs one reading call for every conversation in the
corpus.Deep also lowers the threshold at which a pattern is kept, so rare questions
reach the Answer Library. That is what you want after a product change, and it
is not what you want as a monthly habit.
Start with Standard. Choose Deep only when you changed something
fundamental, or when Kai keeps missing a question you can see in the history.
Goals are optional. They steer emphasis and phrasing.You can select a template, for example Shorter replies, Careful with
numbers, Escalate sooner, or write your own.A goal is steering, never a fact. A goal cannot add information your team
never wrote. If you write “our price is 30.000 TL” as a goal, Kai does not learn
a price from it. The Answer Library stays grounded in what your staff actually
said, and a price belongs in
Current information.Good goals describe behaviour: “End replies with a question or a clear next
step.” “Address price objections with answers the team has already given.”
A retrain rebuilds every entry from scratch, so the identifiers change. Kai
carries your decisions across by content, not by identifier. The rules are
deliberately careful.
Old state
What carries over
Edited
Your words win, whole. The recompiled text is replaced by yours, and the state stays Edited.
Approved
Carried only when the recompiled text is the same text you approved. If Kai worded it differently, the entry returns to Review.
Rejected
Carried whenever the same question appears again, whatever the new wording says. A rejection is about the topic, and re-asking a settled question helps nobody.
Anything else
Returns to Review.
An approval must never sit on text nobody approved. This is why an approved
entry whose wording changed comes back to the queue. Expect some re-review
after every retrain, and expect more of it after a Deep run.
After the run, Kai states that approvals and edits carried over wherever the
content is unchanged.
The retrain creates a draft. Your published version keeps answering customers
the whole time, during the run and after it.To take the new draft live, work the queue and select Publish. Read
Review and publish.
