Schedopia – Appointment Booking, Events & Seat Reservations

Yes. Schedopia is a complete, self-hosted booking plugin for appointments and event seat reservations, with no per-booking fees or seat commissions.

Yes, Schedopia Pro is coming soon as a separate add-on. It brings online payments, two-way calendar sync, and more flexible booking options for your customers. All existing Schedopia features will remain completely free and fully functional, and nothing in the free plugin is locked or limited. Join the waitlist for early access.

Any service business that runs on appointments, such as salons, barbershops, spas, clinics, dentists, therapists, coaches, tutors, consultants, and home or repair services. It also suits businesses that sell seats for dated sessions, such as yoga and fitness studios, workshops and classes, community centres, small theatres and event spaces. You can run either kind of booking, or both.

Yes. Add the [schedopia_booking] form to any page and customers can pick a service, choose a staff member, and book an available time on their own, 24/7. For events, they browse upcoming sessions, pick their seats on the seat map, and reserve them the same way.

Yes. The [schedopia_services] shortcode lists your bookable services as cards with their price, duration and description. Each card's Book button opens the booking form with that service already selected. Book opens your booking page, which you can choose or create under Settings → Shortcode, unless the list is on a page that already has the booking form. If you haven't chosen one, Schedopia uses a page that already holds the booking form. Use category="hair" to list a single category, or category="hair,nails" for several. Each category's name for the shortcode is shown next to it under Schedopia → Categories. Use services="haircut,facial" to list exactly those services in that order, or booking_page="book" to send one list to a different page. In the block editor and Elementor, the Services List block and widget offer the same choices from a menu. All shortcode options are in add it to your site.

Yes. The [schedopia_events] shortcode lists your upcoming events as cards with the date, venue, seats left and the "from" price. Each card's Select seats button opens the booking form on that event's seat map. Sold-out events stay listed as "Fully booked"; add hide_sold_out="yes" to leave them out. Use venue="main-hall" to list a single venue, or events="summer-gala,jazz-night" to list exactly those events in that order. There is also a Events List block and Elementor widget with the same choices. The buttons open your booking page, or a separate Events page you can choose under Settings → Shortcode.

Yes. [schedopia_categories], [schedopia_staff] and [schedopia_venues] show them as cards, and each has a block and an Elementor widget. A category card opens the booking form with only that category's services. A staff card opens it with only that person's services and picks them for the visitor. A venue card opens the seat flow with only that venue's events. Use categories="hair,nails", staff="3,5" or venues="main-hall" to show only some, in that order.

Yes. [schedopia_booking services="haircut,facial"] offers only those services, category="hair" one category's, and staff="3" one team member's (picked for the visitor). On the events side, use events="opening-night" or venue="main-hall". When a visitor arrives from a list card, their choice wins for that visit.

Yes. Create a venue with one or more halls, lay out the seats in the visual seat planner (optionally grouped into tiers such as VIP, Standard and Balcony with their own prices), then create a dated event in that venue. Customers see live seat availability and a "from" price, pick specific seats on the map, and book. Use [schedopia_booking mode="event"] to place the seat flow on its own page.

Yes. Every appointment is validated against real staff availability, and every seat reservation against the seats already taken, inside a transactional double-booking guard. Two customers can never take the same time slot, and a seat can never be reserved twice for the same event.

Schedopia records manual and offline payments: cash, bank transfer, and mark-as-paid. See payments.

MCP (Model Context Protocol) is the standard that lets an AI assistant use tools outside itself. Schedopia has an MCP server built in, so any MCP-capable assistant, such as Claude, ChatGPT, Cursor, Claude Code or Codex, can read and, where you allow it, change your bookings. There is nothing to install besides Schedopia and no separate server to run.

Schedopia does not run an AI model and never contacts an AI service on its own. It is the other way round: you connect the assistant you already use, and it asks your site questions over HTTPS. What the assistant reads in an answer is seen by that assistant's provider, which is the client you chose and approved. Nothing is sent anywhere else, and the Permissions tab decides what it can read at all.

Yes. Settings → Connect your AI publishes Schedopia's admin actions as tools that an MCP client can use. Claude Code, Cursor, Codex, Claude Desktop, claude.ai and ChatGPT all support MCP. The feature is off by default. When you switch it on, reading is allowed, and every tool that changes or deletes something stays off until you turn it on yourself. The assistant acts as the WordPress account that connected it, so it can never do more than that account can, and every call is recorded in the activity log. Connect your AI requires WordPress 6.9 or newer, where the Abilities API is available; everything else in Schedopia works from 6.5. Step-by-step: set it up, and the full tool list under what it can do.

Yes. The services and events lists have their own Gutenberg blocks and Elementor widgets, where you choose what they show without typing a shortcode. The [schedopia_booking] form works in any editor through the Gutenberg shortcode block or the Elementor Shortcode widget. Only one booking form can appear per page; a services or events list can sit alongside it.

Not unless you ask it to. Out of the box Schedopia contacts no external service and loads nothing from third-party CDNs, so your business data stays on your own site. There is one opt-in exception: if you switch on reCAPTCHA spam protection and supply your own keys, the booking form then loads Google's script and checks submissions with Google (see the External Services section below). The only other third-party links are the optional "add to calendar" buttons in customer emails. They are ordinary links your customer may click to save their appointment in Google or Outlook. Connect your AI is inbound only. It is off by default, and when you switch it on, an AI client you sign in and approve connects to your site. The plugin never contacts any AI service itself.

Custom tables (wp_schedopia_*). Bookings, services, staff, customers, payments, venues, seats, and events are stored relationally rather than as posts.

Through documented lifecycle hooks, filters, and driver interfaces (BookingSource, NotificationChannel, PaymentMethod). Every booking flows through one validated path, so an extension can never create a booking the core would reject. A full REST API is available under /wp-json/schedopia/v1/. On WordPress 6.9 or newer the same actions are also registered with the Abilities API, and Settings → Connect your AI can expose them to an AI assistant you approve, over the plugin's own MCP endpoint. Developer docs: schedopia.com/docs.

Uninstall keeps your business data by default. It is deleted only if you explicitly opt in.