National Visa Center: Have been calling all day - at least ** times...
A National Visa Center customer review by GetHuman user ~Idontknow from November 18th, 2017
Background on ~Idontknow's case
GetHuman: ~Idontknow - can you tell our other National Visa Center customers when your case took place?
~Idontknow: Yup. It was afternoon, on November 11th.
GetHuman: Did you reach out to National Visa Center, and if so, how?
GetHuman: And which of these common National Visa Center customer issues best describes the reason you wanted to talk to them?
(Shows ~Idontknow a list of common National Visa Center problems)
~Idontknow: "Ask for Immigration Help" was why I was trying to call.
~Idontknow's review of National Visa Center customer service
GetHuman: So how would you sum up your experience for GetHuman's National Visa Center 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.
~Idontknow: Have been calling all day - at least ** times - always busy. This is even worse than trying to get someone to help at USCIS.
GetHuman: Let's quantify your experience contacting National Visa Center. On a scale of 1 to 5, how easy is it go get help on a National Visa Center problem?
~Idontknow: 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?
~Idontknow: I'd give them a one out of five on communication.
GetHuman: And what about National Visa Center's ability to quickly and effectively address your problem?
~Idontknow: For that I would say one out of five.
GetHuman: And finally- any advice for other National Visa Center customers?
~Idontknow: Call them early in the day or late. Don't forget any personal or account information you might need for National Visa Center to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Idontknow taken from his National Visa Center customer service problem that occurred on November 11th, 2017.