Meetup.com: line answered quickly, pressed *, had a less th...
A Meetup.com customer review by GetHuman user ~naplesbeachbum from November 20th, 2017
Background on ~naplesbeachbum's case
GetHuman: ~naplesbeachbum - can you tell our other Meetup.com customers when your case took place?
~naplesbeachbum: Yes I can. It was afternoon, on November 14th.
GetHuman: Did you reach out to Meetup.com, and if so, how?
GetHuman: And which of these common Meetup.com customer issues best describes the reason you wanted to talk to them?
(Shows ~naplesbeachbum a list of common Meetup.com problems)
~naplesbeachbum: "Change plan" was why I was trying to contact.
~naplesbeachbum's review of Meetup.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Meetup.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.
~naplesbeachbum: line answered quickly, pressed *, had a less than * minute wait while transferred to a community specialist. person was very helpful and thoroughly answered all my questions
GetHuman: Let's quantify your experience contacting Meetup.com. On a scale of 1 to 5, how easy is it go get help on a Meetup.com problem?
~naplesbeachbum: 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?
~naplesbeachbum: I'd give them a four out of five on communication.
GetHuman: And what about Meetup.com's ability to quickly and effectively address your problem?
~naplesbeachbum: For that I would say three out of five.
GetHuman: And finally- any advice for other Meetup.com customers?
~naplesbeachbum: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Meetup.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~naplesbeachbum taken from his Meetup.com customer service problem that occurred on November 14th, 2017.