> For the complete documentation index, see [llms.txt](https://docs.getgymini.com/gymini/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getgymini.com/gymini/features/features-overview/pipelines-and-opportunities/utilizing-opportunity-status-buckets.md).

# Utilizing Opportunity Status Buckets

### Overview

In Gymini, the opportunity status buckets — "Won," "Lost," and "Abandoned" — play a pivotal role in managing and tracking the progress of leads in your sales pipeline. This guide will help you understand how to effectively use these buckets to maintain a clean and efficient pipeline.

**Understanding the Opportunity Status Buckets**

When you are in the opportunities view, moving an opportunity tile will reveal three buckets: "Won," "Lost," and "Abandoned." These represent the different statuses an opportunity can have:

* **Open**: The default status when an opportunity is created.
* **Won**: Indicates a successful closure of a lead.
* **Lost**: Used less frequently, generally for leads who request no further contact.
* **Abandoned**: For leads that stop responding over time.

**Utilizing the Buckets for Closing Leads**

1. **Training Clients**: Educate your clients to drag opportunities into the "Won" bucket as they secure them.
2. **Creating Triggers**: Set up triggers to automatically mark opportunities as "Won" when they move to the final stage in your pipeline.

**Keeping the Pipeline Visually Clean**

1. **Changing the Status**: Altering the status of an opportunity removes it visually from the pipeline, helping to avoid clutter from inactive leads.
2. **View Adjustments**: Adjust the view settings to "All" to see all opportunities, including those marked as "Abandoned."

**Implementing a Strategic Approach with Campaigns**

1. **Initial Nurture Campaign**: Develop a campaign to nurture new leads with various communication methods, aiming to secure a booking.
2. **Not Yet Ready Campaign**: Create a placeholder campaign to hold leads not yet ready to convert, facilitating a smooth transition to a long-term nurture strategy.
3. **Long-term Nurture Campaign**: Establish a campaign for long-term nurturing, sending periodic emails to maintain engagement with the leads.

**Setting Up Triggers for Automated Management**

1. **Trigger Creation**: Develop triggers to automate the management of leads flowing through different campaigns.
2. **Utilizing the "Not Yet Ready" Campaign**: Use this campaign as a wait step to initiate triggers, helping to manage leads more effectively.
3. **Automating Status Changes**: Set up triggers to automatically change the opportunity status to "Abandoned," removing them visually from the pipeline and adding them to the long-term nurture campaign.

**Conclusion**

Understanding and utilizing the opportunity status buckets in Gymini CRM allows for a more organized and efficient management of your sales pipeline. By setting up strategic campaigns and triggers, you can automate the lead management process, ensuring a clean pipeline and a systematic nurturing strategy.

Remember to explore different trigger configurations to make the most out of the opportunity status buckets in Gymini CRM.


---

# 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://docs.getgymini.com/gymini/features/features-overview/pipelines-and-opportunities/utilizing-opportunity-status-buckets.md?ask=<question>&goal=<endgoal>
```

`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.