Telegram Bot & CRM Integration

This is a build-to-order module, so it is not an instant download. Typical lead time is 2–4 weeks depending on scope and the triggers you need. The process is: a short requirements call, a written scope and fixed quote, development on a staging copy of your Odoo, your review and sign-off, then production installation and go-live. You get progress updates throughout and nothing ships to production until you approve it on staging.

Every engagement includes a defined post-go-live support window for bug fixes and configuration help, with agreed response terms. During that window we also keep the module compatible with your Odoo minor updates. When you upgrade to a new major Odoo version (for example 18 to 19), or want new triggers and features, we scope that as a small follow-on. You own the source code, so you are never locked to us for maintenance.

We build for Odoo 17, 18 and 19, and it runs on both Community and Enterprise. Features that depend on the Enterprise Helpdesk app (like ticket-stage notifications) are substituted with a Project task or a lightweight custom ticket model on Community, so you still get inbound-to-ticket routing either way. We confirm your exact version and edition during scoping.

You create a bot with Telegram's BotFather and give us the token, which we store in res.config.settings (not in code). Odoo receives updates either through a webhook controller over HTTPS or a long-polling scheduled action, whichever suits your hosting. Access to conversations is enforced with ir.model.access.csv and record rules so agents only see the teams and companies they are allowed to, and the token is never exposed to end users.

Yes. Outbound notifications are driven by Odoo automated actions (base.automation) and server actions on the records you choose — sale.order confirmation, account.move invoice posting, stock delivery validation, helpdesk.ticket stage changes, and more. Message text is templated so it can include live fields like order number, amount and a tracking link. We set up your initial set of triggers during the build and document how to add more.

Everything the module captures is stored as standard ORM records — chat_id and username on res.partner, messages in the chatter, files as ir.attachment, subscribers in a dedicated model. That means it is all reportable in Odoo and reachable through the XML-RPC / JSON-RPC API, so you can build dashboards, pull it into other automations, or export it without any proprietary black box.