Ticketmaster: I couldn't fond s ticket purchase I thought I h...
A Ticketmaster customer review by GetHuman user ~Zilenna 73 from November 26th, 2017
Background on ~Zilenna 73's case
GetHuman: ~Zilenna 73 - can you tell our other Ticketmaster customers when your case took place?
~Zilenna 73: Yes. It was middle of the night, on November 17th.
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 ~Zilenna 73 a list of common Ticketmaster problems)
~Zilenna 73: "Cancel order" was why I was trying to call.
~Zilenna 73'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.
~Zilenna 73: I couldn't fond s ticket purchase I thought I had made several months ago. The agent helped look through the system to find the tickets in a number of ways. Unfortunately I hadn't made the purchase (blond moment). But they tried!!
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?
~Zilenna 73: 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?
~Zilenna 73: 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?
~Zilenna 73: For that I would say one out of five.
GetHuman: And finally- any advice for other Ticketmaster customers?
~Zilenna 73: 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 ~Zilenna 73 taken from his Ticketmaster customer service problem that occurred on November 17th, 2017.