National Visa Center: Had to dial this number ** times before it went...
A National Visa Center customer review by GetHuman user ~Wanton Soup from November 22nd, 2017
Background on ~Wanton Soup's case
GetHuman: ~Wanton Soup - can you tell our other National Visa Center customers when your case took place?
~Wanton Soup: Yup. It was morning, on November 19th.
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 ~Wanton Soup a list of common National Visa Center problems)
~Wanton Soup: "Missing Order" was why I was trying to call.
~Wanton Soup'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.
~Wanton Soup: Had to dial this number ** times before it went through! Worker-person at other end was generally unhelpful.
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?
~Wanton Soup: 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?
~Wanton Soup: I'd give them a four out of five on communication.
GetHuman: And what about National Visa Center's ability to quickly and effectively address your problem?
~Wanton Soup: For that I would say one out of five.
GetHuman: And finally- any advice for other National Visa Center customers?
~Wanton Soup: 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 ~Wanton Soup taken from his National Visa Center customer service problem that occurred on November 19th, 2017.