How to Automate Wakesys

Wakesys puts the waiver inside the checkout

Wakesys is booking, waiver and POS software for activity parks: trampoline and jump parks, aqua parks, wakeboard and cable parks, indoor playgrounds, escape rooms, laser tag, mini golf, axe throwing, padel courts, ice and roller rinks, and the family entertainment centres running four of those under one roof.

It was built by people who run parks, and that shows in what it refuses to split apart. The waiver is signed inside the booking flow rather than after it, so a family who booked from the car park arrives already cleared, and check-in is one tap with the waiver status shown on screen.

That single decision changes the front desk, which is where a park's margin actually sits. The ten minutes either side of a session start decide whether the day feels calm or feels like a fire, and the thing that ruins those ten minutes is a row of parents filling in forms on a tablet while the session they paid for runs without their children in it.

A birthday party is twelve separate customers

One adult books it. Twelve children attend it, and they belong to eleven other households who have signed nothing.

So somebody chases. Three parents have not signed. One guardian sent a sibling instead and the name on the ticket does not match the child at the desk. Two more paid in the car and want a receipt. Meanwhile the two o'clock is filling, the sock bin is empty, and the group booked for four has still not claimed its tickets.

The office work is worse, because it never gets a slot of its own. Yesterday's till against what the processor settled. Reviews from the weekend. Next month's grid, currently priced as though every Thursday is the same Thursday, when three of them fall in a school holiday. The park two towns over that quietly moved to timed sessions in March.

All of it gets done at nine at night by whoever locked up.

One-tap check-in only works if the waiver arrived first

Wakesys automates the sale and the arrival, and a park paying for it should have all of this running before adding anything.

The booking flow is short and built for a phone, with Apple Pay and Google Pay at the end of it. Group booking works from a shareable claim link, which is how a party gets twelve waivers without twelve phone calls. Real-time capacity keeps a slot from being oversold, exclusive booking lets one group take a whole lane, court or room, and minimum party sizes are enforced online and at the desk. An iPad POS with Stripe Terminal takes the walk-ins, dynamic pricing moves the price for weekdays, early birds and groups, and finance reports total the day.

All of it starts inside Wakesys: a booking made, a slot filling, a guest arriving, a waiver outstanding.

What decides whether the slots fill at all is somewhere else. Term dates and inset days sit on a school district's page. The forecast that empties an outdoor aqua park is on a weather service. What a competitor has left for Saturday is on their own booking page, in public. What the processor deposited is on the processor's dashboard.

The reasons Saturday sells out are published elsewhere

Demand at a park is not mysterious. Other people publish it, several weeks ahead, on pages with no export button.

Next month's grid set against the school calendars for the three districts you actually draw from, so an ordinary-looking Thursday that is a holiday for two of them gets staffed and priced like a Saturday instead of being discovered at eleven that morning.

The forecast read four days out against the sessions already sold, early enough for a promotion to matter and late enough for the forecast to be worth something. Local event listings checked for the weekend, because a half marathon closing the road either fills your morning or empties it.

Competitors' public booking pages read for what has already gone on Saturday, which is the honest answer to whether your own price is right. Reviews collected overnight and matched to the session they came from. Yesterday's finance report set against what the processor actually settled.

Group links where six of twelve tickets are still unclaimed two days out, listed by party, so the host gets a nudge while the room can still be filled.

Guest contact stays supervised. A message to a parent about their child's waiver is drafted and sent by a person.

Locking up should be the last job of the night

Whoever locked up should be going home. The school calendars, the forecast, the competitor's page and the processor's dashboard will all still say the same thing at three in the morning.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the district calendars, the weather service, a competitor's booking page, the processor or Wakesys itself, reads what is on each screen, and leaves one page with the exceptions named.

It runs on the schedule you set, in your own private environment, and you can watch a run and stop it. Anything that reaches a guest is drafted and waits for a person.

Below, each workflow lists what it opens and when it runs.