Navient: Person repeated everything I said. When I said...
A Navient customer review by GetHuman user GetHuman-223310 from November 26th, 2017
Background on GetHuman-223310's case
GetHuman: GetHuman-223310 - can you tell our other Navient customers when your case took place?
GetHuman-223310: Yes I can. It was late at night, on November 19th.
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 GetHuman-223310 a list of common Navient problems)
GetHuman-223310: "Account Access" was why I was trying to call.
GetHuman-223310'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.
GetHuman-223310: Person repeated everything I said. When I said the information was inaccurate they repeated the same info. Asked for supervisor and got put on hold again... when "transferring" me to supervisor, got survey and then they hung up on me.
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?
GetHuman-223310: 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-223310: I'd give them a one out of five on communication.
GetHuman: And what about Navient's ability to quickly and effectively address your problem?
GetHuman-223310: For that I would say five out of five.
GetHuman: And finally- any advice for other Navient customers?
GetHuman-223310: 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 GetHuman-223310 taken from his Navient customer service problem that occurred on November 19th, 2017.