Sprint Customer Service *****
Eine Sprint Kundenbewertung durch GetHuman-Benutzer GetHuman-jsheppel von Dezember 4., 2017
Background on GetHuman-jsheppel's case
GetHuman: GetHuman-jsheppel - can you tell our other Sprint customers when your case took place?
GetHuman-jsheppel: Yup. It was afternoon, on November 30..
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-jsheppel a list of common Sprint problems)
GetHuman-jsheppel: "Technical support" was why I was trying to call.
GetHuman-jsheppel'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-jsheppel: Sprint Customer Service *****
GetHuman: Can you tell the rest of us a bit more from what happened on 11/30/17?
GetHuman-jsheppel: Cannot get them to help you with problems. Having them call you back is worthless as well. Going back to At&T
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-jsheppel: 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-jsheppel: 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?
GetHuman-jsheppel: For that I would say three out of five.
GetHuman: And finally- any advice for other Sprint customers?
GetHuman-jsheppel: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Sprint weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-jsheppel taken from his Sprint customer service problem that occurred on November 30., 2017.