CitiMortgage: I don't have the Internet. All I was trying to...
A CitiMortgage customer review by GetHuman user GetHuman-312892 from November 23rd, 2017
Background on GetHuman-312892's case
GetHuman: GetHuman-312892 - can you tell our other CitiMortgage customers when your case took place?
GetHuman-312892: Yeah. It was evening, on November 18th.
GetHuman: Did you reach out to CitiMortgage, and if so, how?
GetHuman: And which of these common CitiMortgage customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-312892 a list of common CitiMortgage problems)
GetHuman-312892: "Eligibility question" was why I was trying to call.
GetHuman-312892's review of CitiMortgage customer service
GetHuman: So how would you sum up your experience for GetHuman's CitiMortgage 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-312892: I don't have the Internet. All I was trying to do was required house next-door for the longest. And they keep referring me to the Internet it would be nice to talk to someone.
GetHuman: Let's quantify your experience contacting CitiMortgage. On a scale of 1 to 5, how easy is it go get help on a CitiMortgage problem?
GetHuman-312892: 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?
GetHuman-312892: I'd give them a two out of five on communication.
GetHuman: And what about CitiMortgage's ability to quickly and effectively address your problem?
GetHuman-312892: For that I would say five out of five.
GetHuman: And finally- any advice for other CitiMortgage customers?
GetHuman-312892: Call them early in the day or late. Don't forget any personal or account information you might need for CitiMortgage to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-312892 taken from his CitiMortgage customer service problem that occurred on November 18th, 2017.