Odoo ships a native SMS layer (the sms.sms model, the "Send SMS" composer, and SMS steps in Marketing Automation), but out of the box it is wired to Odoo's own IAP SMS service. If your organization is already standardized on Vonage (formerly Nexmo) for deliverability, pricing, sender-ID governance, and unified reporting, that native path forces you off your existing carrier relationship, gives you no control over the underlying route, and cannot honor your registered alphanumeric sender IDs or country-specific compliance settings. The moment you need Vonage-specific features — messages-API delivery receipts, per-country sender IDs, or account-level throughput — Odoo's built-in IAP gateway runs out of road.

We build a dedicated gateway module that overrides Odoo's SMS transport so every message the system already knows how to send — order confirmations, marketing blasts, OTPs, reminders — leaves through the Vonage Messages/SMS API instead of Odoo IAP. Technically, the module extends the sms.api / sms.sms send path and introduces a vonage.account model holding your API key, secret (or JWT application credentials), and default sender ID, all secured with ir.model.access.csv and record rules so only authorized users touch credentials. Outbound calls are made server-side with proper retry and rate handling; Vonage delivery-receipt webhooks are received on a JSON-RPC/controller endpoint and written back to a state field (sent, delivered, failed, with the Vonage error code) via a compute chain so agents see real delivery status in the chatter and in list/kanban views, not just "queued".

On top of the transport we build the pieces your persona actually asked for: a bulk-vs-transactional routing policy (queued through a scheduled action / cron for large sends, immediate for OTPs and order events), sender-ID configuration per country or per company in a multi-company setup, and template support that reuses Odoo's mail.template / QWeb rendering so placeholders like ${object.partner_id.name} resolve exactly as they do for email. Order-event automation is delivered as Odoo Automated Actions (base automation) triggered on sale.order, stock.picking, or account.move state changes, so "your order shipped" texts fire without anyone clicking send. Everything is exposed to your other systems through the standard Odoo XML-RPC/JSON-RPC API, so external apps can trigger sends through the same governed gateway.

Because this is build-to-order, nothing is a shrink-wrapped download. After a short scoping call we confirm exact triggers, sender IDs, target countries, and Odoo edition (Community vs Enterprise changes what Marketing Automation hooks are available), then build against your Odoo 17.0, 18.0, or 19.0. You get the module built for your version, installed and configured against your Vonage account, tested on a staging database, and handed over with source and docs. Typical delivery is one working week from confirmed scope, and we support it after go-live.