What do ticket buyers and event organizers contact support about?
Ticket buyers contact you about getting in: where their tickets are, how to send one to a friend, what happens now the date has moved, and why a barcode failed at the gate. Organizers and promoters, your second audience, ask about payouts and event settings. Fees bring their own questions: in a 2018 GAO review of event ticket sales, total fees averaged 27% of the ticket price on the primary sites it sampled and 31% on resale sites.
| Conversation type | Can Agent resolve it? | Hand off when | Data Agent needs |
|---|---|---|---|
| “Where are my tickets?” | Yes: gives the release time for delayed delivery, resends access to the order email, explains phone wallets | The order is on a payment or fraud hold, or the buyer wants the account email changed | Order, delivery status, release time |
| Transfer to a friend, or a transfer that never arrived | Yes, within the event's transfer rules | Name-on-ticket events needing an ID change, or the sender says they never sent it | Transfer log, transfer settings |
| Event canceled: refund | Yes: refunds what the organizer's policy allows to the original payment method | Expired cards or orders mixed with packages; ticket protection claims go to the provider | Event status, order, payment, refund policy |
| Event postponed or moved to a new venue | Yes: confirms the new date or venue, that tickets stay valid, and any refund window | Requests after the window closes, or accessible seats to reassign | New date and venue, refund window, seat map |
| “I can't go anymore” | Explains the policy and the official resale or exchange option | Bereavement, illness or other exceptions the organizer may grant | Refund policy, resale rules |
| Ticket won't scan, or came from another seller | Checks the barcode: voided after transfer, already scanned, or never issued by you | The buyer is at the gate now, or a duplicate scan suggests a copied ticket | Scan log, ticket status |
| Fee and charge questions | Yes: itemizes ticket price, service fees, delivery and taxes | The buyer disputes the charge or mentions a chargeback | Order fee breakdown |
| Accessible seating | Shares accessible options and how to buy them on the same terms as other tickets | Specific seating needs, companion seats or exchanges | Accessible inventory |
| Presale codes, queues and purchase limits | Yes: explains presale windows, checks codes, states the limit | Many buyers report the same error at once | Presale lists, code status, limits |
| Organizer payouts and event settings | Yes, for payout schedules, status and how-to questions | Payout holds, disputed settlements or contract terms | Organizer account, payout ledger |
Example scope. Refund rules belong to each event's organizer, so set Agent's limits to match them.
Under the Justice Department's ADA guidance on ticket sales, accessible seats sell through the same channels as other seats, without proof of disability. Agent explains this and passes specific requests to your accessibility team.
What does an AI procedure for missing tickets look like?
Start with ticket delivery. It follows every order and peaks in the days before doors, when delayed tickets release. Agent turns each line of this brief into steps tied to your ticketing system.
Example procedure: “where are my tickets?”
- Verify the buyer. Match the email or phone number to an order. If they write from another address, verify them through your ticketing system first (for example a one-time code sent to the order email via your API). Never change the account email in chat.
- Answer from the delivery state. Not yet released: give the organizer's release time (Example: 72 hours before doors). Released: resend access to the order email and explain adding tickets to Apple Wallet or Google Wallet. Transferred out: say when, and to which masked address. On hold: say a person is checking the order, without explaining the review criteria.
- Limit resends to two per order in 24 hours (Example), always to the order email.
- Watch the clock. If doors open within three hours (Example) and the buyer still has no access, give the box office location and tag the conversation for your event-day queue.
- Escalate on signs of account takeover (an email or password change followed by a transfer out), a held order for an event in the next 48 hours, the words “chargeback”, “scam” or “stolen”, or a second failed fix.
Example conversation (in-app chat; buyer, order and show invented)
Buyer: I bought two tickets for Harbor Lights on Saturday and there's nothing in my app.
Agent: Hi Dana, I can see order 48213 for two general admission tickets. The organizer releases tickets 72 hours before doors, so they'll appear in your app on Wednesday at 7 pm, with an email when they do.
Buyer: OK. Can I send one to my brother?
Agent: Yes, once they appear: open the order, choose Transfer and enter his email. If it hasn't reached him by Thursday, reply here and I'll check the transfer log.
Agent answered from the order and the event's delivery setting, and didn't attempt a transfer on tickets that hadn't been issued.
What guardrails does an AI agent need in event ticketing?
A ticketing agent moves money and decides who gets through the gate, so it stays inside the organizer's policy and never vouches for a ticket it can't see in your system.
What Agent must never do
- Say that a ticket from another seller or a stranger on social media will work. It only reports whether that barcode exists in your system and its state.
- Refund outside the organizer's policy or above its cap (Example: $500 per order without approval).
- Help anyone get around purchase limits or the queue, such as by suggesting extra accounts. The BOTS Act bars circumventing a ticket issuer's online access controls and selling tickets obtained that way.
- Quote a price without mandatory fees. The FTC rule on unfair or deceptive fees, now in effect, requires US live-event ticket sellers to show the total price, mandatory fees included, whenever they show a price.
- Promise EU buyers 14 days to cancel. EU consumer rules exclude concert tickets and other bookings for specific dates from the cooling-off period, so the organizer's policy applies.
- Ask for proof of disability, a full card number or a security code, or give legal advice about chargebacks or consumer rights. Legal questions go to a person.
What triggers a handoff
Scam reports, account takeover signs, dispute language, safety incidents at an event, accessibility requests, VIP and hospitality buyers, and held orders for events in the next 48 hours. Your team gets the order, the scan or transfer log and what Agent already tried.
Data handling
Each step maps to a connector with explicit, revocable permissions, so Agent can read orders and scan history without refund rights until you grant them. Treat accessibility needs and ID details for name-on-ticket events as sensitive. Aftersales is US-hosted and offers a GDPR data processing agreement (see security); your own compliance and consumer and resale law in each market stay with your legal team.
Which channels matter most for ticketing support?
Email and in-app chat carry most ticket questions, social DMs bring fans and scam victims, and SMS and phone matter most on event day.
- Email: buyers reply to confirmations, delivery notices and refund receipts, so the order arrives with the question.
- Web and in-app chat on event pages and inside the ticket wallet, for delivery, transfers, bag policy and door times.
- Social DMs to venue, festival and promoter accounts. Many scams start on social media: UK Home Office figures show about 3,700 gig ticket fraud reports to Action Fraud in 2024, almost half about offers on social media, and more than £1.6 million lost. Agent routes “I bought from someone online” to your fraud queue.
- SMS for event-day notices such as weather delays and gate changes, and buyers' replies. Presale alerts are marketing and need consent, so keep them in your marketing tool.
- WhatsApp for touring shows and international festival-goers, with Agent replying in 31 languages.
- Phone: on Growth and Scale, calls join the same Inbox with warm and cold transfers and per-brand numbers, so a festival hotline can pass a caller to a venue box office.
What systems should a ticketing AI agent connect to?
Connect your ticketing platform first, because it holds the orders, barcodes, delivery settings and transfers Agent reads. Aftersales links to ticketing, scanning and payout systems through its API or webhooks; confirm specific connectors on a call.
- Ticketing platform or box office system: orders, ticket status, release times, transfers, presale lists and limits.
- Access control and scanning: scan history by barcode and gate, so Agent can tell “already scanned” from “voided after transfer”.
- Payments: Stripe refunds if your checkout runs on Stripe, with per-order caps; other processors through the API.
- Fraud screening: order holds sent by webhook, so Agent knows when to stop and hand off.
- Organizer payouts: settlement schedules and status, read-only for Agent.
- Group sales and hospitality: Salesforce, if your sales team works suite and package leads there.
- Knowledge: door times, bag policy, age limits, re-entry, accessibility and refund policy for every event in one Knowledge source.
How much does AI customer service cost for a ticketing team?
For the promoter below, the bill is $2,058 in a typical month and $6,513 in festival month on annual billing. Seats stay flat, the cost follows resolutions, and handed-off conversations cost nothing extra.
Assumptions (Example):
- A promoter selling tickets for three venues and a summer festival through its own ticketing site.
- Four support agents on Growth seats; three box office managers, a finance lead and two event managers on free Lite seats (Growth includes 20).
- Typical month: 3,000 written conversations, with Agent resolving 60% (1,800).
- Festival month: 9,000 conversations, mostly delivery, door-time and transfer questions, with Agent resolving 70% (6,300). Both rates sit below the Aftersales median of 71% after 90 days because fraud, disputes and accessibility always go to people.
| Item | Typical month | Festival month |
|---|---|---|
| Growth seats (4 × $69) | $276.00 | $276.00 |
| Agent resolutions at $0.99 | 1,800 = $1,782.00 | 6,300 = $6,237.00 |
| Lite seats for 6 managers | $0.00 | $0.00 |
| Conversations Agent hands off | $0.00 | $0.00 |
| Total | $2,058.00 | $6,513.00 |
List prices checked October 2026. Monthly billing raises seat prices by 20%. Written conversations only; phone and the Copilot add-on ($29 per rep per month, annual) are not included.
Smaller venues can start free; see pricing.
How do you roll out an AI agent for ticketing in 30 days?
Launch between big on-sales and test the cancellation procedure before you need it.
- Days 1 to 7: connect ticketing, scans and payments, load event policies into Knowledge, and have finance and legal approve refund caps and cancellation wording.
- Days 8 to 14: replay past conversations in a test with personal details removed, then go live on web chat for delivery, door-time and fee questions on two or three smaller events.
- Days 15 to 21: add transfers, postponements and email, switch on Monitors (Growth and up) to score every conversation, and run the cancellation procedure against a test event.
- Days 22 to 30: extend to every event, social DMs and WhatsApp, review resolution rate, handoff reasons and cost per conversation by event in Insights.
Count only conversations that were truly resolved (the resolution rate guide explains how), and set up the people side with helpdesk software for event ticketing.