Build a Booking Website with WordPress

Who this build fits and what the first version needs

This build fits salons, consultants, clinics, trainers, tutors, repair services, agencies, and other appointment businesses. A working first version needs at least one employee/resource, one service, reliable availability, a booking form, confirmation, cancellation/rescheduling policy, notifications, and a way for staff to see upcoming appointments.

Booking is really an availability problem. A polished calendar is useless if two customers can reserve the same person or the system ignores a day off. Amelia documentation makes the dependency clear: services require at least one employee, and employees carry working hours and availability. That is the right way to think about the build—model the resources first, then expose bookable time.

What to know before you start

• List every resource that constrains availability: staff, rooms, equipment, locations, or capacity.
• Define service duration, buffers, lead time, maximum advance booking, and whether group capacity is allowed.
• Decide when payment is required: none, deposit, or full payment.
• Write cancellation and rescheduling rules before turning on customer self-service.
• Confirm the site timezone and whether customers in other timezones should see localized appointment times.

Recommended plugin stack

Plugin choices for this guide: Booking plugins differ a lot by service type and scheduling workflow. Compare them in our best WordPress booking plugins roundup. For this guide, we use Amelia. For email delivery, compare the best WordPress SMTP plugins; this guide uses FluentSMTP only if booking confirmations need a dedicated delivery layer. For SEO, compare the best SEO plugins; this guide uses Rank Math.

How to build a booking website with WordPress step by step

Amelia’s current quick-start flow is simple: employee, service, form, then a real test booking. Build that minimum path before adding packages or complex automations.

Step 01: Create the employee or bookable resource

Go to Amelia → Employees and add the person who delivers the service. Set name, email, working hours, days off, location, and timezone behavior. Turn on the option that makes the employee available on the website where required.

Check: The employee is active and their working hours match the real schedule.

Step 02: Create the service

Go to Amelia → Services. Create a category if needed, then add the service name, duration, price, capacity, and assigned employee. Keep the service name customer-friendly.

Check: The service is assigned to at least one available employee and has the correct duration and price.

Step 03: Set booking rules

Configure minimum notice, booking window, buffer time, capacity, cancellation/rescheduling rules, and whether appointments start as approved or pending. Match these settings to the real business process.

Check: A customer cannot choose a time that violates working hours, days off, notice, or buffer rules.

Step 04: Add the booking form to a page

Create a Booking page and insert Amelia’s Step-by-Step Booking Form using the Gutenberg block, supported builder widget, or shortcode such as [ameliastepbooking]. Publish the page.

Check: The public booking page loads the service and available time slots.

Step 05: Configure payments if required

If customers must pay or leave a deposit, connect the supported payment method and configure when the appointment becomes confirmed. Skip payments entirely if the business collects payment offline.

Check: Successful and failed test payments create the correct appointment/payment state.

Step 06: Configure confirmations and reminders

Set the customer and employee notifications you need for new bookings, cancellations, reschedules, and reminders. If you use scheduled reminders, confirm WordPress cron or the required scheduled task is running.

Check: A test booking sends the expected confirmation to both the customer and staff.

Step 07: Make a complete test booking

Open the booking page in a private browser window, choose the service and time, submit the booking, and then verify it under Amelia → Bookings → Appointments. Test one reschedule/cancel flow and one unavailable time.

Check: The customer-facing time, admin appointment, notifications, and payment state all agree.

What to know before launch

Calendar integrations, reminders, and payment gateways are external dependencies. A booking can be correct inside WordPress while a calendar sync or email reminder fails. Keep a monitoring routine and a manual fallback for urgent schedule issues. If appointments involve medical, legal, or other sensitive information, collect only what is needed and review applicable privacy requirements.

Mistakes to avoid

• Using default working hours without checking staff schedules. The system may expose time nobody can serve.
• Ignoring buffers. Back-to-back appointments can be impossible when travel, cleanup, or preparation is required.
• Assuming calendar sync is instant and flawless. Understand conflict rules and which calendar is authoritative.
• Sending reminders without checking cron. Scheduled notifications need the underlying scheduler to run.
• Letting customers cancel too late without a policy. Configure the system around a written rule.

Best practices for a stronger site

• Keep service names, durations, prices, and preparation notes visible before the customer chooses a time.
• Use one authoritative availability source per employee and document how external calendars interact with it.
• Create a staff procedure for manually blocking emergencies, vacations, and special hours.
• Send reminders at a time that gives customers a realistic chance to reschedule.
• Review no-shows, reschedules, and booking abandonment to improve rules instead of adding more form fields.

Launch checklist

• Every service is assigned to the correct employee/resource.
• Working hours, breaks, days off, and timezone are correct.
• Double booking is prevented in the intended scenarios.
• Payment failure does not create a falsely paid booking.
• Confirmation, cancellation, reschedule, and reminder messages arrive.
• Scheduled reminder cron is functioning.
• Staff can see the information they need without exposing unnecessary customer data.
• Booking form and date/time selection work on mobile.

Operational ownership and maintenance

Booking systems need an owner who checks schedule changes, employee availability, calendar sync, reminder delivery, and failed payments. Build a routine for holidays, emergency closures, staff changes, and daylight-saving or timezone issues if your audience spans regions. Keep a manual fallback for important appointments so staff know what to do if the external calendar, payment gateway, or notification service becomes temporarily unavailable.

How to confirm the first version works

Book the same service in several realistic conditions. First choose a normal available slot and confirm both customer and staff see the same time. Then try a conflicting slot, a day off, a time inside the minimum-notice window, and a reschedule or cancellation. If payment is enabled, test success and failure. If calendar sync is enabled, verify a busy external event blocks availability exactly as intended rather than assuming the integration is working because it connected successfully.

Conclusion

Get availability right before adding marketing features. A booking site is successful when customers can choose a valid slot, staff see the same truth, and changes propagate reliably. Everything else is secondary.

FAQs