Which HubSpot plans support custom inbox channels?

If you’re trying to get Telegram, SMS, or any other messaging channel into the HubSpot conversations inbox, this is the question that stops most teams halfway through setup. It’s also the one HubSpot buries.

Short answer: you need Sales Hub Professional or Enterprise, or Service Hub Professional or Enterprise. Starter tiers and the free CRM can’t take a custom channel, and no integration can work around that.

Why the plan matters

HubSpot’s conversations inbox comes with a fixed set of built-in channels. Team email, live chat, Facebook Messenger, WhatsApp, a few others. Anything outside that list has to come in through the Conversations API as a custom channel.

That API is the gate. It’s what lets an integration register a channel, publish incoming messages onto a thread, and push your team’s replies back out. HubSpot only opens it up on Professional and Enterprise tiers of Sales Hub and Service Hub.

What makes this confusing is that everything else looks ready. You can create contacts, log activity, and there’s a conversations inbox sitting right there in the nav on cheaper plans. The inbox exists. It just won’t accept a channel it didn’t build itself.

The permission nobody mentions

Plan level is only half the problem. Whoever runs the connection also needs Account Access permission in HubSpot.

This one catches teams where a support lead owns the messaging tools but someone in ops or marketing owns the portal. The support lead has every permission that seems relevant, inbox access, contact editing, workflow rights, and the OAuth step still fails. Account Access is a separate setting, closer to super admin than to anything on the support side.

Worth checking before you book the setup call. In HubSpot: Settings, then Users & Teams, open the user, look under the Account tab.

How to check what you’ve got

Click your account name, top right.
Open Account & Billing.
Look at the subscriptions listed for Sales Hub and Service Hub.

You want to see Professional or Enterprise next to at least one of them. Marketing Hub doesn’t count here, which surprises people. Marketing Hub Enterprise plus Sales Hub Starter still won’t work.

If you’re on Starter, the jump to Professional is a real cost. Be honest with yourself about whether messaging in the CRM justifies it on its own, or whether you’re heading to Professional anyway for other reasons and this is just one more thing it unlocks.

What happens if you try it on the wrong plan

Nothing dramatic. The OAuth flow refuses the scope, or the channel creation call fails, and you get an error. You won’t end up with a half-working inbox that silently drops messages.

Still an annoying way to find out. Checking takes two minutes.

One channel or several

Once you’re on a supported plan, the plan itself doesn’t cap how many custom channels you connect. A Telegram bot, a personal Telegram account, and a Twilio number can all run into the same portal, each pointed wherever it makes sense.

Where they land is up to you, per channel. Plenty of teams send support conversations to a shared Support inbox and sales conversations somewhere separate, so routing and notification rules stay sane. Pricing for the integration follows the channels you connect rather than seats, so a second channel doesn’t mean paying for every user twice.

Before you start

Five things to line up:

Sales Hub or Service Hub, Professional or Enterprise
The connecting user has Account Access
You know which conversations inbox each channel feeds
For SMS, an SMS-capable number in your Twilio account
For a Telegram bot, a BotFather token

With those sorted, connecting a channel takes a few minutes.

If you’re on a supported plan and want to see what the connection looks like end to end, the Telegram bot and Twilio SMS pages cover what actually shows up in HubSpot once a channel is live. The activation guides are the click-by-click version.