A
Alexander

1 reviews | Active since Sept 2023

27 Mar 2025, 10:51

Supersonic MTN LTE

I started having issues with my internet speed, where it would drop to 8Mbps at 12 p.m. every day and stay at that speed for the rest of the day. I contacted support, and without going into too much detail, I was told multiple times that a technician would contact me within 5 minutes—yet no one ever did.

After about 5 days of this, I asked to speak to a supervisor. I was told he or she would contact me within 5 minutes. Thirty minutes passed—still nothing. I contacted support again and insisted that I would not wait for a callback and needed to be put through to a supervisor immediately. I was then placed on hold for 40 minutes. I hung up, called again, and told the person who answered that if I wasn't contacted by a supervisor within 10 minutes, I would message their COO on LinkedIn to detail the poor support experience I was receiving.

Within 3 minutes, the supervisor called me. He said he would keep me updated—he updated me 2 times and then stopped. After two weeks of dealing with the issue and still receiving no help or updates, I went ahead and messaged the COO on LinkedIn. A week later, the COO read my message and rep**** that she would investigate the issue.

The very next day, I was contacted by support with updates—but those also stopped. So I asked for the ticket number Supersonic had logged with MTN and called MTN directly for updates. MTN told me the issue was logged 21 days after I initially contacted Supersonic—just one day after I spoke with the COO.

MTN told me that only Supersonic can provide updates. Supersonic, on the other hand, keeps saying the issue is with MTN. So here I am, still stuck in the dark. It’s been a month already.

TL;DR: If you’re thinking about using Supersonic for MTN LTE—don’t. Just go with MTN directly. This way you wouldn't have to threaten Supersonic support by contacting superiors to get help. Took them 21 days to create a ticket with MTN for my issue because I messaged the COO.

0
Replies (0)