Metro PCS: They are the worse company ever! DO NOT go ther...
A Metro PCS customer review by GetHuman user ~suzysea from November 23rd, 2017
Background on ~suzysea's case
GetHuman: ~suzysea - can you tell our other Metro PCS customers when your case took place?
~suzysea: Yes. It was afternoon, on November 18th.
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 ~suzysea a list of common Metro PCS problems)
~suzysea: "Lost or Stolen Phone" was why I was trying to call.
~suzysea'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.
~suzysea: They are the worse company ever! DO NOT go there!!!!!!!!!! We had no service at the house, they were unwilling to help and the phone is locked. SO we have to pay to have it unlocked as they won't unlock it. Then the place we went to said they couldn't unlock it as it was a Metro PCS phone! VERY UNHAPPY!!!!
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?
~suzysea: 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?
~suzysea: 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?
~suzysea: For that I would say three out of five.
GetHuman: And finally- any advice for other Metro PCS customers?
~suzysea: 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 ~suzysea taken from his Metro PCS customer service problem that occurred on November 18th, 2017.