For years, Odoo’s telephony story was straightforward and limited. You got a VoIP integration that could place and receive calls through a SIP provider, log them against contacts, and maybe trigger a popup when someone dialed in. It was functional — barely — and it was nobody’s idea of a phone system. If your business needed call routing, an IVR menu, or even basic after-hours voicemail, you were still writing checks to a separate PBX vendor.
Version 20 changes the math. The renamed Phone app now ships with a visual call flow designer that lets you build complete call routing logic as a diagram of connected nodes. It’s not a minor enhancement bolted onto the side of VoIP — it’s a PBX layer built directly into the ERP, and it handles the scenarios that previously required dedicated hardware or a third-party cloud phone service.
Routing Calls With Boxes and Arrows Instead of Config Files
The call flow builder presents routing logic as a canvas of interconnected nodes. You start with an incoming call entry point and drag out the path it should follow. Each node represents a routing decision or destination: extensions, time-based conditions, ring groups, IVR menus, call queues, and voicemail boxes. Connections between nodes are drawn visually, and the entire flow reads like a flowchart — because it is one.
The time condition node alone eliminates a surprising amount of configuration pain. You define business hours directly on the node, and calls arriving outside those hours automatically follow a different branch — typically straight to voicemail or a reduced-staff queue. No cron jobs, no server actions, no custom code. The visual layout makes the logic auditable at a glance, which matters when you’re troubleshooting why a caller ended up in the wrong department at 5:01 PM on a Friday.
IVR Menus That Actually Connect to Your Business Data
Building an IVR menu in a traditional PBX means recording audio prompts and mapping DTMF tones to extension numbers in a configuration interface that hasn’t changed aesthetically since 2004. Odoo’s approach ties the IVR directly into the call flow canvas. Each menu option is a numbered branch that connects to another node — an extension, a queue, a nested submenu, or a voicemail box.
The real advantage isn’t visual, though. Because the IVR lives inside the ERP, menu options can route based on data that a standalone phone system would never have access to. A caller pressing “2 for support” can land in a queue that’s staffed according to the current HR schedule, not a static extension list that someone forgot to update three months ago.
Every Node Creates Records Automatically
This is the detail that separates the feature from a generic diagramming tool with telephony bolted on. Every node in the call flow builder can create its corresponding Odoo record on the spot. Drop a queue node onto the canvas, and Odoo creates the queue record behind it. Add an extension node, and the extension is provisioned. Voicemail boxes, ring groups, IVR definitions — the flow diagram isn’t a blueprint you configure separately; it is the configuration.
For businesses that previously maintained parallel setups — one in the PBX admin panel and another in the ERP for logging purposes — this collapses two systems into one. When you reorganize a department in Odoo, the call routing can follow without a separate change request to the telecom vendor.
The Lock-In Trade-Off Nobody Will Mention at the Demo
There’s a significant caveat worth addressing directly. The call flow designer and its PBX capabilities are currently tied to Odoo’s own telephony service. If you’re running a third-party SIP trunk or using an existing cloud PBX provider, you don’t get the call flow builder — you get the same basic VoIP integration from previous versions.
This is a deliberate product decision, not a technical limitation. Odoo controls the entire stack when you use their telephony service, which means they can guarantee that the visual routing actually works as drawn. Opening the PBX layer to arbitrary SIP providers would introduce compatibility variables that are genuinely difficult to manage. Whether that trade-off is acceptable depends entirely on your organization’s existing telecom commitments and how much you value having phone routing live inside the same system as your CRM, helpdesk, and HR records.
Who This Actually Matters For
Small and mid-sized businesses that are already running Odoo and paying for a separate phone system are the obvious audience. If you’re spending $30 per seat per month on a cloud PBX that your team configures through a completely disconnected admin panel, consolidating into Odoo’s Phone app starts making financial and operational sense — provided you can live within Odoo’s telephony ecosystem.
For larger enterprises with entrenched Avaya, Cisco, or Teams Calling deployments, this isn’t a rip-and-replace proposition. But for the segment of the market that treats their phone system as an afterthought — the companies still running an ancient FreePBX box under someone’s desk — Odoo just offered a path to a modern phone system that doesn’t require a second vendor, a second admin interface, or a second monthly invoice.
The call flow designer is the kind of feature that redefines what category Odoo’s Phone app competes in. It’s no longer a VoIP add-on. It’s a business phone system that happens to share a database with your entire operation.