SMSC SMS Integration with Bitrix24: Setup & Features

Many companies face the problem: SMS notifications from Bitrix24 do not reach all clients — numbers are outdated, messages are lost, and the cost of mailing increases. We solve this by integrating SMSC, one of the oldest SMS aggregators, which offers HLR checks and cascade sending via Viber. We'll break down how to configure the connection via REST API, set up callbacks, and achieve 99% message delivery. Our experience shows that proper integration reduces mailing costs by 30-40% by excluding invalid numbers and using the cheaper Viber channel. For a medium business, savings can amount to tens of thousands of rubles monthly.

How to Register the SMSC Provider in Bitrix24?

To connect SMSC, the messageservice module is used. The provider is registered via the REST method messageservice.sender.add with parameters: CODE="smsc", TYPE="SMS", HANDLER=URL of your handler. The handler accepts a request from Bitrix24, forms a GET request to the SMSC API:

https://smsc.ru/sys/send.php?login=LOGIN&psw=PASSWORD&phones=NUMBER&mes=TEXT&fmt=3&op=1

The parameter fmt=3 — JSON response, op=1 — request delivery status. The handler saves the mapping between Bitrix24 message_id and SMSC id, then returns confirmation. This ensures full tracking of the send. Official SMSC API documentation contains a complete list of parameters.

Why Perform HLR Checks Before Mailing?

HLR (Home Location Register) — a request to the operator that checks the number's activity, identifies the operator and region. SMSC provides HLR via a separate API method:

https://smsc.ru/sys/hlr.php?login=LOGIN&psw=PASSWORD&phones=NUMBER&fmt=3

The response includes status (0=active, 1=unavailable, 2=does not exist), operator and region. In the context of Bitrix24, HLR checking allows:

• Excluding unavailable numbers from bulk mailings, saving budget.
• Automatically determining the operator and region when creating a lead via a business process with an HTTP request. The result is saved in custom fields UF_CRM_OPERATOR and UF_CRM_REGION.

Cascade Sending: SMS + Viber

SMSC supports cascade delivery in a single API call. The logic: the message is sent via Viber; if the recipient hasn't read it within a set time (usually 1-2 hours), an SMS is automatically sent. API parameters:

https://smsc.ru/sys/send.php?login=LOGIN&psw=PASSWORD&phones=NUMBER&mes=TEXT&fmt=3&viber=1&viber_timeout=3600

viber=1 — attempt delivery via Viber, viber_timeout — timeout in seconds before fallback to SMS. Viber messages are usually 1.5-2 times cheaper than SMS, allowing you to reach the maximum number of recipients at minimal cost. In Bitrix24, cascade is configured at the handler level: the CRM robot calls the standard "Send SMS" action, and the handler decides whether to send via Viber with fallback or pure SMS — depending on the message type or segment.

Bulk Sending for Mass Mailings

SMSC accepts up to 100 numbers in a single request (comma-separated). For mass mailings via CRM marketing, this is critical: instead of 10,000 individual requests, the handler groups numbers into batches of 100 and sends 100 requests. The benefit: mailing speed increases by an order of magnitude, and server/API load is minimal. Implementation: the handler accepts requests from Bitrix24 (each is one number), stores them in a queue (Redis, database, file), a cron task every 5-10 seconds picks up to 100 numbers and sends them as a batch. Statuses are mapped back by each message's id.

Callback for Delivery Statuses

SMSC sends status notifications to a specified URL. Configuration is done in the SMSC control panel (section "Settings → Status Handler"). Statuses:

The handler receives id and status, finds the associated Bitrix24 message_id, and updates the status in CRM. Status "22" is especially useful: it shows that the cascade worked and the client received an SMS instead of Viber. This information can be written to a custom contact field — on the next mailing, send SMS directly, bypassing the Viber timeout.

Step-by-Step Handler Setup

1. Create a PHP script on your server that accepts a POST request from Bitrix24 with fields message_id, phone, text.
2. Register the provider via messageservice.sender.add, specifying the script URL as HANDLER.
3. Configure the callback URL in the SMSC control panel for receiving statuses.
4. Test sending a test message from CRM.
5. Configure CRM robots for automatic sending of notifications by stages.

Implementation Timelines

What's Included in the Work

• Registering SMSC as a provider via messageservice.sender.add
• Developing a handler for Bitrix24 requests → SMSC API with cascade and bulk sending support
• Setting up HLR checks on the contact database
• Creating a callback handler for delivery statuses
• Configuring CRM robots for transactional notifications
• Integration with CRM marketing for mass mailings
• Testing all scenarios (SMS, Viber, cascade, HLR)
• Documentation and training

We guarantee stable integration performance. Our team has 10+ years of experience with Bitrix24 and SMS services. We will assess your project and propose the optimal solution. Contact us for a consultation and get stable SMS communication with clients. Leave a request on the website, and we will find a solution for your budget.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.