CP
Charles P

1 reviews | Active since May 2026

12 May 2026, 11:34

Over a Month Later and MTN Still Cannot Resolve a Basic Apple Watch eSIM Issue – Yet They Continue Billing Me

MTN continues billing me monthly for an Apple Watch eSIM / OneNumber service that they have been unable to provide or properly support for more than a month.

Despite numerous emails, escalations, screenshots, and PDF submissions clearly depicting the issue, MTN still cannot resolve what appears to be a backend provisioning problem linked to their wearable eSIM platform.

What is most concerning is that MTN confirmed under reference RITM*** that the activation had been completed, yet the Apple Watch still shows “No SIM” and “No Connection”. The service remains completely unusable.

At this stage, the issue is no longer simply technical. It raises serious concerns regarding MTN’s technical expertise, escalation capability, and overall customer support standards.

Clients are paying monthly for services MTN appears unable to properly provision, support, or troubleshoot.

Even worse, communication throughout this process has been extremely poor: • Delayed responses • Generic feedback • No meaningful technical explanations • No accountability • No direct contact from anyone with authority or sufficient technical competence to resolve the issue

As a long-standing MTN client, this experience has been exceptionally disappointing and reflects very poorly on MTN’s customer care and technical support structures.

Case References: RITM*** RITM***

0
Replies (2)
CP
Charles P's update13 May 2026, 11:29
Reviewer Update
Another week, another MTN escalation, another “please wait 24–48 hours.”My Apple Watch eSIM / OneNumber issue has now dragged on for more than a month under references RITM*** and RITM***, despite:
• Multiple emails
• Telephone calls
• In-store visits
• Screenshots
• PDF submissions
• Repeated escalationsMTN even confirmed at one stage that the activation had been completed, yet the watch still shows “No SIM” and “No Connection”.The most alarming part is not the technical fault itself. Technical issues happen.The real concern is that MTN appears incapable of properly escalating, managing, communicating, or resolving the issue despite having ample time and information to do so.Each response simply repeats:
“Ticket reopened”
“Escalated to support”
“Please wait 24–48 hours”Meanwhile, the service still does not work, yet billing continues uninterrupted.At this stage, it genuinely appears that no one within MTN’s support structures has the authority, expertise, or accountability to take ownership of the matter and resolve it properly.For a company marketing premium digital services like Apple Watch connectivity and OneNumber, this level of technical support and customer communication is deeply disappointing.References:
RITM***
RITM***
CP
Charles P's update14 May 2026, 11:37
Reviewer Update
MTN’s latest response to my ongoing Apple Watch eSIM / OneNumber issue is honestly astonishing.After more than a month of escalations, emails, calls, screenshots, PDF submissions, and store visits, MTN’s support team responded by saying:
“eSIM activation from old watch to new watch done as per attached screenshots.”The problem?
The screenshots themselves clearly show the watch still displaying:
• “No SIM”
• “No Connection”In other words, MTN is now effectively using screenshots proving the service does NOT work as evidence that the issue has supposedly been resolved.At this stage, the issue is no longer just technical. It reflects a complete breakdown in communication, escalation management, technical accountability, and customer support competence.No one at MTN appears willing to take ownership of the matter or escalate it to someone genuinely capable of resolving it.Instead, the process has become:
• Generic responses
• Reopened tickets
• Endless delays
• No meaningful technical engagement
• Continued billing for a non-functional serviceIt is genuinely concerning that a company of MTN’s size appears unable to resolve what should be a straightforward Apple Watch eSIM provisioning issue.Case References:
RITM***
RITM***