Sales teams that run their voice on RingCentral usually keep texting outside of Odoo — in the softphone, on a personal handset, or in a spreadsheet nobody reads. The result is a broken record of truth: a rep fires a follow-up text after a call, the lead replies, and none of it lands on the crm.lead or res.partner timeline where the next person to touch the deal would look. Odoo's core sms module can send text, but it is wired to a single in-app messaging provider and does not know how to speak to your RingCentral account, route from a per-user business number, capture inbound replies, or reconcile delivery receipts. Out of the box you get one-way blasts on someone else's carrier, not a two-way conversation tied to the sales record.

ECOSIRE builds a clean-room Odoo extension that treats RingCentral as a first-class SMS transport inside CRM. We add a Send SMS action on res.partner and crm.lead that composes through the RingCentral SMS/MMS REST API using an OAuth-authenticated per-user sending number or extension, so each rep texts from their own business line and every message is attributed to the right salesperson. Outbound and inbound messages are persisted to a dedicated conversation model and mirrored into mail.thread, so the full history renders in the chatter alongside calls and emails. Inbound replies arrive via a RingCentral webhook to a controller route that authenticates the notification, matches the sender against phone_validation-normalized numbers, and appends the message to the matching contact or lead — creating a subtype-tagged chatter entry and an activity where you want a human to respond. A per-contact threaded view shows the back-and-forth as a single conversation rather than scattered log lines.

Technically the build is grounded in real Odoo primitives. New models subclass models.Model with @api.depends computes for message status roll-ups and thread counts; templates carry merge fields resolved against the record so Hi {{ object.name }}, your quote is ready renders per recipient. Bulk send runs from a list-view server action that iterates the selected records, applies opt-out and suppression checks, and writes one log line per message so a partial failure is visible instead of silent. Delivery status (queued, sent, delivered, failed) is reconciled either from RingCentral message-status callbacks or a scheduled ir.cron poll, and surfaced as a status badge on each message. STOP-keyword and opt-out handling maintains a suppression list that both the single-send and bulk paths honor, so you stay compliant. Access is locked down with ir.model.access.csv plus record rules — reps see and send on their own records, managers see the team — and everything is exposed to your other systems through Odoo's XML-RPC/JSON-RPC API. It runs on Community or Enterprise and we target Odoo 17.0, 18.0, and 19.0; the deliverable is pinned to the version you confirm.

Because this is made to order, nothing ships until we agree on scope. After a short scoping call we confirm your RingCentral app credentials and number routing, the templates and opt-out language you need, and any bulk-send governance, then build against your target Odoo version, run UAT on a staging database, and install to production with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company sending-number routing, deeper MMS/media handling, additional integrations, or migration of existing message history increases the quoted scope. You receive a firm fixed quote after the scoping call, never a surprise.