How to Get Instant Slack or Teams Alerts When Negative Feedback Lands
An unhappy client is recoverable today and gone next month. Here's how to route negative feedback straight into Slack or Teams so you can act while it still counts.

How to Get Instant Slack or Teams Alerts When Negative Feedback Lands
A negative customer rating has a shelf life. Act on it today and it's often a saved relationship - handled well, a client who had a problem can end up more loyal than one who never did. Discover the same rating in a dashboard a month later and it's just a data point explaining why they've gone quiet. The difference between those two outcomes is almost entirely speed.
Which makes the worst possible destination for a bad rating a dashboard that nobody checks between Monday meetings. The fix is to bring the alert to the people, not the people to the alert: push negative feedback straight into the Slack or Teams channel your team already lives in, the moment it arrives. Here's how to set that up in Canopy.
How it works
Canopy can post every incoming feedback response into Slack or Microsoft Teams in real time, and - crucially - you can filter what it posts. You choose whether a channel hears about all responses, positive only, or negative only. That filter is what turns a noisy feed into a useful one: point a channel at negative-only and it stays silent until something genuinely needs saving, so a notification there always means "someone should act."
Setting it up, step by step
1. Connect your channel. In Canopy's settings, connect the Slack or Teams channel you want alerts to go to. Teams and Slack both work the same way, so use whichever your team actually watches.
2. Choose the filter. Set what that channel should receive: all responses, positive only, or negative only. For a rapid-response setup, negative-only is the one that matters - it means every ping is a real prompt to act, with none of the noise of good ratings burying the bad.
3. Point it at the right people. Make sure the channel is one the people who can actually respond are in - a service manager, a team lead, whoever owns client relationships. An alert only helps if it reaches someone who can pick up the phone.
4. Optionally keep a positive channel too. Many MSPs run two: a negative-only channel for rescues, and an all-or-positive channel elsewhere so the team sees the wins roll in. Good ratings are great for morale - they just shouldn't share a channel with the ones that need action.
What to do when one fires
The setup is quick; the habit is what delivers the value. When a negative alert lands, the play is simple and fast: someone reaches out to the client the same day - a genuine "we saw your feedback, tell us what happened, here's how we'll put it right." Speed is the whole point. A client who complains and gets an immediate, attentive response frequently comes away more confident in you than before, because they've now seen that when something goes wrong, you're on it. Left for a week, the same feedback hardens into a reason to leave.
Small setup, outsized return
This is one of the highest-return things you can switch on. It costs a few minutes to connect a channel and pick a filter, and in exchange your team stops finding out about unhappy clients too late. Autotask closes the ticket and Canopy captures how the customer felt - and this alert makes sure the ones who weren't happy reach a human while there's still time to fix it. Retention is usually cheaper than acquisition, and a same-day phone call is about the cheapest retention there is.
Stop guessing. See it in Canopy.
Canopy turns your Autotask data into the answers this article is about — technician scorecards, backlog, CSAT, pipeline and MRR, in one place.
Set up feedback alerts