How to never miss a customer reply buried in a Slack thread
Teams trying to catch replies in old threads deploy real workarounds. Manual scrolling (works for two weeks, then people get busy). Reminder bots (ends up 30 reminders per week, half already resolved). Emoji reactions (decentralized, easily forgotten). I watched a support manager build a spreadsheet and update it every morning. She gave up on it after a month.
None of these work. They're friction on a broken system.
The real solution is to stop treating this as a team discipline problem and treat it as a system problem. You need automated, reliable notification for customer follow-ups in threads. You need the system to tell you what changed, not rely on people to remember to look.
That's what smart notifications do. They're built into BackReply. Here's the mechanism: when a customer replies in Intercom to a conversation that's been sitting, BackReply detects it and posts a compact alert in your main Slack channel. You see it. You act on it. Done.
The system comes with three notification modes. Choose the right one and it handles the problem automatically.
Quiet mode posts no notifications. Skip this.
Responsive mode is what I recommend. BackReply nudges on a turn change (customer now waiting on you), a reopened conversation, a customer returning after a day-plus idle, or a wait past the idle threshold you set (default 1 hour). Tuned for action, not noise.
Attentive mode posts every customer message. For enterprise or sales support where single deals matter. It's noisy. Most teams find it overwhelming.
Pick based on volume and SLA. Around 20 tickets daily on a 2-hour SLA: start Responsive. 20-50 tickets on a 4-hour SLA: Responsive with a 30-minute idle threshold. Enterprise or high-stakes deal support: Attentive. Early-stage small team: start Responsive and adjust up if needed.
Setup takes minutes. Connect BackReply. Configure Smart Notifications. Pick mode. The system watches Intercom automatically.
Every workaround I listed decays. Scrolling stops the first busy week. Reminder bots get tuned out. Emoji systems die quietly. The automated nudge is the only version I've seen still working months in, because nobody has to remember anything.
It's also customer-aware. Threads hold context. The main channel holds alerts. When something changes, the alert surfaces. When you need details, the thread is there.
Start with Responsive, run it for a week, and count the follow-ups you catch that would have sat invisible. Most teams stay there. The smart notifications page has the full trigger list.