My Mother was invested in several TIAA-CREF acc...
A TIAA-CREF customer review by GetHuman user ~Patty from November 6th, 2017
Background on ~Patty's case
GetHuman: ~Patty - can you tell our other TIAA-CREF customers when your case took place?
~Patty: Yup. It was afternoon, on November 4th.
GetHuman: Did you reach out to TIAA-CREF, and if so, how?
GetHuman: And which of these common TIAA-CREF customer issues best describes the reason you wanted to talk to them?
(Shows ~Patty a list of common TIAA-CREF problems)
~Patty: "Renew coverage" was why I was trying to call.
~Patty's review of TIAA-CREF customer service
GetHuman: So how would you sum up your experience for GetHuman's TIAA-CREF 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.
~Patty: My Mother was invested in several TIAA-CREF accounts with me as her beneficiary. When she died TIAA-CREF put me through ****, giving me misinformation & changing the instructions in the midst of my paper-work efforts. I had to get help from the President's Office to deal with the hurdles they threw in my way. They reduced me to tears over & over for months!
GetHuman: Let's quantify your experience contacting TIAA-CREF. On a scale of 1 to 5, how easy is it go get help on a TIAA-CREF problem?
~Patty: 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?
~Patty: I'd give them a three out of five on communication.
GetHuman: And what about TIAA-CREF's ability to quickly and effectively address your problem?
~Patty: For that I would say two out of five.
GetHuman: And finally- any advice for other TIAA-CREF customers?
~Patty: Call them early in the day or late. Don't forget any personal or account information you might need for TIAA-CREF to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Patty taken from his TIAA-CREF customer service problem that occurred on November 4th, 2017.