How to Deploy Intercom Fin on Telegram

Telegram is a busy support channel, and most businesses need AI backup to manage it without issues. In Intercom’s case, that AI is Fin.

But does Fin AI work on Telegram? If you check Intercom's documented channel list, the answer is no. However, that’s not the only way.

Intercom doesn’t support Telegram natively, but it supports it through integration.

Connecting Intercom Fin to Telegram means you need to look for an integration tool, like Octopods. Then, you’ll start getting Telegram messages inside Intercom, and Fin will reply to them like normal conversations.

In this article, we walk you through the setup steps to connect Telegram and use Fin as your Telegram AI agent. That includes tuning Fin’s tone and handover and what limitations you might meet.

Why Fin doesn't cover Telegram natively

Fin doesn't cover Telegram natively because Intercom hasn't built a first-party Telegram connection for it to plug into. To deploy Fin on Telegram, you'll have to connect Intercom and Telegram through a third-party integration first.

Where Fin is officially documented to work

Intercom's own documentation lists a specific set of channels for Fin:

• Messenger
• Email
• WhatsApp
• SMS
• Facebook
• Instagram
• Voice, Slack, and Discord, documented separately

Telegram isn't part of that lineup. You can see the full breakdown of where Fin works here.

What this actually means for you

Fin answers whatever shows up in your Intercom inbox as a conversation. It doesn't care where that conversation originated. So, you only need to get Telegram messages into Intercom as conversations.

Why Intercom doesn’t support Telegram natively

It’s a matter of where Intercom has focused its engineering time. Building and maintaining a native channel connection takes real work, and Intercom has prioritized the channels with the widest business adoption first.

Why Telegram is different from other channels

Telegram brings an extra obstacle that WhatsApp, Facebook, and Instagram don't have.

Those three all let a business connect through an official business account model. On the other hand, Telegram is bot-based, so there's no such thing as a "business account" you can register and connect directly. You can't send or receive a single Telegram message as a business without creating a bot first.

That one detail shapes everything about how Telegram gets connected to Intercom, right down to how the setup process works. The Telegram and Intercom integration guide walks through exactly how that connection comes together.

What you need before you start

To get Intercom Fin on Telegram, you need to do a few things on both Intercom and Telegram.

Here’s what you need to do.

On the Intercom side:

• Create an Intercom workspace and enable Fin.
• Create content in the Knowledge Hub that's good enough for Fin to use.
• Subscribe to a plan that gives you access to Workflows

On the Telegram side:

• Create a Telegram account.
• Create a bot through @BotFather using the /newbot command.
• Get the bot's HTTP API token from BotFather.
• Create an Octopods workspace with admin access to your Octopods workspace.

One clarification that comes up constantly: you need one channel connection per bot, not per user or per conversation. That means a single bot handling hundreds of customers still counts as just one connection, so you don't need to worry about scaling your setup as your Telegram volume grows.

How to connect Telegram to Fin using Octopods

Here are the steps you need to follow to set up Intercom Fin on Telegram through Octopods.

1. Create the bot in BotFather

To create a bot in BotFather, you need to message @BotFather on Telegram, send the /newbot command, and follow the prompts. BotFather gives you back an HTTP API token in this format: a numeric ID, a colon, then a long string of letters and numbers.

Keep it because you’ll need it later when connecting your Telegram bot to Octopods.

2. Connect it to Intercom

Paste that token into Octopods to link your bot to your Intercom workspace. From that point on, every message a customer sends to your bot creates a new conversation in your Intercom inbox, just like email or live chat.

3. Confirm the round trip manually first

Before Fin gets involved, test the connection yourself:

• Message your own bot from Telegram
• Check the conversation appears in your Intercom inbox
• Reply from Intercom
• Confirm your reply arrives back in Telegram

This isolates any connection issues from any Fin issues, so you know exactly where to look if something goes wrong later.

4. Point Fin at those conversations

Telegram connects through Octopods rather than a first-party Intercom channel, so these conversations arrive as API conversations. Fin only answers API conversations through a Workflow, which means Simple Deploy won't cover Telegram on its own. You'll need:

• A Workflow using the "When customer sends their first message" trigger
• Your Telegram audience selected in the trigger settings
• A "Let Fin answer" step added to the path

Once that Workflow is live, Fin picks up new Telegram conversations the same way it picks up any other channel.

If you get an "Invalid token" error, it means the token got truncated when copied. Copy everything after the colon, and double-check there are no spaces. Telegram tokens never contain spaces.

For the exact click-by-click steps, follow the Telegram and Intercom setup guide.

Here's a video tutorial showing the whole setup in action:

https://www.youtube.com/watch?v=352wuum-GKs

How to customize Fin's behavior for Telegram

Now that you have everything connected, it’s time to customize Fin for Telegram communication.

Here's exactly what to adjust and why it matters.

Message length

Fin's default answers are a bit long, while Telegram users prefer short messages.

You can use Fin’s Guidance to set a character limit for your Telegram audience, the same way you'd cap length for Facebook or Instagram, where Intercom already recommends this because those channels enforce a hard 1,000-character limit.

Telegram doesn't enforce a limit like that, but your customers will thank you for having one.

Formatting

Telegram renders messages differently from the Messenger widget, and this is where you need to know one specific limitation upfront: Fin can't consistently present hyperlinks as clickable, formatted links.

Guidance can encourage Fin to hyperlink where possible, but it can't guarantee it every time.

Tone

Telegram conversations tend to run shorter and more casual than email or even live chat. Ideally, you should use Guidance to set a more conversational tone specifically for your Telegram audience, separate from the tone you use on more formal channels.

