Integration / Messaging
In short
Telegram connects natively: create a bot with @BotFather and add its token in Bitrix24's Contact Center, and chats land in Bitrix24 with history saved to the CRM. Twilio is built in as an SMS provider (CRM → Sales → Sales center) and as a WhatsApp channel. For Indian SMS you need a DLT-registered provider, which usually means a marketplace app or a custom SMS connector.
Clients don't all choose the same channel. Some message on Telegram, some reply to SMS, some only answer WhatsApp. If each channel lives in a separate app on someone's phone, the CRM shows half the conversation and follow-ups depend on memory.
Bitrix24's Contact Center and SMS providers bring these channels into one place. Here is what works natively, what each provider costs you in setup, and where a custom connector is the practical answer — particularly for SMS in India.
Checked against the Bitrix24 Market and vendor documentation on 6 October 2026. Sources are listed at the end.
Built-in Telegram channel: create a bot in @BotFather, paste its access token into Bitrix24 (CRM → Contact Center → Telegram).
Best for: Businesses whose clients use Telegram for support or sales.
Twilio is available as a built-in SMS provider under CRM → Sales → Sales center → SMS provider.
Best for: International SMS where Twilio coverage and pricing suit you.
One of Bitrix24's documented WhatsApp connection methods (alongside Edna.io and Instant WhatsApp).
Best for: Teams already using Twilio. See our WhatsApp guide for the other routes.
Indian commercial SMS must go through a DLT-registered provider with registered sender IDs and templates.
Best for: Any business sending SMS to Indian numbers.
Inbound Telegram message
Telegram → Bitrix24
Opens a chat in Contact Center, matched to or creating a CRM record.
Outbound SMS
Bitrix24 → gateway
From a CRM record or automation rule, using an approved template.
Delivery status
Gateway → Bitrix24
Delivered / failed on the record — so automation doesn't assume a message arrived.
SMS replies
Gateway → Bitrix24
Where the route supports two-way SMS, replies land on the same record.
Opt-outs
Gateway → Bitrix24
STOP / unsubscribe recorded so campaigns respect consent.
| Data | Direction | What good looks like |
|---|---|---|
| Inbound Telegram message | Telegram → Bitrix24 | Opens a chat in Contact Center, matched to or creating a CRM record. |
| Outbound SMS | Bitrix24 → gateway | From a CRM record or automation rule, using an approved template. |
| Delivery status | Gateway → Bitrix24 | Delivered / failed on the record — so automation doesn't assume a message arrived. |
| SMS replies | Gateway → Bitrix24 | Where the route supports two-way SMS, replies land on the same record. |
| Opt-outs | Gateway → Bitrix24 | STOP / unsubscribe recorded so campaigns respect consent. |
Two or more of these? Get a written recommendation before you buy an app.
Get a free messaging planCustom development
We connect any SMS gateway or messaging platform to Bitrix24 through its official extension points, so the provider appears inside Bitrix24 like a native one.
messageservice.sender.add registers your SMS gateway as a Bitrix24 SMS provider, so CRM records and automation rules can send through it; delivery statuses are written back.
Custom Contact Center connectors (imconnector.register and related methods) for messaging channels Bitrix24 doesn't support natively.
DLT-registered providers' APIs with template IDs and sender IDs mapped per message type (transactional, promotional, OTP).
Twilio Messaging API with status callbacks; Telegram Bot API for flows beyond the native channel (menus, structured lead capture).
Which channels, which countries, which message types — and the registration (DLT, sender IDs) each needs.
Telegram bot and Twilio where they fit.
Register your gateway as a Bitrix24 SMS provider or Contact Center connector.
Registered templates and variables linked to automation rules.
Delivery status, replies, and opt-outs written back to the record.
Queues, working hours, and documentation.
Typical effort: Connecting Telegram or Twilio is typically a day or two; a custom SMS provider connector with DLT templates and delivery reports usually takes one to two weeks. The integration cost guide explains what moves the number; you get a fixed price after the free review.
Tell us which channels and countries you message. We'll set up what's native and build the connector for the rest — including DLT-compliant SMS for India.
Create a bot with @BotFather in Telegram, copy its access token, then in Bitrix24 open CRM → Contact Center → Telegram and paste the token. Customers can then message your bot and agents reply from Bitrix24, with chat history saved to the CRM.
Yes. Twilio is available as a built-in SMS provider in the Sales center, and as one of the documented ways to connect WhatsApp.
Yes, through an SMS provider that complies with India's DLT rules. Most Indian gateways need a marketplace app or a custom connector registered with Bitrix24's messageservice API, with DLT templates mapped to your automation.
Yes. Bitrix24's REST API lets a developer register an SMS provider (messageservice.sender.add), after which it can be used from CRM records and automation rules like a built-in provider.
The native Telegram channel works with one-on-one bot chats; Bitrix24 recommends disabling groups for the bot.
Marketplace apps change often; verified 6 October 2026.
Tell us which channels and countries you message. We'll set up what's native and build the connector for the rest — including DLT-compliant SMS for India.