ReachOut Wireless: I waiting for the customer service for * hours...
A ReachOut Wireless customer review by GetHuman user ~nuj yob yang from November 19th, 2017
Background on ~nuj yob yang's case
GetHuman: ~nuj yob yang - can you tell our other ReachOut Wireless customers when your case took place?
~nuj yob yang: Sure. It was afternoon, on November 17th.
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 ~nuj yob yang a list of common ReachOut Wireless problems)
~nuj yob yang: "Technical support" was why I was trying to call.
~nuj yob yang'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.
~nuj yob yang: I waiting for the customer service for * hours but no any body come to chat with me i don't know y they let their customer wait for long times
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?
~nuj yob yang: 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?
~nuj yob yang: 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?
~nuj yob yang: For that I would say four out of five.
GetHuman: And finally- any advice for other ReachOut Wireless customers?
~nuj yob yang: 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 ~nuj yob yang taken from his ReachOut Wireless customer service problem that occurred on November 17th, 2017.