> 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/opportunities.md).
# Opportunities
## Overview
The **Opportunities** taxonomy page is where you manage all Opportunity records in Birdie Settings.
Opportunities are one of the core taxonomy types in Birdie. They represent specific insights, issues, or improvement possibilities identified from feedback.
This page centralizes the operational work of managing Opportunities as taxonomy items. Use it to review your catalog, create new Opportunities, and organize them into collections.
If you want the conceptual definition of an Opportunity and how it behaves in analysis pages, see [Opportunities (Opps)](/customer-intelligence/opportunities.md).\
## Viewing & Searching
The main tab shows the full Opportunity catalog as a list.
Each row includes:
* **Taxonomy ID**, such as `[OP-164]`
* **Opportunity name**, such as `Late fee charges due to payment errors in app`
Use this view to review your Opportunity structure and avoid duplicate entries.
## Creating New Data
Click **New opp** to create a new Opportunity.
When creating a new Opportunity:
1. Define a clear title.
2. Apply filters if needed (optional step)
3. Select related areas
4. Write a description that will guide calibration step.
5. Calibrate this Opportunity
6. Save the record to add it to the catalog.
Use names that describe the customer problem or business opportunity directly.
## Collections Tab
The second tab groups Opportunities by **Opportunity collection**.\
This view helps teams keep related Opportunities together and makes the taxonomy easier to navigate.
Use collections when you need to organize Opportunities by:
* product area
* journey stage
* team ownership
* strategic theme
For conceptual guidance, see [Understanding and Creating Opportunities in Birdie](/core-concepts-and-entities/understanding-and-creating-opportunities-in-birdie.md) and [Collections](/core-concepts-and-entities/collections.md).
## Best Practices
* Use one Opportunity per distinct issue.
* Avoid combining multiple problems in one name.
* Keep naming patterns consistent across teams.
* Group Opportunities into collections that reflect how work is prioritized.
## Related Articles
* [Taxonomy](/admin-and-settings/taxonomy.md)
* [Opportunities (Opps)](/customer-intelligence/opportunities.md)
* [Understanding and Creating Opportunities in Birdie](/core-concepts-and-entities/understanding-and-creating-opportunities-in-birdie.md)
* [Collections](/core-concepts-and-entities/collections.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://ask.birdie.ai/admin-and-settings/taxonomy/opportunities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
