H&R Block: The Guys name was John Cross and he did a Terri...
A H&R Block customer review by GetHuman user ~Alex from November 26th, 2017
Background on ~Alex's case
GetHuman: ~Alex - can you tell our other H&R Block customers when your case took place?
~Alex: Yes. It was morning, on November 20th.
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 ~Alex a list of common H&R Block problems)
~Alex: "Can't Login" was why I was trying to call.
~Alex'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.
~Alex: The Guys name was John Cross and he did a Terrible Job with communicating. Without telling me he changed me over to a **** and tried Charging an additional $*** for ** mins of work. If this what kind of employee's this company has. I am better off doing this blind with a monkey typing for me. Will NEVER go back to them again after than deception and shady treatment.
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?
~Alex: 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?
~Alex: I'd give them a three out of five on communication.
GetHuman: And what about H&R Block's ability to quickly and effectively address your problem?
~Alex: For that I would say one out of five.
GetHuman: And finally- any advice for other H&R Block customers?
~Alex: 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 ~Alex taken from his H&R Block customer service problem that occurred on November 20th, 2017.