DECT REPLACEMENT
Replacing the DECT Estate
DECT was the right answer to a question asked twenty years ago: how do we make a desk phone walk around a building? The handsets, the base stations and the repeaters are still there — ageing, out of support, and stopping dead at the edge of the car park.
Meanwhile everyone carrying a DECT handset is also carrying a mobile. This use case sets out what changes when the business line moves onto the phone that already works everywhere.
At-a-Glance
- Applies to
- Any site running legacy DECT
- Typical settings
- Warehouses, campuses, retail, offices
- Replaces
- DECT handsets, base stations, repeaters
- Deployment
- Business line on mobile handsets by eSIM
- Platform
- The organisation's existing UC platform
Solution Highlights
- Same extension, national coverage
- No base stations or repeaters to maintain
- Calls stay on the UC platform's record
- Existing numbers and routing survive
The Challenge
A DECT estate fails slowly and expensively. Coverage was designed for the building as it was, not as it is; the dead spots are known by folklore; and every extension means another base station on another survey. Handsets break, batteries fade, and replacements for discontinued models turn into a hunt.
The range problem is the sharpest. The moment work steps outside — a yard, a second building, the walk between sites — the handset in the person's pocket is a brick, and the call lands on a personal mobile instead.
The Solution
Each DECT user gets the same thing they had — an extension of the phone system that moves with them — delivered instead as a business line on a mobile handset by eSIM. Their own phone where that suits the role; a rugged device where the environment demands it.
The extension keeps its number, its hunt groups and its place in the call flow, because the line is a full member of the same UC platform. What changes is the radio underneath: mobile network coverage instead of a web of base stations, which means the yard, the far building and the road between sites are all inside range.
The DECT infrastructure is then retired rather than renewed — no surveys, no repeaters, no discontinued-handset hunts, and one less system for IT to keep alive.
What Changes
The first change is coverage. The dead spots folklore mapped simply stop existing, because the line works wherever there is mobile signal — including off site.
The second is the maintenance burden. An ageing radio estate with its own failure modes is replaced by nothing: no base stations, no batteries in a drawer, no renewal quote.
The third is continuity for everyone else. Numbers, groups and routing carry over, so the switchboard, the callers and the call records never notice the handset changed.

Key Changes
- Coverage beyond the building for the first time
- DECT hardware retired, not renewed
- Extensions and routing carried over intact
- One less estate for IT to maintain
Assessment
Nine questions about your own estate. The ones you can't answer are the ones worth looking into.
How it works today
- How many DECT handsets and base stations are still in service?
- Where does coverage actually stop, and who works beyond it?
- Which models are already discontinued or out of support?
What it is costing
- What does the estate cost a year in maintenance and replacements?
- What would the pending renewal or expansion quote come to?
- How many calls fall back to personal mobiles at the coverage edge?
What would change
- Which user group would you migrate first?
- Which roles need a rugged handset rather than their own?
- What could IT stop maintaining a year from now?
DECT solved mobility inside a building; the work stopped staying inside the building. Moving those extensions onto mobile handsets keeps everything the phone system knows — the numbers, the groups, the records — and swaps the ageing radio layer for one that already covers the country.
The renewal quote you do not sign is the business case.
Looking Ahead
Learn More
Visit tango-networks.com or contact your local Tango Extend partner
for a personalised demonstration.
Version 1.0 · August 2026
