Called TD bank and talked to Tony. He couldn't...
A TD Bank customer review by GetHuman user GetHuman-45912 from November 16th, 2017
Background on GetHuman-45912's case
GetHuman: GetHuman-45912 - can you tell our other TD Bank customers when your case took place?
GetHuman-45912: Yeah. It was evening, on November 13th.
GetHuman: Did you reach out to TD Bank, and if so, how?
GetHuman: And which of these common TD Bank customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-45912 a list of common TD Bank problems)
GetHuman-45912: "Account Setup" was why I was trying to call.
GetHuman-45912's review of TD Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's TD Bank 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-45912: Called TD bank and talked to Tony. He couldn't help so he transfered me to FCE at ***-***-****. That was a Wells Fargo number, Ashley said that she could help TD bank customers. Terrible customer relations and service. I am changing banks.*Fred Stutzenberger, Clemson, SC *****-****
GetHuman: Let's quantify your experience contacting TD Bank. On a scale of 1 to 5, how easy is it go get help on a TD Bank problem?
GetHuman-45912: 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-45912: I'd give them a two out of five on communication.
GetHuman: And what about TD Bank's ability to quickly and effectively address your problem?
GetHuman-45912: For that I would say three out of five.
GetHuman: And finally- any advice for other TD Bank customers?
GetHuman-45912: Call them early in the day or late. Don't forget any personal or account information you might need for TD Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-45912 taken from his TD Bank customer service problem that occurred on November 13th, 2017.