Metro PCS: The worst service it could ever be, had this ph...
A Metro PCS customer review by GetHuman user ~bad experince! from November 11th, 2017
Background on ~bad experince!'s case
GetHuman: ~bad experince! - can you tell our other Metro PCS customers when your case took place?
~bad experince!: Yup. It was afternoon, on November 4th.
GetHuman: Did you reach out to Metro PCS, and if so, how?
GetHuman: And which of these common Metro PCS customer issues best describes the reason you wanted to talk to them?
(Shows ~bad experince! a list of common Metro PCS problems)
~bad experince!: "Returns" was why I was trying to call.
~bad experince!'s review of Metro PCS customer service
GetHuman: So how would you sum up your experience for GetHuman's Metro PCS 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.
~bad experince!: The worst service it could ever be, had this phone for * months and had to call every * days to repair another issue. i dont suggest metro pcs to ANYONE! was transfered to a million ppl went down to a local store and was not help an once!
GetHuman: Let's quantify your experience contacting Metro PCS. On a scale of 1 to 5, how easy is it go get help on a Metro PCS problem?
~bad experince!: 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?
~bad experince!: I'd give them a one out of five on communication.
GetHuman: And what about Metro PCS's ability to quickly and effectively address your problem?
~bad experince!: For that I would say five out of five.
GetHuman: And finally- any advice for other Metro PCS customers?
~bad experince!: Call them early in the day or late. Don't forget any personal or account information you might need for Metro PCS to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~bad experince! taken from his Metro PCS customer service problem that occurred on November 4th, 2017.