HubSpot Telegram integration: what the most complete setup should cover

A send button is not a complete integration

Many Telegram-to-CRM implementations start with one narrow path: forward a bot message into an inbox, add a composer to a Contact, or fire a notification from a workflow. Each path can be useful, but a team still loses context when the customer moves from a founder's personal DM to a shared deal group, from a human reply to automation, or from onboarding into support.

For teams that want Telegram operations to stay in HubSpot's Inbox, records, Help Desk, and workflow editor, Resonate makes a credible case as the most complete integration by published functional scope. The basis is specific: one app covers bot and personal-account conversations, direct and group chat, manual and automated messaging, customer communication and internal alerts.

Not every team needs every feature; the advantage is continuity. Built by a HubSpot Diamond Solutions Partner, the app works with the Contacts, Deals, Projects, Tickets, owners, properties, and workflow logic already governing the customer relationship. Initial setup uses Resonate and Telegram, but day-to-day messaging and automation happen in HubSpot's native UI.

One support conversation, one HubSpot thread

A customer messages the company's Telegram bot. That chat appears as a conversation in HubSpot Inbox or Help Desk, where an agent replies without opening a separate Telegram console. The first inbound message can match an existing Contact or create a new one and store the Telegram identity on the record. When the channel is connected to Help Desk, it can also open a ticket using the chosen pipeline, stage, priority, and assignment rules. Later messages remain associated with the Contact and conversation history, plus the ticket in Help Desk.

Because Telegram is connected through HubSpot's custom-channel framework, the thread can use the surrounding HubSpot service toolset: routing and ownership, ticket status, snippets, knowledge-base content, meeting links, and eligible AI-assisted replies. Photos, documents, voice notes, and video move in both directions, and inbound attachments can be imported into HubSpot Files.

The same portal can connect several bots—for example, one per brand—and route each bot to its own inbox. Resonate documents per-bot health checks, teammate links, and repair controls, which matters when Telegram is an operational channel rather than a single marketing experiment.

Manual Telegram messaging where the CRM record lives

For sales and customer-success teams, the Contact card is the shortest route from CRM context to a one-to-one message. It shows whether the Contact has started the bot, creates a personal invite link and QR code for an unlinked person, shows recent messages, opens the full history in a slide-in panel, and includes a composer. A sent message mirrors into the linked HubSpot conversation rather than creating a second, disconnected record.

The Telegram Group card extends the same idea to Deals, Projects, Companies, Tickets, and Contacts. A rep can create or link a customer group from the record, see the group's state, and send an update while remaining in HubSpot. Messages synchronize into one conversation thread, with participant names preserved, instead of being copied as isolated notes. Workflows can post stage changes, approvals, status updates, or milestones into the same linked group.

These cards require a channel-connected Support bot and are not added to record layouts automatically. An admin must open HubSpot's record customization, find the app in the Card library, and place each card where the team works. Projects also need to be enabled and available to the app. For complete group capture, the bot must be in the group and Group Privacy must be disabled in BotFather; otherwise Telegram limits the messages the bot can see.

Personal Telegram DMs complete the relationship view

Not every valuable conversation begins with a company bot. Founders, consultants, account managers, and partner teams often speak to customers from their own Telegram accounts. Resonate can connect a personal account through Telegram Business so client DMs flow into HubSpot and replies typed in the HubSpot inbox are delivered as that person. The client does not see or address a support bot.

Personal mode can run beside one or more support bots, covering relationship-led work without giving up the shared CRM history. Teams should still define who owns the connected account, which inbox receives its conversations, and what happens when that person is away. Telegram says connecting a business bot does not require Premium and currently permits one connected business bot per personal account; because platform entitlements change, confirm both points at setup time.

Personal mode is for inbox DMs and replies as the account owner; automated customer sends still use bots.

Five Telegram actions inside HubSpot Workflows

The automation layer lives under Automation → Workflows and uses HubSpot property tokens. The Contact and group actions resolve the Telegram chat already linked to the enrolled CRM record, so an administrator does not normally copy chat IDs into workflow fields. The internal notification action separately resolves a selected teammate, record owner, internal group, or combination of recipients.

The response loop, not another fire-and-forget action

The most distinctive workflow feature is Send Telegram message with buttons. It can present up to three inline choices and pause that Contact's workflow enrollment for up to 24 hours. When the Contact taps, the action returns the button number, label, and value to HubSpot. The same enrollment resumes, allowing the next branch to act on that output immediately. If the window expires, the workflow receives a no-response result rather than remaining stuck.

That supports appointment confirmation, rescheduling, lead qualification, onboarding choices, support triage, renewal decisions, or any other guided path that can be expressed as a few clear choices. Additional button actions can be chained with branches, property updates, tasks, tickets, and follow-up messages to build a complete decision flow in HubSpot's workflow editor.