Audience rules

Audience rules are what actually make all of this possible. Without them, any Guidance you write applies everywhere, which means you can't run one tone and length for Telegram and a different one for your website chat.

You need to set up an audience rule based on channel, so your Telegram-specific Guidance only fires for Telegram conversations.

Scheduling

Fin's involvement follows the schedule of whatever Workflow it sits in, not a separate global on/off switch. That means you can set Fin to handle Telegram only outside your team's office hours, while your human agents take Telegram during the day, just by adjusting the Workflow's active hours.

Language

Fin officially supports 45-plus languages, but it only answers in a language your content isn't written in if you've turned on real-time translation.

Without it, Fin simply won't respond to a message in a language it doesn't have matching content for, and there's no error message telling you why.

If your Telegram audience spans multiple languages, turn on real-time translation under Fin AI Agent settings before you go live.

Fin Handover to a human agent

Fin hands a Telegram conversation to your team automatically in three situations, and you can add more of your own on top.

Here's how handover works and what your agents see when it happens.

When Fin escalates on its own

Fin hands over without you configuring anything when:

• It can't find an answer in your content
• The customer asks to speak to a person
• A system error occurs

Escalation rules you set on purpose

Other than Fin's automatic triggers, you'll want to build your escalation rules for the following scenarios, refunds, cancellations, or anything touching sensitive customer data.

You can configure these under Fin > Train > Guidance.

What your agent sees

Since a Telegram conversation is a standard Intercom conversation, your agent gets the full thread the moment it lands in their queue.

Octopods also writes Custom Data Attributes onto every Telegram contact, including the customer's Telegram username and Telegram user ID, and you can use those attributes to build automatic assignment rules.

That means you can route Telegram conversations to a specific team the same way you'd route by language or region, so the right agent gets the conversation without anyone manually reassigning it.

For more on managing that view day to day, see how to manage Telegram messages in Intercom.

The disambiguation response

When Fin can't find a confident answer, it doesn't go quiet and it doesn't hand over immediately either. It gives the customer a disambiguation response instead, which:

• Shares context on what it did find
• Expresses uncertainty rather than guessing
• Attempts a partial answer if one is possible
• Asks the customer a clarifying question

One Telegram-specific habit to build: When your agents do pick up a handed-off Telegram conversation, remind them to actually write for Telegram. Keep replies short and conversational, the way your customer's other messages in that same thread already are.

Octopods limitations for Intercom Fin on Telegram

Here's a few limitations you might run into deploying Fin on Telegram through Octopods:

• Telegram's interactive features aren't something Fin generates on its own. Inline keyboards and reply buttons work on Telegram, but only through the Octopods API called from an Intercom Action, not from the Intercom composer and not from Fin itself.
• Fin Vision is documented for chat and email, not for Telegram. There's no documentation confirming Fin Vision works over Telegram or any other integrated channel, so a customer's screenshot might not get the same treatment on Telegram that it would in the Messenger.
• Multi-brand configuration is built for chat and email. Intercom's brand and Fin identity settings are documented for chat and email channels. If you run multiple brands, expect Telegram to use your default Fin identity rather than a per-brand one.
• Intercom's support team has limited ability to troubleshoot Octopods-specific issues. Intercom states this directly in its own FAQ: while Fin works with channels connected through third-party integrations, their support team's ability to troubleshoot problems specific to that third-party integration is limited.
• A Telegram bot can't message someone who hasn't messaged it first. This is a Telegram platform rule. Your customer has to find your bot and send the first message, or tap a link that opens a chat with it, before you can send them anything.
• Fin can't book meetings, on Telegram or anywhere else. There's no meeting tool available to Fin on any channel, so if a customer asks to schedule a call over Telegram, Fin will hand that off rather than attempt it.

How to test Fin on Telegram

You test Fin on Telegram before customers see it, using the teammate preview, since Fin isn't supported on [TEST] workspaces.

That preview is your private testing ground, and once you're ready for live traffic, you also get a one-time free allocation of resolutions, so you can validate real behavior

To build a test script, you should:

• Pull ten real questions from your actual Telegram conversation history, since real customer phrasing surfaces problems a tidy, well-written test question never will
• Include at least two questions you already know your help center doesn't answer, so you can watch what the escalation path actually looks like before a real customer hits it

On each test, check:

• Whether the answer is actually correct and complete
• Whether the message length feels right for Telegram, not like a wall of text
• Whether any links render acceptably instead of looking like a stray URL
• Whether handover fires when it should
• Whether the escalated conversation lands with the right team

Run your test script in the languages your Telegram customers actually use, not just English.

If your help center content is only written in English, confirm real-time translation is switched on before you go live.

Otherwise, you'll only find out it's missing when a customer's message in another language quietly gets no answer at all.

A few behaviors will show up during testing that look like bugs but are actually just how Fin works:

• One-word replies get weak results, since Fin doesn't have enough context to work with
• Long, multi-part questions get worse answers than short, specific ones
• If a customer fires off several messages in a row without waiting for a reply, Fin only answers the most recent one

Final thoughts

Fin doesn't cover Telegram natively, but you can connect it to Intercom through an Integration layer and set up Fin

Once Octopods brings your Telegram messages into Intercom as regular conversations, Fin answers them, tunes to them, and hands them off just like it does everywhere else.

You just need the bot connected, a Workflow pointing Fin at those conversations, and a bit of tuning around length, tone, and language so Fin actually sounds right on Telegram.