# CRM - Customizing the Reason for Winning or Losing an Opportunity In **CRM**, the **Customization of the Opportunity Win or Loss Reason** allows you to record why a deal was **won** or **lost**, helping with sales funnel analysis and improving the sales strategy. 📊 ### ⚙️ What is the Win or Loss Reason Are **customized options** that the user selects when **winning or losing an opportunity** in the CRM. These reasons help answer questions such as: * Why are we losing sales? * Which factors contribute most to closing deals? * Is there a pattern in customer objections? *** ### 🛠️ How to Customize the Reasons Follow the step-by-step guide: 1️⃣ Access **System Settings** ⚙️\ 2️⃣ Go to **CRM**\ 3️⃣ Click on **Win/Loss Reasons**\ 4️⃣ Add or edit the reasons as needed\ 5️⃣ Save the changes After that, the reasons will be available for selection when **marking an opportunity as won or lost**. {% embed url="" %} *** ### 📝 Examples of Win Reasons * Competitive pricing * Customer's urgent need * Best solution presented * Customer referral * Quick service ### ❌ Examples of Loss Reasons * High price * Customer chose a competitor * No budget at the moment * Lack of customer response * Decision postponed *** ### 💡 Best Practices ✔ Use **clear and objective reasons**\ ✔ Avoid too many options so as not to confuse the team\ ✔ Review the reasons periodically to improve the analyses\ ✔ Use the data to adjust **sales arguments and positioning** *** --- # Agent Instructions: 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://docs.sprinthub.com/en/topics/general/crm/crm-initial-settings/crm-customizing-the-reason-for-opportunity-win-or-loss.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.