Sprint Corporate Care: The nice people I spoke to are out of the U.S...
A Sprint Corporate Care customer review by GetHuman user ~Suz from November 27th, 2017
Background on ~Suz's case
GetHuman: ~Suz - can you tell our other Sprint Corporate Care customers when your case took place?
~Suz: Yes. It was afternoon, on November 26th.
GetHuman: Did you reach out to Sprint Corporate Care, and if so, how?
GetHuman: And which of these common Sprint Corporate Care customer issues best describes the reason you wanted to talk to them?
(Shows ~Suz a list of common Sprint Corporate Care problems)
~Suz: "Technical Support" was why I was trying to call.
~Suz's review of Sprint Corporate Care customer service
GetHuman: So how would you sum up your experience for GetHuman's Sprint Corporate Care 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.
~Suz: The nice people I spoke to are out of the U.S. and cannot resolve anything. I moved from the Sprint service area, it is now the end of May and I have been trying to resolve this since January.
GetHuman: Let's quantify your experience contacting Sprint Corporate Care. On a scale of 1 to 5, how easy is it go get help on a Sprint Corporate Care problem?
~Suz: 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?
~Suz: I'd give them a two out of five on communication.
GetHuman: And what about Sprint Corporate Care's ability to quickly and effectively address your problem?
~Suz: For that I would say five out of five.
GetHuman: And finally- any advice for other Sprint Corporate Care customers?
~Suz: Call them early in the day or late. Don't forget any personal or account information you might need for Sprint Corporate Care to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Suz taken from his Sprint Corporate Care customer service problem that occurred on November 26th, 2017.