Threshold vs Slack & Intercom
Most builders run one tool for the team (Slack) and another for buyers (a support inbox like Intercom), and then have no shared record of either once a thread scrolls away. Threshold takes a different aim: put internal team chat and buyer messaging in one system, and file every message on the home it belongs to. Slack and Intercom are deep, best-of-breed products; Threshold trades some of that breadth for a single connected record.
Quick answer
Threshold includes internal team chat (channels, DMs, @mentions) and buyer-to-team messaging with read receipts, typing indicators, attachments, emoji reactions, on-demand translation, and message editing, and stores every conversation on the buyer's home record. A Slack + Intercom stack offers a larger app ecosystem and deeper standalone support tooling, but keeps those conversations in separate systems from your buyer records.
| Threshold | Slack + Intercom | |
|---|---|---|
| Buyer ↔ team messaging tied to the home record | Separate support inbox | |
| Internal team chat, channels & DMs | Slack | |
| @mentions & per-user notifications | ||
| Read receipts, including per-user in group rooms | Varies by plan | |
| Typing indicators | ||
| Attachments (photos, iPhone HEIC, PDF, Excel, text) | ||
| Emoji reactions & picker | ||
| On-demand translation for multilingual buyers | Add-on / limited | |
| Edit a sent message with an “edited” label | ||
| Every message stored on the buyer's home record | ||
| One system, no separate chat + support subscriptions | ||
| Large third-party app & bot ecosystem | Builder-focused |
Threshold's messaging is built for a builder's buyer and team workflow, not as a general team-chat or marketing-support platform. For company-wide chat across many departments or a full support marketing suite, dedicated tools go deeper.
Buyers message your team from inside their home portal, and the thread lives on their record next to their configuration, contract, and change orders. Your team gets its own internal chat, shared rooms and one-to-one DMs, with @mentions, per-user notifications, read receipts (including who read what in a group room), and typing indicators. Every surface supports attachments, photos, iPhone HEIC files, PDFs, spreadsheets and text, emoji reactions, message editing with an "edited" label, and on-demand translation so a multilingual buyer and an English-speaking sales team can read each other cleanly. Because it's one system, none of it has to be exported or reconciled later, and it carries the same experience into the mobile app.
If you need company-wide chat spanning every department, a huge library of Slack apps and bots, voice and video huddles, or a full marketing and support suite with ticketing, help-center articles, and outbound campaigns, those platforms are built for exactly that depth. Some builders keep Slack for broad internal operations and let Threshold own the buyer-facing and deal-specific conversations, that's a perfectly reasonable split.
Bottom line
Choose Slack and Intercom when breadth of chat and support tooling is the point. Choose Threshold when you want buyer and team messaging to be one connected part of the home record, no extra subscriptions, no scattered inboxes, and every conversation already filed with the deal it belongs to.
We'll load one of your floor plans and walk you through the buyer journey end to end, no slide deck.
Request a Demo