sprint needs to train their employees better be...
A Sprint customer review by GetHuman user GetHuman-402670 from November 22nd, 2017
Background on GetHuman-402670's case
GetHuman: GetHuman-402670 - can you tell our other Sprint customers when your case took place?
GetHuman-402670: Yes I can. It was middle of the night, on November 12th.
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-402670 a list of common Sprint problems)
GetHuman-402670: "Cancel Service" was why I was trying to call.
GetHuman-402670'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-402670: sprint needs to train their employees better because most of them dont know what theyre doing. call **** *** **** youre better off using this number. at least this line doesnt hang up. Im still on the phone and its been an hour... smh...this is why i love verizon.
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-402670: 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?
GetHuman-402670: 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-402670: For that I would say five out of five.
GetHuman: And finally- any advice for other Sprint customers?
GetHuman-402670: Call them early in the day or late. Don't forget any personal or account information you might need for Sprint to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-402670 taken from his Sprint customer service problem that occurred on November 12th, 2017.