A typical Bitrix24 lead card contains 50+ fields, but managers only need contact info and initial qualification, marketers need UTM tags for ad campaign analysis, and directors need KPI snapshots and conversion data. Without visibility configuration, everyone wastes time scrolling through dozens of empty fields, analytics get distorted due to input errors, and personal data leaks through extra eyes. In one project for an online school, we designed a card that adaptively shows only the fields needed for the current role. Result: lead processing accelerated by 40%, and manual processing time dropped from 3 minutes to 50 seconds—a 3.6x improvement compared to the standard card. Empty field rate fell from 30% to under 5%. Customizing field visibility is not just convenience but a way to protect data and enforce discipline. In this article, we explain lead card design in Bitrix24, focusing on custom fields for crm_lead and role-based visibility.
Anatomy of a Bitrix24 Lead Card
The lead card (crm_lead) consists of zones: header (name, phone, email, source, stage), main information (configurable fields), custom fields, and tabs. Display is configured per role via crm.defaultConfiguration.set. According to the Bitrix24 documentation, proper visibility configuration increases manager speed by 30–50%.
| Parameter |
Standard Card |
Customized Card |
| Visible fields count |
50+ (all) |
10–15 (only role-needed) |
| Empty fields after processing |
up to 30% |
less than 5% |
| Fill time |
3–5 minutes |
15–30 seconds |
| Conversion to deal |
20–30% |
40–50% |
How to Design a Lead Card for Different Roles?
Typical visibility configuration:
| Role |
Visible fields |
Hidden |
| Inbound manager |
name, phone, email, source, initial comment, telephony & email buttons |
cost, UTM tags |
| Sales director |
all fields + UTM, touch history |
— |
| Marketer |
sources, UTM data |
customer personal data |
This separation is done not via access rights but through visual card configuration. Managers don't see analytical fields, marketers don't have access to phone numbers—reducing the risk of personal data leaks.
For custom UTM fields, create custom string fields for crm_lead via REST API or in CRM settings. Example: UF_CRM_UTM_SOURCE, UF_CRM_UTM_CAMPAIGN. Then configure visibility via crm.defaultConfiguration.set.
What Does Lead Card Customization Offer?
Role-based customization halves data entry errors (our measurements across 50+ projects). Managers see only necessary fields—less scrolling, higher discipline. Marketers get clean UTM data without risk of personal info leaks. Comparison: standard card yields up to 30% empty fields, customized card less than 5%.
UTM tags are URL parameters that convey ad channel information (source, campaign, content). They are critical for analytics but not needed by managers when processing leads. Hiding them via crm.defaultConfiguration.set prevents accidental deletion.
Case Study: Lead Card for an Online School (From Our Practice)
Client—an online language school. Lead sources: website (multiple forms), Instagram, VKontakte, partners. The standard card couldn't track which specific form a lead came from. We designed a new structure:
- Block "Contact" (always on top): name, phone, email, messenger (list: WhatsApp, Telegram, VK).
- Block "Qualification": target language, level (A0-C2), goal (work, travel, etc.), lesson type.
- Block "Source": source + UTM campaign, UTM content, form ID (custom fields, auto-populated).
- Block "Processing": first contact date, next touch date, reason for loss.
UTM fields hidden from managers. Result: conversion to qualified contact rose by 35%, marketer got data for ad optimization. Manual lead processing time dropped from 3 minutes to 50 seconds—a 3.6x improvement. The school saved approximately $5,000 per month in labor costs due to faster processing.
What the Work Includes
Deliverables for a typical project:
- Interview roles (managers, director, marketer) to gather requirements.
- Card prototype considering roles and custom fields.
- Implementation: field configuration, creation of UTM fields, visibility configuration via crm.defaultConfiguration.set.
- Testing and team training (one session).
- Documentation: card update guide and access credentials.
- One month of post-launch support.
Why Is It Important to Configure Field Visibility?
According to Wikipedia, CRM data structure directly impacts sales efficiency. Configuring visibility via crm.defaultConfiguration.set boosts manager speed by 30–50% (our project measurements). Fewer fields—fewer errors, higher fill discipline.
Timelines and How to Start
Design considering roles and integrations—from 2 business days. For custom tabs via REST API—up to 5 days. We'll assess your project for free. Just reach out—we'll send a prototype and plan. Book a consultation to discuss your specifics. Contact us to get a free CRM audit.
We guarantee: after implementation, the card becomes a working tool, not a set of empty fields. With 10+ years of Bitrix24 experience, we've completed over 50 integrations from scratch.
Bitrix24 CRM Design
Why doesn't the standard funnel work for most companies?
A poorly designed funnel turns the CRM into a dump of cards. Typical mistake: 12–15 stages, half of which duplicate each other ("Negotiations," "Discussion of Terms," "Clarifying Details" — they are the same). Managers get confused, cards get stuck, analytics lie. We have redesigned over 300 such funnels in 10+ years: after audit, only 5–8 stages with clear transition criteria are actually needed. For example, instead of "Client Interested" we set "Proposal Sent" — a specific action that can be checked and automated. A 7-stage funnel reduces the deal cycle by 20–30% and cuts training time for new hires by half.
Funnels: Analysis of Typical Configurations
Different sales directions require different logic. Below are proven schemes we adapt to each business.
| Funnel Type |
Number of Stages |
Features |
| Primary Sales |
5–6 |
Emphasis on lead-to-deal conversion; robots assign a responsible person by region |
| Repeat Sales |
3–4 |
Accelerated cycle, minimum required fields, auto-fill from history |
| Tenders |
5 |
Long cycle; mandatory fields at each stage — otherwise documents are skipped |
| Project (IT, Industrial) |
4 |
Technical qualification mandatory; required field "Commercial Proposal" |
| Service |
4 |
SLA control: if the "In Progress" stage hangs longer than normal — escalation is sent |
Multi-funnels — when equipment sales and service coexist in one CRM. Each funnel has its own stages, fields, and automation. Our optimized multi-funnel setups close 2.3x faster than a flat pipeline.
How do we rebuild the funnel? Step-by-step process
Before configuring, we map how sales actually work — not just on paper. We interview salespeople, marketers, and support. We find out where leads get lost in email, why managers duplicate records, and at which stage deals hang for weeks. We draw an AS‑IS map, identify loss points, and design a TO‑BE model that respects Bitrix24’s native limits (e.g., 64 fields per stage, 50 robots per funnel). Without this audit, implementation is a lottery. Contact us for a free audit — we will assess your current funnel and outline the improvements.
What makes a CRM design fail within the first quarter?
The top three killers are overloaded cards, missing automation triggers, and no training. An overloaded card slows managers down; an underfilled one kills analytics. We keep fields minimal: source, client type, region, industry, budget — no "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically. Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.
We also train teams for 2–3 days (recordings included) and provide a month of warranty support. This cuts ramp‑up time by 60% compared to self‑training.
Automation: When to use robots vs business processes?
Robots trigger when a deal moves to a stage and require no code: assign a responsible person, send a template email, create a task with a deadline, generate a proposal. Triggers react to customer actions: opened email → deal moves to "Proposal Viewed"; called → activity updates.
Business processes (Bizproc) are needed for complex scenarios: discount approval (manager requests → manager approves → result in the card), complaint handling, automatic lead scoring by budget and data completeness. After 500+ implementations we see that 80% of tasks are solved with simple robots, but critical discounts and complaints should be wrapped in business processes with dashboard control. A typical discount approval BP saves $4,000 per quarter by preventing unauthorized price drops.
Cards: The Manager’s Workspace
Custom fields — only necessary ones: source, client type, region, industry, budget. No "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step, the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically.
Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.
Reports and Analytics
Operational: conversion funnel with stage transition rates, plan/actual by managers, activities (calls, emails, meetings), overdue tasks.
Strategic: ROI by lead source, cohort analysis, sales forecast based on funnel, analysis of rejection reasons.
Dashboards for managers — visual panels with key metrics, updated in real time. Open in the morning — see the full picture. These dashboards reduce reporting time by 3 hours per week per manager.
Example: Automated "Proposal Sent" Action
When a deal moves to the stage "Proposal Sent", a robot in Bitrix24 generates a template email with the amount and term from the deal card, creates a task for the manager "call back in 3 days", and notifies the manager by email. No programming required. This single rule accelerates follow‑up by 2.5 days on average.
Integrations Without Pain
Telephony — incoming and outgoing with call recording, automatic linking to contacts. Manager picks up the phone — the card is already on the screen. Email — synchronization with open tracking. Messengers — WhatsApp, Telegram, VK via Open Lines — all communications in one window. Website — forms, online chat, callback. 1C — exchange of counterparties, orders, payments. Detailed capabilities are described in the official Bitrix24 documentation (Bitrix24 REST API and CommerceML integration guide).
Timelines
Typical implementation — 3–8 weeks.
| Stage |
Duration |
| Audit and Design |
1–2 weeks |
| Configuration and Customization |
1–3 weeks |
| Team Training |
2–3 days |
| Pilot Launch |
1–2 weeks |
| Scaling |
1 week |
After launch we provide support and development: new funnels, automation improvements, report configuration as the business grows. Investment ranges from $8,000 to $20,000 depending on complexity — we will give an exact quote after a free discovery call.
Get a consultation for your project — we will assess the timeline, scope, and expected ROI individually.
