An illustrative example: most lost deals are marked “too expensive”. Management prepares to revise the offer. A review reveals one customer needed a different deadline, another never replied and a third really discussed price. One button hid three different problems.
CRM means customer relationship management. A loss-reason field helps when the team interprets options consistently and can explain a selection using a concrete example.
Separate fact from assumption
“The customer said the deadline does not work” is a confirmed observation. “Probably too expensive” after silence is an assumption. Do not mix them in one category.
Keep an honest “reason not established” option. It reveals missing information that would otherwise disappear into convenient wording. No response does not prove a price-related refusal either.
Clarify through an appropriate conversation, rather than persistent messages merely to complete a field. Customers are not obliged to participate in an internal report.
Build a short directory
Choose distinct reasons that lead to different company decisions, such as an unsuitable deadline, an unsuitable solution scope or a changed request. These are illustrative categories to test against your own enquiries.
Give each a short definition and example. If employees repeatedly choose between almost identical options, merge them or clarify the boundary.
For a team in Kazakhstan, agree category meanings in the languages used. Different translations should not create different reasons for one event.
Incorporate recording into Bitrix24
Agree where to store the reason: in the configured closing process or a separate configured field. Record capabilities are described in the official guide. Check the specific method, settings and permissions for your edition and plan.
Do not multiply stages for every minor wording variation if the team needs an analytical directory. Keep an explanation separately when it genuinely helps interpret the situation.
Test training cases: a known reason, several factors and missing information. Employees should understand what to choose without inventing an answer to satisfy a mandatory field.
Review conclusions alongside examples
Look beyond loss counts to the contents of several enquiries. A change in recording rules can itself change the distribution of reasons; that is not yet evidence of market change.
Do not automatically blame a salesperson for an unknown reason. Discuss which information is missing and how the process can improve. Discount or product decisions need separate assessment, not just one chart.
QQDev implements Bitrix24 and trains teams. The implementation page is a place to discuss a clear directory and a review process. Begin with several anonymised lost enquiries to identify useful categories.