Connect personal Telegram accounts (not bots) to Odoo. Operators read and reply to customer messages right inside Odoo Discuss, with automatic lead creation in CRM on first contact.
This module talks to Telegram as a real user — the same way Telegram Desktop does. It is not a Bot API integration. Built for manual operator work — sales and support conversations, not mass messaging, which Telegram's Terms of Service prohibit for personal accounts.
The module ships with a companion daemon (Docker Compose) that talks to Telegram. It requires self-hosted Odoo — on-premise, VPS, or Odoo.sh with custom services. Odoo Online is not supported.
Real screenshots from an Odoo 18 database with the module installed.
Settings → Telegram: a readiness checklist, API credentials, connected accounts, live service status and a built-in FAQ.
Comparison between our module and classical bot-based integration.
The official way via bots. Good for simple broadcasts, but has strict limitations for full CRM workflows.
Number of accounts
Typically one shared bot for the whole company
CRM Workflow
Complex webhook-based logic
Starting a conversation
The client must message the bot first
Connection Type
Public Bot (@botname)
Protocol-level integration (like a Desktop client). No intermediaries or Bot API restrictions.
Number of accounts
Unlimited for every operator
CRM Workflow
Native integration & auto-leads
Starting a conversation
Operators can write first from the company number
Connection Type
Personal Number (Userbot)
No 'one account per DB' restriction. Each operator can run their own personal account.
One company number can be worked by the whole team: colleagues see every conversation of the account and reply to clients — without a Telegram account of their own.
Daily limits on cold first messages and phone lookups, plus an automatic 24-hour pause when Telegram signals peer-flood — the module actively protects your numbers.
A Check Telegram button on the contact card shows whether a phone number is on Telegram — operators write first only to clients they can actually reach.
Messages are duplicated in Odoo Discuss instantly. Phone replies also appear in Odoo.
Live delivery tracking: sending → sent → read. Emoji reactions sync both ways, and inbound photos up to 20 MB appear right in Discuss.
Authorization via phone number + SMS/code (with 2FA support), or via QR-code scan.
Every first message and phone lookup is recorded with the operator and date — managers see who contacted whom, and the log drives the daily limits.
Telegram sessions are stored Fernet-encrypted in your own database. Disconnecting an account revokes its session instantly.