T-Mobile: I called them and didn't wait on hold* the rep...
A T-Mobile customer review by GetHuman user ~Eliz from November 21st, 2017
Background on ~Eliz's case
GetHuman: ~Eliz - can you tell our other T-Mobile customers when your case took place?
~Eliz: Yes. It was evening, on November 15th.
GetHuman: Did you reach out to T-Mobile, and if so, how?
GetHuman: And which of these common T-Mobile customer issues best describes the reason you wanted to talk to them?
(Shows ~Eliz a list of common T-Mobile problems)
~Eliz: "Update account information" was why I was trying to call.
~Eliz's review of T-Mobile customer service
GetHuman: So how would you sum up your experience for GetHuman's T-Mobile 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.
~Eliz: I called them and didn't wait on hold* the rep answered immediatly. The rep was in training and kept putting me on mute to ask someone else my questions. I finally asked for someone else who could help me since she was not understanding anything I said. I was on the phone for **min and I spoke to the supervisor who applogized and helped me in less than * min.
GetHuman: Let's quantify your experience contacting T-Mobile. On a scale of 1 to 5, how easy is it go get help on a T-Mobile problem?
~Eliz: I'd give them a three 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?
~Eliz: I'd give them a two out of five on communication.
GetHuman: And what about T-Mobile's ability to quickly and effectively address your problem?
~Eliz: For that I would say three out of five.
GetHuman: And finally- any advice for other T-Mobile customers?
~Eliz: Call them early in the day or late. Don't forget any personal or account information you might need for T-Mobile to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Eliz taken from his T-Mobile customer service problem that occurred on November 15th, 2017.