Tickets for a major concert go on sale at 10am. By 10:02, 200,000 people are in the queue. By 10:15, the show is sold out. By 10:20, your support inbox has 3,000 new messages.

"Why was I charged twice?" "The page crashed and I don't know if my order went through." "I bought two tickets but only got confirmation for one." "The presale code didn't work." "I accidentally bought tickets for the wrong date."

Your support team of 8 people stares at the queue. They'll be digging out for the next week.

The Spike Pattern

Event ticketing has the most extreme support volume spikes of any industry. Normal daily volume might be 100 tickets. On-sale day hits 2,000 to 5,000. The day before a major event is another spike (parking questions, entry time, bag policy). The day after a cancelled or postponed event is the biggest spike of all (refund requests from thousands of ticket holders at once).

You can't staff for these spikes. Hiring 50 temporary agents for one day per month doesn't work. Training costs alone would eat your margin.

And unlike most industries, these spikes are predictable. You know exactly when they'll hit. You just can't do anything about them with human-only support.

The Top Questions

Event ticketing support is beautifully repetitive. Across all platforms, the same questions dominate:

"Can I get a refund?" is number one by a wide margin. 30 to 40% of all support contacts, depending on the event and refund policy. The answer depends on the policy, the event date, and sometimes the reason. But the classification is instant.

"I was charged but didn't get tickets." Double charges and failed transactions during high-traffic on-sales are the second biggest category. These are scary for customers (they see $200 gone from their account with nothing to show for it) and require backend verification.

"How do I transfer my tickets?" Transfer policies vary by event, venue, and ticket type. But for any given event, the answer is the same for everyone asking.

"What's the bag policy / parking / entry time / accessibility?" Event-day logistics questions. These are fully documented on the event page. People ask anyway because they want confirmation, or they're on their phone and don't want to scroll.

"The event was cancelled/postponed, what happens to my tickets?" This triggers a mass support event. Everyone contacts you at once with the same question.

About 70 to 80% of ticketing support can be resolved with standard responses.

AI for the Flood

When 3,000 messages hit your inbox in 20 minutes, AI doesn't flinch. Each message gets classified in under 200 milliseconds. Refund request, double charge inquiry, transfer question, logistics question, billing issue, complaint.

For the simple ones (logistics, transfer instructions, event details), AI responds immediately with the correct information. "The bag policy for Madison Square Garden allows bags under 12x12x6 inches. No backpacks. Full details here: [link]."

For refund requests, AI checks the refund policy for that specific event and responds accordingly. If refunds are available, it processes them or provides instructions. If not, it explains the policy and offers alternatives (credit, transfer).

For double charges and missing tickets, AI gathers the order information (email, last four digits of card, transaction time) and creates a priority support ticket with all details attached. A human agent picks it up with everything they need to resolve it in 2 minutes instead of 10.

The Post-Cancellation Tsunami

When a major event gets cancelled, thousands of ticket holders contact support within hours. They all want the same thing: their money back.

Without AI, this means a week of backlog. With AI, the response goes out instantly to every person: "We're sorry to announce [Event] has been cancelled. All ticket purchases will be automatically refunded to your original payment method within 5-10 business days. You don't need to do anything. If you don't see the refund after 10 business days, contact us and we'll investigate."

That one automated response, going out to 5,000 people in real time, saves approximately 400 hours of agent time ($6,000 to $8,000 in labor).

Accessibility and ADA Compliance

Accessibility questions deserve special attention. "Do you have wheelchair seating?" "Is there an ASL interpreter?" "Can I bring a medical device?" These aren't just logistics questions. They determine whether someone can attend the event at all.

AI should handle these with extra care. Classify them as high-priority, provide the specific accessibility information for the venue, and always include a direct contact for the venue's accessibility coordinator. If the AI isn't 100% sure about the answer, route to a human immediately. Getting an accessibility answer wrong is potentially discriminatory, not just bad support.

Integration with Ticketing Systems

The most useful AI integration for ticketing platforms connects to your order management system. When someone says "I was charged twice," AI can look up their order by email, check whether two charges actually went through or if one is a pending authorization that will drop off, and give a specific answer instead of a generic one.

Platforms like Eventbrite, Universe, and AXS have APIs that make this possible. Custom ticketing platforms usually have some kind of order lookup endpoint.

Even without deep integration, classification alone is valuable. Sorting 3,000 messages into categories (refund, double charge, transfer, logistics, complaint) takes an 8-person team hours to do manually. AI does it in seconds. The team then works through each category queue in priority order instead of first-in-first-out, which means the most urgent issues get resolved first.

The Numbers

A mid-size ticketing platform handles 5,000 to 10,000 support contacts per month, with extreme variance. At $0.20 per classification, that's $1,000 to $2,000/month. At $0.30 per resolution for auto-resolved queries, add another $1,000 to $2,000/month for the 50 to 60% that can be fully automated.

Total: $2,000 to $4,000/month for AI support.

Compare to a 6-person support team at $40,000 per person: $240,000/year, or $20,000/month. AI handles 60 to 70% of volume, effectively freeing 3 to 4 of those positions for complex cases, escalations, and VIP support.

The real win: on-sale day. When 3,000 messages hit in 20 minutes, AI handles them. Your team doesn't burn out. Your customers don't wait 72 hours for a response. Ticket buyers who had a bad experience get a fast resolution and don't charge back. Chargebacks at $25 to $50 each add up fast when you're processing thousands of transactions per event.