# Taxonomy

## Overview

Taxonomy is one of the core foundations of Birdie.

It is how each client structures their own classification system inside the platform.

The **Taxonomy** section in Settings centralizes everything related to creating, organizing, and managing taxonomy records.

Use this section to:

* manage the full taxonomy catalog
* create new taxonomy items
* keep naming organized
* group records into collections

Birdie supports five taxonomy types:

* Areas
* Opportunities
* Segments
* Reasons
* Criteria

## How the Taxonomy Section Works

Each taxonomy type has its own subpage.

On each subpage, the main tab shows a list of taxonomy records.

Each row includes:

* **Taxonomy ID**, such as `[OP-164]`
* **Taxonomy name**, such as `Late fee charges due to payment errors in app`

Each page also includes a button to create a new item for that taxonomy type, such as **New opp** or the equivalent action.

## Collections Tab

Most taxonomy subpages also include a second tab for **Collections**.

This tab groups taxonomy items by their respective collection, such as Opportunity collections, Segment collections, or Criteria collections.

Use the Collections tab to:

* keep related taxonomy together
* mirror your team, product, or workflow structure
* reduce duplication
* make navigation easier

### Exception: Reasons

**Reasons** do not use collections.

Reasons are grouped inside **Areas**, because they belong to the QA hierarchy rather than an independent collection structure.

## Taxonomy Types

<table data-view="cards"><thead><tr><th>Type</th><th>Description</th><th data-card-target data-type="content-ref">Page</th></tr></thead><tbody><tr><td>Areas</td><td>Manage broad themes used to organize feedback.</td><td><a href="taxonomy/areas">areas</a></td></tr><tr><td>Opportunities</td><td>Manage specific issues and improvement opportunities.</td><td><a href="taxonomy/reasons">reasons</a></td></tr><tr><td>Segments</td><td>Manage audience and behavior-based groupings.</td><td><a href="taxonomy/segments">segments</a></td></tr><tr><td>Reasons</td><td>Manage contact motives and QA service categories.</td><td><a href="taxonomy/opportunities">opportunities</a></td></tr><tr><td>Criteria</td><td>Manage QA rules used to evaluate service quality.</td><td><a href="taxonomy/criteria">criteria</a></td></tr></tbody></table>

## Best Practices

* Define naming conventions before scaling the taxonomy.
* Reuse existing items when possible.
* Use collections to reflect how your business is organized.
* Review the catalog regularly to avoid duplicates and outdated entries.

## Related Articles

* [Areas](https://ask.birdie.ai/core-concepts-and-entities/areas)
* [Opportunities (Opps)](https://ask.birdie.ai/voice-of-customer/opportunities)
* [Segments](https://ask.birdie.ai/core-concepts-and-entities/segments)
* [Reasons](https://ask.birdie.ai/agent-quality-assurance/reasons)
* [Criteria](https://ask.birdie.ai/agent-quality-assurance/criteria)