Most teams that run Odoo eventually hit the same wall: customer conversation lives in one place (Discuss, mail.thread, the chatter) while the channel customers actually reply on — their phone — lives in a disconnected mobile app or a browser tab nobody logs. Sales confirmations, delivery notices, service updates and one-off replies get copy-pasted by hand, or worse, never reach the record they belong to. Odoo core gives you email and internal messaging, but out of the box it has no notion of an outbound/inbound mobile messaging gateway, no delivery-state tracking, and no clean abstraction layer to bolt a third-party provider onto. That is exactly the gap this base module fills.

This is the foundation layer — a deliberately provider-agnostic base module that gives your Odoo the reusable scaffolding every mobile-messaging feature depends on. Technically, we ship a new set of ORM models (models.Model) for message envelopes, delivery status and per-channel configuration, wired into the existing mail.thread / mail.message backbone so a mobile message logs into the same chatter timeline as email and notes. The module defines a mailing.gateway-style connector interface (an abstract base you subclass per provider), outbound send methods, a webhook controller endpoint for inbound and delivery-receipt callbacks, and @api.depends computed fields for message state (queued, sent, delivered, failed). Everything is exposed through the standard XML-RPC/JSON-RPC API so external systems and your other custom modules can enqueue messages programmatically.

Because it is the base, it is built to be extended rather than to lock you in. The __manifest__.py declares clean dependencies (mail, base) and no heavyweight extras, so it installs on Community or Enterprise. Security is real, not an afterthought: dedicated groups plus ir.model.access.csv entries and record rules scope who can view message logs and who can configure gateways — with multi-company record rules where you run more than one company. We include the views (XML list/form for configuration and message logs, an OWL-friendly structure ready for later interactive widgets), an automated action / server-action hook so other modules can trigger sends on state changes, and optional QWeb templates for message-body rendering. The result is a stable, documented contract that your team — or a future ECOSIRE feature module — can build channel-specific behavior on without re-plumbing the fundamentals.

Delivery is build-to-order. After a short scoping call we confirm exact scope in writing — your Odoo version (17.0, 18.0 or 19.0), Community vs Enterprise, which provider gateway you intend to connect, single- vs multi-company, and any data or workflow specifics. We then build against a staging copy of your database, run UAT with you, and only deploy to production with a documented rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company topology, additional provider integrations, deeper localization, and data-migration volume increase the quoted scope. You always get a fixed written quote after the scoping call — never a surprise.