ReachOut Wireless: customer service is the worst I have ever known...
A ReachOut Wireless customer review by GetHuman user GetHuman-169444 from November 16th, 2017
Background on GetHuman-169444's case
GetHuman: GetHuman-169444 - can you tell our other ReachOut Wireless customers when your case took place?
GetHuman-169444: Yes. It was late at night, on November 14th.
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 GetHuman-169444 a list of common ReachOut Wireless problems)
GetHuman-169444: "Complaint" was why I was trying to call.
GetHuman-169444'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.
GetHuman-169444: customer service is the worst I have ever known. They should go out of business and let another company take over.
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?
GetHuman-169444: 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?
GetHuman-169444: I'd give them a one out of five on communication.
GetHuman: And what about ReachOut Wireless's ability to quickly and effectively address your problem?
GetHuman-169444: For that I would say two out of five.
GetHuman: And finally- any advice for other ReachOut Wireless customers?
GetHuman-169444: 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 GetHuman-169444 taken from his ReachOut Wireless customer service problem that occurred on November 14th, 2017.