Bitrix24
Bitrix24 chat integration: conversations straight into CRM
A client writes on the site or in a messenger — a lead with the full conversation appears in Bitrix24, and the manager replies from the familiar Chatva inbox.
14 days of the Team plan — free
Кира Мещерякова
Лид · Битрикс24 · 2 мин назад
Переписка прикреплена
Ответственный: Анна С. · назначена автоматически
2 min
from message to lead
5 events
streamed to the CRM via webhooks
100%
of conversations in the client card
API
and webhooks on the Business plan
Conversations live in messengers. Deals live in CRM. Manual work in between
What breaks when chats and Bitrix24 live apart
“Forgot to log the lead”
A client wrote in a messenger, the manager replied and moved on. Nobody created the deal in Bitrix24 — the client vanished from the pipeline forever.
The thread is torn off the deal
The CRM holds just a phone and a couple of handwritten lines. What was promised, which price was agreed — nobody can recall.
A new manager is blind to history
A colleague got sick, the deal was handed over. To understand the context you would need their phone — and it is not at hand.
Reports lie
How many leads came this month? From which channels? If half the inquiries never reach the CRM, analytics is just guessing.
What happens in Bitrix24 automatically
The connection works via Chatva's REST API and webhooks — configured in the dashboard without code
| Event in Chatva | What happens in Bitrix24 |
|---|---|
| New conversation from the site or a messenger | A lead is created with name, channel and first message |
| Client leaves a phone or email | The contact is enriched, the lead is linked to the existing client |
| Conversation assigned to an operator | The responsible manager changes in the lead |
| Conversation closed | The lead moves to the right pipeline stage |
| Client leaves a rating | Rating and comment land in the deal card |
The lead creates itself — no manual entry
Every inquiry from any channel becomes a lead: with the client's name, channel, first message and the entire following conversation. The manager never touches the keyboard — just replies.
- deduplication: search the contact by phone and email first;
- the first-touch channel is stored in the lead for analytics;
- the responsible person is filled in automatically from the conversation.
Кира Мещерякова
Лид · Битрикс24 · 2 мин назад
Переписка прикреплена
Ответственный: Анна С. · назначена автоматически
Replies in minutes, while the lead is warm
First-response speed is the main lead conversion factor. A push about a new conversation arrives instantly: the manager replies in minutes while competitors check email.
- notifications to the browser, Telegram and email;
- a conversation unanswered for five minutes signals the manager;
- the CRM lead records the first-response time.
Новый диалогсейчас
Telegram · Кира М.: «Здравствуйте! А есть ли рассрочка?»
Диалог без ответа 5 минут2 мин
Назначьте оператора, клиент ждёт
Custom logic via API and webhooks
The basic connection is configured without code, and custom logic is open through the REST API: pull conversations into your handlers, enrich deals with any data, build your own scenarios.
- events: message:new, conversation:new, conversation:update;
- signed webhooks with retries — no event gets lost;
- an OpenAPI spec for developers.
Диалог
Чатва
Вебхук
message:new
Битрикс24
лид + переписка
How to set it up
No developer needed — webhooks for the basics, REST API for complex logic
- 1
Enable the API in Chatva
On the Business plan an API key and webhook URL are created in the company settings.
- 2
Create an inbound webhook in Bitrix24
In the “For developers” section of Bitrix24 create a webhook with CRM permissions and copy its URL.
- 3
Map the events
Choose which Chatva events to send to Bitrix24: new conversation, contact, closing, rating. Ready-made connections work via connectors or directly.
- 4
Test with a trial conversation
Message yourself from the site — a lead with the conversation appears in the CRM within a couple of minutes.
How it works for a sales team
B2B and long cycles
A deal lives for months — the whole touchpoint history is in the card. Any manager gets the context in a minute; the client never has to “remind what we discussed”.
Online store with managers
Inquiries from the site and messengers become leads with product context right away. The head of sales sees a pipeline of real inquiries, not guesses.
Services and booking
A client booked in chat — the lead is already waiting in the pipeline with a date and a master. A repeat visit links to the existing contact, no duplicates.
Real estate
A listing inquiry is tied to the property. The realtor replies faster than competitors — and takes the client to a viewing.
What to check before integrating
Five questions that remove all surprises
- Cloud or on-premise? Webhooks work in both; on-premise needs external access to the portal.
- Access to the “For developers” section in Bitrix24 — needed to create the inbound webhook with CRM permissions.
- Where to put the leads: a dedicated chat pipeline or the shared one — the head of sales decides.
- The dedup rule: search the contact by phone/email first, create a new lead only after that.
- Who handles the unusual: the basic connection is no-code, complex logic goes to your developer with our documentation.
A pipeline without holes and manual entry
What changes in numbers when chats meet the CRM
0 leads
lost “because someone forgot to log it”
2 min
from message to CRM card
100%
of conversations attached to deals
1 inbox
for client replies instead of five apps
The head of sales laughed: “we got twice as many leads this month”. Turns out half the inquiries simply never reached the CRM before.
Honest pricing
Start free and grow with your customer flow. Cancel in one click, your data stays yours.
Pay for a year and get two months free.
Start
To test the idea
0 ₽/ per month
- 1 agent
- Site widget and Telegram
- 100 chats per month
- Quick replies
Team
For sales and support teams
1 490 ₽/ per month
- 5 agents
- All channels, no limits
- Autopilot and bots
- Telegram notifications
- Analytics and ratings
Business
Chains and high volumes
4 990 ₽/ per month
- Unlimited agents
- SLA and priority support
- API and webhooks
- White label, no Chatva mention
- A dedicated manager
FAQ about the Bitrix24 integration
Webhooks and the REST API are available on the free Bitrix24 plan too. On the Chatva side the integration works on the Business plan, where the API is available.
Both cloud and on-premise Bitrix24 work — webhooks are supported by both. On-premise needs external access to the portal.
Yes, the typical setup searches the contact by phone or email first and only then creates a new lead. No duplicates.
Yes, connections with amoCRM and 1C are built on the same API and webhooks. Message us — we will help configure it for your scheme.
Not for the basic connection: webhooks are configured in the interfaces of both systems. For custom logic, involve a developer — the API documentation is open.
Related reading
Connect conversations and CRM
The first lead from chat will appear in Bitrix24 today.