Sprint Corporate Care: I have been on and off the phone with sprint fo...
A Sprint Corporate Care customer review by GetHuman user ~yvt from November 21st, 2017
Background on ~yvt's case
GetHuman: ~yvt - can you tell our other Sprint Corporate Care customers when your case took place?
~yvt: Sure. It was morning, on November 12th.
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 ~yvt a list of common Sprint Corporate Care problems)
~yvt: "Service problem" was why I was trying to call.
~yvt'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.
~yvt: I have been on and off the phone with sprint for * days now tring to port a number. I get different answers from everyone I talk to and hung up on when I ask to speak to a supervisor.
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?
~yvt: I'd give them a one 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?
~yvt: 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?
~yvt: For that I would say three out of five.
GetHuman: And finally- any advice for other Sprint Corporate Care customers?
~yvt: 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 ~yvt taken from his Sprint Corporate Care customer service problem that occurred on November 12th, 2017.