DISH: over an hour .on the chat line and they disconn...
A DISH customer review by GetHuman user GetHuman-405735 from November 24th, 2017
Background on GetHuman-405735's case
GetHuman: GetHuman-405735 - can you tell our other DISH customers when your case took place?
GetHuman-405735: Yes I can. It was middle of the night, on November 18th.
GetHuman: Did you reach out to DISH, and if so, how?
GetHuman: And which of these common DISH customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-405735 a list of common DISH problems)
GetHuman-405735: "Account Access" was why I was trying to call.
GetHuman-405735's review of DISH customer service
GetHuman: So how would you sum up your experience for GetHuman's DISH 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-405735: over an hour .on the chat line and they disconnected without fixing problem.called tech support * times and got disconnected.they didn't want to send a tech to my house just new equipment.Finally on *rd call I got it done.I had to ask for a credit on * days service lost. THEY ****!
GetHuman: Let's quantify your experience contacting DISH. On a scale of 1 to 5, how easy is it go get help on a DISH problem?
GetHuman-405735: 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?
GetHuman-405735: I'd give them a five out of five on communication.
GetHuman: And what about DISH's ability to quickly and effectively address your problem?
GetHuman-405735: For that I would say five out of five.
GetHuman: And finally- any advice for other DISH customers?
GetHuman-405735: Call them early in the day or late. Don't forget any personal or account information you might need for DISH to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-405735 taken from his DISH customer service problem that occurred on November 18th, 2017.