The problem
Before each party, an entertainer needs the birthday child's first name and how to say it, their age, the number of children, the venue and parking, any allergies (to sweets, latex balloons or face paint) and whether the parent agrees to photos. Collecting that by message and phone takes about 25 minutes a party; with 12 parties a month, that's 5 hours, and a detail lost in a chat thread can mean the wrong name at the big moment or a latex balloon near a child with an allergy.
What the AI does
Jotform is an online form builder with conditional logic, file uploads and e-signatures, and an option to store data on EU servers. Build one party details form and send it with every booking confirmation. Use conditional questions so an allergy answer opens a box for details, and ask photo consent as a separate yes or no. Answers come to you in one place before the party. Collect only what the party needs, and delete the details after it.
A worked example
A children's magician and party host in Leeds runs about 12 parties a month. They send a Jotform party details form with each booking, with allergy and photo consent questions, and read the answers the night before.
Before
About 25 minutes per party gathering details by message and phone: 12 × 25 = 300 minutes, 5 hours a month
After
About 5 minutes per party to send the form and read the answers: 60 minutes, 1 hour a month
What it's worth
About $133£100€119A$192C$188 a month saved, against about $39£29€35A$56C$55 to $45£34€40A$65C$64 for Jotform Bronze. That's 4 hours (300 minus 60 minutes) at an assumed $33£25€30A$48C$47 an hour. Bronze is €34 (about $39£29€35A$56C$55) a month billed annually or €39 (about $45£34€40A$65C$64) monthly, shown in euros on Jotform's EU site, for 25 forms and 1,000 submissions a month. The free plan isn't used here because the form collects children's health details.
How to set it up
- Choose a paid Jotform plan and the EU data storage option before you build the form.
- Build one form: child's first name and age, pronunciation, number of children, venue and parking, allergies with a details box, and photo consent as a separate yes or no.
- Add a short privacy notice to the form: what you collect, why, who sees it and when you delete it.
- Send the form link with every booking confirmation and ask for it back a week before the party.
- Read the answers the night before, check allergies with the parent on arrival, and delete the submission after the party.
What goes wrong
- Allergy details are health data about a child, which UK GDPR treats as special category data. Keep them out of free personal accounts, collect only what's needed and delete them after the party.
- A form answer is not a safety check. Confirm allergies with the parent on the day and keep allergens out of anything you hand out.
- Photo consent from one parent covers only their child. Other children at the party need their own parents' consent, so keep them out of photos you post.
- Don't ask for more than the party needs. Surnames, dates of birth and school names aren't needed for a magic show.