ReachOut Wireless: Best option is chat they help early while assit...
A ReachOut Wireless customer review by GetHuman user ~Patrick from November 22nd, 2017
Background on ~Patrick's case
GetHuman: ~Patrick - can you tell our other ReachOut Wireless customers when your case took place?
~Patrick: Yes I can. It was evening, 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 ~Patrick a list of common ReachOut Wireless problems)
~Patrick: "Overcharge/Strange charge" was why I was trying to call.
~Patrick'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.
~Patrick: Best option is chat they help early while assiting many cutomers. Others need to understand. They do as much they can. Great. Reachout chat. *Bradley jones was the best rep i have seen
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?
~Patrick: 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?
~Patrick: I'd give them a four out of five on communication.
GetHuman: And what about ReachOut Wireless's ability to quickly and effectively address your problem?
~Patrick: For that I would say one out of five.
GetHuman: And finally- any advice for other ReachOut Wireless customers?
~Patrick: 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 ~Patrick taken from his ReachOut Wireless customer service problem that occurred on November 14th, 2017.