Sprint Corporate Care: I wanted you all to know that employee *VL...
A Sprint Corporate Care customer review by GetHuman user ~Frank from November 26th, 2017
Background on ~Frank's case
GetHuman: ~Frank - can you tell our other Sprint Corporate Care customers when your case took place?
~Frank: Sure. It was evening, on November 18th.
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 ~Frank a list of common Sprint Corporate Care problems)
~Frank: "Refund a Charge" was why I was trying to call.
~Frank'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.
~Frank: I wanted you all to know that employee *VL***** was outstanding. James was very professional and represented your Customer Service section well. Thank you. --a customer for life.
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?
~Frank: I'd give them a four 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?
~Frank: I'd give them a one out of five on communication.
GetHuman: And what about Sprint Corporate Care's ability to quickly and effectively address your problem?
~Frank: For that I would say two out of five.
GetHuman: And finally- any advice for other Sprint Corporate Care customers?
~Frank: 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 ~Frank taken from his Sprint Corporate Care customer service problem that occurred on November 18th, 2017.