How manual SMS sending kills conversion
Imagine an online store loses 20% of orders at the delivery stage — the courier can't reach the customer, and automatic SMS isn't set up. Managers manually copy numbers, open the provider's web interface, type messages. One message takes 3 minutes, no control, no statistics. The client doesn't get a notification — the order returns.
We solve this problem at the API level: integrate an SMS provider via the REST method messageservice.sender.add, develop a PHP handler, and configure CRM robots. After implementation, our clients see a 15–20% reduction in returns and up to 50% time savings for managers. Our team has over 10 years of Bitrix24 integration experience.
How to connect an SMS provider to Bitrix24?
SMS in Bitrix24 work through the messageservice module. It's a unified interface: CRM passes the text and recipient number to a registered provider via REST API. For Russian services (SMS.ru, SMSC, MTS Exolve) we register a HANDLER — a script URL that receives requests from Bitrix24 and sends them to the provider's API. Important: the sender name (alphanumeric sender ID) must be registered separately with the operator — otherwise the client will see an unknown number instead of the company name.
Minimal setup:
- Register the provider:
messageservice.sender.add with parameters CODE, TYPE=SMS, HANDLER.
- Create a PHP handler: form the XML/JSON for the provider, send the request, return the response.
- Check permissions: the user must have the right to send SMS.
After registration, the provider appears in the list of SMS services in CRM. Average delivery speed through a Russian provider is 1–3 seconds, with a 99% delivery rate (with correct callback).
Comparison of popular SMS providers for Bitrix24
| Provider |
Connection type |
Callback statuses |
Features |
| SMS.ru |
REST API + ready application |
Yes |
Low price, fast registration |
| SMSC |
REST API, HTTP |
Yes |
Supports mass campaigns |
| MTS Exolve |
REST API via messaging |
Yes |
High speed, delivery under 1 s |
| Twilio |
Built-in provider |
Yes |
International numbers, 1.5x cost |
SMS.ru processes requests 2 times faster than Twilio on Russian numbers, with 30% lower per-message cost. For mass campaigns, SMSC offers flexible tariffs and a convenient API.
Automatic SMS from CRM: robots and triggers
The main scenario is CRM robots. Create a robot on the 'Stage changed' event and add the 'Send SMS' action. For example:
- Deal on 'Awaiting payment' stage → SMS with payment link and amount.
- Order shipped → SMS with tracking number. REST API
- Missed call → SMS with promise to call back in 15 minutes.
Text templates support field substitutions: #CONTACT_NAME#, #DEAL_TITLE#, custom fields. We help set up a chain of 3–5 robots for different scenarios.
Additionally, through CRM marketing, you can launch mass campaigns by segments: filter contacts that consent to advertising, create an SMS campaign, select a provider, and run it. Bitrix24 sends messages in bulk and shows statistics: sent, delivered, errors.
Why it's important to set up delivery status reception?
Without callback, Bitrix24 considers the SMS sent even if it didn't arrive. We configure a handler that receives statuses from the provider and updates the record via messageservice.sender.update. As a result, you see the real picture: delivered, not delivered, in queue. Our clients get transparent statistics and can react to problems in time.
Typical problems during SMS integration and their solutions
| Problem |
Cause |
Solution |
| SMS not sending, error in logs |
Incorrect HANDLER or API key |
Check handler URL and provider keys |
| Delivery statuses not coming in |
Callback not configured on provider side |
Add callback URL in provider settings |
| Failure during mass campaign |
Exceeding provider API limits |
Agents with pauses between requests |
| Bitrix24 doesn't see the provider |
Error in provider registration code |
Check messageservice.sender.add and permissions |
What's included in the SMS campaign setup
- Audit of current CRM and SMS usage scenarios
- Provider registration via REST API
- PHP handler development (Bitrix Framework)
- Callback configuration for delivery statuses
- CRM robot configuration (up to 5 scenarios)
- Template creation with field substitutions
- Mass campaign setup via CRM marketing
- Testing: manual send, robot, callback
- Documentation and staff training
- 30-day performance guarantee after delivery
Contact us for a consultation — we'll assess your project and propose the optimal solution. Get a cost estimate and timeline tailored to your CRM.
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
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
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
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- 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.
