CaptainBook

The summer schedule is agreed and every product option needs its dates. The agent runs Create Availability Rule per option with the weekday recurrence, first with Dry Run enabled so the response reports how many slots the rule would materialize. That count goes into a review in Slack alongside the product title and the date range. Once the numbers look right, the agent commits, and because generation is asynchronous it polls List Availabilities to confirm the slots have landed with the expected capacity. A rule that would have opened four hundred slots instead of forty is caught before it reaches the booking page.

A guide calls in sick and one afternoon departure has to shrink from twelve seats to six. The agent runs List Availabilities for the product option and date, finds the slot, and calls Update Availability with the reduced capacity, previewing with Dry Run first. It then runs List Bookings for the same slot to see who is already booked past the new limit, and posts the affected guests to the operations channel with their booking references. Nothing is canceled automatically. The agent surfaces the overage and the reassignment options, and the duty manager decides who moves.

Every night the agent runs List Transactions across the tenant for the day's window, filtered by status and type, and writes each charge, refund, and comp into Xero with the booking reference attached. Amounts arrive in minor currency units, so the agent converts once, in one place, rather than in every downstream report. Anything the ledger cannot match becomes an automation exception routed to finance in Slack with the transaction, the booking, and the customer already attached, so the person picking it up starts with the full picture instead of a reference number.