A chatbot that reads your Amelia schedule

Amelia stores appointments in wp_amelia_appointments with per-customer rows in wp_amelia_customer_bookings, services in wp_amelia_services, employees in wp_amelia_employees, and locations in wp_amelia_locations. Service prices, durations, and capacity all sit on the services table, while customer information lives in wp_amelia_users.

That gives admins a real conversational layer over the Amelia calendar. A clinic manager asks how many consultations are booked tomorrow, the bot returns counts per employee and per service. An owner asks which employee is most booked this week, the bot reads customer_bookings and returns ranked totals. A receptionist asks for tomorrow's first appointment, the bot pulls the customer name from wp_amelia_users in one query.

Multibot lets a separate public bot run on the booking page with access only to wp_amelia_services for availability and pricing, no access to customer rows. Display conditions lock the admin bot to staff roles. Conversation logging records every prompt and answer inside WordPress for accuracy audits as the schedule grows.

Workflow

How SleekAI plugs into Amelia Booking

1

Map Amelia tables

Wire wp_amelia_appointments, customer_bookings, services, employees, locations, and users into SleekAI data sources so the bot can read schedule, staff, customer, and pricing rows from one place.

2

Scope to clinic staff

Use display conditions on user role so only administrators or a chosen staff role see the admin booking bot. Public visitors get a separate availability bot with no access to customer rows under multibot.

3

Expose Amelia lookups

Add helpers for appointments per day, bookings per employee, revenue per service over a date range, and customer search by name or email, so the model has clean primitives for schedule reasoning.

4

Audit and refine

Read the SleekAI conversation log, learn which schedule questions recur during the day, and turn them into pinned presets the front desk can tap each morning instead of retyping the same prompts.

Try it now

A typical Amelia Booking conversation

A clinic manager in WP Admin checking the day ahead and which doctor is most booked, with customer name and appointment status surfaced from the Amelia tables.

Comparison

Generic chatbot vs SleekAI for Amelia Booking

Generic chatbot

Cannot read your wp_amelia_appointments or customer_bookings rows
Has no idea which employees and services your business runs
Treats every schedule question as generic FAQ text
Will not filter appointments by employee, service, or date
Cannot return real booking counts or revenue totals

SleekAI chatbot

Reads wp_amelia_appointments, services, employees, and customers
Counts bookings by employee, service, location, or date range
Returns service revenue totals from real booking rows
Display conditions for staff-role-only admin bot access
Logs every conversation and token count inside WordPress

Features

What SleekAI gives you for Amelia Booking

Appointment-aware

The bot reads wp_amelia_appointments with service id, employee id, location id, and status, so it can answer real schedule questions instead of generic copy from your services landing page.

Employee workload

Each booking in customer_bookings ties to an employee in wp_amelia_employees. The bot can rank workload, count finished appointments, and flag which staff member needs more slots opened next week.

Service revenue

Service prices live on wp_amelia_services with optional extras and durations. The bot multiplies completed bookings against the configured price to return real revenue per service over any date range.

Use cases

Where Amelia Booking teams use this

Daily morning check

Pull the day's appointments grouped by employee and service in one question instead of scrolling the Amelia calendar grid one column at a time before the clinic opens for first appointments.

Service revenue audits

Ask which service or package generated the most revenue this month, with the bot reading wp_amelia_appointments status approved or completed and totaling against the configured wp_amelia_services price.

Customer lookups

Ask for upcoming appointments for a customer by email or name, and the bot joins wp_amelia_users to wp_amelia_customer_bookings to surface the schedule from inside WP Admin chat in seconds.

The bigger picture

Why chat over Amelia changes clinic ops

Amelia is great for visual schedule management, but every analytical question costs a click trail. How many appointments tomorrow, which doctor is overbooked, what did consultations bring in this month, those exist as data and live nowhere convenient on the standard reports screen. A plain-English layer over the same wp_amelia_appointments and customer_bookings rows collapses that loop.

A clinic manager can ask the question on a phone between rounds and get a real number, not an estimate, because the model reads the same rows the calendar reads. For receptionists the win compounds. A walk-in asks for the next slot with a specific doctor, instead of paging through the calendar the front desk asks the bot.

