Ticketmaster: I couldn't get through (busy signal) with the r...
A Ticketmaster customer review by GetHuman user ~lemonstuff from November 26th, 2017
Background on ~lemonstuff's case
GetHuman: ~lemonstuff - can you tell our other Ticketmaster customers when your case took place?
~lemonstuff: Yes I can. It was late at night, on November 21st.
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 ~lemonstuff a list of common Ticketmaster problems)
~lemonstuff: "Track an Order" was why I was trying to call.
~lemonstuff'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.
~lemonstuff: I couldn't get through (busy signal) with the regular customer service number, so I tried the number suggested and got a human quite quickly. The rep was helpful and resolved my issue completely within minutes of talking.
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?
~lemonstuff: 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?
~lemonstuff: 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?
~lemonstuff: For that I would say four out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
~lemonstuff: Call them early in the day or late. 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 ~lemonstuff taken from his Ticketmaster customer service problem that occurred on November 21st, 2017.