Skip to content

EP Booking

EP Booking is a full appointment-scheduling system. Services, staff, availability schedules, a multi-step booking form your customers fill out on your site (in their own timezone), Stripe payments, calendar invites, self-serve rescheduling, a multi-tier reminder ladder, public per-service booking pages, an embeddable widget for any website, signed webhooks, an admin calendar, a private video call for each booking (through EP Video on your own site, or Zoom), and actions an AI assistant can use to run your diary.

This page documents EP Booking 2.7.4. If you are on a 1.x version, take the update from your admin Updates screen; the upgrading section covers the one setting to check first.

Published by ElmsPark Studio.

What it does end-to-end:

  1. You define services (haircut, consultation, massage) with price and duration.
  2. You define staff with individual availability schedules, which services they offer, and optionally a personal calendar feed that blocks their slots.
  3. A customer visits your site (or your public booking page, or the widget embedded on another site), picks a service, picks a staff member (optional), picks a date and a time slot, with every time shown in their own timezone.
  4. They enter their details, optionally pay via Stripe, and confirm.
  5. Automated emails go out: a confirmation carrying a calendar invite (.ics), then reminders on your configured ladder (up to 7 days, 24 hours and 1 hour before).
  6. The customer can reschedule or cancel themselves from links in the confirmation email, within your configured window.
  7. Your admin panel shows the booking in a filterable list and on a month calendar. You can confirm, cancel, reschedule or refund from the admin.
  8. If you use webhooks, your CRM or automation platform is notified of every booking event, with an HMAC signature to verify.
  9. If EP Video (or EP Booking Zoom) is set up, the booking got its own video call automatically, and the link is in the confirmation email and the calendar invite. See Video calls.

What EP Booking is NOT: a calendar app, a resource scheduler for rooms, or a class-booking system for group events. It is appointment-by-appointment scheduling between one customer and one staff member.

  • PageMotor 0.11.5 or later (while PageMotor is in beta, each release needs the latest core)
  • EP Suite base class (bundled)
  • EP Email (required for notifications)

Optional add-ons:

  • EP Video for a private video call on your own site for each booking (recommended: nothing to install for your customers)
  • EP Booking Zoom for Zoom meetings instead
  • EP Cron for reliable reminder delivery on quiet sites (without it, reminders piggyback on page loads)
  • EP Newsletter to offer opt-in on the booking form
  • EP GDPR for consent logging
  • EP Affiliate to attribute bookings to referrers
  1. ep-booking.zip comes with an EP Suite licence, and ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.
  2. Upload via Plugins → Manage Plugins. Activate.
  3. Work through the settings sections in this order: General → Services → Staff → Categories → Booking Rules → Notifications → Form Design → Payments → Booking Form.

The 2.x line converts your bookings to be anchored in universal time (UTC), so daylight-saving changes and international customers can never shift an appointment. The conversion runs automatically on your first admin visit after updating, and it uses one setting to interpret your existing bookings:

Before you update, check Settings → General → Business Timezone and make sure it names your actual business timezone (for example Europe/London). Everything in 2.x derives from it: availability, slot generation, reminders, invites and the one-off conversion of your existing bookings.

Everything else is opt-in. Rescheduling, public pages, webhooks and round-robin assignment are all off by default, so nothing about your live booking flow changes until you switch a feature on.

  • Business name, address, phone for notification emails.
  • Opening / closing times are the outer envelope of when bookings are possible. Individual staff schedules can be tighter.
  • Business Timezone. The single most important setting. All availability, booking maths and reminders derive from it.

Create each bookable service with:

  • Name (e.g. “60-minute massage”).
  • Category (optional grouping).
  • Duration in minutes.
  • Price. Set to 0 for free bookings.
  • Require payment? Per-service toggle. Off for free or pay-on-arrival services.
  • Active? Inactive services don’t appear on the booking form.

Create each staff member with:

  • Name and photo (optional).
  • Availability schedule, a recurring weekly pattern (e.g. Mon-Fri 9-5, Wed off).
  • Holiday blocks, specific date ranges to mark unavailable.
  • Services offered, picked from your service list.
  • Busy calendar (ICS URL), optional. Paste a secret ICS address from their Google, Outlook or Apple calendar and events on it block their booking slots. See external calendar sync.
  • Block with EP Calendar entries of, optional, shown when EP Calendar is active. Pick a site user and every entry that user makes in EP Calendar blocks this staff member’s slots straight away. See external calendar sync.

Optional. Groups services for display on the booking form and the [booking-services] catalog shortcode.

  • Minimum advance time. Can’t book less than N hours before the slot.
  • Maximum advance time. Can’t book more than N days ahead.
  • Default duration for services that don’t override.
  • Time slot interval. How finely slots are offered: 15, 20, 30, or 60 minutes.
  • Cancellation window. Customer can cancel (or reschedule) themselves up to N hours before the booking.
  • Self-Serve Rescheduling. Adds a reschedule link to confirmation emails so customers can move their own appointment. Off by default.
  • “Any Available” Assignment. How a booking is assigned when the customer picks “Any Available”: List order (legacy) always favours the first listed staff member; Least recently booked (round-robin) shares work evenly across the team. See round-robin assignment.
  • Auto-confirm? If off, bookings start in Pending and you manually confirm each one.

Four emails are configurable with templates:

  • Confirmation, sent immediately after booking, with the calendar invite attached.
  • Reminder, sent on the ladder you pick in Reminder Schedule: 24 hours + 1 hour before (recommended), 7 days + 24 hours + 1 hour, or a single 24-hour or 1-hour reminder. Each tier sends once, timed from the exact appointment instant; appointments booked inside a tier’s window simply skip that tier.
  • Rescheduled, sent after a customer moves their booking, with the updated invite attached.
  • Cancellation, sent when a booking is cancelled, with a cancellation invite that removes the event from the customer’s calendar.

