
The Job Runs on Phones the Firm Does Not Control
The Problem
The People Who Run the Project Are the Hardest to Ring
Everyone the client and the suppliers actually need sits outside the firm's phone system:
- Project managers — covering several sites, reachable only on a personal mobile that half the supply chain has saved
- Site managers — somewhere on a site the radio does not fully cover, with the site cabin phone ringing into an empty room
- Subcontractors and suppliers — holding a different number for every person on every job, none of them the firm's
- The client — ringing a number that belongs to a person, not the project, and starting again every time the team changes
- Handover — a round of new-number emails to every supplier, every time staff move between jobs
The Impact
Three Things It Costs You
Reachability. A delivery change that reaches the wrong person costs a day; a decision that reaches nobody costs more. The project has no number that reliably finds a person.
Continuity. Staff move between jobs constantly. When the client's and suppliers' saved numbers belong to people rather than the project, every move breaks the chain of contact.
The record. Instructions, variations and delivery changes agreed by phone are precisely the traffic that ends up in dispute — and when they happen on personal mobiles, the account of a decision comes down to memory against memory.
The Solution
One Project Number, on the Phones People Already Carry
Project and site managers carry a business line on their own handsets, delivered by eSIM; site roles that need a tougher device get the same line on a rugged handset. Nothing to install, and no application to open with gloves on.
Calls to the project reach the person covering it today. A delivery driver, a subcontractor or the client rings one number and lands on whoever can act — not a voicemail on a phone left in a site cabin. Outbound, every call carries the firm's identity.
It runs on the phone system the firm already has — Microsoft Teams Phone, Cisco Webex Calling, BroadWorks, NetSapiens, Zoom Phone and others — so every conversation about a variation, a delay or a delivery sits on the platform's record. When the account of a decision is questioned months later, there is a log rather than a memory.
Take it further
Recommended resources
The Proof
Use Cases: Construction
Start with one project and the roles the client actually rings.
- Site and Project Communications — a project number that outlives the team, managers reachable on any site, and phone-agreed changes retrievable afterwards.
- Thirty Use Cases — a compendium across sectors and working patterns.