Bookly plugin review and common issues

Time slot display depends on service duration and staff working hours alignment. Check: (1) in Bookly → Staff Members → [staff] → Schedule, verify the working hours are set for the selected day with sufficient time for at least one appointment; (2) the service duration plus any buffer time must fit within a working hours block; (3) verify the time slot length in Bookly → Settings → General → Time Slot Length is configured appropriately (15 or 30 minutes); (4) check the minimum advance booking time setting — if set to 24 hours, same-day slots will not appear; (5) if using the Multiple Staff add-on, ensure the staff member is assigned to the selected service.

Bookly uses WordPress’s wp_mail() for notifications. Check: (1) go to Bookly → Notifications → Email Settings and verify the “From” email address and the notification trigger (on booking confirmation, on payment); (2) use WP Mail SMTP’s test email function to verify WordPress email is working at all; (3) check the client’s spam folder; (4) review Bookly → Notifications to confirm the specific notification templates are enabled and contain valid content; (5) for WP Mail SMTP or other SMTP plugins, ensure the SMTP configuration is valid — Bookly inherits WordPress’s email sending configuration.

WooCommerce payment in Bookly requires the WooCommerce add-on. With the add-on installed: (1) go to Bookly → Settings → Payments → WooCommerce and enable the integration; (2) verify WooCommerce is active and a payment gateway is configured; (3) check that the service price is set (non-zero price) in Bookly → Services — free services do not trigger payment; (4) ensure the Bookly WooCommerce product is published in WooCommerce → Products (Bookly creates a virtual product automatically); (5) test with a service that has a specific price configured.

Chained appointments (booking multiple services sequentially in one booking session) require the Chain Appointments add-on. With it installed, clients can select multiple services during the booking process — the plugin automatically calculates the combined duration and schedules the services back-to-back. This is useful for businesses where clients commonly book a haircut + color treatment together, or a massage + consultation. Configure which services can be chained in the add-on settings.

Custom fields on the booking form require the Custom Fields add-on. After installing, go to Bookly → Custom Fields → Add New Field. Select the field type (text, textarea, select, checkbox, file upload) and configure the label, required/optional status, and which services display this field. Fields appear in the booking form between the client information step and confirmation. Responses are saved with each appointment and visible in the booking details in Bookly → Appointments.

Bookly free is suitable for a solo practitioner (single staff member) offering one service at one location. If you need to add a second staff member, accept online payments, send SMS reminders, or enable recurring bookings, you need add-ons. For most real-world service businesses, at least 2-3 add-ons are required before the booking system is production-ready. Amelia’s paid-but-comprehensive approach is often more cost-effective for businesses that need the full feature set.

Bookly does not claim HIPAA compliance out of the box — it is a general-purpose booking plugin. For medical practices with HIPAA requirements, the data stored in Bookly (patient names, appointment types, contact information) is stored in your WordPress database. True HIPAA compliance requires a Business Associate Agreement (BAA) with your hosting provider, encrypted data transmission, access controls, and audit logs that WordPress alone does not provide. Bookly can be part of a HIPAA-aware setup when combined with appropriate hosting, but it does not carry its own HIPAA certification.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.