DirecTV: Voice recognition on menu was horrible. Repeat...
A DirecTV customer review by GetHuman user GetHuman-381309 from November 28th, 2017
Background on GetHuman-381309's case
GetHuman: GetHuman-381309 - can you tell our other DirecTV customers when your case took place?
GetHuman-381309: Yes. It was afternoon, on November 23rd.
GetHuman: Did you reach out to DirecTV, and if so, how?
GetHuman: And which of these common DirecTV customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-381309 a list of common DirecTV problems)
GetHuman-381309: "Service Outage" was why I was trying to call.
GetHuman-381309's review of DirecTV customer service
GetHuman: So how would you sum up your experience for GetHuman's DirecTV 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-381309: Voice recognition on menu was horrible. Repeated three times and still did not understand. Used numbers and was directed to wrong department. Wait time too long. Knew this was going to happen once AT&T took over. Might cut the cord completely.
GetHuman: Let's quantify your experience contacting DirecTV. On a scale of 1 to 5, how easy is it go get help on a DirecTV problem?
GetHuman-381309: 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-381309: I'd give them a four out of five on communication.
GetHuman: And what about DirecTV's ability to quickly and effectively address your problem?
GetHuman-381309: For that I would say five out of five.
GetHuman: And finally- any advice for other DirecTV customers?
GetHuman-381309: Call them early in the day or late. Don't forget any personal or account information you might need for DirecTV to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-381309 taken from his DirecTV customer service problem that occurred on November 23rd, 2017.