A made-to-order Odoo integration that wires your cloud phone system into CRM, Contacts, and Helpdesk — click-to-call, inbound screen-pop, SMS threads, two-way contact sync, and recording links logged straight onto the record. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifeste de l'app
Conçu autour de votre flux de travail
A made-to-order Odoo integration that wires your cloud phone system into CRM, Contacts, and Helpdesk — click-to-call, inbound screen-pop, SMS threads, two-way contact sync, and recording links logged straight onto the record. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0.
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
ECOSIRE la développe, la configure et l'installe sur votre Odoo.
Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.
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 2–4 weeks from confirmed scope. Pricing starts from $249 (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.
Runs the Odoo CRM and needs every call and SMS logged automatically against the lead or contact, so pipeline reviews reflect actual outreach and no follow-up slips through the cracks.
Wants reps to dial with one click from the lead they're working, get an instant screen-pop on inbound calls, and stop tabbing between a softphone and Odoo to log outcomes by hand.
Needs inbound calls tied to the right Helpdesk ticket or partner, recordings attached for quality review, and SMS threads visible to the whole team instead of trapped in a separate phone app.
Responsible for a clean, upgrade-safe deployment: proper access rules on recordings, secrets kept out of source, webhooks secured, and a module that survives version upgrades across 17/18/19.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Nature of solution | Made-to-order module scoped, built, installed, and supported by ECOSIRE | In-house or freelancer build from scratch | A typical off-the-shelf apps.odoo.com module | |
| Inbound screen-pop | Webhook-driven pop with E.164 matching against partners and leads | Possible, but you design and build the matching yourself | Varies; often carrier-specific and rigid | |
| Automatic call & SMS logging | Calls and SMS posted to chatter with direction, duration, and recording link | Whatever you have time to build and maintain | Basic call logging; SMS threading often absent | |
| Two-way contact sync | Mapped sync model with external ids and agreed conflict rules | Must be designed, built, and hardened by your team | One-way or limited, with fixed field mapping | |
| Odoo version & edition fit | Built for your exact 17/18/19, Community or Enterprise | Depends on your developer's coverage | Only the versions the vendor chose to publish | |
| Security & access control | Dedicated access rules, record rules, secret-verified webhooks, secrets in system parameters | Only as strong as your build discipline | Generic defaults; rarely team-scoped | |
| Source code & ownership | Full source plus Git repository handover | You own it, but you also built and must maintain it | Often obfuscated or licence-locked | |
| Support & upgrades | Post-go-live window plus optional paid maintenance and version upgrades | You are the support team | Vendor-dependent; upgrades not guaranteed |
This is a build-to-order module, so it is not an instant download. Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we agree the exact call, SMS, sync, and logging behavior, then build, test on staging, and install. Complex multi-company or high-volume data-migration scopes can extend the timeline, which we state in the quote.
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Some capabilities depend on Enterprise-only apps (for example certain Helpdesk features); we flag anything edition-specific during scoping so there are no surprises.
Pricing starts from $249 (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 increase the quoted scope. You get a fixed quote after the scoping call — the from-price is a starting indication, not the final number.
Every build includes a post-go-live support window for defect fixes and configuration adjustments; the exact duration is stated in your quote. Because you receive the full source and Git repository, you own the code. We also offer paid maintenance for Odoo version upgrades (for example moving from 18.0 to 19.0) and for adding new capabilities later.
No. We connect your existing cloud phone provider to Odoo over its REST API and webhooks. You keep your phone system and numbers; the connector adds click-to-call, inbound screen-pop, automatic call and SMS logging, contact sync, and recording links inside Odoo.
Yes. We add dedicated `ir.model.access.csv` entries and record rules so call logs and recordings are only visible to the relevant sales team or helpdesk group. Webhook endpoints are secret-verified, and API credentials are stored in system parameters (`ir.config_parameter`), never hardcoded in source.
Yes, within scope. We can back-fill historical call records and run an initial two-way contact sync between Odoo and your carrier address book. The volume of historical data and the conflict-resolution rules for existing contacts are agreed during scoping and reflected in the quote.
A made-to-order Odoo integration that wires your cloud phone system into CRM, Contacts, and Helpdesk — click-to-call, inbound screen-pop, SMS threads, two-way contact sync, and recording links logged straight onto the record. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0.