The limit is important: an arbitrary free-text Telegram reply does not resume this action. This is a button-driven decision bot, not an open-ended AI chatbot. Resonate's dashboard tester can check configuration, delivery, timing, outputs, and raw results against a real Contact or Deal, but a production launch should still test an actual enrollment, every button branch, and the full no-response window.

What the full Telegram customer lifecycle can look like

Imagine a prospect DMs a founder's personal Telegram account. The DM is visible on the Contact in HubSpot. When the opportunity grows, the account owner creates a Telegram group from the Deal so the buyer, sales engineer, and implementation lead share one room. A workflow posts an approval update and later announces Project milestones using live CRM properties.

After launch, the customer messages the support bot. Help Desk creates or matches the Contact, opens a routed ticket, and gives the support agent the history and current account context. A later workflow sends a button-based satisfaction check; the selected answer resumes the enrollment and opens the appropriate follow-up path.

No single feature creates that continuity. It comes from supporting both identities, both conversation shapes, and both ways of working while keeping each interaction attached to the record that owns the next decision. The personal DM, Deal group, and Help Desk conversation remain distinct threads associated through CRM context; the app does not claim to migrate them automatically into one thread.

Setup, requirements, and the boundaries to plan for

Initial setup does not happen entirely inside HubSpot. An administrator installs the app, signs in to Resonate's Telegram dashboard, connects the HubSpot portal through OAuth, and creates a free bot with @BotFather using /newbot. After adding the bot token, the admin chooses Support for Inbox, Help Desk, Contact-card, and group-thread behavior, or Outbound only for supported Contact workflow sends. Personal-account mode is connected separately from Telegram Settings → Business → Chatbots.

For Inbox or Help Desk, the admin connects Telegram as a custom channel and chooses the destination and routing. A Help Desk connection also configures the ticket pipeline, stage, priority, and properties; HubSpot accounts created after 1 April 2024 cannot create tickets from channels connected only to Conversations Inbox. Current HubSpot documentation lists custom channels for eligible Sales Hub or Service Hub Professional and Enterprise accounts; custom Help Desk channels additionally require HubSpot Credits. Personal, Contact-card, and CRM-group conversations need an eligible Sales or Service Hub Professional-or-higher inbox; Contact-card and group conversations additionally require a channel-connected Support bot. Workflow actions need a Professional or Enterprise HubSpot product with workflow access, but Contact workflow messages and employee alerts do not require a Help Desk inbox. All capabilities require an active Resonate trial or subscription, and seats and advanced service features remain subject to the portal's HubSpot entitlements.

A Telegram bot cannot initiate a private conversation. The person must open that specific bot and tap Start or message it first. The Contact card's invite link and QR code can bind the chat to the intended record; a phone number shared in the chat that matches the Contact, or a Telegram ID already stored on that record, can also link it. This is an opt-in channel, not a cold-outreach workaround.

• Protect the BotFather token like a password and give each bot a recognizable name and welcome message.
• Add the Contact and Telegram Group cards to the exact record layouts used by the team.
• Use a real Contact, Deal, and Project to test identity matching, permissions, routing, files, and property-token rendering.
• Check Group Privacy, bot membership, and Project access before relying on two-way group capture.
• Give photo and file actions a publicly accessible URL and define a fallback for missing chats, groups, or files.
• Verify that internal alerts reach only the intended employee or group and never reuse a customer action for operational notes.

Pricing and who should consider it

At publication, Resonate lists one all-inclusive plan at $49 per month or $490 per year, with a 14-day trial that does not require a credit card. The plan includes all four capability areas, five workflow actions, two CRM cards, and multiple bots and brands. Pricing and platform requirements can change: use the product and Marketplace pages for current pricing, and cross-check entitlements against current Resonate, HubSpot, and Telegram documentation because Marketplace requirement copy can lag platform changes.

A team that only needs one one-way alert may be better served by a simple webhook. A team seeking unsolicited Telegram outreach will run into Telegram's opt-in rule regardless of integration. The case for Resonate is strongest when Telegram is already part of support, sales, onboarding, delivery, or account management and HubSpot needs to remain the shared operating record.

The bottom line

Resonate's Telegram Integration is built around conversation continuity rather than a single messaging trick. It supports personal and bot identities, DMs and groups, manual and automated work, customer and employee messages, and the CRM objects that connect them. For HubSpot teams that need all of those paths, its published feature set is unusually broad.

The boundaries are sensible and should be part of the rollout: bots require opt-in, cards require setup, full group capture requires the right privacy setting, HubSpot plans govern the available surfaces, and workflow replies are button-driven. Within those boundaries, the app covers the customer conversation from first Telegram contact through Deal or Project collaboration, automation, and support.