Social messages are where a lot of buying intent now lives, but they land outside your ERP. Agents flip between a phone app for Instagram Direct, a separate desktop tab for Messenger, and Odoo for the actual customer record — so replies are slow, context is lost, and there is no audit trail tying a conversation to a lead, a sales order, or a helpdesk ticket. Odoo's Discuss app already gives you a solid real-time channel and message backbone (mail.thread, mail.channel/discuss.channel, presence, attachments), but out of the box it has no connector to the graph messaging APIs, so those channels simply never appear in Odoo.

This is a made-to-order integration that closes that gap. We build a dedicated Odoo module that authenticates to your business messaging accounts, subscribes to inbound-message webhooks, and materializes each social conversation as a native Discuss thread. On the technical side that means new ORM models (models.Model) for the connected page/account, the conversation, and the external participant, each extending mail.thread so chatter, followers, and activities work as usual; a controller exposing a signed webhook endpoint that verifies the platform signature, deduplicates event ids, and enqueues inbound payloads; and an outbound service that calls the platform Send API when an agent posts a reply in Discuss. Message identity is mapped both ways so edits, delivery/read state, and threading stay consistent, and media (images, voice notes, story replies) is stored as ir.attachment records against the thread. We honor the platforms' customer-service messaging windows and surface the window state in the UI so agents know when a free-form reply is still allowed.

Because it is real Odoo, everything wires into the rest of your system. Inbound conversations can auto-create or match a res.partner, spin up a crm.lead or a helpdesk.ticket via automated actions/server actions, and route to the right team using record rules. Access is governed by ir.model.access.csv plus record rules so agents only see the channels they own; views are delivered in XML/OWL to fit the Discuss client; and reporting is available through QWeb and standard Odoo analytics (volume, first-response time, per-agent load). Integrations with your own middleware or a customer portal are exposed through Odoo's XML-RPC/JSON-RPC API. We target Odoo 17.0, 18.0, and 19.0 and confirm Community vs Enterprise assumptions during scoping, since the Discuss client and some helpdesk features differ between the two.

Delivery is build-to-order. We start with a short scoping call to confirm your Odoo version and edition, which social accounts and pages you connect, volume, and which downstream records (partner, lead, ticket, sales order) each conversation should touch. You then get a fixed written quote and timeline — typical delivery is 2 to 4 weeks from confirmed scope — after which we build on a branch, hand over on a staging database for UAT, and deploy to production with a rollback plan. Pricing starts from $249 (indicative, single-company base scope); connecting multiple pages or accounts, multi-company routing, deep CRM/helpdesk automation, or historical conversation migration increases the quoted scope.