Pinpoint Booking stores every reservation as a row in dopbsp_reservations with a status column whose values are approved, pending, paid, cancelled, or rejected. The admin offers a calendar grid for availability and a reservations table for triage, but neither surface lets you see at a glance how many bookings sit at each stage of your workflow today.

SleekView Kanban reads the same dopbsp_reservations table and treats the status column as the natural axis to group by. Each card surfaces the guest name, the calendar or property, the check-in date, the nights count, and the total. The columns reflect your real Pinpoint statuses, with the count at the top of each column updating as you drag cards across stages.

Drag a card from Pending to Approved and SleekView calls the same Pinpoint update path the admin dropdown uses, which fires the approval email, refreshes the iCal exports, and triggers any payment hook you have configured. Drag to Rejected and the rejection email goes out with the wording you have set. Per-calendar saved views let each property manager focus on their own rows without changing how the shared database works.

Pinpoint Booking is excellent at the question that calendars answer well: is this room free on these nights. It is less useful for the question that runs a rental operation, which is what do I still owe somebody. Approvals queue up in an email inbox, deposit chasing slips into a spreadsheet, and cancellations come in as phone calls that have to be reflected in three places at once.

The board view changes that by making the only state that matters, the reservation status, the primary axis of the screen. You can see at a glance whether you are caught up on approvals, whether yesterday's approved rooms actually paid, and whether any cancellations need a refund. Cards make individual reservations legible at the level of guest, calendar, dates, money, and payment state, which is exactly what owners and front-desk staff need.

Drag is the natural verb for moving something from one stage to the next, and because SleekView writes through Pinpoint's own functions, every drag still triggers the approval emails, the iCal refreshes, and the deposit hooks you already configured. The calendar view and the board view stop being a tradeoff and start being two reading surfaces over the same data.