Care.com: Ustedes dan un cervicio mal****simo,si uno no l...
Una recensione del cliente Care.com da parte dell'utente GetHuman ~Gisela peralta da novembre 28º, 2017
Background on ~Gisela peralta's case
GetHuman: ~Gisela peralta - can you tell our other Care.com customers when your case took place?
~Gisela peralta: Sure. It was morning, on novembre 20º.
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 ~Gisela peralta a list of common Care.com problems)
~Gisela peralta: "Overcharge/Strange charge" was why I was trying to call.
~Gisela peralta'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.
~Gisela peralta: Ustedes dan un cervicio mal****simo,si uno no le paga ustede no le consiguen trabajo a uno y eso no ser serio. Lleno y llen**** aplicaciones y nada que me ayudan despu****s que deje de pagarle.
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?
~Gisela peralta: 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?
~Gisela peralta: I'd give them a three out of five on communication.
GetHuman: And what about Care.com's ability to quickly and effectively address your problem?
~Gisela peralta: For that I would say two out of five.
GetHuman: And finally- any advice for other Care.com customers?
~Gisela peralta: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Care.com sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~Gisela peralta taken from his Care.com customer service problem that occurred on novembre 20º, 2017.