IP Telephony & Unified Communications Optimisation · Technical White Paper
IP Telephony & Unified Communications Optimisation
A method for tendering voice and connectivity as one operating model — specifying outcomes rather than prices, modelling escalation across the contract term, and controlling a migration without creating downtime.
4–5 · Tender design
Specify the outcome, not a better price
The requirement deliberately specified outcomes rather than asking suppliers to beat the incumbent. It requested differentiated connectivity by site, hosted telephony, multiple handset types, soft phones, voicemail, usage reporting, auto-attendant, call recording, number porting, routers, switches, service-level commitments, monitoring, implementation planning, power-protection options and alternative commercial structures.
The comparison framework then placed price alongside proof of regulatory standing, customer support, training, uptime, security reporting, implementation planning, itemised billing, references, device quality, internet performance and the SLA.
Price was one criterion inside an operating model, rather than the criterion with some qualitative notes attached.
8 · Commercial modelling
Why the headline quote was not enough
Four things sat between the quoted rental and the real cost: a legacy settlement obligation on financed equipment, separate SLA and call charges, a line-rental treatment that changes later in the contract, and escalation structures that differ by scenario.
Each of those can move the outcome more than the rental difference being compared. Modelling only the opening rental produces a confident answer to the wrong question.
11 · The escalation trap
In the latest quote set, lower opening rentals were paired with higher escalation. The cheapest month one was not the cheapest contract.
Comparing the full path of charges rather than the first invoice is therefore not a refinement — it is the difference between selecting the best option and selecting the one that presents best.
12 · Service levels
A service level with no consequence is a statement of intent
Uptime, fault logging, mean time to respond, mean time to repair, penalties, reporting and monitoring together determine whether a nominal service level has any commercial effect.
The selected proposal included punitive provisions under which qualifying non-performance generates a credit against the affected site's charge. That is what converts an SLA from a paragraph into a control.
13 · The migration rule
Number porting is one of the highest operational risks in a PBX migration, because the voice identity of the organisation moves at the same time as the platform beneath it.
Separate commercial termination from technical cut-over. The old service should remain available until the new route, equipment and porting status are all controlled.
Cancelling the incumbent first and hoping the new platform becomes ready before the numbers move is how an organisation creates its own downtime. Here, porting was coordinated with installation, and redirection was planned as a continuity control for any site that could not be completed as expected.
14–15 · Implementation governance
Controls applied before site sign-off
- Serial-number audit. Equipment make, model, quantity and serial number recorded before a site was signed off — so the equipment register and the invoice cannot drift apart.
- Proof of delivery tied to installation. Not to pre-delivery. Equipment sitting in a store room is not an implemented site, and should not be billed as one.
- Implementation as its own workstream. Treated separately from the commercial award, with its own sequencing, rather than assumed to follow from signature.
- Ownership after the rental period. Contemplated explicitly in the contract conditions, rather than left to be discovered at the end of the term.
17 · What can be claimed
A scoped comparison, honestly labelled
The defensible headline is the 16.5% reduction on the selected opening finance rental, against the comparator used in the retained commercial model — carrying the qualification that legacy settlement, SLA and call charges, and later connectivity-rental treatment all sit outside it.
No full lifecycle percentage is stated, because the evidence does not support one. The deeper result was the reconstruction and control of the voice-and-data architecture: an estate that is documented, a service level with teeth, a migration that did not create downtime, and an equipment register that matches what is installed.