JetAppointment plugin review and common issues

Time slot availability requires: (1) the service provider’s working hours are correctly configured in JetAppointment → Appointments → Service Providers → [provider] → Schedule; (2) the service’s duration is configured — a 60-minute service in a provider’s 9am-5pm schedule should show time slots from 9am to 4pm (last slot starts 1 hour before closing); (3) the appointment form widget is connected to the correct service and provider; (4) buffer time between appointments may be consuming available slots — reduce or disable buffer time for testing; (5) verify the date being checked is not a configured day off.

JetAppointment email notifications use WordPress wp_mail(). Check: (1) in JetAppointment → Settings → Email Notifications, verify customer confirmation email is enabled with correct template and recipient (the booking email address field); (2) configure WP Mail SMTP for reliable delivery of transactional booking emails; (3) check the booking email address in the customer’s submission — if the email field was not required and was left blank, no confirmation can be sent; (4) verify the email is not in spam; (5) test with a real email address on a test booking.

Google Calendar sync requires OAuth connection: (1) in JetAppointment → Settings → Google Calendar, connect with a Google account that has Calendar API access; (2) each service provider must be assigned a Google Calendar in their provider settings (their individual work calendar); (3) verify the Google Cloud project has the Calendar API enabled; (4) OAuth tokens can expire — reconnect the Google Calendar integration if sync was previously working; (5) new bookings sync to Google Calendar on booking confirmation, not retroactively — verify new bookings after configuration.

In JetAppointment, create multiple Service Providers (staff members) each with their own schedule and service assignments. Create an Elementor page with the JetAppointment Booking Form widget. In the widget settings, configure the form to show Service Provider selection as a field — customers choose their preferred provider. The time slot availability updates dynamically based on the selected provider’s schedule. Connect the booking form to WooCommerce or Stripe for payment collection at the booking step.

Create a JetEngine Listing Grid that displays service providers as posts (if providers are a custom post type) or as a repeater from JetEngine’s meta data. Add JetAppointment dynamic tags to show each provider’s next available slot in the listing cards. Combine with JetSmartFilters to allow filtering providers by service type, location, or availability. Each provider card links to their individual booking page. This creates a provider directory with embedded availability indicators.

Amelia is a more mature, standalone appointment solution with a superior admin management interface, richer reporting, customer profiles, and more comprehensive email workflows — making it better for businesses where appointment management is the primary focus. JetAppointment is better for Crocoblock users already using Elementor + JetEngine who want native ecosystem integration at a lower cost ($19 vs $69/year). For a spa website not already using Crocoblock, Amelia’s better UX and appointment-focused feature depth make it the more suitable choice.

JetAppointment is designed for one-on-one appointments where one client books one provider per time slot. For group bookings (e.g., a yoga class with 15 participants booking the same session), JetBooking’s capacity-based booking or a dedicated group booking solution is more appropriate. Some workarounds exist for group bookings in JetAppointment, but it requires custom configuration and is not a native supported use case.

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.