> For the complete documentation index, see [llms.txt](https://docs.meetalto.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meetalto.ai/using-meet-alto/knowledge/improve-answers.md).

# Improve your AI's answers

Diagnose weak replies, resolve missing knowledge, and measure whether your correction helped.

Use **AI Feedback** in the sidebar and your test conversations to find repeatable problems. Keep one example of the question, the weak response, and what a helpful answer should have done.

**AI Feedback** has three tabs:

| Tab                       | What you find there                                                       |
| ------------------------- | ------------------------------------------------------------------------- |
| **Conversation Feedback** | Feedback your team left on AI replies                                     |
| **Knowledge Gaps**        | Questions your AI couldn't answer, and sources that contradict each other |
| **Guidelines**            | The reply guidelines Alto builds from your team's feedback                |

## Fix the right layer

| Problem                           | Change                                                |
| --------------------------------- | ----------------------------------------------------- |
| Wrong or missing fact             | Correct the owning knowledge source                   |
| Outdated policy                   | Replace the old information and remove contradictions |
| Wrong tone or unnecessary length  | Improve Brand Guidelines or voice examples            |
| Wrong next step in a conversation | Edit the agent's playbook                             |
| A customer needed a person        | Clarify the handoff and review workflow               |

## Fill a knowledge gap

A content gap is a question your AI had no information for.

1. Open **AI Feedback** and choose the **Knowledge Gaps** tab. The number beside it counts open gaps.
2. Choose **Content gaps**, and keep **Open** selected.
3. Read the question. To see where it came from, expand **Came up in … conversations** and choose **Open** next to a message.
4. Choose **Add to Knowledge Base**.
5. Check the **Question** and write the **Answer**. If the answer starts as an **AI draft**, check every fact before you keep it. Replace placeholders such as "\[discount amount]"; the answer can't be saved while they remain.
6. Choose **Add & mark resolved**.

The answer is saved to your Knowledge Sources as a text entry whose title starts with "FAQ:", and the gap moves to **Resolved**. The new entry must finish processing before the AI can use it; follow the [knowledge status checks](/using-meet-alto/knowledge.md) if it doesn't.

A gap suggestion is evidence of a question, not proof of the correct answer. Ask the business owner when a policy or exception is uncertain.

If a gap doesn't need an answer, open its menu and choose **Mark as done** or **Dismiss**. Choose **Reopen** to bring it back.

## Resolve a conflict

A conflict means two of your sources disagree. Adding a third answer doesn't remove the contradiction, so fix or delete the wrong source instead.

1. In **Knowledge Gaps**, choose **Conflicts**.
2. Read the excerpts from each source and **Why this looks contradictory**.
3. Choose **Review sources in Knowledge Base**. This opens **Settings → AI Training → Knowledge Sources**.
4. Fix the source that is wrong:
   * A website: update the page on your site, then refresh the website in Knowledge Sources. See [Add a website](/using-meet-alto/knowledge/websites.md).
   * An uploaded document: replace or delete it. See [Add files](/using-meet-alto/knowledge/files.md).
   * A text answer: edit or delete it. See [Add a text answer](/using-meet-alto/knowledge/add-knowledge.md).

Once you fix or delete the wrong source, the conflict closes by itself.

## Give actionable feedback

1. In the **Inbox**, open the comment or conversation with the AI reply or draft.
2. Select the feedback button on the reply (its tooltip says **Add Feedback**).
3. For a reply that was sent, describe the change in **Your Feedback** and choose **Submit Feedback**. For a draft waiting for review, type in the **Give feedback on this response...** box under it and select the arrow.

Prefer a correction such as "Ask which product they own before describing compatibility" over "Be better." Keep comment feedback and direct-message feedback in the right context; public replies and private conversations have different goals.

Your feedback appears under **Conversation Feedback** with a status:

* **Queued for processing**: Meet Alto will process the feedback automatically before it changes future replies.
* **Added to guidelines**: the feedback was included in the guideline version shown.
* **Not reusable**: the feedback wasn't suitable as a reusable guideline for future replies.
* **Moved to Knowledge Gaps**: the feedback identified missing knowledge to review in the Knowledge Gaps tab.

To see what applies, open **Guidelines** and choose the **Account** and **Reply scope** (**Comments** or **DMs**). **Active guidelines** apply to replies for that account and scope. An empty version means there are no learned guidelines in that version; it doesn't necessarily mean feedback was deleted.

If previously processed feedback is edited or removed, **Updating guidelines** explains that learned guidance is temporarily paused while Meet Alto rebuilds it. Brand and Knowledge settings still apply. New feedback waiting to be processed does not by itself pause existing guidelines. Choose **Refresh** to check the latest state, or **Retry** if the page couldn't load.

## Check that it worked

After a correction, repeat the original question and a nearby variation. Check that the answer improved without creating a new promise elsewhere. Keep a small set of questions to retest whenever you make substantial changes.

Make this part of your [weekly review](/using-meet-alto/playbooks/weekly-review.md). For a source that is still processing, follow the [knowledge status checks](/using-meet-alto/knowledge.md) first.