Corel: Prior to this I had one question and somehow I...
A Corel customer review by GetHuman user ~redflame from November 9th, 2017
Background on ~redflame's case
GetHuman: ~redflame - can you tell our other Corel customers when your case took place?
~redflame: Yup. It was afternoon, on November 3rd.
GetHuman: Did you reach out to Corel, and if so, how?
GetHuman: And which of these common Corel customer issues best describes the reason you wanted to talk to them?
(Shows ~redflame a list of common Corel problems)
~redflame: "Technical support" was why I was trying to call.
~redflame's review of Corel customer service
GetHuman: So how would you sum up your experience for GetHuman's Corel 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.
~redflame: Prior to this I had one question and somehow I found someone who helped me right away however this time I felt like a rat in a maze. Moved, computer crashed, could not find software, had to buy another WPwhich I really like but we have sunk a good deal of money into it and now I cannot find an avenue to receive help... sad taste in my mouth. Judy Van Camp
GetHuman: Let's quantify your experience contacting Corel. On a scale of 1 to 5, how easy is it go get help on a Corel problem?
~redflame: I'd give them a two 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?
~redflame: I'd give them a one out of five on communication.
GetHuman: And what about Corel's ability to quickly and effectively address your problem?
~redflame: For that I would say two out of five.
GetHuman: And finally- any advice for other Corel customers?
~redflame: Call them early in the day or late. Don't forget any personal or account information you might need for Corel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~redflame taken from his Corel customer service problem that occurred on November 3rd, 2017.