Ticketmaster: Customer serv rep, Sharon from West Virginia of...
A Ticketmaster customer review by GetHuman user ~Bonnie Consola from November 28th, 2017
Background on ~Bonnie Consola's case
GetHuman: ~Bonnie Consola - can you tell our other Ticketmaster customers when your case took place?
~Bonnie Consola: Sure. It was late at night, on November 25th.
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 ~Bonnie Consola a list of common Ticketmaster problems)
~Bonnie Consola: "Cancel order" was why I was trying to contact.
~Bonnie Consola'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.
~Bonnie Consola: Customer serv rep, Sharon from West Virginia office was one of the most helpful and caring people I've ever dealt with. Helped me secure a refund of * tickets.
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?
~Bonnie Consola: 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?
~Bonnie Consola: I'd give them a three out of five on communication.
GetHuman: And what about Ticketmaster's ability to quickly and effectively address your problem?
~Bonnie Consola: For that I would say four out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
~Bonnie Consola: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Ticketmaster to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Bonnie Consola taken from his Ticketmaster customer service problem that occurred on November 25th, 2017.