Clients rarely read email, but SMS get opened within seconds – open rates for transactional messages reach 95%+. Losing an order due to lack of notification can cause significant losses, while sending an SMS costs pennies. The savings are obvious. For an e-commerce store with 10,000 orders per month, we set up automatic notifications: after implementing SMS payment reminders, overdue invoices dropped by 30%, and profit increased by 5%. Contact us to calculate your scenario.
Connecting an SMS Provider
Bitrix24 does not send SMS directly – you need a provider. Built-in integrations: SMS Aero (direct integration), SMSC, Unisender, SendPulse (via omnichannel module). Any provider with HTTP API can be connected via a custom provider. According to Bitrix24 documentation, registering an alpha-name takes 1–3 business days.
Connection in Settings → Telephony → SMS providers. Enter the API key, sender name (alpha-name), and test sending. Important nuance: the alpha-name must be registered in advance, otherwise SMS will not be delivered.
SMS Aero surpasses SMSC in alpha-name registration speed by 1.5 times, but for large volumes SMSC is more economical due to lower per-message cost.
How to Choose an SMS Provider?
Provider choice depends on volumes and alpha-name requirements. SMS Aero – fast registration, suitable for small businesses. SMSC – cheaper for large batches, but registration takes longer. Unisender is convenient if you already use their email campaigns. For specific needs (custom templates, complex logic), consider integrating via HTTP API – it gives full control.
Setting Up the "Send SMS" Robot
Set up the robot in a few steps:
- Open the pipeline in CRM.
- On the desired stage, add the "Send SMS" robot.
- Select the connected provider.
- Specify the recipient number – use the field
{=Document.PHONE}.
- Write the message text (up to 160 characters for Latin, 70 for Cyrillic). Example:
Your request #{=Document.ID} has been received.
Manager {=Document.ASSIGNED_BY_SHORT_NAME} will call by {=Document.CLOSEDATE:formatDate}.
- Set a delay if needed.
- Add a condition for sending (e.g., deal status ≠ "Paid").
Why Is It Important to Set Sending Conditions?
An SMS reminder about payment logically should be sent not immediately, but after N days. The delay is configured in the robot. Add a condition: send SMS only if the phone is filled in and the deal has not moved to the "Paid" stage. Without this condition, a customer who pays the next day will receive an unnecessary reminder. Condition setup: Add condition → Deal status ≠ "Paid".
🔍 Common Mistake
The phone field in CRM is not filled in. If the contact or deal does not have a number, the robot will not send SMS, but won't report an error. Check that numbers are present, or add a condition `{=Document.PHONE} != ''`.
How to Build a Chain of Multiple SMS?
Based on one pipeline, you can set up a sequence of reminders. For example, payment reminder after 3 days → after 7 → final after 10. Scheme:
- Robot "Send SMS" with a 3-day delay, condition: status = "Invoice sent".
- Robot with a 7-day delay, same condition.
- Robot "Create task" after 10 days – manual work for the manager.
An already scheduled robot cannot be canceled – only if the deal moves to another stage, unsent robots are automatically canceled.
Limitations and SMS Consent
Legislation on SMS mass mailings requires recipient consent. Transactional SMS are a gray area; for marketing, consent is mandatory. Bitrix24 does not have a built-in "SMS consent" field. Solution: a custom checkbox field on the contact or deal, a condition in the robot: send only if {=Document.UF_CRM_SMS_CONSENT} = Y.
Comparison of Popular Providers
| Provider |
Alpha-name Registration |
SMS Cost (Russian numbers) |
Integration with Bitrix24 |
| SMS Aero |
1-2 days |
depends on scope |
direct |
| SMSC |
1-3 days |
depends on scope |
direct |
| Unisender |
2-3 days |
depends on scope |
via omnichannel |
What's Included in the Work
- Analysis of the sales pipeline and selection of SMS scenarios.
- Connecting the SMS provider and registering the alpha-name.
- Setting up robots with conditions and delays.
- Testing sending on real numbers.
- Documentation on settings and training for managers.
Timeline and Cost
| Task |
Time |
| Alpha-name registration with provider |
1–3 days (not dependent on us) |
| Connecting the provider in Bitrix24 |
30 min |
| Setting up robots with SMS for the pipeline |
1–2 hours |
The technical part takes 2–4 hours. The rest is waiting for the provider. Get your project evaluated in one day – just write to us. 10+ years of Bitrix experience: configured SMS notifications for 50+ projects. We guarantee stable operation and post-launch support. Get a consultation from an engineer.
Learn more about connecting providers in the official Bitrix24 documentation.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.