Sprint: this service is terrible... ive only been on sp...
A Sprint customer review by GetHuman user ~SPRINTSUCKSF150 from November 20th, 2017
Background on ~SPRINTSUCKSF150's case
GetHuman: ~SPRINTSUCKSF150 - can you tell our other Sprint customers when your case took place?
~SPRINTSUCKSF150: Yup. It was late at night, on November 18th.
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 ~SPRINTSUCKSF150 a list of common Sprint problems)
~SPRINTSUCKSF150: "Change plan" was why I was trying to call.
~SPRINTSUCKSF150'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.
~SPRINTSUCKSF150: this service is terrible... ive only been on sprint for no even * days and this is going way downhill! customer service ha...no help at all our signal is horrible and hangs up * second after making a call. sprint ****** ***** im so unhappy with this service
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?
~SPRINTSUCKSF150: 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?
~SPRINTSUCKSF150: I'd give them a two out of five on communication.
GetHuman: And what about Sprint's ability to quickly and effectively address your problem?
~SPRINTSUCKSF150: For that I would say one out of five.
GetHuman: And finally- any advice for other Sprint customers?
~SPRINTSUCKSF150: 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 ~SPRINTSUCKSF150 taken from his Sprint customer service problem that occurred on November 18th, 2017.