Ticketmaster: Too much "technology." I don't want to talk to...
Ticketmaster Ulasan pelanggan oleh pengguna GetHuman ~tedj47 dari November 28, 2017
Background on ~tedj47's case
GetHuman: ~tedj47 - can you tell our other Ticketmaster customers when your case took place?
~tedj47: Yes I can. It was morning, on November 23.
GetHuman: Did you reach out to Ticketmaster, and if so, how?
GetHuman: And which of these common Ticketmaster customer issues best describes the reason you wanted to talk to them?
(Shows ~tedj47 a list of common Ticketmaster problems)
~tedj47: "Refund" was why I was trying to call.
~tedj47's review of Ticketmaster customer service
GetHuman: So how would you sum up your experience for GetHuman's Ticketmaster 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.
~tedj47: Too much "technology." I don't want to talk to "technology", I want to speak to a living, breathing person. Bottom line, my "lost tickets" for Earth, Wind, and Fire*Chicago are still lost. No one takes responsibility for anything! As I live and breathe, I am calling a lawyer.
GetHuman: Let's quantify your experience contacting Ticketmaster. On a scale of 1 to 5, how easy is it go get help on a Ticketmaster problem?
~tedj47: 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?
~tedj47: I'd give them a four out of five on communication.
GetHuman: And what about Ticketmaster's ability to quickly and effectively address your problem?
~tedj47: For that I would say three out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
~tedj47: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk Ticketmaster mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~tedj47 taken from his Ticketmaster customer service problem that occurred on November 23, 2017.