WordPress booking systems: time slots, confirmation emails, and cancellation rules

A photography consultation, craft workshop, and one-to-one lesson all appear to be a choice of date and time, but their real constraints differ. One needs instructor approval, another a minimum number of attendees, and another cleanup after the service. Putting a calendar on the website alone solves none of these problems.

Before building a booking system, write down the rules normally confirmed by phone. The plugin should show available slots under those rules, keep records, and send notifications. Staff also need a process for cancellations, failed payments, and unexpected closures.

Define whether the booking reserves a person, a place, or a resource

For a one-person photography consultation, allow 45 minutes plus 15 minutes to prepare afterward; one instructor can receive only one party at a time. A craft workshop may hold six people in one slot. If two instructors share a classroom, the room itself also limits bookings; separate staff availability is not enough.

For each service, list its duration, buffer, minimum and maximum attendance, staff member, location, and equipment. Say whether a group reserves the whole slot or unrelated customers may join the same slot. These details show whether a plugin’s capacity and resource features meet the need.

Also define the minimum advance notice, how many months ahead customers can book, and cancellation and rescheduling cutoffs. If staff cannot arrange someone at short notice this afternoon, do not display a slot one hour from now as immediately bookable. Online rules should match bookings taken by phone, at the desk, and through social messages.

Compare plugins and paid features against the workflow

Amelia organizes services, staff, and appointment management, making it a candidate for a studio’s scheduling needs. Bookly also supports booking and calendar integration, but Google Calendar synchronization has different modes; full two-way sync needs the corresponding plan or add-on. “Supports Google” does not mean every mode offers the same capability.

If products and payments already run through WooCommerce, consider WooCommerce Bookings. In its “requires confirmation” flow, the customer first requests a slot and receives a payment link after confirmation. This differs from paying and completing a booking immediately on button click, so both wording and notifications must reflect the state before and after approval.

Check whether each candidate has three required capabilities: capacity for people or resources, the payment method you need, and a customer route for cancellation or rescheduling. A free version displaying a basic form does not imply it includes every operational feature. Budget for licensing, notification-channel fees, and maintenance, then prototype one candidate.

Set regular and exceptional hours with Amelia

Set the correct city time zone in WordPress, such as Taipei, then decide whether to display times in the customer’s time zone. Cross-border online consultations should state the time basis on the booking page and confirmation email. For in-person services, make clear that the time is local to the venue so both parties interpret the same appointment consistently.

Create the service, assign staff and working hours, and set service duration and required buffers. Amelia’s time-slot step limits usable time increments. For a 45-minute service plus a 15-minute buffer, choose a step that supports those values, then check the actual start times shown to customers.

Handle days off and special working days separately. Amelia’s special days can override normal working hours, while days off still take priority and prevent booking. Before adding a makeup workday, check whether a day off is also configured. If the location changes at short notice, verify that the assigned staff member offers the service and has availability there; changing only the displayed address is insufficient.

1. Set the site time zone and create services, staff, and locations.
2. Enter service duration, buffer, capacity, and regular working hours.
3. Add days off and special days, then check priority on exception dates.
4. Use a customer account to inspect selectable slots and compare each with the written schedule.

Distinguish request submission, confirmation, and payment notices

After a booking is created, the page and email should state its current status. If manual approval is required, explain how and when staff will respond. For an immediately confirmed service, provide the date, time zone, location, service details, and preparation instructions. Do not title a pending-approval email “Booking confirmed” and prompt a customer to arrange travel prematurely.

Amelia has event-triggered and scheduled notifications. Creation, rescheduling, or cancellation may trigger a message immediately; a reminder one day ahead requires the scheduler to keep running. In testing, wait until the reminder’s scheduled time and verify that the site scheduler actually ran. One immediate confirmation email does not prove that the next-day reminder will arrive.

Test customer and staff notifications separately. Customers need an action route; staff need service details and tasks. Internal notes must not be emailed to customers. Collect only the phone number, name, and other fields required for the service. When payment fails, clearly say whether the slot remains held and what to do next.

Test capacity, calendar sync, and rescheduling

Have two ordinary customer accounts book the same slot in sequence and watch whether remaining capacity is correct. Amelia has a setting that can allow pending appointments beyond maximum capacity, and administrators may have permission to override limits. If the studio does not accept overbooking, align both settings and daily procedures with that rule.

When using an external calendar, check sync direction, which busy events block slots, and whether updates lag. Bookly’s documentation specifically warns that an all-day event marked free may not block a slot as expected. Test creating, changing, and deleting an event; seeing one appointment appear on a calendar is not enough to finish validation.

After a customer reschedules, check that the new slot is reserved, the old one released, and the date and location updated in notifications. Test multi-session purchases, group bookings, and one participant’s cancellation separately so a single action does not remove the whole group’s still-active bookings.

Make cancellation and refunds a traceable closing process

On the booking page, explain cancellation, rescheduling, lateness, and no-show rules, including contact routes and applicable time limits. Actual policy must suit the service and applicable rules; a plugin setting that limits a button does not replace a judgment about consumer rights.

After cancellation, verify the slot, order, and payment separately. Even when the screen says “Cancelled,” check whether the payment provider actually refunded it, how much, and whether the refund failed. With manual bank transfers, record the responsible person and outcome. After a refund, verify that notifications no longer tell the customer to attend.

Before opening bookings to the public, rehearse an unexpected closure: find affected appointments, contact and reschedule each customer, update the roster, and record the outcome. Routinely review the next week’s schedule, unconfirmed requests, and failed notifications so online booking reduces coordination instead of becoming another form staff must constantly watch.

Check WordPress email delivery

Plan a website contact form

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress