SleekView Charts for Amelia
Amelia spreads appointments, customers, employees, services, and payments across separate custom tables. SleekView Charts joins them once and renders dashboards for reception, finance, and managers.
♾️ Lifetime License available
From Amelia's tables to a single dashboard
Amelia stores rich operational data across wp_amelia_appointments, wp_amelia_customer_bookings, wp_amelia_users, wp_amelia_services, and wp_amelia_payments. The plugin's own dashboard widgets show useful slices, but they're fixed in shape and don't let a manager combine, for example, employee utilisation with a payment-method breakdown for the same date range.
SleekView Charts treats those tables as one joined dataset and renders configurable chart cards on top. The reception dashboard surfaces today's approved versus pending counts. The owner dashboard tracks revenue by service category and by employee. The finance dashboard reconciles Stripe versus PayPal totals against appointment status. The data path is the same path the table view uses, so every chart change is reflected in the corresponding row list.
Cards aggregate at the database level using Amelia's existing indexes, and writes (when a card links into an inline-edit flow) route through the Amelia API so notifications and gateway calls behave exactly as they do from the plugin's own admin.
Workflow
Join Amelia tables into one chart dataset
Source from appointments
wp_amelia_appointments as the dataset base. Each row is one appointment with foreign keys for customer, employee, service, and payment.
Join customers, services, payments
wp_amelia_users (customers and employees), wp_amelia_services, and wp_amelia_payments onto the dataset. Status, gateway, and price land alongside the booking time.
Configure four cards
Pin per-role dashboards
Sample dashboard
Charts you can build from Amelia data
Upcoming appointments
Count
Appointment status mix
Count
group by status
Revenue by employee
Sum(price)
group by employee_id
Appointments per day
Count
group by bookingStart
Comparison
Default Amelia reporting vs SleekView Charts
Default Amelia dashboard widgets
- Amelia's dashboard widgets are fixed in shape and not user-configurable
- Cross-table charts (revenue by employee and by service together) require exports
- No per-role saved dashboards (reception, owner, finance)
- Filtering applies per widget rather than to a full dashboard at once
- Payment-method breakdowns aren't exposed as their own chart
SleekView Charts
- Configurable chart cards over wp_amelia_appointments and joined tables
- Saved dashboards per role: reception, owner, finance
- Dashboard-level date and employee filters cascade to every card
- Mix Number, Bar, Donut, and Area cards in one workspace
- Charts share the dataset with SleekView's table view for click-through
Features
What SleekView Charts gives you for Amelia
Configurable cards, not fixed widgets
Pick the dimension, the metric, and the chart type per card. Build a revenue-by-employee bar one week and switch it to a revenue-by-service-category donut the next, without touching code.
Amelia tables joined once
Appointments, customers, employees, services, and payments are joined into a single SleekView dataset. Every card reads from the same join, so groupings stay consistent across the dashboard.
Per-role dashboards
Save a dashboard per role with capability gating. Each user opens the dashboard that matches their job, not a generic widget grid.
Audience
Who builds Amelia charts dashboards with SleekView
Reception
Pending and approved counts for today, no-show rate over the week, and the busiest hours visible at a glance before doors open.
Studio owners
Revenue by employee, service mix, and month-over-month trend on one screen. The numbers that drive the monthly review live in the dashboard, not a spreadsheet.
Finance
Payment-method totals, refund counts, and outstanding deposit balances filtered by date range. Reconciliation runs from a saved dashboard each month-end.
The bigger picture
Why a configurable dashboard beats fixed widgets
Amelia's built-in dashboard is helpful for a glance and limiting for a serious review. The widgets are fixed in shape, the slices are pre-chosen, and a manager who wants to ask a slightly different question has to export and pivot. The questions Amelia operators actually ask are not radical: which employees drive revenue, which services book most reliably, what share of bookings are still pending the day of service, which payment method dominates this month.
Each one is one chart against one dataset, and the dataset already exists inside Amelia's own tables. SleekView Charts gives that dataset a configurable rendering layer, with a card grammar that maps cleanly to the operational questions: Number for the KPI, Donut for the share, Bar for the ranking, Area for the trend. The dashboard becomes the place reception, owners, and finance each meet their data, on their terms, without exports.
Questions
Common questions about SleekView Charts for Amelia
No. Amelia's dashboard widgets stay where they are. SleekView Charts sits alongside as a configurable layer. Some teams keep both; others use the Amelia dashboard for at-a-glance health and SleekView dashboards for the deeper, role-specific review.
Yes. Amelia events live in wp_amelia_events with bookings against them, and packages live in their own tables with redemption history. Each becomes a separate dataset, so you can build a dashboard mixing appointments, events, and package-driven revenue.
Dashboard-level filters (date range, employee, service category) cascade to every card. Per-card filters override the dashboard filter for that card only, which is useful for an all-time KPI card sitting next to date-scoped trend cards.
Yes. Card data is scoped to what the viewing role is allowed to see. If an employee role is gated to their own bookings, the per-employee revenue bar shows only their own slice, not the team's.
Yes. Use a Pie or Donut grouped by payment status from wp_amelia_payments, joined onto the appointment dataset. Useful for spotting unpaid deposits before service, especially during peak booking periods.
Yes. Package and gift-card redemptions sit in their own Amelia tables. Build dedicated cards for redemption volume, balance remaining, and expired packages so finance and ops both see the picture without a separate report.
Cards query the live Amelia tables on render. A status change made in the table view or in Amelia's own admin appears in the chart on the next reload, with no separate sync.
Yes. Aggregations run server-side using the indexes Amelia already creates on its tables. A multi-employee, multi-service install with years of history renders the dashboard in well under a second.
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.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
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