HughesNet: After calling ***-***-**** several times, and b...
A HughesNet customer review by GetHuman user ~tizabuzygirl from November 18th, 2017
Background on ~tizabuzygirl's case
GetHuman: ~tizabuzygirl - can you tell our other HughesNet customers when your case took place?
~tizabuzygirl: Yes I can. It was afternoon, on November 12th.
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 ~tizabuzygirl a list of common HughesNet problems)
~tizabuzygirl: "Cancel Service" was why I was trying to call.
~tizabuzygirl'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.
~tizabuzygirl: After calling ***-***-**** several times, and being transferred three times per call, and then the final transfer resulted in an inaudible CSR, I hung up and dialed the corporate number. I am so thankful for the service I received. It exceeded my expectations.
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?
~tizabuzygirl: I'd give them a three 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?
~tizabuzygirl: I'd give them a two out of five on communication.
GetHuman: And what about HughesNet's ability to quickly and effectively address your problem?
~tizabuzygirl: For that I would say one out of five.
GetHuman: And finally- any advice for other HughesNet customers?
~tizabuzygirl: 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 ~tizabuzygirl taken from his HughesNet customer service problem that occurred on November 12th, 2017.