QuickBooks: The problem wasn't fixed and I kept being put o...
A QuickBooks customer review by GetHuman user ~sierranicole80154452 from November 26th, 2017
Background on ~sierranicole80154452's case
GetHuman: ~sierranicole80154452 - can you tell our other QuickBooks customers when your case took place?
~sierranicole80154452: Yeah. It was afternoon, on November 18th.
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 ~sierranicole80154452 a list of common QuickBooks problems)
~sierranicole80154452: "Make a purchase" was why I was trying to contact.
~sierranicole80154452'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.
~sierranicole80154452: The problem wasn't fixed and I kept being put on hold all to find out that the problem was above what they could fix
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?
~sierranicole80154452: 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?
~sierranicole80154452: 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?
~sierranicole80154452: For that I would say five out of five.
GetHuman: And finally- any advice for other QuickBooks customers?
~sierranicole80154452: 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 ~sierranicole80154452 taken from his QuickBooks customer service problem that occurred on November 18th, 2017.