We design contact cards in Bitrix24 so that managers find the right person within seconds. Instead of chaos — a clean structure: every role and relationship with the company is calibrated. Deal speed and conversion grow directly from proper data organization. In one project, we cut time to find the decision-maker by 5x through position standardization and role introduction — saving 15,000 rubles per month on cold calls. We have been working with Bitrix24 for over 7 years and completed 50+ CRM optimization projects.
Consider the key elements of a contact card.
Contact's Place in CRM Architecture
A contact (table b_crm_contact) is the central link between people and business processes. One contact can be attached to multiple companies (many-to-many via b_crm_contact_company), be a participant in deals, a recipient of newsletters, a source of calls. The difference between a contact and a lead is fundamental: a lead is a one-time inquiry, a contact is a long-term profile. Card fields should reflect not a single transaction but personal data and roles. For a deep understanding of CRM principles, see the Wikipedia article on CRM.
Why Position Standardization Is Critical for Filtering?
Without standardization, the 'Position' field becomes garbage: "Head Physician", "head physician", "Head.Physician" — four variants of the same. Our client, a medical equipment distributor, faced exactly this: 4,200 contacts, but managers could not quickly find who in the hospital was responsible for ultrasound procurement. The solution: replace the string field with a custom list of fixed options. A custom list field reduces filtering time by 5x compared to a string field.
How to Design a Contact Card for B2B Segment?
For B2B, priority is professional data: company, position, role in the DMU (decision-making unit), next contact date. Personal data is minimal. For B2C — personal profile with purchase history and segments from RFM analysis. For professional services — fields: source, current projects, documents (NDA).
Key Contact Fields
| Field Type |
Examples |
Purpose |
| Identification |
NAME, LAST_NAME, HONORIFIC |
Basic identification |
| Contact |
PHONE (work, mobile), EMAIL |
Communication with client |
| Company relation |
COMPANY, POST, ROLE (decision-maker, influencer) |
Sales context |
| Custom |
Specialization, source |
Flexible filtering |
| 1C integration |
1C_ID, 1C_ACCOUNT |
Link to accounting system |
Comparison of design approaches:
| Criterion |
String field |
Custom list |
| Uniformity |
None |
Full (all records uniform) |
| Filtering speed |
1x (baseline) |
5x faster |
| Data accuracy |
Depends on operator |
Controlled by admin |
How to Set Up Custom Fields for Roles: Step-by-Step
- Define the list of roles in your business (decision-maker, influencer, user, undefined).
- Create a list field via
crm.contact.userfield.add or through the CRM interface. Set type 'enumeration'.
- Migrate old data via script: update each contact via
crm.contact.update, populating the new field.
- Set the field as mandatory when moving a deal to the 'Quote Sent' stage (via Bitrix24 business processes).
Typical design mistakes
- Using a text field for position — leads to duplicates and chaos.
- No link to company — loses deal context.
- Not using required fields — managers skip filling critical data.
What Turnkey Contact Card Design Includes
- Audit of current CRM structure and identifying bottlenecks.
- Designing fields, lists, and relationships between entities.
- Configuring access rights for each role (manager, director, marketer).
- Creating custom fields and migrating data from old fields.
- Team training and documentation.
- Warranty on work and post-launch support.
Case Study: Contact Card for a Medical Equipment Distributor
Our client, a distributor, had 4,200 contacts with chaotic positions. We standardized the POST field, added a decision-making role (list: Initiator, Influencer, Decision-maker, User) and specialization (list of medical specialties). We hid UTM fields from managers. The client noted: "After standardization, we started reaching the right decision-makers on the first call, saving 2 hours per day per manager." Cold calls without results dropped by 30%, as calls went to the right people.
Why Integrate 1C with Bitrix24 for Contact Cards?
Integrating 1C with Bitrix24 enriches contact cards with data from the accounting system: purchase history, accounts receivable, contract prices. This lets the manager see the full picture without switching systems. Setting up exchange via CommerceML or REST API is a typical stage of Bitrix24 development.
Timeline and Terms
Contact card design and setup: 2 to 4 business days. When working on contact, company, and deal cards simultaneously — 8–12 days including approvals. Cost is calculated individually for your project. Get a consultation on your project — it's free. Order an audit of your CRM — it's free.
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.
