Amelia

Amelia is a WordPress appointment and event booking plugin for service businesses that need more than a single contact form. It brings customer scheduling, payment collection, reminders, staff calendars and operational reporting into one booking system. The feature set is aimed at organisations such as healthcare providers, beauty businesses and education services, where appointments, cancellations and repeat visits all need consistent handling.

Booking workflow

The customer-facing booking interface is the centre of Amelia. Visitors can choose from the services offered by a business and submit the information requested through a custom booking form. That form is useful when an appointment requires more than a name and email address: the business can collect the client details it considers essential as part of the scheduling process.

Service and staff management gives the booking process a structure suited to larger operations. Instead of treating every appointment as an isolated entry, Amelia supports multiple services and multiple staff members. That distinction matters for a clinic with several practitioners, a salon with different treatments, or an education provider offering several appointment types.

Payments and reminders

Amelia includes connections to popular payment gateways, so businesses can take payment as part of the booking flow rather than handling every transaction separately. The listing does not identify the individual gateways, so the exact payment options should be checked against the business’s preferred provider before committing to the setup.

Automated email and SMS notifications address the practical work that follows a booking. Clients can receive appointment reminders, while the business has a defined communication layer around scheduled visits. Support for recurring appointments also suits regular clients who return on a repeated schedule, rather than requiring staff to recreate each visit manually.

Calendar and reporting

Google Calendar synchronisation keeps appointment information aligned with a calendar that staff may already use for day-to-day planning. It is a useful bridge between the booking system and personal or team scheduling, particularly when several staff members need visibility of their commitments.

The reporting tools cover appointments, cancellations and revenue. Those categories give an operator a way to review both activity and its financial outcome. The reporting emphasis is operational rather than purely presentational: a manager can look at booking volume, lost appointments and income when assessing how the service is performing.

What to weigh

Amelia’s breadth is also its main cost. A business booking appointments across several services and staff members has more schedules, form fields, payment settings, reminders and calendar relationships to organise than a business using a simple enquiry form. The plugin is therefore a poor fit for a site that only needs visitors to send a message or request a callback.

The payment and messaging features introduce outside dependencies that need planning. Gateway connections must match the business’s payment arrangements, while email and SMS reminders require the relevant communication setup to be maintained. Google Calendar synchronisation adds another calendar layer to keep aligned. These are useful parts of a serious booking workflow, but they also create more configuration points than a basic appointment form.

The vendor copy also leaves some implementation detail open. It names popular payment gateways and describes advanced reporting, but does not specify the gateways, report formats or depth of the available metrics. Businesses with strict payment, compliance or management-reporting requirements should confirm those details before building their process around the plugin.

Who it suits

Amelia fits service businesses that need a structured appointment operation rather than a lone booking field. Its strongest case is a multi-staff organisation offering several services, accepting payments, reminding clients, handling recurring visits and reviewing cancellations or revenue. A smaller operator with occasional appointments may find that breadth unnecessary, while a growing team has more reason to use the staff, calendar and reporting features together.