TaxAct: I could not understand the woman, Annie, who an...
A TaxAct customer review by GetHuman user ~jo from November 9th, 2017
Background on ~jo's case
GetHuman: ~jo - can you tell our other TaxAct customers when your case took place?
~jo: Yes. It was afternoon, on October 30th.
GetHuman: Did you reach out to TaxAct, and if so, how?
GetHuman: And which of these common TaxAct customer issues best describes the reason you wanted to talk to them?
(Shows ~jo a list of common TaxAct problems)
~jo: "Refund a Charge" was why I was trying to call.
~jo's review of TaxAct customer service
GetHuman: So how would you sum up your experience for GetHuman's TaxAct 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.
~jo: I could not understand the woman, Annie, who answered the phone. She was unbelievably rude, impatient and I hope it is on record somewhere. Called to get help and was told I had to pay for phone service. Site says I have completed my return, but no record of it anywhere. I just gave this chick my VISA and am still on hold...finally hung up and called back and got Courtney who was very sympathetic and kudos to her for her.
GetHuman: Let's quantify your experience contacting TaxAct. On a scale of 1 to 5, how easy is it go get help on a TaxAct problem?
~jo: 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?
~jo: I'd give them a four out of five on communication.
GetHuman: And what about TaxAct's ability to quickly and effectively address your problem?
~jo: For that I would say three out of five.
GetHuman: And finally- any advice for other TaxAct customers?
~jo: Call them early in the day or late. Don't forget any personal or account information you might need for TaxAct to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jo taken from his TaxAct customer service problem that occurred on October 30th, 2017.