Turning Data Requests Into Self-Service: Building an AI-Powered Analytics Product Users Love
Overview
| Experience | In Person |
|---|---|
| Track | Analytics & BI |
| Industry | Enterprise Technology, Communications, Media & Entertainment |
| Technologies | AI/BI, Genie |
| Skill Level | Intermediate |
| DOWNLOAD SESSION SLIDES | |
Ticketmaster's operations team was drowning in data requests. Every "how many fans showed up to buy tickets last week?" question cost engineering hours. We were spending over 8 weeks/year being human query engines. We needed to give users the power to answer their own questions.
We built OMT Wizard: a conversational analytics tool that lets non-technical users ask questions in plain English and get instant answers. Powered by Databricks Genie, it launched to 500+ users and achieved high stickiness. The users who try it keep coming back.
This session shares product lessons from building AI-powered internal tools — how we identified the right problem to solve, designed for trust and transparency, trained the AI on business logic, measured real adoption and turned skeptics into champions. You'll learn what worked — suggested questions, showing your work — what didn't — hiding complexity — and how to build AI products that solve real problems instead of looking for problems to solve.
Session Speakers
Brian Muehlenkamp
/Product Manager - Demand Intelligence
Ticketmaster
Full Summary
How Ticketmaster Built a Natural Language Analytics Wizard on Genie
High‑demand on‑sales at Ticketmaster compress critical decisions into minutes, and the most valuable questions rarely fit a prebuilt dashboard. The team addressed the constant drag of ad hoc data pulls by embedding a text‑to‑SQL assistant, the Wizard, directly into their on‑sale management tool and Slack.
FAQ
The stack stayed simple: Unity Catalog, Genie, Lambda, GraphQL, and React. Most effort went into curating business context in the Genie workspace, labeling columns, writing instructions, and validating queries. Engineers primarily connected the API and built a lightweight UI.
Operations teams already lived in the on‑sale tool while screen‑sharing with stakeholders, so placing the assistant next to the controls preserved flow. Slack extended reach to mobile and open channels, turning public threads into examples that helped other users discover what the Wizard could do.
Validated queries and clear instructions anchored consistent responses. A weekly improvement loop analyzed conversation logs, cloned the workspace, tested changes, and promoted fixes, often resolving reported issues within minutes and restoring confidence quickly.
No. The initial release focused on historical data because upstream ETLs ran hourly, every six hours, or overnight. That choice was acceptable since live KPIs already appeared in the surrounding tool. Real‑time coverage was added later.
Usage includes 83 unique users across 28 teams and more than 760 questions, about 10 percent of monthly actives. Many of those questions would have pulled engineers or data scientists off core work, so the tool reduced ad hoc requests and sped up decisions during live events.