> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/taxonomy/reasons.md).
# 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](/agent-quality-assurance/reasons.md).
## 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.
2. Define the data filter that represents it.
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.\
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](/admin-and-settings/taxonomy.md)
* [Areas](/core-concepts-and-entities/areas.md)
* [Reasons](/agent-quality-assurance/reasons.md)
* [Criteria](/agent-quality-assurance/criteria.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ask.birdie.ai/admin-and-settings/taxonomy/reasons.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.