Sprint Nextel: Was transferred * times on the regular sprint n...
A Sprint Nextel customer review by GetHuman user ~Chicken Lady from November 20th, 2017
Background on ~Chicken Lady's case
GetHuman: ~Chicken Lady - can you tell our other Sprint Nextel customers when your case took place?
~Chicken Lady: Yes I can. It was morning, on November 18th.
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 ~Chicken Lady a list of common Sprint Nextel problems)
~Chicken Lady: "Cancel service" was why I was trying to call.
~Chicken Lady'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.
~Chicken Lady: Was transferred * times on the regular sprint number then got disconnected without resolving my issue previous to this call. Susie helped me immediately and my issue was resolved in * minutes! Thanks.
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?
~Chicken Lady: I'd give them a two 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?
~Chicken Lady: I'd give them a one out of five on communication.
GetHuman: And what about Sprint Nextel's ability to quickly and effectively address your problem?
~Chicken Lady: For that I would say two out of five.
GetHuman: And finally- any advice for other Sprint Nextel customers?
~Chicken Lady: 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 ~Chicken Lady taken from his Sprint Nextel customer service problem that occurred on November 18th, 2017.