Sprint Corporate Care: I wish I had never responded to their email off...
Una recensione del cliente Sprint Corporate Care da parte dell'utente GetHuman ~John da novembre 27º, 2017
Background on ~John's case
GetHuman: ~John - can you tell our other Sprint Corporate Care customers when your case took place?
~John: Yup. It was evening, on novembre 17º.
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 ~John a list of common Sprint Corporate Care problems)
~John: "Cancel Service" was why I was trying to call.
~John'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.
~John: I wish I had never responded to their email offer. Nothing is getting done. I get passed from one customer care rep to another. Then they don't come back on line.
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?
~John: 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?
~John: 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?
~John: For that I would say four out of five.
GetHuman: And finally- any advice for other Sprint Corporate Care customers?
~John: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Sprint Corporate Care sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~John taken from his Sprint Corporate Care customer service problem that occurred on novembre 17º, 2017.