Care.com: not sure why all the bad reviews. i had the "a...
A Care.com customer review by GetHuman user ~georgeperdue85 from November 20th, 2017
Background on ~georgeperdue85's case
GetHuman: ~georgeperdue85 - can you tell our other Care.com customers when your case took place?
~georgeperdue85: Yeah. It was middle of the night, on November 10th.
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 ~georgeperdue85 a list of common Care.com problems)
~georgeperdue85: "Refund a Charge" was why I was trying to call.
~georgeperdue85'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.
~georgeperdue85: not sure why all the bad reviews. i had the "auto call back" option return my call so i really had no actual wait time holding a phone to my ear and they called be back in less than * min, and then solved my issue immediately
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?
~georgeperdue85: 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?
~georgeperdue85: I'd give them a one out of five on communication.
GetHuman: And what about Care.com's ability to quickly and effectively address your problem?
~georgeperdue85: For that I would say one out of five.
GetHuman: And finally- any advice for other Care.com customers?
~georgeperdue85: 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 ~georgeperdue85 taken from his Care.com customer service problem that occurred on November 10th, 2017.