ReachOut Wireless: you were suppose to turn my phone on and they d...
A ReachOut Wireless customer review by GetHuman user ~susan couch from November 20th, 2017
Background on ~susan couch's case
GetHuman: ~susan couch - can you tell our other ReachOut Wireless customers when your case took place?
~susan couch: Sure. It was middle of the night, on November 16th.
GetHuman: Did you reach out to ReachOut Wireless, and if so, how?
GetHuman: And which of these common ReachOut Wireless customer issues best describes the reason you wanted to talk to them?
(Shows ~susan couch a list of common ReachOut Wireless problems)
~susan couch: "Update account information" was why I was trying to call.
~susan couch's review of ReachOut Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's ReachOut Wireless 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.
~susan couch: you were suppose to turn my phone on and they didnt this is the worst service i have ever seen someone better turn my phone on
GetHuman: Let's quantify your experience contacting ReachOut Wireless. On a scale of 1 to 5, how easy is it go get help on a ReachOut Wireless problem?
~susan couch: 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?
~susan couch: I'd give them a two out of five on communication.
GetHuman: And what about ReachOut Wireless's ability to quickly and effectively address your problem?
~susan couch: For that I would say one out of five.
GetHuman: And finally- any advice for other ReachOut Wireless customers?
~susan couch: Call them early in the day or late. Don't forget any personal or account information you might need for ReachOut Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~susan couch taken from his ReachOut Wireless customer service problem that occurred on November 16th, 2017.