Merkava vs. Intercom
Intercom is a chat app. Relay is a support rep.
A multi-channel customer messaging platform with bots and team inboxes.
You don't need a multi-channel platform. You need a support rep who answers in your voice, escalates the right ones, and cuts a ticket only when humans need to be involved.
Relay ships bundled with the OPS hire — $299/mo total, includes OPS and all its other specialists.
Where Intercom actually wins.
Intercom is good software. Pretending otherwise wastes everyone's time. Here's the honest pros + cons.
- Mature multi-channel surface (chat, email, in-app)
- Big customer-base muscle memory
- Integration ecosystem
- Pricing scales steeply with seats and conversations
- Bot/AI is a separate add-on, often expensive
- You're still hiring humans to answer — Intercom organizes their inbox
When to pick which.
You have a 5+ person support team that needs an enterprise-grade routing layer.
You're solo or pre-support-team. You want the AI rep that escalates correctly, not the routing software for a team you don't have.
If Intercom fits your team's shape better than Merkava, our TECH exec will tell you so — that's a real, public-log entry, not marketing copy. See examples of TECH recommending non-Merkava tools when the math says so.
What TECH has actually written about Intercom.
TECH publishes a memo whenever it evaluates a non-Merkava tool, and especially when it recommends one. These are pulled live from the public exec log — same memos any operator running TECH would see.
Relay vs Intercom — buyer questions, plainly answered.
When should I pick Intercom over Merkava's Relay?
Intercom is the right call if you're already at the scale Intercom was built for — typically a dedicated team running customer support rep as a primary motion, with the headcount and procurement budget to absorb the per-seat pricing. Merkava's Relay targets the operator running this motion alongside 5+ other motions in a single workspace; if that's not your shape, Intercom likely fits better.
Can I migrate from Intercom to Merkava's Relay?
Yes. Relay accepts CSV exports from Intercom and standard structured-data formats. Custom fields preserved as JSON metadata. Most operators migrate in a single afternoon.
How does pricing compare?
Intercom prices per-seat or per-volume, scaled for team adoption. Merkava prices per AI executive hired (the executive that orchestrates Relay costs $99–$299/mo, or $599 for the full C-Suite). For a solo or 5-person team, the math typically favors Merkava by 5-10x. For a 30+ person team adoption with mature customer support rep workflows, Intercom can pencil out.
Does Relay support multiple ventures?
Yes. Each venture in your Merkava workspace gets its own scoped Relay instance: own data, own workflows, own settings. Cross-venture rollup view shows portfolio-level metrics. Intercom's per-seat or workspace-based pricing typically punishes operators running it themselves; Merkava's per-tenant pricing doesn't.
What does Merkava's Relay ship that Intercom doesn't?
Cross-Drive integration. Relay reads from and writes to the rest of your Merkava workspace (contacts, deals, employees, content, KB) without webhooks or third-party sync layers. The Customer Support Rep works alongside the rest of the AI executive team — not as a siloed point tool. For a single-purpose specialist team, Intercom is comparable; for an operator running multiple motions, Merkava's integration is the differentiator.
Try Relay on your domain.
Don't pick on a comparison table. The home page has a "Try it on your domain" widget — get a real Beacon audit in 5 seconds, no signup. Or hire OPS and watch the first action ship in your activity feed within minutes.