Bitrix24: requests become leads
Every request in your Sensever project can become a lead in your Bitrix24. The lead includes the customer's name, phone or email, the channel, the customer's first message and a link to the request. When the request is closed, the conversation is added to the lead as a comment.
What you need
A Bitrix24 portal (cloud or self-hosted) where you may create webhooks — usually an administrator.
Leads turned on in the portal. In the simple CRM mode (deals and contacts only, no leads) Sensever cannot create leads.
Owner or admin rights in the Sensever project.
Step 1. An inbound webhook in Bitrix24
In Bitrix24, open Developer resources → Other → Inbound webhook.
In the permissions, tick CRM (crm). Nothing else is needed.
Click Save and copy the webhook address — it looks like
https://your-portal.bitrix24.com/rest/1/abc123…/.
Keep this address secret: anyone who has it can work with your CRM. Sensever stores it encrypted and shows only its beginning and last characters.
Step 2. Connect it in Sensever
Projects → the project → the CRM tile.
Paste the webhook address. If you copied it with a method at the end (for example
…/profile.json), that's fine.Choose when to create a lead (see below).
Choose the country for numbers written without "+". By default it's the country of the project owner's account. A number like "8 912 345-67-89" is read in this country; numbers with "+" are read as written.
Click Connect. Sensever checks the webhook: that it works, has the CRM permission and that leads are on. It also adds the lead source Sensever to your portal (if the webhook may do it; otherwise leads go with the source "Other").
When a lead is created
Only when the customer leaves a phone or email (default) — conversations without a contact don't clutter the CRM.
Right at the first message — every request becomes a lead; the phone or email is added later when it appears.
You can change this on the CRM tile at any time; it applies to new events.
Where the contact comes from
Sensever adds a phone or email to the lead from:
the messenger: the WhatsApp number; the customer's name and @username in Telegram, MAX, Instagram and Facebook Messenger;
the request card: a phone your team typed in, or a contact the customer shared after "Request contact";
your website: the name, email and phone you pass to the widget with
identify();a Sensever account: its confirmed phone and email;
the customer's own messages: a phone or email the customer writes in the chat.
Only the customer's messages count, never your team's. Only clear phone forms are taken — "+7 (912) 345-67-89", "8 912 345-67-89", "912-345-67-89". Sums, order numbers, article numbers, card numbers and dates are not phones, even when they are long. Phones go to Bitrix24 in the international format (+79123456789), marked as mobile or work.
What a lead looks like
Title: "Request #12 — WhatsApp". The number counts the project's requests sent to Bitrix24, starting from 1.
Name, phone, email — what Sensever knows.
Source: Sensever. Source details: the channel or your website, @username and the profile link.
Comment: the customer's first message and the link to the request in Sensever. The link opens for your team after signing in.
Duplicates
Before creating a lead, Sensever searches Bitrix24 by the phone and email. If a contact or a lead with them already exists, no new lead is created: the new request goes to the existing record as a comment. A contact is preferred to a lead; among several, the newest one is used.
A phone or email that appears later is added to the lead Sensever created. If the request went to an existing record, the new contact is added there as a comment — Sensever never changes someone else's record.
When the request is closed
The conversation goes to the lead (or the found record) as a comment: who wrote what and when (time in UTC), files marked as "[files: N]". Very long conversations are cut from the beginning, and the latest messages are kept.
Errors
If Bitrix24 stops accepting leads, the CRM tile shows "Leads are not being sent" with the reason, and the Sensever Channels bot messages the project owner and admins once:
Message | What to do |
|---|---|
The webhook was deleted or the address is wrong | Create a new inbound webhook and paste its address on the CRM tile. |
The webhook has no "CRM (crm)" permission | Edit the webhook in Bitrix24, tick CRM (crm), save. |
Leads are turned off in the portal | Switch the CRM to the classic mode (with leads) in the CRM settings. |
Bitrix24 refused the lead data | Check required fields you added to leads in Bitrix24 — Sensever fills only title, name, phone, email, source and comment. |
Bitrix24 does not respond | Nothing: Sensever retries by itself. |
Requests waiting during an error are sent as soon as you paste a working webhook. Sensever keeps to the Bitrix24 limit of two requests per second, so a busy hour may reach the CRM with a short delay.
Turning it off
Disconnect on the CRM tile stops sending new requests. Leads already created stay in Bitrix24. If you connect again later — or connect another portal — the numbering starts from 1, and requests opened before the connection are not sent.
Yorumlar