✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Bookly Pro Addons

SleekView reads the Bookly customer appointments table, groups each row by its status, and shows the customer, service, staff, and time on the card face. Drag a Pending card into Approved to update the Bookly row and run the same notification chain the back office triggers.

♾️ Lifetime License available

SleekView Kanban board for Bookly Pro Addons

Bookly stacks status, payment, and notes per row

Bookly Pro Addons stores every appointment in two related rows. The slot lives in wp_bookly_appointments, and the per-customer attachment lives in wp_bookly_customer_appointments with a status column that moves through Pending, Approved, Cancelled, and Rejected. Payment lives in a third table, with notification status tracked next to it. The default list view is a wide grid of all those joins, which is precise and slow to scan.

SleekView reads the joined view Bookly itself uses on the back office screen, with wp_bookly_customer_appointments.status as the natural group column. The board renders one card per customer attachment, so a group appointment with three attendees produces three cards in the column that matches each attendee's status. Cards pull the customer name and the service title for the headline, staff member and time for the meta line, with payment state as a corner badge.

Drag a card from Pending into Approved and SleekView writes the new status to the customer appointment row, fires the Bookly notification hook so the email or SMS goes through Bookly's own gateway, and updates the staff calendar sync if you have the add-on installed. Cards inside group appointments stay independent so you can approve some attendees and reject others without touching the slot row underneath them.

Workflow

Bookly Pro appointments to kanban in four steps

1

Connect the Bookly tables

Point SleekView at the Bookly customer appointments table and let it auto-join the appointments, customers, services, and staff tables. The board sees the same merged view the Bookly back office uses, including any custom field values you have configured through the Custom Fields add-on.
2

Pick status as the group column

Choose the customer appointment status field as the grouping. Pending, Approved, Cancelled, and Rejected each become a column. Counts in the header roll up live and a per-column revenue total displays above the cards using the appointment price from the joined service row.
3

Choose what shows on each card

Pick the fields that go on the card face. The standard Bookly layout uses customer name plus service title as the headline, staff member and appointment time as the meta line, with payment status and notification status as two colored dots in the corner of the card body for quick scanning.
4

Enable drag-and-drop writeback

Flip the drag toggle and a status change on the board updates the Bookly row, fires the Bookly notification hook for SMS and email, and syncs to the staff Google Calendar through the Bookly add-on chain. The same audit log the back office records also captures the kanban move.

Sample board

Sample Bookly Pro Addons board

Ninety-seven customer appointments from the next ten days. Pending awaits human approval, Approved holds the locked schedule, Cancelled and Rejected sit visible for refund and reporting.
Pending
19
Olivia Chen, 60 Min Massage
Therapist Rae, Fri 16:00, 110 USD
Diego Castro, Hair Color
Stylist Jin, Sat 11:00, 145 USD
Mei Lin, Acupuncture
Dr Park, Mon 09:30, 95 USD
Approved
58
Thomas Reid, Personal Training
Coach Vega, recurring, 80 USD
Hana Kim, Skincare Consult
Dr Lee, Wed 14:00, 175 USD
Ahmed Bakr, Sports Therapy
Therapist Mira, Tue 18:00, 130 USD
Cancelled
12
Greta Lund, Yoga Class
Cancelled by customer, refund 35 USD
Pedro Alves, Couples Massage
Cancelled, partial deposit kept
Sophie Nguyen, Bridal Trial
Cancelled by salon, full refund
Rejected
8
Riley Hart, Late Night Cut
Outside open hours, rebook offered
Lucia Rossi, Bridal Package
Staff conflict, alternative slot sent
Aaron Cole, Tattoo Consult
Underage, parental consent needed

Comparison

Bookly back office vs SleekView Kanban

Default Bookly back office

  • Default list shows joined rows in a wide grid that is precise but slow to scan visually
  • Status changes require opening the appointment modal and clicking through dropdowns
  • No column totals for revenue or notification status across pending versus approved
  • Group appointments collapse into the slot row, hiding per-attendee status differences
  • Rejected entries clutter the same calendar view as live appointments, no visual split

SleekView Kanban

  • Reads wp_bookly_customer_appointments with the same joins the back office uses
  • Group by status, staff_id, service_id, or any Bookly custom field
  • Drag writeback fires Bookly notification hooks for SMS, email, and calendar sync
  • Card faces surface payment state and notification state as colored dots in the corner
  • Group appointments render as independent cards so per attendee status stays clear

