H2O Wireless: Unable to get service at my home AND they REFUS...
A H2O Wireless customer review by GetHuman user ~fed up with h2o from November 23rd, 2017
Background on ~fed up with h2o's case
GetHuman: ~fed up with h2o - can you tell our other H2O Wireless customers when your case took place?
~fed up with h2o: Yes. It was morning, on November 22nd.
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 ~fed up with h2o a list of common H2O Wireless problems)
~fed up with h2o: "Overcharge/Strange charge" was why I was trying to call.
~fed up with h2o'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.
~fed up with h2o: Unable to get service at my home AND they REFUSE to refund my money. Spent $**on SIM cards that they place the blame on - & they want me to buy a third one!?
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?
~fed up with h2o: I'd give them a one 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?
~fed up with h2o: I'd give them a one out of five on communication.
GetHuman: And what about H2O Wireless's ability to quickly and effectively address your problem?
~fed up with h2o: For that I would say three out of five.
GetHuman: And finally- any advice for other H2O Wireless customers?
~fed up with h2o: 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 ~fed up with h2o taken from his H2O Wireless customer service problem that occurred on November 22nd, 2017.