A build-to-order Odoo integration that routes Instagram Direct and Messenger conversations into the Discuss app so your team answers social messages from one threaded inbox. ECOSIRE builds, installs, and supports it on Odoo 17, 18, or 19 after a scoping call. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A build-to-order Odoo integration that routes Instagram Direct and Messenger conversations into the Discuss app so your team answers social messages from one threaded inbox. ECOSIRE builds, installs, and supports it on Odoo 17, 18, or 19 after a scoping call.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
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.
Retail and consumer brands that field a high volume of Instagram Direct and Messenger inquiries and want those conversations to sit next to the contact, order, and inventory data already in Odoo instead of on a phone.
Helpdesk leads who need every social message to become a trackable ticket with an owner, SLA timer, and first-response reporting, all inside Discuss rather than a separate messaging app.
Sales managers who want DMs that show buying intent to auto-create or attach to a `crm.lead`, route to the right salesperson, and keep a full conversation history against the opportunity.
In-house Odoo admins responsible for module governance who need clean security rules, documented webhook handling, credential rotation, and a maintainable module across the 17/18/19 upgrade path.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Fit to your Odoo & process | Built to your exact version, edition, and CRM/helpdesk flow | Fully bespoke but you own all design decisions | Generic feature set, adapt your process to it | |
| Social channels in Discuss | Instagram DM & Messenger as native Discuss threads | Possible, depends on in-house skill | Often one channel or a bolted-on inbox | |
| CRM / helpdesk wiring | Auto partner/lead/ticket via scoped automated actions | Whatever you have time to build | Usually limited or manual linking | |
| Security model | `ir.model.access.csv` + record rules per team/agent | Depends on developer discipline | Coarse, rarely per-channel ownership | |
| Delivery time | Typically 2-4 weeks from confirmed scope | Unpredictable; hiring/ramp overhead | Instant install but then integration work | |
| Cost model | From $249 indicative, fixed quote after scoping | High developer day-rate, open-ended | Low license fee, hidden setup cost | |
| Support & version upgrades | Support window + optional 17/18/19 maintenance | You maintain it yourself | Vendor roadmap, not your priorities | |
| Code ownership | Full source + git repo handed over to you | You own it entirely | Encrypted/licensed, no real ownership |
This is build-to-order, so we build it specifically for your setup rather than shipping a pre-existing download. Typical delivery is 2 to 4 weeks from confirmed scope. After the scoping call we give you a written timeline; account connections, volume, and how much CRM/helpdesk automation you want are the main factors.
Pricing starts from $249, which is indicative for a single-company base scope. We hold a short scoping call, confirm your Odoo version, edition, connected accounts, and downstream records, then give you a fixed written quote before any build starts. There is no firm price until scope is agreed.
We build for Odoo 17.0, 18.0, and 19.0 on either Community or Enterprise. We confirm your exact version and edition during scoping because the Discuss client and some helpdesk capabilities differ between Community and Enterprise, and we adjust the build accordingly.
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks. Beyond that we offer ongoing maintenance, and because the messaging platform APIs change over time we can quote a maintenance arrangement to keep the connector aligned with API and version changes.
No. It is a productized service, not an off-the-shelf marketplace download. We build the module against your requirements, install and configure it, then hand over the source and git repository. You own the code once delivered.
Inbound conversations can match or create a `res.partner`, then automated/server actions can spin up a `crm.lead` or `helpdesk.ticket` and route it to the right team via record rules. Exactly which records are touched is defined during scoping so the flow fits your process.
Tokens and webhook secrets are stored securely with scoped system parameters and rotation support. The inbound controller verifies the platform signature on every payload, deduplicates event ids, and access to conversations is governed by `ir.model.access.csv` and record rules.
A build-to-order Odoo integration that routes Instagram Direct and Messenger conversations into the Discuss app so your team answers social messages from one threaded inbox. ECOSIRE builds, installs, and supports it on Odoo 17, 18, or 19 after a scoping call.