Why connect Telegram to Intercom
Intercom is used by SaaS, fintech and marketplace companies in the US, UK and EU for support and lifecycle messaging. There is no native Telegram channel, so conversations are created through the API and kept in sync both ways by our middleware. A Telegram bot or Mini App without the integration creates a second customer list that nobody maintains; with it, every Telegram interaction lands on the right record, managers get alerts where they already are, and customers get updates in the chat they actually read.
How the integration works
- Auth. An app access token with contacts, conversations and events scopes.
- Inbound. Telegram users mapped to Intercom contacts; messages create or continue conversations with Mini App context as attributes.
- Outbound. Webhooks on teammate replies forward messages to Telegram; Series and Outbound messages can trigger Telegram sends through our endpoint.
- AI. Fin or our assistant answers first from your Articles; unresolved threads route to teammates with a summary.
Typical flows
- Support chat in Telegram mirrored to the Intercom inbox
- Product events from the Mini App → Series campaigns → Telegram nudges
- Lead qualification in Telegram → contact attributes and tags
- CSAT and NPS via the bot
Architecture
| Layer | What runs there |
|---|---|
| Telegram | Your bot (grammY or aiogram) and Mini App; users never leave Telegram |
| Middleware | A small service on your cloud (Node.js or Python): auth with Intercom, upserts, dedupe, templates, rate limits, retries, audit log |
| Intercom | Native objects and automations; no custom code inside Intercom beyond fields and triggers |
| Monitoring | Failed syncs alert your team in a Telegram group; a daily reconciliation report catches drift |
We keep business logic in the middleware so that Intercom upgrades, API version changes and bot changes do not break each other. The middleware ships with tests, an admin page for retries and documentation your developers can extend.
Data, consent and compliance
Telegram user IDs, usernames and phone numbers are personal data. The integration stores consent (captured in the bot or Mini App), supports unsubscribe commands, honors deletion requests by removing the Telegram identity from Intercom records, and keeps data in your Intercom region and your cloud region. For GDPR, UK GDPR, PIPEDA and the Australian Privacy Act we provide a data flow document for your DPO.
Pricing and timeline
| Scope | Budget | Timeline |
|---|---|---|
| One-way: Telegram → Intercom records and manager alerts | from $3,000 | 1–2 weeks |
| Two-way: plus triggered messages and operator replies | +$1,500–$3,000 | +1 week |
| Commerce or support add-ons (orders, tickets, payments) | +$1,500–$4,000 | +1–2 weeks |
Every integration includes field mapping, a sandbox phase, a go-live checklist and 30 days of fixes. Need the bot or Mini App built as well? See Telegram bot development and Mini App development.
* All prices and ranges on this page are indicative. The final cost is calculated for each project individually and depends on the complexity of the task, the number of developers and specialists required, and the delivery timeline you set. Use the ranges to understand the typical bracket, not as a fixed offer; the fixed price is confirmed in writing after scoping. Read our pricing terms.