Customer support seat pricing

Intercom 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 for the features) costs $1,275 per month. That's $15,300 per year just to have people access Intercom.

Here's the tension: that 15-person team doesn't actually need 15 Intercom seats. Three of those people are account executives who jump in when things get heated. Two are engineers who handle technical escalations. Four are marketing and product people who occasionally need to check on customer feedback. The other six are dedicated support staff. So you're paying $1,275 a month for six people who use the platform daily and nine people who touch it a few times a week.

If you paid only for the people who actively use the platform, your bill would be $510 per month. That's a difference of $765 monthly, or $9,180 annually. At a startup with limited margins, that's real money.

This is why I'm seeing teams rethink their Intercom architecture entirely.

The traditional answer was: cut down headcount, have fewer people reply to customers, build a tighter support org. That works if your company is happy with slow escalations and less cross-functional input. Most aren't. You want engineers to be able to jump into customer conversations. You want product managers to see customer feedback firsthand. You want account executives involved in tricky situations. Intercom seats were the tax you paid for that visibility.

But now there's a different option. Many teams are keeping their cross-functional involvement and cutting seats by having non-seat-holding employees reply through a shared account.

Here's how it works: you maintain a few core seats for your dedicated support staff. Your engineers, AEs, and other occasional participants log into Slack instead. When they need to reply to a customer, they write their message in a Slack thread. A tool like BackReply pushes that message to Intercom, where it goes out under a service account (Intercom's Operator) with an attribution line: "Sent by [name] via Slack."

The customer gets the reply. The conversation gets updated in Intercom. The engineer doesn't need a $85 per month seat. The company saves money. The workflow is faster because they never leave Slack.

I know what you're thinking: the attribution isn't as polished as a native Intercom account. Fair point. But here's what matters in practice: customers care that they got a good answer. They don't care whether it came from a named Intercom seat or via a service account. They see the name of who helped them. That's the attribution that matters.

For your dedicated support staff who carry the customer relationship, you should still buy seats. They get full Intercom access, native attribution, and accountability. For everyone else, the service account model works well.

Let me do the math on the team scenario I mentioned earlier.

Fifteen-person team on Advanced: $1,275 monthly, $15,300 annually.

Same team using six Intercom seats for core support staff, nine people replying via a shared account: $510 monthly, $6,120 annually. You save $9,180 per year.

Scale that across your SaaS business. That money moves from a software license to hiring or product investment. For a company with a 5-person support team where two people are part-time or occasional, that's around $2,000 a year at the Advanced tier just from those two seats. Smaller margins on SaaS mean those savings matter.

The collaboration model works best when your tool gives you clear visibility into who said what, when. You need attribution, timestamps, and the ability to track conversations across Slack and Intercom. You also need the replies to land in Intercom automatically, not manually. Copy-pasting defeats the purpose.

This is the conversation I have with ops leaders every month: "You're paying for seats you don't need because your tool doesn't make it easy for people to collaborate without owning a seat." That's changing. Tools are built now to enable this workflow natively.

If you want to see how the shared-account flow holds up in practice, the collaboration page walks through it. And since this whole argument is about pricing, it's fair to check ours too: BackReply's pricing is built on the same idea, plans priced by connected Intercom users, with unlimited Slack collaborators.