What we integrate with Bitrix24
Kaspi, WhatsApp, Telegram, 1C, telephony, website — each connection with a timeline and scope. We do not sell “integration in general”: below is exactly what gets connected, what the manager gains and where it is described in detail.
How much does a Bitrix24 integration cost?
The price is based on the scope of work. Typical connections fit into clear ranges: WhatsApp and Instagram via Wazzup — 2–4 hours, Telegram — 2–4 hours, a Kazakhstan operator’s telephony over SIP — 4–8 hours, Kaspi payments and orders — 8–16 hours, a standard 1C exchange — 16–40 hours, exchange customisation and complex scenarios — by estimate. We name the exact amount in tenge including VAT in a proposal within one business day after a 30-minute audit; cost and deadline are fixed in the contract.
Estimates for typical IT TECHNOLOGY projects, September 2026. Bitrix24 licences, Wazzup and telecom tariffs are paid separately at the provider’s list price.
Integration showcase
Everything listed here we have connected more than once; each has a page or an article with details.
What each integration gives and how long it takes
Hours are the scope of a typical project; the calendar time depends on how fast the provider issues access.
| Integration | What the business gets | Scope | More |
|---|---|---|---|
| Kaspi | Kaspi payments and orders visible in the deal, no manual statement matching, stock written off | 8–16 hours | “Kaspi integration” page and the Kaspi article in the blog |
| WhatsApp + Instagram via Wazzup | All conversations in the record, replies from the CRM, templates, campaigns to the base without bans | 2–4 hours | “Wazzup” page and the messaging article |
| Telegram | Requests from the bot and channel into the pipeline, team notifications | 2–4 hours | “Telegram integration” page |
| 1C (standard exchange) | One directory of counterparties and products, invoices from the deal, stock in the record | 16–40 hours | “1C integration” page and the exchange article |
| Telephony (SIP / Asterisk / operator app) | Client record on call, recording, missed calls into tasks, reports per manager | 4–8 hours | “IP telephony” page |
| Website, quizzes, landing pages | Every request is a lead with source and UTM, no duplicates | 2–6 hours | Included in implementation |
| End-to-end analytics, e-mail and SMS | Cost per request by channel, campaigns by segment | 4–12 hours | End-to-end analytics article |
An integration is part of the implementation, not a separate module
Process first, button second
Before connecting Kaspi or 1C we work out who does what with the data. Otherwise the integration brings the chaos of the accounting system into the CRM.
A contract with price and deadline
The cost and deadline of every integration are fixed in the contract; our delay costs us 0.1% per day. Details on the guarantees page.
Kazakhstan specifics
Several legal entities per client, e-invoices and 1C:Kazakhstan, local telecom operators, Kaspi — things missing from Russian manuals.
Support after launch
1C exchanges and telephony break on updates — we watch them under an SLA rather than “deliver and leave”.
Frequent questions about integrations
Tell us what needs to be connected to Bitrix24
In a 30-minute audit we will say which integrations you actually need and name the price and deadline in a proposal the next business day.