Citi Student Loans: I had to press * five times. The customer servi...
A Citi Student Loans customer review by GetHuman user ~harveyjlime from November 2nd, 2017
Background on ~harveyjlime's case
GetHuman: ~harveyjlime - can you tell our other Citi Student Loans customers when your case took place?
~harveyjlime: Yes. It was middle of the night, on October 24th.
GetHuman: Did you reach out to Citi Student Loans, and if so, how?
GetHuman: And which of these common Citi Student Loans customer issues best describes the reason you wanted to talk to them?
(Shows ~harveyjlime a list of common Citi Student Loans problems)
~harveyjlime: "Extension" was why I was trying to call.
~harveyjlime's review of Citi Student Loans customer service
GetHuman: So how would you sum up your experience for GetHuman's Citi Student Loans 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.
~harveyjlime: I had to press * five times. The customer service person picked up right away. They were very helpful and answered my question right away.
GetHuman: Let's quantify your experience contacting Citi Student Loans. On a scale of 1 to 5, how easy is it go get help on a Citi Student Loans problem?
~harveyjlime: 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?
~harveyjlime: I'd give them a five out of five on communication.
GetHuman: And what about Citi Student Loans's ability to quickly and effectively address your problem?
~harveyjlime: For that I would say five out of five.
GetHuman: And finally- any advice for other Citi Student Loans customers?
~harveyjlime: Call them early in the day or late. Don't forget any personal or account information you might need for Citi Student Loans to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~harveyjlime taken from his Citi Student Loans customer service problem that occurred on October 24th, 2017.