How to Configure Notifications in kommoCRM: From Built-In Alerts to Exception Control
kommoCRM notifications help managers react to tasks, messages, and events. For sales leaders, the next step is exception control: alerts when a lead has no task, sits idle, or becomes overdue.
CRM notifications should help you react quickly when something important happens, or when something important does not happen. In kommoCRM, notifications can warn you about new leads, task deadlines, incoming messages, and automation events. But there is also a second layer of control: catching exceptions such as leads with no tasks, overdue actions, unanswered inbound requests, or leads stuck in Unsorted.
This article explains how to set up both kinds of alerts, where the built-in options stop, and how LeadsAlarm helps you focus on what matters. It connects directly with the broader topic of how not to lose leads in kommoCRM: notifications are useful only if they help the team react before a lead falls out of the process.
Two kinds of signals: events and exceptions
Most CRM notifications tell you when something happens: a task has been assigned, a lead has moved to a new stage, or a client sends a message. These are important, but they only highlight events that already occurred.
Equally important are situations where something did not happen: no task was created, a lead has been idle for days, a customer’s question went unanswered, or a lead stayed in Unsorted too long. kommoCRM’s standard notifications cover the first group. Exception-control tools such as LeadsAlarm cover the second.
What you can configure with built-in tools
Use kommoCRM’s standard tools for day-to-day reminders. For deeper oversight, add an exception layer.
| Scenario | Built-in tool | Limitation |
|---|---|---|
| Tasks | kommoCRM reminds managers about upcoming tasks through the notification center, push, and email alerts. | Works only if a task exists. The system stays quiet if a manager closes a task and forgets the next one. |
| Push notifications | Mobile and browser push notifications appear when events occur. | Easy to dismiss, and too many alerts become background noise. |
| Notifications can be sent immediately or as a digest. | Slow for urgent sales actions and easy to miss. | |
| Digital pipeline | Automation can create tasks or notifications when a lead reaches a stage. | Works for predefined processes, but does not detect when no action was taken. |
| Salesbot | Scripts can send messages inside kommoCRM or messengers when conditions are met. | Useful for communication and routine flows, but not a full pipeline health monitor. |
| Notification Center | Centralized interface for alerts from kommoCRM and connected services. | Focused on events, not missing next steps or stalled leads. |
Relying only on these mechanisms means you still need to check whether active leads have follow-up tasks and whether inbound requests are sitting idle. Many sales leaders spend time reviewing filters and lists that could be replaced with targeted exception alerts.
Want only critical kommoCRM alerts?
LeadsAlarm monitors exceptions such as leads without tasks, overdue actions, and idle stages, then sends a concise Telegram alert when attention is needed.
Where to turn on notifications
If you only need standard alerts, start with kommoCRM’s own notification settings. Kommo’s help center describes four delivery channels: browser, email, mobile app, and Telegram. You configure them from the user profile, not from a pipeline.
1. Configure personal notification channels
Use this path for each manager:
- Log in to kommoCRM.
- Click the profile picture in the upper-left corner.
- Open Profile.
- Scroll to Notification settings.
- Enable the channels the manager should use.
- Select or clear the event checkboxes.
- Click Save in the upper-right corner.
Channel setup in practice:
- Browser: enable browser notifications in kommoCRM and allow notifications for Kommo in the browser permission prompt.
- Email: use immediate delivery only for important operational events. Use scheduled delivery for reports, billing, and low-urgency summaries.
- Mobile: install the kommoCRM mobile app on iOS or Android, log in, and allow push notifications on the device.
- Telegram: in profile notification settings, add Telegram notifications through Kommo’s notification bot and subscribe by clicking Start.
For sales work, the most useful checkboxes are usually:
- Incoming leads: notify when a new inbound lead arrives in the pipeline.
- Chat messages: notify about new client messages from connected messengers.
- Incoming emails: notify about new email from connected mailboxes.
- Calls: notify about new calls if telephony is connected.
- Errors and other info: notify about integration or automation errors.
- Tasks: before the task: choose a reminder such as 5, 15, 30, or 60 minutes before the deadline.
- Tasks: expired: notify when a task becomes overdue.
- Tasks: assigned to you: notify when a manager receives a new task.
Do not enable every checkbox for every user. For a manager, incoming leads, chat messages, assigned tasks, and overdue tasks are usually enough. For an administrator, errors, billing, activity limits, and scheduled reports may also make sense.
2. Use the Notification Center for routine events
kommoCRM’s Notification Center is opened from the bubble icon in the lower-left part of the interface. It gathers system messages, task notifications, chats, and team messages in one place.
Use it for routine operational visibility:
- New chat messages from connected channels.
- Mentions and internal team messages.
- New or overdue tasks.
- System messages, billing, and integration errors.
There is an important nuance with chat notifications: a chat notification stays visible until the conversation is closed or marked as answered. That is useful for operators, but it is still not the same as SLA control. It shows that a message exists; it does not prove that every lead has a next action.
3. Configure email frequency
Email notifications have more timing options than push channels. In kommoCRM you can send some email notifications immediately or collect them into a scheduled message. Use this split:
- Immediate email: billing-critical issues, integration errors, and reports for owners who are not always inside the CRM.
- Scheduled email: daily summaries and scheduled reports.
- Avoid email for first-response control: a lead can go cold before the email is opened.
For scheduled reports, open the Notification Center, enable Scheduled report, click Setup, and choose which fields should be included in the report. This is useful for retrospective management, not for urgent reaction.
4. Create automatic tasks in Digital Pipeline
Notifications work best when the process always creates tasks. Otherwise there is nothing to remind the manager about.
To create tasks automatically:
- Open Leads.
- Click Automate in the upper-right corner.
- Choose the pipeline stage where the rule should work.
- Click the + button in an empty space under that stage.
- Select Add task.
- Add conditions if the rule should apply only to specific leads, tags, sources, or responsible users.
- Set the execute rule, for example when a new lead is created or when a lead is moved to this stage.
- Set the task deadline: immediately, end of day, in 1 day, in 3 days, end of week, or a custom number of days, hours, and minutes.
- Choose the responsible user. For most sales processes, use the current responsible user of the lead.
- Choose the task type, such as Follow up or Meeting.
- Add a short task comment that tells the manager exactly what to do.
- Save the trigger.
Example rules:
- New inbound lead -> create a “First contact” task -> deadline in 15 minutes -> responsible user is the current lead owner.
- Lead moved to “Proposal sent” -> create a “Follow up on proposal” task -> deadline in 3 days.
- Lead moved to “Awaiting payment” -> create a “Check payment status” task -> deadline end of day.
This turns notifications into a working SLA mechanism. The CRM does not just show events; it creates the next step and then reminds the responsible person before or after the deadline.
5. Use Calendar filters for overdue tasks
For task control, open Calendar from the left menu. Kommo’s task interface has list and board views, search, filters, and saved custom filters.
Useful checks:
- My tasks: what the current manager must do.
- Overdue: tasks that already missed the deadline.
- Responsible users + expired tasks: a saved supervisor filter for managers with overdue work.
- Task type filters: separate calls, meetings, follow-ups, or custom task types.
These filters are good for daily and weekly audits. They still require someone to open the CRM, so they should complement real-time alerts rather than replace them.
6. Use Salesbot for client-facing automation
For more complex scenarios, such as sending an automatic chat message, routing a lead, or qualifying the client before a manager joins, use Salesbot in the Digital Pipeline.
Path:
- Open Leads.
- Go to Automate.
- Click + under the stage.
- Select Salesbot.
- Add conditions and execution rules.
- Choose the bot or create a new one.
- Save the trigger.
Salesbot is strong for customer communication and routine actions. It can answer instantly and reduce first-response time, but it should not be treated as a complete monitoring system for pipeline health.
Official Kommo references: notification setup, advanced notification settings, notification center, digital pipeline triggers, and task management.
Types of notifications and their real use
Task notifications: the foundation
Task notifications are the backbone of kommoCRM alerts. If there is a task, there can be a reminder.
The problem is what happens when there is no task. If a manager finishes a call and does not schedule the next action, the lead quietly disappears from the radar. That is why leads without tasks in kommoCRM should be monitored separately.
Push notifications: speed versus noise
Push notifications are fast and useful for mobile salespeople. They help managers see incoming messages, assignments, and task reminders quickly.
But push notifications are easy to swipe away. If every small event generates a ping, the team develops alert fatigue. For strategic control, push should be a support channel, not the only source of truth.
Email alerts: backup channel
Email notifications are useful for account registration, billing, technical updates, and non-urgent summaries. For sales control, they are usually too slow. By the time an email is opened, the opportunity may already be cold.
Main mistakes when configuring alerts
Mistake 1: alert overload
If you receive too many notifications, your brain starts to ignore them. Ten important alerts per day may be manageable. A hundred mixed alerts will teach people to dismiss everything.
The solution is to limit notifications to critical actions. Each alert should answer: what should someone do now?
Mistake 2: no exception control
Standard notifications tell you when actions are taken, but rarely when they are missing. For example:
- A lead has no task.
- A lead stays in one stage for too long.
- An inbound lead remains unanswered for 15 minutes.
- A task becomes overdue.
You can search for some of these situations manually. For example, filters can find leads without tasks in kommoCRM. But a filter still shows the issue only when someone opens it.
Replace manual pipeline checks with Telegram alerts
LeadsAlarm detects leads without tasks, overdue actions, and idle stages, then sends a concise alert with the context needed to act.
How to level up kommoCRM with exception control
For a head of sales, standard notifications are not enough. You do not need to hear about every routine event; you need to know when the process breaks.
| Scenario | Standard in kommoCRM | External control in Telegram |
|---|---|---|
| Overdue task | Visible in the CRM, reports, or task list. | Instant alert when the deadline is missed. |
| Lead without a task | Usually found through manual filters. | Telegram signal when an active lead has no next action. |
| Stalled lead | Requires manual checking. | Alert after X days in the same stage without movement. |
If you spend half an hour per day checking the pipeline through filters, that is wasted management time. Worse, you can still miss problems until days later. Exception control turns those checks into real-time signals.
Solution: LeadsAlarm
LeadsAlarm sits on top of kommoCRM and focuses only on problems. It does not ping you about every small event; it alerts you when something goes wrong.
Examples:
- An active lead has no next task, so you receive a message and can assign one.
- A task is overdue, so the team sees it immediately rather than at the next meeting.
- A lead is idle in a stage, so you can follow up before the prospect loses interest.
This approach reduces noise: fewer notifications, but each one is tied to a risk of losing money.
How to build a notification system without overload
Start simple. Not every event deserves an alert. Notify managers about tasks, messages, and calls through standard kommoCRM channels. For sales leaders, create a separate layer for exception control: leads without tasks, overdue actions, stalled stages, and unanswered leads.
That way kommoCRM continues to handle routine tracking and communication, while external control helps catch bottlenecks. In practice, this supports the same control system described in Lead Control in kommoCRM.
Turn on critical kommoCRM alerts in Telegram
LeadsAlarm monitors exceptions in your pipeline and helps you react without daily manual CRM reviews.
Conclusion
Setting up basic notifications in kommoCRM takes only a few minutes. That is enough to get started: managers will see tasks, messages, and standard events.
But a systematic sales department needs more than built-in alerts. The CRM should not only notify you about events; it should help you avoid forgotten clients, leads without tasks, and overdue actions. By combining kommoCRM notifications with exception control from LeadsAlarm, you can keep response times fast and the pipeline healthy without drowning in noise.
Frequently asked questions
What can kommoCRM notify users about?
kommoCRM can notify users about tasks, messages, incoming events, automation actions, and selected system updates through interface, mobile, browser, and email channels.
What is the main limitation of built-in notifications?
Built-in notifications mostly react to events that happened. They do not reliably detect exceptions such as leads without tasks or leads that stayed idle too long.
Should sales teams use email notifications for urgent work?
Email is useful as a backup or archive channel, but it is usually too slow for urgent sales control.
How does LeadsAlarm improve notification control?
LeadsAlarm monitors exceptions in kommoCRM and sends concise Telegram alerts when a lead needs attention.
What else to read
Try LeadsAlarm on your kommoCRM pipeline
Setup takes a few minutes: the service starts tracking unassigned leads, leads without tasks, and overdue actions, then sends signals to Telegram.