Navient: Spoke to someone whose English was so atrocious...
A Navient customer review by GetHuman user ~Amber from November 5th, 2017
Background on ~Amber's case
GetHuman: ~Amber - can you tell our other Navient customers when your case took place?
~Amber: Yup. It was middle of the night, on October 28th.
GetHuman: Did you reach out to Navient, and if so, how?
GetHuman: And which of these common Navient customer issues best describes the reason you wanted to talk to them?
(Shows ~Amber a list of common Navient problems)
~Amber: "Repayment question" was why I was trying to call.
~Amber's review of Navient customer service
GetHuman: So how would you sum up your experience for GetHuman's Navient 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.
~Amber: Spoke to someone whose English was so atrocious that I could not understand a word he said. His name was Ackmen-Abijidabi or something like that. Asked to be transferred to someone whose English was better. Was then transferred to Muhammed-Abil-Amabenujab. All I could understand from him was, "Try going online to fix your problem." Horrendous.
GetHuman: Let's quantify your experience contacting Navient. On a scale of 1 to 5, how easy is it go get help on a Navient problem?
~Amber: I'd give them a two 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?
~Amber: I'd give them a five out of five on communication.
GetHuman: And what about Navient's ability to quickly and effectively address your problem?
~Amber: For that I would say four out of five.
GetHuman: And finally- any advice for other Navient customers?
~Amber: Call them early in the day or late. Don't forget any personal or account information you might need for Navient to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Amber taken from his Navient customer service problem that occurred on October 28th, 2017.