Twilio SMS Gateway (Enterprise-grade)

The module wires Twilio's Programmable Messaging API directly into Odoo's ORM so you can send an SMS from virtually any record — a Sales Order, a Purchase Order, a contact (res.partner), a Helpdesk ticket, or a POS receipt — using a "Send SMS" action that respects Odoo's own security. Transactional messaging is driven by Odoo automated actions (base.automation) and server actions: confirm a Sales Order and the customer gets an order confirmation; validate a delivery (stock.picking) and a "your order has shipped" text goes out; a Helpdesk ticket changes stage and the requester is notified — all from templated, translatable messages.

Under the hood we add a dedicated Twilio outbound message model (a proper models.Model with fields for recipient, body, Twilio SID, status and error code) and compute fields with @api.depends for delivery status and segment/cost estimation. Inbound messages and delivery receipts are captured through a secured controller endpoint that receives Twilio status-callback and inbound webhooks, validates the X-Twilio-Signature, and updates each message's state (queued → sent → delivered → failed/undelivered). Two-way replies are threaded back onto the originating partner or record via the Odoo chatter (mail.thread), so your team sees the full conversation where the work actually happens.

Access is governed the Odoo way: ir.model.access.csv grants create/read/write on the SMS models to the right groups, and record rules keep multi-company and per-user visibility clean. Credentials (Account SID, Auth Token, Messaging Service SID / sender numbers) are stored in encrypted system parameters or a dedicated config model, never hard-coded. Everything is exposed over Odoo's XML-RPC / JSON-RPC API too, so external systems can queue SMS through the same audited pipeline.

Bulk and marketing SMS is built for operators: import recipients from Excel/CSV, map columns to partner fields, personalize with Jinja/QWeb-style placeholders (customer name, order reference, amount), preview segment counts and estimated Twilio cost, then send in throttled batches that respect Twilio rate limits and your Messaging Service. Delivery, opt-out (STOP/UNSUBSCRIBE handling) and status data flow back into Odoo for reporting via QWeb PDF/list views and standard Odoo pivot/graph analytics.

Compatible with Odoo 17, 18 and 19 on both Community and Enterprise (Enterprise unlocks tighter integration with the native SMS marketing app where you have it). ECOSIRE handles the __manifest__.py, models, views (XML + OWL where interactive), security, controllers, tests and deployment — and stays on to support and update it.