Sales and support teams that live in Odoo lose context the moment a call happens outside it. Reps dial from a softphone in another browser tab, calls never make it into the mail.thread history, and there is no reliable way to tie call duration, recordings, or missed-call follow-ups back to the crm.lead or helpdesk.ticket that triggered them. Odoo core has no native concept of a cloud PBX: there is no telephony model, no webhook receiver for call events, and no click-to-dial. Managers end up reconstructing call activity from spreadsheets and memory, and every "did we call them back?" question turns into a manual investigation.

This is a build-to-order integration that ECOSIRE designs and develops against your specific cloud telephony account. We create a dedicated telephony module with its own __manifest__.py declaring dependencies on mail, crm, and (optionally) helpdesk, plus a res.config.settings extension that securely stores your API ID, API token, and per-user agent numbers. A new voip.call.log model (extending models.Model) captures direction, from/to numbers, duration, timestamps, call status, recording URL, and a Reference field that links each call to the matching res.partner, crm.lead, or ticket. Compute fields with @api.depends derive talk-time and answer/miss classification, and every logged call posts a message into the linked record's chatter so the full timeline lives where your team already works.

Technically, the integration works in both directions. A hardened controller exposes an authenticated webhook endpoint that receives call events from the provider in near real time, verifies the signature, matches the phone number to an existing contact (creating a lightweight lead when configured to), and writes the log. Outbound click-to-dial is delivered through an OWL widget and a JSON-RPC method that triggers the call from the record view. Number matching is normalized to E.164 so extensions and country prefixes reconcile cleanly. Access is governed by ir.model.access.csv plus record rules so agents see only their own calls while managers see the team, and an optional automated action (or scheduled ir.cron) creates a follow-up mail.activity on every missed inbound call so nothing slips.

Delivery is build-to-order, not an instant download. We start with a scoping call to confirm your Odoo version and edition, which events you want captured, the objects calls should attach to, and how number matching and lead creation should behave. You approve a fixed quote and scope, we build and test on a staging database, you run UAT, and we deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope, depending on complexity and integration depth. Community and Enterprise are both supported; helpdesk-linked calling and some UI hooks depend on the Enterprise apps you run, which we confirm during scoping.

Pricing starts from $999 (indicative, single-company base scope); multi-company routing, additional integrations, deeper recording/transcription handling, custom reporting, and historical call-data migration increase the quoted scope. The scoping call produces a firm fixed quote before any build work begins.