Nissan USA: I had to wade through * long automated selectio...
A Nissan USA customer review by GetHuman user GetHuman-141577 from November 16th, 2017
Background on GetHuman-141577's case
GetHuman: GetHuman-141577 - can you tell our other Nissan USA customers when your case took place?
GetHuman-141577: Yeah. It was middle of the night, on November 8th.
GetHuman: Did you reach out to Nissan USA, and if so, how?
GetHuman: And which of these common Nissan USA customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-141577 a list of common Nissan USA problems)
GetHuman-141577: "Make a booking" was why I was trying to call.
GetHuman-141577's review of Nissan USA customer service
GetHuman: So how would you sum up your experience for GetHuman's Nissan USA 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-141577: I had to wade through * long automated selections only to find out they don't work weekends. Just calling them to tell them they missent first class mail to my address intended for another person.
GetHuman: Let's quantify your experience contacting Nissan USA. On a scale of 1 to 5, how easy is it go get help on a Nissan USA problem?
GetHuman-141577: 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-141577: I'd give them a four out of five on communication.
GetHuman: And what about Nissan USA's ability to quickly and effectively address your problem?
GetHuman-141577: For that I would say one out of five.
GetHuman: And finally- any advice for other Nissan USA customers?
GetHuman-141577: Call them early in the day or late. Don't forget any personal or account information you might need for Nissan USA to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-141577 taken from his Nissan USA customer service problem that occurred on November 8th, 2017.