Ticketmaster: He understood my prolem and explained to me how...
A Ticketmaster customer review by GetHuman user GetHuman-290196 from November 14th, 2017
Background on GetHuman-290196's case
GetHuman: GetHuman-290196 - can you tell our other Ticketmaster customers when your case took place?
GetHuman-290196: Sure. It was afternoon, on November 6th.
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 GetHuman-290196 a list of common Ticketmaster problems)
GetHuman-290196: "Purchase Problem" was why I was trying to call.
GetHuman-290196'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.
GetHuman-290196: He understood my prolem and explained to me how it happened and how to prevent it from happening in the future, but was unable to fix the problem that I already created for myself.
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?
GetHuman-290196: I'd give them a one 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?
GetHuman-290196: I'd give them a one out of five on communication.
GetHuman: And what about Ticketmaster's ability to quickly and effectively address your problem?
GetHuman-290196: For that I would say one out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
GetHuman-290196: 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 GetHuman-290196 taken from his Ticketmaster customer service problem that occurred on November 6th, 2017.