Templates support placeholders: {customer_name}, {service_name}, {booking_date}, {booking_time}, {staff_name}, {business_name}, {cancel_url}, {reschedule_url}, and more. The rescheduled template additionally supports {old_booking_date} and {old_booking_time}. An admin-alert toggle emails you too whenever a customer books.

The default confirmation template includes the reschedule link automatically when rescheduling is enabled; if you have written your own template, add {reschedule_url} where you want it.

Visual controls so the booking form matches your site’s look:

  • Primary colour, accent colour, text colour.
  • Corner rounding on buttons and cards.
  • Max width of the form container.
  • Card shadow strength.

EP Booking is not only one-to-one appointments. Set a service’s Capacity above 1 and the slot accepts that many concurrent bookings. Set the Price label to something like per person and the price displays as £12 per person. Use it for yoga classes, group workshops and fitness sessions. Buffer times still apply between the slot and the next.

Each service has a buffer before and a buffer after, in minutes. These block the slots immediately adjacent to a booking so staff have time for cleanup or prep. They do not block whole days. For days off, use staff exceptions.

Bookings move through five states:

StatusSet byWhat happens
PendingA new booking when Auto-confirm is offNo confirmation email yet. Waits for admin approval.
ConfirmedAuto-confirm on, or an admin clicking ConfirmConfirmation email sent, reminder ladder armed, video call created (EP Video or Zoom) if the service has one.
CompletedAn admin, after the appointmentCloses the booking. Used for reporting.
CancelledThe customer’s cancellation link, or an adminCancellation email sent, video link removed. Stripe refund attempted if Auto-refund is on.
No-showAn admin, after a no-showCloses the booking without a refund. Used for reporting.
  • API keys for test and live modes.
  • Currency: GBP, USD, EUR, AUD, CAD, NZD, CHF, JPY.
  • Webhook secret so Stripe can notify the plugin when payments settle.
  • Per-service payment toggle lets you mix paid and unpaid services in the same booking system.

EP Booking is timezone-correct end to end:

  • Your availability is defined in your Business Timezone. A 9-to-5 Tuesday schedule means 9-to-5 in your local wall-clock time, on both sides of a daylight-saving change.
  • Visitors see slots in their own timezone. The form detects the visitor’s timezone and renders every slot label in it, with a note saying so, and a day marker when a slot falls on a different calendar day for them. A client in New York booking your 09:00 London slot sees 4:00 am, and both of you hold the same instant.
  • Bookings are stored as universal instants. Reminders, invites and rescheduling all work from the exact UTC moment, so nothing drifts when the clocks change.

Every confirmation email attaches a standards-compliant .ics invite that lands the appointment in Apple Calendar, Outlook or Google Calendar at the correct local time, with a built-in 1-hour alarm. When a booking is rescheduled the updated invite moves the existing calendar event rather than duplicating it, and a cancellation sends the matching cancellation file so the event is struck through or removed. When the booking has a video call (EP Video or Zoom), its join link is the event’s location and is also in the event description.

Each confirmed booking can get its own private video call, made automatically. The customer joins from the link in their emails, in the browser, with nothing to install. You join from Join as host in your bookings list.

Which service makes the call. Settings → Video calls → Video calls with:

ChoiceWhat happens
Automatic (default)Uses EP Video when it is active and set up, otherwise Zoom (EP Booking Zoom).
EP VideoCalls on your own site through EP Video. Shows “(not active)” if EP Video is not switched on.
ZoomZoom meetings through EP Booking Zoom.
No video linksNo calls for any booking.

The section tells you which one your bookings will use right now.

Per service. Each service has a Video call tick, on by default. Untick it for anything that happens in person, and its bookings get no link.

Where the link appears. In the confirmation, reminder and rescheduled emails, in the calendar invite (as the event’s location), and in the customer’s bookings. Email templates can use {video_url} for the customer’s link and {video_host_url} for yours. The older {zoom_url} and {zoom_host_url} still work and carry whichever call the booking has.

When things change. A rescheduled booking gets a new call and link, which goes out in the rescheduled email. A cancelled booking’s link is removed. Deleting a booking or a customer removes their calls too.

With EP Video, the call can also have its notes, transcript and follow-ups, like any other EP Video call. See the EP Video guide.

Enable Booking Rules → Self-Serve Rescheduling and every confirmation email carries a reschedule link. The customer lands on a plain page (no login, no JavaScript required) showing their current booking and a date picker of genuinely open slots. The move applies atomically: the slot is re-checked at the moment of submission, the updated invite goes out with a fresh video link (EP Video or Zoom), and pending reminders re-arm for the new time. The cancellation window doubles as the reschedule cutoff.

Enable Public Pages & Embed → Public Booking Pages and every active service gets its own shareable booking page URL, ideal for email signatures, social bios and QR codes. The settings panel lists the URL for each service.

The same panel gives you a one-line embed snippet:

<script src="https://YOUR-SITE/…/ep-booking-embed.js" data-ep-booking="SERVICE-SLUG" async></script>

Paste it into any website (a partner’s site, a landing page, anywhere) and a fully working, auto-resizing booking widget appears there, while your PageMotor site processes the booking exactly as normal. Optional data-staff="ID" pins the widget to one staff member. Copy the snippet from the settings panel rather than this page, as it carries your site’s real URL.

Set Webhooks → Webhook URL and EP Booking POSTs a JSON payload to it on four events: booking.created, booking.confirmed, booking.rescheduled and booking.cancelled. Delivery is best-effort with a 3-second timeout; failures are logged, never retried, and can never block or slow a customer’s booking.

Set a Signing Secret and every delivery carries an X-EP-Booking-Signature: sha256=… header, the HMAC-SHA256 of the raw body. Verify it before trusting the payload. Use webhooks to wire bookings into a CRM, an automation platform, or your own dashboard.

The Calendar section of the settings screen shows a month grid of every booking, colour-coded by status, with customer and service details on hover and previous/next month navigation. The bookings list remains the place to act on a booking; the calendar is the at-a-glance view of the month’s shape.

