Setting up manager notifications in CRM Bitrix24
Manager missed incoming lead because notification went to general chat buried under messages. Another manager didn't see deal status change because notifications weren't set up for it. In CRM Bitrix24, notifications work, but by default configured too broadly — critical events drown in information noise.
Task — set up targeted notifications: right event → right person → right channel.
Notification channels in Bitrix24
Bitrix24 supports multiple notification delivery channels:
| 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) | Automatic with system notification | Critical field events |
messageservice.message.send or mail template |
Duplicate for external managers |
System notifications go to bell in top right corner and mobile push. This is primary channel for CRM events.
Setup via CRM robots
Robots — stock automation tool in CRM Bitrix24, doesn't require programming. Configured in CRM → Robots and triggers for each entity (leads, deals, contacts).
"Notification" robot (RobotNotification) sends system notification to specified user or responsible person. Parameters:
- To whom — responsible, manager, specific employee, followers
-
Text — with field placeholders:
{=Document:TITLE},{=Document:ASSIGNED_BY_PRINTABLE},{=Document:OPPORTUNITY} - Trigger condition — funnel stage, field value, user role
Example setups:
-
New lead — robot on "Unprocessed" stage: notification to sales manager and responsible manager. Text: "New lead: {=Document:TITLE}, source: {=Document:SOURCE_ID}".
-
Stuck deal — robot with timer: if deal on "Negotiations" stage for more than 3 days — notify manager. Use "Wait" robot + condition.
-
Large deal — robot on "New" stage with condition
OPPORTUNITY > 100000: notification to director in separate chat.
Setup via business processes
For complex logic (notification chains, escalation, conditional routing) use Bitrix24 business processes. They provide access to actions:
- User notification — like robot, but inside arbitrary workflow
- Send message to chat — for team alerts
- Task — create task as "heavy" notification requiring response
Business process launches on CRM element creation/change. Designer provides conditions, loops, parallel branches.
Integration with external channels
If managers use Telegram — integrate via Bitrix24 webhook (rest/1/xxxx/) and Telegram Bot API. When robot triggers, calls outgoing webhook, which sends message to Telegram chat or private.
For Slack, Discord and other messengers — similar schema via webhooks.
Common setup mistakes
Excessive notifications. Manager gets 50+ notifications per day — stops reading them. Solution: notify only about actions requiring response. Information events (customer opened email, viewed proposal) — only in deal card, without notification.
No escalation. Notification sent, but manager didn't respond in an hour. Without escalation lead cools down. Set up via robot with timer: if status unchanged for N minutes — notify manager.
Duplicates. Robot and business process on same event — manager gets two notifications. Before setting new rule — check existing ones.
Setup takes one working day: audit current rules, design "event → recipient → channel" matrix, configure robots and test on real scenarios.