示意预览Route Facebook Messenger chats into Odoo Discuss, capture leads/tickets, and reply from Odoo.
Built to order for Odoo 17/18/19.
什么是 Facebook Messenger Live Chat & CRM Connector？
Route Facebook Messenger chats into Odoo Discuss, capture leads/tickets, and reply from Odoo. Built to order for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Your buyers already message you on Facebook Messenger — but those conversations live outside Odoo, disconnected from your CRM pipeline and Helpdesk. This build-to-order module closes that gap by wiring the Meta Messenger Platform API directly into Odoo Discuss, so every inbound Messenger thread becomes a channel your agents can answer without ever leaving Odoo.
This is not a ready-made download from apps.odoo.com. ECOSIRE designs, builds, installs and supports the module for your specific Odoo instance, with a typical lead time of one working week. We build against the official Meta Messenger Platform (Graph API + webhooks), so message ingestion, agent replies, the persistent menu and the greeting screen all use Meta-sanctioned mechanisms rather than fragile scraping.
Under the hood the module ships as a proper Odoo addon with its own __manifest__.py, ORM models (models.Model with typed fields and @api.depends computes for conversation state), security via ir.model.access.csv and record rules for multi-team isolation, XML/OWL views inside Discuss, and QWeb-rendered conversation exports. A Meta webhook controller receives inbound events, verifies the X-Hub-Signature-256 payload, deduplicates by message ID, and creates or updates a Discuss channel. From there an automated action can convert the thread into a crm.lead or a helpdesk.ticket, so no sales-ready message slips through the cracks.
We support Odoo 17, 18 and 19, on Community or Enterprise. Enterprise unlocks the tightest fit with Discuss and Helpdesk; on Community we adapt lead capture to the modules you run. You get the full source, a documented configuration, admin training, and a post-launch support window — and because you own the code, you are never locked into a black-box vendor app.
你得到什么
- Complete, commented module source (the Odoo addon: __manifest__.py, models, controllers, views, security, data) delivered to your repository
- Meta App + Facebook Page setup: webhook subscription, permissions/scopes, Page access token wiring, and app-review guidance where your use case needs it
- Installation and configuration on your Odoo 17/18/19 instance (or a staging copy first), including config parameters and cron/automated-action setup
- Lead and ticket routing rules configured to your CRM pipeline stages and Helpdesk teams
- Admin and agent documentation: how to connect a Page, manage the persistent menu, reply from Discuss, and read the conversation logs
- A live training session for your sales/support team plus a short handover walkthrough
- A defined post-launch support and warranty window for bug fixes and Meta-side changes (e.g. token or API-version updates)
- Deployment notes and a rollback plan so the addon can be upgraded safely on future Odoo point releases
这是给谁的
D2C / retail brand owner
Runs sales and support largely through the Facebook Page inbox and wants those conversations, and the leads inside them, to live in Odoo CRM instead of a separate browser tab.
Customer support / helpdesk lead
Needs Messenger inquiries to become trackable helpdesk.ticket records with SLAs, team routing and a full audit trail, answered by agents from one Odoo Discuss inbox.
Marketing / growth manager
Wants to capture Messenger conversations as attributed crm.lead records and send policy-compliant broadcast follow-ups (order updates, reminders) without leaving Odoo.
Facebook Messenger Live Chat & CRM Connector 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Messenger threads inside Odoo Discuss | Native — inbound and outbound in Discuss | Possible but you design it from scratch | Varies; often a separate widget, not Discuss | 不包括在内 |
| Auto-create crm.lead / helpdesk.ticket | Built to your pipeline via automated actions | Buildable, but you write the routing logic | Sometimes leads only, rarely tickets | 不包括在内 |
| Official Meta Messenger Platform API | Yes — Graph API, signed webhooks, Send API | Depends on your team's Meta expertise | Usually yes | 不包括在内 |
| Persistent menu & greeting setup | Configured and handed over | You implement it yourself | Sometimes included | 不包括在内 |
| Team routing via record rules | Yes — ir.model.access.csv + record rules | You build and test isolation yourself | Limited or per-plan | 不包括在内 |
| Source code ownership | Full source delivered to you | Yes, you own what you build | No — vendor black box | n/a — core code |
| Odoo 17 / 18 / 19 + Community & Enterprise | Supported and version-fitted | You maintain each version yourself | Often lags new Odoo releases | 部分支持 |
| Post-launch support & Meta-change updates | Defined support window + retainer option | Your team owns all maintenance | Per subscription, quality varies | 不包括在内 |
关于Facebook Messenger Live Chat & CRM Connector的常见问题
How long until the module is delivered and live?
This is a build-to-order module, not an instant download. Typical lead time is one working week depending on scope — for example whether you need Helpdesk ticketing, custom routing rules, or Meta app review for advanced permissions. After a short scoping call we confirm the timeline, build against a staging copy of your Odoo, then install and verify on production with you.
What support and updates do I get after launch?
You get a defined post-launch support and warranty window covering bug fixes and adjustments for Meta-side changes such as Graph API version bumps or token renewals. Because you receive the full source, your own team (or ECOSIRE on an ongoing plan) can maintain it. We can also quote a support retainer that keeps the connector current across future Odoo point releases and Messenger Platform policy changes.
Does it work on Odoo Community or only Enterprise?
Both. The connector supports Odoo 17, 18 and 19 on Community or Enterprise. Enterprise gives the tightest integration with Discuss and Helpdesk; on Community we adapt lead capture to the CRM/messaging modules you actually run and confirm the exact behavior during scoping.
Is this an official apps.odoo.com module?
No. It is a custom module that ECOSIRE builds, installs and supports specifically for your instance — you own the code. That means no black-box vendor lock-in, and the addon is shaped to your pipeline, teams and Meta app rather than a one-size-fits-all listing.
How does it stay within Facebook's messaging rules?
We build on the official Meta Messenger Platform. Agent replies are sent inside Meta's 24-hour standard messaging window, and follow-ups outside it use approved message tags or one-time notifications. The webhook validates Meta's signed payloads, and we set up your Page access token, app secret and webhook verify token correctly so the integration passes Meta's requirements.
Can Messenger conversations become CRM leads and Helpdesk tickets automatically?
Yes. An automated action (or a scheduled ir.cron sweep) converts qualifying Messenger threads into crm.lead or helpdesk.ticket records, tagged with source and team, and links the sender to a res.partner. Your agents reply from Discuss while the pipeline, SLAs and reporting update as standard Odoo records.
相关模块
Facebook Messenger Live Chat & CRM Connector
Route Facebook Messenger chats into Odoo Discuss, capture leads/tickets, and reply from Odoo. Built to order for Odoo 17/18/19.
- Meta Messenger Platform API connection (Graph API + Page access token) with the OAuth/webhook subscription configured against your verified Facebook Page and Meta App
- Secure inbound webhook controller that validates the X-Hub-Signature-256 signature, verifies the challenge on subscription, and rejects unsigned or replayed payloads
- Inbound Messenger messages land as Odoo Discuss channels — text, quick replies, attachments and images mapped to mail.message records
- Automatic lead/ticket creation: an automated action (or ir.cron sweep) converts qualifying threads into crm.lead or helpdesk.ticket records with source and campaign tagging