The most expensive mistake when deploying a CRM in Kazakhstan is assuming the project is finished on configuration day. You paid for Bitrix24, the vendor built the pipeline, connected Wazzup and telephony, and ran a demo, yet a month later half the deals are being handled in WhatsApp on personal phones, the reports are empty, and the manager is back to compiling numbers in Excel late at night. The problem is almost never the system. The problem is that the team was never trained to work in it. Below is a practical guide to getting through this stage without losing people or money.
Why Sales Reps Sabotage the CRM (and Why That's Normal)
Resistance is neither laziness nor malice; it is a rational response. The sales rep sees the CRM as a tool for controlling them rather than helping them. Here are the typical real reasons, the ones rarely said out loud:
- "It's extra work" - managing a deal in the CRM on top of the usual WhatsApp and notepad. A double workload with no visible benefit.
- "I'll get penalized based on the reports" - the fear that the data will be used against them rather than for their growth.
- "My contact base is my value" - a veteran salesperson fears that once clients are entered into the system, they will no longer be irreplaceable.
- "I already hit my targets" - a strong performer doesn't see why they should change something that works for them personally.
- "None of this makes sense" - a genuine usability problem: 40 fields in the record, of which only 5 are actually needed.
Onboarding: The First 2 Weeks Decide Everything
Habits form in the first few weeks. If during this period a sales rep manages to close even one deal "off the books," you've lost. Here is what needs to happen at the start:
- Role-based training, not a "general 2-hour webinar." Teach the sales rep how to manage a deal and call from the record; teach the sales manager how to read dashboards; teach the marketer how to view lead sources. Everyone learns only their own part.
- Practice on real tasks. Not "here are the buttons," but "enter your three current clients right now, with me watching." Hands on the system from day one.
- A short one-page cheat sheet: how to create a deal, where to log a comment, which 5 fields are mandatory. A PDF in the shared chat, not a 30-page manual.
- A designated "champion" within the team - the most engaged rep, the one people turn to with questions instead of the vendor. This removes the fear of "asking the boss something stupid."
A separate point on integrations: this is the key argument against sabotage in the Kazakhstani context. When Wazzup pulls conversations from WhatsApp, Instagram, and Telegram straight into the deal record, and calls through Asterisk are logged automatically, the rep no longer needs to "duplicate" anything; they simply work in the same place where they talk to the client. The CRM stops being an extra window and becomes the only window.
Policy: What "Working in the CRM" Means in Numbers
"Maintain the CRM conscientiously" is not a policy; it's a wish. A policy is a set of measurable rules that make any violation obvious without argument. Here is the minimum working set for a sales department:
- Every inbound contact (a call, WhatsApp message, website inquiry, or lead from 2GIS or hh.kz) becomes a lead or deal within 15 minutes. No deal in the CRM means the client does not exist.
- Every active deal always has a scheduled next activity - a call, meeting, or task. A deal with no activity equals an abandoned deal.
- A deal moves to the next stage only when the mandatory fields are filled in (amount, owner, source). This is enforced with stage-level required fields in Bitrix24, so the policy works technically rather than on the honor system.
- There must be no overdue activities at the end of the day. Either complete it, or reschedule it with a comment.
A policy you can't verify in 30 seconds from a dashboard isn't a policy; it's a statement of intent.
Formalize the policy in writing (an order or an addendum to the job description) with a signature. In Kazakhstan this matters not only for discipline but legally as well: a bonus tied to CRM usage must have a documented basis, otherwise you will lose any dispute over payment.
Incentives: Tie Money to the System, Not to Threats
A stick with no carrot produces box-ticking data entry - fields stuffed with garbage just to pass the check. What works is a three-tier combination:
- Direct benefit. Part of the bonus (for example, 10-15% of the variable component) is paid only for deals correctly processed through the CRM. If a deal is closed off the books, no commission is accrued on it. This is not a penalty; it is a condition of accounting.
- Pain relief. Show that the system saves the rep time: automated reminders instead of keeping everything in their head, templates for quotes and invoices, automated Kaspi verification - less routine, more calls.
- Recognition. A public ranking by conversion and activity (calls, meetings) drawn from Bitrix24 reports. "Top rep of the week" based on CRM data is a simple, cheap incentive that works in small teams.
Oversight Through Reports: What a Manager Should Check Every Day
Oversight works only if it is systematic and fast. Not "open every deal and read through it," but 5 minutes each morning on a dashboard. Here is the minimum set of metrics that immediately exposes sabotage:
- The number of new deals from yesterday per sales rep - a sudden zero from an active salesperson means they're working off the books.
- Deals with no scheduled activities - a direct indicator of abandoned clients.
- Overdue activities by employee - discipline in its purest form.
- Response time to a new lead - a key metric for Kazakhstan, where the client will move to a competitor in the next chat within 10 minutes.
- The pipeline by stage and the conversion between stages - where deals get stuck and lost.
Set up an automated export of these reports to Telegram or to the manager's email once a day. When the numbers arrive on their own and in front of everyone, discussing them in a standup becomes routine rather than a "crackdown." Oversight is depersonalized - the complaint is directed at the data, not at the individual.
How to Overcome Resistance: Specific Moves
- Don't roll everything out at once. Start with just the pipeline and mandatory deal management. Add automation, bots, and complex scenarios after 3-4 weeks, once the basic habit is in place.
- Remove unnecessary fields. If the record has 30 fields, keep 6 mandatory ones and hide the rest. A simpler record directly reduces resistance.
- Handle the "star" separately. Show your strong rep, the one who keeps the contact base in their head, their personal benefit: automated re-engagement of old clients, reminders about repeat sales. Their buy-in pulls the rest along.
- Review deals from the CRM, not from anecdotes. In the standup, open the record: "What's going on here?" If there's no data, that is precisely the problem, discussed in front of everyone. After 2-3 such standups, everyone starts filling things in.
- Allow a short transition period with dual record-keeping, but with a hard cutoff date. After it, the CRM only, with no exceptions even for the manager.
The Manager's Role: The Single Biggest Success Factor
No policy and no integration will save you if the leader themselves doesn't work in the system. If the director asks for a summary "verbally" or in Excel, the team instantly reads the signal: the CRM is a formality for show. Conversely, when the manager assigns tasks through Bitrix24, reviews deals personally, and makes decisions based on data from the system, using the CRM becomes the only way to "stay on the radar." This cannot be delegated to a vendor or bought with money.
The practical minimum for a manager in the first month: a daily 5-minute dashboard review, a weekly pipeline review in the standup strictly based on the records, and their own tasks only through the system. Three simple leadership habits set the culture for the whole department faster than any directive.
A Quick Checklist
- Role-based onboarding plus practice on real clients in the first 2 weeks.
- A policy stated in measurable numbers, formalized in writing with a signature.
- Integrations (Wazzup, Asterisk, 1C) so the CRM is the only window, not a second one.
- Part of the bonus tied to correct deal management.
- Daily oversight on 5 metrics, with reports arriving automatically.
- Unnecessary fields removed, everything rolled out in stages.
- The manager lives in the system themselves and runs standups based on the records.
Getting your team accustomed to the CRM is a management challenge, not a technical one. The technology can be bought and configured in a week. The habit is formed by people, policies, and the manager's personal example over the first month. Get through this stage deliberately and you'll have a system that genuinely brings in money. Skip it and you'll have an expensive electronic notepad that no one looks at.
