QuickBooks: Called twice for two of my accounts. First one...
A QuickBooks customer review by GetHuman user ~accountant153 from November 24th, 2017
Background on ~accountant153's case
GetHuman: ~accountant153 - can you tell our other QuickBooks customers when your case took place?
~accountant153: Yup. It was middle of the night, on November 22nd.
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 ~accountant153 a list of common QuickBooks problems)
~accountant153: "Technical support" was why I was trying to contact.
~accountant153'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.
~accountant153: Called twice for two of my accounts. First one was a breeze. Issue was solved quickly. Second one was problematic but in the end I was please with the outcome. Very Good customer service overall.
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?
~accountant153: 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?
~accountant153: 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?
~accountant153: For that I would say three out of five.
GetHuman: And finally- any advice for other QuickBooks customers?
~accountant153: 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 ~accountant153 taken from his QuickBooks customer service problem that occurred on November 22nd, 2017.