SMS Broadcast Configuration via Bitrix24
Managers send SMS to clients manually — they copy a phone number, open the provider's web interface, type a message. Three minutes per message, zero control, no connection to CRM. Bitrix24 can send SMS directly from a deal card, contact, or via automation — you need to correctly connect the provider and configure workflows.
messageservice Module
SMS in Bitrix24 work through the messageservice module. It's a unified interface for connecting SMS providers: Bitrix24 doesn't send messages itself, but transfers the text and recipient number to a registered provider via REST API.
By default, in Bitrix24 cloud there are built-in providers available (Bitrix24 SMS Center, Twilio). To work with international services — SMS.ru, SMSC, Twilio — the provider is registered via the messageservice.sender.add method or connected through an app from the Marketplace.
Connecting an SMS Provider
Minimum configuration:
-
Provider registration — via REST method
messageservice.sender.addspecifyCODE,TYPE=SMS,HANDLER(URL of a handler that receives requests from Bitrix24 and forwards them to the provider's API). - Handler — a script that receives the recipient number and message text from Bitrix24, forms a request to the provider's API, and returns the status.
- Sender name — configured on the provider side. The client sees a company name instead of a number (requires alphanumeric sender ID registration with the operator).
After registration, the provider appears in the list of available SMS services in CRM settings.
SMS from CRM: Manual Sending and Automation
Manual sending. The manager opens a contact or deal card, clicks "SMS" in the timeline, selects a provider, enters the message text. The message is sent, and the record is saved in history.
Robots and triggers. The main scenario — automatic SMS sending when a deal stage changes:
- Deal moved to "Awaiting Payment" stage → SMS with payment details and payment link
- Order shipped → SMS with tracking number
- Missed call → SMS "We will call back within 15 minutes"
Configured via CRM robots: action "Send SMS", provider selection, message template with field substitution (#CONTACT_NAME#, #DEAL_TITLE#, custom fields).
CRM marketing. Bulk broadcasts by segment: filter the contact base in the "CRM Marketing → Broadcasts" section, create an SMS broadcast with text, select a provider, launch. Bitrix24 sends messages in batches and shows delivery statistics.
Delivery Statuses
Without feedback from the provider, Bitrix24 doesn't know if the message was delivered. To track statuses, the provider must send a callback to the URL registered in the handler. The messageservice.sender.update method allows you to update the message status: delivered, not delivered, queued.
In practice: if the provider doesn't support callbacks or the handler isn't configured — all SMS in Bitrix24 will have the "Sent" status, even if they actually weren't delivered.
What We Configure
- SMS provider registration via
messageservice.sender.add - Handler for transferring SMS to provider API
- Callback for receiving delivery statuses
- CRM robots for automatic SMS sending by deal stages
- SMS templates with field substitution from CRM
- Bulk broadcasts via CRM marketing
- Testing: sending from a card, robot execution, delivery status receipt