“Dead” deals are out of the pipeline, and checking the CRM has become a background process

Context

Over time, the furniture company's CRM had accumulated what accumulates in any living Bitrix24 database: deals with empty required fields, customer records with no one responsible, stages overdue by weeks, statuses that don't reflect reality. Each little thing is harmless on its own. Together they do the one thing that matters: people stop trusting the data. The pipeline report says one thing, the sales reps say another, and the manager is forced to check the database by hand over and over — work that eats hours and still doesn't give the full picture, because by tomorrow the database has “drifted” again.

What was built

The “Auditor” is a Telegram bot that turns this checking into a background process. Every day, on schedule, it walks through deals and records via the Bitrix24 REST API and runs a set of checks: empty required fields, deals with no movement beyond the standard, overdue stages, incorrect and contradictory statuses, records with no one responsible. It changes nothing in the CRM — it only reads: the decision on what to do with the findings stays with people.

How it works

The key decision is personal reports. Each responsible person gets only their own problems in Telegram: a list with direct links to the specific deals, grouped by type. No need to hunt for yourself in one giant sheet — open it, go through the links, fix things. The manager gets the overall picture: who has how much outstanding and how discipline changes from week to week.

Outcome

“Dead” deals are out of the pipeline — either revived or honestly closed. CRM discipline became visible without manual checks: a problem that used to live until someone stumbled on it now lives until the morning report. Checking the database went from a recurring manual task for the manager to a background process that doesn't tire and doesn't miss anything.

Boundaries

The bot runs read-only: there is not a single CRM write method in the code. That's a deliberate boundary — a control tool must not itself touch what it controls.

Stack

What I'd do differently

• Split the report by responsible person from the start. The first version sent one shared report to everyone — only the manager read it, while the sales reps let “other people's” problems slide past. The personal breakdown — each person gets only their own deals — came in the second iteration, but it should have been there from day one

What it means in money

The “Auditor” doesn't bring in new money — it restores the reliability of the numbers you use to count it. Think of how many decisions a month are made off the pipeline: discounts, purchasing, sales reps' bonuses. If even one decision a quarter rested on broken data, the cost of that mistake is already comparable to the cost of implementation. Support costs less than one hour of the manager's time a week.

Where next

People also look at

Got Bitrix24, but can't trust the data in it?