Open WhatsApp Connector

Key Features

Two-way messaging bridge that posts inbound and outbound WhatsApp messages as threaded conversations inside Odoo Discuss via the native `mail`/`message_post` framework

Authenticated webhook controller endpoint that verifies provider signatures, deduplicates by provider message id, and rejects replayed or forged payloads

Automatic `res.partner` resolution/creation from the sender's phone number, with matching against existing contacts to avoid duplicates

Configurable chatbot/flow engine built on `automated actions` and server actions — keyword triggers, menu trees, and business-hours routing editable without code redeploys

WhatsApp message template management that mirrors your provider-approved templates with typed parameter mapping and language variants

Outbound send service layer with queued dispatch, retry/backoff, and delivery + read status callbacks written back onto the message record

Support routing that converts or attaches an inbound conversation to a `helpdesk.ticket`, `crm.lead`, or sales follow-up activity

Media handling for inbound/outbound images, documents, and audio stored as `ir.attachment` with size and MIME validation

Per-agent and per-team visibility enforced through `ir.model.access.csv` and record rules; multi-company isolation of numbers and threads

Full conversation audit trail with timestamps, direction, provider status, and linked source record for compliance

Custom models with compute fields and `@api.depends` for unread counts, SLA timers, and last-response tracking on each conversation

XML/OWL views: Discuss-integrated conversation panel, configuration screens, and template editor consistent with Odoo UI conventions

Optional XML-RPC/JSON-RPC hooks so external systems can send templated WhatsApp messages through Odoo as the system of record

Built and regression-tested against Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Most teams that run Odoo end up managing WhatsApp conversations in a completely separate place — a phone, a browser tab, a shared inbox no one really owns — while their customers, orders, and tickets all live in Odoo. Replies get lost, context is copy-pasted by hand, and there is no audit trail linking a message thread back to the res.partner, sale order, or helpdesk.ticket it belongs to. Odoo core gives you Discuss plus email and SMS gateways, but out of the box it has no native two-way WhatsApp channel in Community, and the Enterprise offering is coupled to specific plans and providers. When you want inbound messages, chatbot automation, and support routing all threaded into the ERP your team already lives in, native Odoo runs out of road.

The Open WhatsApp Connector is a build-to-order Odoo module that ECOSIRE scopes, builds, and installs for you. Technically it introduces a set of custom models — a WhatsApp account/channel configuration, message and template records, and a conversation link — wired into Odoo's mail framework so every inbound and outbound message lands as a threaded conversation inside Discuss. Incoming webhooks from your chosen WhatsApp Business API provider hit an authenticated controller endpoint that verifies the payload signature, deduplicates by provider message id, resolves or creates the matching res.partner, and posts the message onto the correct discuss.channel or the relevant record's chatter via message_post. Outbound sends go through a provider service layer with retries and delivery/read status callbacks, and are queued so a slow provider never blocks a user's UI.

On top of the transport we build the automation you actually need: a lightweight chatbot/flow engine driven by automated actions and server actions so keyword triggers, menu trees, and business-hours routing can be configured without redeploying code; template management that mirrors your approved WhatsApp message templates with parameter mapping; and support routing that turns an inbound conversation into (or attaches it to) a helpdesk.ticket, CRM lead, or sales follow-up. Everything respects Odoo's security model — access is governed by ir.model.access.csv and record rules so agents only see their teams' conversations, and multi-company setups keep each company's WhatsApp number and threads isolated. It ships as a proper module with a clean __manifest__.py, OWL/XML views, and QWuBE-free QWeb where reports are needed, and it is built and tested against Odoo 17.0, 18.0, and 19.0 (Community or Enterprise).

Because this is made to order, delivery follows a clear path: a scoping call to confirm your provider, numbers, volumes, and automation rules; a fixed written quote; build on an isolated branch; UAT on a staging database with your real templates and test numbers; then production install with a short hypercare window. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional numbers, multi-company routing, deeper chatbot flows, extra integrations (CRM, Helpdesk, eCommerce), and higher message volumes increase the quoted scope. You receive a fixed price after the scoping call — never a surprise.

What you get

