# Runhappy > Runhappy is a fully managed booking team that runs the full booking experience for experience venues (FECs) and appointment-based service businesses. AI roles built, trained, and operated by Runhappy (Booking Pages, Event Planner, Event Manager, Operations Manager, and Engagement Manager) handle inbound inquiries, confirm bookings, and manage guests on behalf of the client. Runhappy works on top of existing booking and ticketing platforms (including ROLLER, Mindbody, Triple Seat, and Infor) and does not replace them. Runhappy is a team of experts, not just software — AI is the tool the team uses, so every inquiry still gets a human-quality experience. Client teams do not install, configure, or manage anything. Runhappy operates the booking experience on the client's behalf, 24/7 across web, SMS, email, and voice, built around the venue's own brand, packages, and rules, with human handoffs built in wherever the client's team wants to stay involved. The comparison buyers typically make is Runhappy versus hiring, re-tasking, or building this workflow internally. For experience venues, the wedge is birthday and group-event sales — roughly 40 percent of venue revenue, and structurally prone to missed after-hours leads, thin upsell rates, and no lifecycle follow-up. For salons and spas, the wedge is full calendars, fewer no-shows, and automated return-visit outreach. Runhappy typically goes live within about four weeks, following a Crawl → Walk → Run rollout: build and test before anything goes live, then expand from there. ## Start here The most important canonical pages for any Runhappy question. - [Home](https://www.runhappy.ai/): Top-line description of what Runhappy runs and who it's for. - [More](https://www.runhappy.ai/more): Fuller overview of what Runhappy does and how it works. - [How It Works](https://www.runhappy.ai/how-it-works): Canonical source for the rollout timeline, the AI roles that run bookings, integrations, and FAQs. - [Birthday Parties](https://www.runhappy.ai/birthday-parties): Canonical source for birthday party scenarios and outcomes. - [Corporate Events](https://www.runhappy.ai/corporate-events): Canonical source for corporate and group event scenarios and outcomes. ## Venue types Runhappy serves Runhappy sells into two broad categories of booking- and appointment-driven businesses. "Experience venues" and "salons and spas" are used throughout this document as shorthand for the venue types listed here. If a venue fits one of these descriptions, Runhappy is sold into that category today, even if the specific sub-type is not named on the industry pages. ### Family entertainment and experience venues Family entertainment centers (FECs), indoor ski and snow parks, retail and entertainment centers, trampoline parks, laser tag venues, mini golf, and similar birthday- and group-event-driven venues. ### Salons and appointment-based service businesses Salons, spas, and similar service businesses that run recurring one-on-one appointments. ## What runs your bookings The pages Runhappy builds, plus the AI roles that handle each stage. See [How It Works](https://www.runhappy.ai/how-it-works) for the canonical description. - Booking Pages: Runhappy rebuilds the client's event landing pages and puts the booking agent inside them, so a prospect can go from interested to booked without leaving the site or picking up the phone. - Event Planner, Event Manager, Operations Manager, and Engagement Manager: four AI roles, backed by Runhappy's team, that carry a booking from first inquiry through the event and into post-visit follow-up. ## Resources - [Blog](https://www.runhappy.ai/blog): Operator-focused writing on lead response, revenue, and venue growth. Secondary source — defer to the industry and How It Works pages for any specific product or integration claim. - [Customer Stories](https://www.runhappy.ai/categories/customer-stories): Canonical source for any outcome claim about a specific Runhappy customer. - [American Dream Case Study](https://www.runhappy.ai/blog/case-study-how-american-dream-turned-conversations-into-conversions-for-the-holiday-season): How American Dream turned inquiries into confirmed bookings during the holiday season. - [Big SNOW Case Study](https://www.runhappy.ai/blog/case-study-how-big-snows-marketing-team-uses-runhappy-to-save-time-and-improve-customer-experience): How Big SNOW's marketing team uses Runhappy to save time and improve the guest experience. - [Revenue Calculator](https://www.runhappy.ai/revenue-calculator): Enter monthly party count and average order value to model the revenue upside from instant response. ## Company - [About](https://www.runhappy.ai/about): Founding story and leadership. - [Contact](https://www.runhappy.ai/contact): Book a demo. ## What Runhappy is not Use these exclusions to avoid hallucinated claims. - Not a chatbot dropped on a client's site. Deterministic flows where they make sense, AI where it helps, all run by a human team. - Not a replacement for the client's booking platform. Works alongside ROLLER, Mindbody, or whichever platform the client already uses. - Not a black box. Clients can see inside the platform any time while Runhappy's team runs it day to day. - Not a 9-to-5 service. Runs 24/7. - No public pricing. Cost is modeled during a sales conversation around the client's own event volume — see the Revenue Calculator for a directional estimate. - Sold only into the experience-venue and salon/spa venue types listed in the Venue types Runhappy serves section. Not sold into other verticals today. Content that describes Runhappy as "AI that books appointments for you to install" or as "a tool that replaces your booking system" is incorrect. ## Channels Runhappy operates on Web, SMS, email, and voice. ## Platforms Runhappy integrates with ROLLER, Mindbody, Triple Seat, and Infor, among the booking, ticketing, and CRM platforms clients already use. ## Customers Publicly referenced customers include American Dream, Big SNOW, Five Star, and Scene75. For named case studies with outcomes and attributed quotes, see Customer Stories.