Are T-Mobile charging you for ghost calls? Let us know
Hey, T-Mobile customers - do you ever bother checking your itemised bills to see who you've been ringing? Of course not - you know who you've made calls to because it's your phone, right? Nah, not quite. In the case of one avid Bitterwallet reader, a "computer glitch" has apparently invented calls and added them to his bill - and it appears to be happening to other customers.
Here's reader Justin with the skinny:
Whilst checking my online call log (which include unbilled charges), I saw that I had been charged for two calls to UK mobile numbers.
I couldn't remember calling the numbers, and didn't recognise them, so I did a little research and it turned out they were allocated to O2 and T-Mobile, and were therefore standard UK mobile numbers and included in my inclusive minutes.
These numbers were not called by me - I checked the call log on my handset to be sure. When I rang them, one number was dead, and therefore a charge is technically impossible, and the other number was some posh tart I'd never spoken to before in my life.
Here's the online call log to show Justin has been charged for two calls that he claims were never made, and weren't recorded by his handset's call log (click for larger image):
So what are T-Mobile up to? According to the customer services manager that Justin spoke to, T-Mobile are aware that something "strange" is going on, and that their technical team are investigating this "computer glitch".
Worryingly, Justin was told that he isn't the only customer that's been affected, meaning hundred, thousands or more customers may be being charged for these "ghost" calls. Plenty of customers never check their bill to dispute adhoc charges, meaning T-Mobile could be raking in thousands if this is a widespread problem.
While T-Mobile investigates, we want to hear from you if you've also being billed for ghost calls. Have a look at your last bill or your current usage online and check the chargeable calls outside your monthly allowance - let us know at [email protected] if you've experienced a similarproblem.