Email is not an operational system. When the primary mechanism for keeping wholesale partners informed is a message to an account manager, the information has to travel through several unreliable human steps before it reaches the place that matters. It often doesn’t make it.
There’s a pattern of OLO management that’s so common it barely gets noticed. A withdrawal programme is announced. An email goes to the OLO account manager. A capacity upgrade is scheduled. An email goes to the OLO account manager. A fault affects the wholesale area. An email goes to the OLO account manager, usually after the fact.
At the host operator, this registers as “OLOs have been notified.” At the OLO, what actually happens is rather different. The email goes to the account manager. The account manager may or may not relay it to the relevant operational team. The relevant operational team may or may not update their systems. The support team may or may not know about it when the customer calls.
Email is not an operational system. It is a communication channel between humans, with all the reliability that implies. Using it as the primary mechanism for keeping wholesale partners operationally informed is a choice with predictable consequences.
The information that gets lost in transit
When a withdrawal notification email lands in an OLO account manager’s inbox, the information it contains needs to travel through several steps before it reaches the place where it can actually prevent problems. Account manager reads it. Forwards to the operations team. Operations team raises a task to update the ordering system. Someone does the update. Or they don’t, because the deadline seemed far away or the workload was high that week.
The result: copper orders continue to be placed against addresses in the withdrawal zone, not because the OLO is ignoring the notification but because the notification never reliably translated into a system constraint. The host operator sees this as non-compliance. The OLO sees it as an operational failure on their side that they weren’t given the tools to prevent. Both are right. The underlying cause is that the notification was designed for human processing, not for system integration.
The relationship cost
OLOs who operate in a state of information asymmetry — knowing less about what’s happening on the network they depend on than the host operator’s own teams — make a reasonable adjustment to compensate. They pad their own SLA commitments to customers. They over-provision support capacity to handle unexpected failures. They develop informal relationships with contacts in the host operator’s NOC because the formal channels aren’t reliable enough.
All of this is friction. Friction that makes the wholesale relationship feel harder than it needs to be, and that accumulates into a commercial relationship that’s more adversarial than it should be. The OLO that feels like a professional partner — well-informed, properly tooled, treated with the same operational respect as an internal team — is a fundamentally different commercial relationship from the OLO that has to call to find out what’s happening.
What the operational alternative looks like
The shift from email-based OLO management to systems-based OLO management isn’t dramatic. It doesn’t require rebuilding the wholesale relationship from scratch. It requires connecting the host operator’s operational systems to a portal that the OLO can actually use.
When a withdrawal zone is defined in the OSS, the OLO portal shows it automatically. OLO ordering systems can query the portal to check address status before placing an order. No email required. No translation step. The constraint is in the system.
When a fault affects OLO customer addresses, the portal reflects it in real time. The OLO support team can see it before the customer calls. The automatic notification that goes to the account manager is supplementary — a courtesy, not the primary channel.
When a maintenance window is scheduled, it appears in the portal with enough lead time for the OLO to communicate to their customers. The account manager gets an email too, but it’s the portal entry that actually matters operationally.
None of this requires the OLO to trust the host operator more. It requires the host operator to give the OLO the tools to verify. That’s a much more sustainable foundation for a wholesale relationship.