T-Mobile: this type of service is not a good idea..what h...
A T-Mobile customer review by GetHuman user ~sick and tired from November 13th, 2017
Background on ~sick and tired's case
GetHuman: ~sick and tired - can you tell our other T-Mobile customers when your case took place?
~sick and tired: Yes I can. It was afternoon, on November 3rd.
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 ~sick and tired a list of common T-Mobile problems)
~sick and tired: "Payment Arrangement" was why I was trying to call.
~sick and tired'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.
~sick and tired: this type of service is not a good idea..what happen to getting someone on the phone, especially a phone company...when someone answers they rude and transfer you to ** people before you can get anything answered..............
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?
~sick and tired: 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?
~sick and tired: I'd give them a five out of five on communication.
GetHuman: And what about T-Mobile's ability to quickly and effectively address your problem?
~sick and tired: For that I would say five out of five.
GetHuman: And finally- any advice for other T-Mobile customers?
~sick and tired: 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 ~sick and tired taken from his T-Mobile customer service problem that occurred on November 3rd, 2017.