Why are my Telegram messages not showing up in HubSpot?
The usual causes, in the order worth checking: plan tier, permissions, which inbox the channel points at, bot privacy mode, and who messaged first.
Nine times out of ten it’s one of five things, and the first two are settings in HubSpot rather than anything to do with Telegram. Work down the list in order, because the early ones invalidate the later ones.
1. Your HubSpot plan can’t accept a custom channel
Custom conversations channels need Sales Hub or Service Hub Professional or Enterprise. On Starter or the free CRM, the channel cannot be created at all, and no integration can work around it.
Check in HubSpot under Settings, then Account Management, then Subscriptions. You want Professional or Enterprise next to Sales Hub or Service Hub specifically. Marketing Hub Enterprise plus Sales Hub Starter still won’t work, because it’s the wrong hub.
If this is the problem, nothing further down the list will fix it.
2. The person who connected it lacked Account Access
Whoever runs the connection needs Account Access permission in HubSpot. Without it the OAuth step can appear to complete while the channel never actually registers.
The symptom is distinctive: setup looked fine, no error appeared, and no channel shows up in the inbox settings afterwards. If that matches, have an admin reconnect it.
3. The channel points at a different inbox
Each connected Telegram account routes to one specific conversations inbox. If your team is watching the main support inbox and the channel was pointed somewhere else during setup, the messages are arriving perfectly well somewhere nobody is looking.
Open HubSpot’s Inbox settings and check which inbox the channel is assigned to. This is easily the most common false alarm, and it’s the fastest to rule out.
4. Bot privacy mode is swallowing group messages
This one only affects bots in group chats, and it catches almost everyone once.
By default, Telegram bots run with privacy mode on. In a group, the bot only receives messages that directly address it: replies to the bot, and messages containing a slash command or an @mention of the bot. Ordinary group chatter is never delivered to the bot at all, so there is nothing for the integration to forward.
Direct messages to the bot are unaffected. If one-to-one chats appear in HubSpot but group conversations don’t, this is your answer.
Fix it in Telegram, not in HubSpot. Message @BotFather, send /mybots, pick your bot, open Bot Settings, then Group Privacy, and turn it off. Then remove the bot from the group and add it back, because the change only applies from the point it rejoins.
5. The customer never messaged first
Telegram is reply-based. A bot cannot open a conversation with someone who has never contacted it, and that is Telegram’s rule rather than a limitation of any integration.
If you’re testing and nothing arrives, confirm the test account actually sent a message to the bot or the connected personal account first. Sending from HubSpot into silence won’t create a thread.
Still nothing?
A few less common causes, roughly in order of likelihood.
The bot token was regenerated. If anyone sent /revoke to BotFather after setup, the old token stopped working and the channel needs reconnecting with the new one.
A personal Telegram account got signed out. Telegram sessions can end, whether from a security prompt, a password change, or someone clearing active sessions in the app. Reconnect it.
The right contact exists but you’re looking at the wrong record. Telegram matches on username or user ID, so a customer with no email or phone on file gets a contact created from their Telegram identity. The conversation is logged, just against a record you might not recognise at a glance.
And a busy group chat can bury things. If you pointed a talkative group at your main support queue, the messages are all there, they’re just competing with everything else. Point noisy groups at their own inbox.
The order matters
Plan, then permission, then inbox, then privacy mode, then who messaged first. Teams tend to start at the Telegram end because that’s the unfamiliar half, and then spend an hour on bot settings when the account was on Starter the whole time.
The activation guide covers the connection step by step, and which HubSpot plans support custom inbox channels goes deeper on the first two items.