Metro PCS: My rep was amazing. She was really cool. I didn...
A Metro PCS customer review by GetHuman user ~Happy SaQuera! from November 23rd, 2017
Background on ~Happy SaQuera!'s case
GetHuman: ~Happy SaQuera! - can you tell our other Metro PCS customers when your case took place?
~Happy SaQuera!: Yes. It was evening, on November 19th.
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 ~Happy SaQuera! a list of common Metro PCS problems)
~Happy SaQuera!: "Device Support" was why I was trying to call.
~Happy SaQuera!'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.
~Happy SaQuera!: My rep was amazing. She was really cool. I didn't catch her name but she was totally helpful. I didn't get to thank her because my phone had died :( which really sucked because i knew i would never be able to reach her again.
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?
~Happy SaQuera!: I'd give them a one 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?
~Happy SaQuera!: I'd give them a four out of five on communication.
GetHuman: And what about Metro PCS's ability to quickly and effectively address your problem?
~Happy SaQuera!: For that I would say one out of five.
GetHuman: And finally- any advice for other Metro PCS customers?
~Happy SaQuera!: 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 ~Happy SaQuera! taken from his Metro PCS customer service problem that occurred on November 19th, 2017.