A regular calls to reschedule, the receptionist asks for upcoming appointments by name and gets the result in one line. The data was always there, the bottleneck was the interface. SleekAI keeps that interface in WordPress, scoped to the right role, with every conversation logged for audit and refinement as the schedule grows quarter over quarter.

Questions

Common questions about SleekAI for Amelia Booking

Yes. Amelia stores appointments, customer bookings, services, employees, and locations in dedicated wp_amelia_ tables. SleekAI can be configured to read all of those via the data source wizard, so the bot reasons over real rows instead of generic copy from the booking page or a static FAQ document.

Only if you configure it that way. Display conditions can lock the admin booking bot to administrators or a staff role. A separate public bot can run on the booking page with read access limited to wp_amelia_services availability, never to customer rows. PII stays inside the admin side, scoped to roles.

Yes. Each appointment ties to an employee id on wp_amelia_employees. The bot can group bookings by employee over any date range, count completed appointments, and surface which employee is fully booked or under-utilised over the week ahead without manual filtering in the calendar grid.

Push older appointments into an OpenAI Files vector store and let retrieval pull only the relevant slice on demand. Recent and upcoming appointments stay live in the data source so calendar queries feel real-time, while years of history sit in retrieval for trend questions and seasonality.

Yes. Free Amelia creates the same core wp_amelia_ tables, so the bot can read appointments, services, employees, and locations. Pro features like events, packages, and taxes add extra columns and dedicated tables that SleekAI can read once you enable them on the install.

Yes. Amelia events live in wp_amelia_events with bookings in wp_amelia_customer_bookings, and packages tie multiple service appointments together with a wp_amelia_packages row. The bot can answer how many spots are left in an event or how many sessions remain in a customer's package.

Yes, when you enable the write helpers. SleekAI exposes tools that map onto Amelia booking actions, so the admin bot can book or cancel on confirmed instruction from a staff user. The default install keeps read-only behaviour to avoid accidental schedule changes from chat input.

Bring your own API key for OpenAI, Anthropic, Google, or OpenRouter. Each chatbot can pick a different model, so a public availability bot can run on a small model while the admin schedule and revenue bot uses a stronger reasoning model for the harder Amelia reporting questions.

Other chatbots SleekAI builds well

AI chatbot for LiveChat on WordPress: deflect the easy chats, route the rest

LiveChat is built for human agents. SleekAI takes the first turn from your WordPress content, then hands the conversation back to LiveCha...

AI chatbot for Squirrly SEO: on-page guidance from your own data

SleekAI maps Squirrly's _sq_post_keyword, _sq_seo_title, and _sq_seo_description postmeta plus the qss_seo and qss_journey tables into th...

AI chatbot for Gravity Forms User Registration: explain signups & roles

SleekAI's chatbot reads your registration feeds from gf_addon_feed, resulting users from wp_users, and mapped profile values from wp_user...

AI chatbot for Dokan Store Support: per-vendor ticket triage

SleekAI's chatbot reads Dokan Store Support tickets, vendor IDs, ticket status, and the related order from your WordPress database so cus...

AI chatbot for LifterLMS Mailchimp: list-aware course Q&A

SleekAI's chatbot reads LifterLMS course progress and the Mailchimp list and group mappings stored in postmeta, so replies stay consisten...

AI chatbot for Bookly Google Calendar Sync

SleekAI reads live data from wp_bookly_appointments, wp_bookly_staff, and the Google Calendar Sync columns, so ...

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

Get started

3 websites
1 year of updates
1 year of support

Pro

€149

EUR

per year

Get started

Unlimited websites
1 year of updates
1 year of support

Lifetime ♾️

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

SleekAI
SleekByte
SleekMotion
SleekPixel
SleekRank
SleekView

€749

Continue to checkout

Browse more

Plugin Integration

Content Types

Meta Ai

Industry Health

AI chatbot for Amelia Booking: query appointments in chat

A chatbot that reads your Amelia schedule