23andMe: Very hard to order replacement kit but was call...
A 23andMe customer review by GetHuman user ~qualimatic from November 18th, 2017
Background on ~qualimatic's case
GetHuman: ~qualimatic - can you tell our other 23andMe customers when your case took place?
~qualimatic: Yes. It was middle of the night, on November 11th.
GetHuman: Did you reach out to 23andMe, and if so, how?
GetHuman: And which of these common 23andMe customer issues best describes the reason you wanted to talk to them?
(Shows ~qualimatic a list of common 23andMe problems)
~qualimatic: "Setup an account" was why I was trying to call.
~qualimatic's review of 23andMe customer service
GetHuman: So how would you sum up your experience for GetHuman's 23andMe 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.
~qualimatic: Very hard to order replacement kit but was called by ***-***-**** after several emails to complain. Spit kit was confusing and sent without the critical DNA solution mix so I was sent email to order replace kit for $**. I am not sure if I can recommend but will wait and see after my results.
GetHuman: Let's quantify your experience contacting 23andMe. On a scale of 1 to 5, how easy is it go get help on a 23andMe problem?
~qualimatic: I'd give them a two 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?
~qualimatic: I'd give them a five out of five on communication.
GetHuman: And what about 23andMe's ability to quickly and effectively address your problem?
~qualimatic: For that I would say five out of five.
GetHuman: And finally- any advice for other 23andMe customers?
~qualimatic: Call them early in the day or late. Don't forget any personal or account information you might need for 23andMe to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~qualimatic taken from his 23andMe customer service problem that occurred on November 11th, 2017.