Sales and support teams that run Odoo lose real money in the gap between the phone system and the CRM. Reps dial from a softphone in one window and log the outcome by hand in another; inbound calls ring with no idea which res.partner or crm.lead is calling; SMS conversations happen entirely off-system, invisible to managers and absent from the customer timeline. Odoo core ships phone and mobile fields and a basic VoIP widget, but out of the box it does not synchronize your contacts to the carrier, screen-pop an inbound caller, thread SMS onto the record, or attach the call recording where the next rep can find it. The result is missed follow-ups, unlogged calls, and a customer 360 that is missing every conversation that happened by voice.

ECOSIRE builds a dedicated telephony connector that closes that gap. We ship a new Odoo module — its own __manifest__.py declaring dependencies on mail, contacts, crm, and optionally helpdesk/sale — that authenticates to your cloud phone provider over its REST API and webhooks. On the outbound side we register a click-to-call widget on phone/mobile fields so a rep dials in one click; on the inbound side an authenticated webhook controller receives the ring event, resolves the caller number against res.partner and crm.lead using normalized E.164 matching (a stored @api.depends compute field keeps a search-indexed canonical number), and screen-pops the matching record. Every completed call becomes a mail.message on the record's chatter with direction, duration, agent, and a link to the conversation recording; a scheduled or webhook-driven job fetches the recording URL once the provider makes it available.

Contact sync runs two ways through a mapped model (telephony.contact.sync with external-id bookkeeping) so a new res.partner reaches the carrier address book and carrier-side edits flow back without clobbering local data — conflict rules are agreed during scoping. SMS is threaded as a first-class conversation: inbound and outbound messages post to chatter and, where you want it, feed Odoo's Discuss so managers see the whole thread. Security is real, not an afterthought: dedicated ir.model.access.csv entries and record rules keep recordings and call logs visible only to the right sales team or helpdesk group, webhook endpoints are secret-verified, and API credentials live in system parameters, never in source. Everything is delivered against Odoo 17.0, 18.0, or 19.0, Community or Enterprise (we flag any capability that depends on an Enterprise-only app during scoping).

Because this is build-to-order, nothing is downloaded and switched on today. We start with a scoping call, agree the exact call, SMS, sync, and logging behavior for your edition and version, then build, test on a staging database, and install with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company routing, additional phone numbers or carrier accounts, deeper Helpdesk/Sales integration, localization, and the volume of historical call data to migrate all increase the quoted scope. You receive a fixed quote after the scoping call.