HughesNet: The accent is so bad you always are asking them...
A HughesNet customer review by GetHuman user ~Mad@Hughes from October 27th, 2017
Background on ~Mad@Hughes's case
GetHuman: ~Mad@Hughes - can you tell our other HughesNet customers when your case took place?
~Mad@Hughes: Yes I can. It was evening, on October 22nd.
GetHuman: Did you reach out to HughesNet, and if so, how?
GetHuman: And which of these common HughesNet customer issues best describes the reason you wanted to talk to them?
(Shows ~Mad@Hughes a list of common HughesNet problems)
~Mad@Hughes: "Cancel Service" was why I was trying to call.
~Mad@Hughes's review of HughesNet customer service
GetHuman: So how would you sum up your experience for GetHuman's HughesNet 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.
~Mad@Hughes: The accent is so bad you always are asking them to repeat themselves. I have hung up and called back in hopes of getting someone I can understand. They trouble shoot with a script and are often unable to fix a problem. I have complained to the FCC asking that their license to use radio bandwidth be revoked due to bad service.
GetHuman: Let's quantify your experience contacting HughesNet. On a scale of 1 to 5, how easy is it go get help on a HughesNet problem?
~Mad@Hughes: I'd give them a five 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?
~Mad@Hughes: I'd give them a four out of five on communication.
GetHuman: And what about HughesNet's ability to quickly and effectively address your problem?
~Mad@Hughes: For that I would say one out of five.
GetHuman: And finally- any advice for other HughesNet customers?
~Mad@Hughes: Call them early in the day or late. Don't forget any personal or account information you might need for HughesNet to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Mad@Hughes taken from his HughesNet customer service problem that occurred on October 22nd, 2017.