Connect to IntercomGet Alerted for Every Terrible CSAT Rating in Intercom
A 😠 rating in Intercom is not just a data point — it is a customer telling you directly that something went seriously wrong. These conversations deserve immediate human attention, not a queued dashboard review.
Without automated alerts
- 1Open Intercom Reports → Customer satisfaction and filter for 😠 and 🙁 ratings.
- 2Open each dissatisfied conversation manually.
- 3Triage and decide on escalation or follow-up.
The problem: Manual triage happens when you remember to do it. A 😠 rating that sits unseen for six hours is a customer who has had six hours to write a bad review or start a cancellation flow.
With Supportman
Route terrible and bad ratings to a dedicated Slack channel the moment they arrive — assignee, customer, emoji, remark, and a link back to Intercom. No Reports filter, no star thresholds.
- Connect Supportman to your Intercom workspace and Slack (OAuth, two clicks).
- On Pro and above, set a DSAT channel in App Home — 🙁 😠 route there instantly; toggle 😠 alone if you only want the worst cases.
- The alert includes the customer remark, assignee, and a View Conversation link.
Solve it together on the DSAT notification
The alert is not just a ping — it is a Slack message your team can reply to. Context stays in one thread while you decide who owns recovery and what to do next.
- 1A DSAT notification lands in your channel with the assignee, customer, emoji rating, remark, and a View Conversation link.
- 2Reply in the thread — @mention the assignee, team lead, or CS rep who should own recovery and share what you know.
- 3Agree on next steps in Slack first; open Intercom only when someone is ready to reach back out to the customer.
Intercom uses emoji ratings, not stars — Supportman alerts your team in Slack within seconds when a customer leaves a 😠 or 🙁.
Can terrible-rating alerts page an on-call engineer or manager?
Supportman posts to Slack. If you configure Slack to send high-priority notifications for your DSAT channel, it will reach whoever is on call. Direct paging integrations (PagerDuty, etc.) are on the roadmap.
How common are terrible (😠) ratings?
Varies by product and team, but most B2B SaaS support teams see 😠 and 🙁 on a small fraction of rated conversations. Even at low volume, each one deserves attention.