TurboTax: The service representive who helped me was cour...
A TurboTax customer review by GetHuman user ~debby from November 14th, 2017
Background on ~debby's case
GetHuman: ~debby - can you tell our other TurboTax customers when your case took place?
~debby: Yeah. It was afternoon, on November 9th.
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 ~debby a list of common TurboTax problems)
~debby: "Payment Arrangement" was why I was trying to call.
~debby'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.
~debby: The service representive who helped me was courteous, and helped me with my problem. She e-mailed me the instructions I needed to clear up my problem, and since I was at work, she had me go on-line and also showed me step by step what I would needed to do when I got home. These same instructions were in the e-mail she sent very promptly.
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?
~debby: 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?
~debby: I'd give them a one out of five on communication.
GetHuman: And what about TurboTax's ability to quickly and effectively address your problem?
~debby: For that I would say two out of five.
GetHuman: And finally- any advice for other TurboTax customers?
~debby: 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 ~debby taken from his TurboTax customer service problem that occurred on November 9th, 2017.