Most support teams run intercom slack automation to route customer conversations, flag high-value accounts, and keep sales or account managers in the loop without forcing everyone to live in Intercom. The goal is to give the right context to the right people in Slack, where they already work, without adding noise or manual copy-paste.
What people usually automate here
- When a conversation is tagged "urgent" or "enterprise" in Intercom, post the message text, customer email, and conversation URL to a dedicated Slack channel like #support-escalations
- When a lead's Intercom profile hits a lifecycle stage (e.g., "trial_started" or "qualified"), send their name, company, and ARR estimate to #sales-handoffs
- When a teammate assigns a conversation to themselves in Intercom, notify their personal Slack DM or a team channel with the customer's company name and last interaction date
- When a specific conversation tag gets added (e.g., "feature_request", "churn_risk"), post a summary to #product-feedback with a button linking back to the Intercom thread
- When a customer replies after 48+ hours of silence, ping the assigned CSM in Slack with the conversation history and a one-click link to respond
Off-the-shelf vs custom-built
Zapier and Make both offer Intercom-to-Slack templates that work fine for a single trigger and a single Slack message. If you want "new conversation → post to #support," a template does the job in ten minutes and costs you one task per conversation.
The ceiling appears fast. Intercom sends a lot of events—every message, tag change, assignment, and close. If you run multiple Zaps filtering on different tags or lead attributes, you burn through a 2,000-event/mo Zapier plan in days. Make's 10,000 operations sounds generous until you realize every filter, lookup, and Slack post counts separately. You also hit rate limits: Slack's tier-2 limit is 20 messages per minute per channel, so a burst of 50 urgent chats can bottleneck or drop messages.
A custom build costs more upfront but runs on your own infrastructure. You handle webhook retries, batch notifications into threaded summaries instead of spamming 50 individual posts, and add conditional logic like "only notify if the customer's MRR > $500 and the tag is 'churn_risk'." You also dodge per-task pricing—once it's deployed, volume is nearly free.
Where custom builds beat templates
Imagine your support team uses Intercom tags to triage: "billing," "bug," "feature_request," "enterprise." You want each tag to route to a different Slack channel, but only if the conversation is unassigned and the customer sent the most recent message (not an internal note). You also want to suppress duplicate notifications if someone re-tags within five minutes.
A Zapier template would require five separate Zaps, each with multi-step filters checking assignment status, last message sender, and timestamp. Every incoming Intercom event fires all five Zaps to evaluate filters, burning tasks even when conditions fail. If two tags get added in quick succession, both Zaps fire and you get duplicate posts. Suppressing duplicates requires a lookup table (another task per check) or a delay step that makes notifications slower. The whole setup costs 200–300 tasks per day for a busy queue, and debugging which Zap failed is a nightmare.
A custom build listens to one Intercom webhook, checks all conditions in-memory, writes a simple five-minute cache to Redis or a local dictionary, and posts once to the correct channel. If Slack rate-limits the post, it queues the retry. If the customer updates their message, it edits the existing Slack thread instead of double-posting. Total cost after deployment: server time, maybe $15/month.
Ready to map your version?
If you're juggling multiple Intercom tags, user segments, or team routing rules, the template approach turns into a per-task treadmill. Run your workflow through the Opportunity Scanner to see volume estimates and whether a custom build pays off in three months—or book a scoping call if you already know the math works and want a fixed quote.