Healthcare teams live in two disconnected worlds: patients reach out on WhatsApp because it is where they already are, while the clinical and admin record lives in Odoo. The result is a front desk juggling a personal phone in one hand and calendar.event / patient records in the other — no audit trail of what was promised, no link between a reminder sent and the appointment it belongs to, and no way for a covering colleague to see the conversation history. Odoo's native Discuss and email/SMS gateway don't speak the WhatsApp Cloud API, message templates, or the 24-hour customer-service window, and the marketing-oriented WhatsApp features in Enterprise are built for campaign blasts rather than a real two-way service inbox tied to a patient's chart.

We build a dedicated WhatsApp inbox module for your Odoo. At its core is a new whatsapp.channel / whatsapp.message model pair (extending mail.thread so every conversation posts to the standard chatter and inherits followers, activities, and the message log) with models.Model fields for direction, WABA phone-number id, template name, delivery status, and the linked res.partner or patient record. A controller exposes an authenticated webhook endpoint that receives inbound messages and status callbacks from the WhatsApp Cloud API, verifies the signature, and threads each message onto the right conversation by matching the sender's number. Outbound sending — free-text replies inside the 24-hour window and pre-approved template messages outside it — goes through a queued service so a slow API call never blocks the UI. The agent-facing screen is an OWL inbox view (chat-style panel, unread counts, quick replies, media attachments stored as ir.attachment) rendered from XML, and the whole thing is wired to automated actions / server actions so an appointment confirmation or a no-show follow-up can fire a template automatically from an Odoo record change.

Everything is scoped to healthcare-grade access control. Conversations are protected by ir.model.access.csv plus record rules so front-desk staff see only their department's threads while clinicians see their own patients; message bodies can be flagged and hidden from non-authorized groups. The module ships with QWeb-rendered conversation transcripts for the patient file, and every send/receive is timestamped for your compliance log. It integrates with the rest of Odoo through the standard XML-RPC/JSON-RPC API, so existing automations or external systems can trigger a message without touching WhatsApp directly. We support Odoo 17.0, 18.0, and 19.0, and build against Community or Enterprise depending on your edition — noting where Enterprise's native messaging features can be reused versus where the Community build needs the full custom stack.

Because this is build-to-order, we start with a scoping call to lock the exact WhatsApp Business account setup, template catalogue, patient-matching rules, and role model, then deliver on your own staging database first for UAT before go-live. Typical delivery is one working week from confirmed scope. You need your own approved WhatsApp Business Account and Cloud API access (Meta's terms and per-message pricing are separate from our fee); we handle the Odoo side end to end. Pricing starts from $999 (indicative, single-company base scope); multi-company routing, multiple WABA numbers, deeper patient-record matching, and integration with third-party clinical systems increase the quoted scope.