IRS: Too much call volume, so the recording just sai...
A IRS customer review by GetHuman user ~idonthaveascreenname from November 28th, 2017
Background on ~idonthaveascreenname's case
GetHuman: ~idonthaveascreenname - can you tell our other IRS customers when your case took place?
~idonthaveascreenname: Sure. It was morning, on November 19th.
GetHuman: Did you reach out to IRS, and if so, how?
GetHuman: And which of these common IRS customer issues best describes the reason you wanted to talk to them?
(Shows ~idonthaveascreenname a list of common IRS problems)
~idonthaveascreenname: "Tax Question" was why I was trying to call.
~idonthaveascreenname's review of IRS customer service
GetHuman: So how would you sum up your experience for GetHuman's IRS 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.
~idonthaveascreenname: Too much call volume, so the recording just said go to irs.gov but I've gone there and it won't tell me the status of my return filed * months ago. I have repeatedly tried to call and always get the same "due to extremely high call volume, your call can not be answered at this time".
GetHuman: Let's quantify your experience contacting IRS. On a scale of 1 to 5, how easy is it go get help on a IRS problem?
~idonthaveascreenname: 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?
~idonthaveascreenname: I'd give them a five out of five on communication.
GetHuman: And what about IRS's ability to quickly and effectively address your problem?
~idonthaveascreenname: For that I would say one out of five.
GetHuman: And finally- any advice for other IRS customers?
~idonthaveascreenname: Call them early in the day or late. Don't forget any personal or account information you might need for IRS to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~idonthaveascreenname taken from his IRS customer service problem that occurred on November 19th, 2017.