The three real reasons
- It gives the rep nothing. They spend time and receive supervision. Until the CRM makes their own work easier, it stays somebody else's tool.
- Too many fields. Twenty fields get filled in approximately never. Five required ones get filled in.
- Nobody checks. A rule nobody verifies quietly stops being followed, and you find out from the reports.
What to do before setup
- Write down the reports you will look at every week. Not «analytics», specific numbers.
- For each report, write down the fields without which it cannot be built.
- Anything that did not make that list does not go into the CRM.
- Check which of those fields can be captured automatically: call time, source, payment amount.
What to give the rep in return
- a stalled-conversation list the system compiles, not the rep
- a reminder about the customer who never picked up
- an invoice and delivery note by order number, without assembling them by hand
- the customer's history in one window instead of scattered across chats
Every one of those saves the rep time. After them, filling in fields stops being a one-way obligation: they put something in and get something out.
How to check without turning it into surveillance
- Once a week, pull ten closed records.
- Reconcile them against the conversations: does the stated close reason match what actually happened.
- More than two mismatches out of ten is a question about the process, not about the person.
- Make data quality one modest line in the bonus, not the whole of it.
Signs the rollout failed
- reps keep a private spreadsheet on the side
- records get created retroactively at the end of the day
- half the deals have an empty close reason
- revenue in the CRM and revenue in the bank differ by more than a tenth