H2O Wireless: h*o needs to step up there game, they send the...
A H2O Wireless customer review by GetHuman user GetHuman-370023 from November 23rd, 2017
Background on GetHuman-370023's case
GetHuman: GetHuman-370023 - can you tell our other H2O Wireless customers when your case took place?
GetHuman-370023: Yup. It was morning, on November 19th.
GetHuman: Did you reach out to H2O Wireless, and if so, how?
GetHuman: And which of these common H2O Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-370023 a list of common H2O Wireless problems)
GetHuman-370023: "Account Access" was why I was trying to call.
GetHuman-370023's review of H2O Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's H2O 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-370023: h*o needs to step up there game, they send the call overseas, to ppl who cant speak a lick of English so most of the time is spend repeating the question, and still no solution!
GetHuman: Let's quantify your experience contacting H2O Wireless. On a scale of 1 to 5, how easy is it go get help on a H2O Wireless problem?
GetHuman-370023: 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-370023: I'd give them a five out of five on communication.
GetHuman: And what about H2O Wireless's ability to quickly and effectively address your problem?
GetHuman-370023: For that I would say one out of five.
GetHuman: And finally- any advice for other H2O Wireless customers?
GetHuman-370023: Call them early in the day or late. Don't forget any personal or account information you might need for H2O Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-370023 taken from his H2O Wireless customer service problem that occurred on November 19th, 2017.