# Reasons

## Overview

The **Reasons** taxonomy page is where you manage all Reason records in Birdie Settings.

Reasons are one of the core taxonomy types in Birdie. They represent the main contact motives or service categories used to structure quality analysis.

This page centralizes the operational work of managing Reasons as taxonomy items. Use it to review your catalog and create new Reasons.

Reasons are grouped inside **Areas**.

If you want the conceptual definition of a Reason and how it behaves in QA workflows, see [Reasons](https://ask.birdie.ai/agent-quality-assurance/reasons).<br>

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FCPokqIUqX09t8tWTmood%2Fimage.png?alt=media&#x26;token=e2a67f65-6bc7-4cdd-a98c-74d0871249d8" alt="" width="563"><figcaption></figcaption></figure>

## Viewing & Searching

The main tab shows the full Reason catalog as a list.

Each row includes:

* **Taxonomy ID**, such as `[RS-021]`
* **Reason name**, such as `Billing support`

Use this view to review the list of contact reasons already configured.

## Creating New Data

Click **New reason** to create a new Reason.

When creating a new Reason:

1. Define the contact motive or service flow.<br>

   <figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FeKeZnFXq3NKYdauF6SqR%2Fimage.png?alt=media&#x26;token=2f0a6418-f4e7-4d8c-b555-32dd9097911c" alt="" width="375"><figcaption></figcaption></figure>
2. Define the data filter that represents it.<br>

   <figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FKEHXfEqyKUTSvItVJ5SQ%2Fimage.png?alt=media&#x26;token=a55ad1df-0862-4d82-bc37-fa187e9d65e1" alt="" width="375"><figcaption></figcaption></figure>
3. Save it to add it to the catalog.

Use names that match how your operation classifies service demand.

## Organization Inside Areas

Reasons are grouped by **Area**, not by collection.\ <br>

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FyLcK74Pv2TzeDHK1EbEq%2Fimage.png?alt=media&#x26;token=b12d7269-bafc-4a5f-9883-615bb18097cb" alt="" width="563"><figcaption></figcaption></figure>

This structure keeps each Reason tied to the correct operational context.

Use this structure when you need to:

* separate contact motives by Area
* keep the taxonomy aligned with QA workflows
* maintain a clear hierarchy between Areas and Reasons

## Best Practices

* Use one Reason per service motive.
* Avoid duplicate labels for the same flow.
* Keep naming aligned with internal operations.
* Keep each Reason under the correct Area.

## Related Articles

* [Taxonomy](https://ask.birdie.ai/admin-and-settings/taxonomy)
* [Areas](https://ask.birdie.ai/core-concepts-and-entities/areas)
* [Reasons](https://ask.birdie.ai/agent-quality-assurance/reasons)
* [Criteria](https://ask.birdie.ai/agent-quality-assurance/criteria)
