Integration

WhatsApp for Bitrix24, on the official Business API

Every WhatsApp conversation becomes a Bitrix24 lead, deal or contact — with the fields you choose, in the pipeline you already use. No copy-paste, no separate inbox to babysit.

What this integration actually does

Zhat Convex sits between the official WhatsApp Business Platform and your Bitrix24 portal. A customer messages your WhatsApp number; the conversation lands in a shared team inbox, and the same moment it does, Zhat Convex writes it into Bitrix24 — as a lead, a deal or a contact, whichever your process expects.

It is a two-way link, not a one-way dump:

  • Inbound. New WhatsApp conversations create Bitrix24 records, populated with the fields you mapped — including which click-to-chat campaign or QR code produced the lead.
  • Outbound. Lead status changes in Bitrix24 flow back, so the inbox reflects where the deal actually stands.
  • People. Your Bitrix24 employees and departments are mirrored, so conversations route to the right owner and attribution survives the handoff.

Map any WhatsApp field to any Bitrix24 field

Most connectors decide for you which data lands where, and you live with it. Zhat Convex keeps a canonical catalogue of 25 conversation fields — customer name, phone number, first message body, the campaign and UTM parameters behind the click-to-chat link, the assigned agent, conversation tags, the WhatsApp number that received it — and a mapping editor that points each one at whatever Bitrix24 field you want, custom fields included.

The same catalogue drives the Zoho CRM connector, so the mapping you design is a property of your business, not of one vendor's schema.

How to connect WhatsApp to Bitrix24

  1. Create your Zhat Convex workspace and choose a plan.
  2. Connect your WhatsApp number. We walk you through Meta Business verification, registering the number on the WhatsApp Business Platform, and getting your first message templates approved.
  3. Paste your Bitrix24 inbound webhook. In Bitrix24, go to Developer resources → Other → Inbound webhook, grant it CRM scope, and copy the URL. It must include the REST path — it looks like https://your-portal.bitrix24.com/rest/1/abc123token/, not just your portal address.
  4. Map your fields. Accept the sensible defaults, or point each WhatsApp field at the Bitrix24 field you actually use.
  5. Send a test message. The conversation should appear in your inbox and the lead in your Bitrix24 pipeline within seconds.

What Bitrix24's built-in Open Channels won't do

Bitrix24 Open Channels can receive WhatsApp through a connector, and for some teams that is enough. What it does not do is put your own number on the official WhatsApp Business API — that means Meta Business verification, number registration, template approval, and a sender reputation you own rather than share. That onboarding is the hard part, and it is the part Zhat Convex takes on.

You also get the things a CRM connector alone cannot give you: broadcasts, click-to-chat links and QR codes with campaign tracking, automation and auto-replies, voice calls, and honest per-message cost accounting.

What WhatsApp actually costs, and how we bill it

Two separate things, kept separate. You pay Zhat Convex a flat platform subscription — $49, $99 or $199 a month. Meta bills its own messaging charges per delivered message, priced by the recipient's country and the message category.

Zhat Convex meters every message against Meta's own billable flag and draws the cost from a WhatsApp budget you top up. Service replies inside the 24-hour customer service window are free — Meta does not charge for them and neither do we. There is no invented “5,000 messages included” allowance to run out at the worst possible moment. See pricing for the full breakdown.

Bitrix24 + WhatsApp: common questions

Does Bitrix24 have a native WhatsApp integration?
Bitrix24 has Open Channels, which can connect WhatsApp through a third-party connector — but it does not onboard your own number onto the official WhatsApp Business API for you. That is the gap Zhat Convex fills: we handle Meta Business verification, number registration and template approval, then push the conversation into Bitrix24 as a lead, deal or contact.
What does Zhat Convex create in Bitrix24?
Leads, deals and contacts. Zhat Convex also syncs lead status back from Bitrix24, and mirrors your Bitrix24 employees and departments so conversations can be assigned to the right person automatically.
Can I choose which WhatsApp fields go into which Bitrix24 fields?
Yes. Zhat Convex has a canonical catalogue of 25 conversation fields — the customer name, phone, first message, the click-to-chat campaign that produced the lead, the assigned agent, tags and more — and a mapping editor that lets you point each one at any Bitrix24 field, including your custom fields. You are not locked into someone else's schema.
Do I need my own WhatsApp Business API number?
Yes, and it stays yours. Zhat Convex runs on the official WhatsApp Business Platform under your own Meta Business account, so you own the number and the sender reputation — you are not sharing a pooled number.
What does it cost to run WhatsApp through Bitrix24?
Two separate costs. Zhat Convex charges a flat platform subscription from $49/month. Meta charges separately, per delivered message, priced by the recipient country and message category — Zhat Convex meters that against Meta's own billable flag and draws it from a WhatsApp budget you top up. Service replies inside the 24-hour customer service window are free.