> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aide.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Topic confidence, near misses and what teaches Aide a topic

> Aide scores every customer message against your topics and tags it only when it is sure enough.

Aide scores every customer message against your topics and tags it only when it is sure enough. This article explains the score, what to do with a message that fell just short, and which of your answers Aide learns from. Topics are under **Topics** in the sidebar; for creating and organising them, see [Topics and how Aide tags conversations](https://docs.aide.app/automation/topics.md).

## How Aide decides

When Aide tags a message, it reads each topic's **When to use this topic** and the topic's examples, and gives each topic a score. A topic is tagged when it scores at least the topic's **Threshold**, 80% by default. The threshold is shown in the topic's settings and can't be changed yet.

The chip on a customer message tells you what happened:

| Chip | Meaning |
| - | - |
| A solid topic chip | The topic was tagged. Open it to see how sure Aide was, and mark it **Right topic** or **Wrong topic**. |
| A greyed, dashed chip such as **Sales 45% · under 80%** | A near miss: the best topic scored under its threshold, so the message got no topic. |
| A dashed **Suggested** chip | None of your topics fits. Aide proposes a new one. |

## Review near misses

1. Open **Topics** and select a topic. **Near misses** lists the messages from the last 30 days that came closest to it without reaching the threshold, newest first.
2. Each row shows the score and the threshold, the message, and how long ago it arrived. Select the time to open the conversation.
3. Choose **It's** followed by the topic's name if the message belongs to the topic, or **Not** followed by its name if it doesn't. Either way the message leaves the list.
4. Choose **Load more near misses** for older ones.

You can do the same from a conversation: open the dashed chip, read Aide's reason, and choose one of the two buttons. A message that later gets a topic no longer shows a near miss.

## What teaches Aide

* **It's** adds the message to the topic as a positive example. **Not** adds it as a negative example.
* When Aide tags new messages, it reads only a topic's positive examples that don't need review, the five newest of them. Confirming a near miss puts that message among them.
* A negative example records your decision and takes the message off the list. It isn't read when Aide tags new messages. To stop a topic catching the wrong messages, say what it is not for in **When to use this topic**.
* An example Aide has flagged for review isn't read while it is flagged.

## A topic with no examples

When a topic has no positive examples yet, its page says that Aide hasn't seen an example of the topic. That is often why messages fall short of the threshold. Confirm a near miss, or add 3 to 5 real customer messages as examples.

## When no topic fits

A message none of your topics fits gets a **Suggested** chip instead of a near miss. Open it to see the proposed name, description and group and how many messages it was seen in, then choose **Add topic** or **Dismiss**. Aide also adds suggestions that keep coming up (see [Topics Aide adds on its own](https://docs.aide.app/automation/topics-added-automatically.md)).

## Confidence in procedures

A procedure can require a minimum score with a **topic confidence** condition, from 80% to 97.5% (see [Choose when a procedure runs](https://docs.aide.app/automation/procedure-when-to-use.md)).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.