One of your reps said it recently, maybe not to you directly: “I’ve got so many notifications I don’t read any of them.”
That’s worth sitting with. Because if your team has stopped reading notifications, the problem isn’t Slack. It’s that everything got the same weight, and when everything is urgent, nothing is.
The mess usually has an enthusiastic origin
Most notification chaos on sales teams doesn’t come from neglect. It usually starts with good intentions and a HubSpot workflows tab.
Deal stage changes, activity reminders, overdue tasks, lead assignments, pipeline thresholds: all firing into Slack. Each one individually defensible. Collectively, a wall of identical pings that your team learns, very quickly, to ignore.
And that’s before you count everything else that’s been connected to Slack. Intercom, Jira, Google Calendar, whatever the team voted to add six months ago and nobody uses anymore. The HubSpot notifications are just the ones you built yourself.
And once the ignore habit forms, it’s hard to break. You can send the most important message of the quarter into that channel and it lands with the same visual weight as a notification that a contact’s job title has been updated in HubSpot.
Save your DMs for when they actually matter
The same logic applies to any bot nudge you’ve set up to chase pipeline updates or prompt follow-ups. A bot reminder is easy to dismiss. A direct message from you asking where something stands is not. That difference matters, because you only get so many of the latter before people start dreading them.
Use reminders for the things that genuinely need a prompt and they’ll land. Run them constantly and they become part of the noise, dismissed along with everything else.
“Does this spark joy?”
Most teams never do this. They add notifications over time and never go back. So go through them. For each one, ask: does someone actually need to know this right now? Not eventually. Not as a nice-to-have. Right now, in the middle of whatever they’re doing.
Most of it won’t survive that question. A deal crossing a significant threshold probably does. A contact’s job title updating in HubSpot probably doesn’t. The things that require action today stay. Everything else gets moved somewhere people check on their own schedule.
What this looks like in practice
Next time a notification lands, stop for a second and ask whether it earns the right to be there.
It sounds like small work compared to closing deals. But the notification environment your team works in determines whether something important actually gets seen or disappears into the feed with everything else. Just because you can automatically create a channel for every deal in the pipeline doesn’t mean you should.