Background
An enterprise workforce relied on a fragmented set of communication tools — desk phones, mobile, video conferencing, instant messaging, all separate. Mobility was painful; cost was high; the experience was inconsistent.
The leadership team wanted to consolidate into one platform that would carry voice, video, chat, and collaboration, while keeping the existing PSTN telephony in place.
The task
Replace the legacy IP-telephony estate with Microsoft Teams Phone, integrated with Etisalat PSTN, and migrate the workforce without disruption.
The solution
A direct routing integration with Etisalat PSTN was designed and tested, preserving existing numbers and dial plans while bringing voice into Teams.
A phased migration moved business units onto Teams Phone in waves, paired with training and a residual desk-phone capability for the small number of edge cases.
The result is one application for voice, video, chat, files, and collaboration — and a mobile workforce that has parity with the desk experience.
What Microsoft Teams with Telephony for Enhanced Mobility shows
This engagement matters because improve mobility and connectivity with microsoft teams phone required more than a technical deployment. The work combined Enterprise Systems and Smart Operations with an operating cadence the client could keep using after the project team stepped back.
The reusable pattern is the discipline behind the delivery: understand the baseline as it really is, decide what must be standardised, integrate with the systems that already carry the work, and measure whether daily operations become clearer, faster, or more reliable.
For similar organisations, the first question is not which tool to buy. It is who owns the outcome, which data is trusted, how adoption will be reinforced, and what evidence will prove the engagement changed the operation.
The follow-through is where many projects lose value. I look for early signs that the work has landed: the management meeting changes, the process owner is clear, the data appears at the point of decision, and the team knows what to do when requirements shift.
Transferable lessons
- Start from the operating problem before choosing a platform or vendor.
- Design governance, ownership, and integration together, because none of them can compensate for the absence of the others.
- Leave behind a cadence for measurement and improvement, not a new system waiting for another project to make it work.
Implementing Microsoft Teams with Etisalat PSTN
Assess current telephony, design the Teams Phone target state, integrate with Etisalat PSTN, migrate in phases.
- 01
Inventory current telephony estate, dial plans, and call flows.
- 02
Configure Teams Phone, integrate with Etisalat PSTN via direct routing.
- 03
Roll out in phases, with user training and concierge support.