I hate Sprint. I moved over from Verizon, worst...
Una recensione del cliente Sprint da parte dell'utente GetHuman GetHuman-315748 da novembre 27º, 2017
Background on GetHuman-315748's case
GetHuman: GetHuman-315748 - can you tell our other Sprint customers when your case took place?
GetHuman-315748: Yup. It was afternoon, on novembre 18º.
GetHuman: Did you reach out to Sprint, and if so, how?
GetHuman: And which of these common Sprint customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-315748 a list of common Sprint problems)
GetHuman-315748: "Refund" was why I was trying to call.
GetHuman-315748's review of Sprint customer service
GetHuman: So how would you sum up your experience for GetHuman's Sprint 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-315748: I hate Sprint. I moved over from Verizon, worst mistake ever. I have * phones with Sprint a IPhone *, * and * they all ****. I can't wait to switch back to Verizon. I am sending this in my AT&T iPhone *, because my Sprint piece of **** phone is locked up.
GetHuman: Let's quantify your experience contacting Sprint. On a scale of 1 to 5, how easy is it go get help on a Sprint problem?
GetHuman-315748: 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-315748: I'd give them a four out of five on communication.
GetHuman: And what about Sprint's ability to quickly and effectively address your problem?
GetHuman-315748: For that I would say five out of five.
GetHuman: And finally- any advice for other Sprint customers?
GetHuman-315748: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Sprint sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-315748 taken from his Sprint customer service problem that occurred on novembre 18º, 2017.