No one H&R Block takes responsibility for anyth...
A H&R Block customer review by GetHuman user GetHuman-253936 from November 26th, 2017
Background on GetHuman-253936's case
GetHuman: GetHuman-253936 - can you tell our other H&R Block customers when your case took place?
GetHuman-253936: Sure. It was morning, on November 21st.
GetHuman: Did you reach out to H&R Block, and if so, how?
GetHuman: And which of these common H&R Block customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-253936 a list of common H&R Block problems)
GetHuman-253936: "Can't Login" was why I was trying to call.
GetHuman-253936's review of H&R Block customer service
GetHuman: So how would you sum up your experience for GetHuman's H&R Block 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-253936: No one H&R Block takes responsibility for anything, whether it be online, software or in-person with. Worst experience ever. Each office might as well be an entirely different company, blaming the next person in line for the companies mistakes.
GetHuman: Let's quantify your experience contacting H&R Block. On a scale of 1 to 5, how easy is it go get help on a H&R Block problem?
GetHuman-253936: I'd give them a one 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-253936: I'd give them a one out of five on communication.
GetHuman: And what about H&R Block's ability to quickly and effectively address your problem?
GetHuman-253936: For that I would say one out of five.
GetHuman: And finally- any advice for other H&R Block customers?
GetHuman-253936: Call them early in the day or late. Don't forget any personal or account information you might need for H&R Block to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-253936 taken from his H&R Block customer service problem that occurred on November 21st, 2017.