Canada Revenue: French, once you get to agent say "No parle enf...
A Canada Revenue customer review by GetHuman user ~Jesusdawkins from November 28th, 2017
Background on ~Jesusdawkins's case
GetHuman: ~Jesusdawkins - can you tell our other Canada Revenue customers when your case took place?
~Jesusdawkins: Yes I can. It was middle of the night, on November 25th.
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 ~Jesusdawkins a list of common Canada Revenue problems)
~Jesusdawkins: "Request a Statement" was why I was trying to call.
~Jesusdawkins'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.
~Jesusdawkins: French, once you get to agent say "No parle enfrancias, parle english"**They're typically anglophone, and when I got through, it took * minutes to fix my issue!
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?
~Jesusdawkins: 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?
~Jesusdawkins: I'd give them a one out of five on communication.
GetHuman: And what about Canada Revenue's ability to quickly and effectively address your problem?
~Jesusdawkins: For that I would say one out of five.
GetHuman: And finally- any advice for other Canada Revenue customers?
~Jesusdawkins: 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 ~Jesusdawkins taken from his Canada Revenue customer service problem that occurred on November 25th, 2017.