Match.com: Compliant
A Match.com customer review by GetHuman user GetHuman-lenonthe from December 1st, 2017
Background on GetHuman-lenonthe's case
GetHuman: GetHuman-lenonthe - can you tell our other Match.com customers when your case took place?
GetHuman-lenonthe: Yes. It was evening, on November 25th.
GetHuman: Did you reach out to Match.com, and if so, how?
GetHuman: And which of these common Match.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-lenonthe a list of common Match.com problems)
GetHuman-lenonthe: "Lower my bill" was why I was trying to call.
GetHuman-lenonthe's review of Match.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Match.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-lenonthe: Compliant
GetHuman: Can you tell the rest of us a bit more from what happened on 11/25/17?
GetHuman-lenonthe: You would have thought.Since Match screwed up my ability to communicate for at least * days.They would have extended my subscription
GetHuman: Let's quantify your experience contacting Match.com. On a scale of 1 to 5, how easy is it go get help on a Match.com problem?
GetHuman-lenonthe: I'd give them a two 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-lenonthe: I'd give them a one out of five on communication.
GetHuman: And what about Match.com's ability to quickly and effectively address your problem?
GetHuman-lenonthe: For that I would say one out of five.
GetHuman: And finally- any advice for other Match.com customers?
GetHuman-lenonthe: Call them early in the day or late. Don't forget any personal or account information you might need for Match.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-lenonthe taken from his Match.com customer service problem that occurred on November 25th, 2017.