Setting Up Feedback to Bitrix24 CRM: Submissions to Leads and Deals

A feedback form on the site sends an email to the administrator—and that's it. No task for the manager, no history in CRM, no SLA on response. Clients wait for answers for days, requests get lost, managers don't see the full picture of inquiries. According to statistics, up to 30% of requests are lost during email transmission, and the average response time exceeds 4 hours. Setting up direct transfer to Bitrix24 solves this problem in 4–6 hours: each request becomes a lead or deal with an assigned responsible person, deadline, and full context. We have implemented over 50 such integrations—the average time to create a request in CRM after form submission is 1-2 seconds.

We configure the integration for your business: from a simple feedback form to multi-step custom forms with non‑standard fields. As a result, the manager sees the request in CRM one second after submission, not an hour later when they check email. Below, we break down the technical options: which components to use, how to properly create leads and deals, configure notifications, and avoid duplicates.

Feedback Component Options

In 1C-Bitrix, feedback is implemented via:

• bitrix:main.feedback — standard component, simple form.
• bitrix:form.result.new — extended web-form module with any field types.
• Custom component or Ajax form on React/Vue.

For all options the approach is the same: intercept the successful submission event and call the Bitrix24 REST API.

Why Lead and Not Deal?

The main question when setting up is which entity to create. A lead is suitable for new or unknown clients: the manager qualifies and converts it into a contact/deal. A deal should be created if the client already exists in the database—determined by phone/email via crm.duplicate.findByComm. If you just need to record the fact of an inquiry from an existing contact, use an activity (call/email).

For sites with a high volume of new inquiries, it's correct to create leads—this gives the manager context and allows proper funnel management. For B2B with a limited client base, create deals or activities immediately to avoid cluttering with unprocessed leads. Automation via REST API reduces entity creation time by 90% compared to manual entry.

How to Avoid Duplicate Contacts?

Duplicates are a common problem in integration. We implement a check via crm.duplicate.findByComm before creating a lead. If an existing contact is found, we link the new lead to it or create a deal. Additionally, you can set up a business process in Bitrix24 to automatically merge duplicates according to rules. This reduces the duplicate percentage to 1-2% vs 15% without checking.

Configuration via main.feedback Component

The component bitrix:main.feedback uses the event OnBeforeEventAdd (module main). Subscribe in init.php:

AddEventHandler('main', 'OnBeforeEventAdd', function(&$eventName, &$lid, &$fields) {
    if ($eventName !== 'FEEDBACK') return;

    $b24WebhookUrl = COption::GetOptionString('my_module', 'b24_webhook');
    $http = new \Bitrix\Main\Web\HttpClient();

    $leadData = [
        'TITLE'    => 'Обратная связь с сайта',
        'NAME'     => $fields['NAME'] ?? '',
        'PHONE'    => [['VALUE' => $fields['PHONE'] ?? '', 'VALUE_TYPE' => 'WORK']],
        'EMAIL'    => [['VALUE' => $fields['EMAIL'] ?? '', 'VALUE_TYPE' => 'WORK']],
        'COMMENTS' => $fields['MESSAGE'] ?? '',
        'SOURCE_ID'=> 'WEB',
    ];

    $http->post($b24WebhookUrl . 'crm.lead.add.json',
        json_encode(['fields' => $leadData]));
});

This handler creates a lead in CRM and returns its ID. Execution time is less than 1 second. On error (e.g., invalid webhook), the event is not interrupted—the submission is still sent via email.

Notifying the Responsible Person

After creating a lead via REST, a notification is automatically triggered to the responsible person in Bitrix24 (if CRM notifications are configured in the portal). Additionally, you can set a task with a 2-hour deadline:

$b24->call('tasks.task.add', ['fields' => [
    'TITLE'       => 'Ответить на обращение: ' . $leadData['NAME'],
    'RESPONSIBLE_ID' => $assignedId,
    'DEADLINE'    => date('c', strtotime('+2 hours')),
    'UF_CRM_TASK' => ['L_' . $leadId], // привязка к лиду
]]);

Storing Webhook Settings

The Bitrix24 webhook URL is stored in module settings via COption (table b_option), not hardcoded. The editing interface is in Settings → Product Settings → Module Settings.

What to Choose: Lead, Deal, or Activity?

The choice of entity affects the funnel and manager workload. Lead—full qualification cycle, requires time for conversion. Deal—immediately in work, but without a "warming up" stage. Activity—minimal action, but doesn't appear in funnel reports. For new high-potential clients, a lead is better; for repeat inquiries, a deal or activity. Comparison by criteria: processing speed (activity is fastest), analytics depth (lead gives full picture), duplicate risk (lower for activity).

Typical Stages and Timelines

Basic setup takes 4 to 6 hours. Complex scenarios (custom forms, multiple sites, non‑standard fields) may take up to 2 days. Contact us for a consultation and accurate estimate—we will prepare a commercial proposal without surcharges for urgency.

What's Included in the Work

• Audit of existing forms and agreement on field mapping (1 hour)
• Creation of incoming webhook with necessary permissions (30 min)
• PHP handler development with duplicate check using crm.duplicate.findByComm (2–3 hours)
• Configuration of push notifications and automatic task creation with deadlines (1 hour)
• Testing and debugging of all scenarios: success, error, duplicate detection (1–2 hours)
• Documentation: storage of webhook URL, code comments, and event log setup
• Post-launch support for 2 weeks

AddMessage2Log('Lead created: ' . print_r($leadData, true), 'b24_integration');

Our Experience and Guarantees

We have been working with Bitrix24 for over 7 years and have completed 50+ feedback integrations for companies of various sizes—from online stores to manufacturing enterprises. We guarantee correct operation of all mechanisms: lead creation, duplicate handling, notifications. Our integration is 3x faster than manual entry and reduces duplicate rates from 15% to under 2%. After launch, we provide support for 2 weeks. Order feedback setup with CRM—turn a simple form into a managed sales channel. Starting from $200, we'll evaluate your project and deliver a turnkey solution in 4–6 hours.

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

1. Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
2. Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
3. Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
4. Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
5. Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
6. Training. Trainings tailored to your configuration, video instructions, documentation.

What is included in the work?

Cloud or on-premise: which to choose?

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

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.