DirecTV: The phone number worked beautifully. Connected...
A DirecTV customer review by GetHuman user ~nony mouse from November 21st, 2017
Background on ~nony mouse's case
GetHuman: ~nony mouse - can you tell our other DirecTV customers when your case took place?
~nony mouse: Yes. It was late at night, on November 17th.
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 ~nony mouse a list of common DirecTV problems)
~nony mouse: "Refund" was why I was trying to call.
~nony mouse'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.
~nony mouse: The phone number worked beautifully. Connected right away!! After robots getting me nowhere for over an hour I stumbled on this page and thank you thank you to whoever discovered this number. And then my tech person, Crystal, was wonderful and she totally helped resolve a huge billing*service*disconnection error.
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?
~nony mouse: 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?
~nony mouse: 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?
~nony mouse: For that I would say five out of five.
GetHuman: And finally- any advice for other DirecTV customers?
~nony mouse: 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 ~nony mouse taken from his DirecTV customer service problem that occurred on November 17th, 2017.