Care.com: Reaching a human was hard. When I followed the...
A Care.com customer review by GetHuman user GetHuman-341822 from November 21st, 2017
Background on GetHuman-341822's case
GetHuman: GetHuman-341822 - can you tell our other Care.com customers when your case took place?
GetHuman-341822: Yeah. It was middle of the night, on November 11th.
GetHuman: Did you reach out to Care.com, and if so, how?
GetHuman: And which of these common Care.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-341822 a list of common Care.com problems)
GetHuman-341822: "Setup service" was why I was trying to call.
GetHuman-341822's review of Care.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Care.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-341822: Reaching a human was hard. When I followed the prompts, it didn't get me there, but referred me back to the web site, which didn't help. I had to "lie" by pressing the numbers shown on gethuman.com. Once I got a human, he was great.
GetHuman: Let's quantify your experience contacting Care.com. On a scale of 1 to 5, how easy is it go get help on a Care.com problem?
GetHuman-341822: 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-341822: I'd give them a two out of five on communication.
GetHuman: And what about Care.com's ability to quickly and effectively address your problem?
GetHuman-341822: For that I would say five out of five.
GetHuman: And finally- any advice for other Care.com customers?
GetHuman-341822: Call them early in the day or late. Don't forget any personal or account information you might need for Care.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-341822 taken from his Care.com customer service problem that occurred on November 11th, 2017.