/book-customer

1. 01 Call search_members to find the accountId. If they don't exist, run the add-customer playbook first.
2. 02 Call list_services to find the right service. Filter by name keyword if provided.
3. 03 Call get_available_slots with serviceId + date range (default to next 7 days if user didn't specify).
4. 04 Confirm the slot with the user before booking — slot pickers vary, so don't assume "earliest" without asking.
5. 05 Call create_booking with accountId + serviceId + start time + duration.
6. 06 Call confirm_booking unless the service requires customer-side payment (check with get_service_detail.requiresPayment).
7. 07 Optionally call send_whatsapp_message to notify the customer with a booking template.

• search_members
• list_services
• get_available_slots
• create_booking
• confirm_booking
• send_whatsapp_message

Every tool ships with MCP annotations (title, readOnlyHint, destructiveHint, openWorldHint, idempotentHint). Clients can gate destructive calls before invoking. Full catalog: /server-card.json.

• /cancel-and-refund

  Cancel a booking with the proper refund + audit chain.

  Read playbook
• /handle-no-show

  Mark a booking as no-show and apply the configured penalty.

  Read playbook
• /send-booking-reminder

  Find tomorrow's confirmed bookings and ping each customer.

  Read playbook