T-Mobile (UK): First time I rang I waited * minutes then got d...
A T-Mobile (UK) customer review by GetHuman user ~dannythesin from November 13th, 2017
Background on ~dannythesin's case
GetHuman: ~dannythesin - can you tell our other T-Mobile (UK) customers when your case took place?
~dannythesin: Yes. It was morning, on November 11th.
GetHuman: Did you reach out to T-Mobile (UK), and if so, how?
GetHuman: And which of these common T-Mobile (UK) customer issues best describes the reason you wanted to talk to them?
(Shows ~dannythesin a list of common T-Mobile (UK) problems)
~dannythesin: "Complaint" was why I was trying to call.
~dannythesin's review of T-Mobile (UK) customer service
GetHuman: So how would you sum up your experience for GetHuman's T-Mobile (UK) customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~dannythesin: First time I rang I waited * minutes then got disconnected.*Second time I waited * minutes and was connected to a call centre in the Philippines. Talked to a very helpful polite guy who sorted out my problem quickly.
GetHuman: Let's quantify your experience contacting T-Mobile (UK). On a scale of 1 to 5, how easy is it go get help on a T-Mobile (UK) problem?
~dannythesin: I'd give them a two out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~dannythesin: I'd give them a one out of five on communication.
GetHuman: And what about T-Mobile (UK)'s ability to quickly and effectively address your problem?
~dannythesin: For that I would say two out of five.
GetHuman: And finally- any advice for other T-Mobile (UK) customers?
~dannythesin: Call them early in the day or late. Don't forget any personal or account information you might need for T-Mobile (UK) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~dannythesin taken from his T-Mobile (UK) customer service problem that occurred on November 11th, 2017.