Bookings for Admins & Teams
Customers book through chat. Your team works in calmer tools. The important promise: both sides drive the same booking system, so a booking a customer made on LINE at midnight is the same booking your receptionist sees in the morning — never a copy that can drift apart.
The short version: staff get a schedule they can act on directly, customer and hours tools, a searchable commands reference, a full change history — and an AI helper that proposes changes but never applies them until a human confirms.
One system, three ways in
| Who | How they work | Confirmation style |
|---|---|---|
| Customers | Chat (website, LINE, …) with the AI Booking Assistant | Conversational ("Shall I cancel this?" → "Yes") |
| Staff, directly | Admin console: schedule, customers, services, hours | Clicking explicit action buttons |
| Staff, by asking | AI helper in the admin console | A proposal card — Confirm, Edit, or Dismiss |
Underneath, all three issue the same operations (check availability, create, reschedule, cancel, and more). That is deliberate: there is exactly one place where booking rules live, so behavior is identical and auditable no matter who asked.
Working directly: the admin console
These tools are live for pilot teams on the booking admin console:
- Schedule — week calendar and table views, filters by status, booking detail with cancel, reschedule, mark no-show, and create-on-behalf (handy for phone calls).
- Customers — channel accounts (website, LINE), upcoming bookings, identity merge history, and admin unmerge when a link was made in error. See Customer Identity & Linking Accounts.
- Services — catalog titles, durations, capacity, and active/inactive.
- Hours — weekly open windows, date exceptions, and blocked time so the assistant only offers times you can serve.
- Commands — searchable reference of every operation (who may run it, what inputs it needs, whether it changes data), plus ⌘K to jump to a page or command from anywhere in admin.
- Audit — recent staff and system changes with who asked, through which door (console, chat helper, or AI), and before → after.
Working by asking: the admin AI helper
Some jobs are tedious in any interface: "Cancel Lee's 3pm today" or "What services do we offer?" The admin helper accepts that kind of instruction, works out the exact operation, and then stops for anything that would change data:
Proposed change — Cancel booking … for Lee, 15:00 Asia/Bangkok
[ Confirm ] [ Edit ] [ Dismiss ]
Nothing mutates until a human clicks Confirm. Read-only questions are answered from live command results (for example listing services or reading hours). When staff confirm a change (or use Schedule actions), the customer is notified on their channel — LINE push and/or a message in their web chat — in English and Thai by default (Chinese when requested).
Accountability by default
Every mutating change records who asked, through which door (chat, console, or AI helper), and what changed — before and after. Customers can only act on their own identity; staff act for the team. Sensitive fixes such as undoing an account link are admin-only and appear in both the identity history and the command audit trail.
Rollout status
- Customer booking assistant — in pilot (chat on website and LINE).
- Admin console — Schedule, Customers, Services, Hours, Commands, and Audit are available for pilot teams.
- Admin AI helper — confirm-card flow in pilot, with customer notify on staff changes.
If your team needs access, talk to us — the booking data already lives in one place.