Canada Revenue: Cant get connected to this phone number. It has...
A Canada Revenue customer review by GetHuman user GetHuman-349535 from November 27th, 2017
Background on GetHuman-349535's case
GetHuman: GetHuman-349535 - can you tell our other Canada Revenue customers when your case took place?
GetHuman-349535: 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 GetHuman-349535 a list of common Canada Revenue problems)
GetHuman-349535: "Request a Statement" was why I was trying to call.
GetHuman-349535'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.
GetHuman-349535: Cant get connected to this phone number. It has a busy signal. How am I suppose to talk to someone about HST when I get a busy signal, no queue or voicemail...
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?
GetHuman-349535: 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?
GetHuman-349535: 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?
GetHuman-349535: For that I would say one out of five.
GetHuman: And finally- any advice for other Canada Revenue customers?
GetHuman-349535: 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 GetHuman-349535 taken from his Canada Revenue customer service problem that occurred on November 25th, 2017.