Features

What SleekView Kanban gives you for Bookly Pro Addons

Drag updates the customer appointment row

Bookly stores per-customer status separately from the slot. Drag a card and SleekView updates that customer appointment row, leaving the slot intact for other attendees. The Bookly back office reflects the change immediately on its next load with no resync.

Notifications fire through Bookly

Every drag fires the Bookly notification hook, so the same template that sends approval and rejection emails through the back office sends them on a kanban move. SMS, email, and the WhatsApp add-on all behave identically without duplicate config.

Per attendee status for group bookings

A group appointment with three customers produces three cards, each in the column that matches its own status. Approve one attendee, reject another, and leave the third in Pending. The slot stays intact in Bookly and the three customers get their correct individual notification.

Audience

Where Bookly teams use the board daily

Salons running multi-stylist days

Reception groups the Pending column at start of day, drags into Approved as stylists confirm, and rejects conflicts with one drag. The Bookly notification chain fires correctly per card without anyone touching the modal.

Clinics with intake forms attached

Bookly Custom Fields capture intake answers. Cards show a small forms badge so receptionists know which Pending appointments came in with completed intake data and can drag them straight into Approved with no back office trip.

Tutors confirming group sessions

Tutors review group session attendees as separate cards, approve the ones who paid, and reject duplicates. The slot stays open at the right capacity and Bookly's confirmation emails go out to the correct customers only.

The bigger picture

Why Bookly teams adopt a kanban board

Bookly Pro Addons is a comprehensive booking system, with a back office tuned for accuracy more than speed. That accuracy pays off when you need to edit a specific appointment in detail, and it gets in the way when you have twenty pending appointments and ten minutes before lunch. The kanban board removes the modal trip from the most common Bookly task, which is moving a customer appointment from Pending to Approved or Rejected.

Every other behaviour stays Bookly. The notification engine sends through Bookly templates. The custom fields appear on the card detail panel.

The Google Calendar sync add-on runs on the same hook. The board is a viewing layer on top of the Bookly data layer, never a replacement for it. For larger studios with multiple staff, the per-staff swim lane mode is the bigger win.

Owners drop into a board that splits Approved into one swim lane per stylist, see the imbalance, drag a few cards from the overloaded stylist into another swim lane to reassign, and the Bookly staff column updates on the appointment row underneath each card.

Questions

Common questions about SleekView Kanban for Bookly Pro Addons

Yes. SleekView writes to the exact same customer appointment row Bookly's back office reads, fires the matching action hook, and runs the notification engine through Bookly's own templates. The back office reflects the change on next load with no manual sync step.

 

Yes. The notification engine in Bookly hooks the same status change action SleekView fires on a drag. Whatever you have configured in Bookly Notification settings, including the SMS gateway add-on and the WhatsApp add-on, runs on every kanban move exactly as it does on a back office status change.

 

Each attendee in a Bookly group appointment is a separate customer appointment row. SleekView shows one card per row, so a group appointment with three attendees produces three cards. Approving one attendee leaves the others untouched, and the slot row stays open for whichever attendees remain.

 

Yes. When a logged-in WordPress user is mapped to a Bookly staff member, you can scope the kanban board to that staff ID. The user sees only cards assigned to them, while admins see everything. The same per-staff visibility rules apply on the kanban board and the back office list.

 

Yes. Custom field answers appear in the card detail panel when you click the card, and you can also surface up to two field values on the card face. A common pattern is to show an intake form badge if the customer completed the form, with the full answers visible inside the detail panel.

 

Yes. Recurring series appear as linked cards on the board. By default a status change applies to the single instance you dragged. You can flip a board setting to cascade the change down the series, which is the right behaviour for weekly recurring courses where one approval covers every future session.

 

Yes. The Bookly Google Calendar add-on listens to the same status change hook SleekView fires. When a card moves from Pending to Approved, the appointment is created or updated on the staff member's Google Calendar through the Bookly add-on without any duplicate sync logic on SleekView's side.

 

Yes. The kanban board is a viewing and editing layer on top of the same data. You can leave the Bookly back office open in another tab, make changes there, and the board picks up the new status, payment, or staff assignment on its next refresh, which runs every few seconds by default.

 

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

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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