By default, “Any Available” bookings go to the first listed staff member who is free (the behaviour of every earlier version). Switch Booking Rules → “Any Available” Assignment to Least recently booked (round-robin) and the work is shared: each slot is offered under the team member who was booked longest ago, with ties broken by fewest upcoming appointments, then list order. Staff-specific bookings and each person’s exclusive hours are unaffected; only the choice among equally available team members changes.

Give any staff member a Busy calendar (ICS URL) in the Staff editor and events on that calendar block their booking slots. This is the provider-agnostic route: Google Calendar, Outlook and Apple Calendar all offer a secret ICS address for exactly this purpose, with no accounts to connect and no API keys.

  • Timed events and recurring events (daily, weekly, monthly and yearly, including “the last Friday” and Outlook’s “last weekday of the month”) are honoured, and dates removed in the source calendar stay open. All-day events block slots only when All-day calendar events is switched on under Booking Rules (it is off by default, so an all-day reminder or birthday does not close a whole day).
  • Feeds are checked at most every five minutes, so a change on the external calendar takes up to five minutes to affect the booking form.
  • If a feed is temporarily unreachable, the last fetched copy is used; if there is no copy at all, slots stay open rather than your booking page going blank, and the failure is logged.

The ICS URL is a secret: anyone holding it can read that calendar’s events. Use the calendar provider’s “reset private address” if it ever leaks.

With EP Calendar (2.5.0 and later). Instead of copying a calendar address, link the staff member to a site user under Block with EP Calendar entries of. That user’s EP Calendar entries, and any EP Calendar external feed set to block slots for them, then block this staff member’s slots immediately, with no five-minute wait. Cancelled entries never block, all-day entries follow the All-day calendar events setting, and a Busy calendar address keeps working alongside the link. If EP Calendar is switched off, bookings carry on as before.

ShortcodePurpose
[booking-form]The full multi-step booking form. Can be preset: [booking-form service=60-min-massage] or [booking-form staff=alice] or [booking-form category=wellness].
[booking-services]Service catalog grid. Each service links to a prefilled booking form.
  1. Customer lands on your booking page and sees the multi-step form.
  2. Step 1: service — pick from the list (or already preset via shortcode attribute, public page, or embed).
  3. Step 2: staff — pick a specific staff member, or “any available”.
  4. Step 3: date — calendar showing which dates have availability.
  5. Step 4: time — slots for the chosen date, shown in the customer’s own timezone, based on staff schedule, existing bookings and any external busy calendar.
  6. Step 5: details — name, email, phone, notes. Optional newsletter opt-in and GDPR consent.
  7. Step 6: pay (if applicable) — Stripe checkout.
  8. Confirmation — success message plus confirmation email with the calendar invite and, if enabled, the reschedule link.
  • Bookings. Filterable list. Status column (Pending / Confirmed / Cancelled / Completed). Actions to change status, cancel, refund via Stripe, or add notes.
  • Calendar. Month grid of all bookings, colour-coded by status.
  • Customers. Contact records with booking history per customer.
  • Services, Staff, Categories. CRUD interfaces for each.
  • Import / Export. JSON and CSV for bulk moves between sites.

Round-trips your booking structure between sites. Use it to move a sandbox configuration to live, to back up before a big change, or to stand a new site up from a config an AI wrote for you.

Five things, and only these five: categories, services, staff, staff-service assignments, and weekly availability.

Worth being precise about what is not in an export, because it is easy to assume otherwise:

  • Settings are not exported. Business details, timezone, booking rules, form design, notification copy and integration toggles all stay on the site. An export is not a settings backup.
  • Staff exceptions are not exported. Per-staff holidays, days off and custom hours stay behind too.
  • Bookings and customer records are not exported. They live on the site they were made on.

Because no settings leave the site, no Stripe key or webhook secret can leak through an export. The file is safe to share or commit.

JSON and CSV both round-trip. JSON is easier to edit by hand or with an LLM. CSV is easier to spot-check in a spreadsheet, and uses a ## Section header per section.

Pick the mode from the Duplicate Handling dropdown before importing:

  • Add to existing records (recommended, the default). Existing entries are left alone and only new ones are inserted.
  • Replace existing records. Entries matching on name, or email for staff, are overwritten by the imported version.
  • Delete all existing records and import fresh. Wipes categories, services, staff and availability before importing. Bookings and customers are not touched.

The Import/Export dashboard has a Generate with AI panel containing a copy-pastable prompt. Paste it into Claude, ChatGPT or Gemini, answer the interview questions about your business, and you get back a JSON file to drop into the importer. The prompt covers categories, services with capacity and buffers, staff with availability, exceptions and basic settings.

This is also the one route by which settings can arrive on a site through the importer. An export will never contain them, but a hand-written or AI-generated JSON can, and the importer applies them when they are present.

  • EP Video. Activate and set it up, and every confirmed booking gets a private video call on your own site, with the link in the emails and the calendar invite. See Video calls.
  • EP Booking Zoom. The Zoom alternative: every confirmed booking gets a Zoom meeting instead, recreated when a booking is rescheduled. Choose between them under Video calls.
  • Your AI assistant. An assistant connected to your site’s MCP can check free times, see who is booked, book someone in, confirm or cancel bookings and give staff a day off. See Your AI assistant.
  • EP Cron. When present, reminders ride its heartbeat instead of waiting for a page load, which matters on quiet sites.
  • EP Newsletter. Optional opt-in checkbox on the booking form with list selection.
  • EP GDPR. Consent logging on booking submissions.
  • EP Affiliate. Confirmed bookings fire an affiliate conversion, so referred bookings earn commission.
  • Stripe. Payment, webhook verification, and admin-initiated refunds from the bookings list.

