Travis Credit Union: won't go higher than ** minutes or I would've p...
A Travis Credit Union customer review by GetHuman user ~GregBrady from November 27th, 2017
Background on ~GregBrady's case
GetHuman: ~GregBrady - can you tell our other Travis Credit Union customers when your case took place?
~GregBrady: Yes. It was afternoon, on November 18th.
GetHuman: Did you reach out to Travis Credit Union, and if so, how?
GetHuman: And which of these common Travis Credit Union customer issues best describes the reason you wanted to talk to them?
(Shows ~GregBrady a list of common Travis Credit Union problems)
~GregBrady: "Question" was why I was trying to call.
~GregBrady's review of Travis Credit Union customer service
GetHuman: So how would you sum up your experience for GetHuman's Travis Credit Union 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.
~GregBrady: won't go higher than ** minutes or I would've put more. Anyways... TCU has NO LIVE PERSON AFTER HOURS... so if you have a problem... TOO BAD... TOUGH LUCK
GetHuman: Let's quantify your experience contacting Travis Credit Union. On a scale of 1 to 5, how easy is it go get help on a Travis Credit Union problem?
~GregBrady: I'd give them a three 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?
~GregBrady: I'd give them a two out of five on communication.
GetHuman: And what about Travis Credit Union's ability to quickly and effectively address your problem?
~GregBrady: For that I would say one out of five.
GetHuman: And finally- any advice for other Travis Credit Union customers?
~GregBrady: Call them early in the day or late. Don't forget any personal or account information you might need for Travis Credit Union to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~GregBrady taken from his Travis Credit Union customer service problem that occurred on November 18th, 2017.