Facebook Messenger Live Chat & CRM Connector

Name: Facebook Messenger Live Chat & CRM Connector
Brand: ECOSIRE
SKU: messenger-livechat-crm

主な機能

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

Agent replies sent straight from Discuss — outbound messages are relayed to Messenger via the Send API within Meta's 24-hour standard messaging window

Sender enrichment: the Messenger PSID is resolved to a res.partner (name and profile pic where the Graph API permits) so conversations attach to a real contact

Persistent menu and Get Started greeting configured through the module so first-time users see your branded welcome and quick-action buttons

Broadcast and notification tags that let you send message-tag or one-time-notification follow-ups within Meta's policy (order updates, appointment reminders)

Team routing with record rules so each sales or support team only sees its own Messenger channels — enforced by ir.model.access.csv plus record-level domains

Compute fields with @api.depends track conversation status (new, assigned, answered, closed) and SLA timers for reporting

Full audit trail: raw Meta payloads and delivery/read receipts logged per message for compliance and debugging

QWeb report export of a conversation transcript (PDF) for handoff, dispute resolution or record-keeping

Configurable auto-reply / away message and business-hours handling driven by Odoo resource calendars

JSON-RPC/XML-RPC friendly — the created leads, tickets and channels are standard Odoo records, so external tools and dashboards read them normally

Token and secret management for the Page access token, App secret and webhook verify token stored via Odoo config parameters, not hard-coded

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

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 2 to 4 weeks. 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 の比較方法

基準	エコシエール	カスタムビルド	競合他社
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
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 2 to 4 weeks 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.