HughesNet: My technical problem is not yet solved, but by...
A HughesNet customer review by GetHuman user GetHuman-146843 from November 12th, 2017
Background on GetHuman-146843's case
GetHuman: GetHuman-146843 - can you tell our other HughesNet customers when your case took place?
GetHuman-146843: Yup. It was morning, on November 7th.
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-146843 a list of common HughesNet problems)
GetHuman-146843: "Cancel Service" was why I was trying to call.
GetHuman-146843'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-146843: My technical problem is not yet solved, but by using this telephone I was able for the FIRST time to talk with someone who actually seemed like she wanted to (and would) do something to ssolve my technical problem.
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-146843: 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-146843: I'd give them a five out of five on communication.
GetHuman: And what about HughesNet's ability to quickly and effectively address your problem?
GetHuman-146843: For that I would say three out of five.
GetHuman: And finally- any advice for other HughesNet customers?
GetHuman-146843: 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-146843 taken from his HughesNet customer service problem that occurred on November 7th, 2017.