A soft play centre can automate party bookings for about $20 to $170 a month at list prices: a booking tool with deposits and forms from roughly $20 to $69, plus an optional enquiry chatbot from $0 to about $100. Automate availability checks, deposits, reminders and consent forms; keep menu changes, complaints and allergy questions with a person.
The saving shows up in staff hours, not in the software invoice. A party enquiry takes several messages to settle, and most of those messages are the same ones. A centre answering 90 enquiries a month by hand can spend more on staff time than on any software below, while food needs and children's photos stay decisions for a person.
What a party enquiry costs you today
Start with your current cost, because it sets the ceiling on what automation is worth. Count a typical month of party enquiries and time one of them from first message to deposit.
Say a centre gets 90 party enquiries a month and 40 become bookings. Each enquiry involves about five messages over a few days: "what dates are free", "what is included", "how many children", "how do I pay", and a reminder to return the form. If each enquiry costs 15 minutes of staff time, that is 22.5 hours a month. At an illustrative $15 an hour, the hidden cost is about $337 a month, plus the parties lost to slow replies. Replace those numbers with your own; the shape of the sum is what matters.
The jobs, in the order they are worth automating
- Availability and slot holds: showing free party-room times, so nobody emails "is the 14th free?".
- Deposit at booking: money in before the slot is held.
- Package questions: what is included, how many children, extra guests, food options.
- Confirmation and reminders: a clear message now, a reminder a week before, and one the day before.
- Form chasing: guardian consent, guest numbers, dietary needs.
- After the party: a thank-you and a review request.
Jobs 1, 2, 4 and 5 are mostly the booking tool. Job 3 is where a chatbot or an AI-drafted reply earns its place. Job 6 is cheap and often forgotten.
Three set-ups priced per month
These use public list prices checked in October 2026 for tools a small centre might actually consider. They are examples, and you should price your own shortlist the same way.
| Set-up | What you pay for | Monthly (list) | What it does |
|---|---|---|---|
| Lean | Acuity Scheduling Starter ($20), free chatbot tier ($0) | $20 | Online party slots, deposits, intake forms, email reminders; a free chatbot tier such as Botpress (100 conversations a month) |
| Middle | Acuity Standard ($34) plus an entry chatbot such as Hyperleap Plus ($40) | $74 | Adds text reminders and packages; a bot answering up to 3,000 replies, sharing a booking link |
| Fuller | Acuity Premium ($69) plus Hyperleap Pro ($100) | $169 | Adds Acuity's AI Booking Assistant; Hyperleap's in-chat booking works with Calendly or Cal.com |
Some details behind those figures. Acuity lists Starter at $20, Standard at $34 and Premium at $69 monthly, with a lower price on annual billing; deposits and intake forms appear on all three, packages from Standard, text reminders from Standard, and the AI Booking Assistant, which Acuity describes only as an "AI chat bot for clients", on Premium. Ask for a demo of what it answers before paying the extra $35. Hyperleap lists Plus at $40 a month for 3,000 AI replies, where Plus shares a booking link; Pro at $100 books inside the chat, but through Calendly or Cal.com, so on Acuity you would stay with the link. The fuller row pays for two chatbots, so test Acuity's own assistant first: if it answers your package questions well, drop Hyperleap and the fuller set-up costs $69.
Other chatbot routes exist. Tidio lists a free plan with 50 AI conversations over its lifetime, and its standalone Lyro agent from $32.50 a month for 50 conversations. Botpress lists a free plan of 100 conversations a month. Intercom's Fin charges $0.99 for each resolved outcome, which suits a centre with few but valuable conversations. Free tiers vary and change, so confirm on the vendor's page before building anything on them.
Worked sum: which set-up pays back
Using the 22.5 hours of enquiry time above, suppose the middle set-up cuts it by half: 11 hours saved. At $15 an hour that is $165, against $74 of software, a net gain of $91 a month before counting extra parties won by quick replies. The lean set-up at $20 with, say, a third of the time saved (7.5 hours, $112) nets $92 but leaves chatbot-type questions to staff. The fuller set-up at $169 only breaks even if it saves 11 hours or books extra parties. One more booked party at a $200 package, with a 25% deposit, pays for most of the difference. If you cannot name where the extra bookings come from, stay in the middle.
A note on playground-design tools
Search results for soft play and AI are full of design and costing tools. GetSoftPlay, for example, offers free planning tools for people investing in an indoor play centre: an AI concept visual, a cost calculator and quote requests. Its page puts equipment and installation at a rule-of-thumb $180 to $500 per square metre, a build job that is a different question from this one. The party-booking costs here are monthly operating costs for a centre that already exists.
What to automate first: availability and deposits
Most of the value comes from two settings. First, publish only the party slots you are happy to sell: say Saturday and Sunday at 11 am, 1.30 pm and 4 pm. Give each a capacity of one party, and a buffer for the clean-up. Second, take a deposit at booking. A common pattern is a flat $50 or 25% of the package, non-refundable inside 14 days of the party. The figure is yours to set; what matters is that it is on the booking page and repeated in the confirmation.
Example: before and after for a typical enquiry
Before: a parent messages "Do you have a Saturday in March for 15 kids?". Staff reply the next day with three dates. The parent replies two days later, picks one, and asks about food. Two more messages follow before a deposit request, and the slot has sold to someone else in the meantime. After: the parent opens the booking page, sees the free Saturday slots, picks one, pays the deposit, and answers the form questions. Staff see the booking in the morning. The enquiry that took five messages and six days takes ten minutes.
Where an AI chatbot or drafted reply fits
Parents have questions the booking page will not answer. A chatbot, or a set of saved replies drafted with a chat assistant, handles them: how long is the party, can we bring a cake, is there a minimum number, what about adults, are siblings welcome, where do we park. Write the answers once, in plain language, and give them to the chatbot as its source.
A filled-in extract of the sheet:
Party length: 2 hours (90 minutes in the party room, 30 minutes extra play).
Numbers: minimum 10 children, maximum 25. Extra children $9 each.
Food: hot food package from $8 a child; you may bring your own cake.
Allergies: do NOT answer. Say a team member will confirm and take a message.
Adults: up to 2 free per 10 children; extra adults $4.
Deposit: $50 at booking; balance on the day; cancellations within 14 days lose the deposit.
Photos: ask us about photo rules. Never promise any photos or permissions.Give the same text to staff as a cheat sheet. If the chatbot and the team say different things, the chatbot gets blamed, even when the sheet is wrong.
Example: a sample draft and what to fix
Prompt to a chat assistant: "Write a reply to a parent asking whether they can bring their own cake and a nut-free birthday cake for a child with an allergy. Use the sheet above. Do not say any food is safe." A typical draft reads: "Yes, you are welcome to bring your own cake. For allergies, please share the details with us on the form and a team member will confirm what we can do." What you would fix: the draft is fine on cake, but add "we cannot guarantee any food is free of traces of allergens" if that is your policy, and check that the reply does not describe your kitchen. Save the corrected version as a template and reuse it.
For more on what to automate and what to leave with people, see the party-rental booking software tutorial, which covers quote and availability tools in a similar business.
Consent forms and photo permissions
Parties for children raise the stakes on forms. Aim to collect these at booking, in the booking tool's intake form, rather than by chasing parents on the day:
- Guardian name and phone number: a number you can reach on the day.
- Child's name and age: only what you need.
- Dietary and access needs: a free-text box that routes to staff, not to the chatbot.
- Acceptance of the centre's rules and terms: a tick box, with the wording checked by whoever advises you on liability.
- Photo permission: a separate tick box with a clear yes or no, not bundled with the terms.
Keep photo permission separate on purpose. A parent may be happy for you to take photos for the family and unhappy about the centre's social media. If you plan to use any child's image in marketing, or feed one into an AI tool, you need that tick first. The preschool social media tutorial has wording parents tend to accept. Rules on children's images and data differ and change, so ask a qualified adviser what applies to you.
The same logic applies to what you hand a chatbot. Do not paste forms with children's names, allergies or health details into a public chat assistant to "summarise" them. Keep the data in the booking tool, and give the assistant only the general sheet. If you do use an AI tool on guest data, use a business plan, check its data settings and keep the amount of personal detail small.
Reminders that actually reduce empty rooms
A party slot is a fixed asset with a short shelf life. A good reminder sequence costs almost nothing and protects it. A pattern worth copying:
- Right after booking: confirmation with the date, time, deposit received and cancellation rule.
- Two weeks before: a nudge to confirm final numbers and return the form, with a link.
- Three days before: numbers locked, food choices due, what to bring.
- The day before: arrival time, parking, who to ask for.
- The day after: a thank-you and a review request, sent to the parent.
Text reminders are only on Acuity's Standard plan and above (Starter lists email), which is a point for the middle set-up. For more on reminder timing and wording, the no-show reminder tutorial goes into detail.
Example: a reminder written with AI, and what you edit
Prompt: "Write a short text to a parent, three days before a children's party, asking them to confirm numbers and food choices by Thursday. Warm, plain, under 50 words." A draft might read: "Hi [first name], your party is in three days. Please confirm the number of children and food choices by Thursday using the link below. Any questions, just reply here. We cannot wait!" What you would fix: "We cannot wait!" reads oddly, and a person has to confirm the deadline matches your kitchen's cut-off. Replace the placeholder with the real link and keep the message under one text.
Changes, cancellations and the double-booking trap
Parties change: the guest list grows, the date moves, a child falls ill. Decide the rules before automation, because software will apply them to everyone without a moment's thought. A workable set:
- Number changes: up to 7 days before, free to change; inside 7 days, charged at the booked number or the final number, whichever is higher.
- Date changes: one free move up to 14 days before, subject to availability; a second move costs a fee, or forfeits the deposit.
- Cancellation: deposit kept inside 14 days. Allow a human to waive it for illness, because goodwill here is cheap.
Put the rules into the confirmation message and the chatbot sheet in the same words. A parent who reads "free to change up to 7 days before" on the booking page and "10 days" in a chat reply has found a loophole you wrote yourself.
Example: a double booking, and how it happened
A centre takes party bookings through its website tool and also still takes them by phone and Instagram, writing those in a paper diary. On a busy Saturday the tool shows 1.30 pm as free while the diary has a party in that slot from a phone call weeks earlier. Two families arrive. The cause is two sources of truth. The prevention is simple: every booking, from any route, goes into the one system within the hour, and the diary is retired. If staff must take phone bookings, they enter them directly and use the same deposit link.
Who does what on the day
Automation reduces admin but does not run a party. A short split of duties helps:
- The system: sends confirmations and reminders, holds slots, collects deposits and forms, and flags unreturned forms three days out.
- The party host: checks the booking list on arrival, confirms final numbers, and handles food and any allergy notes in person.
- The manager: reads the weekly summary, answers escalated messages and decides on goodwill refunds.
Print the day's list each morning with the guardian's phone number, number of children, and any flagged needs. If the printed list and the system disagree, the system is probably wrong and should be corrected that day. Free-text notes are the field most likely to carry a safety detail, such as a child's allergy, so train hosts to read them aloud at the briefing.
Finally, keep a short log of questions the chatbot could not answer in its first month. Each one is either a missing line on the sheet or a question that should always go to a person. Add the first kind to the sheet. Mark the second kind on the sheet as a rule, so the chatbot passes it on rather than guessing, and keep the list of the second kind short and clear.
Limits and costs to check before paying
- Counting rules: chatbot plans count conversations, replies or resolutions differently. A half-hour of chatting may be one conversation or twenty replies.
- Payment fees: deposits go through a payment provider that takes its own fee. Check it, since it is not in the software price.
- Annual versus monthly: several pages show a lower price for annual billing. Quote the monthly price when planning, because you may leave.
- Integrations: a chatbot that cannot see your booking calendar can only share a link. In-chat booking needs a connection, and that may sit on a higher plan.
- Staff training: an hour for each person who answers messages is cheap; no training is costly.
Checking it worked after two months
Measure four numbers before and after: enquiries per month, enquiries that became deposits, median time to first reply, and staff hours spent on party messages. Say enquiry-to-deposit moves from 44% to 52% and staff time falls from 22 to 12 hours. That is a clear result. If conversions stay flat and time falls, the system is working as a saving, not as a sales tool, which is fine too. If time does not fall, read the chatbot transcripts for the questions it could not answer and add them to the sheet.
When you are ready to widen the system, the website chatbot cost and payback tutorial helps judge a larger set-up. Until then, start with the lean one, count the hours for a month, and spend more only when the numbers ask you to.
Questions soft play owners ask about party automation
Can a chatbot answer food allergy questions for a party?
It should not. Allergy and medical questions need a person who can check ingredients and the child's actual needs. Set the chatbot to say it will pass the question to a team member, take a message, and never to suggest that any food is safe.
Do I need a parent's consent for photos taken at a party?
Collect it separately from the booking terms, with a clear tick box for whether photos of the child may be used on social media or marketing. Rules on children's images vary, so check what applies to you. Never use a child's photo in an AI tool without that permission.
Is a free chatbot enough for a small centre?
Often it is for a trial. Free tiers cap conversations, so a centre with 60 or more enquiries a month may outgrow one. Test with a busy weekend's worth of real questions first, and compare the upgrade price before you build anything on it.
Should deposits be taken automatically?
Yes, if your booking tool supports it, because a held slot with no deposit is the most common cause of empty party rooms. Set a clear amount, say 25% or a flat figure, and state the cancellation rule in the confirmation message.
Further reads
- Mini Golf Business Software: Party Bookings and Season Passes — Party bookings and season passes in another family venue.
- Venue Booking Software: Calendar, Deposits and AI Replies Compared — Calendar and deposit rules compared across venue software.
- Dive Shop Software: Courses, Gear Hire and Waivers Handled With AI — How another business handles waivers at booking.
- Tattoo Studio Software: Booking, Deposits and Consent Forms Compared — Consent forms collected at booking, compared across tools.
- Bowling Alley Marketing: Eight League and Party Offers Written With AI — Party offers from a neighbouring leisure business.
- Ice Rink Software: Session Booking, Lessons and Party Enquiries — Set capacity from ice and hire stock, run lesson blocks with waitlists, take party enquiries to a deposit, and see where AI helps and where it must not.
- Party Rental Contract: Damage, Weather and Deposit Terms With AI — Draft deposit, damage and weather clauses for party rental from a decision sheet, test them against awkward scenarios, then brief your solicitor.
- Trampoline Parks and AI: Party Booking Follow-Ups and Waiver Reminders — A message timeline from party enquiry to arrival day, with sample texts, a stop rule for quiet quotes and a way to get waivers signed in advance.
- AI Entertainment for Events: What Party Hire Firms Can Add to a Package — Five AI add-ons a party hire firm can sell, a costed caricature station for 150 guests, and the venue and consent points to settle before listing any.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Acuity Scheduling pricing page, Tidio pricing page, Hyperleap pricing page, GetSoftPlay site, and the Botpress and Intercom Fin pages (checked September and October 2026). Party volumes, wages and deposit amounts are illustrative assumptions.