QuickBooks: I've had to call QB * times now for things wron...
A QuickBooks customer review by GetHuman user ~Angry about QB from November 25th, 2017
Background on ~Angry about QB's case
GetHuman: ~Angry about QB - can you tell our other QuickBooks customers when your case took place?
~Angry about QB: Yup. It was morning, on November 24th.
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 ~Angry about QB a list of common QuickBooks problems)
~Angry about QB: "Technical Support" was why I was trying to contact.
~Angry about QB'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.
~Angry about QB: I've had to call QB * times now for things wrong in their online coding. They have never been able to help me and it takes literally hours to try. I dread calling them each time.
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?
~Angry about QB: 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?
~Angry about QB: I'd give them a five out of five on communication.
GetHuman: And what about QuickBooks's ability to quickly and effectively address your problem?
~Angry about QB: For that I would say one out of five.
GetHuman: And finally- any advice for other QuickBooks customers?
~Angry about QB: 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 ~Angry about QB taken from his QuickBooks customer service problem that occurred on November 24th, 2017.