Studios — photography, music rehearsal, voiceover booths, recording rooms, podcast suites — have a peculiar booking shape that doesn’t fit either of the two patterns most WordPress booking plugins are built for. They’re not appointment-based the way a salon is (the booker isn’t paying for a person’s time, they’re paying for time-on-equipment-in-a-space). And they’re not pure equipment rental (the kit doesn’t leave the building, but it does need scheduling). They’re somewhere in between, and that in-between is what most plugin shops get wrong.

This post is a practical walk through how studios actually book — what makes the workflow distinct, what features matter, and what to set up if you’re moving from spreadsheets or a phone-booking-only model to a real online system.

Why studios are weird

A studio booking, broken down:

The bookable thing is the room with its installed equipment — a 1,000 sq-ft cyclorama with a Profoto pack, a tracked drum room with a pre-miked kit, a vocal booth with a Neumann U87.
The duration is variable (a half-day, a full day, a 2-hour block) but constrained by your operating hours.
There’s often a deposit collected up front, with the balance billed against actual usage on the day.
Add-ons matter: extra strobes, a specific mic, an assistant for the day, a backline rental. These multiply by booking, not by time slot.
Cancellation policy is real — late cancellations cost the studio inventory because the slot can’t easily be re-sold.
The booker is sometimes a return customer (a regular photographer or band) and sometimes a one-time guest who needs verification.

Most appointment-booking plugins — built around service × employee × time-slot — don’t model any of this naturally. You end up with a fake “service” called “Studio A 4-hour block” and a fake “employee” called “Studio A,” and the rest of the workflow fights you. Most pure rental plugins don’t model the per-booking add-ons or the deposit-then-final-bill pattern.

The right shape is resource-first, with custom fields per booking, configurable approval, and .ics delivery so the booker actually shows up. Once that’s in place, the studio runs itself.

Mapping a studio onto a booking system

Here’s the configuration most studios converge on after a few weeks of running their booking:

One bookable page per room. “Studio A,” “Studio B,” “Vocal Booth 1,” “Drum Room.” Each is its own page with its own:

Bookable hours (matching staffed hours, with day-of-week variation if the studio isn’t open every day)
Minimum slot duration (typically 2 or 4 hours; rarely shorter)
Buffer time between bookings (45 minutes is common — strike, reset, breakfast)
Custom fields (project description, expected crew size, add-ons selection, deposit reference)
Maintainer assignment (the studio manager who reviews bookings)

Two booking modes per room. Studios usually run a hybrid policy:

Auto-approve for return customers — past customers in good standing book and get an immediate confirmation.
Manual approve for new customers — the studio manager reviews to assess fit (large productions, specialized requests, or just calibrating against the day’s load).

The mechanics: org-email restriction set to your past-customer list isn’t quite the right tool, but a “trusted booker” admin role plus manual-approve for everyone else gets you most of the way. Approve once, customer’s bookings auto-confirm thereafter.

OTP verification on every booking. Studios get drive-by spam — bots filling slots with fake addresses, bookers using throwaway emails to grab a desirable Saturday. OTP cuts this to zero. Every booker confirms a code sent to the email they registered with before the slot is held. (Why this matters in detail: What is OTP-verified booking.)

Custom fields per page. The studio manager needs information at booking time, not a follow-up email exchange. Common fields:

Project description (free text)
Crew/band size (number)
Add-ons checklist (checkboxes for extra strobes, specific mics, backline gear, assistants)
How they heard about you (helpful for marketing attribution; optional)
Deposit reference number (filled in after they pay separately, if you take deposits via Stripe outside the booking flow)

.ics calendar attachment on every confirmation. Studio bookings happen days or weeks in advance; the booker forgets between booking and arrival without a calendar entry. The .ics attachment sits in their actual calendar with reminders, dramatically cuts no-shows.

Deposits and payment — handle separately

This is where most studios trip up: trying to find a booking plugin that handles deposit collection, balance billing, refundable holds, and the rest of the financial machinery they need. The realistic answer is to keep deposit collection out of the booking flow entirely.

The pattern that actually works:

Booker books the slot. Status: pending approval. Slot is held.
Studio manager reviews; if approving, sends an invoice for the deposit via Stripe / Square / whatever you already use. Booking marked “awaiting deposit.”
Booker pays deposit. Studio manager marks the booking confirmed (or wires up a webhook from Stripe to do this automatically — a small dev project, but doable).
Day of: booker arrives, balance is calculated based on actual hours, charged through your existing payment system.
Booking marked completed. Audit trail closed.

The booking plugin handles the calendar and the audit trail. Stripe handles the money. Trying to make one tool do both ends in compromises on both sides.

What a typical studio configuration looks like

A medium-sized photography studio with three rooms — Studio A (large cyclorama), Studio B (medium daylight), and a small product room — running on booknslot:

Three pages, one per room.
Operating hours: 8 AM to 8 PM, seven days a week, with maintainer-controlled blackouts for renovations or holidays.
Minimum slot: 4 hours on Studio A and B, 2 hours on the product room.
Buffer: 45 minutes between bookings on A/B, 15 minutes on the product room.
Approval mode: manual approve on first-time bookers, auto-approve on returning customers (managed via an internal trusted-booker list).
Custom fields: project description, crew size, add-ons checkboxes, deposit reference.
OTP verification: mandatory on all bookings.
Calendar attachments: enabled on all confirmations.
Audit trail: full, exposed to admin and the studio manager.

Setup time, for someone who already runs WordPress: about a day, mostly spent writing the room descriptions and add-on options. Once it’s running, daily operation is the studio manager checking the pending queue once or twice a day and approving or rejecting.

Recording and rehearsal studios specifically

A note for music spaces: rehearsal rooms and small recording studios often have an additional wrinkle — band membership. The booker might be one member of a five-person band, and you want all five members to get the calendar invite. Two ways to handle that:

The simplest: add a custom field “additional band member emails (comma-separated).” On approval, the system emails the calendar attachment to all listed addresses. Skips the verification step on the additional emails — they’re trusted as members of the verified booker’s group.
The fancier: treat each band as an organizational unit with its own org-email-domain configuration. Overkill for most studios; relevant for larger operations with dozens of regular bands.

The simple custom-field approach handles 95% of cases without configuration complexity.

Where to start

If you’re moving from a spreadsheet or a phone-booking-only model, the rough plan:

Inventory your rooms. One bookable page per room.
Decide your minimum slot duration per room.
Decide your approval policy: auto for everyone, manual for everyone, or hybrid.
List the custom fields you want collected at booking time.
Decide how deposits are handled (recommendation: kept out of the booking flow).
Set up OTP verification — non-negotiable for any public-facing studio booking page.
Wire up the maintainer dashboard to whoever runs the schedule day-to-day.

The live demo walks through a single booking on mock data so you can see the flow before committing. About 90 seconds, no signup. The fictional resource is a lab oscilloscope, but the booking shape is identical to a 4-hour block on Studio A.

For wider context on the case for a real booking plugin instead of a spreadsheet, see Why your WordPress site probably needs a booking plugin. For the broader feature breakdown, see What makes booknslot different.