Installable, version-pinned module source code for your Odoo 17.0, 18.0, or 19.0 build

On-site or remote installation and configuration on your Odoo instance, wired to your chosen WhatsApp Business API provider

Technical documentation covering models, controller endpoints, webhook setup, security rules, and configuration

End-user guide plus a live training session for agents and administrators

UAT on a staging database with rollback plan before any production change

Post-go-live hypercare support window for bug fixes and configuration adjustments

Git repository handover with full commit history and branch/tag structure

Provider setup checklist and webhook/credential configuration walkthrough

Who this is for

Customer support lead

Runs a team that fields WhatsApp inquiries all day and needs every conversation threaded into Odoo Helpdesk with routing, ownership, and an audit trail instead of a shared phone.

Sales and CRM manager

Wants inbound WhatsApp messages to become CRM leads and follow-up activities automatically, with templated outbound messages sent from the same record salespeople already work in.

eCommerce / retail operations owner

Handles order questions, delivery updates, and abandoned-cart nudges over WhatsApp and needs template-based, status-tracked messaging tied to the customer's `res.partner` and orders.

Odoo administrator / IT lead

Owns the instance and needs a maintainable module with clean security rules, multi-company isolation, and documented webhooks that survives upgrades across Odoo 17/18/19.

How Open WhatsApp Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor
Fit to your process	Built to your exact provider, numbers, and routing rules	Fully bespoke but you define and maintain everything	Generic feature set; you adapt to its assumptions
Odoo integration depth	Threaded into Discuss, Helpdesk, CRM via `message_post`	As deep as your team builds it	Varies; often shallow chatter linkage
Chatbot / automation	Configurable flows via automated + server actions	Whatever you code and maintain yourself	Fixed automation, limited customization
Security & multi-company	Record rules + per-company number/thread isolation	Depends on your implementation rigor	Often single-company or basic access control
Version coverage	Built and tested for Odoo 17/18/19, Community & Enterprise	You port and retest each upgrade	Depends on vendor's maintenance
Delivery model	Scoped, built, installed, 2–4 weeks from confirmed scope	Long in-house build and QA cycle	Instant download but self-install and self-support
Support & ownership	Hypercare window + optional retainer + full git handover	Your team owns all support	Vendor support tiers, usually shared
Total cost predictability	Fixed quote from a $249 indicative base after scoping	Open-ended engineering cost	Low list price, higher hidden integration effort

Frequently Asked Questions about Open WhatsApp Connector

Is this an existing app I can download and install today?

No. The Open WhatsApp Connector is build-to-order. ECOSIRE scopes, builds, installs, and supports it for your specific Odoo version, WhatsApp provider, and automation rules. There is no instant-download package — you start by requesting a quotation.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on how many numbers, chatbot flows, and integrations (Helpdesk, CRM, eCommerce) you need. We confirm the exact schedule in your fixed written quote after the scoping call.

How does pricing and scoping work?

Pricing starts from $249 as an indicative single-company base scope. After a short scoping call we send a fixed written quote. Additional numbers, multi-company routing, deeper chatbot logic, extra integrations, and higher message volumes increase the quoted scope — but you always get a fixed price before we start, never a surprise.

Which Odoo versions and editions are supported?

We build and test against Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Because Community has no built-in WhatsApp channel, this is especially useful there; on Enterprise we integrate cleanly alongside existing Discuss and messaging features.

Do I need a WhatsApp Business API account?

Yes. This connector integrates with the official WhatsApp Business API through a provider of your choice. You supply (or we help you obtain) the API credentials and approved message templates; our module handles webhooks, threading, automation, and status tracking on the Odoo side.

What about support and updates after go-live?

Every build includes a post-go-live hypercare window for bug fixes and configuration tweaks. Beyond that, we offer ongoing support and version-upgrade retainers so the module keeps working as you move between Odoo 17, 18, and 19. You also receive the full git repository so you are never locked in.

How are conversations kept secure and separated by team?

Access is governed by Odoo's `ir.model.access.csv` and record rules, so agents only see their own teams' conversations. Multi-company setups keep each company's WhatsApp number and threads isolated, and every message carries a full audit trail with direction, status, and linked source record.