LatePoint stores bookings in the latepoint_bookings table, customers in latepoint_customers, services in latepoint_services, and agents in latepoint_agents, with per-booking metadata in latepoint_booking_meta. Pro adds custom fields, taxes, deposits, and recurring bookings, all stored in the same tables with extra columns and meta keys.

That gives admins a real conversational layer over the LatePoint calendar. A studio manager asks how many massage bookings are on the books for next week, the bot returns a count grouped by day and agent. An owner asks which service generated the most revenue this month, the bot pulls totals straight from the bookings table and the deposit column. A receptionist asks who is booked tomorrow at 10am, the bot returns the customer name and the service from one row.

Multibot lets a separate public bot run on the booking page with no access to customer rows, just service availability and price checks. Display conditions lock the admin bot to staff roles. Conversation logging records every prompt and answer inside WordPress so the team can audit accuracy over time as the schedule grows.

LatePoint studios run on tight schedules, with front-desk staff juggling phone calls, walk-ins, and the calendar view at the same time. The calendar is fine for visual scanning, but every analytical question becomes a filter, a date range, and a click into the reports section. How many massage bookings this week, which agent is overbooked, what did facials bring in last month, those exist as data and live nowhere convenient.

A plain-English layer over the same latepoint_bookings rows collapses that work. A studio owner can ask the same question on a phone between sessions and get a real number, not an estimate, because the model reads the same database rows the calendar reads. For receptionists the win is even sharper.

A walk-in asks for the next free slot with a specific agent, and instead of paging through the calendar, the front desk asks the bot. A regular calls to reschedule, the receptionist asks for the booking by customer name and gets the upcoming session in one line. The data was always there, the bottleneck was the interface.

SleekAI keeps that interface in WordPress, scoped to the right role, with every conversation logged for audit and refinement.