Website leads in email, WhatsApp, and your CRM: how to set up delivery so you never miss one

A lead you hear about a day later costs the same as one you answered in a minute, but it turns into a sale less often. That's why you set up lead delivery from your website — your potential customers — before you launch ads, following the "at least two channels" rule: one for speed and one for the record. In LeadForms, every channel is connected in the same place — quiz → "Settings" → "Integrations" — and each lead goes out immediately to every active channel, with the quiz answers and contact details. Below is the actual order for setting up email, messengers, Kommo, Bitrix24, and webhooks, and at the end, a setup that keeps you from losing anything.

Website leads to email: setup and testing

The email arrives as soon as the person submits the form. It contains all the answers to the questions and the contact details they left. Setup takes a couple of minutes.

1. Open the quiz → "Settings" → "Integrations" → Email card → "Connect."
2. At the top of the window is your account email with the checkbox "Send leads by email to." Check it if you want emails at that address.
3. In the "Additional emails" field, type an address and click "Add." Repeat for each recipient: the salesperson, the manager, the team's shared inbox.

Leads go to every address on the list. To stop someone from receiving them, delete their address; nobody else is affected. If emails don't arrive, check in this order: the spam folder (providers sometimes put the first emails there, so mark them "not spam"); a typo in the address; the "Leads and reports" section of your dashboard — if the lead is there but the email didn't arrive, the problem is with email, not the quiz; a corporate server that filters external senders, so add a regular inbox and compare. The full version is in the email notifications guide.

Email is the channel for your records: messages can be searched, forwarded, and kept for years. As your only channel it works poorly, because an email is easy to miss among all the others.

Website leads in WhatsApp and Telegram: connected in a minute

Messengers are the channel for speed: the notification hits your phone the moment the form is submitted, and you don't need the dashboard open. LeadForms sends leads to both WhatsApp and Telegram, and both cards are in the same "Integrations" tab, no developer needed. Telegram connects in under a minute because LeadForms has its own bot: no tokens, no need to create a separate bot.

1. Open the quiz → "Settings" → "Integrations" → Telegram card → "Connect."
2. Click "Open Telegram": a chat with the LeadForms bot opens. Click "Start" there.
3. The settings window will show "Waiting for connection…"; the status updates on its own and you don't need to close the window.

From then on, each lead arrives in that chat with the answers and contact details. Details are in the Telegram notifications guide. The limitation of messengers comes from the same thing as their strength: chat messages scroll up fast, and a week later finding a specific lead takes more effort than in email or a CRM.

CRM: website leads in Kommo

When you have more leads than a salesperson can keep in their head, you need a CRM: there, each lead has a status, an owner, and a history. The Kommo integration (formerly amoCRM) connects through authorization, with no keys or webhooks.

1. Quiz → "Settings" → "Integrations" → Kommo card → "Connect," then "Install integration."
2. In the pop-up, choose your Kommo account and click "Allow." You'll see a message confirming the connection.
3. Configure how deals are created. All fields are optional: if you leave everything as is, the deal is created using Kommo's default rules.

What's worth filling in right away:

• Pipeline: where the deal ends up. If you have a separate pipeline for website leads, specify it; otherwise the default pipeline is used.
• Owner: who it's assigned to. If you don't pick anyone, the deal is distributed according to Kommo's rules.
• Title: the deal name, for example "Quiz lead: kitchens."
• Tags: labels for filtering later by quiz, service, or source.

Further down you configure sending additional fields. The quiz answers go into the deal, so the salesperson sees the budget and the need before calling. Screenshots of each step are in the Kommo guide.

Bitrix24: website leads via inbound webhook

In Bitrix24 the lead is created as a lead. Connecting takes a bit longer than Kommo because the portal requires you to create an inbound webhook, but LeadForms guides you through each step.

