Quicken: I tried sending an e-mail & it did not connect...
A Quicken customer review by GetHuman user GetHuman-239215 from October 30th, 2017
Background on GetHuman-239215's case
GetHuman: GetHuman-239215 - can you tell our other Quicken customers when your case took place?
GetHuman-239215: Yes I can. It was afternoon, on October 26th.
GetHuman: Did you reach out to Quicken, and if so, how?
GetHuman: And which of these common Quicken customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-239215 a list of common Quicken problems)
GetHuman-239215: "Change order" was why I was trying to call.
GetHuman-239215's review of Quicken customer service
GetHuman: So how would you sum up your experience for GetHuman's Quicken 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-239215: I tried sending an e-mail & it did not connect. But then I tried Live Chat & got a person right away & he was able to solve my problem. I really appreciate your info because I had tried for some time to find a phone * or e-mail connection with Quicken.
GetHuman: Let's quantify your experience contacting Quicken. On a scale of 1 to 5, how easy is it go get help on a Quicken problem?
GetHuman-239215: 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?
GetHuman-239215: I'd give them a one out of five on communication.
GetHuman: And what about Quicken's ability to quickly and effectively address your problem?
GetHuman-239215: For that I would say one out of five.
GetHuman: And finally- any advice for other Quicken customers?
GetHuman-239215: Call them early in the day or late. Don't forget any personal or account information you might need for Quicken to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-239215 taken from his Quicken customer service problem that occurred on October 26th, 2017.