It writes back. Every card move calls the Setmore API through the plugin's authenticated client and updates the local wp_setmore_appointments row in the same step. The hosted Setmore account, the WordPress plugin cache, and the kanban view all share one consistent picture of the booking state at all times.

The plugin syncs the cancellation back into the local cache on its normal interval, and SleekView reads from that cache. The cancelled card moves automatically into the cancelled column during the next refresh cycle, so staff see the change without anyone having to manually triage the change request.

Yes. The card editor lets you pick any column the plugin stores. A common layout shows customer name and time on the front line, service and staff member on the second line, and reveals the location and note on hover so the receptionist sees the full picture without opening the booking.

Yes. SleekView Kanban inherits the capability checks that Setmore WP already uses for booking edits. If a user can change a booking on the plugin's own edit screen, they can drag a card on the kanban. If they only have read access, the board renders read-only with drag handles hidden from view.

The deposit amount is stored on the same row in the cache table. Add the deposit field to the card and the receptionist sees it on the front of every card. Moving a card into cancelled does not refund the deposit automatically, because deposit handling lives inside the Setmore account and follows its own policy rules.

Yes. The kanban field is configurable, so you can group cards by service type, by staff member, or by location instead of status. Each saved board can use a different grouping, which lets the receptionist work by status while the manager pins a per-staff capacity board to the office monitor.

Notifications are configured inside Setmore, not inside SleekView. When the API call updates the booking status, the Setmore account triggers whatever email or SMS automation you have set up for that transition. The kanban respects whatever notification policy the hosted account already enforces.

Yes. SleekView reads every distinct value in the status column, so any custom status the Setmore account exposes through the API appears automatically as a new kanban column. Pick which custom statuses to surface on the board and hide the rest without losing them from the underlying data.