For the better part of a decade, the telephony corner of Odoo has lived under a label that aged faster than the feature set it described. “VoIP” made sense when Voice over IP was a distinction that mattered — when calling from a computer instead of a copper line was still novel enough that the acronym carried useful information. In 2026, that distinction has long since collapsed. Every call is IP. The name no longer tells anyone anything.
Odoo has quietly agreed. The entire VoIP application has been rebranded to Phone across the documentation, and the change is more than cosmetic. Files have been moved, URLs have been redirected, internal references have been rewritten, and the widget that lets employees click a number to call has been renamed along with everything around it. The module that ERP administrators spent years explaining as “Odoo’s VoIP integration” is now simply Odoo Phone.
What Actually Changed
On a technical level, this is the kind of rename that touches everything without breaking anything. The top-level folder under Productivity that used to be called voip is now phone. The main module guide that was once voip.rst is now phone.rst. The click-to-call sidebar that employees open to place calls — previously documented as the VoIP widget — has been renamed to the Phone widget. Each of those renames cascaded into dozens of supporting files, including the provider integration guides for Axivox, DIDWW, and OnSIP, the workflow pages for sales calls and support calls, and the devices integrations page that walks administrators through pairing desk phones and headsets.
The scope is the kind that makes technical writers wince. More than seventy files moved in a single change: roughly seventeen reStructuredText pages and more than fifty image assets distributed across the Axivox, DIDWW, OnSIP, phone widget, devices integrations, sales calls, and support calls subdirectories. Every internal cross-reference in the documentation that used to point at voip/axivox or voip_widget now points at phone/axivox and phone_widget. Every image path inside the affected pages has been updated so the rendered docs still load the right screenshots after the move.
One file stayed behind. The top-level productivity.rstpage, which lists every app in the productivity suite, was not moved — it was only edited to point its table of contents at the new Phone location. That is the correct call. The productivity index belongs at the root of the productivity folder, not inside the Phone subdirectory.
The Redirects That Keep Links Alive
A rename of this scale would normally break every external link that ever pointed at an Odoo VoIP documentation page. Blog posts, Stack Overflow answers, internal wikis, Slack threads, and customer support macros all contain frozen URLs that assume the old paths still work. Odoo shipped the change with a redirect map that catches those requests and forwards them to the new locations.
The redirect list covers around twenty-one path mappings that correspond one-to-one with the moved files. The main VoIP guide redirects to the main Phone guide. Each Axivox sub-page — the configuration walkthrough, the dial plans guide, the call queues setup, the conference calls instructions, the caller ID configuration, the voicemail setup, the user management reference — redirects to its counterpart under phone/axivox. The DIDWW and OnSIP provider guides redirect similarly. The widget page redirects to the phone widget page. Even the anchor links inside the widget troubleshooting section, which previously lived at voip/voip_widget/troubleshooting_voip, now resolve to phone/phone_widget/troubleshooting.
For administrators who have built runbooks or internal training materials that link into the Odoo docs, nothing should have broken overnight. The redirects handle the transition quietly, and the only thing that changes is the URL that appears in the browser bar after the forward.
Why the Rebrand Matters
It is tempting to read a rename as a cosmetic exercise, but this one fits into a broader pattern in how Odoo has been positioning its communication tools. “VoIP” framed the module as a technical integration — an add-on that bridged Odoo to an IP telephony provider for the benefit of companies that had already decided to run a softphone setup. “Phone” frames it as a product. It is the telephony application you use inside Odoo, regardless of which provider sits behind it or whether you are calling from a browser tab, a desk handset, or a headset paired with a computer.
That product framing changes who the documentation is written for. The old VoIP guide started from the assumption that the reader knew they wanted a VoIP solution and needed help wiring it into Odoo. The new Phone guide covers the same ground, but the name makes it discoverable for readers who are simply looking for the phone feature without knowing or caring about the protocol underneath. A sales manager searching the docs for “how does the phone work in Odoo” will now find the right page on the first attempt.
What Stays the Same
The features inside the renamed module are unchanged. Axivox remains the primary documented provider, with its full set of configuration sub-pages covering dial plans, queues, voicemail, caller ID, and user management. DIDWW and OnSIP remain as alternative provider integrations with their own guides. The widget that employees use to place calls from inside any Odoo view still works the same way, still tracks call activities against records, and still integrates with CRM leads, Sales opportunities, and Helpdesk tickets. The sales calls and support calls workflow guides still describe the same end-to-end processes.
The devices integrations page, which walks through pairing desk phones, headsets, and deskphone hardware with the widget, has been moved under the Phone namespace but otherwise remains the same reference. Anyone who had it bookmarked will land on the new URL automatically thanks to the redirects, and the content inside is identical.
A Better Name for a Grown-Up Module
Odoo’s Phone module is no longer something that needs to be explained as a technical option. It is a feature businesses expect their ERP to have, and the documentation now treats it that way. The shift from an acronym that stopped being useful to a plain word that describes what the tool does is exactly the kind of small, overdue change that makes a mature product feel more like a product.
For teams that use Odoo to automate workflows that include calling customers — sales sequences that dial down a lead list, support queues that route incoming calls to available agents, follow-ups that need a call activity attached to a record — the rebrand will not change anything about how those workflows run. But it will change how new administrators find the setup guides, how documentation links hold up over time, and how the telephony piece of Odoo fits alongside the rest of the productivity suite. After a decade of being the module with the technical name, Phone finally has a name that matches what it does.
It is the kind of housekeeping that is easy to overlook in a release notes scan, but worth paying attention to. When a product stops hiding behind acronyms, it is usually a signal that the team building it has decided the feature is ready to stand on its own.