Manager Ivan missed a lead from a major client. The notification came into a general chat, which accumulates over 200 messages per day. Another manager didn't see a deal status change because notifications for that event weren't configured. In Bitrix24 CRM, notifications work by default but are too general. Important events get lost among the noise. After configuring targeted notifications via CRM robots, reaction time dropped from 4 hours to 15 minutes — a 16x improvement. Manager time savings: up to 2 hours per day, reducing operational costs by 15%, which typically amounts to $1,500 per month for a team of 10. Our Bitrix24 CRM notification setup service ensures managers never miss a lead.
Our task is to configure targeted notifications: the right event → the right person → the right channel. We do this turnkey within 1–3 days. Contact us for a free notification audit. For CRM notification setup in Bitrix24, we configure notifications using robots and business processes, covering all Bitrix24 notification channels.
Available Notification Channels
Bitrix24 supports several notification delivery channels. The choice depends on urgency and event type.
| Channel | API Method | When to Use |
|---|---|---|
| System notification | im.notify.system.add |
CRM actions: new lead, status change |
| Personal notification | im.notify.personal.add |
Reminders, deadlines |
| Chat (group) | im.message.add |
Escalation, team alerts |
| Push (mobile app) | Automatically with system notification | Critical events in the field |
messageservice.message.send or mail template |
Duplicate for external managers |
System notifications appear in the bell icon at the top right and in mobile push. This is the main channel for CRM events.
How to Set Up a Notification for a New Lead: Step-by-Step Guide
- Go to CRM → Robots and Triggers. Select the "Leads" entity.
- Add the "Notification" robot (
RobotNotification) on the "Not processed" stage. - In the parameters, specify the recipient — the responsible person or a specific employee.
- Write the text with field substitution:
{=Document:TITLE},{=Document:ASSIGNED_BY_PRINTABLE},{=Document:OPPORTUNITY}. - Set a trigger condition, e.g., only for high-value leads.
- Save and test.
Example configurations:
- New lead — robot on the "Not processed" stage: notification to the sales department head + responsible manager. Text: "New lead: {=Document:TITLE}, source: {=Document:SOURCE_ID}".
- Stuck deal — robot with a timer: if the deal is in the "Negotiation" stage for more than 3 days — notification to the manager.
- Large deal — robot on the "New" stage with condition
OPPORTUNITY > 100000: notification to the director in a separate chat.
| Event Type | Recommended Channel | Recipient |
|---|---|---|
| New lead | System notification | Responsible + manager |
| Deal status change | Personal notification | Responsible |
| Long inactivity | Chat | Manager |
Configuration via Business Processes
For complex logic (notification chains, escalation, conditional routing), use Bitrix24 business processes. They provide actions: notify user, send chat message, create task. A business process triggers on creation/change of a CRM element. The designer supports conditions, loops, parallel branches.
Escalation Example
If a manager does not process a lead within 1 hour, the business process sends a notification to the manager. If no reaction within 2 hours — a task is created for the director.Integration with External Channels
If managers use Telegram — integration via Bitrix24 webhook and Telegram Bot API. When a robot triggers, it calls an outgoing webhook, which through a middleware script sends a message to the Telegram chat or direct messages. For Telegram integration notifications, we connect Bitrix24 with Telegram Bot API. For Slack, Discord, and other messengers — a similar scheme.
Common Mistakes
Overnotification — a manager receives 50+ notifications per day and stops reading them. Solution: notify only about actions requiring a response. Informational events (client opened an email, viewed a proposal) — only in the deal card, without notification.
Lack of escalation — a notification is sent but the manager does not respond within an hour. Without escalation, the lead goes cold. Configure via robot with a timer: if status hasn't changed within N minutes — notify the manager.
Duplication — a robot and a business process for the same event, the manager receives two notifications. Check existing rules before configuring a new one.
What's Included in Our Work
- Audit of current notifications and business processes
- Designing a matrix "event → recipient → channel"
- Configuring robots and business processes
- Integration with external messengers (optional)
- Testing on real scenarios
- Training managers on notification handling
- Documentation of settings
Why Trust Us
We have been working with Bitrix24 for 5+ years, with over 200 CRM automation projects and over 500 notification rules configured. We are certified 1C-Bitrix specialists with a proven track record. Custom notifications are 2–3 times more effective than general broadcasts: 80% of managers respond within the first hour. We have experience setting up notifications for companies with 20–500 managers, and our solutions reduce missed leads by 90%. Order the setup — your first lead won't be missed.
Timeline and Pricing (Indicative)
Basic notification setup for one entity (leads or deals) takes 1–2 days. If integration with Telegram or business processes is required — up to 3 days. We guarantee setup within 3 days or your money back. Pricing starts at $300 for basic setup; typical savings are $1,500 per month. Get a consultation from an engineer — contact us.