O2 porting snafus leave businesses stranded, sparking doubts
A routine phone line transfer turned into a six-day ordeal for one Spanish business owner, exposing a vulnerability in O2’s porting process and raising questions about the operator’s risk assessment protocols. Jose A. González, head of a commercial agency, found himself locked out of communication with his sales team after attempting to migrate three lines to O2, a situation he aired publicly on social media platform X, formerly Twitter.
The risk assessment bottleneck
The issue, according to O2, stems from the company's risk assessment scoring system—a standard practice in the telecom industry designed to flag potentially fraudulent or high-risk accounts. But in González’s case, the process appears to have ground to a halt, leaving him and his team effectively disconnected. While O2 assures it's “trying to review it as soon as possible,” the delay highlights a potential flaw in the system: the shift from automated porting to manual validation when a risk assessment is triggered.
The company claims this manual intervention is necessary to prevent fraud and protect both O2 and its customers. However, the prolonged wait—six days and counting—suggests a need for streamlining the process, especially given the impact on business operations. The incident underlines a recurring issue in the Spanish telecom sector: the often-opaque and slow-moving porting process, despite assurances of a maximum 48-hour turnaround.
Beyond risk assessment scoring, O2 confirms that other data discrepancies can also cause delays. These include mismatched ownership details, incorrect ICC (Integrated Circuit Card) codes on SIM cards, and inactive mobile or fixed lines. Each of these requires verification, adding layers of complexity to what should be a straightforward procedure.
According to O2’s own documentation, a porting request can be delayed if “the data of ownership does not match” or if the ICC code is incorrect. While these checks are understandable, the lack of clear communication and timely resolution for González’s case raises concerns about the customer experience.
The incident serves as a stark reminder that while automation promises efficiency, it can also create bottlenecks when combined with manual verification processes. For businesses, particularly those reliant on seamless communication, such delays translate to lost productivity and potential revenue.
O2's response, requesting González to resubmit all his data to track the progress, only compounds the frustration—a bureaucratic hurdle that underscores the need for a more transparent and responsive system. The ongoing saga leaves a lingering question: how much friction is acceptable when consumers are simply seeking a better mobile deal?