It sits alongside. SleekView Kanban reads from the same wp_bookafy_appointments cache that the plugin maintains, and writes back through the existing Bookafy API client. The remote Bookafy dashboard, the public booking page, and the WordPress kanban all see the same status for every appointment without any extra reconciliation.

SleekView queues the status change locally and retries once the API returns. The card shows a small syncing indicator until the call succeeds, then locks into the new column. If the call eventually fails for hours, the card reverts to its previous column and a notice in the board header explains what happened.

Yes. The card editor lets you pick any field from the cache, including the meeting URL that Bookafy stores for virtual bookings. A common layout shows customer name and time on the front, with the meeting link revealed on hover, so staff can launch the call without leaving the kanban view.

The board polls the cache table at a configurable interval, with ninety seconds as the default. New bookings appear as cards in the pending column inside that window. Open cards never lose their drag position during a refresh because the board reconciles existing rows in place rather than reloading the whole layout.

It only changes the status to cancelled in Bookafy. Refunds, customer emails, and any downstream automation are handled by the rules you have configured inside the Bookafy account itself, so the kanban respects whatever cancellation policy you already use without you having to define a second policy in WordPress.

Yes. Register a custom status value in the Bookafy account and the board picks it up automatically as a new column. SleekView reads every distinct value in the status field, so any custom status you use in Bookafy appears in the kanban without any extra mapping inside WordPress.

Yes. If the plugin is configured to sync from more than one Bookafy account, SleekView reads the account identifier as an additional field. Add a filter on that field and save one board per account, or leave the filter empty and see all accounts on a single global board for cross account visibility.

Yes. Saved boards can be exposed through a public token URL that hides drag handles and edit controls. Use this to show a client the status of their own bookings without giving them a WordPress login, or to share a service-day overview with a partner team that needs visibility but not edit rights.