Ancestry.com: Rep did not know company policies, couldn't ope...
A Ancestry.com customer review by GetHuman user GetHuman-344426 from November 22nd, 2017
Background on GetHuman-344426's case
GetHuman: GetHuman-344426 - can you tell our other Ancestry.com customers when your case took place?
GetHuman-344426: Sure. It was evening, on November 19th.
GetHuman: Did you reach out to Ancestry.com, and if so, how?
GetHuman: And which of these common Ancestry.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-344426 a list of common Ancestry.com problems)
GetHuman-344426: "Setup service" was why I was trying to call.
GetHuman-344426's review of Ancestry.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Ancestry.com 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-344426: Rep did not know company policies, couldn't operate their computer system well, didn't give correct information. It took three people in two phone calls to get the correct answer.
GetHuman: Let's quantify your experience contacting Ancestry.com. On a scale of 1 to 5, how easy is it go get help on a Ancestry.com problem?
GetHuman-344426: I'd give them a three 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-344426: I'd give them a two out of five on communication.
GetHuman: And what about Ancestry.com's ability to quickly and effectively address your problem?
GetHuman-344426: For that I would say three out of five.
GetHuman: And finally- any advice for other Ancestry.com customers?
GetHuman-344426: Call them early in the day or late. Don't forget any personal or account information you might need for Ancestry.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-344426 taken from his Ancestry.com customer service problem that occurred on November 19th, 2017.