TurboTax: After a long hunt for the phone number I found...
A TurboTax customer review by GetHuman user GetHuman-229611 from November 10th, 2017
Background on GetHuman-229611's case
GetHuman: GetHuman-229611 - can you tell our other TurboTax customers when your case took place?
GetHuman-229611: Sure. It was evening, on November 3rd.
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 GetHuman-229611 a list of common TurboTax problems)
GetHuman-229611: "Refund" was why I was trying to call.
GetHuman-229611'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.
GetHuman-229611: After a long hunt for the phone number I found it but could not even within the hours suggested. After all day trying to contact Turbo Tax I still have not talk to them and now the tax deadline has passed.*What do I do and how do I fix this
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?
GetHuman-229611: 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-229611: I'd give them a two out of five on communication.
GetHuman: And what about TurboTax's ability to quickly and effectively address your problem?
GetHuman-229611: For that I would say three out of five.
GetHuman: And finally- any advice for other TurboTax customers?
GetHuman-229611: 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 GetHuman-229611 taken from his TurboTax customer service problem that occurred on November 3rd, 2017.