Metro PCS: do you even care about your customers? we want...
A Metro PCS customer review by GetHuman user GetHuman-361474 from October 26th, 2017
Background on GetHuman-361474's case
GetHuman: GetHuman-361474 - can you tell our other Metro PCS customers when your case took place?
GetHuman-361474: Yes. It was morning, on October 20th.
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 GetHuman-361474 a list of common Metro PCS problems)
GetHuman-361474: "Payment Arrangement" was why I was trying to call.
GetHuman-361474'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.
GetHuman-361474: do you even care about your customers? we want out and will be sure to let people know the service and the customer service is probably the worst of any cell phone company we've had. this will be our last month with you
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?
GetHuman-361474: 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?
GetHuman-361474: 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?
GetHuman-361474: For that I would say five out of five.
GetHuman: And finally- any advice for other Metro PCS customers?
GetHuman-361474: 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 GetHuman-361474 taken from his Metro PCS customer service problem that occurred on October 20th, 2017.