Most teams that run Odoo still copy the customer's phone number out of a sales order, switch to a phone or a browser tab, hunt for the right greeting, paste in the order reference by hand, and hope they typed the amount correctly. Odoo core will happily send a templated email from almost any record, but the moment your customers live on WhatsApp, Instagram DMs, or Messenger, the native mail.template engine runs out of road: there is no first-class channel binding, no reusable message library scoped to those platforms, and no way to trigger a personalized chat message from a sale.order, account.move, or crm.lead without leaving Odoo. The result is slow follow-ups, off-brand wording, and zero record of what was actually sent.

Message Templates Everywhere is a build-to-order module ECOSIRE designs, builds, and installs to close that gap. We introduce a dedicated template model (conceptually messaging.template) with a channel selector, a mail.render.mixin-backed body so you get the same Jinja/QWeb-style placeholder syntax as native email templates (${object.partner_id.name}, ${object.amount_total}, order and invoice references, portal links), and a model_id binding so a template only surfaces on the record types it belongs to. A reusable "Send message" action is injected into the form views of the models you nominate — sales, invoicing, CRM, helpdesk, subscriptions, or any custom model — rendering the merged text, letting the agent review it, and dispatching it through your chosen messaging provider's API. Every send is written back to the record's mail.thread chatter as a logged note, so the conversation history and the audit trail live where your team already looks.

Technically, the module ships as a clean, upgrade-safe addon: a proper __manifest__.py declaring dependencies (mail, sale, account, crm, and whichever apps your scope needs), ORM models with @api.depends computes for any derived fields, ir.model.access.csv plus record rules so only authorized users and the correct companies can see and send templates, XML/OWL view extensions for the send action, and — where you want it hands-off — base.automation automated actions that fire a template on a stage change, invoice validation, or delivery confirmation. Because outbound chat platforms authenticate per business account, we wire the provider credentials through Odoo system parameters and a guarded settings screen rather than hard-coding anything, and we expose the send routine over the standard XML-RPC/JSON-RPC API so your other systems can trigger the same templates. It runs on Community or Enterprise, and we target your exact series — Odoo 17.0, 18.0, or 19.0 — so nothing depends on version-specific behavior we haven't tested against.

Because this is made to order, nothing is downloaded and switched on the same afternoon. We start with a short scoping call to confirm which record types need the action, which messaging channels and provider accounts you use, the initial template set, and any automation triggers. From confirmed scope, typical delivery is 2 to 4 weeks: we build on a staging copy of your database, hand it to you for UAT, then install into production behind a rollback plan. Pricing starts from $249 (indicative, single-company base scope); additional messaging channels, multi-company routing, deeper localization of template content, and integrations with more record types or external systems increase the quoted scope. You receive a firm fixed quote after the scoping call — never a surprise on the invoice.