# How to retrain the AI after Knowledge Base updates (/docs/portal/knowledge-base/retrain-the-ai)





Saving Knowledge Base edits stores your changes, but the AI only picks them up after you
**Train AI**. This is a deliberate two-step process so you can stage multiple edits and push
them all at once.

Train the AI [#train-the-ai]

<img alt="The Knowledge Base header, with Save, Train AI and Cancel" src="__img0" />

<Steps>
  <Step>
    Open 

    **Knowledge Base**

     and confirm the correct dealership is selected.
  </Step>

  <Step>
    Make and 

    **Save**

     all the changes you want to publish.
  </Step>

  <Step>
    Click 

    **Train AI**

     in the header.
  </Step>

  <Step>
    Wait for the toolbar's progress bar to finish — typically a few seconds.
  </Step>
</Steps>

A green message, *Successfully re-trained vector database on Knowledge Base*, confirms it worked.
A red one means it didn't; try again, and contact support if it keeps failing.

Once training finishes, the next conversation the AI handles will draw on the updated content.

Reading the training state [#reading-the-training-state]

The line under the page title counts entries and how many of them are trained —
*2 knowledge bases, 0/2 trained*. Anything short of the full count means there are saved edits the
AI hasn't been given yet.

**Train AI** greys out once every entry is trained, so a disabled button means there's nothing to
push. It also means the button tells you nothing about *unsaved* edits — those aren't part of the
count at all.

<Callout type="warn">
  Training sends what is **saved**, not what is on screen. Save before you train, or you'll train
  the previous version and the counter will read as though you're up to date.
</Callout>

When you need to retrain [#when-you-need-to-retrain]

Retrain after adding, editing, reordering, or removing a Knowledge Base entry.

You **don't** need to retrain after changing:

* Settings (hours, address, channels)
* Inventory (vehicles refresh automatically from your feed)
* Promotions (they have their own Train AI button under Promotions)

Confirm the new knowledge is live [#confirm-the-new-knowledge-is-live]

After training, [test the AI's knowledge](/docs/portal/knowledge-base/test-ai-knowledge) by
opening [Preview](/docs/portal/preview) and asking a question that should use the new content.

<Callout type="info">
  If the answer is still the old one, reload Preview — the widget reads the configuration when it
  loads. If it's still stale after that, check the counter on the Knowledge Base page: if it reads
  less than the full number trained, the save or the training didn't go through.
</Callout>

A good rhythm [#a-good-rhythm]

* **Daily edits**: Save as you go, then Train AI once at the end of the editing session.
* **Major rewrites**: Save in stages, but only Train AI after the full rewrite is reviewed.
* **Avoid** training many times in quick succession — batch your edits instead.
