What does it cost to connect Telegram or SMS to HubSpot?
The integration fee is the small part. Channel pricing, Twilio pass-through, and the HubSpot plan requirement that catches teams out, added up honestly.
Three separate bills, and only one of them is the integration. Teams evaluating this usually price the connector, sign off on it, and then discover the HubSpot plan requirement halfway through setup. Here is the whole picture before you commit to anything.
1. The integration
TryWired charges per connected channel, not per seat and not per message.
| Channel | First channel | Each additional |
|---|---|---|
| Telegram (bot or personal account) | $40/month | $30/month |
| Twilio SMS | $35/month | $28/month |
A channel is one connected account: one bot, one personal Telegram account, or one Twilio number. Two Telegram bots and one SMS number is $40 plus $30 plus $35, so $105 a month.
Annual billing takes 20% off. Adding users costs nothing, because the price doesn’t track headcount. There’s a 7-day money-back guarantee if the thing doesn’t do what you expected.
2. Twilio, if you use SMS
Twilio bills you directly in your own Twilio account. TryWired adds no markup and takes no cut of message volume.
You pay Twilio for the phone number, roughly a dollar or two a month for a US local number, plus per-message fees that vary by destination country and message type. US A2P traffic also carries brand and campaign registration costs, which are one-off and monthly respectively.
Telegram has no equivalent. There is no per-message cost from Telegram, so a Telegram channel is genuinely just the subscription.
This split matters when you model costs. High SMS volume means a Twilio bill that grows with usage, while the integration fee stays flat. High Telegram volume costs the same as low Telegram volume.
3. HubSpot, and this is the one that surprises people
Custom conversations channels require Sales Hub or Service Hub Professional or Enterprise. Starter tiers and the free CRM cannot accept a custom channel. That is a HubSpot platform limit, and no integration can work around it.
If you’re already on Professional or Enterprise, this line is zero. You’re paying it regardless.
If you’re on Starter, the upgrade to Professional costs more than everything above put together, several times over. So the real question is not what the connector costs. It’s whether you were already planning that upgrade. Teams who were will find this an easy yes. Teams who weren’t should price the upgrade first and decide on that number, because that’s the one that matters.
Check before you buy anything else. It takes a minute in your HubSpot account settings, and it’s the difference between a working setup and a refund request.
Putting it together
A support team on Service Hub Professional connecting one Telegram bot:
- Integration: $40/month
- Telegram: nothing
- HubSpot: already paid
Forty dollars a month, total.
A sales team on Sales Hub Professional running one Twilio number and two personal Telegram accounts:
- Integration: $35 plus $40 plus $30, so $105/month
- Twilio: number rental plus per-message, call it $20 to $60 depending on volume
- HubSpot: already paid
Somewhere around $125 to $165 a month for the whole thing.
A team on Sales Hub Starter wanting the same setup pays the same $125 to $165, plus the upgrade to Professional. That upgrade is the decision, not the connector.
What the price does not include
Per-seat charges do not exist here, so adding your tenth rep costs nothing extra. Neither does per-message pricing on the TryWired side.
Custom work isn’t in the standard price. If the stock Telegram and Twilio connectors don’t cover your workflow, that’s a conversation about scope rather than a plan you can self-serve into.
And there’s no setup fee. Connecting a channel is an OAuth flow and an inbox choice, not an implementation project.
Worth comparing against
Two other costs are easy to forget when you’re deciding.
Doing nothing has a price. Conversations living in someone’s personal Telegram walk out the door when that person does, and nobody else can see the history in the meantime.
Building it yourself has a price too. HubSpot’s Conversations API is public, so a custom channel is buildable. Contact matching, thread continuity, media handling, and duplicate suppression are where the work actually is, and that’s engineering time you keep spending after launch.
Current numbers live on the pricing section of the homepage. If the plan requirement is the open question, which HubSpot plans support custom inbox channels covers how to check yours.