1. Quiz → "Settings" → "Integrations" → Bitrix24 card → "Connect."
2. Copy your portal domain from the browser address bar — the part of the address up to the first slash, like b24-xxxxxx.bitrix24.com — and paste it into the "Your Bitrix24 URL" field.
3. The window will show a direct link to create the webhook in your portal. Open it, choose the "Other" card, then "Inbound webhook." It has to be inbound: an outbound webhook works the other way around and won't do here.
4. Under permissions, choose CRM and click "Create." Copy the URL from the "Request builder" block. It looks like this: https://your-portal.bitrix24.com/rest/1/xxxxxxxx/profile.json.
5. Go back to LeadForms and paste the address into the "Sample URL for REST call" field. The domain, authorization code, and user ID fill in automatically.
6. If needed, enter the "Owner ID": the person's number shown in the address of their Bitrix24 profile, like /company/personal/user/1/. If you leave it empty, leads go to the webhook owner. Below that you can set the lead title.
7. Turn on the "Enable Bitrix24" toggle and save. Without it the integration doesn't work, and this is the most common cause of "I set it up and no leads are coming in."

The full walkthrough with screenshots is in the Bitrix24 guide.

Webhooks and ApiX-Drive: if you use a different CRM

For your own CRM, a spreadsheet, or a service without a ready-made integration, there are webhooks: for each lead, LeadForms sends a POST request with JSON to the URL you specify. You set it up in the same "Integrations" tab, Webhooks card; all you need is your receiver's address. The receiver must respond with a valid HTTP status.

The request body contains: answers, the array of questions with their answers; contacts, with name, phone, email, address, comment, and messenger, if collected; created, the lead date; result, the quiz result, if one was shown; extra, with the URL of the page the lead came from, the referrer, UTM tags, and cookies; and separately the lead id, the quiz id, and the completion time in seconds. That's enough to create a deal on your side, set a priority based on the answers, and tie the lead to an ad campaign via UTM. If the quiz has a two-step form, the webhook fires when the lead is complete; if someone filled in only the first step and didn't come back, the lead may go out about sixty seconds later with partial data. The field descriptions and a sample PHP receiver are in the webhooks guide.

If you don't have a developer, ApiX-Drive gets you the same result: an intermediary service that connects LeadForms to 50+ systems — from CRMs to Google Sheets — without code. Just sign up for ApiX-Drive and link the two accounts; there's a separate guide in the integrations section.

Handling website leads: a setup that keeps you from losing anything

Integrations don't exclude each other: every active channel gets the lead at the same time. A setup that works for a small business looks like this.

• WhatsApp or Telegram: to know about the lead the moment it's submitted and call within the first few minutes.
• Email to the team's shared inbox: backup and archive for when a phone is dead and someone is on vacation.
• The CRM: the only place where a lead has a status. You count how many leads were properly handled in the CRM, not in the chat.

Three rules that close the typical gaps:

1. Test the chain with a test lead before launching ads: complete the quiz yourself and make sure the email arrived, the messenger notification arrived, and the deal was created in the CRM with the answers. Five minutes of testing saves a week of lost leads.
2. Once a day, compare the "Leads and reports" section of your dashboard with the CRM. All leads are stored there regardless of integrations; if the CRM has fewer, find the step where the chain broke.
3. Assign the owner by rule, not by "whoever sees it first": pipeline and owner in Kommo, Owner ID in Bitrix24. A lead without an owner is the most common reason "nobody called back."

FAQ

Can I receive leads in email, WhatsApp, and the CRM at the same time?

Yes, the channels work in parallel. Each active integration gets the lead right after the form is submitted, with the same answers and the same contact details.

What arrives in email and the messenger — just the contact or the answers too?

The contact details and all the answers to the quiz questions. The salesperson sees the need, the timeline, and the budget before calling, instead of asking for them again.

Do I need my own Telegram bot and a token?

No. LeadForms has a ready-made bot: you click "Open Telegram" and "Start," and the connection is confirmed automatically.

Leads aren't being created in Bitrix24 even though the webhook is set up. What should I check?

Three things: whether the "Enable Bitrix24" toggle is on and the settings are saved; whether you pasted exactly the "Request builder" URL into the "Sample URL for REST call" field; and whether you created an inbound webhook, not an outbound one, with CRM permissions.

Where do leads go if no integration is set up?

To the "Leads and reports" section of your dashboard: they're always stored there. Integrations just copy them to wherever you find it easier to work. But without new-lead notifications you'll find out late, so turn on at least email or a messenger from the start.