EP Booking has its own actions in your site’s API and MCP, for administrators. An assistant such as Claude, connected to your site, can:

  • tell you who is booked today or on any day, and find a customer and their bookings
  • check which times are free for a service, the same list your customers see
  • book someone in (into a free time unless you say otherwise), confirm, cancel or refund a booking, and add a private note
  • give a member of staff a day off, or different hours for one day, and switch a service on or off

Anything that emails a customer or moves money waits for you to say yes first. Before cancelling, it tells you if the customer would also be refunded automatically. Giving someone a day off never cancels bookings already there: you are told which ones to deal with. Times are in your business time zone, which it names in every answer.

Every confirmation email includes a tokenised cancel link. The customer clicks it, confirms, and the booking is cancelled with a cancellation invite removing the event from their calendar — no login required. The cancellation window setting controls how close to the appointment they can still cancel (or reschedule) themselves.

There are two paths, and which one you get depends on whether EP Cron is installed.

With EP Cron active, EP Booking registers a task called ep-booking-reminders on the five-minute heartbeat. This is the scheduler of record: reminders fire on time whether or not anybody is browsing the site.

Without EP Cron, the fallback is a check that runs during ordinary page loads, throttled so it runs at most once every 60 seconds. A busy site is fine. A quiet site is not: if nobody visits for three hours, reminders queued in that window go out late by roughly that much.

If reminder timing matters at all, install EP Cron. That is the supported fix, and it is why the ladder can be trusted on a low-traffic site.

  • Honeypot spam protection on the booking form.
  • CSRF tokens on every endpoint.
  • Rate limiting per IP so the form can’t be scraped.
  • Stripe webhook verification so fake payment confirmations can’t mark bookings as paid.
  • Outbound webhook deliveries are HMAC-signed when a secret is set.
  • Reschedule and cancel links use one unguessable token per booking, checked together with the booking’s email address.

Check:

  1. A staff member has been assigned to the service.
  2. That staff member’s availability schedule covers the date range customers are trying to book.
  3. No holiday block is covering the date.
  4. Existing bookings haven’t filled every slot.
  5. If the staff member has a busy calendar URL, events on that external calendar may be blocking the slots. Remember all-day events block the whole day.

Almost always the Business Timezone. The form deliberately shows each visitor their own local time, so a customer abroad seeing a different clock time than you is correct behaviour, and the form says “times shown in your timezone”. But if times are wrong for local customers too, check Settings → General → Business Timezone names your real timezone.

“Confirmation emails aren’t sending”

Section titled ““Confirmation emails aren’t sending””

EP Email handles delivery. Check EP Email’s delivery log. Common causes: SMTP config is wrong, from-address is unverified, or the email queue is stalled.

The ladder needs something to wake it. On busy sites page loads are enough; on quiet sites install EP Cron so reminders ride its heartbeat. Also remember each tier sends once, and an appointment booked inside a tier’s window (e.g. booked 3 hours ahead, 24-hour tier) skips that tier by design.

“My webhook endpoint isn’t receiving events”

Section titled ““My webhook endpoint isn’t receiving events””

Deliveries are fire-and-forget with a 3-second timeout, and failures are logged to the PHP error log rather than retried. Check the endpoint responds within 3 seconds, and if you set a signing secret, make sure you are verifying X-EP-Booking-Signature against the raw request body, not a re-serialised copy.

“Stripe webhook says signature invalid”

Section titled ““Stripe webhook says signature invalid””

The webhook secret in your EP Booking settings does not match the webhook endpoint secret in your Stripe dashboard. Rotate the secret on both sides.

“I can’t refund a booking from admin”

Section titled ““I can’t refund a booking from admin””

Stripe refunds require the original charge to exist on the Stripe side. If the booking was imported from a prior system or paid outside Stripe, the refund button is inactive. Refund through Stripe directly.

“Customers are booking impossible slots”

Section titled ““Customers are booking impossible slots””

Check the time slot interval and the staff duration. If a service is 45 minutes and your slot interval is 60 minutes, customers can still book at :00 and :15 adjacent slots. Tighten the interval to 15 minutes, or align durations to your interval.

“The booking form submits but nothing appears in the admin”

Section titled ““The booking form submits but nothing appears in the admin””

Check for CSRF or rate-limiting errors in your browser’s network tab. Both return a 403 that shows as a generic error in the form.

“The embedded widget doesn’t appear on the other site”

Section titled ““The embedded widget doesn’t appear on the other site””

The snippet must be pasted as-is from the settings panel (it carries your site’s URL), and Public Booking Pages must be enabled: the widget loads the public page in an iframe, so turning public pages off turns the widget off too.

“I deleted a category but the services still exist”

Section titled ““I deleted a category but the services still exist””

That is by design and not a bug. Deleting a category clears the category from its services rather than deleting them, so they survive as uncategorised. Reassign them from the Services dashboard, or delete them individually.

“I imported a JSON but my settings didn’t change”

Section titled ““I imported a JSON but my settings didn’t change””

An export never contains settings, so a file produced by the exporter has none to apply. Only a hand-written or AI-generated JSON carries a settings block. If you were expecting an exported file to restore your configuration, it will restore your categories, services, staff and availability, and nothing else.

For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.

For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.

  • Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
  • A paid booking now stays paid. Stripe does not always send its messages in order. If a customer’s card was declined and they then paid another way, the late “payment failed” message could mark the paid booking as failed, and it then missed its reminders and follow-up emails. A paid or refunded booking now keeps its status.

A security update. Please install it.

  • A booking cannot change someone else’s phone number. The booking form only updates the phone on a customer’s record when they are signed in under that email, or the record has none yet. A different number given with a booking is kept in the booking’s notes.
  • Card payments in Bahraini, Jordanian, Kuwaiti, Omani and Tunisian currency are now sent to Stripe at the right amount.

