HughesNet: I got an English speaking representative but he...
A HughesNet customer review by GetHuman user GetHuman-200511 from November 15th, 2017
Background on GetHuman-200511's case
GetHuman: GetHuman-200511 - can you tell our other HughesNet customers when your case took place?
GetHuman-200511: Sure. It was evening, on November 13th.
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 GetHuman-200511 a list of common HughesNet problems)
GetHuman-200511: "Overcharge on Account" was why I was trying to call.
GetHuman-200511'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.
GetHuman-200511: I got an English speaking representative but he still cannot help me. I'm trying to cancel my service. I've called * different phone numbers and I still cannot get anyone that is capable of cancelling this for me. HUGHES *****!
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?
GetHuman-200511: 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?
GetHuman-200511: 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?
GetHuman-200511: For that I would say three out of five.
GetHuman: And finally- any advice for other HughesNet customers?
GetHuman-200511: 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 GetHuman-200511 taken from his HughesNet customer service problem that occurred on November 13th, 2017.