Fans ask Muse, ChatGPT, Claude, Perplexity, Meta AI and Google about your event. Runner makes sure the answer is yours: the right set times, the right gates, your sponsors by name.
Move a set time, close a gate, swap a stage. Approve it once and fan threads, your event page and the assistants that read Runner all carry the new answer — minutes, not a news cycle.
A public page can be read into a draft — but only a reviewed fact becomes an answer.
Assistants answer about your event whether you've told them anything or not — often with last year's set times and none of your sponsors. Runner gives them the version you'd sign off on, and keeps the receipt every time it's used.
Illustrative numbers. In a real report every one is a logged event — a reply that was sent, a response an assistant fetched, a page a crawler read. Nothing is estimated.
Send set times, stages, gates, policies and sponsored places from your own app or CMS — or edit them in Runner. No rebuild, no new app: one change reaches attendees' threads, your public event page and the assistants that read Runner.
Messaging is yours to choose: Runner's line, your own number, or just the data connection. API docs
Your app reaches the fans who download it; assistants reach everyone else. Want your own line too? Attendees text Runner and get the same approved answer — sponsors named, purchases in the thread.
The answer layer comes first. When you want it to, the same verified thread carries sponsored places, add-ons, and upgrades — never interrupting, always in context.
The stage or lounge a sponsor bought is named their way in every answer — and every time it goes out is logged, by place and by assistant.
A question about a size, product, or extra becomes a purchase and clear pickup instructions — inside the thread.
Relevant, available offers that follow the conversation — an afterparty, a bundle, or the next date, with timing made clear.
The attendee's current ticket and available inventory in view — so the offer fits, and the price difference is clear.
Parking and rides are supported too. Brands and values shown are illustrative.
Announce the lineup, share an on-sale, or update a gate — with audiences and timing controlled by your team.
On-site targeting is shown only where a real check-in or shared-location signal exists — plain texting doesn't provide live location. Sample audience and copy.
Load the lineup, stages, gates and sponsored places once — from your app, a file or your team. Your event page goes live for assistants to read.
Fans and assistants get the same current answers. On-sales, upgrades and add-ons ride the same thread.
Live changes reach every answer in minutes. Sponsors credited, purchases in-thread, your team watching.
The receipts: sales, settlement, and every sponsor impression by place, surface and assistant.
Orders, questions, sponsor impressions and settlement — in views built around the decisions your team actually makes.
Festivals, arenas, clubs, conferences — anywhere fans ask questions before they arrive, and AI answers them.
Multi-stage, multi-day, 10k–100k.
Concerts, games, tours.
Shows, comedy, nightlife.
Sessions, room maps.
Runner reads what your team already knows — through the connection each source actually supports.
A name here reflects how Runner reads or connects to each source — not a partnership or endorsement. Assistants named on this page are where fans ask, not partners.
Paste your event or ticket link. We'll show you what assistants say about it today — and build a preview of what they'd say with Runner.