Nissan Title Services: I was given another to call where I did wait on...
A Nissan Title Services customer review by GetHuman user ~Bimmer721 from November 23rd, 2017
Background on ~Bimmer721's case
GetHuman: ~Bimmer721 - can you tell our other Nissan Title Services customers when your case took place?
~Bimmer721: Yes I can. It was afternoon, on November 13th.
GetHuman: Did you reach out to Nissan Title Services, and if so, how?
GetHuman: And which of these common Nissan Title Services customer issues best describes the reason you wanted to talk to them?
(Shows ~Bimmer721 a list of common Nissan Title Services problems)
~Bimmer721: "Where to buy" was why I was trying to call.
~Bimmer721's review of Nissan Title Services customer service
GetHuman: So how would you sum up your experience for GetHuman's Nissan Title Services 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.
~Bimmer721: I was given another to call where I did wait on hold for a while then got a recording that did not answer my question.
GetHuman: Let's quantify your experience contacting Nissan Title Services. On a scale of 1 to 5, how easy is it go get help on a Nissan Title Services problem?
~Bimmer721: I'd give them a one 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?
~Bimmer721: I'd give them a one out of five on communication.
GetHuman: And what about Nissan Title Services's ability to quickly and effectively address your problem?
~Bimmer721: For that I would say one out of five.
GetHuman: And finally- any advice for other Nissan Title Services customers?
~Bimmer721: Call them early in the day or late. Don't forget any personal or account information you might need for Nissan Title Services to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Bimmer721 taken from his Nissan Title Services customer service problem that occurred on November 13th, 2017.