23andMe: My issue was related to the accidental sealing...
A 23andMe customer review by GetHuman user ~Jeff from November 21st, 2017
Background on ~Jeff's case
GetHuman: ~Jeff - can you tell our other 23andMe customers when your case took place?
~Jeff: Yeah. It was afternoon, on November 15th.
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 ~Jeff a list of common 23andMe problems)
~Jeff: "Setup an account" was why I was trying to call.
~Jeff'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.
~Jeff: My issue was related to the accidental sealing of the return container before writing down the bar code number. I was concerned that reopening the sealed container to get the number and then taping it shut would be a problem. Not so. Happens all the time the fella said. Took longer to find a number to call (none on website) than to get the answer to resolve my dilemma.
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?
~Jeff: 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?
~Jeff: I'd give them a four out of five on communication.
GetHuman: And what about 23andMe's ability to quickly and effectively address your problem?
~Jeff: For that I would say five out of five.
GetHuman: And finally- any advice for other 23andMe customers?
~Jeff: 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 ~Jeff taken from his 23andMe customer service problem that occurred on November 15th, 2017.