TransAmerica: Got someone right on the phone. However this p...
A TransAmerica customer review by GetHuman user GetHuman-161880 from November 24th, 2017
Background on GetHuman-161880's case
GetHuman: GetHuman-161880 - can you tell our other TransAmerica customers when your case took place?
GetHuman-161880: Yes I can. It was afternoon, on November 18th.
GetHuman: Did you reach out to TransAmerica, and if so, how?
GetHuman: And which of these common TransAmerica customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-161880 a list of common TransAmerica problems)
GetHuman-161880: "Setup an account" was why I was trying to call.
GetHuman-161880's review of TransAmerica customer service
GetHuman: So how would you sum up your experience for GetHuman's TransAmerica 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-161880: Got someone right on the phone. However this particular office did not service my policy. All I needed was a fax number for the Admin. Office so rep. was able to assist me.
GetHuman: Let's quantify your experience contacting TransAmerica. On a scale of 1 to 5, how easy is it go get help on a TransAmerica problem?
GetHuman-161880: 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?
GetHuman-161880: I'd give them a five out of five on communication.
GetHuman: And what about TransAmerica's ability to quickly and effectively address your problem?
GetHuman-161880: For that I would say four out of five.
GetHuman: And finally- any advice for other TransAmerica customers?
GetHuman-161880: Call them early in the day or late. Don't forget any personal or account information you might need for TransAmerica to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-161880 taken from his TransAmerica customer service problem that occurred on November 18th, 2017.