Pottery birthday parties: from enquiry to quote to deposit

A birthday party is the best kind of booking a pottery studio can take, and the worst kind to handle the way you handle everything else. It is bigger, it is more valuable, and it depends on details a normal drop-in booking never has to ask about. Treat it like just another slot in the diary and you will find out, usually on the day itself, everything the standard flow forgot to capture.

Why parties break a normal booking flow

A drop-in booking is one person, one activity, one price. A party is a room, a host who needs briefing separately from the guests, food that may or may not be part of the package, and a group size that keeps changing right up until the morning of the event because someone's cousin can or cannot make it after all.

None of that fits neatly into the fields a normal booking form asks for. Try to force it through the same flow and you end up with the real details living somewhere else: a string of emails, a note on a sticky pad, a memory someone on shift that day is expected to have. The party itself might go perfectly well, but only because a staff member happened to remember what the booking form never recorded.

Take the enquiry once, properly

The fix is to stop treating a party like a booking and start treating it like what it actually is at first: an enquiry that has not been priced yet. A form built for parties, separate from your normal booking page, asks for what a party genuinely needs to know before anyone can quote it. The occasion, the date they have in mind, roughly how many guests, whether food is wanted, any allergies worth flagging early rather than discovering at the table.

Ask for it once, in writing, and you never have to reconstruct the conversation from memory later. The enquiry becomes a thread you can come back to, reply in, and hand to whoever is on the desk when the parent calls to ask "did you get my message", without that person needing to hunt through a shared inbox.

Quote in writing with a link they can accept

Once you know roughly what the party involves, quote it properly rather than talking a price over the phone that nobody wrote down. A written quote, sent as a reply in the same thread, does two things a verbal number never does: it gives the parent something to check against later, and it gives you something to point back to if the group size or the food order changes between booking and the day itself.

Send it with a link the parent can accept themselves, in their own time, rather than needing to call back to confirm. Accepting is the moment the enquiry stops being a conversation and starts being a booking, and it is worth making that moment as easy as clicking one link rather than playing phone tag around a school run.

Deposit now, balance at the desk

A party deposit does more work than a drop-in deposit ever needs to. It is protecting a room, a member of staff, and often a slot you turned other bookings away to keep clear, all before you know for certain the party is really going ahead. Take it as soon as the quote is accepted, through the same link, so the booking is confirmed and the calendar is blocked automatically rather than held open on trust until someone remembers to check it.

The balance is different. By the time the party actually happens, the final numbers have usually shifted, someone brought a friend, someone dropped out, an extra round of drinks was ordered. Settling that at the desk on the day, against what actually turned up rather than what was guessed weeks earlier, is fairer to the parent and more accurate for you than trying to nail down an exact final figure in advance.

The day itself: check in the party, seat it, hand over the shelf

On the day, the party is not one booking, it is a group arriving together and needing to become one seated party fast, before the excitement of a room full of children turns into a flurry of separate questions at once. Check the lead booker in and everyone attached to that booking should come with them, rather than being checked in one at a time like separate walk-ins.

Seating should follow the same speed. The room the party was quoted for is already known, so the only decision left on the day is which table takes which end of it, not whether there is space at all. And because a pottery party ends with painted pieces that need to go somewhere, the handover to the kiln room should be as quick as the check-in was: the whole party's pieces logged together, under the booking that already has everyone's name and contact details attached, rather than reconstructed from handwriting on masking tape after the room has emptied.

Afterwards: the collection email that brings the parents back

The party itself ends when the room is cleared, but the booking does not end until every piece painted in it gets collected. That is the second chance a birthday party gives you that a drop-in rarely does: an email a few weeks later telling the parent their child's piece is ready is not just good service, it is a reason for that family to walk back through your door.

Send it warmly, keep the booking reference visible so nobody has to remember which party this was, and make collecting as easy as picking a time that suits them rather than hoping they happen to be passing. A party that ends in a well-handled collection is the version of the story that gets told to the next parent choosing where to book their own child's birthday.

Kilndar turns a party enquiry into a thread, a quote, a deposit and a day-of check-in on one booking, with the pieces and the collection email attached to the same record. Read more on the features page.