HigherOne: When I tried calling using my house phone, the...
A HigherOne customer review by GetHuman user ~Jessica from November 21st, 2017
Background on ~Jessica's case
GetHuman: ~Jessica - can you tell our other HigherOne customers when your case took place?
~Jessica: Yeah. It was morning, on November 13th.
GetHuman: Did you reach out to HigherOne, and if so, how?
GetHuman: And which of these common HigherOne customer issues best describes the reason you wanted to talk to them?
(Shows ~Jessica a list of common HigherOne problems)
~Jessica: "Request a loan" was why I was trying to call.
~Jessica's review of HigherOne customer service
GetHuman: So how would you sum up your experience for GetHuman's HigherOne 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.
~Jessica: When I tried calling using my house phone, the machine wouldn't recognize any of the buttons I was pressing. So I hung up and used my cell phone to call. I was on hold for about * minutes until a representative named Jessica, just like me, picked up and quickly assisted me. She was very friendly and very helpful.
GetHuman: Let's quantify your experience contacting HigherOne. On a scale of 1 to 5, how easy is it go get help on a HigherOne problem?
~Jessica: 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?
~Jessica: I'd give them a five out of five on communication.
GetHuman: And what about HigherOne's ability to quickly and effectively address your problem?
~Jessica: For that I would say one out of five.
GetHuman: And finally- any advice for other HigherOne customers?
~Jessica: Call them early in the day or late. Don't forget any personal or account information you might need for HigherOne to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jessica taken from his HigherOne customer service problem that occurred on November 13th, 2017.