There's a specific kind of friction that shows up the moment a team grows past a handful of people: a manager assigns a task, and then has to separately message the person to make sure they actually saw it. The task existed in the system the whole time — but the system had no way of telling anyone it was there.
Notifications are tied to real events, not a feed to scroll
Assign a task to someone other than yourself, and they're notified immediately. Schedule a meeting for a colleague, or reassign a lead to a different rep, and the same thing happens. These aren't a general activity feed someone has to scroll through hoping to spot what's relevant — each notification is tied to a specific, real event that actually needs that person's attention.
Assigning something to yourself doesn't notify you
A field employee scheduling their own visit, or a manager assigning a task to themselves, doesn't generate a notification — the assigner and the recipient are the same person, so there's nothing to announce. It sounds like a small detail, but it's the difference between notifications that mean something and a stream of noise a team learns to ignore within a week.
One unread count, one place to catch up
Every notification lands in one inbox with a real unread count — on the web dashboard and in the mobile app — so catching up after time away is a matter of opening one list, not reconstructing what happened from separate conversations with each teammate.
The goal isn't more notifications — it's that the ones which matter don't depend on someone remembering to ask.