QuickBooks: I was shocked and surprised to have my call ans...
A QuickBooks customer review by GetHuman user GetHuman-227771 from November 26th, 2017
Background on GetHuman-227771's case
GetHuman: GetHuman-227771 - can you tell our other QuickBooks customers when your case took place?
GetHuman-227771: Sure. It was morning, on November 17th.
GetHuman: Did you reach out to QuickBooks, and if so, how?
GetHuman: And which of these common QuickBooks customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-227771 a list of common QuickBooks problems)
GetHuman-227771: "Technical Support" was why I was trying to contact.
GetHuman-227771's review of QuickBooks customer service
GetHuman: So how would you sum up your experience for GetHuman's QuickBooks 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-227771: I was shocked and surprised to have my call answered after such a short time. The guy on the other end helped me with workarounds for my problems and got my problem solved. Can't believe it!
GetHuman: Let's quantify your experience contacting QuickBooks. On a scale of 1 to 5, how easy is it go get help on a QuickBooks problem?
GetHuman-227771: 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?
GetHuman-227771: I'd give them a two out of five on communication.
GetHuman: And what about QuickBooks's ability to quickly and effectively address your problem?
GetHuman-227771: For that I would say one out of five.
GetHuman: And finally- any advice for other QuickBooks customers?
GetHuman-227771: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for QuickBooks to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-227771 taken from his QuickBooks customer service problem that occurred on November 17th, 2017.