The bell in the top bar shows unread notifications, capped at 9+. Notifications are in-app only — nothing here is emailed or sent to WhatsApp.
What triggers one
- A lead is assigned to you by someone else. Assigning a lead to yourself does not notify you.
- A task is assigned to you by someone else, same rule.
- A task you own is falling due, if the scheduled reminder job is running.
- A lead you own has gone uncontacted past the threshold.
- A lead you own was marked Won by someone else — because finding out from the pipeline board days later is a poor way to learn a deal closed.
- Traffic quality warnings, where enabled.
The rule that keeps this usable
Automated notifications are deduplicated to at most one per item per day. A lead that has been uncontacted for a week generates one alert, not ninety-six.
This is the most important design decision in the feature. A sweep that re-raises the same alert every run produces a bell with dozens of copies of "Lead X is waiting" by the end of the day — at which point the user switches notifications off permanently, and every other alert in the product dies with it. One per item per day is the entire constraint the system is built around.
Why nothing is emailed. Email notifications from a CRM are the fastest route to being filtered into a folder nobody opens, and once that happens they are worse than useless because you believe people are being told. In-app only was a deliberate choice, not a missing feature.
Reading and clearing
Click the bell for the list. Clicking a notification marks it read and takes you to whatever it is about — the lead, the task. There is a mark-all-read action for when the list has got away from you.
Read notifications are kept rather than deleted, so the bell is also a record of what happened.
If the bell never shows anything
Three usual causes, in order of likelihood:
- Nothing is assigned to you. Most notifications are triggered by ownership. A user with no assigned leads or tasks legitimately receives almost nothing.
- Everyone assigns work to themselves. Self-assignment never notifies, by design. On a small team where each person creates and owns their own leads, this alone explains a silent bell.
- The scheduled job is not running. The two automated alerts — tasks due and uncontacted leads — depend on a cron job. Assignment notifications fire immediately and do not, so if you get those but never the automated ones, that is the cause.
If it shows too much
Usually one person reassigning leads in bulk. Each reassignment is a genuine event and each one notifies. Nothing is misfiring, but it is worth knowing before concluding the system is broken.
Notifications are not the safety net
My Day is. Notifications are interruptions — they are good at telling you something changed, and bad at telling you what to do next, because they arrive in the order things happened rather than the order things matter.
A team that works from My Day and treats the bell as secondary misses far less than one relying on the bell alone.