Open a service with Edit and expand Booking rules for this service to use the first five.

  • Each service can have its own booking times. For example a 30-minute call offered only on Monday at 16:00, Tuesday afternoon and Wednesday at 10:00, while longer sessions use the full working hours. The times can sit inside the staff member’s hours or replace them for that service. Time off, closed days and existing bookings always count.
  • Each service can have its own start-time step, such as every 30 minutes for a short call while sessions start on the hour.
  • Ask your own questions on the booking form, per service. Short or long answers, drop-down lists, choose-one and tick boxes, each optional or required, and a question can wait for an earlier answer (for example “Has your Access to Work been approved?” only after “Access to Work”). The answers are kept with the booking, shown in its details and in your new-booking email, and included when someone asks for a copy of their data.
  • Greet people by first name with {customer_first_name}, so an email says “Hi Mary,” and not “Hi Mary Smith,”. Answers can go into emails too, as {answers} or {answer:short-name}.
  • Each service can have its own confirmation and reminder wording.
  • Follow-up emails after the appointment, per service, a chosen number of hours after it ends. Sent once, never to cancelled or no-show bookings, and never more than two days late, so adding one does not email past clients.
  • The screen after booking now shows the booking: what, the date and time in the visitor’s own time zone with yours beside it, the video link once the booking is confirmed, and Google, Outlook and .ics add-to-calendar buttons. The message above it can use the same placeholders as the emails. You can turn the details off under Booking Form.
  • Optional time-zone list under the times, so a visitor can pick their zone if their device reports the wrong one.
  • Your AI assistant can set all of this, and can read each service’s rules and the answers given on a booking.
  • Needs PageMotor 0.11.5.
  • The times shown now always belong to the date you picked. If a visitor tapped one date and then another straight away, the first date’s times could appear under the second date’s heading. The booking itself was never made for the wrong day, because the time is checked again when the booking is sent; only the list on screen could be wrong.
  • Screen readers now announce the booking form’s messages. The confirmation, an error when a booking cannot be sent, and the “unable to load” notices are read out, not only shown.
  • Needs PageMotor 0.11.5.
  • Delete several bookings at once. The Bookings list now has a tick box on every booking and one at the top to tick every booking on the page. Tick the ones you want gone and press Delete selected. You are asked twice, with the number of bookings named, before anything is removed.
  • Each booking is deleted exactly as the single Delete does it, including removing its video call. Up to 200 at a time.
  • Needs PageMotor 0.11.5.
  • Deleting a booking clears its line straight away. After you deleted a booking from the Bookings list, its line stayed on screen until you reloaded the page, and its View button opened nothing. The whole line now goes the moment the booking is deleted.
  • Needs PageMotor 0.11.5.
  • Fixed: bookings made from the public booking form now get their video link. With EP Video, a booking made from the public form or booking page was confirmed with no video call, and a rescheduled booking kept its old link. Bookings confirmed from the admin and the Zoom add-on were not affected.
  • Fixed: cancelling from the link in the confirmation email now removes the video call, as cancelling from the admin always has.
  • Session packages. Sell or give a customer a number of sessions of one service, to be used within a number of days (for example 6 coaching sessions within 90 days). Set them up under Session packages in EP Booking’s settings.
  • Customers book against their package without paying again. A signed-in customer booking under their account’s email uses one session; the confirmation tells them how many are left. When none are left, or the package has ended, the booking is refused with a plain reason. Cancelling a booking gives the session back.
  • Package-only services. Mark a service so it can only be booked by someone with sessions left on a package for it.
  • Shop purchases grant packages. With EP Ecommerce, list the products that grant a package; a paid order gives the buyer the package, and you get an email saying so. A full refund cancels the package, and a refund that fails re-opens it.
  • Extend or adjust a package. Move a customer’s package later for an agreed break, set its last day, add sessions or record sessions used elsewhere. Every change is kept in the package’s history.
  • Customers see their sessions. Put [ep-booking-packages] on a page: a signed-in customer sees each package, the sessions left, the last day and the bookings it covers.
  • Your AI assistant can run packages. New actions: list-packages, save-package, set-service-package-only, grant-package, list-customer-packages, get-customer-package, extend-package, adjust-package, set-package-status, import-packages and sync-package-purchases. create-booking can book against a package.
  • Bring packages across from another booking system. import-packages takes the packages and the customers holding them (with sessions already used), reports what it would do first, and is safe to run twice.
  • Data requests cover packages. With EP GDPR, a person’s data export includes their session packages, with each package’s notes and the bookings drawn from it, and erasing them removes the packages too. Deleting a customer now removes their packages as well.
  • Needs PageMotor 0.11.5.
  • Rescheduling now only offers days with free times. When a customer moves their booking, the date list shows only days with a time they can move to, the same as the booking form’s calendar. Before, they could pick a day the staff member doesn’t work and were only then told nothing was free.
  • The reschedule page now follows the all-day calendar events setting, the same as the booking form.
  • Needs PageMotor 0.11.5.
  • The key sentence under each message box is now in bold. Under Confirmation, Reminder, Cancellation and Rescheduled, “Leave this empty to send the built-in email” now stands out, so it is hard to miss that an empty box sends the full booking details.
  • Needs PageMotor 0.11.5.
  • The codes for your booking emails are now in plain sight. Under each of the four message boxes (Confirmation, Reminder, Cancellation and Rescheduled), a line now always shows what happens. An empty box sends the built-in email with the booking details. Anything you type is sent as written, with codes such as {booking_date} and {booking_time} filled in, and the line lists every code you can use. In 2.7.5 this sat behind a small help icon that was easy to miss.
  • Needs PageMotor 0.11.5.
  • The Reminder Message and Cancellation Message boxes now explain themselves. Each has a help icon saying that an empty box sends the built-in email, with the service, staff, date, time and duration, and that anything you type is sent exactly as written. It also lists the placeholders you can use, such as {booking_date} and {booking_time}, so a short custom message can still carry the booking details.
  • Needs PageMotor 0.11.5.
  • Close the whole business from the admin. Under Staff there is now a “Close the whole business” box: pick a date, add an optional reason, and press Close this day. Nobody can be booked that day, and any bookings already in the diary are listed for you so you can contact those customers.
  • See and reopen closed days in one place. Upcoming closed days are listed in the same box, each with a Remove button that reopens the day.
  • Clear messages if a day cannot be closed. If the day is already closed, or someone has their own hours that day that would keep them bookable, the admin says so and tells you where to change it.
  • Your assistant can now see everyone’s working hours. Asked when you are open, it reads each person’s weekly hours instead of guessing from the free slots.
  • Close the whole business for a day. Your AI assistant can now mark a day when the whole business is closed, rather than giving each member of staff the day off one by one. Nobody can be booked that day, and bookings already in the diary are listed for you.
  • See and remove closed days in the admin. A closed day shows under every member of staff’s Availability, labelled “Whole business closed”, with a Remove button.
  • One less question on a one-person business. When there is only one member of staff, your assistant no longer has to say who a change of hours is for.
  • Booking lists read more naturally. Your assistant can ask for bookings “from” and “to” a date, the same words the calendar uses.
  • Video links last until the appointment. With EP Video, a booking made from the admin or by your AI assistant could get a call link that stopped working about a day after it was made. Those links now last until two hours after the appointment ends, and links already made are put right automatically.
  • Your webhook hears about every booking. “Booking created” and “Booking confirmed” were only sent for bookings made through your booking form. They are now also sent for bookings you add in the admin, bookings your AI assistant makes, and bookings you approve with Confirm.
  • Reminders now go out for bookings your AI assistant makes. A booking made through your assistant was saved without the exact time reminders work from, so it got no reminder until someone next opened the admin. Bookings are now saved complete straight away, and any your assistant made before this update are completed the next time reminders run.
  • Run your diary from Claude or any AI assistant. EP Booking now has its own actions in your site’s API and MCP. An assistant connected to your site can tell you who is booked today, check which times are free, find a customer and their bookings, book someone in, confirm or cancel a booking, add a private note, give a member of staff a day off or different hours for a day, and switch a service on or off. Administrators only.
  • It checks the diary before booking. A booking made by your assistant goes into a free time only, unless you tell it to fit someone in anyway.
  • Nothing reaches a customer without your say-so. Confirming, cancelling and refunding each refuse until the assistant confirms with you. Before cancelling it tells you if the customer would also be refunded automatically. A booking it makes emails the customer only if you ask for that.
  • Days off are reported, not hidden. Giving someone a day off, or shorter hours, never cancels bookings already there: you are told which ones to deal with.
  • Needs PageMotor 0.11.5.
  • Deleting a customer now removes their video calls. Deleting a customer (which deletes all their bookings) now also removes each booking’s Zoom meeting or EP Video call, as deleting a single booking already did. Before, their Zoom meetings stayed in your Zoom account.
  • Confirmation emails are on by default. Customers now get a confirmation email when their booking is confirmed, without you having to find and tick the setting first. You can still turn it off in Settings > Notifications. If you already saved your settings with confirmations turned off, they stay off.
  • Video calls with EP Video. If EP Video is active and set up, each confirmed booking now gets its own private video call on your own site, instead of a Zoom meeting. The link goes in the confirmation, reminder and rescheduled emails, the calendar invite and the customer’s bookings; you join from “Join as host” in your bookings list.
  • Choose per service. Each service has a new “Video call” tick. It is on for new services, so turn it off for anything that happens in person. Your existing services start with it on.
  • New “Video calls” settings. Pick Automatic (EP Video first, then Zoom), EP Video, Zoom or None. The section says which one your bookings will use. Zoom users with no EP Video carry on exactly as before.
  • New email placeholders {video_url} and {video_host_url}. The old {zoom_url} and {zoom_host_url} still work and now carry whichever call your booking has.
  • Fixed: the approval email went out before the meeting was made. A booking approved by hand now creates the call first, so the confirmation carries the link. A booking you add yourself as confirmed now gets a link too.
  • Security: tightens how booking payments are confirmed. Nothing changes for customers.
  • The booking form now loads only the staff details it needs to show.
  • Customer notes now reach the “New Booking” emails sent to you and to the staff member. The templates were looking at the wrong field, so the notes a customer typed never appeared.
  • Security: tightens the protection on the booking form and embed widget. If you have EP Booking’s settings open in another tab, reload it before saving.
  • The embed widget on other websites keeps working: it uses a signed token that does not depend on cookies, so bookings go through even in browsers that block cookies inside embedded frames.
  • Monthly and yearly events in a linked calendar now block every date. When a staff member’s busy calendar address (Google, Outlook or Apple) had a monthly meeting or a yearly event, only its first date blocked booking slots; every later one was left open to be booked. Every occurrence now blocks, including “the second Tuesday”, “the last Friday”, Outlook’s “last weekday of the month” and yearly dates, and dates removed in the source calendar stay open.
  • Weekly and daily events block exactly as before.
  • Block a staff member’s slots with EP Calendar. When EP Calendar is active, each staff member has a new choice, “Block with EP Calendar entries of”. Pick a site user and every entry that user makes in EP Calendar makes those times unbookable for this staff member, on your booking form and when customers reschedule, straight away: no calendar address to copy and no five-minute wait. External feeds in EP Calendar set to block booking slots for that user count too. Leave it on Off and nothing changes.
  • The staff table shows “Blocked by the calendar of …” under the name of each linked staff member.
  • All-day calendar entries follow your existing All-day calendar events setting under Booking Rules, which is off by default. Cancelled entries never block. A staff member’s busy calendar address keeps working alongside the link, and both apply.
  • If EP Calendar is switched off or cannot answer, bookings carry on exactly as before.
  • A repeating appointment in a linked calendar keeps its time after the clocks change. When a staff member’s linked calendar (Google, Outlook or Apple) had a weekly or daily event, every repeat after a clock change was placed one hour out. From 25 October a 9 o’clock weekly commitment blocked 8 to 9 instead of 9 to 10, so a customer could book on top of the real appointment. Repeats now keep their local time all year, in the time zone the calendar event was written in.
  • A repeat that was deleted from the calendar after a clock change is now left open as it should be. Before, that deletion was missed in the same way.
  • Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
  • Danish. Adds a Danish translation.
  • A refund that fails in Stripe no longer leaves the booking marked refunded. Stripe can fail a refund days later (for example when the customer’s card has been closed), or cancel one that was still pending. The money then stays with you, but the booking still said “Refunded”. Now the payment goes back to “Paid”, or to the smaller amount that is still refunded, and a note on the booking says what happened. If the customer should still get their money back, refund them again.
  • The booking itself (confirmed, cancelled and so on) is not changed, just as when you make a refund.
  • One step for you: in your Stripe Dashboard, add the event charge.refund.updated to the webhook you set up for EP Booking, so that failed refunds reach your site. The Stripe settings page now lists it with the other events.
  • Manual bookings you add in the admin check the phone number too. The check that a phone number looks like one only ran on the public booking form, so “123” typed into Manual Booking was still accepted. The same rule now applies there, with the same message.
  • The embed code is ready to paste for each service. Public Pages & Embed used to show one embed line with SERVICE-SLUG in it, to be replaced by a slug you had to work out yourself. It now lists every service with its booking page link and its own embed code, with the right slug already filled in. Copy the one you want onto the other website.
  • A returning customer’s new phone number is kept. When someone who had booked before booked again with a different phone number, the new number was quietly ignored and their bookings kept showing the old one, so you could end up ringing a number they no longer use. The latest number they give now replaces the one on file. This applies to bookings from your booking form and to bookings you add by hand in the admin.
  • The same number written differently (with or without spaces, for example) leaves the stored one as it is, and a number that doesn’t look like a phone number is still refused. The customer’s name on file is not changed.
  • With EP Connect 1.1.2, EP Connect decides for itself when a booking is confirmed. EP Booking no longer adjusts EP Connect’s internal settings to stop unpaid bookings being announced. Nothing changes that you can see. With an older EP Connect it works as in 2.4.41.
  • Manual bookings you add in the admin check the phone number too. The check that a phone number looks like one only ran on the public booking form, so “123” typed into Manual Booking was still accepted. The same rule now applies there, with the same message.
  • The embed code is ready to paste for each service. Public Pages & Embed used to show one embed line with SERVICE-SLUG in it, to be replaced by a slug you had to work out yourself. It now lists every service with its booking page link and its own embed code, with the right slug already filled in. Copy the one you want onto the other website.
  • A returning customer’s new phone number is kept. When someone who had booked before booked again with a different phone number, the new number was quietly ignored and their bookings kept showing the old one, so you could end up ringing a number they no longer use. The latest number they give now replaces the one on file. This applies to bookings from your booking form and to bookings you add by hand in the admin.
  • The same number written differently (with or without spaces, for example) leaves the stored one as it is, and a number that doesn’t look like a phone number is still refused. The customer’s name on file is not changed.
  • The summary cards at the top of the settings page now open their section. Services, Staff, Bookings and Payments looked like panels you could open, and on a phone it was natural to try, but they did nothing. Each card now opens its own section and scrolls to it, and shows a small “Open” so it is clear they can be tapped.
  • The booking form checks that a phone number looks like one. A number such as “123” used to be accepted. The form now asks for a full number, 7 to 15 digits, and allows the usual extras: a leading +, spaces, dashes, dots and brackets, so “+44 (0)1234 567-890” is fine. The same check runs on your site as well as in the customer’s browser, and it applies whenever a phone number is entered, whether or not you require one.
  • The Bookings list can be scrolled sideways on a phone. On a narrow screen the list was cut off after the Date column, so Status, Payment and the View button that leads to Confirm could not be reached at all. The list now scrolls sideways, and keeps a readable width instead of squeezing each date onto three lines. The other admin lists (Customers, Services, Staff, Categories) get the same treatment.
  • Confirmation emails tell the customer what the appointment involves. If you have written a description for a service (the text shown under it on the booking form), the confirmation now includes it under “About your appointment”. Services without a description are unchanged.
  • If you write your own confirmation message, the new {service_description} placeholder adds the same text wherever you put it.
  • Booking invites now say who they are from. The calendar invite in booking emails had no organiser. Apple Mail, Gmail and Outlook showed it properly anyway, but Thunderbird prints ”… has invited you” and left the name blank. The invite now names your business as the organiser, using the address your booking emails are sent from, and lists the customer as attending.
  • The name shown is your business name from the General settings. If you have not set one, your EP Email sender name is used, and failing that your site title.
  • The customer is marked as already accepted, with no reply requested, so their calendar does not send “Accepted” messages back to you.
  • If a booking is made with the same email address your booking emails are sent from (for example when you book yourself to test), the invite is left exactly as before, because an invitation from yourself to yourself confuses calendar apps. To see the new line, test with a different address.
  • Stripe booking payment notifications keep working while you change your webhook signing secret.
  • Fixes Stripe card payments and Stripe notifications failing after your Stripe keys started being stored securely. Paid bookings, refund and cancellation updates from Stripe, and card checkout on the booking form work again.
  • Booking emails sent through EP Email now carry a calendar invite you can add. The invite was being built, but it was handed to EP Email in a form it did not read, so it arrived as an empty file, or not at all, and there was no “add to calendar”. It now arrives as a proper calendar invite on sites that send through SMTP or the server’s own mail. Sites sending through Mailgun, Brevo, SendGrid or the ElmsPark relay still do not get the attachment, because those senders do not pass attachments on yet; that needs a change to EP Email’s senders.
  • A booking email that fails to send is no longer reported as sent. When EP Email turned an email down, for example for a missing sender address, the cancel and reschedule pages still said a confirmation email had been sent. They now only say so when it was, and the reason goes to the error log.
  • “Contact us directly” now says how. When a customer tries to cancel or reschedule after the window has closed, the message now shows your business phone number as a tap-to-call link, if one is set under General. The same goes for the message shown when self-serve rescheduling is switched off.
  • A signing secret or Stripe key that could not be read after a PageMotor update is now recovered. If it cannot be recovered, you are asked to enter it again.
  • If the cancel or reschedule email fails with an error, the customer still sees the confirmation page. An error at that point could leave them on the home page with no message, even though the change had been saved. The cause is now written to the error log.
  • The webhook and Stripe settings now tell your browser not to fill in your login details. Each secret in these settings is a password box with an ordinary text box above it, which browsers mistake for a login form. So they filled in the username and password saved for your site: your username ended up in Webhook URL, and your site password in Signing Secret, ready to be saved as a secret. The boxes now tell browsers they are not a login form, which is the standard signal for browsers to leave them alone.
  • If Webhook URL or a Stripe key box shows your username, clear it before saving. If you saved it like that, nothing was sent: the plugin only sends to an address starting with http.
  • No change to how bookings, payments or webhooks work.
  • The admin Calendar no longer closes when you move to the next or previous month. Next and Prev reload the settings page at the new month, and PageMotor opens every settings section closed after a reload, so the Calendar snapped shut each time and had to be opened again to see the month you had just asked for. It now reopens itself and scrolls into view after a month change.
  • No change to what the Calendar shows or to how bookings work.
  • A staff member’s busy calendar address no longer looks empty after the page is reloaded, and no longer gets wiped by an unrelated save. The address was saved correctly, but when the Staff page was first opened, the list of staff did not carry it, so pressing Edit showed an empty box. Saving that staff member again, for example to change a phone number, then saved the empty box and removed the calendar. The Edit form now always shows the saved address.
  • If a staff member’s calendar seems to have disappeared, paste the address back in once and press Save.
  • No change to how bookings are checked against the calendar.
  • “Test this calendar” now says so when the server was slow to look up the calendar’s address. When a hosting server took too long to look up an address such as calendar.google.com, the test said the server was “being blocked from fetching it”, which sent people looking for a block that was not there. It now says the lookup was slow, that the address itself is fine, and to test again in a moment. It also says that bookings keep using the last copy of the calendar while a slowdown lasts.
  • A lookup that fails outright gets its own message too: check the address was copied in full, and if it opens in your browser, the server’s address lookup is failing, which is a hosting matter.
  • No change to how bookings are checked against the calendar.
  • “Test this calendar” now tells you when the address is not saved yet. Testing an address checks it but does not store it; only Save does. Nothing on screen said so, so an address could be pasted in, tested, and then lost on the next refresh. When the address in the box is not the one you last saved, the test result now ends with “This address is not saved yet. Press Save to keep it.”
  • Opening a staff member to edit, or starting a new one, now clears the previous test result, so it cannot be mistaken for a result about this person.
  • No change to how bookings are checked against the calendar.
  • “Test this calendar” now says clearly what it counted. A successful test used to report something like “266 event(s), 0 of them in the next 30 days”, which looked broken on a calendar full of upcoming birthdays and holidays. It now says how many busy periods will block this person’s booking slots in the next 30 days, and whether all-day entries were counted. By default they are not, because all-day entries such as birthdays and holidays never block slots unless you turn on All-day calendar events under Booking Rules.
  • The test now follows that All-day calendar events setting. On a site with it turned on, all-day entries used to be left out of the count even though they did block slots.
  • The count now comes from the calendar the test has just fetched, so an event you have just added is counted as soon as your calendar provider publishes it. It no longer waits up to five minutes for a saved copy to expire, and the test fetches the calendar only once.
  • No change to how bookings are checked against the calendar.
  • The “Test this calendar” button no longer tells you to reset a calendar address that is working. When Google, Outlook or Apple was limiting requests from your server (a 429 reply), the test told you the secret address had probably been reset and asked you to paste a new one. Resetting would not help, and it breaks the old address everywhere else you use it. A 429 now says the provider is limiting this server for a while, that the address itself is fine, and to test again later.
  • A reply showing the provider is having trouble at its end (500 and above) now says so too, instead of blaming the address.
  • No change to how bookings are checked against the calendar: while a feed cannot be fetched, the last copy is still used.
  • Fixes a doubled cache-busting tag on its booking-form stylesheet and scripts. On PageMotor 0.11 and later the page asked for each file with two version tags on the end of its address (?v=…?v=…), because the core had started adding its own tag and the plugin was still adding one too. The files loaded correctly, so nothing was visibly broken; the addresses were just malformed and every cache saw a longer key than it needed. The plugin now leaves the tag to the core on 0.11 and later, and still adds its own on older cores, where nothing else would.
  • No change to what these files do.
  • Fixes a crash on the booking form when an older EP plugin is installed on the same site. Submitting the form returned an internal error and nothing was saved or sent. EP plugins share one common code library, and whichever copy loads first is the one every EP plugin on that site uses, so a single out-of-date plugin could leave this one calling a spam check its copy did not have. The check now carries its own fallback and no longer depends on another plugin being up to date.
  • No change on a site where this never happened: the same spam check runs, and nothing else changed.
  • Fixes stored keys and passwords appearing blank after updating to PageMotor 0.11.3 or 0.11.4. Existing values are restored automatically, with nothing to re-enter.
  • If you updated PageMotor and then re-entered a key or password, there is nothing to do. If you updated and have not re-entered it, this release restores it on the next page load.
  • Fixed: installing a second plugin that also takes Stripe payments could take the whole site down. Five plugins in the suite share the same Stripe helper. With any two of them switched on, the second to load failed outright and PageMotor disabled it to protect the site, so turning on a new Stripe-capable plugin silently cost you the one you already had, with nothing obvious to explain it.
  • The guard meant to prevent that had never been able to work, for reasons of when the code is read rather than when it runs. It is now written so that it does. Verified by switching two of these plugins on together: previously the site returned an error and one plugin was disabled, now both load cleanly and payment signature checking still works.