E-commerce

AI Support for Ticketing and Events: Transfers, Refunds, and Postponements

September 2026 · ISTRALLEN Team

The queue spikes at the worst time

AI support for ticketing has two predictable surges: the hour before doors, when access problems land all at once, and the moment an event is postponed or cancelled, when every ticket holder contacts you together. An agent that handles the steady middle but falls over at those two points has not solved the actual problem.

A request is classified as either an access or delivery issue or a refund or transfer question, and the two get very different treatment. Access and delivery problems — a mobile ticket that won't load, a wallet pass that won't add, a resend request — are grounded, time-critical actions the agent resolves directly from the ticketing system; when a remote fix fails close to doors, the dashed line shows the same request handed instead to on-site venue staff, who can do things the agent cannot from a chat window. Refund and transfer questions instead read the event's status as a single source of truth and apply whatever follows from it, rather than negotiating: an event that's happening as planned means the ticket is non-refundable but a transfer is still open — with the agent verifying ownership and blocking a double-transfer before logging the change, since two people holding a claim to one seat is exactly the failure mode this guards against; a postponed event means the ticket rolls to the new date and a refund window opens; a cancelled event means refund eligibility follows directly from that status. Decisions that sit above any single state — a goodwill refund outside policy, a fee dispute, or a date conflict on a postponed show — are never the agent's call; the second dashed line shows them handing off to the organiser with the order, the event status, and the conversation already attached.

Refund eligibility depends on event status

Whether a ticket is refundable is usually a factual question once you know the event state — happening, postponed, or cancelled. The agent reads that state and applies the rule, rather than negotiating. "This event is going ahead, so tickets are non-refundable, but transfers are open" is a clear answer; a vague maybe is not.

Transfers are an identity change on an asset

Transferring a ticket changes whose name is on a valuable, entry-controlling asset. The agent validates ownership, prevents a double-transfer, and logs the change, applying the constraint from our support agent project — a wrong tool call has a financial consequence — to a case where the failure mode is two people holding a claim to one seat.

Access and delivery issues

A mobile ticket not showing, a wallet pass that will not add, a resend request — these are grounded lookups and actions against the ticketing system, and they are time-critical near the event. The agent should resolve them fast and, close to doors, know when to route to on-site support instead.

Postponements are a mass event

When a date moves, tickets typically roll to the new date and a refund window opens. The agent explains the specific customer's options from their order, processes a refund if they are eligible and want one, and routes "the new date does not work for me" cases according to the organiser's policy rather than improvising.

Fees, face value, and what comes back

Refund disputes often come down to which components are returned — face value, service fees, delivery fees. The agent has to be exact about this per the policy, because a customer expecting the full amount and receiving face value only will escalate.

Fraud and abuse at the edge

Resale outside allowed channels, chargeback-then-attend, and duplicate-entry attempts are known patterns. The agent applies consistent rules and thresholds and flags anomalies for review, without accusing the customer or blocking entry on its own judgment.

Escalation with the order and event record

Organiser discretion, accessibility requirements, group-booking issues, and disputes hand off with the order, the event status, and the conversation attached.

A worked example

A customer messages an hour before doors because their mobile ticket will not load. The agent confirms the order, reissues the ticket to their account, and sends a fresh link, all from the ticketing system. A second customer asks for a refund on a show that is going ahead as planned. The agent explains that the event status makes the ticket non-refundable, offers the open transfer option instead, and processes the transfer once the customer names the recipient.

Where this stops being right

Organiser and promoter discretion — a goodwill refund on a non-refundable ticket — is not the agent's call; it captures the request and routes it.
Primary sales and resale marketplace transactions sit under different rules; the agent has to know which one a ticket came through before answering.
Consumer refund rights for cancelled events vary by jurisdiction and can override store policy — confirm with counsel; this is not a legal guide.

FAQ

What ticketing support works well with an AI agent? Transfers, resends and access issues, order and event-status questions, and refunds where eligibility follows from the event state and the ticket type.

How does the agent handle a postponed event? It explains that tickets roll to the new date, opens the refund option for eligible holders, processes refunds on request, and routes date-conflict cases to the organiser's policy.

Can the agent approve a goodwill refund outside policy? No — that is organiser discretion. The agent records the request with the order context and routes it to a person who can decide.

ISTRALLEN builds support agents for ticketing platforms that work from event status and hand organiser decisions to a person — see AI for E-commerce.

See it in production

AI for E-commerce → Support agent case study →

← All articles