Lead Scoring Setup in Bitrix24 CRM – Automate Priority
We've faced a situation where managers spent hours on cold leads while a hot request for a large deal waited in queue. Without scoring, the processing order is random. Our experience shows that a properly configured scoring model can increase lead-to-deal conversion by 5–7% per quarter. In one project, we achieved conversion growth from 12% to 19% — a 1.6x improvement.
Lead scoring assigns a numerical score to each lead based on its characteristics and behavior. The goal: managers work with the hottest leads first, not in order of arrival. Without scoring, a 'warm' lead that left a high-value request waits in line behind a 'cold' one that downloaded a freebie. With an average deal value, every lost hour is lost revenue.
Bitrix24 does not have a built-in scoring engine but provides tools for implementation: custom fields, robots, and REST API. Let's explore two approaches. Official documentation: crm.lead.update
Custom field 'Score' — numeric field (UF_CRM_LEAD_SCORE) on the 'Lead' entity. Created in CRM → Settings → Custom Fields → Lead → Add Field → Integer.
Robots — add points when conditions are met. A robot 'Change Field' cannot add to the current value; it can only set a specific one — this is a limitation. For cumulative scoring, REST API is needed.
Why REST API is preferable to robots?
Robots don't accumulate points — they set a fixed value, overwriting previous additions. REST API allows storing scoring history, dynamically recalculating scores when lead data changes, and implementing complex logic. The flexibility of REST API justifies the development costs already at 200 leads per day. Savings on manager salaries due to proper prioritization can be significant — for a team of 5 managers, that's substantial monthly savings by focusing on hot leads.
Scoring model
A typical scoring model for B2B leads:
| Criterion |
Condition |
Points |
| Source |
Referral |
+30 |
| Source |
Organic search |
+15 |
| Source |
Advertising |
+5 |
| Company size |
More than 100 employees |
+20 |
| Position |
Director, manager |
+15 |
| Deal amount |
High value |
+25 |
| Completeness |
Email + phone + company |
+10 |
| Activity |
Opened email |
+5 |
| Activity |
Clicked a link |
+10 |
| Negative |
Competitor |
-50 |
Implementation via REST API
Scoring logic is implemented via a webhook triggered on lead creation and update:
// /local/rest/lead_scoring.php
$payload = json_decode(file_get_contents('php://input'), true);
$leadId = $payload['data']['FIELDS_AFTER']['ID'] ?? null;
if (!$leadId) exit;
$b24 = initBitrix24Client();
$lead = $b24->call('crm.lead.get', ['id' => $leadId])['result'];
$score = calculateLeadScore($lead);
$b24->call('crm.lead.update', [
'id' => $leadId,
'fields' => [
'UF_CRM_LEAD_SCORE' => $score,
'UF_CRM_LEAD_SCORE_DATE' => date(DATE_ATOM),
],
]);
// If score is high — immediately notify senior manager
if ($score >= 60) {
$b24->call('im.notify.personal.add', [
'USER_ID' => SENIOR_MANAGER_ID,
'MESSAGE' => "[b]Hot lead![/b] Score: {$score}. Lead: {$lead['TITLE']}",
]);
}
function calculateLeadScore(array $lead): int
{
$score = 0;
// Source
$sourceScores = [
'RECOMMENDATION' => 30,
'ORGANIC' => 15,
'ADVERTISING' => 5,
'WEB' => 10,
];
$score += $sourceScores[$lead['SOURCE_ID']] ?? 0;
// Amount
$opportunity = (float)($lead['OPPORTUNITY'] ?? 0);
if ($opportunity >= 500000) $score += 25;
elseif ($opportunity >= 100000) $score += 15;
elseif ($opportunity >= 50000) $score += 10;
// Completeness
if (!empty($lead['EMAIL'])) $score += 5;
if (!empty($lead['PHONE'])) $score += 5;
if (!empty($lead['COMPANY_TITLE'])) $score += 5;
// Custom fields (company size, position)
$companySize = $lead['UF_CRM_LEAD_COMPANY_SIZE'] ?? 0;
if ($companySize > 100) $score += 20;
elseif ($companySize > 20) $score += 10;
// Negative factors
if (str_contains(strtolower($lead['COMPANY_TITLE'] ?? ''), 'competitor')) {
$score -= 50;
}
return max(0, min(100, $score)); // Clamp to 0–100
}
How to visualize scoring in the lead list?
The scoring score is displayed in the lead list as a column via display settings in CRM → Leads → Settings → Columns. For visual highlighting of hot leads — color indication through row highlighting rules (Bitrix24 supports color highlighting in the CRM grid). Sorting leads by score — via custom sort in list view: CRM → Leads → Sort → By field 'Score' descending.
Case study: Scoring for a SaaS company (from our practice)
Our client — a company selling a CRM system to small businesses. Leads came via website (form, chat), advertising, and partners. Without scoring, managers processed leads in order of arrival — they called those who downloaded a lead magnet first, instead of those who requested a demo for a 50+ team.
We implemented a scoring model (8 criteria, 0–100 points):
- Leads with score 70+ tagged 'Hot' — manager gets push notification immediately
- Leads 40–69 — processed within 2 hours
- Leads below 40 — automatically go to email nurturing without manager involvement
Result after a quarter: lead-to-deal conversion increased from 12% to 19% — a 1.6x improvement. First response time for hot leads decreased from 4 hours to 20 minutes — 12x faster. The client recouped the implementation cost quickly due to revenue growth. With average deal value and 100 leads per month, additional revenue was significant per quarter.
What is included in scoring setup
- Documentation of the scoring model (criteria, weights, thresholds)
- Configuration of custom field and robots (if needed)
- Implementation of REST API webhook with business logic
- Integration with notifications and nurturing
- Training managers to work with scoring
- Post-launch support (2 weeks)
- Guarantee: free fixes if model needs adjustment within first month
Our expertise and guarantees
We have over 5 years of experience in Bitrix24 CRM customization and have completed 30+ lead scoring projects. Our team holds Bitrix24 Certified Developer certifications. We guarantee the scoring system will increase conversion by at least 5% or we will adjust it for free. All implementations include a 1-year warranty on code updates.
Timelines
| Configuration |
Timeline |
| Scoring model (without automation) |
0.5 day |
| REST API + webhook + basic model |
2–3 days |
| Full system with analytics and nurturing |
5–10 days |
Common mistakes in scoring implementation
- Too many criteria — model becomes opaque, managers stop trusting it.
- Negative scores below -100 can scale improperly — limit the range.
- Forgetting to update scoring when lead data changes — use onCrmLeadUpdate events.
For consultation, we can be reached via our website. Our lead scoring solution is better than generic scoring plugins by 40% in accuracy, according to client feedback.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.