Most teams that run Odoo already live inside it for sales, invoicing, and support — but the conversations that actually close deals and resolve tickets happen on WhatsApp, in someone's phone, invisible to the system of record. Reps copy-paste order numbers into a personal handset, customers reply to a number nobody else can see, and when that person is on leave the thread is simply lost. Odoo's native Discuss and email chatter cover internal notes and SMTP, but there is no first-class, auditable two-way WhatsApp channel bound to the customer, the sales order, or the helpdesk ticket. Off-the-shelf marketplace modules exist, but they are generic, rarely fit your object model, and leave you owning nothing you can extend.

We build a made-to-order integration on Meta's official WhatsApp Business Cloud API — never an unofficial browser-automation hack that risks a number ban. At its core is a new set of models (whatsapp.account, whatsapp.message, whatsapp.template) with proper models.Model inheritance of mail.thread, so inbound and outbound messages post directly onto the chatter of the linked record. A controller exposes a signed webhook endpoint that verifies Meta's X-Hub-Signature-256 HMAC, then routes each inbound payload to the matching res.partner by phone (with configurable country-code normalization) and threads it under the right conversation. Outbound sends go through the Graph API with delivery/read receipts written back via @api.depends compute fields and status enums. A "Send on WhatsApp" action appears on any model you nominate — sale.order, account.move, helpdesk.ticket, crm.lead — rendering a QWeb-style body with record placeholders. Approved message templates are synced from your Business Account so agents pick from the live, Meta-approved list, and automated actions (server actions / base automation) can fire a template when an invoice is posted or a delivery is validated. Everything is scoped with ir.model.access.csv plus record rules so agents see only their teams' threads, and the whole thing ships as a clean, upgrade-safe module with its own __manifest__.py targeting Odoo 17.0, 18.0, or 19.0 on Community or Enterprise.

Because this is build-to-order, you are not downloading a frozen package. We start with a scoping call to pin down which models get the send action, how partners are matched, which templates and automations you need, and whether media (images, PDFs, documents) and multi-number routing are in play. We then build against a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source and the git repository, so your team — or ours on retainer — can extend it later.

Pricing starts from $999 (indicative, single-company base scope); multi-company routing, several linked models, multiple WhatsApp numbers, media handling, deeper localization of phone/number formats, and migrating historical conversation data increase the quoted scope. We confirm a firm fixed quote after the scoping call — never a surprise on the invoice.