Vitacost: I tried to call this number *-* times and twice...
A Vitacost customer review by GetHuman user GetHuman-145174 from November 10th, 2017
Background on GetHuman-145174's case
GetHuman: GetHuman-145174 - can you tell our other Vitacost customers when your case took place?
GetHuman-145174: Yes. It was afternoon, on November 9th.
GetHuman: Did you reach out to Vitacost, and if so, how?
GetHuman: And which of these common Vitacost customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-145174 a list of common Vitacost problems)
GetHuman-145174: "Cancel order" was why I was trying to call.
GetHuman-145174's review of Vitacost customer service
GetHuman: So how would you sum up your experience for GetHuman's Vitacost 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-145174: I tried to call this number *-* times and twice I got the "the number you have called is not available at this time" after waiting on hold for at least ten minutes and the other times it simply hung up after being on hold for even longer.
GetHuman: Let's quantify your experience contacting Vitacost. On a scale of 1 to 5, how easy is it go get help on a Vitacost problem?
GetHuman-145174: I'd give them a four 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-145174: I'd give them a five out of five on communication.
GetHuman: And what about Vitacost's ability to quickly and effectively address your problem?
GetHuman-145174: For that I would say five out of five.
GetHuman: And finally- any advice for other Vitacost customers?
GetHuman-145174: Call them early in the day or late. Don't forget any personal or account information you might need for Vitacost to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-145174 taken from his Vitacost customer service problem that occurred on November 9th, 2017.