Yes. SleekView updates the same status column Amelia reads, calls the same action hooks Amelia fires on a manual approval or rejection, and the confirmation, cancellation, and rejection emails go out through Amelia's own notification engine. Nothing is mirrored to a side database.

Any value that appears in the Amelia status field becomes a column the next time the board refreshes. If you add a new status like On Hold in Amelia settings, you do not need to touch SleekView config. The column appears, with its own count and totals, automatically on next load.

By default a drag updates the single appointment row you grabbed. You can flip a recurring mode on per board so dragging the parent appointment moves every child instance in the series to the new status, which is the right behavior for course bookings or weekly therapy sessions that share one approval decision.

Yes. SleekView fires the same Amelia action hook that a manual status change in the back office fires, which is what triggers the notification engine. Approval emails, rejection emails, and the SMS add-on all behave the same way as if you had clicked through the native modal.

A group booking renders as a single card with attendee count in the meta line. The card pulls the service title and the lead customer name as the title, then surfaces the attendee count as a small badge so you can see at a glance whether the slot is half full or close to capacity.

Yes. Card faces accept up to four fields, so a common layout puts the customer plus service as the title, the employee and time as the meta line, the price as a corner badge, and the payment status as a colored dot. Cards stay scannable while exposing the fields that matter most.

If a logged-in user has the Amelia Employee role and is restricted to seeing their own appointments, the kanban board honors the same query restriction. Staff see only cards tied to their provider record, and admins see everything. No separate ACL config is required.

Amelia events live in a separate table with their own status column. SleekView treats events as a second board source. Point a board at the events table, pick its status as the group column, and you get a parallel kanban for event bookings without affecting your appointment board.