Sprint Nextel: their service *****....early contacts are like...
A Sprint Nextel customer review by GetHuman user ~wippitt1956 from November 28th, 2017
Background on ~wippitt1956's case
GetHuman: ~wippitt1956 - can you tell our other Sprint Nextel customers when your case took place?
~wippitt1956: Yup. It was evening, on November 20th.
GetHuman: Did you reach out to Sprint Nextel, and if so, how?
GetHuman: And which of these common Sprint Nextel customer issues best describes the reason you wanted to talk to them?
(Shows ~wippitt1956 a list of common Sprint Nextel problems)
~wippitt1956: "Cancel service" was why I was trying to call.
~wippitt1956's review of Sprint Nextel customer service
GetHuman: So how would you sum up your experience for GetHuman's Sprint Nextel 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.
~wippitt1956: their service *****....early contacts are like scripted and NEVER have spoken to any supervisor even after * separate calls and told would be sent to a supervisor....I wouldn't speak well of this company ever
GetHuman: Let's quantify your experience contacting Sprint Nextel. On a scale of 1 to 5, how easy is it go get help on a Sprint Nextel problem?
~wippitt1956: 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?
~wippitt1956: I'd give them a four out of five on communication.
GetHuman: And what about Sprint Nextel's ability to quickly and effectively address your problem?
~wippitt1956: For that I would say one out of five.
GetHuman: And finally- any advice for other Sprint Nextel customers?
~wippitt1956: Call them early in the day or late. Don't forget any personal or account information you might need for Sprint Nextel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~wippitt1956 taken from his Sprint Nextel customer service problem that occurred on November 20th, 2017.