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.
Read moreHere's what happens in support operations that use Slack as their command center: a customer writes in. Someone on the team posts the message to a shared channel. The team responds. Context is shared. The issue is solved. Everyone feels good about it. Then, three days later, the
Read moreI've watched this unfold a dozen times: a founder realizes they need visibility into customer feedback. A finance person gets pulled into billing disputes. A product manager wants to catch feature requests before support summarizes them. Each person needs access. Each seat costs money. This is the collaboration
Read moreOne of the most frustrating workflows I've seen in support operations is the copy-paste escalation relay. A customer report comes in. Support agent reads it in Intercom. Something in the ticket needs technical investigation. Agent copies the entire conversation. Pastes it into a Slack channel where engineers
Read moreIntercom pricing is straightforward. Essential is $29 per seat per month. Advanced is $85 per seat per month. Expert is $132 per seat per month. Pick your tier, multiply by headcount, and that's your annual cost. A 15-person team on Advanced (which most growing SaaS companies need
Read moreI spent seven years running support operations across three SaaS companies. In that time, I watched teams spend a staggering amount of energy on a single question: who is replying to this? Not the actual reply. The decision about who should write it. Intercom notifications ping into Slack. Someone says
Read moreA customer opens a ticket at 4pm. The message lands in your support Slack channel. An agent sees it and thinks, "I'll handle this in a minute, just finishing something." They switch back to Intercom. The Slack message gets buried under 30 new messages. By the
Read moreIt's 2pm on a Wednesday. A customer message lands in Intercom. It pops up in your support Slack channel. Two agents see it at the same time. Neither knows the other is already typing. Two minutes later, your customer gets two nearly identical responses within 30 seconds of
Read moreIf you're bootstrapped or early-stage, you've probably looked at your Intercom bill and winced. Each support seat costs real money. Each agent you add pushes you closer to a budget conversation with your CFO. So you do what makes sense: you put fewer people in
Read moreIn the previous article, I laid out the core problem: support teams using both Slack and Intercom are bleeding hours to context switching. Now I want to get specific about where those switches happen and put a dollar figure on each one that you can take to your manager. The
Read moreIf your support team uses Slack for internal coordination and Intercom for customer conversations, every reply to a customer follows the same pattern: read the notification in Slack, open Intercom, find the conversation, type the reply, switch back to Slack, repeat. It takes 30 seconds, maybe a minute. It doesn&
Read moreJoin BackReply and start closing the loop between Slack and Intercom.