Canada Revenue: Couldn't get info I needed but that's my fault...
A Canada Revenue customer review by GetHuman user ~bad tax filer from November 3rd, 2017
Background on ~bad tax filer's case
GetHuman: ~bad tax filer - can you tell our other Canada Revenue customers when your case took place?
~bad tax filer: Yup. It was morning, on October 31st.
GetHuman: Did you reach out to Canada Revenue, and if so, how?
GetHuman: And which of these common Canada Revenue customer issues best describes the reason you wanted to talk to them?
(Shows ~bad tax filer a list of common Canada Revenue problems)
~bad tax filer: "Setup Payment Arrangement" was why I was trying to call.
~bad tax filer's review of Canada Revenue customer service
GetHuman: So how would you sum up your experience for GetHuman's Canada Revenue 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.
~bad tax filer: Couldn't get info I needed but that's my fault because I keep terrible records. She tried everything she could then suggested I write to them to get info.
GetHuman: Let's quantify your experience contacting Canada Revenue. On a scale of 1 to 5, how easy is it go get help on a Canada Revenue problem?
~bad tax filer: 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?
~bad tax filer: I'd give them a two out of five on communication.
GetHuman: And what about Canada Revenue's ability to quickly and effectively address your problem?
~bad tax filer: For that I would say one out of five.
GetHuman: And finally- any advice for other Canada Revenue customers?
~bad tax filer: Call them early in the day or late. Don't forget any personal or account information you might need for Canada Revenue to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~bad tax filer taken from his Canada Revenue customer service problem that occurred on October 31st, 2017.