Automate Chat Data Transfer to Bitrix24 CRM
Imagine a client submits a request via online chat, but the manager only sees the name and phone — all UTM tags, cart contents, and interaction history remain in the chat. Manual transfer leads to duplicates and errors. We solve this with over 50 chat integrations (JivoSite, Chatra, Talk-Me, LiveChat) with Bitrix24. Save up to 80% on manual data entry costs with our chat-to-CRM integration starting at $350.
Why a Simple Connector Isn't Enough?
The native connector from the marketplace only suits simple scenarios. If you need to pass custom fields (cart total, UTM tags, order number), you can't do without a Webhook. A Webhook gives you full control over the data but requires 2–3 times longer development than installing a ready connector. For example, a JivoSite connector takes 2–4 hours to integrate, while a custom Webhook takes 2–3 days but allows flexible field mapping. The Webhook method is 3x more flexible than the native connector and reduces manual data entry by 80%. Setting up a mail channel is 10x faster than a custom Webhook, taking just 1–2 hours.
Three Methods of Data Transfer
Method 1: Webhook → crm.lead.add
Most chat platforms (JivoSite, Chatra, Talk-Me, LiveTex) support a Webhook when a dialog ends. The handler on the site receives the data and creates a lead via crm.lead.add.
Bitrix24 REST API documentation: https://dev.1c-bitrix.ru/rest_help/crm/leads/crm_lead_add.php
View PHP code for Webhook handler
<?php
// /local/api/chat-to-crm.php
require_once $_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php';
$payload = json_decode(file_get_contents('php://input'), true);
if (!$payload) { http_response_code(400); exit; }
$name = trim($payload['visitor']['name'] ?? $payload['name'] ?? '');
$email = trim($payload['visitor']['email'] ?? $payload['email'] ?? '');
$phone = trim($payload['visitor']['phone'] ?? $payload['phone'] ?? '');
$text = buildTranscript($payload); // collect chat history
// Basic validation: at least email or phone
if (!$email && !$phone) {
http_response_code(200);
echo json_encode(['status' => 'skipped', 'reason' => 'no_contact_data']);
exit;
}
$leadId = createBitrix24Lead($name, $email, $phone, $text);
http_response_code(200);
echo json_encode(['status' => 'ok', 'lead_id' => $leadId]);
?>
<?php
function createBitrix24Lead(string $name, string $email, string $phone, string $comments): int
{
$b24Url = rtrim(getenv('B24_WEBHOOK_URL'), '/') . '/';
$fields = [
'TITLE' => 'Chat: ' . ($name ?: $email ?: $phone),
'NAME' => $name,
'COMMENTS' => $comments,
'SOURCE_ID' => 'WEB',
'STATUS_ID' => 'NEW',
];
if ($email) $fields['EMAIL'] = [['VALUE' => $email, 'VALUE_TYPE' => 'WORK']];
if ($phone) $fields['PHONE'] = [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']];
$ch = curl_init($b24Url . 'crm.lead.add.json');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_POSTFIELDS => http_build_query(['fields' => $fields]),
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 10,
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);
return (int)($response['result'] ?? 0);
}
?>
For debugging, use logging to file or a monitoring system. We guarantee the handler correctly handles network errors and duplicates.
Method 2: Native Bitrix24 Connector
JivoSite, LiveChat, and several other platforms have a ready connector in the Bitrix24 marketplace. Installation: Bitrix24 → Marketplace → find the required chat → Install. Authorize the connector in your chat account, configure which Open Line receives the inquiries.
Limitation of native connectors: data is passed as provided by the platform. Custom fields (e.g., cart data from Bitrix) cannot be passed via a native connector — only via Webhook with a custom handler.
Method 3: CRM Mail Channel
The simplest option for chats without Webhook: configure sending the transcript to an email that Bitrix24 monitors as a CRM mail channel. Bitrix24 recognizes the contact by the email in the message and creates a lead automatically.
Setup: Bitrix24 → CRM → Settings → Mail Channels → Add channel. Specify the mailbox from which chat emails arrive. Note: only information from the email will go into the lead — phone number and name if manually entered.
Avoiding Lead Duplicates
Duplication is a common problem in chat integration. If a client writes multiple times, without a check you'll get dozens of identical leads. Solution: before calling crm.lead.add, check for an existing contact by email or phone using crm.lead.list. In our handler we use a function leadExists that queries the API with a filter by EMAIL and PHONE. If a lead already exists, we update it or add a comment, rather than creating a new one. This reduces duplicates by 95%.
Passing Additional Data via UTM
For lead attribution to traffic source, pass UTM tags in the Webhook:
// On the site side: read UTM from URL and store in sessionStorage
const params = new URLSearchParams(window.location.search);
['utm_source', 'utm_medium', 'utm_campaign'].forEach(k => {
if (params.get(k)) sessionStorage.setItem(k, params.get(k));
});
<?php
// In the Webhook handler: get UTM from chat data
// (most chat platforms pass referrer and custom_data)
$utmSource = $payload['visitor']['utm_source'] ?? '';
$utmMedium = $payload['visitor']['utm_medium'] ?? '';
$utmCampaign = $payload['visitor']['utm_campaign'] ?? '';
$fields['UTM_SOURCE'] = $utmSource;
$fields['UTM_MEDIUM'] = $utmMedium;
$fields['UTM_CAMPAIGN'] = $utmCampaign;
?>
Our Work Process
- Analysis: Examine portal architecture, list of chat platforms, data requirements.
- Design: Select integration method, field mapping, deduplication scheme.
- Development: Write Webhook handler, configure connector or mail channel.
- Testing: Test on a test portal, create test leads, review logs.
- Deployment: Move to production, enable monitoring, deliver documentation.
Comparison Table
| Criteria |
Webhook |
Native Connector |
Mail Channel |
| Flexibility |
High (3x vs connector) |
Low |
Medium |
| Setup Complexity |
Medium |
Low |
Very Low |
| Custom Field Support |
Yes |
No |
No |
| Deduplication |
Configurable |
Built-in |
Automatic |
| Implementation Speed |
2–3 days |
2–4 hours |
1 hour |
Typical Implementation Timelines
| Integration Type |
Duration |
| Mail Channel |
1–2 hours |
| Native Connector |
2–4 hours |
| Webhook with Custom Logic |
2–5 days |
Verifying Integration
Create a test dialog in the chat, enter a name, email, and phone. Verify that a new lead appears in CRM with these details. Check UTM tag population and no duplicates on repeat requests. If the lead isn't created, inspect handler logs and Webhook access rights.
What's Included in the Work?
- Setup of Webhook handler or native connector installation
- Creation of custom fields in CRM (if needed)
- Integration with the source: JivoSite, Chatra, Talk-Me, LiveChat, etc.
- Operational documentation and access handover
- 1 month of technical support after launch
Timeline and Cost
Integration timelines depend on complexity and chosen method: from 1 day (mail channel) to 1 week (Webhook with custom logic). Cost is calculated individually after analyzing your project. Example prices: mail channel from $350, native connector from $500, custom Webhook from $1200. Contact us for a free consultation and estimate. Order chat-to-CRM integration setup — we'll choose the optimal method and implement it turnkey. Our engineers have over 8 years of experience with Bitrix24 and sales automation.
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.