Ticketmaster: If you are so ******* busy while Assisting CC's...
Eine Ticketmaster Kundenbewertung durch GetHuman-Benutzer ~Kshiti Hernandez von November 25., 2017
Background on ~Kshiti Hernandez's case
GetHuman: ~Kshiti Hernandez - can you tell our other Ticketmaster customers when your case took place?
~Kshiti Hernandez: Yeah. It was middle of the night, on November 17..
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 ~Kshiti Hernandez a list of common Ticketmaster problems)
~Kshiti Hernandez: "Refund a Charge" was why I was trying to call.
~Kshiti Hernandez'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.
~Kshiti Hernandez: If you are so ******* busy while Assisting CC's just add ******* more agents... Least give the proper traning *.*
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?
~Kshiti Hernandez: 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?
~Kshiti Hernandez: I'd give them a five out of five on communication.
GetHuman: And what about Ticketmaster's ability to quickly and effectively address your problem?
~Kshiti Hernandez: For that I would say two out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
~Kshiti Hernandez: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Ticketmaster weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~Kshiti Hernandez taken from his Ticketmaster customer service problem that occurred on November 17., 2017.