> 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.md). # 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

Type	Description	Page
Areas	Manage broad themes used to organize feedback.	/pages/ixCBYIeVZhWEhX2544X8
Opportunities	Manage specific issues and improvement opportunities.	/pages/90ExVjWAMbaj4rli6hjr
Segments	Manage audience and behavior-based groupings.	/pages/a71rzcRLRRHKzZKv5KDb
Reasons	Manage contact motives and QA service categories.	/pages/SyDOubzYWgBG0DZSLrg5
Criteria	Manage QA rules used to evaluate service quality.	/pages/ZIFvGHYICnblww3lgEic

## 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](/core-concepts-and-entities/areas.md) * [Opportunities (Opps)](/voice-of-customer/opportunities.md) * [Segments](/core-concepts-and-entities/segments.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: ``` GET https://ask.birdie.ai/admin-and-settings/taxonomy.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.