TurboTax: Short wait (* minutes with the screener. Then t...
A TurboTax customer review by GetHuman user ~Another Nobody from November 21st, 2017
Background on ~Another Nobody's case
GetHuman: ~Another Nobody - can you tell our other TurboTax customers when your case took place?
~Another Nobody: Yes. It was afternoon, on November 18th.
GetHuman: Did you reach out to TurboTax, and if so, how?
GetHuman: And which of these common TurboTax customer issues best describes the reason you wanted to talk to them?
(Shows ~Another Nobody a list of common TurboTax problems)
~Another Nobody: "Refund a Charge" was why I was trying to call.
~Another Nobody's review of TurboTax customer service
GetHuman: So how would you sum up your experience for GetHuman's TurboTax 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.
~Another Nobody: Short wait (* minutes with the screener. Then to the tax expert. No help with Program not having criteria - wanted to charge $**.** -** minutes more with no answer or referral. Very disappointed in TurboTax not doing what they advertise.
GetHuman: Let's quantify your experience contacting TurboTax. On a scale of 1 to 5, how easy is it go get help on a TurboTax problem?
~Another Nobody: I'd give them a four 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?
~Another Nobody: I'd give them a five out of five on communication.
GetHuman: And what about TurboTax's ability to quickly and effectively address your problem?
~Another Nobody: For that I would say two out of five.
GetHuman: And finally- any advice for other TurboTax customers?
~Another Nobody: Call them early in the day or late. Don't forget any personal or account information you might need for TurboTax to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Another Nobody taken from his TurboTax customer service problem that occurred on November 18th, 2017.