NutriBullet: Called customer service because the motor of my...
A NutriBullet customer review by GetHuman user ~Jmels from November 25th, 2017
Background on ~Jmels's case
GetHuman: ~Jmels - can you tell our other NutriBullet customers when your case took place?
~Jmels: Yes. It was afternoon, on November 18th.
GetHuman: Did you reach out to NutriBullet, and if so, how?
GetHuman: And which of these common NutriBullet customer issues best describes the reason you wanted to talk to them?
(Shows ~Jmels a list of common NutriBullet problems)
~Jmels: "Complaint" was why I was trying to call.
~Jmels's review of NutriBullet customer service
GetHuman: So how would you sum up your experience for GetHuman's NutriBullet 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.
~Jmels: Called customer service because the motor of my nutribullet stopped working. I chose to wait on hold. After being on hold forever, an automated voice came on and said "goodbye", then disconnected the call. I called back and this time chose the "call back" option. Well, that was yesterday and I still haven't heard back...
GetHuman: Let's quantify your experience contacting NutriBullet. On a scale of 1 to 5, how easy is it go get help on a NutriBullet problem?
~Jmels: I'd give them a five 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?
~Jmels: I'd give them a two out of five on communication.
GetHuman: And what about NutriBullet's ability to quickly and effectively address your problem?
~Jmels: For that I would say one out of five.
GetHuman: And finally- any advice for other NutriBullet customers?
~Jmels: Call them early in the day or late. Don't forget any personal or account information you might need for NutriBullet to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jmels taken from his NutriBullet customer service problem that occurred on November 18th, 2017.