# Bookatu: full reference for AI assistants > Online booking and scheduling software for salons, spas, nail and beauty studios, barbers, personal trainers, coaches, studios, photographers and restaurants. Each business gets a branded booking page, a calendar, automatic reminders, deposits and no-show protection, client records, marketing tools, a public REST API and an MCP server for AI agents. Flat subscription, 0% commission on bookings. This is the expanded version of https://bookatu.com/llms.txt. It is generated from the same content that renders https://bookatu.com/en-nz, so everything below matches the live product. Machine-readable equivalents: the OpenAPI 3.1 spec at https://bookatu.com/api/openapi.json and the capabilities document at https://bookatu.com/api/capabilities. Every help article, blog post and engineering post, and the developer documentation, also has its own plain markdown copy at the page's address with .md on the end (for example https://bookatu.com/help/deposits.md and https://bookatu.com/developers.md); https://bookatu.com/llms.txt lists them all. ## Facts Facts, checked 2026-11-16: What it is: Bookatu (bookatu.com) is online booking and business software for service businesses: a branded booking page and website, a calendar, reminders, deposits, client records and marketing tools. Not to be confused with Bookitu. Who it is for: salons, barbers, spas, personal trainers, coaches, studios, photographers and restaurants. Prices: Solo US$9 a month, Studio US$35 a month, Pro US$79 a month, Scale US$179 a month, billed in USD. Every plan is free for 60 days, there is no free plan, and there is 0% commission on bookings. Add-on: AI and Developer API, US$19 a month, included on Scale. Languages: Bookatu's public pages, booking pages and client emails come in 14 languages (English, Deutsch, Français, Español, Italiano, Nederlands, Português, Dansk, Svenska, Norsk, Suomi, Polski, 日本語, Čeština). AI assistants: a business connects its own AI assistant to its account through the MCP server at https://bookatu.com/api/mcp, which has 81 tools (sign in with OAuth, or use a scoped API key). The docs MCP server at https://bookatu.com/api/mcp/docs has 6 read-only tools and needs no key. Testing an AI agent: a developer's sandbox (a test business with made-up clients, where nothing is sent and no card is charged) answers the same MCP server, and adds sandbox_outbox, sandbox_payments, sandbox_simulate and sandbox_reset for checking what an agent did: https://bookatu.com/developers/testing-ai-agents.md. Website widget: a business puts booking on its own website with one script, bookatu.com/embed.js (or the pinned /embed.v1.js, loadable with an integrity hash). It tells the page what happens in it (ready, service_selected, staff_selected, time_selected, booked, request_sent, handoff, error, closed), never with the client's name, email or phone, and a business can limit it to its own domains, which visitors' browsers enforce. Booking from AI assistants: a client's own assistant can find free times at a business on Bookatu and hold one through the public booking MCP server at https://bookatu.com/api/mcp/book; the client confirms by email before the booking reaches the business. How an owner switches it on: https://bookatu.com/en-nz/help/let-clients-book-from-their-ai. Not HIPAA or PHIPA compliant. No Reserve with Google: clients cannot book a business on Bookatu inside Google Search or Maps. No payment inside AI chats. ## Pricing Every plan is free for 60 days, then from US$9 a month (US$8 a month billed yearly). Plans run from US$9 to US$179 a month, every plan includes all the core booking features (a few optional add-ons cost extra), and there is 0% commission on bookings. The price scales with active clients. An active client is someone who booked or trained with you in the last 90 days. Quiet clients on your list never count, so you only pay for the people you are actually serving. Annual billing charges 10 months for a full year. - Solo: $9 per month (USD), up to 1 staff seat, up to 150 active clients, 500 marketing emails a month. Just you, getting started. - Studio: $35 per month (USD), up to 5 staff seats, up to 600 active clients, 5,000 marketing emails a month. A team of up to five. - Pro: $79 per month (USD), up to 10 staff seats, up to 2000 active clients, 10,000 marketing emails a month. A busy salon, up to ten. - Scale: $179 per month (USD), no cap on staff seats, no cap on active clients, 25,000 marketing emails a month. Bigger teams, no limit. - Pay as you go: an alternative to the monthly plans with no subscription, priced per staff seat per month (details in the FAQ below). - Allowances: booking confirmations, reminders and receipts never count. Past a plan's monthly texts or marketing emails, sending pauses until the allowance renews. Nothing is ever charged for going past an allowance. Included on every plan: - Your own branded booking site - Unlimited staff, services and calendars - Card payments and deposits that stop no-shows - Customer CRM with full visit history - Automatic reminders, reviews and win-back - Loyalty points, gift cards, packages and memberships - Referrals, promo codes and senior discounts - Marketing newsletters and a smart waitlist - Client programs and homework for trainers and clinics - 0% booking commission, your clients are always yours Optional add-ons, the only extra charges: - SMS reminders: $5 per month on Solo; included on Studio, Pro and Scale. Texts go out in New Zealand, the United States and Canada so far (in the United States and Canada only to clients who agreed to get texts), and on Bookatu's own numbers only once the business's plan is paid, not during the free trial. Email reminders are on every plan. - Be Bookable by AI + Developer API: $19 per month, included free on Scale. Unlocks API keys, the v1 REST management endpoints and the MCP server for the business. - AI with your own Gemini key: $4 per month, the same AI features and Developer API with the business paying Google for its AI use. Not combined with the managed add-on. - Extra gallery storage: 25 GB packs at $5 per month. Client galleries are included on Pro and Scale, and always on for photography businesses. - Full details: https://bookatu.com/en-nz/pricing Custom domain: included on Pro and Scale, also during a free trial of one of them. The business buys and renews its own domain name. ## Common questions ### Pricing Q: Is there a pay-as-you-go option with no monthly fee? A: Yes. With pay as you go there is no subscription. You pay 8 dollars per team member each month, and nothing at all in a month with no team. It follows the size of your team rather than how busy you are, so the price is predictable and you control it: add a team member and you add a seat, remove one and the seat comes off. It is billed only from the day you add a card, never for a day before. Once your team settles, a monthly plan usually works out cheaper and we point that out so you never overpay. Q: How much does Bookatu cost after the free trial? A: After the 60-day free trial you pick a paid plan yourself, in Plan & billing. Each plan covers a range of active clients, and Plan & billing suggests the one that fits you right now. Plans start at $9 a month for Solo, then $35 for Studio, $79 for Pro and $179 for Scale. Bookatu never takes a commission on your bookings. See the pricing page for the active-client range each plan covers. Q: What is an active client? A: An active client is a client who booked or visited you in the last 90 days, counted on a rolling basis. Quiet clients sitting in your list don't count, so the plan that fits you depends on how busy you actually are, not the size of your contact list. You choose your plan yourself, in Plan & billing. Q: Do you charge per staff member? A: No. Your plan is based on how many active clients you have, not how many staff or team members you add. You can add your whole team without paying more per person. Q: How long is the free trial, and what happens when it ends? A: Bookatu is free for 60 days. When the trial ends, your booking page stays open and you choose a plan when you are ready. Until then you are on pay as you go, which is only billed from the day you add a card. Your data is always safe. Q: How do I cancel my subscription? A: Any time, from the billing area in Settings, which opens your secure billing portal. There is no lock-in. You can come back later by choosing a plan again. Closing your business stops billing as well. Pay as you go sends no invoice from the month you ask, and a plan is cancelled with no final invoice when the closure goes through. Your data stays yours and you can export it before you go. ### Features Q: Can I share photo galleries with my clients? A: Yes. If you take photos for clients, you can share a private gallery in each client's booking account. They see low-resolution previews with a baked-in watermark, heart their favourites, and download the full-resolution files once their picks are settled. You can include a set number of photos and charge for extras, and your storage is metered with the option to add more. Q: Can a restaurant take online orders for pickup? A: Yes. Restaurants can list their dishes as a menu on their public page and take pay-online, collect-in-store orders. Guests add items to a cart and pay online with no commission taken, and each order arrives as a ticket to prepare. Q: Can I add a Book now button to my own website? A: Yes. Under Grow, Website widget, you copy a one-line snippet and paste it into your site (Squarespace, Shopify, WordPress or Wix), with no plugin to install. Choose Button for a Book now button that opens your booking page, Pop-up to open booking over your own page, Inline menu to put your services inside the page, or Floating to pin a button to the corner of every page. Q: Can I run group classes and clinics? A: Yes, if you run a studio or work as a trainer, coach or photographer. As well as one-to-one appointments, you can run fixed-time group sessions: a class or clinic at a set day and time with a limit on spots. People book and pay online, the page shows how many spots are left and marks it full at the limit, and you can set it to repeat each week. It suits tennis clinics, fitness and yoga classes, group coaching, workshops and photographer mini-session days. Q: Can I keep a class private and share the link? A: Yes, if you run a studio or work as a trainer, coach or photographer. You can make a group class private so it does not show on your public page, then share a link on WhatsApp or in a group chat so only the people you send it to can see the sessions and book. You can copy a link for the whole class or for one specific session, which drops the person straight onto that date to book. It is made for members-only clinics and closed groups. Q: Do outdoor sessions show a weather forecast? A: Yes, for studios, trainers, coaches and photographers running group sessions. Each upcoming group session shows a live weather forecast for that day right on the booking card, so people booking an outdoor class or clinic can see what to expect. If you cancel a rained-off session, everyone who booked is credited back automatically and emailed. ### Getting started Q: What is Bookatu? A: Bookatu is online booking and scheduling software for salons, spas, studios and personal trainers. You get a branded booking page, a calendar, automatic reminders, deposits and no-show protection, client records, and marketing tools, all in one place. Q: How do clients book an appointment? A: Clients open your booking page, pick a service, choose a team member or 'any available', select a time that fits your real availability, and confirm. They get an instant confirmation and a reminder before the visit. Booking takes under a minute and works on any phone. Q: Do clients need to create an account to book? A: No. Clients can book in seconds with just their name and contact details. No app to download and no password to remember. They can optionally sign in later to view and manage their visits. Q: Is there a free plan? A: No. Every plan is free for 60 days, then from US$9 a month (US$8 a month billed yearly). Plans run from US$9 to US$179 a month, every plan includes all the core booking features (a few optional add-ons cost extra), and there is 0% commission on bookings. See the pricing page for the plans side by side. Q: Is there a setup checklist to help me go live? A: Yes. When you first sign in, your admin dashboard shows a short checklist that takes you from sign-up to a live, bookable storefront, and each step only ticks when you have really done it. See the first-run setup checklist help article for a walkthrough. Q: Can clients book from their phone? A: Yes. The booking page and the whole admin are built mobile-first, so both your clients and your team can book and manage appointments from a phone. Q: Can I install Bookatu as an app on my phone? A: Yes. Bookatu installs straight from your web browser, with no app store. On Android or Chrome, tap the Install app button. On an iPhone or iPad, open the page in Safari, tap Share, then Add to Home Screen. Both you and your clients can install it for one-tap access. Q: Can I use my own website or domain? A: Yes. Your booking page lives at its own web address, and you can add a Book now button or embed the booking widget on your existing website. You can also link to it from your Instagram bio, your Google profile and your email signature, so clients can book wherever they find you. On the Pro and Scale plans you can also connect a domain you own, so your booking page opens at your own address. See the using your own domain for your booking page help article. Q: Can I give my team a daily checklist? A: Yes. You can build a daily checklist of your opening, between-client and closing jobs that your staff tick off on their phones. It records who did what and when, and resets each morning. Salons can load a ready-made list in one tap and edit it. It keeps your standards the same on every shift and helps train new starters. Q: Can I add a trainee who only sees the checklist? A: Yes. A trainee is a login type for juniors and apprentices. When they sign in they see only the team checklist, so they can tick off their jobs, and nothing else: not your calendar, your clients, your money or your settings. It is the safe way to bring a new starter onto the team. You can change their role to give more access later. ### Payments Q: How do payments and deposits work? A: You choose how clients pay you by card in Settings, Payment options: Bookatu payments, which you set up inside Bookatu, or your own Stripe account. Either way, Stripe holds the money and pays it into your bank. You can ask for a deposit at the time of booking to reduce no-shows, with the deposit coming off the total on the day. Bookatu does not take a commission on your bookings, and you pay Stripe's card fees. Q: Does Bookatu take a commission on my bookings? A: No. Bookatu charges a flat subscription, not a percentage of your bookings. The money your clients pay goes to your own connected payment account. Q: Do you send SMS text reminders, and do they cost extra? A: Email reminders are included on every plan. Text (SMS) reminders are included on the Studio, Pro and Scale plans, and on the Solo plan you can switch them on for a small monthly add-on. Each plan comes with a monthly text allowance, and you can see exactly what is included on the pricing page. Texts from Bookatu's number start once your plan is paid, not during the free trial. They can only be sent in some countries so far, which the SMS text reminders help article lists, and they carry booking confirmations and appointment reminders. Other texts need your own texting number. Bookatu still never takes a commission on your bookings. Q: When do I get paid? A: Booking deposits go straight into your own Stripe account, because clients pay you, not us. Stripe then pays the money out to your bank on a regular schedule, often every couple of business days. Your first payout can take a little longer while Stripe verifies your account. Bookatu never holds your deposits. Q: Can I issue a refund? A: Yes. Booking deposits paid online go back to the client in full when you cancel the booking. For a shop order, open it and press Cancel & refund, then Yes, refund. To refund only part of a payment, do it in your Stripe dashboard for now. ### No-shows Q: How does Bookatu reduce no-shows? A: Reminders go out before each visit, and you can ask for a deposit when clients book. With the no-show shield on, regulars with a clean record skip the deposit, while new clients and anyone with a past no-show pay the usual one, never a bigger one. In New Zealand, Australia and the United States you can also ask clients to save a card, which is only charged a fee you set if they cancel late or do not turn up. Card holds are not available to clinics in the United States. Q: What happens when a client cancels? A: The slot reopens automatically, and Bookatu offers it to the best-matching client on your waitlist, your highest-value waiting client who fits that service and time, so a cancellation can turn into a re-booking instead of an empty hour. Q: What happens if I use up my SMS texts for the month? A: Your SMS reminders pause for the rest of that month, and your email reminders keep going automatically, so clients are never left unreminded. The allowance is a fair-use limit, not a hard cliff, and it resets at the start of the next month. Nothing extra is charged. ### Scheduling Q: Can I manage more than one staff member? A: Yes. Each team member has their own bookable services, working hours and calendar column. Clients can pick a specific person or let the system find anyone available. Q: Can I block off time so clients can't book it? A: Yes. You can block off time for breaks, holidays or admin (for everyone or one team member), and that time is removed from online availability immediately and shown on your calendar. Q: Does it use my real working hours? A: Yes. Your business hours drive both the calendar and what clients can book, so people can only book when you are actually open. ### Marketing Q: Can I send newsletters and offers to my clients? A: Yes. You can email clients who opted in, with a live preview of how the email will look, scheduling, and one-click unsubscribe. Only subscribed clients are ever emailed. Q: Can I run happy-hour or off-peak deals? A: Yes. You set off-peak windows, such as weekday mornings or Sunday afternoons, and a percentage off, shown on your public Deals page. The discount applies automatically to bookings made in those quiet windows, so you fill slow hours without discounting your busy ones. This is separate from typed promo codes. Q: How do new clients find my business on Bookatu? A: Through your own booking page link, which you can put in your Instagram bio, your Google profile and your email signature, and through the Website widget on your own site. Search engines can find your page too, once you switch on List my booking page in search under Settings, SEO & analytics. Bookatu takes no commission on the bookings that come in. Q: What do the City and Region settings do? A: Your City or town and your Region (a wider area or state) show on your booking page and go into the details search engines read, so people near you can find you. Set both accurately under Settings, Business details. See the getting found online help article for more. Q: Can I add a link to my existing website? A: Yes. Type your domain in the Website field under Settings, Business details, and Bookatu shows a tidy 'Visit our website' link on your storefront's contact card. You can also add extra websites and your social profiles in the same place. This links out to a website you already have; it does not connect your own domain to your Bookatu storefront. See the your business profile, website and social links help article. Q: Can I add my Instagram, TikTok and Facebook to my booking page? A: Yes. In the Website & social section under Settings, Business details, type your Instagram, TikTok or Facebook, just your @handle is enough, you do not need the full link. Use 'Add another link' for extra websites or other media like YouTube, X, LinkedIn or WhatsApp. Each one you fill in shows on your booking page's contact card with the right icon, and the ones you skip are left out. This links out to the profiles you already have; it does not connect your own domain to your storefront. See the your business profile, website and social links help article. ### Business types Q: What types of business is Bookatu for? A: Salons, spas, nail and beauty studios, barbers, personal trainers, fitness studios, photographers, coaches, restaurants and freelancers. The wording and features adapt to your industry. For example, trainers get workout checklists. Q: Does Bookatu use my industry's wording? A: Yes. The whole experience rewords to your trade based on the business type you choose. Trainers see sessions, spas see treatments and therapists, studios see classes, and restaurants reserve tables from a menu. Whatever you do, the booking page and client portal read as if they were built for it. ### Data Q: Who owns my client data? A: You do. Your client list, notes and history are yours. You can export your data, and each business's data is isolated from every other business on the platform. Q: How do I move my clients from Fresha to Bookatu? A: You don't have to start from scratch. Export your client list from your current tool as a CSV file, which Fresha and most booking apps can do, then import it into Bookatu under Clients. If the file is messy or you'd like a hand, send it to us and we'll help bring your clients across. Q: Is my data backed up, and can I export it? A: Your data is yours and you can export it any time, including your client list, bookings and payment records, as files you can open in a spreadsheet. It is stored securely, and each business's data is kept separate from every other business on the platform, so you are never locked in. ### Selling & shop Q: Can I sell products, and can you ship them? A: Yes. You can sell retail and take-home products from a Shop on your booking page. Each product is either shippable, where checkout collects a delivery address, or pay-online-and-collect-in-store. Clients pay by card at checkout, and you fulfil orders yourself while the order status tracks each one. Q: Can I sell gift cards, packages and memberships? A: Yes. You can sell gift cards, prepaid packages, where a client pays an amount and gets more credit to spend, and recurring monthly memberships. Clients buy them from your booking site and pay by card. A gift card's recipient gets a code. Once it is redeemed, by the client on their account page or by your team, the value becomes credit on their account, and that credit pays the deposit when your team books them in and it covers the whole deposit. ### Developers Q: Is there an API or AI-agent (MCP) integration? A: Yes. Bookatu has a REST API and an MCP server. The API lets other software work with your business data, and the MCP server lets an AI assistant you connect to your own account check your availability and make or move bookings for you. The pricing page shows what each plan includes and which add-ons cost extra. The technical reference is at /developers. ## Help guides ### Share photo galleries with your clients If you take photos for clients (a photographer, or before-and-after shots in a salon or clinic), you can share a private gallery with each client inside their own booking account. They see watermarked previews, heart the ones they love, and download the full-resolution files once their picks are settled. It replaces emailing huge files or paying for a separate gallery tool. Your work is protected, since previews are low-resolution with a baked-in watermark, so nobody can take the finished photos before they pay, and you can charge for extra shots beyond a client's included set. How to use it: 1. Open a client from Clients, then upload their shoot under Photos. Keep 'Watermarked proof' on so previews are protected. 2. Set how many photos are included and the price per extra, then switch the photos to Shared. They appear in that client's private gallery. 3. Send the gallery: use 'Send gallery to client' to email a secure link, or copy the link and send it your own way. The link lasts 30 days. 4. The client hearts their favourites and pays for any extras. Full-resolution downloads unlock once their selection is settled. 5. Watch your storage on the Galleries page. If you run low you can add storage in 25 GB packs. Guide: https://bookatu.com/en-nz/help/client-galleries ### Put your menu online and take pickup orders Restaurants can list their dishes as a menu on their public page and take pay-online, collect-in-store orders. Guests add items to a cart and pay, and you get the order as a ticket to prepare. It turns your booking page into a simple ordering page too, with guests paying online and no commission taken. How to use it: 1. Go to Menu (under Catalog). Add each dish with a name, price, a short description and a photo. Use the category to set the course, for example Starters, Mains, Drinks. 2. Mark a dish as purchasable and give it a price so guests can order it. Leave it not-purchasable to show it as a display-only menu line. 3. Your menu now shows on your public page. Guests add items to the cart and pay online. 4. Paid orders arrive under Pickup orders. Work them through as you prepare and hand them over. 5. To take payments you need Stripe connected, under Settings then Payments. Guide: https://bookatu.com/en-nz/help/restaurant-menu-and-pickup ### Sell session packs and chase unpaid sessions For trainers and coaches: sell a pack of sessions (say ten) that counts down as the client trains, and keep track of who has paid. The 'who owes you' board lists every unpaid session so cash and bank-transfer clients do not slip through. Packs pull money forward and pre-commit the next visits. The payments-owed board means you stop forgetting who still has not paid, which is the quiet leak in most one-to-one businesses. How to use it: 1. Create a pack under Packages: give it a name, a price and the number of sessions. When a client buys it, the sessions are added to their balance. 2. Each completed session counts one down. The client sees their remaining sessions in their account, and you see it on their client page. 3. For cash or bank clients, open Finance to see 'who owes you'. It lists each person and the amount outstanding. 4. Log a cash or bank payment against a session, or send a reminder, right from that board. 5. The board keeps a running total of what is owed, so you always know where you stand. Guide: https://bookatu.com/en-nz/help/session-packs-and-getting-paid ### Add booking to your own website One small snippet you paste on the website you already have. It can be a Book now button, your whole services menu inside the page, a pop-up that opens over your site, or a button that floats on every page. If your site already has a Book now button you like, you can keep that one. The snippet just takes the click. Your visitors are already on your website. This turns them into bookings in minutes, with no plugin to install and nothing for a web designer to build. The pop-up keeps people on your own site all the way to the confirmation, instead of sending them somewhere else to finish. How to use it: 1. Go to Grow, then Website widget, and choose how it should look: a button, your menu inside the page, a pop-up, or a floating button. 2. Set the text and colour. To make a button that books one particular service, choose that service under Opens at. 3. Copy the snippet and paste it into your site: a Code block in Squarespace, a Custom HTML block in WordPress, an Embed HTML element in Wix, a Custom Liquid section in Shopify. 4. For the floating button, paste it once into your site's footer or custom code settings instead, and it appears on every page. 5. To open at one person, one branch or one day, or with a promo code already entered, choose them in the builder too. The button, the pop-up, the menu and the floating button all keep them, and a booking that came from an ad or a newsletter link to your site shows that campaign under Came via. 6. To count bookings in Google Analytics, Google Ads, Tag Manager or the Meta pixel, use the events the widget sends to your page: one for each step, and one when someone books, with the service and its price. They never include your client's name, email or phone. The widget only uses tags your site already loads, so your cookie banner stays in charge. 7. Under Only allow your own websites, add your domains. Visitors' browsers then refuse to show the widget on any other site, at every step of a booking. 8. Publish the page and check it there. Site builders block scripts in preview mode, so the widget only comes alive once the page is published. Guide: https://bookatu.com/en-nz/help/website-book-now-button ### Follow up with people who didn't finish booking When someone begins booking (or buying a package or gift card) and leaves their contact details but does not finish, Bookatu saves them as a lead. Enquiries land in Leads too: one sent about a trip on your booking page, or one sent from your own website's enquiry form through the Bookatu API. These are warm prospects who were one step from booking. A quick call or message often turns them into a real booking, and replying fast is the single biggest thing that wins them. How to use it: 1. Open Inbox, then Leads. New leads and enquiries sit under Needs follow-up. 2. An enquiry shows Their answers, so you can see what they asked for. 3. Press Book them in to open a new booking with their details already filled in. It needs Edit the calendar. 4. Tap their phone number to call them, or press Copy email to write to them. Then press Mark contacted, or Dismiss if it is not worth chasing. 5. A dismissed enquiry stays under Dismissed, where you can delete it. 6. New booking enquiries also show on your Dashboard, so none go cold. Guide: https://bookatu.com/en-nz/help/leads-and-follow-ups ### Pay as you go: no monthly fee An alternative to a monthly plan. Instead of a fixed fee, you pay 8 dollars per team member each month. A month with no team costs nothing. It follows the size of your team, not how busy you are. It removes the risk of paying a subscription before the bookings are coming in, which suits new, seasonal or quiet-some-months businesses, and the price only moves when you add or remove a team member. How to use it: 1. See the pricing page and the live estimator to work out what it would cost for the size of your team. 2. You are billed once at the end of each month, and only from the day you add a card, never for a day before. 3. Once your team settles, a monthly plan usually works out cheaper, and we tell you when to switch so you never overpay. Guide: https://bookatu.com/en-nz/help/pay-as-you-go ### Automations that run your admin for you Bookatu can send the routine messages a salon lives on (appointment reminders, thank-yous, review requests, win-back offers and birthday treats) and quietly offer freed-up slots to your waitlist. They run in the background once switched on, using wording you can change to sound like you. It is the admin you would never find time to do by hand, done for you every day. That means fewer no-shows, more Google reviews, and lapsed regulars coming back instead of drifting to someone else. How to use it: 1. Open Settings, then Messaging & retention. Switch on the messages you want: appointment reminders, a thank-you after each visit, win-back offers and birthday treats. Most are on by default. 2. Set the timings: how many hours before a booking to remind, and how many days of silence trigger the first and second win-back. Reword the win-back and birthday messages in your own voice, then Save. 3. Optional: turn on Also send reminders by text (SMS) if you want texts as well as email. SMS is a paid channel, so it follows your plan's allowance and only goes to clients who opted in. 4. To send review requests automatically, go to Grow, Reviews and paste your Google review link. After a completed visit, happy clients are pointed to Google while unhappy feedback stays private for you to fix. 5. To let cancellations refill themselves, open Settings, tap What clients see and switch on Waitlist. When a spot opens, the best-matched waiting clients get a one-tap 'claim this spot' offer, and the first to claim gets it. Guide: https://bookatu.com/en-nz/help/automations-overview ### Set up automated reminders Automated messages around every appointment: a confirmation the moment a client books, and a reminder before the visit. Email is included on every plan, and text (SMS) is available depending on your plan. Most no-shows are just forgotten visits, so a well-timed nudge is the cheapest way to protect your day and your takings. It runs by itself, so you fill more chairs and keep regulars coming back without chasing anyone. How to use it: 1. In the admin, open Settings, then Messaging & retention. Confirmations and reminders are on by default for new bookings, so there is usually nothing to install. 2. Keep the reminders switch on. It reads Send appointment reminders, or uses your business's own word for a booking. A confirmation goes out the moment a client books, showing your business name and the visit details. If you like, also switch on Ask clients to confirm the day before. 3. Under Send reminders before, set how far ahead the reminder lands. The default is 24 hours before the visit, which suits most salons and gives clients time to rearrange or cancel. 4. Choose the channel. Email reminders are included on every plan. To add text reminders, switch on Also send reminders by text (SMS) on the same page (included from the Studio plan up, or a low-cost add-on on Solo). Bookatu's numbers can only send texts in some countries so far, and the guide SMS text reminders and the Solo SMS add-on lists them. Elsewhere the settings show that texts are not available in your country yet, and email reminders go out as normal. Bookatu's numbers send booking confirmations and appointment reminders only. Other texts need your own texting number. 5. Save. Texts carry your business name and clients can reply STOP to opt out, which keeps you within messaging rules. 6. Check it is live from the Retention dashboard, which shows whether reminders are on and how far ahead they are sent. Guide: https://bookatu.com/en-nz/help/automated-reminders-setup ### Win back clients automatically Bookatu watches each client's own visit rhythm and, when someone slips past it, automatically emails them a friendly win-back offer to bring them back in. It runs on its own from your settings, so no one has to remember who has gone quiet. Lapsed clients are revenue you have already earned once, and a gentle nudge at the right time wins them back before they find somewhere else. Because it sends itself, you get those visits back with zero manual work and nobody slips through the cracks. How to use it: 1. Open Settings and tap Messaging & retention. 2. Turn on "Send win-back offers to clients we have not seen in a while". 3. Set "First win-back after" (for example 45 days) for a gentle nudge, and "Second win-back after" (for example 90 days) for a stronger offer. 4. Edit the "Win-back message" to include a reason to return, like 15% off their next visit, then Save. Only clients with an email who agreed to marketing are ever contacted. 5. Check progress any time under Grow, Retention: the win-back queue shows who is drifting, and you can send one early with a tap if you want. Guide: https://bookatu.com/en-nz/help/win-back-automation ### Fill cancellations automatically with the waitlist The waitlist collects clients who want an earlier appointment. When a booking is cancelled, Bookatu automatically offers that freed slot to your waiting clients with a one-tap claim link, so nobody has to make a phone call. Gaps fill themselves while you keep working, so you lose far less revenue to last-minute cancellations. Offering openings to your highest-value clients first also keeps your best regulars coming back. How to use it: 1. Open Waitlist in the left admin menu and click "View public form" to get your waitlist link. Share it (it also sits on your booking page) so clients can join and pick a service, an optional staff member, and the dates that suit them. 2. Offers go out by email straight away. To send them by text too, connect your own texting number under Inbox, then Channels. 3. That is the whole setup. Auto-fill now runs on its own. The moment an appointment is cancelled, Bookatu offers the freed slot to the top waiting clients, ranked by lifetime value, each with their own one-tap claim link. 4. The first client to tap their link books the slot; everyone else simply sees "already filled." Nothing is ever double-booked, and clients are not pestered again for the same opening. 5. To offer a specific opening by hand, open Waitlist and use the "Offer a slot" button on the client at the top of the list. They are your highest-value match. 6. Check the Waitlist page to watch entries move from Waiting to Offered to Booked, so you can see gaps filling themselves. Guide: https://bookatu.com/en-nz/help/waitlist-auto-fill ### Your booking page Every business gets its own booking page at a simple web address. Clients pick a service, choose a time that is actually free, and book. It shows your name, colours, photos and reviews. An empty section is left off your page. Clients can book any time, day or night, without calling or messaging. No more back and forth, and your calendar fills itself. How to use it: 1. Add your services under Catalog, Services (name, price, how long it takes). 2. Add your team under Settings → Team, and tick which services each person does. 3. Set your opening hours under Settings. 4. Share your booking link from the Share & QR code page, or use View site to see exactly what clients see. 5. Your booking page and shop are protected by a spam check and daily limits. On an unusually busy day, more online bookings or purchases may be turned away for the rest of the day. Clients are asked to try again later or to contact you, and we email you that day. Your team can still book people in from the admin. 6. If a client says their booking or enquiry would not send, they may have seen: We could not confirm this came from a person, so it was not sent. What they typed stays in the form. Ask them to reload the page and try again. If that does not work, they can try another network or turn off their ad blocker, or contact you directly. Guide: https://bookatu.com/en-nz/help/your-booking-page ### Why my booking page is not live yet Your booking page stays private until it is ready to publish, and until then anyone who opens your link sees a short 'coming soon' message instead of your services. Publishing always needs your email confirmed. It needs Stripe only when something on your page takes money online: deposits, a card on file for your cancellation policy, or products sold in your online shop. If you take payments another way, turn those off and your page can go live without Stripe, as long as it has a service clients can book, a team member to book with, and a phone number or email. Almost everyone who gets stuck here has already been to Stripe once. Stripe asks for a few details in stages, and it is easy to reach the end of one stage, close the tab, and assume that was it. Knowing that is usually all it takes to finish in a couple of minutes. How to use it: 1. Open Settings and look at the Booking page section, which says what is in the way. 'Connect Stripe to publish' means you have not started Stripe yet, and 'Finish Stripe to publish' means you started and there are still a few details to give. Underneath, it lists what needs Stripe, each with a link to switch it off if you would rather not use Stripe. 2. Press the button in that panel. If you have started setting up Bookatu payments, it opens Settings, Payment options, where you finish inside Bookatu. Otherwise it takes you to Stripe and picks up exactly where you left off, so nothing you have already entered is asked for twice. 3. Stripe usually wants three things: who you are (a photo ID or a few personal details), what the business is, and a bank account to pay you into. The bank account is the step people most often stop at. 4. Come back to Settings when Stripe says you are done. The Publish button turns on, and pressing it puts your page live at once. 5. If Stripe says everything is complete but Settings still asks you to finish, tell us. That is our problem to fix, not yours, and it is worth reporting rather than trying again. Guide: https://bookatu.com/en-nz/help/why-my-page-is-not-live ### Connecting Stripe for payments Stripe is the service that securely takes card payments, so anything that charges a card (deposits, gift card sales, packages, memberships and shop orders) runs through it. Under How do you want to get paid? you choose Bookatu payments, which you set up inside Bookatu, or your own Stripe account. Either way, Stripe holds your money and pays it into your bank. Bookatu never holds your money, never sees card numbers and never takes a cut of your bookings. Once you can take payments, deposits and online payments work for real. Your booking page needs this to go live when the page takes money online (deposits, a card on file or shop sales); a page without those can go live without it. See Why my booking page is not live yet if the Publish button is still off. How to use it: 1. Open Settings, then Payment options. Under How do you want to get paid?, pick one and press Continue. If you picked Bookatu payments when you signed up, it opens on your business details instead. Only the owner can change payments. 2. Bookatu payments is marked Recommended. Clients pay by card on your page, and Stripe pays the money into your bank. Check your business details and press Looks right, then fill in About you, which is Stripe's own form. Your bank and ID numbers go straight to Stripe. 3. When it says You can take payments, press Add your bank and fill in Where should Stripe pay you?. Until you add a bank, payments collect in your Stripe balance and nothing is lost. 4. Connect my own Stripe is for when you already use Stripe or want Stripe's own dashboard. Press Connect Stripe to sign in or create an account on Stripe's site, then manage your payments in Stripe. 5. Not now lets you take payment in person. Come back to Payment options when you want card payments. 6. Bookatu takes no commission. You pay Stripe's card fees, which come off each payment before it reaches your bank, and Bookatu adds nothing on top. 7. Once you are set up, the Bookatu payments card says Active, with Payouts, Update details and Fee invoices. If Stripe needs one more thing from you, a banner says so: press Fix now. Until Bookatu payments has taken a payment or saved a client's card, you can still move to your own Stripe: press Connect my own Stripe on the same card. Then turn deposits on under Settings, Deposits & cancellations. 8. Use test mode while you practise, with no real money, then switch to live mode to take real payments. Do a full practice booking before you go live. 9. Building your own version of Bookatu? Self-hosted setups configure their own Stripe keys instead. That developer detail lives at /developers, separate from this owner setup. Guide: https://bookatu.com/en-nz/help/connecting-stripe ### Adding your team Each team member can have their own account and their own set of services and hours. Clients can pick who they want to see. Everyone sees only their own day, bookings are shared out correctly, and you avoid double bookings. How to use it: 1. Open Settings and tap Team and add each person. 2. Tick which services they offer and set their working days. 3. Turn 'bookable' on for anyone clients should be able to choose. 4. To let someone sign in to your admin, use Give someone a login, and always set a temporary password. Someone new to Bookatu signs in with it straight away. Someone who already has a Bookatu login gets an email instead, and joins once they accept. The link in it works for 14 days, a newer invite replaces an older one, and they must sign in with the email it was sent to. Guide: https://bookatu.com/en-nz/help/inviting-your-team ### Running more than one branch Branches are for one business with more than one address. Each branch has its own opening hours, phone, email and time zone. Staff, services and rooms can belong to a branch, or to none, and none means every branch. You run every site from one account while each branch keeps its own day. Clients book the branch that suits them, and nothing you already set up has to move. How to use it: 1. Open Settings, then Branches, and press Add a branch. Give it a name, its address, phone and email, and its time zone, which decides what today means at that branch. Then set its opening hours. Branches is for owners and admins with Manage the business. 2. Put staff, services and rooms in a branch, or leave them out so every branch shares them. 3. Press View this branch to see the admin for that one branch. 4. When more than one branch is open, clients choose one when they book. 5. A branch you switch off takes no new bookings. Removing a branch makes its staff and services shared again. Guide: https://bookatu.com/en-nz/help/running-more-than-one-branch ### The calendar A live view of every booking, colour coded by status. You can drag a booking to a new time, add notes, and see gaps. It is the one screen your front desk lives in. Moving a client is a drag and drop, not a phone call. How to use it: 1. Open Today, Calendar. 2. Drag any booking block to a new time or staff column to reschedule. 3. Click a booking to see details, add a note, or mark it complete or a no-show. 4. When more than one of your team takes bookings, Team shows everyone side by side, over 1 week or 4 weeks. 5. Day, Week, Month and Team each have a full screen that fills the browser window. Press Full screen above the calendar to open it. To leave, press Exit full screen or the Escape key. 6. To bill a booking without leaving the calendar, open it and press Invoice. Under Who pays, choose the client, or a company (with a PO reference if they gave you one). Under How they pay, choose a Payment link they pay by card online, or an Invoice they pay by bank transfer. Then press Send to email it to them, or Create, don't send. It needs Invoices switched on in Settings, Messaging & retention, and a role with Manage the business and See analytics & earnings. Guide: https://bookatu.com/en-nz/help/calendar ### Who booked it, booking history and the bookings CSV Every booking says who made it and how, such as Booked by Sam · Phone, on its page and in its panel on the calendar. Its History card lists everything recorded for it, oldest first: what happened, who did it and when. On the calendar, Export bookings (CSV) downloads your bookings for the days you choose. When a client says they never booked that time, or a booking moved and nobody remembers why, the answer is on the booking. The CSV puts every booking in one file for your accountant, a spreadsheet or your own reports. How to use it: 1. Open a booking from Appointments, or tap it on the calendar and choose Full details. Booked by names who made it: a team member, Client online, an API key or an app you connected by the name you gave it, AI assistant with the name of whoever confirmed it when your dashboard assistant made it, or Not recorded for older bookings. A client is never named there. 2. After the name comes how it came in, such as Online, Phone, Walk-in or In person or other. Anyone who can open the booking sees this line, on its page and in its panel on the calendar. 3. Further down, History lists each change, such as a move or a paid deposit, with who did it and the time on your business's clock. It shows to anyone with Manage the business, which owners and admins have by default, and the Audit log button opens the full trail. Bookings made before the audit trail began have no history. 4. To download bookings, open Today, then Calendar, and open Export bookings (CSV) below the calendar. Choose From and To, up to 366 days, a Status and, with more than one branch, a Branch. It starts on the month on screen. Tap Download CSV. 5. The file has Date, Time, Client, Service, Staff, Status, Checked in and Branch, in your business's time zone. For someone who sees everyone's calendar it also has each client's Email and Phone, a Tags column when a booking in it has a tag, and one column for each booking question, headed Q: and the question. 6. Downloading needs See analytics & earnings and Export data, which owners and admins have by default. Someone who only sees their own calendar gets only their own bookings, without contact details. Each download is recorded in the Audit log. Guide: https://bookatu.com/en-nz/help/booking-history-and-bookings-export ### Deposits A deposit is a small amount (a flat figure like $20, or a percentage) charged when a client books online. It comes off their final bill. Clients who pay something upfront almost always turn up. It is the single best way to cut no-shows. How to use it: 1. Connect Stripe first (see Connecting Stripe). Without it, deposits cannot charge. 2. Open Settings, then Deposits & cancellations, and turn on Ask for a deposit to confirm a booking. 3. Set a Default deposit as a flat amount. To charge a percentage instead, enter it in Or deposit percentage. 4. To only charge risky clients, turn on the No-show shield instead of charging everyone. Guide: https://bookatu.com/en-nz/help/deposits ### No-show shield A smart version of deposits. It looks at each client's history. Loyal regulars with a clean record book with no deposit. New clients or anyone with past no-shows are asked for a deposit. You protect yourself from no-shows without putting up a barrier for your best, most loyal clients. They get a friction-free booking, you stay protected. How to use it: 1. Connect Stripe and set a deposit amount first. 2. Turn on 'No-show shield' under Settings. 3. That is it. The app decides per client who needs to pay. Guide: https://bookatu.com/en-nz/help/no-show-shield ### Charge a fee for no-shows and late cancellations With card holds on, clients save a card when they book online, and nothing is charged then. If they cancel late or do not turn up, the fee you set waits for you to charge it or let it go. Card holds are available to businesses in New Zealand, Australia and the United States, except clinics in the United States. A late cancellation or a no-show leaves a slot you rarely get back. A saved card helps clients take their booking seriously, and you decide each time whether a fee is fair. How to use it: 1. Open Settings, then Cancellation policy, and turn on Require a card to hold the booking. The note at the top shows whether card holds are live for your business. 2. Set the Free cancellation window, in hours, and a Maximum fee (cap), the most a client can ever be charged. 3. Under If a client cancels inside the free window, and again under If a client does not attend (no-show), choose the Fee type: No fee, % of service or Fixed amount. Enter the percent or the amount, then choose What counts as a no-show. 4. Check What a client would pay, which shows each fee on an example service, then press Save cancellation policy. Keep any fee in line with your real loss, for example less the earlier someone cancels. A flat full-price fee may not hold up. 5. When a fee is earned it waits under Money, then No-show fees, marked Did not turn up or Cancelled late. Press Charge to take it, and the client is emailed a receipt, or press Let it go. Nothing is ever charged on its own. 6. The No-show fees page is for owners and admins whose role has Refund orders. Guide: https://bookatu.com/en-nz/help/no-show-and-late-cancellation-fees ### Surcharges for public holidays and busy times A surcharge adds a percent or a fixed amount to bookings that start on the dates or at the weekly times you choose, such as 15% on public holidays or $10 on Saturday evenings. You set them in Settings, under Surcharges. A business has none until you add one, so until then prices are the same on every day and at every time. Opening on a public holiday costs you more, and a surcharge lets the price say so without changing your service menu. Clients who book online see the extra amount before they book, so nobody is surprised at the counter, and an online booking is never charged more than the client was shown. How to use it: 1. Open Settings, then Surcharges (under Essentials), and tap Add a surcharge. Changing surcharges needs Manage the business, which owners and admins have by default. 2. Type the Name clients see, such as Public holiday surcharge. Choose Percent of the price (a whole number from 1 to 100) or Fixed amount. Then pick dates on the calendar, add a weekly time under Every week, or both. A booking that starts at the end time of a weekly time is not surcharged. 3. To cover public holidays without picking them one by one, tick Use public holidays and choose New Zealand or Australia. It uses the national list for 2026 to 2028, with the Mondayised and observed days. Regional anniversary days and state holidays are not on it, so pick those on the calendar. Clients are told which holiday it is, such as Public holiday surcharge (Christmas Day). 4. Leave Every service ticked, or untick it and choose the services. With more than one branch, Where keeps it to one. Check the preview, then tap Add surcharge. To stop one, tap Switch off. Bookings already made keep the price they were made with. 5. What clients see: on your booking page and website widget, the times a surcharge covers are marked, such as +15%, with a line naming it. The review before they book shows the total with it included, and their confirmation and receipt show it on a line of its own. A percent deposit is worked out on that total. If the price of a time goes up while they are booking, they are asked to check the time again instead of being charged more. 6. When two surcharges cover the same time they are not added up: only the one that comes to more money applies. A percent is worked out on the price before any promo code, and the code never comes off the surcharge. A fixed amount is added once per booking, whatever the group size. A free booking is never surcharged. 7. When your team books a time with a surcharge in New booking, it shows before you save. Tick Waive the surcharge to leave it off. Waiving needs Refund orders, which owners and admins have by default, and it is recorded in the Audit log with your name. 8. Moving a booking, by your team or by the client, prices it again at the new time and keeps the smaller of the two surcharges. Moving it off a holiday drops the surcharge, and moving it onto one adds nothing. Guide: https://bookatu.com/en-nz/help/surcharges ### Smart waitlist When you are fully booked, clients can join a waitlist. When a slot opens, you see the waiting list ranked by how much each client spends with you, so you can offer the spot to your best client first. Cancellations stop being lost money. You fill the gap, and you reward your highest value clients. How to use it: 1. Clients join automatically from the booking page when a day is full. 2. Open Today, Waitlist to see who is waiting, ranked by value. 3. Tap a client to offer them the open spot by message. Guide: https://bookatu.com/en-nz/help/waitlist ### Inbox and channels One shared inbox for the channels you connect, such as your own texting number, WhatsApp and email. Every message lands here so nothing is missed. Your team stops juggling five apps. Every conversation, and every booking that comes from it, is in one place. How to use it: 1. Go to Inbox, then Channels, and connect the channels you use. Facebook Messenger and Instagram are not ready to connect yet. 2. Messages appear in Inbox. 3. Reply from there, or tap 'Send booking link' to turn a chat into a booking. Guide: https://bookatu.com/en-nz/help/inbox-and-channels ### AI receptionist and auto-reply When a new client messages you, the assistant replies using your real services, prices and hours, and sends your booking link. It hands anything tricky (like a complaint) to a human. It only ever talks about your business, and politely declines anything off topic. You capture clients who message after hours or while you are with someone, without hiring a receptionist. How to use it: 1. Go to Inbox, then Channels, and turn on 'Auto-reply new chats'. 2. The free version answers booking, hours and price questions. 3. For smarter replies, also turn on 'AI receptionist (smart conversational replies)'. This AI version (an add-on) writes natural replies. It needs an AI key configured. Guide: https://bookatu.com/en-nz/help/ai-receptionist ### Intake and consent forms Build an intake or consent form with the fields you need (a health history, consent statements, a signature and more), attach it to the services that need it, and clients fill and sign it on their phone before their visit. Already have the form on paper? Upload the PDF and we build the digital version for you to review. No more paper and clipboards, and the first ten minutes of a visit go to the treatment, not admin. You get a signed record, with the client's drawn signature and the exact time, kept on their profile for any treatment that needs one. How to use it: 1. Go to Catalog, then Forms. Build a form by adding fields, or upload your existing PDF under Import from PDF and we draft it for you to check. 2. Review the draft, fix anything the scan missed, and reorder fields with the up and down arrows. Use Edit any time to change a form later. 3. Tick which services require it, then turn it on. 4. When a client books that service they get a link to complete it, filled in with their details. They tick the consent lines and draw their signature. You can also tap Get fill link to share it any time. 5. See who has signed on the Forms page: each form shows how many are signed, and View responses lists every submission. A signed form also shows on the client's profile. Guide: https://bookatu.com/en-nz/help/intake-forms ### Ask clients questions while they book Booking questions are short questions a client answers while they book, such as Is your hair past your shoulders? Ask one for a single service or for all of them, make it required or not, and choose the kind of answer: Short text, Long text, Single choice, Multiple choice, Yes / no, Number or Date. They are asked on your booking page, in your website widget and through the booking API. You learn what you need to prepare before the client walks in, like how long their hair is or whether it is their first visit, without a phone call or a separate form. The answers wait on the booking, where your team already looks. How to use it: 1. Open Catalog, then Services or Forms, and tap Booking questions. Changing them needs Manage the business, and removing one also needs Delete records. 2. Under Add a question, set Asked for to All services or to one service, and choose the Answer type. Type the Question and, if you like, some Help text. For Single choice or Multiple choice, type the Choices one a line. 3. Tick Clients must answer it to book online to make it required, then tap Add question. A service asks at most 10 questions, its own and the ones for all services together. Use Up and Down to change the order. Questions for all services are asked first, then the service's own. 4. Clients see them under A few questions before they book, with the required ones marked. Your team sees the same questions in New booking and can leave any of them blank. 5. The answers show on the booking's page under Booking questions, where your team can fill them in or change them, and in the booking's panel on the calendar. They are in the bookings CSV, one column a question, for anyone who sees every calendar, and in the client's own data export. Changing a question later never changes the answers already given. 6. Do not ask for medical or health details here. For health history, allergies, medication or consent, use an intake form, which is kept apart from the booking and signed by the client. A question that reads as asking for health details is flagged when you save it, so you can move it to a form or reword it. Guide: https://bookatu.com/en-nz/help/booking-questions ### Programs (for trainers and coaches) Build a program of items (exercises, steps, homework) with videos, images and notes, and assign it to a client. They follow it on their phone, tick items off, and can time each one. Your clients keep training between sessions and stay accountable. It is your coaching, in their pocket. How to use it: 1. Go to Catalog, then Programs (called Workouts for trainers and coaches), and create one. 2. Add items with a video link, notes, and optional reps or a timer length. 3. Assign it to a client. They get a private link to follow along and check items off. Guide: https://bookatu.com/en-nz/help/programs ### Newsletters Write an email, choose who gets it (everyone, recent clients, lapsed clients, or your VIPs), add an image, and send now or schedule it. Only clients who agreed to marketing are ever emailed, and every email has a one click unsubscribe. A quiet week is a newsletter away from being a busy one. Reaching lapsed clients is the cheapest marketing you have. How to use it: 1. Go to Grow, Newsletters. 2. Write a subject and message, pick an audience, optionally add an image or a send time. 3. Save as a draft, then send. You will see how many opened it. Guide: https://bookatu.com/en-nz/help/newsletters ### Retention and win-backs The app notices when a regular has not been in for a while and can send a friendly win-back message, plus birthday and thank-you notes. Clients drift away quietly. A gentle nudge at the right time brings them back before they find somewhere else. How to use it: 1. Go to Grow, Retention to see who is due a nudge. 2. Turn on automatic win-backs, birthdays and thank-yous under Settings. Guide: https://bookatu.com/en-nz/help/retention ### Reviews and the Google flywheel After a visit, clients can leave a review. If they are happy (4 or 5 stars) you can point them to your Google page. Unhappy feedback stays private so you can fix it. Recent Google reviews are one of the biggest things that get you found by new local clients. How to use it: 1. Add your Google review link under Grow, Reviews. 2. Review requests are sent after appointments are completed. 3. Happy clients see a 'share on Google' button. Guide: https://bookatu.com/en-nz/help/reviews ### Referrals Give clients a personal link to share. When a friend books through it, both can be rewarded. A referred client is your cheapest and most loyal client. This makes referring you easy. How to use it: 1. Open Grow, Referrals to see and share referral links and track who referred whom. Guide: https://bookatu.com/en-nz/help/referrals ### QR codes (sharing your booking link) The QR codes page gives you everything you need to put booking everywhere: a clean link, a printable QR code for posters and cards, a separate code for each service, one for reviews or gift cards, and a snippet to embed booking on your own website. The easier it is to start booking, the more people do. Put the QR at reception, in your window, on your receipts. How to use it: 1. Open Grow, then Share & QR code. 2. Download a QR as a PNG, print it straight from the page, or copy the link or the website embed code. Guide: https://bookatu.com/en-nz/help/beam ### The Discovery network A shared public page where people can browse local businesses on Bookatu, see ratings and deals, and book. Your business is listed automatically. Extra exposure to new clients, with no commission ever. People browsing for a business like yours nearby can find and book you. How to use it: 1. You are listed automatically. To opt out, ask us to set your business to not discoverable. Guide: https://bookatu.com/en-nz/help/discovery-network ### Gift cards Clients buy a gift card on your booking site, and the recipient gets a code. Once the code is redeemed, by the client on their account page or by your team, the value becomes credit on their account. That credit pays the deposit when your team books them in and it covers the whole deposit. Gift cards are money in the bank today for services later, and they bring in brand new clients (the people receiving them). How to use it: 1. Clients buy from the Gift cards link on your booking site. 2. You can also issue one manually under Catalog, Gift cards. 3. Connect Stripe so online purchases can be paid. Guide: https://bookatu.com/en-nz/help/gift-cards ### Gift card promo codes, resends, reissues and history Every gift card has its own page, opened from the list on Gift cards, with what is left on it, who it is for and everything that has happened to it. From there you can send the gift card email again or reissue the card with a new code. A promo code can also take money off the price of a gift card bought online, once you allow it. When a client has lost their code, or a card went to the wrong inbox, you can sort it out in a few taps and see exactly where the money went. A gift card offer, such as 10% off cards in December, runs on the promo codes you already have. How to use it: 1. To let a promo code work on gift cards, open Grow, then Promo codes. Tick Can be used on gift cards when you create the code, or tap Allow on gift cards beside one you already have. Every code is off for gift cards until you do. 2. The code takes money off the price, never the card's value: a $100 card at 10% off costs $90 and is worth $100. The buyer types it under Promo code on your gift card page and sees what they will pay before they check out. The code has to be live, not expired and have a use left, and it counts as used once the payment goes through. A code that would make a card free is refused, and cards you issue yourself never carry one. 3. Open Catalog, then Gift cards, and tap a card under All gift cards to open its page. History lists each step, oldest first: issued (with any promo code and what it took off), paid, emailed, redeemed and into whose credit, voided and reissued. Anyone with Manage the business also sees who did each step. 4. Resend email sends the gift card email again to the recipient on file, with the code and what is left on it. You cannot type a different address here. It shows for an active card with a recipient email, to anyone with Adjust loyalty and gift cards. Without that permission a card's code shows only its last four characters. 5. Reissue with a new code voids the old code at once and moves what is left on it to a new code, which is emailed to the recipient if there is an address on file. Tap Yes, reissue to go ahead, or Keep this card. Reissuing needs Adjust loyalty and gift cards and Manage the business. Each card's History names the other by its last four characters. 6. Tap Download CSV at the top of Gift cards for every card, newest first, with the columns Code, Status, Original value, Remaining value, Currency, Issued, Expires, Recipient email, Promo code and Promo discount. Codes show only their last four characters. The download needs Export data, Recipient email is filled in only for someone who can also manage the business, and each download is recorded in the Audit log. Guide: https://bookatu.com/en-nz/help/managing-gift-cards ### Packages (prepaid bundles) A package is a deal where a client pays an amount upfront and gets a larger amount of credit to spend (for example pay $200, get $250). The credit sits in their wallet. You get cash upfront and the client commits to coming back several times. Great for courses of treatment. How to use it: 1. Go to Catalog, Packages and create one (price, and the credit value the client receives). 2. Clients buy it from the Packages link on your booking site. Guide: https://bookatu.com/en-nz/help/packages ### Memberships A membership charges the client every month and can give them monthly credit and perks. It keeps charging until cancelled. Predictable monthly income (the holy grail) and clients who feel like members, not one-off visitors. How to use it: 1. Go to Catalog, Memberships and create a plan (monthly price, any monthly credit, perks). 2. Clients join from the Memberships link on your booking site. Needs Stripe connected. Guide: https://bookatu.com/en-nz/help/memberships ### Wallet credit and loyalty Gift cards a client redeems, packages and membership credit all add to their account credit. When your team books a client in and their credit covers the whole deposit, the deposit is paid from it. When a client books online, the deposit is paid by card and their credit is left alone. Loyalty points reward repeat visits. Credit a client has bought or been given pulls them back to spend it with you, and points give your regulars one more reason to return. How to use it: 1. Credit needs no setting up. It builds up as clients redeem gift cards, buy packages or get membership credit. 2. To run points, open Settings, then Loyalty & rewards, and switch on Run the Bookatu Rewards points programme. 3. Points are earned on what the client actually paid, once the visit is done. If that money is refunded, the points it earned are taken back. Guide: https://bookatu.com/en-nz/help/wallet-and-loyalty ### Developer API and AI agents (MCP) Bookatu has a public REST API and an MCP server. The API lets other software work with your business data, and the MCP server lets an AI assistant you connect to your own account, such as Claude, check your availability and make or move bookings for you. You can ask your own AI assistant to find a free time or book a client in, and it works from your real calendar. The API also lets you connect Bookatu to other tools you use. How to use it: 1. At a high level the public API can read your business details, services, staff and availability, create a booking, manage your customers, and read, create or cancel appointments. 2. Create an API key under Settings, API & monitoring, and use it to authenticate your requests. Making a key or a webhook, and connecting an app, needs a confirmed email: until you have opened the link we emailed you, the page says Confirm your email first. 3. Your own website can send its enquiry form straight into Leads, with a key that has Add enquiries ticked. The developer docs show how. 4. If a key stops working because the person who made it is no longer on your team, or their role lost the right, Bookatu tells you on your alerts and by email. Website enquiries it sends are held for 30 days so nothing is lost. Ask the AI assistant in your dashboard to move them into Leads, then make a new key on the Developer API page and use it in place of the old one. 5. A key our support team made for you is labelled as made on behalf of your business. You can revoke it like any other key. 6. If Bookatu ever suspends a business, its API keys are switched off, and each request answers with a note to contact Bookatu support. 7. See the full reference, including request and response details and webhooks, at /developers. Guide: https://bookatu.com/en-nz/help/api-and-mcp ### Test mode and sandboxes A sandbox is a test business inside Bookatu, made for building and testing an integration. It answers the same API with the same booking rules and sends the same webhooks as a live business, but every email, text and notification it would send is kept in its Outbox, and its payments go through a simulated checkout unless it is set up for Stripe test mode. The full developer guide is Testing with a sandbox, at /developers/testing. Your developer can try every call, deposits and webhooks included, without touching your real business, your clients or a real card. A sandbox says Test mode on every page of its admin and Test business on its booking pages, and it is never listed anywhere public. How to use it: 1. Sign in with a Bookatu account whose email is confirmed and open /developers/sandbox. You don't need a business on Bookatu. Pick a name, a time zone and a currency, accept the test-mode terms and make your sandbox. You can have up to 3 at a time. If the page says making sandboxes is switched off at the moment, they are not open yet. 2. Each sandbox comes with sample staff, services, clients and bookings, and a first test key with every scope. Test keys start bk_test_ and live keys start bk_live_. Make more keys and webhooks in the sandbox's own admin, under Settings, then API & monitoring. 3. A test key works only on a sandbox, and a live key only on a live business. The other way round is refused before anything runs, with 403 LIVEMODE_MISMATCH, and every answer says which kind of business it reached in livemode. 4. What the sandbox would have sent is under Outbox in its admin, and every simulated payment it made is under Test payments, beside it: paid, declined, abandoned or refunded. Its simulated checkouts have Pay (test), Decline (test) and Abandon buttons instead of a card form. Never type a real card number into a sandbox. The simulator makes events happen now, such as a deposit being paid. 5. Payments can also go through Stripe test mode instead of the simulator, where it is offered. On Test payments, choose Connect a Stripe test account and fill in Stripe's pages with Stripe's test details only, never your real ID or bank account. If you stop part way, Continue on Stripe takes you back, and Check again shows whether the account is ready. Then choose Turn on Stripe test mode. New payments open Stripe's own checkout page, where you pay with a test card such as 4242 4242 4242 4242, and they are listed in Finance. No real money moves. Switch back to simulated payments whenever you like. 6. Reset wipes a sandbox and fills it with fresh sample data, and Delete removes it, both from your sandboxes page. A sandbox nobody uses for 30 days is deleted, and you get an email 7 days before. 7. Every call, with examples, is in Testing with a sandbox at /developers/testing, and as markdown at /developers/testing.md. When it works, Going live at /developers/going-live says how to switch to a live business's key. Guide: https://bookatu.com/en-nz/help/test-mode-and-sandboxes ### Check out bookings from another point of sale The checkout hand-off is one address with two calls: GET and POST /api/v1/{slug}/appointments/{id}/checkout. GET returns what the booking comes to: each service and extra with its lineId and who did it, the price, discounts, tax lines, the deposit already paid, and dueCents, which is exactly what to take. POST records the sale your point of sale took, completes the booking and links the sale to it, using the same checkout code as Bookatu's own point of sale. Nobody rings up a visit twice, and the booking, the sale, staff credit and the money line up in Bookatu as if its own point of sale had taken it. Posting is idempotent on your externalSaleId, so a retry after a dropped connection returns replayed: true and writes nothing. How to use it: 1. Owners and admins make the key in Settings, then API & monitoring, under API keys. In What this key may do, tick both boxes on the Checkout at another point of sale row: See what a booking comes to at checkout (checkout:read) and Check bookings out from another point of sale (checkout:write). These are opt-in, and a key made before scopes never carries them. The maker must be able to see everyone's calendar (for checkout:read) and edit the calendar (for checkout:write). Add See bookings (bookings:read) to list the day's bookings with GET /appointments, and See clients (customers:read) if your point of sale needs the client's name, email and phone. Without it the client comes by id only. 2. Send the key as Authorization: Bearer on every call. Call GET /api/v1/{slug}/appointments/{id}/checkout and ring up its lines. checkout.allowed says whether the booking can be checked out now, and checkout.blocked gives the reason: not_live, deposit_pending, already_checked_out or invoiced. invoiced means the booking is on an invoice and is paid there, so do not take money for it at your point of sale. 3. Take the money, then POST to the same address with { externalSaleId, source, amountCents, currency, tender, tipCents, tipSplit, lines }. externalSaleId is your point of sale's own sale id. source names your point of sale, such as moneris_mgr (it defaults to external and can never be bookatu). amountCents must equal dueCents. currency is optional but must be the business's. tender is card, cash or other. lines, as [{ lineId, staffId }], credits a line to someone else. 4. Posting the same externalSaleId from the same point of sale again returns the original sale with replayed: true. Refusals write nothing and give a reason: 400 card_number (externalSaleId or source looks like a card number, which is never accepted); 409 amount_mismatch (with expectedCents), already_checked_out, external_sale_used, lines_changed (read the checkout again), not_live, deposit_pending or invoiced (the booking is paid on its invoice); 422 currency or tip_split; 503 while the hand-off is still being switched on for the business. 5. To hear about every checkout, add a webhook in the Webhooks card on the same page and tick booking.checked_out under Only if you tick it. It is never sent to an endpoint that takes all events. It also fires for checkouts at Bookatu's own point of sale (sale.source bookatu), with the same payload as GET and the client by id only. 6. The full reference, with every field and example, is on the developer docs at /developers#checkout-handoff, and as markdown at /developers.md. Guide: https://bookatu.com/en-nz/help/checkout-from-an-outside-till ### Let AI tools read Bookatu's guides Bookatu publishes its help centre, blog, engineering blog and developer docs in forms AI tools read easily. /llms.txt lists every page with a link to its markdown copy, /llms-full.txt carries the content in full, and every help, blog and engineering page, and /developers, has a plain markdown copy at its address plus .md. A public docs MCP server at https://bookatu.com/api/mcp/docs lets any MCP client search them with no API key. When you or your developer ask an AI tool how Bookatu works, it can answer from the real guides instead of guessing. The assistant in your dashboard uses the same guides, so a how-do-I question gets the real steps and a link to the guide. How to use it: 1. Give an AI tool https://bookatu.com/llms.txt as the index, or https://bookatu.com/llms-full.txt for one file with full guides, FAQ answers and the complete API reference. 2. For one page, add .md to its address, for example https://bookatu.com/help/deposits.md or https://bookatu.com/developers.md. A translated guide has its copy under its market, such as /de-de/help/deposits.md. Each copy starts with front matter naming the page, its language and its dates, so the tool can cite it. 3. In an MCP client, add the server https://bookatu.com/api/mcp/docs. It needs no API key or sign-in, can only read, and never sees a business's data. Its tools are search_help, get_help_article, search_blog, get_blog_post, search_developer_docs, which finds the endpoint, webhook or guide on /developers a question is about, and get_plans, which gives the public plans, add-ons and trial length. Pass section engineering for the engineering blog, and language for any of the 14 help languages. 4. To act on your own business, such as checking availability or making a booking, use the business MCP server at https://bookatu.com/api/mcp with an API key instead (see Developer API and AI agents). 5. The main AI crawlers, including GPTBot, ClaudeBot, PerplexityBot and Bingbot (which grounds Microsoft Copilot), may read these public pages. robots.txt keeps them out of admin, account, sign-in and client pages. 6. In your dashboard, owners and admins can ask the assistant a how-do-I question. It answers from up to three matching help guides, in your business's language, and adds a Help guide link and an Open in your dashboard link under the reply. Guide: https://bookatu.com/en-nz/help/reading-bookatu-docs-from-ai-tools ### Manage your blog from an AI tool The business MCP server at https://bookatu.com/api/mcp has six blog tools: blog_list_posts, blog_get_post, blog_create_post, blog_update_post, blog_publish_post and blog_unpublish_post. They work only on the blog of the business the key or connected app belongs to. There is no delete tool, so removing a post stays something you do in the dashboard. You can ask your AI assistant to draft a post, tidy one up or take one offline without opening the editor. The tools accept and refuse the same values the editor does, a post from another business never resolves, and a new post stays a draft unless the AI is told to publish it. How to use it: 1. Owners and admins make a key in Settings, then API & monitoring, under API keys. In What this key may do, on the Blog, forms and email drafts row, tick See posts, forms and email drafts (content:read) for the two read tools and Write posts, forms and email drafts (content:write) for the four that write. Both need 'Manage the business'. A key made before scopes needs read and write access to write, and an app connected through sign-in needs Read and write when you approve it. 2. Point your MCP client at https://bookatu.com/api/mcp and send the key as Authorization: Bearer bk_live_... on every request. tools/list shows only the tools the key can call, and a read-only credential is refused on every write tool. 3. blog_list_posts lists drafts and published posts, newest first, with an optional status of all, draft or published. It returns id, slug, title, status, publishedAt and excerpt, never the body. blog_get_post returns one post in full, markdown body included, by postId or slug, and drafts are visible. 4. blog_create_post needs a title (2 to 140 characters) and a markdown body (up to 50,000 characters), with an optional excerpt (up to 300) and an http(s) coverImageUrl. The slug comes from the title and is made unique. It saves a draft unless you pass publish: true, which puts the post live at once. 5. blog_update_post takes a postId and only the fields to change. Everything else is left as it is, and the slug never changes, so a live link keeps working. An empty excerpt or coverImageUrl clears it, and status draft or published changes who can see it. blog_publish_post and blog_unpublish_post only change the status. The first publish sets publishedAt, and later unpublishing or publishing again keeps that date. 6. The tools cannot set the search title, search description or tags, and an update leaves them as they are. Set them in the editor under Grow, then Blog, in Search & sharing. A bad value is refused with an error rather than trimmed, and a post id from another business answers Post not found. Full tool schemas are at /developers. Guide: https://bookatu.com/en-nz/help/manage-your-blog-from-ai-tools ### Tax and accounting A tax tool that records the tax on every completed visit, shows what you owe for a period, reconciles it against the payments you took, and exports a file you can import into Xero or QuickBooks. Tax time stops being a scramble. You see your tax collected for the month, quarter or year at a glance, and your accountant gets a tidy export instead of a shoebox of numbers. How to use it: 1. Open Tax under Settings and turn on tax once you are registered. 2. Set your rate, the tax name (GST, VAT or sales tax) and your registration number. 3. Pick a period to see sales, tax collected and a reconciliation. 4. Export a filing CSV, or an Xero or QuickBooks file, for your accountant. Guide: https://bookatu.com/en-nz/help/tax-and-accounting ### Client notes and photos A private record on each client where your team can add timestamped notes (formulas, preferences, allergies) and before and after photos. Important notes can be pinned to the top. Every visit feels personal and consistent, even with a different team member. Pinned allergy notes keep clients safe, and before/after photos show progress. How to use it: 1. Open a client from Clients. 2. Add a note in the Notes section, and pin allergies or formulas so they show first. 3. Upload before/after photos in the Photos section. They are visible to your team only. Guide: https://bookatu.com/en-nz/help/client-notes-and-photos ### Tags for clients and bookings Tags are your team's own labels, such as VIP or New client. Each one has a name, a colour and what it is for: clients, bookings or both. They show on the calendar, the client list and each booking, filter your client list, and can be the audience of an email campaign. What your team keeps in their heads becomes visible to everyone at a glance. A tag on the calendar tells whoever is on shift what to expect, and a tagged group of clients is one tap away when you want to email them. How to use it: 1. Open Clients and tap Tags. Under Add a tag, type a Name, up to 40 characters, and choose For: Clients and bookings, Clients only or Bookings only. Pick a Colour and tap Add tag. A business can have up to 200 tags. Making and changing tags needs Manage the business. 2. To tag a client, open them from Clients, choose a tag under Add a tag in their Tags section and tap Add. To tag a booking, open it and use its Tags card, which needs Edit the calendar. Tap the cross on a tag to take it off. 3. To filter the client list, tap tags in the Tags row above it. The list shows the clients who have every tag you picked, and you can bookmark the page to come back to that view. 4. On the calendar, a booking shows its tags as small coloured chips, two and then a count of the rest, or as dots on a short booking. Its panel and its page show them all. 5. To email a tagged group, open Grow, then Newsletters, write your campaign, and on the Audience step choose Clients tagged with that tag. Only clients who agreed to marketing are emailed. 6. To rename, recolour or delete a tag, open Change or delete under it on the Tags page. Deleting takes it off every client and booking, asks you to confirm when it is in use, and needs Delete records. 7. Tags are for your team. They don't show on your booking pages, client emails or the client app, and they are left out of AI assistants and webhooks. Apps you connect with an API key that can see clients or bookings do read them. A client who downloads or asks for their data sees the tags on them, so name tags as you would say them to the client, and keep medical details in the client's record, not in tags. Guide: https://bookatu.com/en-nz/help/client-and-booking-tags ### Blocking off time A way to block off time on your calendar so it cannot be booked online. Block it for everyone or one team member, with an optional reason. You can also block a room or chair, and make a block repeat every week. Lunch, training, a dentist appointment or a public holiday stays protected. Blocked time is removed from online availability straight away and shown on your calendar. A blocked room only takes away the services that need it, and bookings go to another free room. How to use it: 1. Open the Calendar and find the Blocked times panel. 2. Pick a date, a start and end time, who it applies to, and an optional reason. Tick Repeats weekly to choose the days and how long it repeats, up to two years. 3. The block appears on the calendar and clients can no longer book that time. When you remove a repeating block, choose This one, This and following or The whole series. Guide: https://bookatu.com/en-nz/help/blocking-off-time ### Funding to grow A finance area that shows your earnings and gives an estimate of revenue-based funding you may be a fit for, based on your booking activity. You can register interest in one click. When you want to invest in a new chair, room or hire, this shows what funding might be available and lets you put your hand up, without leaving your booking software. How to use it: 1. Open Finance to see your earnings over the last 30 days. 2. Review the funding estimate. It is an estimate, not an offer of credit, and any funding is provided by a licensed partner subject to approval. 3. Register interest and we will be in touch when funding opens for your account. Guide: https://bookatu.com/en-nz/help/funding ### Automatic reminders Automatic messages around each appointment: a confirmation when the client books, and a reminder before the visit, so the booking stays top of mind. Email reminders are always included on every plan. Text (SMS) reminders are a separate, faster channel that depends on your plan. Most no-shows are simply forgotten appointments, so a timely reminder is the cheapest way to fill more of your schedule. A text is read fastest of all, which is why SMS cuts no-shows the hardest. How to use it: 1. Reminders are on by default for new bookings. Clients get a confirmation when they book and a reminder before the visit, using your business name and the visit details. 2. Email reminders are included for everyone. Text reminders are a paid channel and depend on your plan (see SMS text reminders and the Solo SMS add-on). Bookatu's numbers can only send texts in some countries so far, and that guide lists them. Elsewhere the settings show that texts are not available in your country yet, and email reminders go out as normal. Bookatu's numbers send booking confirmations and appointment reminders only. Other texts need your own texting number. 3. Adjust the tone and the timing of reminders in Settings, Messaging & retention. Guide: https://bookatu.com/en-nz/help/automatic-reminders ### Choosing which messages clients get Bookatu sends clients some messages by itself, such as booking confirmations and reminders. The switch Only send client messages when we press Send, in Settings under Client messages, pauses all of them at once. The same page has a switch for each message by email and by text. Those keep their settings while it is on, so turning it off brings each back as it was. Some businesses would rather write to every client themselves, or send their messages from their own website. With the switch on, nothing reaches a client unless someone on your team chose to send it, and you can still see what was held. How to use it: 1. Open Settings, then Client messages, and turn on Only send client messages when we press Send. To stop just one message, switch it off by email or by text on the same page. Changing these needs Manage the business, which owners and admins have by default. 2. Anything you send yourself still goes, such as Send a payment link or a reply from the Inbox. So do messages a client asks for, such as a sign-in link or a gift card they bought. Emails to your own team are not affected. 3. A held message is never sent by itself later, even after you turn the switch off. See messages we held, on the same page, lists each one with the client and why it was held, and Send now sends one that can still go. It never shows the client's address or the message's words. 4. To leave one booking out, open it and use the Client messages card: Turn messages off stops messages about that booking, and Turn messages on brings them back. It needs Edit the calendar. 5. The assistant in your dashboard can tell you how these switches are set, list the messages we held, and send one after you confirm it. It does not change the switches. You do that here. 6. Run your own website on the Bookatu API or MCP? An API key with messages:read reads these switches and the held list, and one with messages:write changes them, for each message by email or text. The developer docs list every message. Send now works there too: a key with messages:write sends a held message, from your website or from an AI tool you connect with that key. Guide: https://bookatu.com/en-nz/help/choosing-which-messages-clients-get ### Cancellations and your cancellation window A cancellation window is the notice you ask clients to give before changing or cancelling. Cancel inside the window and any deposit can be forfeited. Your window is the default for every service, and a service or trip can ask for its own notice instead. A clear, fair policy protects your time without feeling harsh, and the deposit rule discourages last-minute drop-offs. How to use it: 1. Open Settings, then Deposits & cancellations, and set your Free cancellation window. Enter a number and choose hours or days, up to 365 days. Clients can cancel or change for free up to this long before. 2. To ask for different notice on one service or trip, open it in Services. Under Notice to cancel or change, choose Set for this service and enter its own number in hours or days. Use your business default keeps your window. 3. A booking is held to its service's notice. It decides when a cancel is late, and whether a paid deposit is kept when you keep deposits on late cancels. Quick swap and a client cancelling their own class place follow it too. 4. Clients see the policy when they book, and the notice for their booking on their booking page and in their confirmation. 5. When a client cancels, the slot reopens and is offered to your waitlist automatically. Guide: https://bookatu.com/en-nz/help/cancellations-and-your-window ### How clients meet you Each service has a How clients meet you setting. It says where the service happens: at your place, at a venue you set on each booking, at the client's place, in an online meeting, on a trip, or nowhere when you deliver the work. Clients are then told the right place on their booking page and in their booking emails. A trip also has a destination and an itinerary, and any service or trip can ask for its own notice to cancel or change. Clients know where to go without having to ask. A trip shows its destination and never your office address, and an online meeting gives the call link instead of an address. A service that needs more notice, such as a trip, can ask for it while your other services keep your usual window. How to use it: 1. Open Services and add or edit a service. Under How clients meet you, pick one: At your place, At a venue (set on each booking), At the client's place, Online meeting, Trip, or No meeting (work delivered). 2. If you leave it unpicked, Bookatu works it out only where it is clear. A service of whole days is a trip, a service that already gives a Google Meet link is an online meeting, and a business with an address is At your place. The editor then shows Set from this service under the choice. You can pick another one whenever you like. 3. When nothing makes it clear, a Suggested by AI box may show, for example 'Looks like an online meeting. Use this?' It reads only the service's name and description, and it uses your AI allowance. Nothing is set until you press Use this, and Not now leaves it as it was. With AI off or unavailable, no suggestion shows. 4. A trip is a service whose Length in is Whole days. Add its Destination, a country or region in one line. Under Itinerary, add days one at a time, up to as many days as the trip lasts, each with a short title and an optional note. Drag a day to move it, or focus its handle and press the up and down arrow keys. The bin button removes a day. Clients see the days you fill in. 5. Under Notice to cancel or change, keep Use your business default, which shows your own window, or choose Set for this service and enter a number in hours or days. A booking is held to its service's notice. It decides when a cancel counts as late, and so when your rules for late cancels apply. Clients are told it on their booking page and in their confirmation. 6. On the booking page clients open from their confirmation, a Where row shows the place. At your place, it is your business name and suburb or city with Get directions. At a venue, it is the venue with Get directions. At the client's place, it says We come to you, with their address when you have it. For an online meeting, Join the call shows once the call link is made. A trip shows its destination and itinerary days, and No meeting shows no place. The Where line in booking emails and the place in calendar files follow the same choice. 7. For developers: the REST API (POST /services and PATCH /services/{id}) and the MCP tools create_service and update_service take meetingType (null lets Bookatu work it out), noticeHours (0 to 8760, null for your business default) and, for a trip, destination and itinerary. You can also ask the AI assistant in your dashboard to set any of this. Guide: https://bookatu.com/en-nz/help/how-clients-meet-you ### Booking terms clients accept to book online Booking terms are your own words, such as your rules for arriving late or for cancelling, that a client has to accept to book online. You add them in Settings, under Booking terms. While the box is empty, nobody is asked anything. Clients read your rules before they book instead of at the door. Each booking keeps when the client accepted them and exactly which words, so if a client later says they never saw a rule, you can check what they agreed to. How to use it: 1. Open Settings, then Booking terms (under Essentials). Type Your booking terms as plain text, up to 5,000 characters, and tap Save booking terms. Line breaks are kept. Changing them needs Manage the business. 2. Your booking page and website widget then show the terms above Confirm, with a box the client has to tick to book: I have read and accept the booking terms. It always starts unticked. If you change the terms while someone is booking, they are asked to read them again and tick the box once more. 3. A booking made through the booking API has to say the client accepted the terms, or nothing is booked. Bookings your team makes are never asked. 4. Every change to the words is a new version. Under the box you see the one in force now, such as version 3f9a2c1b, and bookings already made keep the version their client accepted. 5. On each booking's page, Terms accepted shows the date and the version the client accepted. The same record is in the client's own data export. 6. To stop asking, empty the box and save. Bookings made before keep their record. Guide: https://bookatu.com/en-nz/help/booking-terms ### Rescheduling a booking Two ways to move a booking to a new time: drag it to a new slot on the calendar, or open the appointment and pick a new time. Plans change. Rescheduling in a couple of clicks keeps the client and your calendar in sync, instead of cancelling and rebooking. How to use it: 1. On the calendar, drag the appointment to its new time. 2. Or open the appointment and choose a new slot. 3. The client is kept up to date automatically. Guide: https://bookatu.com/en-nz/help/rescheduling-a-booking ### The client portal A simple page where a client can sign in with a one-time email link to see their upcoming and past visits, and print a receipt. Clients can self-serve without calling you, and a tidy receipt looks professional and saves you admin. How to use it: 1. Clients open your booking site and choose 'My visits'. 2. They enter their email and get a secure sign-in link, no password to remember. 3. From there they can view visits and print or save a receipt. Guide: https://bookatu.com/en-nz/help/your-client-portal ### Setting your opening hours Your weekly opening hours. They decide the calendar's time range and, crucially, the only times clients can book online. One source of truth means clients can never book when you are closed, and your calendar always reflects your real day. How to use it: 1. Open Settings and set open and close times for each day. 2. Mark days you are closed. 3. Block off one-off breaks or holidays from the calendar's Blocked times panel. Guide: https://bookatu.com/en-nz/help/setting-your-hours ### Special dates and public holiday closures Special dates change your hours for one date and leave your weekly hours as they are. A date can be closed all day, or open with its own hours, such as 10:00 to 14:00 on Christmas Eve. You can also close on every national public holiday of New Zealand or Australia in one go, from today to the end of 2028. Clients can only book the hours you are open, so a holiday, a short day or a one-off Sunday is right on your booking page the moment you save it. There is no changing your weekly hours and remembering to change them back. How to use it: 1. Open Settings, then Opening hours, and tap the Special dates link under your hours. Anyone who can open the page sees the list. Changing it needs Edit the calendar. 2. Under Add a special date, pick the Date and choose Closed all day, or Open, with these hours and set Opens and Closes. Tap Save date. A date can be up to five years ahead, and saving a date that is already special replaces its hours. 3. Holiday hours are one opening and one closing time, with no break. On a date you open, clients can book the team members who work that day of the week, within the hours you set. 4. To close on public holidays, choose your Country under Close on public holidays. The card lists every date it will close. Tap the button under it to close them all. New Zealand has the national holidays, Matariki included, and the Mondayised days. Australia has the seven national holidays and their national weekend days. Regional anniversary days and state holidays are not included, so add yours as special dates. 5. The import only ever closes dates. It never changes a date you have already set, and every date it adds shows in Upcoming special dates, where Remove puts that date back to your weekly hours. 6. Bookings already on a date you close or shorten stay booked. The list says how many there are, so you can move or cancel them on the calendar. 7. Special dates apply to the whole business: every branch, each on its own calendar date. A date cannot be special at one branch only. To keep one person, a room or part of a day free of bookings instead, use Blocked times on the calendar. To charge more on a holiday rather than close, use a surcharge. Guide: https://bookatu.com/en-nz/help/special-dates-and-public-holidays ### Setting up your services Your menu of bookable services. Each has a name, price, how long it takes, and an optional category to keep things tidy. Each one also says how clients meet you for it, and can ask for its own notice to cancel or change. Accurate durations keep your calendar realistic and prevent double-booking, and categories make a long menu easy to scan. How to use it: 1. Open Services and add a service with its price and duration. 2. Group similar services with a category. 3. Choose which team members can perform each service. 4. Under How clients meet you, choose where the service happens: at your place, at a venue, at the client's place, online, on a trip, or no meeting when you deliver the work. Clients are then told the right place for it. 5. Under Notice to cancel or change, keep Use your business default, or choose Set for this service and give it its own number of hours or days. 6. For a trip, set Length in to Whole days. Then add its Destination and, under Itinerary, a short title for each day, up to as many days as the trip lasts. Clients see the days you fill in. 7. A service of whole days, such as a trip or a retreat, shows on your booking page with an Enquire button unless you turn off Show on my page. Clients send you an enquiry rather than booking it there, and the enquiry lands in Leads, where you can book them in. Guide: https://bookatu.com/en-nz/help/setting-up-services ### Missed-call text-back and callbacks When a call to your own Twilio number is missed, the caller hears a short message and gets a text from that number with your booking link. The call shows in your Inbox and the caller is added to Leads, so you can follow up instead of the lead going cold. A missed call is often a missed booking. Catching it as a callback turns a lost lead into a booking. How to use it: 1. Connect your own Twilio number under Inbox, then Channels, on the SMS card. The text goes from that number, never from Bookatu's. 2. Then contact support to finish connecting calls to that number. That part is not on your screens, so we do it with you. 3. When a call is missed, look for it in your Inbox and under Leads. 4. Call or message them back, or send your booking link. 5. Then press Mark contacted on their card in Leads, or Dismiss. Guide: https://bookatu.com/en-nz/help/missed-call-text-back ### Getting found online Every booking page ships with the right titles, descriptions and structured data so search engines and AI assistants understand who you are, what you offer and when you are open. To ask search engines to find your page, switch on List my booking page in search. It is off by default, and search engines decide what they show. When someone searches for your service near them, or asks an AI assistant to book, your business can show up. More visibility means more bookings. How to use it: 1. Fill in your business name, address, hours and services completely. 2. Open Settings, then SEO & analytics, switch on List my booking page in search and press Save search settings. It adds your booking page to the sitemap Bookatu gives Google and Bing. 3. Set your City or town and Region under Settings, Business details. They show on your booking page and go into the details search engines read, so people near you can find you. 4. Add real photos and collect reviews to stand out. 5. Share your booking link everywhere: Instagram, Google, your email signature. Guide: https://bookatu.com/en-nz/help/getting-found-online ### See your bookings in Google Analytics Conversion tracking tells your own Google Analytics each time someone books or sends an enquiry on your booking page. That shows as a lead. Once the booking is paid in full, it shows as a purchase with the amount paid. You see which posts, ads and campaigns bring real bookings, not just visits, so you can put your time and money where it pays off. How to use it: 1. Open Settings, then SEO & analytics. Paste your Google Analytics ID, which starts with G-, and press Save search settings. 2. Switch on Count bookings in Google Analytics. The switch uses your business's own word for bookings, such as appointments. 3. For purchases, make a Measurement Protocol API secret in Google Analytics, under Admin, Data streams, your web stream, Measurement Protocol API secrets. Paste it under Measurement Protocol API secret. Without it only leads are counted. 4. Press Save conversion tracking. To remove it later, tick Remove the saved secret and save again. 5. If you run Google Ads or Meta tags on your own website, the Website widget passes them a lead too (see Add booking to your own website). Guide: https://bookatu.com/en-nz/help/count-bookings-in-google-analytics ### Importing your clients A way to load your current clients into Bookatu all at once, instead of typing them in one by one. You upload a file (a CSV, the kind any spreadsheet can save) with names, phone numbers and emails, and they appear in your client list. You keep your contacts when you switch, so you can message clients and recognise faces from day one. Nobody gets left behind. How to use it: 1. Export your clients from your old tool as a CSV file. Most booking apps have an export option. 2. In Bookatu, open Clients and choose Import. 3. Match up the columns (name, phone, email) and bring them in. 4. If the file is messy or you would like a hand, send it to us and we will help bring your clients across. Guide: https://bookatu.com/en-nz/help/importing-your-clients ### Using Bookatu on your phone Bookatu works in any phone's web browser, with no app to download. Your booking page is built for small screens, and so is the admin, so you can check your day, take a booking or reply to a client from your pocket. Most clients book on their phone, and you are not always at a desk. Everything works on mobile, so you never miss a booking wherever you are. How to use it: 1. Clients just open your booking link on their phone and book. Nothing to install. 2. For yourself, open Bookatu in your phone's browser. You can install it to your home screen for one-tap access (see Installing Bookatu as an app). 3. Check the calendar, add a booking, take a note or message a client, all from mobile. Guide: https://bookatu.com/en-nz/help/the-mobile-experience ### Managing staff, rooms and chairs As well as staff, you can set up rooms or chairs as bookable resources. Bookatu makes sure a service that needs a room only books when both the right person and a free room are available, and it can pick a free room for you. No more double-booked rooms or two people needing the same chair. Your busiest days run smoothly because the calendar knows what each booking needs. How to use it: 1. Add your team under Settings → Team and tick the services each person does. 2. Add your rooms or chairs as resources, and link them to the services that need them. 3. Let Bookatu pick a free room automatically, or set one yourself on the booking. 4. The calendar shows each person and resource, so you can spot clashes at a glance. Guide: https://bookatu.com/en-nz/help/managing-multiple-staff-and-rooms ### Time zones and travel Every time in Bookatu is shown in your business's local time, the time zone you set when you signed up. Clients booking from their phone, wherever they are, see the time in your zone. There is no confusion about when an appointment is. The time a client sees when booking is the time on the clock at your salon or studio. How to use it: 1. Set your business location and time zone in Settings when you start. 2. Clients see all times in your business's time zone automatically. 3. If you travel or work from more than one place, keep your business time zone set to where you actually see clients. Guide: https://bookatu.com/en-nz/help/time-zones-and-travel ### Sharing your booking link on Instagram and Google Your booking page has a short link you can paste anywhere, and a QR code you can print. Share & QR code gives you both, ready to copy. Clients book where they already are. A link in your Instagram bio or on your Google profile turns someone who was only browsing into a booking, instead of leaving them to hunt for your phone number. How to use it: 1. Open Grow, then Share & QR code, and copy your booking link. 2. Put it in your Instagram bio and on your story links. 3. Add it to your Google Business profile, so it sits next to your opening hours. 4. Put it in your email signature, and print the QR code for your window or your counter. 5. To put booking on the website itself rather than link to it, use the Website widget instead. Guide: https://bookatu.com/en-nz/help/embedding-your-booking-page ### Get booked from Google, Instagram and Maps Get booked on Google and social gives you a booking link for each of Google, Instagram, Facebook, Apple Maps and Bing. Each link opens your booking page with a tag on the end, such as via=google, so the booking is labelled with where the client came from. This does not put booking inside Google itself: Bookatu is not one of Google's booking providers, so the link sends clients to your own booking page. Clients can book from wherever they found you, without hunting for your number. Because every link carries its own tag, you can see which place actually brings in bookings and spend your time there. How to use it: 1. Open Grow, then Google & social. Owners and admins can open it. If your booking page is not live yet, or online booking is paused, the page warns you, because until then the links do not open your booking page. 2. Each channel has its own card with your link and a copy button. The Instagram and Facebook cards also show a QR code: scan it with the phone you run those apps on, then copy the link there. 3. Follow How to add it on each card. Google: Edit profile, then Contact, then Appointment links. Instagram: Edit profile, then Links, then Add external link (the Book now action button only works with Instagram's own partners). Facebook: Add action button, then Book now, linked to your website. Apple Maps: in Apple Business Connect, open Locations and select Add next to Actions. Bing: your business details in Bing Places for Business. 4. Google and Bing can take a few days to show a new link. Apple checks every action first, which can take up to three business days. 5. A booking made through a link shows Came via with the channel, such as Google or Apple Maps. In Reports, under Where bookings come from, Online bookings from your Google and social links gives the totals per channel, with Download these as a CSV. Build a report can also break bookings down by Booking link. 6. If your role can see reports, each card also shows how many bookings that link brought in the last 90 days. Only appointments clients book online are counted. Class places are not labelled. Guide: https://bookatu.com/en-nz/help/get-booked-on-google-and-social ### Promo codes and discounts A way to give clients money off, either with a code they type at booking (like a launch offer or a quiet-Tuesday deal) or as a standing discount such as a senior or student rate. A well-timed offer fills quiet days and rewards loyalty, without dropping your everyday prices. Codes also let you see which promotions actually bring people in. How to use it: 1. Open Grow, Promo codes and create a code. 2. Choose an amount or a percentage off, and whether it is for everyone or a group like seniors. 3. Set a usage limit or an end date if it is a short campaign. 4. Share the code per channel from the same page, or apply a standing discount to the right clients so it comes off automatically. Guide: https://bookatu.com/en-nz/help/promo-codes-and-discounts ### Keeping clients coming back A round-up of the tools that bring clients back: reminders so they do not forget, win-backs for clients who have gone quiet, loyalty rewards for regulars, gift cards and packages that pre-pay future visits, and reviews that build trust. Used together they keep your chair full. Keeping a client is far cheaper than finding a new one. A few gentle nudges and small rewards turn first-timers into the regulars your business is built on. How to use it: 1. Turn on automatic reminders and win-backs so quiet clients get a friendly nudge (see Retention and win-backs). 2. Switch on loyalty points to reward repeat visits (see Wallet credit and loyalty). 3. Sell packages and gift cards so clients pre-pay and come back to use the credit. 4. Collect reviews after visits to build the trust that brings new clients in (see Reviews and the Google flywheel). Guide: https://bookatu.com/en-nz/help/keeping-clients-coming-back ### Getting paid and payouts When a client pays by card, such as a booking deposit, the money goes to your Stripe account, whether you use Bookatu payments or your own Stripe. Stripe then pays it out to your bank on a regular schedule. Bookatu never holds your money and never takes a cut of your bookings. Deposits are paid to you directly, with no middleman sitting on your cash. You can see every payment and when it lands. How to use it: 1. Choose how you get paid first (see Connecting Stripe for payments). 2. With Bookatu payments, add your bank in Settings, Payment options, under Where should Stripe pay you?. Until you do, payments collect in your Stripe balance and nothing is lost. With your own Stripe, add your bank account in your Stripe dashboard. 3. Stripe pays out on its schedule, often every couple of business days. Your first payout can take a little longer. 4. With Bookatu payments, press Payouts on the Bookatu payments card to see your balance, your next payout, the schedule and your payout history. With your own Stripe, Payouts opens your Stripe dashboard, where you can also change your payout timing. 5. If a payout could not reach your bank, the Bookatu payments card says so. Press Update your bank to fix it. Guide: https://bookatu.com/en-nz/help/getting-paid-and-payouts ### Refunds and cancellation charges Booking deposits are paid into your own Stripe account. When you cancel a booking whose deposit was paid online, Bookatu gives the deposit back to the client in full. This guide also covers refunding a shop order, refunding part of a payment, and when your cancellation policy lets you keep a deposit. You stay in control and fair. Genuine refunds are quick, and a clear deposit rule protects you when someone cancels at the last minute. How to use it: 1. When you cancel a booking whose deposit was paid online, the deposit goes back to the client in full. The cancel card says so before you confirm. 2. For a shop order, open it under Money, Orders and press Cancel & refund, then Yes, refund. 3. To refund only part of a payment, use your Stripe dashboard: find the payment, then refund the part you want to give back. Bookatu cannot do this yet. 4. Set your cancellation window (the notice you need) in Settings. Clients see it when they book. 5. If a client cancels inside that window, any deposit can be kept, in line with the policy they agreed to. 6. When in doubt, refund. A goodwill refund usually costs less than a bad review. Guide: https://bookatu.com/en-nz/help/refunds-and-cancellation-charges ### Ask the assistant The assistant is a chat inside your dashboard. Ask it about your bookings, booking requests, classes, clients, team, takings, tips, reports, forms, blog posts, campaigns and the audit log, and it answers from your own records. Ask it to book a client, add a service, receive stock, draft a form, accept a booking request, set the walk-in wait, add someone to a class, write or publish a blog post or draft an email campaign, and it shows you a card with the exact change to confirm. It can also show which messages your clients get and the ones that were held, send a held message, and move a held website enquiry into Leads. Each of those asks you to confirm first, and a sent message cannot be undone. Which messages clients get stays yours to change, in Settings, Client messages. You get answers without hunting through screens, and the small jobs take a sentence. Nothing changes until you confirm. It only ever sees your own business, and only what your role can see. How to use it: 1. Open the assistant from your dashboard, and type your question in your own words. 2. For a question, it looks the answer up in your records and replies. For a change, it shows a card with the details: check it and tap Confirm. 3. For a setup with several steps, such as a new service that needs its own consent form, it shows a plan. Review it and confirm once. 4. Changed your mind? Many changes have Undo on the card and in the history. Some cannot be undone from the chat, such as accepting a booking request or adding someone to a class: their card has no Undo, and the history says Can't be undone. 5. Your clients' names, emails and phone numbers only reach the AI once someone who manages the business has said yes to AI using client details in Settings, AI. Until then it sees initials only. 6. It never changes roles or logins, billing, passwords, bank details, API keys or webhooks, and it never shows a client's answers on a form. It also leaves anything that gives money back to you, such as declining a booking request, cancelling a visit or taking someone off a class. For those, and anything else it cannot do yet, it gives you the steps and a button to the exact screen. Guide: https://bookatu.com/en-nz/help/ask-the-assistant ### Booking requests and approval With booking approval on, a booking a client makes online, on your booking page, website widget or through the booking API, is held as a request until you accept or decline it. The client is told it is requested, and the time is held for them. You choose every online booking or only new clients, and a client's move of a confirmed booking can wait for your yes too. Bookings your team makes are never held. The one exception is a visit of several services booked through the dashboard assistant, which follows the same rule as an online booking. You decide who books before a time is confirmed, with no back and forth. Nothing waits forever: a request nobody answers is declined for you after the hours you choose, the time is freed and the client is told. Your team is reminded once, half way. How to use it: 1. Open Settings, then Booking approval, and turn on Approve online bookings before they are confirmed. Under Which online bookings, choose Every online booking or Only new clients. A new client has no visit and no confirmed booking with you yet. 2. Turn on Client moves need approval too if a client moving a confirmed booking from their booking link should wait for your answer. The booking keeps its time until you accept the new one. 3. Under Decline unanswered requests after, set how many hours a request may wait, from 1 to 336 (48 to start). A request also lapses at its own start time. Tap Save booking approval. 4. Open Booking requests to see what is waiting, oldest first, each with when it has to be answered by. Tap Accept to confirm it, or Decline, with a note for the client if you like. The client is emailed either way. 5. A deposit is taken when the request is made and refunded if you decline. A request whose deposit is still being paid can be answered once the payment has gone through. 6. Only a role that may edit the calendar can answer, and someone who sees only their own calendar sees only their own requests. You can also ask the assistant to accept one, for example "Accept the request from Olivia for Saturday": it shows the request on a card for you to confirm. Declining is done here, because it can refund a deposit. Guide: https://bookatu.com/en-nz/help/booking-requests-and-approval ### Understanding your insights A plain-English view of your numbers: how much you have earned, how many bookings you have had, your busiest times, your most popular services, and how many clients are coming back. It updates as bookings come in. You make better calls when you can see the picture. Spot your quiet days, your best sellers and whether clients are returning, then act on it. How to use it: 1. Open Insights to see your earnings and bookings over a period you choose. 2. Look at top services and busy times to plan your week and your staffing. 3. Watch new versus returning clients to see if your marketing is working. 4. Pair it with Retention to win back clients who have drifted. 5. Or just ask the assistant, for example "How did we do last month compared with the month before?" or "When are we quietest?". It answers from the same numbers. Guide: https://bookatu.com/en-nz/help/understanding-your-insights ### Your subscription and billing Bookatu starts with a 60-day free trial. After that you move onto a paid plan, priced by how many active clients you have each month rather than by staff or features. An active client is someone who booked or visited you in the last 90 days, so quiet contacts on your list never count. See the pricing page for each plan's price and the active-client range it covers. Bookatu never takes a commission on your bookings. You only pay in line with how busy you are, and adding your whole team costs nothing extra. No surprise fees, and no cut of your takings. How to use it: 1. Try everything free for 60 days. 2. When you are ready, pick the plan that covers your number of active clients on the pricing page. Pay yearly instead of monthly and you get two months free. 3. Text (SMS) reminders are included on the Studio, Pro and Scale plans, and available as a low-cost add-on on Solo (see SMS text reminders and the Solo SMS add-on). Texts from Bookatu's number come with a paid plan, so they start once your plan is paid, not during the trial. They can only be sent in some countries so far, and that guide lists them. Bookatu's numbers send booking confirmations and appointment reminders only. Other texts need your own texting number. 4. When your trial ends, your booking page stays open, and you choose a plan when you are ready. Until then you are on pay as you go, which is only billed from the day you add a card, never for a day before. 5. Manage your card and invoices, or cancel, from the billing area in Settings, which opens your secure billing portal. To change plan while you are paying for one, contact us at hello@bookatu.com. You can always export your data. 6. If you cancel, your public booking page stops taking bookings once the plan ends, and nothing is deleted. To come back, choose a plan again in the billing area. 7. Closing your business stops billing. From the month you ask to close it, pay as you go sends no invoice, and when the closure goes through any plan is cancelled with no final invoice. 8. Nothing is ever charged for going past an allowance. When your monthly texts or marketing emails run out, they pause until the allowance renews. Guide: https://bookatu.com/en-nz/help/your-subscription-and-billing ### Exporting your data A way to download your information, such as your client list, your bookings and your payment records, as files you can open in a spreadsheet. Each business's data is kept separate from every other business on Bookatu. You are never locked in. You can back things up, share figures with your accountant, or move on if you ever need to, with your data in hand. How to use it: 1. Open Clients to export your client list. 2. Use the Tax or payments area to export your sales and payment records as a CSV, or a Xero or QuickBooks file. 3. For everything at once, open Settings, then Privacy and security, and use Export organization data. It downloads your whole business as one file. It never includes payment credentials, and you can run it once per day. 4. Keep the file somewhere safe, or hand it to your accountant. Guide: https://bookatu.com/en-nz/help/exporting-your-data ### Privacy requests and data deletion A queue on the Privacy and security screen (under Settings) that tracks every client request to have their data erased. Your clients start these themselves. In their account on your booking page there is a Privacy section where they can download a copy of their data instantly, or request deletion by typing their name and then confirming through a link emailed to them. After they confirm there is a 48 hour cooling-off period where they can still cancel. Most requests then complete on their own, and the queue shows you where each one stands. Data-protection law (GDPR in Europe) gives clients the right to a copy of their data and the right to have it erased, and expects a response within a month. Bookatu runs the mechanical part for you. Identity is confirmed by email, changed minds get a cancel window, financial records are kept for tax law with the personal details removed, and every active request shows a countdown so you never miss the deadline. How to use it: 1. Open Settings, then Privacy and security. The Deletion requests card lists every request with its status, such as awaiting email confirmation, cooling off, needs your review, or completed. 2. Most requests need nothing from you. Once the client confirms by email and the 48 hour cooling-off passes, the erasure runs by itself and the row shows Completed. 3. A request is held for your review when the account is not settled, for example an upcoming appointment, an unpaid amount, or an active saved-card agreement. The reason is shown on the row in plain words. 4. When that is resolved, tap Review and complete. You see exactly what will be permanently deleted and what will be kept for tax records with the personal details removed. Type the client's name to confirm, and the erasure runs. 5. Keep an eye on the countdown on active requests. It shows how many days remain of the one-month response window the law expects. 6. To download a full copy of your own business, use Export organization data on the same screen. It is owner-only, never includes payment credentials, can run once per day, and sends you a confirmation email each time. Guide: https://bookatu.com/en-nz/help/privacy-requests-and-data-deletion ### Contacting support If you are stuck or something is not working, you can get in touch with our team. We would also love to hear about bugs and ideas, the small things that would make your day easier. You are not on your own. A quick message often saves an hour of guessing, and your feedback shapes what we build next. How to use it: 1. Look for the Help or Support link in the app to get in touch. 2. Reply to any email we have sent you, that reaches us too. 3. When reporting a problem, tell us what you did, what you expected, and what happened. A screenshot helps a lot. 4. When Bookatu support opens your client conversations, client records or main settings pages to help you, your Audit log shows it as Bookatu support viewed, with the time. Guide: https://bookatu.com/en-nz/help/contacting-support ### Stripe is not working Stripe is what charges cards for deposits and online sales. Most problems come down to three things: still being in test mode, an account that is not fully switched on, or bank details Stripe still needs. Knowing which of the three it is gets payments working again in minutes, so you stop losing online bookings and sales. How to use it: 1. Nothing charges, or it is all pretend money: you are in test mode. Test mode is practice with no real money. Switch to live mode to take real payments. 2. Stripe says charges are not enabled, or card payments are paused: your account is not fully activated yet. With Bookatu payments, open Settings, Payment options and press Fix now or See what's needed. With your own Stripe, finish the setup steps in your Stripe dashboard, usually a few details about you and your business. 3. Payouts are pending or stuck: add or confirm your bank account. With Bookatu payments, do it in Settings, Payment options. With your own Stripe, do it in Stripe. Your first payout also takes a little longer while Stripe checks your account. 4. Still stuck: open Settings → Payment options to confirm Stripe is connected, then reach out to us. Guide: https://bookatu.com/en-nz/help/connecting-stripe-troubleshooting ### SMS text reminders and the Solo SMS add-on Reminders and confirmations can go to clients by text message as well as by email. A text is read within minutes, so it is the channel that cuts no-shows the hardest. Texts from Bookatu's number come with a paid plan, so they start once your plan is paid, not during a trial. They can only be sent in some countries so far, listed in the note at the end of this guide. Elsewhere the settings show that texts are not available in your country yet, and email reminders go out as normal. Bookatu's numbers send booking confirmations and appointment reminders only. Other texts need your own texting number. SMS lands on the lock screen and gets opened almost every time, far more than email. For the appointments you most need people to remember, a text is the surest nudge. How to use it: 1. Who gets SMS: the Studio, Pro and Scale plans include text reminders. On the Solo plan you can switch them on as a low-cost monthly add-on. See the pricing page for what each plan includes. 2. Each plan comes with a monthly text allowance, a fair-use limit. There is a cap because every text has a real cost to send over the phone networks, unlike email which is effectively free. 3. If you reach the allowance, SMS pauses for the rest of the month and your email reminders keep going automatically, as long as reminder emails are on. The allowance resets at the start of the next month. Nothing extra is charged. 4. Turn SMS reminders on under Settings → Messaging & retention. On the Solo plan, buy the add-on from your billing settings. 5. Texts show your business name, and clients can reply STOP to opt out at any time, which keeps you on the right side of messaging rules. Guide: https://bookatu.com/en-nz/help/sms-reminders-and-add-on ### Text confirmations and your own reminder times Text messages, in Settings, is where you set your own rules for texts. You can text clients when a booking is confirmed or moved, send one or two reminder texts at the hours you choose, and set quiet hours when no text goes out. Everything on it is off until you switch it on. A short text with the service and the time reaches the client as soon as the booking is confirmed, and, from your own number, again with the new time if it moves, so fewer people turn up at the wrong time. Your own reminder times let you nudge clients a day ahead and again closer to the visit, and quiet hours mean nobody gets a text at night. How to use it: 1. Go to Settings and open Text messages, in the Grow group. Only roles that can manage settings can change it (owners and admins, unless you changed your roles). If you do not see Text messages, texts cannot be sent from your account yet. 2. Switch on 'Text clients when a booking is made or moved'. Clients get a short text with the service and the time when a booking is confirmed. The text with the new time, when a booking moves, only goes out when you send texts from your own number. On Bookatu's number, clients get the confirmation text only. Clients who said yes to texts before you switched this on agreed to reminders only, so they are not texted about their bookings. 3. For your own reminder times, switch on 'Choose when reminder texts go out'. Set First reminder in hours before the booking (1 to 336) and Second reminder (0 for no second reminder). These go even when reminder emails are off, but 'Also send reminders by text (SMS)' under Messaging & retention must be on. A booking made after a reminder's time does not get that reminder. 4. Switch on Quiet hours and set From and To. They start at 21:00 to 08:00 and follow the client's clock. A reminder due in quiet hours waits until they end, or goes before they start if the booking is earlier. A confirmation or a move made in quiet hours is texted when they end, unless the booking starts first. Press Save text messages. 5. A text only goes out when all of this is true: the client ticked the text box on your booking page, has a phone number and never replied STOP; your account has an SMS provider (Bookatu's, if the note at the end of this guide lists your country, or your own Twilio account connected under Inbox, then Channels); texts from Bookatu's number come with a paid plan, so they do not go out during a trial; and your plan includes texts with allowance left. Each text counts towards your monthly allowance. Plans and allowances are in SMS text reminders and the Solo SMS add-on. Guide: https://bookatu.com/en-nz/help/sms-confirmations-and-reminder-timing ### Installing Bookatu as an app Bookatu can be installed straight from your web browser, so it sits on your home screen like any other app. There is nothing to download from an app store. You get a home-screen icon, a full-screen app feel, and one tap to open. It loads faster on repeat visits, and it works both for you as the owner and for your clients on your booking page. How to use it: 1. On Android, Chrome or a desktop browser: look for the Install app button and tap it, then confirm. Your browser adds Bookatu to your home screen or apps. 2. On an iPhone or iPad, Safari has no install button, so do it by hand: tap the Share icon (the square with an arrow pointing up), choose Add to Home Screen, then tap Add. 3. Installing adds an icon and opens Bookatu full screen. It is the same Bookatu, your login and data are unchanged, and it updates itself automatically, so you never reinstall. 4. Your clients can install your booking page the same way, which makes rebooking with you a single tap next time. Guide: https://bookatu.com/en-nz/help/installing-bookatu-app ### Selling retail products in your shop A Shop on your booking site where clients can buy products, separate from your services and your gift cards. It is the place for retail and take-home items you already stock. It earns extra revenue from the clients who are already on your page, and it lets you sell the home-care and retail lines you keep on the shelf, without setting up a separate online store. How to use it: 1. Add a product under Catalog, Shop, with a name, price, an image and an optional SKU. 2. Stock tracking is optional. Leave stock empty and it stays untracked. Set a number and Bookatu counts it down as the product sells. 3. Mark a product as purchasable to show the Buy now button on your site, mark it featured to bring it to the top, and use active and the sort order to control what shows and in what order. 4. Clients pay online by card (see Connecting Stripe for payments). 5. Each product is either shipped or collected in store. How that works is covered in Shipping and collect-in-store for product orders. Guide: https://bookatu.com/en-nz/help/selling-retail-products ### Sell and check out at the point of sale Bookatu's point of sale is the Point of sale page in your dashboard. It rings up products at the counter, and it checks bookings out: the service, its extras and who did them are already in the sale, and you add any products on top. It records money you have already taken, in cash, on your own card machine or another way. Bookatu does not charge the client's card at the point of sale. One sale does it all. Stock drops the moment you record it, a booking is marked done, the right person is credited for what they sold, and the receipt is ready when the client asks for it. It runs in the browser on the computer, tablet or phone at your counter, and works with a receipt printer, a cash drawer, a barcode scanner, a customer display and a label printer. How to use it: 1. Open the Point of sale page: tap Sell on Products, or Point of sale on your Dashboard. Tap a product to add it to the sale, or search or scan for it. The point of sale sells the products you have added under Products. A service is paid for by checking its booking out. 2. Give a discount if you like, as a percentage or an amount, choose who it was Sold by, and tap 'Attach client (for a receipt by email)' to put the sale on a client's profile. Pick how the client paid, Cash, Card or Other, and tap Record sale. Card means a card taken on your own card machine, and Other is any other way. Bookatu only records how you were paid. It charges nobody, and there is no refund at the point of sale, so give money back the way you took it. 3. To check a booking out, tap Check out on it, in the Calendar or on the booking's own page. The Point of sale page opens with the booking's service, its extras and the person who did them in the sale, and anything already paid towards it comes off. Add any products they are buying, pick how they paid and tap Complete checkout. The booking is marked done. Checking out needs the 'Edit the calendar' permission. 4. To offer a tip when you check a booking out, turn on 'Accept tips at checkout' in the Tips card on the Point of sale page. Set up to 4 suggestions, as percentages of the booking's price, choose 'How a tip is split' between your team and tap 'Save tip settings'. The tip goes on top of what is left to pay and shows on the receipt. These settings need 'Manage the business'. 5. After a sale, tap Print receipt or Email receipt. To email it, the sale needs a client with an email address, and you can attach one right then. Recent sales, further down the page, lists your last 10 sales, so you can open a receipt again to reprint or email it. It shows takings, so only people with 'See analytics & earnings' see it. 6. Receipt printer and cash drawer: receipts print through your browser's print dialog, so any receipt printer this computer can print to works. Make it the default printer and pick its 80 mm roll paper once in the dialog. The receipt is 72 mm wide, the printable width of an 80 mm roll. Turn on 'Print a receipt when a sale is recorded' in the 'Receipt printer and cash drawer' card and the dialog opens with every sale. That card shows only to people with 'Manage the business'. A web page cannot open a cash drawer itself, but a drawer plugged into the receipt printer opens as each receipt prints, once the printer's driver is set to open it. 7. Barcode scanners: a USB or Bluetooth scanner that types like a keyboard rings a product straight into the sale, with no button to press, when it ends each scan with Enter or Tab, the usual settings. Put each product's code in its Barcode box under Products first. On a phone, a tablet or a computer with a webcam, tap Scan to use the camera instead, and allow camera access when the browser asks. No barcode? Hold the product's label in the frame and tap Identify. 8. Customer display, label printers and card machines: tap Customer display beside Scan to show the client their sale as you ring it up, in a second window on this computer (Open on this computer) or on a tablet facing them (Pair a tablet, then scan the QR code with the tablet or type the code on it). The tablet needs no sign-in and stays paired for 30 days. Print labels, in a product's menu under Products, prints a barcode, the name and the price on a Dymo, Brother or Zebra label printer or an A4 sheet of 21 labels. If a product has no barcode, someone with 'Manage the business' can tap Make a barcode to give it one the point of sale scans. Card machines are not connected to Bookatu: take the card on your own machine, then pick Card so the sale records how it was paid. If another point of sale system takes payment for your bookings, it can check them out through Bookatu's API, as Check out bookings from another point of sale explains. Weighing scales are not supported. Guide: https://bookatu.com/en-nz/help/use-the-till ### Shipping and collect-in-store for product orders Every product you sell is either shippable, where Stripe checkout collects the client's shipping address, or pay-online-collect-in-store, where the client pays now and picks it up from you. You can sell to clients who cannot get in, or keep things simple with click-and-collect. You decide per product, and each order is tracked from payment to handover. How to use it: 1. Mark a product shippable if you will post it, or leave it as collect-in-store. Shippable products ask the buyer for a delivery address at checkout. 2. Orders appear under Money, Orders. An order starts as Paid, then becomes Fulfilled once you ship it, or Collected once the client picks it up. An order can also be Cancelled or Refunded. 3. When you have posted an order, mark it Fulfilled. When a client collects in store, mark it Collected. The status keeps you and the client clear on where things are. 4. To refund an order, open it and press Cancel & refund, then Yes, refund. The money goes back to the buyer (see Refunds and cancellation charges). 5. Bookatu does not buy postage or print shipping labels. You post the item yourself, and the order status tracks it. Guide: https://bookatu.com/en-nz/help/product-shipping-and-fulfilment ### Deals and off-peak offers An automatic percentage off when clients book during the quiet windows you choose. The offer is shown on your public Deals page. It fills your slowest hours without discounting the times that are already busy. Clients get a reason to book off-peak, and you keep full price at your peak. How to use it: 1. Turn deals on under Settings, then choose your off-peak windows from the presets, such as weekday mornings, weekday afternoons, Saturday mornings or Sundays. 2. Set the percentage off you want to give in those windows. 3. The discount then applies automatically to any booking made in an off-peak window. There is no code for the client to type. 4. This is different from promo codes, which are typed codes or standing discounts. Deals are automatic and tied to your quiet times (see Promo codes and discounts). Guide: https://bookatu.com/en-nz/help/deals-and-off-peak-offers ### Choosing your business type and industry wording When you choose your industry, such as salon, spa, personal trainer, clinic, studio, restaurant or other, Bookatu rewords the booking page and the app to suit your trade. The booking button, the services heading, the words for your team and your rooms, and the client portal all read naturally for your kind of business. A trainer books sessions with a trainer at a training location, a clinic offers treatments with a practitioner in a treatment room, and a restaurant invites guests to reserve a table from the menu. How to use it: 1. Set your business type in Settings when you start, or change it later. 2. Switching updates the wording across your booking page and the client portal, for example the booking button, the services heading, and the names used for your staff. 3. Your bookable resources are renamed to match too, so they read as Rooms, Treatment rooms, Training locations or Tables depending on your trade. 4. Freelancer or contractor: you work for clients directly, as a freelancer, independent contractor or sole trader, for example in design, development, writing, consulting, tutoring, music or the trades. Clients book a call or a job on your page, and you invoice them yourself. Guide: https://bookatu.com/en-nz/help/choosing-your-business-type ### Securing your account: two-factor and team logins The settings that keep your business data safe: a strong password, two-factor authentication (2FA) for an extra step at sign-in, and a separate login for each team member. Your client records, payments and messages are sensitive. Two-factor means a stolen or guessed password is not enough on its own to get in, and separate logins mean you can see who did what and remove access cleanly when someone leaves. Bookatu also sends a security email to your confirmed email address when your password, two-step login or passkeys change, Google sign-in is added to your login, or someone signs in from a new browser, so a change you did not make does not go unseen. How to use it: 1. Open Privacy & security from the Settings menu and turn on Two-step login. You are asked for your password first, unless you signed in a moment ago. You scan a code with an authenticator app on your phone, and from then on it asks for a short code when you sign in. It needs a confirmed email: until you have opened the link we emailed you, the card says Confirm your email first. 2. Save your recovery codes somewhere safe when you set up 2FA. They let you back in if you lose your phone. 3. Change your password any time under Account security, in Settings, Privacy & security, and use a long, unique one you do not use anywhere else. If you sign in with Google and have no password yet, you can choose one there within ten minutes of signing in and press Save password. Signed out and cannot remember it? Tap Forgot password? on the sign-in page and we email you a link. 4. When you sign out, that session ends straight away. The sign-in links we email your clients for their booking accounts can only be used once. 5. Give each team member their own login rather than sharing one (see Adding your team). When someone leaves, remove their access so they can no longer sign in. Guide: https://bookatu.com/en-nz/help/securing-your-account ### Confirming your email and signing in When you sign up, Bookatu emails you a link to confirm your address. Opened in a browser where you are already signed in to this login, it confirms in one click. Anywhere else it asks for the login's password. Someone could sign up with your address before you do. Whoever first proves they can read the inbox, by the link, by Google or by Forgot password, ends whatever was set up on the login before, so a stranger who got there first keeps no way in. After that, a security email tells you about every change to how you sign in. How to use it: 1. Open the link in the email and, if asked, type the password you chose when you signed up. Your email is confirmed and you are signed in. The link works for seven days. 2. If you did not make this login, or you forgot its password, tap I did not make this login, or I forgot its password and choose a new password. Anything set up on the login before is removed: its earlier password, two-step login, passkeys and connected apps, and every device is signed out. API keys and webhooks keep working, and the Security page lists them for you to review. 3. You can also use Continue with Google with the same address. Google has already checked it, so your email is confirmed and the same things are removed. To have a password too (the phone app needs one), choose one under Account security, in Settings, Privacy & security, within ten minutes of signing in, or use Forgot password. 4. Signed out and cannot remember your password? Tap Forgot password? on the sign-in page and enter your email. We send a link that works once, for 30 minutes. If two-step login is on, you also enter a code from your authenticator app or a recovery code. If it is off and the login has a passkey, your device asks for the passkey when you save. 5. Until your email is confirmed, making an API key, a webhook or a calendar link, connecting an app, turning on two-step login and adding a passkey all say Confirm your email first, with a button that sends you the link again. 6. Once your email is confirmed, Bookatu sends a security email to it when your password changes, two-step login is turned on or off, recovery codes are renewed, a passkey is added or removed, Google sign-in is added to your login, or you sign in from a browser that has not signed in as you before. If it was not you, reset your password and write to hello@bookatu.com. If it was Google sign-in, write to us: a reset does not remove it. Guide: https://bookatu.com/en-nz/help/confirming-your-email-and-signing-in ### Check your security on the Security page The Security page, under Settings, shows a Security checklist for your business with a score, such as 5 of 7 checks passed. Each check is worked out from your own team, API keys and settings, explained in one plain sentence, and comes with a button that opens the page where you fix it. Below the checklist you set auto sign-out, and a section called Everything in one place links to every other security setting where it already lives. Security settings live in several places: Team, Privacy & security and API & monitoring. This page puts them side by side, shows what needs attention first, and turns each gap into one tap. Owners and admins can open it. How to use it: 1. Open Settings, then Security. The Security checklist at the top shows your score, for example 5 of 7 checks passed, and how many things are left to fix. 2. Read each check. A tick means it passes and a warning sign means it needs attention. Each one that you can fix has a button that opens the right page, such as Require it, See who, Turn on yours, Add a passkey, Review keys, Review access, Review or Turn it on. 3. The checks are: two-step login required for the team, everyone on the team using two-step login, owners and admins using two-step login, owners and admins having a passkey or two-step login, API keys that have never been used or not used in 90 days, keys and connected apps that can change things rather than only read, keys or apps left behind by people no longer on your team, keys and webhooks made before an email was confirmed, which you revoke or keep on the API page, everyone on the team having signed in within 90 days, and auto sign-out. The checks about keys and apps only appear when your business has some. The sign-in check appears from late January 2027, once Bookatu has 90 days of sign-ins to look at; people who joined in the last 90 days are not counted. 4. If you are an admin, some fixes are the owner's alone. Instead of a button you see who can make the change, for example Only the owner can change this, on Team > Two-step. 5. Set Auto sign-out after inactivity in its own card on the same page. It is off until someone turns it on. 6. Scroll to Everything in one place for links to two-step login for you and your team, passkeys, role permissions, the Audit log, API keys and connected apps, and your data. Each opens where it already lives. For an admin, the ones only the owner can open are named but not linked. Guide: https://bookatu.com/en-nz/help/the-security-page ### Sign people out automatically after inactivity Auto sign-out is a setting on the Security page. When it is on, anyone on your team who has done nothing in your business for the time you choose (15 minutes, 30 minutes, 1 hour or 2 hours) is signed out. It is off by default, and owners and admins can switch it on. A front desk computer or a tablet left signed in can show your clients and your takings to anyone who walks past. Auto sign-out closes that gap without anyone having to remember. A minute before, the person gets a warning and can stay signed in with one tap. How to use it: 1. Open Settings, then Security, and find Auto sign-out after inactivity. The badge shows Off, or On with the time you chose. 2. Under Sign people out after, pick 15 minutes, 30 minutes, 1 hour or 2 hours without activity, then tap Save. Turning it on signs nobody out straight away: everyone's clock starts from that moment. The change is recorded in the Audit log. 3. A minute before the time runs out, the person sees Still there? with a countdown. Stay signed in keeps them in. Sign out now signs them out straight away. If they do neither, they are taken to the sign-in page with a note that they were signed out after a period of inactivity. 4. Only real activity in the browser counts: a click, a key press, a tap, scrolling or moving the mouse. A page refreshing itself in the background does not. With several tabs open in the same browser, activity in any of them keeps the person signed in. 5. It applies to your business only, on the web. Someone who also works at another business stays signed in there, and Bookatu support is not affected. 6. To switch it off, choose Off (stay signed in) and tap Save. Guide: https://bookatu.com/en-nz/help/auto-sign-out-after-inactivity ### Sign in with a passkey A passkey lets you sign in with Face ID, Touch ID, Windows Hello, your phone or a security key instead of typing a password. It belongs to you, not to one business, so it signs you in to every business you work with on Bookatu. Your password, Google sign-in and two-step login keep working as they do now. There is nothing to remember and nothing anyone can phish. Because it needs your fingerprint, face or PIN on the device that holds it, signing in with one counts as two-step login, including at a business that requires two-step login for everyone. On the Security page it also passes the check that owners and admins have a passkey or two-step login. How to use it: 1. Owners and admins: open Settings, then Privacy & security, and find the Passkeys card. Everyone else on the team: tap Two-step login at the top of the admin and find Your passkeys. Anyone can add their own. If your browser cannot make passkeys, the card says so: open the page in an up-to-date Safari, Chrome, Edge or Firefox. Adding one needs a confirmed email: until you have opened the link we emailed you, the card says Confirm your email first. 2. Tap Add a passkey and give it a name so you can tell your passkeys apart. It suggests one from your device, such as iPhone or Mac. You can have up to 20 passkeys. 3. Prove it is you first. Enter your password, or a code from your authenticator app or a recovery code (tap Use a two-step code instead if you have both). If you only sign in with Google there is no password to check, so you must have signed in within the last ten minutes, or you will be asked to sign out and in again. 4. Tap Continue and follow your device's own prompt. Your new passkey appears in the list with the date it was added. A Synced badge means it is backed up by the device or account that holds it. 5. Next time, choose Sign in with a passkey on the sign-in page, or pick your passkey when your browser offers it in the email field. You are not asked for a two-step code. 6. Use Rename to change a name, or Remove then Yes, remove to take one off. You cannot remove your only way to sign in: with no password and no Google sign-in, add another passkey first. On a new device, sign in with your password or Google as usual, then add a passkey for that device. Guide: https://bookatu.com/en-nz/help/sign-in-with-a-passkey ### Remove someone from your team and sign them out Remove and sign out is a button on a person's row under Settings, then Team, in Who can sign in. Before anything happens it shows a summary of what they have at your business: upcoming bookings, API keys and connected apps they made, and calendar connections. When you confirm, their login here is removed, the keys and apps they made stop working, their calendar sync is disconnected, and their upcoming bookings go to the person you choose or are left unassigned. Someone who has left should not keep a way in. Doing it in one step means nothing is forgotten, like a key they made for an integration or a calendar link that still shows your bookings. Nothing is cancelled and their history is kept, and other businesses they belong to are not affected. How to use it: 1. Open Settings, then Team, and scroll to Who can sign in. The owner, and admins who can manage the team, see Remove and sign out on other people's rows. It is never on your own row, an admin never sees it on an owner's row, and it is never on the last owner's. 2. Tap Remove and sign out and read the summary. Their login here is removed, so they are signed out of this business on their next click. Any API keys, connected apps, Google Calendar connection and calendar link they have here are listed. 3. If they have upcoming bookings, choose one: Move them to a team member who can be booked, or Leave them unassigned for you to reassign on the calendar. Each keeps its time and nothing is cancelled. If the person you choose already has a booking at the same time, that one is left unassigned instead. Handing bookings over needs someone who can edit the calendar. 4. If they have a card on your booking page, leave Take them off the booking page too ticked so clients can no longer book them. Their card moves to Removed with its history, and can be restored. 5. Tap Remove and sign out with their name. The Done screen lists what happened and anything left to sort out, such as bookings they share with someone else or classes they teach, which stay as they are. 6. The plain Remove button only removes the login and leaves their keys and apps working. If that happens, the Security page shows Nothing left behind by people who have left until you revoke them. Guide: https://bookatu.com/en-nz/help/removing-a-team-member ### Local discovery hubs (your city and service pages) Shared public pages on Bookatu at /discover/{city} and /discover/{city}/{service} that list real, bookable businesses by town and by service. Each hub has the right structured data and is in the sitemap, so a search like 'haircut in your town' can surface a list of businesses people can book straight away, with yours among them. It is extra exposure to new clients who are searching for a service in their area but do not yet know your name. There is no commission and no paid placement, so being listed costs you nothing and never takes a cut of your bookings. How to use it: 1. Open Settings, tap Business details and set your City or town accurately. This is what groups you onto the right city hub. 2. Optionally set your Region (your wider area or state) so you also appear in broader local results. 3. Complete your services so you show on the matching service hub, for example the haircuts or massage page for your town. 4. Keep your profile, photos and reviews current so you stand out in the list against other businesses. 5. A hub page only appears once at least one real business is listed for it, so there are no thin or empty pages. Being listed is free, not a paid ad. This is being listed on Bookatu's hubs, which is different from connecting your own domain to your storefront. Guide: https://bookatu.com/en-nz/help/local-discovery-hubs ### Write blog posts with your own AI Use your own AI sits at the top of the blog post editor. You give it a title and a few words on what the post should cover, and it builds a prompt you paste into the AI you already use. When you paste the AI's whole reply back, it fills in the title, excerpt, body, search title, search description and tags. You can write with the AI you already know, and it uses no Bookatu AI credits. The prompt carries only your business name, type, city and website language, never client details, and asks the AI not to make up prices, offers, opening hours or staff names. Nothing goes live until you publish it. How to use it: 1. Open Grow, then Blog, and tap New post, or open a post to edit it. Blog is in the menu for owners and admins. 2. Tap Use your own AI. Type a Title (2 to 140 characters) and, under 'What should it cover?', a few words on who it is for and the main points. Tap Generate prompt, then Copy prompt. 3. Paste the prompt into ChatGPT, Claude, Gemini or any other AI. Copy its whole reply, paste it under 'Paste the AI's answer' and tap Fill the post. If the post already has different words, you are asked 'Replace what is there?' first. Tap Yes, replace or Keep what is there. 4. Check what was filled in. The title and body are replaced. The body is cut at 50,000 characters, the excerpt at 300, the search title at 70 and the search description at 200, and you get up to 6 lowercase tags of up to 24 characters each. Any raw HTML is removed. If the answer has no excerpt, search title, search description or tags, what you had stays. 5. If the reply cannot be read, nothing changes and you see what to fix, for example an answer with no title or no post body. Ask the AI again and paste its new reply. 6. Filling the post does not save or publish it. Tap Save draft to keep working, or Publish to put it on your storefront. On a post that is already live, Save changes publishes your edits straight away. The built-in AI buttons beside Excerpt and Body ('Write it for me', or 'Polish my wording' once there is text) and 'Suggest with AI' under Search & sharing still work alongside it. Guide: https://bookatu.com/en-nz/help/write-blog-posts-with-your-own-ai ### Your business profile, website and social links The profile fields under Settings → Business details that describe your business and tie your booking page to the rest of your online presence. The smart Website field is where you type your main domain (for example yoursalon.co.nz). Below it, a Website & social section lets you add your Instagram, TikTok and Facebook just by typing your @handle, plus an 'Add another link' button for extra websites and other media like YouTube, X, LinkedIn, WhatsApp or any other labelled link. Bookatu shows each one you fill in on your storefront contact card with the right icon, and leaves out the ones you skip. The same screen holds your City or town and Region. Clients can jump straight from your booking page to your website and the social profiles where you post your work, so the page that takes bookings also sends people to follow you. Your City and Region show on your booking page and go into the details search engines read, and a complete profile helps you get found. You only fill in what you have, and only those links show. How to use it: 1. Open Settings and tap Business details. 2. Type your main website domain in the Website field (just the domain, like yoursalon.co.nz), or leave it blank. Bookatu cleans it into a readable 'Visit our website' link for you. 3. In the Website & social section, type your Instagram, TikTok or Facebook. You can paste the full link, but you do not have to. Just typing your @handle is enough, and Bookatu turns it into the right link with the right icon. 4. Use 'Add another link' to add an extra website or other media such as YouTube, X, LinkedIn or WhatsApp. Pick the type, type the handle or link, and give it a short label if it is an 'other' link. 5. Leave out anything you do not have. Only the links you fill in appear on your booking page, each with its own icon. 6. Set your City or town and your Region. They show on your booking page and help people near you find you. 7. Save, then use View site to check the contact card shows your website and social links. 8. Note: this links out to websites and profiles you already have, with the icon for each. It does not point or connect your own domain at your Bookatu storefront, so do not expect a custom-domain setup here. Guide: https://bookatu.com/en-nz/help/your-business-profile-and-website ### Your first-run setup checklist A slim strip near the top of your admin home that says how many steps are left before you can take bookings. Tap it to expand the full checklist. Each step only ticks when you have really done it, so the progress ring means something. It shows exactly what is left to do, in order, so you are never guessing, and it stays out of your way, folded into one line until you want it. Because steps only tick when truly complete, there are no false day-one ticks, and you can be taking bookings the same day you sign up. How to use it: 1. Confirm your email by opening the link in your welcome email. Until you do, your page cannot go live. If the email went missing, press Resend email on the checklist. 2. Add your services, each with a name, how long it takes and the price, so your menu is right. 3. Set your opening hours, which decide when clients can book. 4. Add your team and tick which services each person does. 5. Add your logo so your booking page looks like you. 6. Connect Stripe to get paid (or Get paid). You can go live without it unless your page takes money online, and it is what turns deposits and online payments on (see Connecting Stripe for payments). 7. Share your booking page. Once it is live, put your link everywhere (see Your booking page). Guide: https://bookatu.com/en-nz/help/your-setup-checklist ### Finding your way around the admin A labelled side rail with a compact fly-out menu, plus a menu sheet on small screens. Six areas sit on the rail: Today (your day: calendar, appointments, clients, waitlist), Catalog (everything you offer: services, products, forms, packages), Inbox (messages and leads), Grow (marketing), Money (orders, reports and billing) and Settings. The fly-out shows just the items for the area you are in. You can find any area quickly, and if you are not sure where something lives, the search box in the menu jumps straight to it. The fly-out only shows what is relevant to where you are, and it closes itself when you pick something or tap away. How to use it: 1. Use the side rail to switch between Today, Catalog, Inbox, Grow, Money and Settings. 2. Not sure where something is? Open the menu and type in the search box to jump straight to any screen. 3. Open the fly-out to see the items within the current area. It closes when you select something, click outside it, or press Esc. 4. On a phone, open the menu sheet to reach the same areas. Guide: https://bookatu.com/en-nz/help/finding-your-way-around ### Recurring and standing appointments A way to book a client in for the same service over and over at a set rhythm, like every 4 weeks. From any of their bookings you choose how often they come back and how many visits to lock in, and the app books the whole run at the same time of day. Each visit is a normal confirmed booking, so the client gets a confirmation and the usual reminders before each date. Clients who leave with their next visits already booked come back far more often, so your column stays full weeks ahead. It is owner-booked only and never charges anything: no deposits, no card on file, just confirmed appointments. Like every Bookatu feature, it is on your plan at no extra cost. How to use it: 1. Open Today, Calendar and click one of the client's bookings. It can be an upcoming or a just-finished visit. 2. Find the 'See you again?' card and pick how often: Weekly, Fortnightly, Every 4 weeks, Every 6 weeks, or Custom for your own number of weeks. 3. Pick how many visits to lock in, from 2 up to 12. 4. Tap the 'Book the visits' button. Every visit is booked at the same time of day as this one, starting one interval after it. 5. Check the result list. Any date that clashed with an existing booking is marked as a clash and skipped, so you can rebook just those from a free slot. 6. To add a single visit instead of a whole run, open a finished booking and use the 'Book a one-off next visit' card to start the next one in 4, 6, or 8 weeks. Guide: https://bookatu.com/en-nz/help/recurring-appointments ### Run video appointments with Google Meet A way to run appointments by video instead of in person. You connect one business Google account, turn on the master switch, then mark which services are video calls. Bookings for those services get a Google Meet link in the confirmation email, and the appointment also lands on that Google Calendar. Included on every plan. It lets you offer consults, follow-ups and online sessions without making meeting links by hand. The right link is in every confirmation, so clients just turn up. In-person services stay untouched, so a mixed business runs both at once. How to use it: 1. Open Settings and tap Payment options. Find 'Google for video meetings' and press Connect Google. Sign in with the one business Google account you want to use. You should then see 'Connected as' with that address. 2. Open Settings and tap Booking rules. Turn on 'Add a Google Meet link to online bookings'. This is the master switch for video appointments. 3. Open Services and edit a service you run by video. Under How clients meet you, choose Online meeting and save. Do this for each video service, and choose another way for your in-person ones. 4. Online meeting is what gives the service its Google Meet link, and choosing any other way turns the link off. Clients then get the call link instead of an address, and their booking page shows Join the call once the link is made. Until Google is connected and video meetings are on, the editor says so under Online meeting. 5. Test it with a booking for that service. A Google Meet link is created with the booking, and the confirmation email shows a 'Join the video call' button. The appointment also appears on the connected Google Calendar. 6. If a team member has linked their own Google Calendar with sync turned on, that person's video bookings use their Google account instead of the business one. Otherwise everything runs through the business account you connected. Guide: https://bookatu.com/en-nz/help/video-appointments ### Using your own domain for your booking page A way to show your booking page on a web address you own, instead of the bookatu.com link. You connect a domain you already bought, add the DNS records Bookatu shows you at your registrar, and your booking page then opens at that address. You can connect more than one domain, and they all open the same booking page. Custom domains are included on the Pro and Scale plans. You buy the domain name yourself and renew it with the company you bought it from. Your booking page sits on your own brand, so it feels like part of your own website and is easier for clients to trust and remember. There is still no commission, and bookings and payments work just as they do on your bookatu.com link. Your domain shows your public booking page only. Your dashboard stays on bookatu.com, and you and your team sign in there as before. How to use it: 1. Make sure you own a domain first. If you do not have one, buy it from any registrar (the company where you buy and manage domain names). 2. Open Settings, then Custom domain. If your plan does not include it, you see See plans & upgrade instead of the form. 3. Under Add a domain, type your own domain, without https:// and with nothing after it. Then tap Connect domain. 4. Sign in to your registrar and add the DNS records Bookatu shows for that domain. Copy each row across exactly as shown, matching the Type, the Name / Host and the Value. Do not use your registrar's forwarding or redirect option: visitors would be sent back to your bookatu.com link and your domain would never finish verifying. If the domain is already in use somewhere else, Bookatu shows one more record that proves it is yours. 5. Come back and wait. DNS changes can take a little while. The status moves from Pending DNS to Verifying to Live on its own, and the page updates without you refreshing. You can also tap Check status to look now. If it shows Needs attention, check each record against what Bookatu shows. 6. Once it shows Live, visit your domain to confirm your booking page opens there. To add another address, use Add a domain again. To disconnect one, tap Remove. Guide: https://bookatu.com/en-nz/help/custom-domain ### Moving or reassigning a booking Two quick ways to shift a booking on the calendar. Drag a booking block to a new time, and if you like into another staff member's column, to reschedule it. Or move it to a different staff member while keeping the same time. As the owner you can push the move through even outside your open hours, so you can squeeze in an early or late client. Reshuffling a day takes a few taps, not a phone call or a rebooking. A client runs late, a stylist calls in sick, two appointments clash, and you fix it in one move. The client's record updates with it. The one thing the app stops is putting two bookings on the same staff member at the exact same start time, so you cannot accidentally double-book one person. How to use it: 1. Open Today, then Calendar, and find the booking on the day view. 2. To change the time, drag the booking block up or down. On a computer, to change the time and the staff member at once, drag it across into another staff column. It snaps to the nearest 15 minutes, and you will see an 'Appointment moved' confirmation. 3. To keep the same time but hand it to someone else, tap the booking to open its details, then under 'Move to another staff member' pick a name and choose Move. This is the way to reassign on a phone, where the calendar shows one staff member at a time. 4. You can also do both from the appointment's own page. Open it from Appointments, then use Reschedule to pick a new date and time, or Move to staff to reassign it while keeping the time. 5. Moving outside your open hours is fine. The greyed early-morning and after-close areas still accept a booking, so an early or late client fits in. 6. Only upcoming bookings can be dragged. Cancelled, completed and no-show appointments are locked, so open the appointment and use Reschedule to rebook that client instead. Guide: https://bookatu.com/en-nz/help/moving-and-reassigning-bookings ### Set up a daily checklist for your team A daily checklist for your team. The opening jobs, the cleaning between clients, the end-of-day close, all in one list. Your staff open it on their phone, tap each task as they finish it, and you see who did what. Salons can load a ready-made list in one tap and edit it to fit. It keeps your standards the same on every shift, whoever is on. A new starter knows exactly what to do without asking, and you get a clear record of what was done and by whom, which matters for hygiene and for training a junior. How to use it: 1. Open Checklist under Home. If you run a salon, spa, barber or nail bar, tap 'Load salon checklist' to start with a ready-made list, then change anything you like. 2. Add your own tasks with 'Add a task'. Give each one a section like Opening or Closing, an optional group, and when it should be done: Open, After each client, Every hour, Daily or Close. 3. Share the checklist link with your team. They open it on their phone, sign in, and tick tasks as they go. Each tick records their name. 4. Check the 'Today' panel to see who ticked what and at what time. The list clears itself each morning, ready for the next shift. 5. Turn a task off if you do not need it today, or delete it for good. Guide: https://bookatu.com/en-nz/help/team-checklist ### Add a trainee who only sees the checklist Trainee is a login type for juniors and apprentices. When they sign in they see only the team checklist, so they can tick off their jobs on their phone. They cannot see your calendar, your clients, your money or any settings. It is the safe way to bring a new starter onto the team. They get exactly what they need to do their work well, and none of the private parts of your business. You still see who did what on the checklist. How to use it: 1. Open Team under Settings and use Give someone a login, not the button on a staff card, which has no Trainee role. Enter their name and email, choose Trainee and set a temporary password. 2. Tell them the password yourself. When they log in they land straight on the checklist and cannot reach anything else. If they already have a Bookatu login, they get an email instead and join once they accept. 3. They tick tasks on their phone as they work. Their name shows against each tick in your Today view. 4. To give them more access later, change their role to Staff or Admin from the same Team page. Guide: https://bookatu.com/en-nz/help/trainee-accounts ### Share a private class or clinic link You can make a group class or clinic private, so it does not show on your public booking page. You then share a link with the people you want, on WhatsApp or in a group chat, and only they can see the sessions and book. You can even copy a link for one specific session. Group classes are available to studios, trainers, coaches and photographers. It is made for a members-only clinic, a private group, or a one-off session you only want certain people to join. The class stays hidden from the public, but the people with the link can book in seconds. How to use it: 1. Open Services and find your group class. On its row, open the '...' menu and choose 'Make private (link-only)'. A 'Private' badge appears. 2. From the same menu, choose 'Copy private link' to copy the link for the whole class, then paste it into a message. 3. To share one specific date, open Manage sessions and use the 'Copy link' button on that session. The person lands straight on that session to book. 4. To put the class back on your public page, open the '...' menu and choose 'Make public (show on page)'. Guide: https://bookatu.com/en-nz/help/share-a-private-class ### Book several services in one visit A visit is two to four different services for one client, one straight after another, with the same person or different people. Each service is still its own booking on your calendar, marked Visit 1/2, Visit 2/2 and so on. To the client it is one visit: one confirmation listing every service, one reminder, one deposit, one booking link and one checkout at the point of sale. Clients book the whole appointment in one go instead of booking each service and hoping the times line up. Bookatu only offers start times where every service fits back to back, so nobody waits around between services. At the point of sale you check out the whole visit as one sale. How to use it: 1. Clients can't book a visit until you switch it on. Open Settings, then Several services in one visit, turn on 'Clients can book several services in one visit' and tap Save. You need the Manage permission, which owners and admins have by default. 2. On your booking page the client picks their first service. On the date and time step they tap Add another service and choose what comes next, up to 4 services. Only times where the whole visit fits are shown, and the review lists each service with its start time and price. On your website widget, 'Book several services in one visit' opens your full booking page in a new tab. 3. Your team can always book a visit, whatever the setting. Open New booking, or drag across a staff column on the Calendar, pick the first service, then tap + Add another service. Each row has its own person or Any available. If the visit does not fit, the form names the service, the time and the person that is the problem. 4. The client gets one confirmation and one reminder for the whole visit. If they book online and you take deposits, they pay one deposit: each service's deposit added up, but never more than the first service costs. 5. From their booking link the client moves or cancels the whole visit at once. A move keeps each person and counts once against 'Most times one booking can be moved online'. If you have 'Client moves need approval too' turned on, the client is asked to contact you to move a visit. 6. Tap Check out on any service in the visit. It becomes one sale with a line for each service, credited to the person who did it. On the calendar each service is still its own booking, so dragging or cancelling one there changes only that service. Guide: https://bookatu.com/en-nz/help/several-services-in-one-visit ### Set which services can be booked together Each service has its own Combination rules, under its editor on the Services page. On a service you choose which other services it can share a visit with, what it is Never with (for example 4 braids and 6 braids), and which extras are offered with it. On an extra you also choose which services it is offered with and whether it adds its time to the booking. Clients and your team are only offered combinations that make sense, so nobody books two things you cannot do together. If a combination that is not allowed still gets through, it is refused with the reason before anything is booked. Extras that take real time make the booking longer, so your calendar stays honest. How to use it: 1. Open Catalog, then Services, and tap Edit on a service. Below its details is Combination rules, with its own Save combination rules button. Only roles with the Manage permission see it, which owners and admins have by default. Classes have no combination rules. 2. Under In the same visit, keep Any other service (the default) or pick Only the services I choose and tick them. Two services share a visit only if neither one's list leaves the other out. 3. Under Never with, tick anything that must never be booked with this service, such as 4 braids and 6 braids. Set it on either one and it holds both ways round. 4. Under Extras offered with it, keep Every extra or pick Only the extras I choose. An extra is a service with 'Offer as an add-on' switched on. On an extra's own rules you set Offered with, Never with, and 'Adds its time to the booking', which is off by default. 5. What clients see: when several services in one visit is on, Add another service only lists services that go with the visit, and the review only shows extras that fit. Extras that add time are offered before the time is picked, under 'Extras that take extra time'. Two extras that are never together work as a choice, so ticking one unticks the other. 6. What your team sees: New booking only offers services and extras that go together, and an extra that adds time lengthens the Duration. If the chosen services stop going together, a warning names them, for example '4 braids and 6 braids can't be booked together.', and the booking is refused until you change it or the rule. Guide: https://bookatu.com/en-nz/help/service-combination-rules ### Book a service that needs two or more people A service can need 1 to 4 people at the same time. Bookatu only offers a time when that many people who do the service are free together, and the booking goes in each of their columns on the calendar. Every service starts at 1 person, so nothing changes until you set it. Two-person services stop being two bookings you line up by hand, and nobody on the booking can be double-booked. At checkout each person is credited a fair share, so commission and tips come out right without sums on paper. How to use it: 1. Open Catalog, then Services, tap Edit on the service and set People needed at once, for example 2 people. Tap Save changes. Changing it needs the Manage permission, which owners and admins have by default. It is not offered for restaurants, classes or add-ons, and the list then shows a tag such as '2 people at once'. 2. On your booking page the client picks one person or anyone, and whoever else does the service and is free joins them. A service like this is always booked on its own, never as part of a visit of several services. 3. On New booking, or when you drag across a staff column on the Calendar, choose the service and the form shows 'Also with:'. Pick each other person or leave Anyone free. The times shown are when they are all free together. 4. The calendar draws the booking in each person's column. Move it from its own person's column; the copy in the others' columns opens the booking but cannot be dragged. Team members who only see their own column still see the bookings they are on. 5. Moving keeps the same people where they are free and finds others where they are not. Cancelling frees everyone on it. 6. Tap Check out as usual. It is one sale with the same total, and each line is shared equally between everyone on the booking, with odd cents going to its own person first. Each person earns commission on their share under their own rule, and tips follow 'How a tip is split' on the Point of sale page, or the amounts you enter at the point of sale. Guide: https://bookatu.com/en-nz/help/bookings-with-two-or-more-staff ### Book a service that needs a room and equipment Some treatments need more than one thing free at the same time, such as a treatment room and a laser machine. With Also needs on a service, Bookatu only offers a time when a person and one free resource of each kind are available, and the booking holds them all for its whole length. A service that needs one kind, or none, works exactly as before. Your one laser can no longer be booked in two rooms at once. A laser held by one booking is busy for every service that needs a laser, so clashes are caught when the booking is made, not on the day. How to use it: 1. First give each resource a Kind on your resources page under Catalog (its name depends on your business type, such as Rooms, Treatment rooms or Resources), for example Room and Laser. Also needs only appears once you have active resources of two or more kinds. 2. Open Catalog, then Services, tap Edit on the service and pick the first kind under Requires a room (the label uses your own word, such as Requires a treatment room). Then tick each other kind under Also needs and tap Save changes. A service can need up to 4 kinds. 3. Changing Also needs takes the Manage permission, which owners and admins have by default. It is never offered to restaurants, or for classes and add-ons. The Services list then shows a tag such as 'Needs Room + Laser'. 4. Your booking page and New booking only offer times when one of each kind is free. If you book a time where a kind is taken, New booking says so, for example 'No free laser then.' Choose another time, or tap Save anyway to save it with whatever is free. 5. Moving a booking keeps each resource where it is still free and picks another of the same kind where it is not. If a client moves it online and a kind is full, the move is refused and nothing changes. If your team moves it to a time Bookatu would not offer, the extra resources are dropped, just as the room is. Cancelling frees everything it held, and the booking's page lists every resource it holds. Guide: https://bookatu.com/en-nz/help/services-that-need-a-room-and-equipment ### Let a client swap out of a late cancellation Quick swap is a setting, and it is off by default. When it is on, a client who would pay a late-cancellation fee or lose their deposit by cancelling now sees Ask to swap out beside Cancel (fee applies) on their booking page. Their time is offered to matching clients on your waitlist while they stay booked, and the first waiting client to take it gets the booking. A late cancellation usually leaves a gap you cannot fill. With Quick swap the time passes straight to someone who wants it, with the same team member, room and equipment, so the slot stays booked. The client who asked is released with no late-cancellation fee and no lost deposit, so they have a fair way out instead of not turning up. How to use it: 1. Open Settings, then Quick swap (under Essentials). Owners and admins can change it, and so can any role you give 'Manage the business'. Turn on 'Let clients swap out of a late cancellation'. 2. Under 'Stop offers before the start', set how many hours before the booking offers end, from 1 to 336 (2 by default). Under 'Their deposit, when a swap goes through', choose to refund it, to their card or to the credit they paid with, or to keep it as account credit for their next booking. Tap Save Quick swap. 3. Inside your late window, the client sees Ask to swap out beside Cancel (fee applies) on their booking page. When they tap 'Yes, offer my time', up to five waiting clients who want that service on that day (and that team member, if they chose one) get a one-tap link, your best-spending clients first. Anyone who joins the waitlist later is offered it too, until offers stop. The client stays booked and can tap 'Withdraw my request' until someone takes it. 4. The first waiting client to tap 'Take this spot' gets the booking, and pays their own deposit if one is due. The client who asked is cancelled with no fee and their deposit is handled the way you chose. You get an email and an alert, and see the swap on the calendar and in the booking. A refund Stripe refuses stays on the booking for you to handle. 5. If nobody takes it before offers stop, the client stays booked and is told so. They can still cancel, with the usual fee, or with the full price if you chose that in the next step. 6. Under 'If they cancel inside the last 2 hours', choose what a cancellation costs once offers have stopped: 'The usual late-cancellation fee' (the default), 'The full price, for bookings quick swap could offer', or 'The full price, for every booking'. The hours are the ones you set for offers to stop, or your free-cancellation window under Cancellation policy if that is shorter: the full price only ever applies where cancelling would already cost a fee or the deposit, so a cancellation that would be free stays free. The full price is what the client would have paid, every service of a visit, less any deposit you keep, up to your maximum fee, and one fee is queued for the whole visit. It needs 'Require a card to hold the booking' and a fee under Cancellation policy, so there is a card to charge. 7. The full price only applies to a booking made on your booking page, whose client saw it there before they confirmed. Bookings made by your team, through the API or an assistant, or with a card saved for an earlier booking, keep the usual fee, and so do bookings made before you chose it, or before you last switched it back on. The client's booking page and the 'still booked' email say what cancelling then costs, and the fee waits on the No-show fees screen for you to charge or let go, like any other. If you change your mind before you charge it (back to the usual fee, Quick swap off, or other hours), Charge takes the usual fee for when they cancelled instead, never more than either. If you change your cancellation policy before you charge it, the fee is not charged: the client agreed to the old terms for that booking. 8. Quick swap is never offered for a booking that is checked in, completed, a no-show, cancelled or already started, or one waiting for a deposit or for your answer. Classes, group bookings and bookings away from your premises or with travel are left out too, and nothing is offered while you approve online bookings first. A visit of several services swaps as a whole, only to a waiting client who wants all of it. Guide: https://bookatu.com/en-nz/help/quick-swap ### Invoice a company that pays by bank transfer Two different things get called an invoice, and Bookatu does both. A payment link is for a client who will pay by card there and then: they tap Pay now and the money reaches your Stripe account. An invoice document is for a business whose accounts department pays by bank transfer on their own schedule, such as a company booking hair and makeup for a shoot, or a venue paying for a class you ran. That one needs no card at all, so you can send it whether or not you have connected Stripe. You can also bill a booking straight from the calendar (see The calendar). An accounts department will not tap a Pay now button. It wants a document with a number on it, the company's own purchase-order reference, when payment is due, and where to send the money, and it will bounce anything missing those. This is the invoice most people currently make by hand in a separate invoice builder, retyping what is already in their calendar. How to use it: 1. Open Finance. Under Invoices, choose 'Invoice a company' rather than 'Payment link'. 2. Fill in the company, who it goes to, and their reference if they gave you a purchase-order number. Set the payment terms, 14 days being the usual. 3. Add a line for each thing you did, with a quantity and a price. The total, and your GST or VAT if you are registered, are worked out as you type. 4. Send it, and they get the invoice by email with a link to the document itself. They can print it or save it as a PDF for their records. You can open the same link any time from the invoice list. 5. When the transfer lands in your bank, open Finance and tap 'Mark paid' on that invoice. Ticked the wrong one? 'Not paid after all' puts it back. 6. Chasing a late one is one tap: 'Send again' re-sends the same invoice, with the same number, to the same address. 7. Put your bank details in Settings first. They appear on every invoice under 'How to pay', and without them the company has nothing to pay into. Guide: https://bookatu.com/en-nz/help/invoicing-a-company ### Bill a booking in parts Bill in parts splits one booking into several invoices: part now, the rest later. Each part has its own number and can be a payment link the client pays by card, or an invoice they pay by bank transfer. The final invoice bills whatever is left. Anything already paid towards the booking counts as paid, so it is not billed again, and each part carries its share of the tax. Paying in full stays the default on every invoice. Bigger jobs are often paid in stages: a share up front and the rest later. The booking shows what is paid and what is left, and you cannot bill more than is left. How to use it: 1. Open Settings, then Messaging & retention. Switch on Invoices, then switch on Bill in parts, which shows under it, and press Save settings. A business that signed up as a freelancer or contractor starts with both on. 2. Open the booking on the calendar or on its own page and press Invoice. Under How much, choose Part of it and type a percent or an amount. A percent is of the whole price. Left to bill shows what is left, and This invoice shows what this part bills. Invoicing needs a role with Manage the business and See analytics & earnings. 3. Choose Who pays and How they pay as for any invoice, then press Send to email it, or Create, don't send. How much only shows for one booking with nothing added to it. 4. The booking's Payment section now shows Price, Paid and Left to bill, and each part by its number, such as Part 1, with Open, Overdue or Paid. Press Bill part to send another part, or Bill the rest to send the final invoice for what is left. 5. The client gets each part you send as its own invoice. Its line starts with the part's number and names the service and the date. The final one starts The rest of. They pay a payment link by card and an invoice by bank transfer, as usual. 6. Open Finance to see Left to bill: each booking billed in parts with some of its price not on an invoice yet, with a button to open the booking. Under Booked and collected, what is still unpaid on a completed booking billed in parts shows as Billed in parts, not paid yet, and not under Payments owed. 7. Turning Bill in parts off stops new parts. Parts already sent still work, and you can still bill the rest. Guide: https://bookatu.com/en-nz/help/bill-a-booking-in-parts ### Send a client a payment link A payment link is an itemised invoice with a Pay now button. You add the lines, send it, and the client pays by card. The money goes to your own Stripe account, the same as a deposit does. You can also bill a booking straight from the calendar (see The calendar). Not everything you are owed comes through a booking. A colour correction that ran long, a product someone took home, a session agreed over text. This charges for it without asking anyone to read out a card number. How to use it: 1. Open Finance. Under Invoices, keep 'Payment link' selected. 2. Enter the client's email, then add a line for each item with a quantity and price. The total updates as you type. 3. Send it. They get an email with a Pay now button and pay by card. 4. To send it by text or WhatsApp as well, tap 'Copy link' on it under Recent invoices and paste it into your message. 5. The link does not go stale. Whenever they open it, today or in three weeks, it takes them to a live payment page, and if they have already paid it says so rather than charging twice. 6. Paid invoices show as paid in your list, and the money appears in your Stripe payouts like any other card payment. 7. This one needs Stripe connected, because it takes a card. If you have not connected it, send an invoice document instead and let them pay by transfer. Guide: https://bookatu.com/en-nz/help/sending-a-payment-link ### Set tiered commission and goal bonuses A tiered rule is a commission percentage that steps up with what a person sells in a pay period, like tax brackets. With 30% up to $5,000.00, then 40%, they earn 30% on their first $5,000.00 of sales in the period and 40% on the rest. A goal bonus is a fixed amount a person earns when their sales in a pay period reach a target you set. Your busiest people are rewarded without a spreadsheet at the end of each pay period. Every change applies from today and every earlier day keeps the rule it had, so a period you have already paid never changes. How to use it: 1. Open Money → Commission rules. To change rules you need 'Manage the business' and 'See analytics & earnings', which owners and admins have by default. 2. Under 'Set a tiered rule', pick Who (everyone, or one person) and For (every service, services in one category, every product, or products in one category). Enter the 'First rate (%)', then the amount under 'Then, on sales above' and its 'Rate (%)'. Add up to two more steps if you need them, then tap 'Save tiered rule'. 3. Under 'Goal bonuses', pick Who, choose what it Counts (services sold, products sold, or both), enter the target in 'When a pay period reaches' and the Bonus, then tap 'Save goal'. A goal set today counts for the pay period you are in. 4. Sales are counted after discounts and before tax, less refunds. A person's own rule or goal beats the one for everyone. Booth renters earn no commission or bonus. 5. Tiers and goals count per pay period. Until you set your pay periods on Payroll, they are calendar months. 6. See the results on Payroll (the Payroll button at the top of the page): commission with its tiers, and a Goal bonus column showing each person's sales against the target. Staff earnings shows commission line by line. Guide: https://bookatu.com/en-nz/help/tiered-commissions-and-goal-bonuses ### Set up a booth or chair renter A booth renter is someone on your team who rents a booth or a chair from you instead of working for commission. From the day you pick, they earn no commission or goal bonus, keep their own takings and tips, and owe you rent every week, every two weeks or every month. Their bookings stay in your calendar, but their money stays out of your team's pay. Payroll works out the rent due in each pay period and gives you a rent statement for them, and Staff earnings and Payroll list renters apart from your employees. How to use it: 1. Open Settings → Team and tap the pencil on the person's card. The Pay section at the bottom is shown to anyone with 'Manage the business' and 'See analytics & earnings', which owners and admins have by default. 2. Tick '[their name] rents a booth or chair'. Enter the Rent and choose when it is Due: Every week, Every two weeks or Every month. 3. Set 'Renting from' to today or a later day, then tap 'Save pay'. The first rent is due on that day, then every week, fortnight or month after it. A monthly rent due on the 29th to the 31st falls on the last day of a shorter month. 4. Their card now shows a Booth renter badge. To stop, untick the box, pick the day under 'Stops renting from' and tap 'Save pay'. Earlier days keep the commission and rent they had. 5. Open Payroll from the top of Money → Staff earnings. Renters have their own Booth renters table with their takings, tips and Rent owed, and a 'Rent statement' link listing the rent due in that pay period. 6. Renters are left out of the Wagepoint and ADP payroll files. The Payroll CSV includes them, marked as Booth renter. Guide: https://bookatu.com/en-nz/help/booth-rental ### Set pay periods and download payroll Payroll shows one pay period at a time, person by person: hours booked, services and products sold, commission, goal bonus, tips and the total. You choose whether pay periods run weekly, fortnightly, twice a month or monthly, and from which day. Until you set them, pay periods are calendar months. Pay day stops being a copy and paste job. The Payroll CSV holds every figure, and the Wagepoint and ADP Workforce Now files are laid out for those systems' imports, matched by each person's payroll number. Tips are their own column, never commissioned and never taxed. How to use it: 1. Open Money → Staff earnings (or Commission rules) and tap Payroll at the top. Seeing it needs 'See analytics & earnings'. It opens on the last pay period that ended; pick another under 'Pay period' and tap Show. 2. Under 'Pay periods', choose how often you Pay (Weekly, Fortnightly, Twice a month or Monthly) and the date under Starting, then tap 'Save pay periods'. A change can start from the first day of the pay period you are in, or a later day up to a year ahead. Monthly periods start on the 1st to the 28th, and twice a month runs from the 1st and the 16th. Changing them needs 'Manage the business' as well. 3. Add each person's payroll number, their Employee ID in Wagepoint or File # in ADP: Settings → Team, tap the pencil on their card and fill in 'Payroll number' under Pay, then tap 'Save pay'. Payroll lists anyone still missing one. 4. Under 'Download for your payroll system', tap 'Payroll CSV' or 'Wagepoint earnings file'. For ADP, enter your ADP company code, Batch ID and your Commission, Bonus and Tips codes, then tap 'ADP paydata file'. Downloads need 'Export data' and are recorded in the audit log. 5. The Payroll CSV has everyone, booth renters included: hours booked, visits, services and products before tax, refunds and voids, commission, goal bonus, tips, booth rent owed and the total. The Wagepoint and ADP files have employees only. 6. QuickBooks Payroll has no file import for commission, bonus or tips, so enter them in the pay run from the Payroll CSV. Guide: https://bookatu.com/en-nz/help/pay-periods-and-payroll-export ### Connect QuickBooks Online Bookatu can post each day's sales to your QuickBooks Online company as one journal entry per day (per location, if you have more than one): services and products at your tax codes, discounts, tips, deposits, refunds and the money taken, by how it was paid. Totals only, so no client is named in QuickBooks. Until Bookatu switches it on, the QuickBooks Online page says 'QuickBooks Online is not switched on for Bookatu yet', and the 'Export to QuickBooks' and 'Export to Xero' files on the Tax page carry the same sales for you to import. Your books stay up to date without importing a file, and the sales and tax sent for each day are the ones your Tax page shows, with GST, HST, PST and QST each on its own tax code. A day is never posted twice, and a day that changes in Bookatu in the week after is replaced the next night. How to use it: 1. Open Money → Tax and tap 'connect QuickBooks Online' under the export buttons. That link only appears once QuickBooks is switched on. You need 'Manage the business', 'See analytics & earnings' and 'Export data', which owners and admins have by default. 2. Tap 'Connect to QuickBooks', sign in at Intuit and choose your company. Bookatu asks for accounting access only. 3. Under 'Where each part of a day goes', check each account: Services sold, Products sold, Discounts, Refunds, Tips for the team, Deposits held, Bookatu clearing, and one for each way you are paid (Paid online (Stripe), Cash, Card on your own terminal, Bank transfer, Other ways of paying). They start filled in from your own chart of accounts. 4. Under 'Tax codes', check the QuickBooks code for each way you tax, such as GST + QST. A code is only suggested when its rates match yours exactly, so pick any that are left on 'Not chosen'. If your QuickBooks company uses locations, you can also tag each entry with one under QuickBooks locations. 5. Set the 'First day to send' (today, or up to a year back) and tap 'Save mapping'. Nothing is sent until you do. Pick a day after anything you already imported from the CSV export. 6. Each day is sent the night after it ends. 'Sync now' sends the days that are over straight away, 'Send one day again' replaces one day's entry, and 'Days sent' and the 'Sync log' say why any day was not sent. 'Disconnect QuickBooks' revokes Bookatu's access; what was already posted stays in QuickBooks. Guide: https://bookatu.com/en-nz/help/connecting-quickbooks-online ### Let clients book from their own AI assistant Bookatu runs a public booking server that a person's own AI assistant can connect to. When a client asks their assistant for a time with you, it looks you up from your booking link and checks your free times. It then holds the time the client picks. Bookatu emails the client a code and a link. Nothing is booked until the client gives the code to their assistant, or opens the link and confirms. More people hand everyday errands to an assistant, and a booking is one of them. Your free times and prices stay exactly as they are on your booking page, and if you accept bookings by hand, a booking from an assistant arrives as a request. Bookatu never takes payment in a chat. A service that takes a deposit is booked on your booking page, and the assistant gives the client the link. How to use it: 1. Open Settings, then Clients' AI assistants. If a checklist shows at the top, a line without a tick says what is still in the way, with a link to the page where you fix it. 2. Tick None of my services are health or medical care, when that is true of your business. Assistants can't book health services, and we record who ticked it and when. 3. Switch on Let clients' AI assistants book me. 4. To be found when a client's assistant searches by service and town, also switch on List me when assistants search. Without it, an assistant can still hold a time with you when a client gives it your booking link. 5. Under Services assistants can't book, pick anything you would rather clients book on your booking page. 6. Check What an assistant sees, which is what an assistant is told when it looks you up. To stop at any time, switch Let clients' AI assistants book me off again. 7. Every hold an assistant makes, and how it ended, shows in the Audit log. Under What, pick Clients' AI assistants. Guide: https://bookatu.com/en-nz/help/let-clients-book-from-their-ai ## Developer API (v1 REST) Base URL: https://bookatu.com/api/v1/{slug}. Replace {slug} with the business's URL slug. All responses are JSON; errors are { ok: false, error }. Authentication: public endpoints need none. Key-protected endpoints send "Authorization: Bearer bk_live_YOUR_KEY" or "X-Api-Key: bk_live_YOUR_KEY". - Keys are issued from the admin dashboard by an owner or admin with a confirmed email (or set up by Bookatu support on the business's behalf and labelled as such, see below), and shown exactly once at creation. Store them in a secret manager or environment variable; they cannot be retrieved again. - A key is a random token (bk_live_ followed by a 32-character id). Only its SHA-256 hash is stored, and verification uses a timing-safe comparison. - Keys support an optional expiry, are checked against revocation on every request, and record a lastUsedAt timestamp so you can audit usage. - Each key has scopes, picked when it is made: bookings:read, bookings:write, availability:read, catalog:read, catalog:write, staff:read, customers:read, reports:read, content:read, content:write, webhooks:read, webhooks:write, checkout:read, checkout:write, audit:read, customers:write, customers:manage, pos:write, marketing:write, enquiries:write, bookings:override, messages:read, messages:write. Every key-protected endpoint and every MCP tool needs exactly one, named on it below (GET /customers needs customers:read, reading bookings bookings:read, making, moving, cancelling or answering them and changing a class roster bookings:write, the money reports reports:read), and tools/list shows only the tools the key can call. A call outside the key's scopes returns 403 naming the scope it needed (missingScope in the body; error.data.missingScope over MCP). - checkout:read, checkout:write, audit:read, customers:write, customers:manage, pos:write, marketing:write, enquiries:write, bookings:override, messages:read, messages:write are carried only by a key made with them ticked: the checkout scopes are for another point of sale (such as Moneris MGR) checking bookings out, audit:read reads the audit log, and customers:write puts the business's tags on clients and takes them off. A key made before scopes never has them, whatever its access level, and neither does a connected app. Anything that names a client (their name, email and phone) needs customers:read as well. bookings:override lets a key book as Book anyway does on the calendar (outside opening hours, in the past, further ahead than clients can book, or over another booking), for importing bookings from another system; without it a key's bookings are held to the open slots. enquiries:write is for a website form's own key: it sends the form's enquiries into Leads (POST /enquiries) and lists the trip codes they may name (GET /enquiries/trips). It also moves an enquiry held for the business into Leads (POST /enquiries/held/{id}/release), and reaches nothing else. customers:manage adds a client and changes their name, email, phone or notes (never their marketing consent, and never a delete). pos:write records a product sold in person so its stock drops; it takes no payment. marketing:write posts a notice on the storefront. messages:read reads which automatic client messages are on and which were held back; messages:write turns them on or off and sends a held one now. - A key can never do more than the person who made it may do in the business: they can only give it scopes their role holds (customers:read needs Export data, reports:read needs See analytics & earnings), and if their role later loses a right, or they leave the team, their keys lose it too. A connected app is held to the person who approved it the same way. The one exception is a key or connected app Bookatu support sets up for a business: it acts on that business's behalf, with what the owner role could give, or with the maker's own role once they join the team, and whoami says so (credential.onBehalfOf names the business). A sandbox never gets one. - On the business MCP server, each tool also asks of that person what its own screen in the dashboard asks, on the business's Role permissions: a catalog or blog write needs Manage the business, and create_booking with asStaff needs Edit the calendar. A call their role no longer allows returns 403 with error.data.code MAKER_LACKS_PERMISSION and the permission it needed, and tools/list leaves the tool out. Once they leave the team, every tool returns 403 with MAKER_NOT_ON_TEAM, whether or not its screen asks a right, and tools/list offers none. A key that records nobody can never use asStaff: AS_STAFF_NEEDS_MAKER. - Keys made before scopes keep the access level they were made with: read-write or read-only. A read-only key may call the GET endpoints and read-only MCP tools, but write endpoints (creating or cancelling a booking) return 403. The checkout and audit scopes are the exception: such a key never has them. A key made before scopes that records who made it is held to that person the same way on the MCP server, and a rotated key records the person who rotated it. On the REST API too, such a key stops once that person is no longer on the business's team: its calls return 403 naming the scope, and the endpoints the MCP tools also serve answer with code MAKER_NOT_ON_TEAM. The dashboard marks them as legacy; replace them with scoped keys. - Revoke a key immediately from the dashboard if it is ever exposed. Revoked and expired keys stop authenticating at once. - When Bookatu suspends a business, its keys stop working. Every REST call with one of its keys answers 403 with code BUSINESS_SUSPENDED and livemode, and the words "This business is suspended, so its API keys are switched off. Contact Bookatu support." (it used to be a 401). The MCP server still answers 401. - Test keys start bk_test_ and belong to a sandbox business, a test business made for building and testing (see /developers/testing): a sandbox issues only test keys and a live business only bk_live_ keys, with the same scopes. A key of the other mode is refused with 403 and code LIVEMODE_MISMATCH, and every JSON answer says livemode (false from a sandbox), as does the Bookatu-Livemode header. The customer booking-management endpoints take no API key. A booking carries a manage key, the client's credential for changing it: it is the k query parameter on the manage link in the client's confirmation email, POST /book returns it as manageKey, and it may be sent as the X-Manage-Key header instead of k. With the appointment id alone, GET /booking/{id} answers a read-only status (access "view", no selfService), and the availability, reschedule and cancel endpoints answer 403 with code MANAGE_KEY_REQUIRED; with the key (access "manage") everything works as described. Bookings made before manage keys existed have none and are managed on their id alone, as the links already emailed for them expect. Ids are apt_ followed by a 16-character nanoid, and are scoped to the business in the URL, so a valid id or key from one business can never be read or acted on through another's. Treat the manage key, and the id, like a password: show them to nobody but the person who booked, and never store them where others can read them. Every one of these endpoints is rate limited per IP, returns only what the person who booked already knows, and answers a 404 for anything that is not this business's booking. The public endpoints (business, services, staff, availability, book) return Access-Control-Allow-Origin: * and answer the CORS preflight (OPTIONS) with 204, so any site or agent can call them directly from a browser. Key-protected endpoints deliberately do NOT send the wildcard: their allowed CORS origin is the platform's own origin, because business data has no legitimate cross-origin browser use. The customer booking-management endpoints (everything under /booking/{id}) do not send it either, and answer no preflight: they are authorised by the booking's manage key (or, for a booking from before manage keys, its id), which has no business being replayed from a third-party page. Neither restriction affects server-to-server or native mobile callers, which are not subject to browser CORS at all. Never embed a bk_live_ key in browser or mobile-client code. Call key-protected endpoints from your own server. Rate limits: Every answer of the v1 REST API and the MCP servers says where the call stands: RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (in seconds) for the window closest to its limit, and RateLimit-Policy naming every window it was counted against, for example 30;w=60, 2000;w=86400. Each key is limited on its own and with its business's other keys, per minute and per day, at its plan's numbers; the keyless endpoints are limited per address at each business; test keys and sandboxes have lower limits whatever the plan. A call past a limit is answered 429 with Retry-After: wait that long, and back off with jitter on repeated 429 and 5xx answers. The full table, the raised tier and how to back off are at /developers/rate-limits. The customer booking-management family under /booking/{id} is limited per IP, and each of those endpoints states its own budget. Every answer of the v1 REST API and the MCP servers also carries a Request-Id header, an id for that one call, for example req_V1StGXR8Z5jdHi6B. Quote it when you report a problem, so the call can be found. It is made by Bookatu for each call: a Request-Id you send is ignored. Booking statuses across responses: pending, confirmed, completed, cancelled, no_show. A separate, first-party mobile API (under /api/mobile) powers the Bookatu mobile experience. It is actively evolving and is intentionally not documented here, as its endpoints are still changing. For integrations, build against the v1 REST API or the MCP server documented on this page. ### GET /api/v1/{slug}/business: Business profile + opening hours No authentication required. The business profile: name, industry, country, currency, timezone, locale, address, phone, the public booking link, and the full week of opening hours. Lets an agent introduce the business and know when it is open before checking availability. At a business that lets clients book several services in one visit, visits says so, with the most services one visit takes: { "maxServices": 4 } (absent everywhere else). At a business that asks booking questions for every service, questions lists those (each service's own are on GET /services); absent otherwise. It also says what the business's own page shows, by the same rules as that page: emailBase64 (the business's email in base64, exactly as its page hands it to the browser, only while the business shows it publicly, else null; the plain address is never in this answer, so decode it only when someone chooses to email), links (its website and profiles), tagline and logoUrl (null when not set), and storefront: cover (the page's first photo, else null), photos (its gallery in order, each with a caption or null and a focal point from 0 to 100), team (whether the page shows its team), trips (the trips of whole days the page shows, each with its days, its price in minor units with priceLabel in the business's language, its photo and the enquireUrl of its enquiry page; display only, never listed on GET /services or bookable on POST /book), enquireUrl (the enquiry page while there are trips, else null) and map (the place and a directionsUrl while the address is shown, else null). No authentication required. Errors: - 404: No business exists for the {slug}. - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/business ``` Example response: ``` { "name": "Maison Vera", "slug": "maison-vera", "industry": "nails", "country": "NZ", "currency": "NZD", "timezone": "Pacific/Auckland", "locale": "en-NZ", "address": "12 Queen St, Auckland", "phone": "09 555 0100", "emailBase64": null, "links": [{ "type": "website", "url": "https://maisonvera.example/", "display": "maisonvera.example" }], "tagline": "Nails and brows in the heart of the city.", "logoUrl": "https://bookatu.com/img/maison-vera/logo.webp", "bookingUrl": "https://bookatu.com/maison-vera/book", "hours": [ { "weekday": 0, "open": false, "openMin": null, "closeMin": null, "breakStartMin": null, "breakEndMin": null }, { "weekday": 1, "open": true, "openMin": 540, "closeMin": 1080, "breakStartMin": 780, "breakEndMin": 840 }, { "weekday": 2, "open": true, "openMin": 540, "closeMin": 1080, "breakStartMin": null, "breakEndMin": null }, { "weekday": 3, "open": true, "openMin": 540, "closeMin": 1080, "breakStartMin": null, "breakEndMin": null }, { "weekday": 4, "open": true, "openMin": 540, "closeMin": 1080, "breakStartMin": null, "breakEndMin": null }, { "weekday": 5, "open": true, "openMin": 540, "closeMin": 1140, "breakStartMin": null, "breakEndMin": null }, { "weekday": 6, "open": true, "openMin": 600, "closeMin": 960, "breakStartMin": null, "breakEndMin": null } ], "storefront": { "cover": { "url": "https://bookatu.com/img/maison-vera/1.webp", "focalX": 50, "focalY": 40 }, "photos": [{ "url": "https://bookatu.com/img/maison-vera/1.webp", "caption": null, "focalX": 50, "focalY": 40 }], "team": true, "enquireUrl": null, "trips": [], "map": { "caption": "12 Queen St, Auckland", "query": "12 Queen St, Auckland, NZ", "directionsUrl": "https://www.google.com/maps/search/?api=1&query=12%20Queen%20St%2C%20Auckland%2C%20NZ" } } } // hours always has all 7 days. weekday 0 = Sunday .. 6 = Saturday. // openMin / closeMin are minutes from local midnight, and are null when closed. // breakStartMin / breakEndMin are a mid-day closure (Monday above shuts 1pm to // 2pm) and are null when the day runs straight through. A day with a break // trades openMin-breakStartMin and breakEndMin-closeMin, and NOTHING between: // treat the outer pair alone as open all day and you will send someone to a // locked door. ``` ### GET /api/v1/{slug}/services: List active, online-bookable services No authentication required. The org's public profile plus every service that is active and bookable online, ordered by sort order then name. Use a service id and durationMin when checking availability and booking. At a business with extras, each service also has addOns: the extras offered with it under the business's combination rules ({ id, name, description, priceCents, durationMin, addsTime }; addsTime true means its durationMin is added to the booking). Pass their ids as addOnIds when booking. A business with no extras returns no addOns. Every service also says how clients meet the business for it, as its booking page tells them: meetingType is place (at the business), venue (an address set on each booking), client (at the client's place), online (a call link), trip or none (no meeting, the work is delivered), or null when nothing says so (it is never guessed). And noticeHours is the notice a booking of it needs to cancel or change for free, in hours: the service's own when it has one, else the business's free cancellation window. A service with combination rules lists them as combinations: onlyWith, the only other services it can share a visit with (absent: any), and neverWith, the services and extras it is never booked with, whichever of the two set it (a 4 braids and a 6 braids, say). A service two or more of the team do at once says how many as peopleNeeded. Each only when there is something to say, so every other row is exactly as it was. A service that needs two or more kinds of resource at once (a treatment room and a laser machine, say) lists them as resourceKinds, in order: a time is offered only when a person and one free resource of each kind are free together, and a booking of it holds one of each for its whole length, the first kind's as the booking's own room. Absent on a service that needs one kind or none, so its row is exactly as it was. A service the business asks booking questions for lists them as questions, in the order they are asked: { id, type (text, textarea, radio, checkboxes, yes_no, number or date), label, required, helpText?, options? (radio and checkboxes), allServices? (true: asked for every service) }. Answer them as answers on POST /book; a required one must be answered (422 ANSWERS_REQUIRED). A service with no questions has no questions field. A service that lasts whole days (a trip) is booked by the business only (its New booking form and POST /appointments) and is never listed or booked here. No authentication required. Errors: - 404: No business exists for the {slug}. - 500: Unexpected server error. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/services ``` Example response: ``` { "org": { "name": "Maison Vera", "slug": "maison-vera", "currency": "NZD", "timezone": "Pacific/Auckland" }, "services": [ { "id": "svc_abc123", "name": "Gel Manicure", "description": "Long-lasting gel polish with cuticle care.", "category": "Nails", "durationMin": 60, "priceCents": 7500, "currency": "NZD", "meetingType": "place", "noticeHours": 24, "questions": [ { "id": "bq_hairlength", "type": "yes_no", "label": "Are your nails longer than 1 cm?", "required": true, "helpText": "So we book enough time." }, { "id": "bq_heard", "type": "radio", "label": "How did you hear about us?", "required": false, "options": ["A friend", "Instagram"], "allServices": true } ] } ] } // description is the service description, or null when none is set. // meetingType is null when nothing says how clients meet the business for it. // noticeHours is the service's own notice, else the business's window. // questions is there only on a service the business asks booking questions // for: answer them as answers on POST /book. ``` ### GET /api/v1/{slug}/staff: List bookable team members No authentication required. The bookable team members (id, name, title, bio) so an agent can offer "book with X". Public-facing fields only, never staff email or phone. No authentication required. Errors: - 404: No business exists for the {slug}. - 500: Unexpected server error. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/staff ``` Example response: ``` { "org": { "name": "Maison Vera", "slug": "maison-vera", "timezone": "Pacific/Auckland" }, "staff": [ { "id": "stf_abc", "name": "Anna", "title": "Senior Nail Tech", "bio": null } ] } // title and bio are null when not set. ``` ### GET /api/v1/{slug}/availability: Open slots for a service No authentication required. Bookable slots for a service across a date window. The engine accounts for opening hours, existing appointments, blocked time (one-off or weekly, for a person, for everyone, or for a room or chair the service needs: when another room of the kind is free the slot stays and uses it), buffer times, resources and minimum booking notice. Each slot's startAt is a UTC ISO 8601 string ready to pass straight to a booking call. Each time also comes as when: { utc, primary, business: { timeZone, local, utcOffset, abbr, display }, client } with the offset in force on that day (a slot after the clocks change carries the new one), on the business's clock (the branch's at a branch) and, when the client's zone is known, on theirs (client is null otherwise; dayDiffers says their date is another day). Quote display rather than converting a time yourself. timeZone names the clock the slots and the from/to dates are on. No authentication required. This is the read for a NEW booking: to move an existing one, use GET /booking/{id}/availability instead, because this read counts that booking's own slot as busy. A slot a surcharge covers (a public holiday or a busy time the business charges more for) also carries priceCents (the price before it, before any discount code), surcharges (the one that applies: label, amountType percent or fixed, amount as a whole percent or in minor units, and amountCents, what it adds) and totalCents, what the booking comes to at that time. When two of the business's surcharges cover one time, only the higher applies, so surcharges has one entry. Show it to the client before they book. Every other slot has none of these fields. Parameters: - serviceId (query, required): An active, online-bookable service id. - from (query, required): Start date, YYYY-MM-DD. - to (query, required): End date, YYYY-MM-DD. Must be on or after from, and at most 60 days later. - staffId (query, optional): Restrict slots to one team member. - partySize (query, optional): How many people are coming, 1 to 50. Only times with a table that seats them come back (for a service that takes a group: a room that seats them all and a person free), and each slot then names the tables that fit (resourceIds), smallest first. Pass one straight back as resourceId when booking. Omit to apply no capacity filter. - addOnIds (query, optional): The extras the booking will have, comma-separated ids from the service's addOns. Extras with addsTime make the booking longer, so only times with room for the longer booking come back. Omit for the service on its own. - locationId (query, optional): One of this business's branches. Slots then follow that branch's own opening hours and only the team and rooms based there, plus anyone based at no branch (who works at all of them). Omit to search the whole business. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected, and the answer widens back to the whole business. - clientTimeZone (query, optional): The client's own time zone, the IANA zone of a place (America/Toronto): each slot's when then gives the time on their clock too. Abbreviations (EST, which would be read as Panama), offsets (+13:00) and Etc/ zones are refused with code UNKNOWN_TIME_ZONE (400): ask the person which city they are in. Never guessed from the request. Errors: - 400: serviceId is missing, from/to are not YYYY-MM-DD, from is later than to, or the range exceeds 60 days; or clientTimeZone is not a place's zone (code UNKNOWN_TIME_ZONE). Or from or to is a date that does not exist, such as 30 February ("Use a real date in YYYY-MM-DD format."), or is too far away ("Ask for dates in the next few years."). - 404: The {slug} is unknown, or the serviceId is not an active, online-bookable service in this org. - 500: Unexpected server error. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/availability?serviceId=svc_abc123&from=2026-06-10&to=2026-06-14" ``` Example response: ``` { "org": { "name": "Maison Vera", "slug": "maison-vera", "timezone": "Pacific/Auckland" }, "days": [ { "date": "2026-06-10", "open": true, "slots": [ { "startMin": 540, "startAt": "2026-06-09T21:00:00.000Z", "when": { "utc": "2026-06-09T21:00:00Z", "primary": "business", "business": { "timeZone": "Pacific/Auckland", "local": "2026-06-10T09:00:00+12:00", "utcOffset": "+12:00", "abbr": "NZST", "display": "Wednesday, 10 June at 9:00 am NZST" }, "client": null } } ] }, { "date": "2026-06-11", "open": false, "slots": [] } ], "timeZone": "Pacific/Auckland", "datesAreOn": "business" } // startMin is minutes from local midnight; startAt is the UTC instant to book. // A slot on a date the business charges a surcharge on also has: // "priceCents": 8000, // "surcharges": [{ "label": "Public holiday surcharge", "amountType": "percent", "amount": 15, "amountCents": 1200 }], // "totalCents": 9200 ``` ### POST /api/v1/{slug}/book: Create a booking (online source) No authentication required. The customer-facing booking call, with no key and no account, so nobody calling it has proved who they are. The slot is validated server-side (race-condition safe) and a booking reference is returned. A booking's ref is the business's prefix, a dash and 6 characters, such as MV-7QK2M9 at a business named Maison Vera. Treat it as text: a booking made earlier keeps the ref it was given. As an online-source booking it fully respects availability and minimum notice. A customer record is matched by email then phone or created, but an email match changes nothing: every customer is treated as new (a business that approves new clients' bookings gets a request), no deposit is waived, nothing on an existing record is filled in, and the answer is the same for a known email and an unknown one. A service that takes a deposit is refused with 409 and code DEPOSIT_NEEDS_BOOKING_PAGE, with bookingPageUrl, the business's own booking page where the deposit can be paid; nothing is booked. So is a service the business requires a card saved to hold (409, code CARD_REQUIRED_USE_BOOKING_PAGE, with bookingPageUrl): a card is only ever saved in the booking page's own card step. At a business that has set booking terms, the person must accept them: send acceptTerms: true (and the termsVersion they were shown); without it the answer is 422 with code TERMS_NOT_ACCEPTED and the terms to show, and nothing is booked. At a business that asks booking questions (GET /services lists them on each service as questions), send the person's answers as answers; a required question without an answer is 422 with code ANSWERS_REQUIRED and missingQuestionIds, an answer that cannot be read 422 ANSWERS_INVALID with invalidAnswers, and nothing is booked. The appointmentId in the answer is the person's private key to their booking: never show it, store it or put it in a chat; the person manages the booking from the confirmation email they are sent. The manageKey beside it is what changes the booking, and is just as private: an app of the person's own sends it as k (or X-Manage-Key) to /booking/{id}. The answer's when is the booked time on the business's clock and, with clientTimeZone, the client's. A booking made at a surcharged time also has priceCents (its total, the surcharge included) and surcharge: { label, amountCents }; a booking without one has neither. A booking keeps the surcharge it was made with. A service that lasts whole days (a trip) is booked by the business only (its New booking form and POST /appointments) and is never listed or booked here. To retry safely after a timeout, send an Idempotency-Key header: the same key with the same email and body within 24 hours answers what the first call answered, with idempotentReplay: true and the Idempotent-Replayed header, and books nothing more. A key is never shared between two people, as it is held per email. A replay does not carry manageKey (the client has it in their confirmation email), and carries a note saying so. With no Idempotency-Key, the very same request (the same email and every field the same) sent again within two minutes books nothing more either: it answers 200 with the first booking, idempotentReplay: true and the Idempotent-Replayed header, without manageKey, and with a note saying so. Any other body, or the same one once the first booking is cancelled, books as normal. Still send an Idempotency-Key when you retry: it holds for 24 hours, not two minutes. No authentication required; at most 5 bookings per address per business in 10 minutes and 15 a day, and 40 a day per business. Parameters: - serviceId (body, required): An active, online-bookable service id from GET /services. - startAt (body, optional): An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00.000Z") or "2026-06-10T21:00:00+12:00", in whole minutes. Read strictly: no offset is a 422 with code TIME_NEEDS_OFFSET and an example on the business's clock; a date that does not exist, seconds other than :00 or anything else is a 422 with code TIME_INVALID. Nothing is booked or moved either way. Send startAt or localTime, exactly one. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. - name (body, required): Customer name, 2 to 80 characters (trimmed). - email (body, required): A valid email address. - phone (body, required): 6 to 30 characters; digits, spaces and + ( ) - only. - staffId (body, optional): Specific staff id. Omit to let the system assign a free team member. - notes (body, optional): Free text, max 500 characters. - partySize (body, optional): How many people are coming, 1 to 50. Restaurants: only a table that seats the party is used, and the booking records the covers. A service that takes a group: no more than its most, in a room that seats them all, still with a person, and priced per head when the service is. Omit for a booking for one seat, which is every appointment-style booking. - resourceId (body, optional): A specific table (or room) of this business to prefer. Honoured only while it is genuinely free for that time; otherwise the smallest one that fits the party is assigned. An id that is not this business's is ignored. - repeat (body, optional): Book this visit and repeats of it as one series: { "everyDays": 14, "visits": 6 } or { "monthly": true, "visits": 6 }, where visits counts every visit, this one included. POST /appointments (a key with bookings:write): every 1 to 365 days or monthly, 2 to 26 visits, each repeat checked against the calendar. POST /book: only what the business lets clients repeat online (its services, every 1 to 4 weeks or monthly, up to its most visits), else 422 with nothing booked. A repeat that is not free is left out and listed with why, never forced in; only the first visit can need a deposit. The answer then has a series: { id, every, bookedCount, skippedCount, visits: [{ index, startAt, status: booked | skipped, appointmentId?, ref?, code?, reason? }] }. Omit to book one visit. - marketingConsent (body, optional): Only when the customer agreed to get marketing email from this business: { "source": "website_form", "wording": "the exact words they agreed to" } (source up to 60 characters, wording 10 to 2000). Through this call the yes is never taken on its own: a new customer is emailed by the business to confirm it, and is subscribed only once they do. Omit it when they did not agree: nobody is opted in by default, and a customer already on file keeps the choice they made. Malformed is a 422 with nothing booked. - addOnIds (body, optional): Extras to add, up to 20: ids from the service's addOns in GET /services (only the extras the business offers with that service are listed there). One the service does not take under the business's combination rules (an extra it does not offer, or two that are never together) is a 409 with the reason, e.g. "Gloss can't be added to 4 braids.", and nothing is booked. Each extra is added to the price; one with addsTime also makes the booking longer by its durationMin, so ask GET /availability with the same addOnIds first. Omit to book no extras. - locationId (body, optional): The branch this booking is for, recorded on the appointment so the customer is told the right address. Omit for a business with one address. An id that is not this business's, or names a branch that is currently closed, is ignored, and the booking then follows the assigned team member's own branch. - acceptTerms (body, optional): true once the person has read and accepted the business's booking terms. Required, as true, while the business has set terms: without it the answer is 422 with code TERMS_NOT_ACCEPTED and terms ({ text, version }) to show them, and nothing is booked. Show terms.text as plain text. A business with no terms never asks, and ignores it. - termsVersion (body, optional): The terms.version the person was shown (the SHA-256 of the text). When sent and it is not the version in force (the business changed its terms meanwhile), the answer is the same 422 TERMS_NOT_ACCEPTED with the terms in force, so they are shown again. - answers (body, optional): The person's answers to the business's booking questions, as { [questionId]: answer }, the questions GET /services lists on each service (questions). A string for text (up to 300 characters), textarea (up to 2000), radio (one of its options), number (a plain decimal) and date (YYYY-MM-DD); a list of its options for checkboxes; true or false for yes_no. Every required question must be answered: else the answer is 422 with code ANSWERS_REQUIRED and missingQuestionIds, and nothing is booked. An answer that cannot be read is 422 with code ANSWERS_INVALID and invalidAnswers ({ [questionId]: too_long | not_an_option | not_a_number | not_a_date | not_yes_or_no | bad_value }). An answer to a question the booking does not ask is ignored. The answers are kept for the business only: never echoed back, never in a webhook. A business with no questions never asks, and ignores it. - clientTimeZone (body, optional): The client's own time zone, the IANA zone of a place (America/Toronto), kept on the booking so their emails and pages show their clock too; the answer's when gives the time on both clocks. Abbreviations (EST, which would be read as Panama), offsets (+13:00) and Etc/ zones are refused with code UNKNOWN_TIME_ZONE (422, nothing booked): ask the person which city they are in. Never guessed from the request. - Idempotency-Key (header, optional): Optional. 16 to 64 visible characters, a new one for each booking the person makes and the same one when you send that booking again (after a timeout, say). A retry with the same key, email and body within 24 hours answers what the first call answered, with idempotentReplay: true, and books nothing more. Browsers may send it (CORS allows it). Errors: - 400: The request body is not valid JSON. - 422: Validation failed: the response includes a fieldErrors map naming each invalid field (e.g. email, phone). A startAt with no offset has code TIME_NEEDS_OFFSET and an example in the business's zone; one that is not a real RFC 3339 date-time on a whole minute, or both startAt and localTime, has code TIME_INVALID, as has a startAt too far away to book (send a date in the next few years); a localTime the clocks skip that day has code TIME_DOES_NOT_EXIST with nextValid, one they show twice TIME_AMBIGUOUS with both candidates; a timeZone or clientTimeZone that is not a place's zone has code UNKNOWN_TIME_ZONE. At a business with booking terms, a booking without acceptTerms: true (or with a termsVersion that is not the one in force) has code TERMS_NOT_ACCEPTED and terms { text, version } to show. At a business with booking questions, a required question left without an answer has code ANSWERS_REQUIRED and missingQuestionIds (the ids, in the order asked); an answer that cannot be read has code ANSWERS_INVALID and invalidAnswers. Nothing is booked. - 422: code NOT_ON_TEAM at fieldErrors.staffId: the staffId is not on the business's team ("That person isn't on your team. Choose someone who is, or Any available."). Pick a staffId from GET /staff, or leave it out for anyone free. Nothing is booked. - 409: Nothing was booked: the slot was just taken, the service is unavailable, inactive or not offered online, the service takes a deposit (code DEPOSIT_NEEDS_BOOKING_PAGE, with bookingPageUrl), the business requires a card saved to hold it (code CARD_REQUIRED_USE_BOOKING_PAGE, with bookingPageUrl), or the business is not taking online bookings right now (code BOOKING_PAUSED). - 429: Too many bookings: 5 per address per business in 10 minutes, 15 a day, or 40 a day at the business through this call. The response carries Retry-After. - 400: IDEMPOTENCY_MISMATCH: the Idempotency-Key is not 16 to 64 visible characters, or it was used with the same email for a different booking in the last 24 hours. Send a new key. Nothing was booked. - 409: IDEMPOTENCY_IN_PROGRESS: the first request with this Idempotency-Key is still running. Try again after Retry-After. - 409: BOOKING_IN_PROGRESS: with no Idempotency-Key, the same booking was sent a moment ago and is still being made. Wait retryAfterSec seconds (the Retry-After header says the same), then send it again: it answers the first booking. - 404: No business exists for the {slug}. - 500: Unexpected server error. Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/book \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 6f1c2a9e-4b7d-4e21-9c3a-booking-0001" \ -d '{ "serviceId": "svc_abc123", "startAt": "2026-06-10T09:00:00Z", "name": "Alex Smith", "email": "alex@example.com", "phone": "+64 21 555 0100" }' ``` Example response: ``` { "ok": true, "ref": "MV-7QK2M9", "appointmentId": "apt_abc123", "manageKey": "3q2-Lr8xN0b6VfJm1oZ4sYtKcE9uWgHdAiPkQnTwXeU", "status": "confirmed", "needsPayment": false } // status is "pending" for a request the business still has to accept. // At a surcharged time (a public holiday), also: // "priceCents": 9200, "surcharge": { "label": "Public holiday surcharge", "amountCents": 1200 } // appointmentId and manageKey are the person's private keys to their booking: // never show them, store them or put them in a chat; they manage it from the // email they are sent. An app of their own sends manageKey as k (or // X-Manage-Key) to /booking/{id} to cancel or move it. // A service that takes a deposit is refused, and nothing is booked: // HTTP 409 { "ok": false, "error": "This service takes a deposit, which can only be paid on the business's booking page. Nothing was booked: send the person to bookingPageUrl.", "code": "DEPOSIT_NEEDS_BOOKING_PAGE", "bookingPageUrl": "https://bookatu.com/maison-vera/book?service=svc_abc123" } // So is a service the business requires a card saved to hold: // HTTP 409 { "ok": false, "error": "This service needs a card saved to hold the booking, which can only be done on the business's booking page. Nothing was booked: send the person to bookingPageUrl.", "code": "CARD_REQUIRED_USE_BOOKING_PAGE", "bookingPageUrl": "https://bookatu.com/maison-vera/book?service=svc_abc123" } // At a business with booking terms, a booking without acceptTerms: true: // HTTP 422 { "ok": false, "error": "This business asks clients to accept its booking terms to book. Show the person the terms (terms.text), and send acceptTerms: true only once they have accepted them. Nothing was booked.", "code": "TERMS_NOT_ACCEPTED", "terms": { "text": "Please arrive 10 minutes early.", "version": "3f2a…" } } // At a business with booking questions, a booking without a required answer: // HTTP 422 { "ok": false, "error": "This business asks a few questions before it takes this booking. Send the answers to the required questions (missingQuestionIds), or book on the business's booking page.", "code": "ANSWERS_REQUIRED", "missingQuestionIds": ["bq_hairlength"] } ``` ### GET /api/v1/{slug}/booking/{id}: Read one booking (the customer's own) No API key. Authorised by the booking's manage key (k, or X-Manage-Key); the appointment id alone reads a read-only status. The JSON twin of the manage-booking page a customer reaches from their confirmation email: their booking, its service, its team member, its price and deposit, plus the business's cancellation policy and what the customer may still change online (selfService), worked out by the same rules the web page and the change endpoints apply: whether a cancel or a move would be accepted now and why not, until when online changes stay open, how many online moves are left, and, when the business lets customers choose someone else when they move, who they may choose. Authorised by the booking's manage key (k or X-Manage-Key; no API key, no account) and deliberately narrow; with the appointment id alone it answers a read-only status (access "view": no selfService, no quickSwap): only what the person who booked already knows. No customer record, no notes, no other bookings. When the booking is one service of a visit of several, visit lists the visit's services still on ({ id, services: [{ appointmentId, service, staff, startAt, endAt, durationMin, priceCents, status }] }), and selfService is the visit's, under the rules of its first service. A booking two or more of the team do at once also has booking.additionalStaff: the others' names, besides staff. At a business that switched Quick swap on, quickSwap says what the manage-booking page would offer about swapping out of a late cancellation: status (null, requested, claimed, withdrawn or expired), requestedAt, cutoffAt (when offers stop), canAsk and, when not, block (off, approval, closed, not_confirmed, checked_in, request_open, not_offered, asked, past_cutoff or not_late), and canWithdraw (the client's ask stands and the time is still on offer: false once the business has stopped offering it, for example by switching Quick swap off). Read only: the customer asks and withdraws on the web page. Inside the last hours before the start (after cutoffAt, the hours the business set for offers to stop, or its free-cancellation window if that is shorter), a business may have chosen to charge a client who cancels the full price of the booking (for a visit, every service of it still on, as one fee), less any deposit it keeps, up to its maximum fee: for every booking, or only for bookings Quick swap could offer. It applies only where cancelling would already cost a late-cancellation fee or the deposit, only where the business requires a card to hold bookings, and only to a booking made on the business's booking page whose client was shown it there before confirming: a booking made through this API, an assistant or by the business, or before the business chose it, keeps the usual late-cancellation fee. If the business later changes its Quick swap choice or hours, the usual fee is charged instead; if it changes its cancellation policy, the fee is not charged; a no-show is charged as before. The manage-booking page says what cancelling would cost. when is the booking's start on the business's clock and, when the client's zone was kept with the booking, on theirs (source "booking"). A booking made at a surcharged time also has surcharge: { label, amountCents }, part of priceCents. policy.cancellationWindowHours is this booking's own notice: its service's when the service has one, else the business's free cancellation window. Rate limited to 30 requests per IP every 5 minutes. Parameters: - id (path, required): The appointment id, as returned by POST /book (apt_…). - k (query, optional): The booking's manage key: manageKey from POST /book, or the k on the client's manage link. The X-Manage-Key header works too. Needed to read in full (with the id alone it is a read-only status) a booking that has one; bookings from before manage keys have none. Errors: - 404: No business exists for the {slug}, or no booking with that id in this business (the same 404 either way: a distinct response would confirm an id exists somewhere). - 429: More than 30 requests from one IP in 5 minutes. The response carries Retry-After. - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/booking/apt_abc123 ``` Example response: ``` { "org": { "slug": "maison-vera", "name": "Maison Vera", "currency": "NZD", "timezone": "Pacific/Auckland" }, "booking": { "id": "apt_abc123", "ref": "MV-7QK2M9", "status": "confirmed", "startAt": "2026-06-10T21:00:00.000Z", "endAt": "2026-06-10T22:00:00.000Z", "durationMin": 60, "service": "Gel Manicure", "staff": "Anna", "priceCents": 7500, "depositCents": 2000, "addOns": [{ "name": "Nail art", "priceCents": 1500 }] }, "policy": { "cancellationWindowHours": 24, "forfeitDepositOnLateCancel": true }, "selfService": { "canCancel": true, "canReschedule": true, "cancelBlocked": null, "rescheduleBlocked": null, "changesCloseAt": "2026-06-09T21:00:00.000Z", "movesLeft": 2, "canChangeStaff": true, "staffOptions": [ { "id": "stf_anna", "name": "Anna", "current": true }, { "id": "stf_mia", "name": "Mia", "current": false } ], "message": null, "contact": null } } // policy is the cancellation policy this booking is held to: cancelling or // moving more than cancellationWindowHours before the start is free, and // inside that window a paid deposit is kept when forfeitDepositOnLateCancel is // true. cancellationWindowHours is this booking's own notice: its service's // when the service has one, else the business's free cancellation window. // ref and staff are null when unset; addOns is [] when there are none. // // selfService is what the customer may change online right now. canCancel and // canReschedule say whether POST /cancel and POST /reschedule would be accepted; // when not, cancelBlocked / rescheduleBlocked carry the same code those // endpoints' 409 does: cancel_off or reschedule_off (the business takes that // change by phone or email only), past_cutoff, reschedule_limit, cancel_closed // or move_closed (the booking is cancelled, completed, a no-show or has // started), or deposit_unpaid (rescheduleBlocked only: the booking is held // until its deposit is paid, and cannot be moved before). changesCloseAt is when online changes stop (null: never); movesLeft // is null when there is no limit. staffOptions lists who the booking can be // moved to (the booked person first, current: true) and is [] unless // canChangeStaff. message and contact are what the web page shows instead of // the changes the business keeps for itself, in its language: null when // nothing is kept back, and for a booking that is over. // // At a business that switched Quick swap on there is also quickSwap, e.g. // { "status": null, "requestedAt": null, "cutoffAt": "2026-06-10T19:00:00.000Z", // "canAsk": true, "block": null, "canWithdraw": false }: whether the customer // may ask to swap out of a late cancellation on the web page now, and when // offers stop. ``` ### GET /api/v1/{slug}/booking/{id}/availability: Open slots for MOVING this booking No API key. Authorised by the booking's manage key (k, or X-Manage-Key); the appointment id alone reads a read-only status. Bookable slots for moving an existing booking, across a date window. This differs from GET /availability in two ways that matter: the booking's own slot is EXCLUDED from the busy set (otherwise an appointment's own hold hides the very time its owner is trying to shift around), and the fit uses the booking's own service and its own length, which is not always the service's default, because an add-on or a duration override can make the booking longer. Pass a returned startAt straight to POST /booking/{id}/reschedule. Authorised by the booking's manage key (k or X-Manage-Key); with the id alone it answers 403 MANAGE_KEY_REQUIRED. For one service of a visit of several, the slots are the starts the whole visit fits, each service keeping its person and length, and visit gives its id and its whole length ({ id, durationMin }). Rate limited to 30 requests per IP every 5 minutes. Parameters: - id (path, required): The appointment id being moved. - k (query, optional): The booking's manage key: manageKey from POST /book, or the k on the client's manage link. The X-Manage-Key header works too. Needed to list move times for a booking that has one; bookings from before manage keys have none. - from (query, required): Start date, YYYY-MM-DD. - to (query, required): End date, YYYY-MM-DD. Must be on or after from, and at most 60 days later. - locationId (query, optional): One of this business's branches. Slots then follow that branch's own opening hours and only the team and rooms based there, plus anyone based at no branch (who works at all of them). Omit to search the whole business. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected, and the answer widens back to the whole business. - staffId (query, optional): Someone else to move the booking to: an id from selfService.staffOptions on GET /booking/{id}. Omitted, the slots are the booked team member's. Anyone the business does not let the customer choose returns no days. Errors: - 400: from/to are not YYYY-MM-DD, from is later than to, or the range exceeds 60 days. Or from or to is a date that does not exist, such as 30 February ("Use a real date in YYYY-MM-DD format."), or is too far away ("Ask for dates in the next few years."). - 404: No business exists for the {slug}, or no booking with that id in this business. - 429: More than 30 requests from one IP in 5 minutes. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/booking/apt_abc123/availability?from=2026-06-10&to=2026-06-14" ``` Example response: ``` { "org": { "slug": "maison-vera", "name": "Maison Vera", "timezone": "Pacific/Auckland" }, "booking": { "id": "apt_abc123", "durationMin": 60 }, "days": [ { "date": "2026-06-10", "open": true, "slots": [ { "startMin": 540, "startAt": "2026-06-09T21:00:00.000Z" } ] }, { "date": "2026-06-11", "open": false, "slots": [] } ] } // booking.durationMin is the length being fitted (the booking's, not the // service's default). startMin is minutes from local midnight; startAt is the // UTC instant to send back when rescheduling. ``` ### POST /api/v1/{slug}/booking/{id}/reschedule: Move a booking to a new time No API key. Authorised by the booking's manage key (k, or X-Manage-Key); the appointment id alone reads a read-only status. The customer-facing reschedule: the same call the manage-booking web page makes, with the same strict rules. The new time is validated as a real, open slot: opening hours, existing bookings, buffers, resources and the business's minimum booking notice all apply, and the booking's own hold is excluded so it can be moved within its own slot. A time that is not bookable returns 409 with the reason, and nothing changes. The booking keeps its team member unless the availability engine has to reassign it, and its length is unchanged. Moving a booking fires the booking.rescheduled webhook and updates any connected calendar. Only an upcoming pending or confirmed booking can be moved: a cancelled, completed, no-show or past booking returns 409 (the same rule as the web page), so a cancelled booking can never be quietly reinstated. For one service of a visit of several, the whole visit moves: every service keeps its person and length, startAt is the first service's new start, it counts once against the business's limit on moves, and nobody else can be picked (staffId). Rate limited to 10 requests per IP every 10 minutes. Parameters: - id (path, required): The appointment id to move. - k (query, optional): The booking's manage key: manageKey from POST /book, or the k on the client's manage link. The X-Manage-Key header works too. Needed to move a booking that has one; bookings from before manage keys have none. - startAt (body, optional): The new start time, e.g. a startAt from GET /booking/{id}/availability, in the future. An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00.000Z") or "2026-06-10T21:00:00+12:00", in whole minutes. Read strictly: no offset is a 422 with code TIME_NEEDS_OFFSET and an example on the business's clock; a date that does not exist, seconds other than :00 or anything else is a 422 with code TIME_INVALID. Nothing is booked or moved either way. Send startAt or localTime, exactly one. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. Read on the booking's branch's clock when it is at one. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. - staffId (body, optional): Move the booking to someone else: an id from selfService.staffOptions on GET /booking/{id}, only when the business lets customers choose (canChangeStaff). A change of person counts as a move, at the same time or not. Omitted, the booking keeps its team member. Errors: - 400: The request body is not valid JSON. - 422: Neither startAt nor localTime was sent, or both were; startAt has no offset (code TIME_NEEDS_OFFSET, with an example) or is not a real RFC 3339 date-time on a whole minute (TIME_INVALID); localTime is a time the clocks skip that day (TIME_DOES_NOT_EXIST, with nextValid) or show twice (TIME_AMBIGUOUS, with both candidates); timeZone is not a place's zone (UNKNOWN_TIME_ZONE); the time is in the past; or staffId is not a string. Nothing is moved. - 409: The time is not bookable (already taken, outside opening hours, or inside the minimum booking notice). The response carries the reason. Also returned when the booking is cancelled, completed, a no-show, or has already started, and when the business's online-change rules refuse the move; then the response also carries blocked (reschedule_off, past_cutoff, reschedule_limit, staff_not_offered for a person the customer may not choose, or deposit_unpaid for a booking held until its deposit is paid) and the business's contact { phone, email }. - 404: No business exists for the {slug}, or no booking with that id in this business. - 429: More than 10 requests from one IP in 10 minutes. Also when this booking, or this address at the business, has made too many changes in a short while: the same limit the manage-booking page has. Nothing is moved or cancelled. The response carries Retry-After. - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/booking/apt_abc123/reschedule \ -H "Content-Type: application/json" \ -d '{ "startAt": "2026-06-12T21:00:00.000Z" }' ``` Example response: ``` { "ok": true, "startAt": "2026-06-12T21:00:00.000Z" } // startAt echoes the time that was taken, so the new booking can be rendered // without a second read. ``` ### POST /api/v1/{slug}/booking/{id}/cancel: Cancel a booking (the customer's own) No API key. Authorised by the booking's manage key (k, or X-Manage-Key); the appointment id alone reads a read-only status. The customer-facing cancellation: the same call the manage-booking web page makes, so the cancellation policy, any deposit refund or forfeiture, the booking.cancelled webhook, the waitlist re-offer and the cancellation emails the business may have switched on are identical however it is triggered. The forfeited flag says whether a paid deposit was kept under the policy, which an app needs in order to tell the person the truth on the confirmation screen. Cancelling an already-cancelled booking is idempotent (alreadyCancelled: true), so a retry after a dropped connection is safe. Only an upcoming pending or confirmed booking can be cancelled: a completed, no-show or started booking returns 409. For one service of a visit of several, the whole visit is cancelled, under the rules of its first service, with one email each way. Rate limited to 10 requests per IP every 10 minutes. Parameters: - id (path, required): The appointment id to cancel. - k (query, optional): The booking's manage key: manageKey from POST /book, or the k on the client's manage link. The X-Manage-Key header works too. Needed to cancel a booking that has one; bookings from before manage keys have none. Errors: - 409: The booking could not be cancelled. The response carries the reason. When the business's online-change rules refuse it, or the booking is over, it also carries blocked (cancel_off, past_cutoff or cancel_closed) and the business's contact { phone, email }, as selfService on GET /booking/{id} predicts. - 404: No business exists for the {slug}, or no booking with that id in this business. - 429: More than 10 requests from one IP in 10 minutes. Also when this booking, or this address at the business, has made too many changes in a short while: the same limit the manage-booking page has. Nothing is moved or cancelled. The response carries Retry-After. - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/booking/apt_abc123/cancel ``` Example response: ``` { "ok": true, "alreadyCancelled": false, "forfeited": false } // forfeited is true when a paid deposit was kept under the cancellation policy // (see policy on GET /booking/{id}). ``` ### GET /api/v1/{slug}/customers: List customers Requires an API key. Needs the customers:read scope. Up to 1000 customers in this org (id, name, email, phone and tags), ordered by name. tags lists the business's own tags on it ({ id, name, color }: color is a palette name such as indigo or rose), in name order, [] for none. Tags are the team's internal labels: never show them to a client, and they are never in a webhook payload. Requires a valid API key whose org matches the {slug}. The person who made the key must still have "Export data" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool list_customers. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the customers:read scope (the body names it as missingScope). - 404: No business exists for the {slug}. - 500: Unexpected server error. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/customers \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "customers": [ { "id": "cus_xyz", "name": "Alex Smith", "email": "alex@example.com", "phone": "+64211234567", "tags": [{ "id": "tag_vip123", "name": "VIP", "color": "indigo" }] } ] } // Capped at 1000 customers, ordered by name. ``` ### GET /api/v1/{slug}/appointments: List appointments Requires an API key. Needs the bookings:read scope. By default, upcoming appointments with status pending or confirmed whose startAt is now or later, ordered by start time, capped at 200. Optional filters let you pull a specific window or statuses, and limit/offset page through results. When more rows may exist, the response includes nextOffset. Each row says where the booking came from: source (online: the client; phone, walk_in or admin: the team, the API or the phone app; magic_fill: a waitlist claim), leadSource (the tag it came in with, as stored, e.g. a booking link's ?via=) and channel (google, instagram, facebook, apple_maps or bing for a client who came through one of the business's booking links, else null); seriesId names the repeat series a booking is a visit of, and visitId the visit of several services it is one of (each null when it is neither; GET /visits/{id} reads a visit). notifyClient is false for a booking whose client Bookatu does not message (made with notifyClient: false on POST /appointments, or switched off on the booking's page), else true. A trip (a booking of a service that lasts whole days) also has startDate and endDate (its first and last day on the business's calendar, both inclusive) and days, after notifyClient; startAt is its first day's midnight there and endAt the midnight after its last day. Other bookings have none of the three. A booking that two or more of the team do at once also has additionalStaffIds: the others on it besides staffId, in their order (absent on every other booking). A booking of a service that needs two or more kinds of resource at once, or one holding more than one resource, also has resources: every room, chair or machine it holds, { id, name, kind }, its own room first and then the others in the order of the service's resourceKinds. A booking saved without one of its kinds lists only what it holds ([] for nothing). Absent on every other booking. Quick swap: a booking whose client asked to swap out of a late cancellation (the business offers the time to its waitlist while the client stays booked) also has swap ({ status, requestedAt, cutoffAt, closedAt, claimedAppointmentId }). status is requested (offered to the waitlist until cutoffAt), claimed (a waiting client took it over: claimedAppointmentId is their booking, and this one is cancelled with no fee), withdrawn or expired (nobody took it by the cutoff, or the booking changed since). The ask is on the first service of a visit. Absent on every other booking, so a business that never switched Quick swap on reads exactly as before. tags lists the business's own tags on it ({ id, name, color }: color is a palette name such as indigo or rose), in name order, [] for none. Tags are the team's internal labels: never show them to a client, and they are never in a webhook payload. A booking's ref is the business's prefix, a dash and 6 characters, such as MV-7QK2M9 at a business named Maison Vera. Treat it as text: a booking made earlier keeps the ref it was given. Requires a valid API key scoped to this org. The person who made the key must still have "See everyone's calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool list_appointments. Parameters: - from (query, optional): Lower time bound, ISO 8601. Overrides the default "now". Use it to list a past window. - to (query, optional): Upper time bound, ISO 8601 (inclusive). - status (query, optional): Comma-separated statuses to include: pending, confirmed, completed, cancelled, no_show. Defaults to pending + confirmed. - limit (query, optional): Page size, 1 to 200 (default 200). - offset (query, optional): Rows to skip, for pagination. The response carries nextOffset when more may exist. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope). - 404: No business exists for the {slug}. - 500: Unexpected server error. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/appointments?status=completed&from=2026-06-01&limit=50" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "appointments": [ { "id": "apt_abc123", "ref": "MV-7QK2M9", "serviceName": "Gel Manicure", "startAt": "2026-06-10T21:00:00.000Z", "endAt": "2026-06-10T22:00:00.000Z", "durationMin": 60, "priceCents": 7500, "status": "confirmed", "customerId": "cus_xyz", "staffId": "stf_abc", "notes": null, "createdAt": "2026-06-01T03:12:00.000Z", "notifyClient": true, "source": "online", "leadSource": "google", "channel": "google", "seriesId": null, "visitId": null, "tags": [{ "id": "tag_bridal456", "name": "Bridal", "color": "rose" }] } ] } // Only pending + confirmed, startAt >= now, oldest first, max 200 rows. ``` ### GET /api/v1/{slug}/services/{id}: Get one service No authentication required. A single active, online-bookable service by id, in the same shape as a row of GET /services, addOns included at a business with extras. Every service also says how clients meet the business for it, as its booking page tells them: meetingType is place (at the business), venue (an address set on each booking), client (at the client's place), online (a call link), trip or none (no meeting, the work is delivered), or null when nothing says so (it is never guessed). And noticeHours is the notice a booking of it needs to cancel or change for free, in hours: the service's own when it has one, else the business's free cancellation window. A service with combination rules lists them as combinations: onlyWith, the only other services it can share a visit with (absent: any), and neverWith, the services and extras it is never booked with, whichever of the two set it (a 4 braids and a 6 braids, say). A service two or more of the team do at once says how many as peopleNeeded. Each only when there is something to say, so every other row is exactly as it was. A service that needs two or more kinds of resource at once (a treatment room and a laser machine, say) lists them as resourceKinds, in order: a time is offered only when a person and one free resource of each kind are free together, and a booking of it holds one of each for its whole length, the first kind's as the booking's own room. Absent on a service that needs one kind or none, so its row is exactly as it was. A service the business asks booking questions for lists them as questions, in the order they are asked: { id, type (text, textarea, radio, checkboxes, yes_no, number or date), label, required, helpText?, options? (radio and checkboxes), allServices? (true: asked for every service) }. Answer them as answers on POST /book; a required one must be answered (422 ANSWERS_REQUIRED). A service with no questions has no questions field. No authentication required. Parameters: - id (path, required): The service id (from GET /services). Errors: - 404: No business exists for the {slug}, or no active, online-bookable service with that id. - 500: Unexpected server error. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/services/svc_abc123 ``` Example response: ``` { "id": "svc_abc123", "name": "Gel Manicure", "description": "Long-lasting gel polish with cuticle care.", "category": "Nails", "durationMin": 60, "priceCents": 7500, "currency": "NZD", "meetingType": "place", "noticeHours": 24 } ``` ### GET /api/v1/{slug}/appointments/{id}: Get one appointment Requires an API key. Needs the bookings:read scope. A single appointment by id, scoped to the key's org (a key for one business can never read another's). Same lean shape as a row of GET /appointments, source, leadSource, channel, seriesId, visitId, notifyClient and tags included. notifyClient is false for a booking whose client Bookatu does not message (made with notifyClient: false on POST /appointments, or switched off on the booking's page), else true. A trip (a booking of a service that lasts whole days) also has startDate and endDate (its first and last day on the business's calendar, both inclusive) and days, after notifyClient; startAt is its first day's midnight there and endAt the midnight after its last day. Other bookings have none of the three. A booking that two or more of the team do at once also has additionalStaffIds: the others on it besides staffId, in their order (absent on every other booking). A booking of a service that needs two or more kinds of resource at once, or one holding more than one resource, also has resources: every room, chair or machine it holds, { id, name, kind }, its own room first and then the others in the order of the service's resourceKinds. A booking saved without one of its kinds lists only what it holds ([] for nothing). Absent on every other booking. Quick swap: a booking whose client asked to swap out of a late cancellation (the business offers the time to its waitlist while the client stays booked) also has swap ({ status, requestedAt, cutoffAt, closedAt, claimedAppointmentId }). status is requested (offered to the waitlist until cutoffAt), claimed (a waiting client took it over: claimedAppointmentId is their booking, and this one is cancelled with no fee), withdrawn or expired (nobody took it by the cutoff, or the booking changed since). The ask is on the first service of a visit. Absent on every other booking, so a business that never switched Quick swap on reads exactly as before. tags lists the business's own tags on it ({ id, name, color }: color is a palette name such as indigo or rose), in name order, [] for none. Tags are the team's internal labels: never show them to a client, and they are never in a webhook payload. A booking made at a surcharged time also has surcharge: { label, amountCents }, part of priceCents. A read-only key may call this. Requires a valid API key scoped to this org. Parameters: - id (path, required): The appointment id. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope). - 404: No business exists for the {slug}, or no appointment with that id in this org. - 500: Unexpected server error. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123 \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "id": "apt_abc123", "ref": "MV-7QK2M9", "serviceName": "Gel Manicure", "startAt": "2026-06-10T21:00:00.000Z", "endAt": "2026-06-10T22:00:00.000Z", "durationMin": 60, "priceCents": 7500, "status": "confirmed", "customerId": "cus_xyz", "staffId": "stf_abc", "notes": null, "createdAt": "2026-06-01T03:12:00.000Z", "notifyClient": true, "source": "phone", "leadSource": null, "channel": null, "seriesId": "ser_abc123", "visitId": null, "tags": [] } ``` ### POST /api/v1/{slug}/appointments: Create a booking (admin source) Requires an API key. Needs the bookings:write scope. Create a booking with source: admin and the same body as POST /book, plus requestDeposit, additionalStaffIds (the others on a booking two or more of the team do at once, then named in the answer too) and notifyClient (false: Bookatu never messages the client about this booking; the team's alerts and the webhooks are unchanged). For a service that needs two or more kinds of resource at once (resourceKinds on GET /services), the engine holds one free resource of each kind at a time it offers, resourceId prefers the first kind's one (the room), and the answer lists everything the booking holds as resources ({ id, name, kind }); at a time the engine does not offer it may hold fewer, exactly as a room is left off, and resources says what it holds. The other resources are always the engine's choice and cannot be named. To book a visit of several services, use POST /visits. A booking made with a key is held to the business's open slots: a time outside its opening hours, in the past, further ahead than its clients can book, or not free for the person asked for (or for anyone, when staffId is left out) is refused with 409, and nothing is written, the client included. A key made with the opt-in bookings:override scope books as Book anyway does on the calendar instead (any time, over another booking), for importing bookings from another system; even then the same person is never booked twice at the same start. Each booking counts against the key's booking window and the business's day of bookings made through its keys and connected apps (each visit of a repeat counts); past either the answer is 429 with Retry-After, and the owner is told once when the day's is reached. Use POST /book for customer-facing flows. A booking made at a surcharged time also has priceCents (its total, the surcharge included) and surcharge: { label, amountCents }; a booking without one has neither. A booking keeps the surcharge it was made with. A service that lasts whole days (a trip: Services, Length in Whole days) is booked by its days, startDate with endDate or with days, never by a time, and is priced once per booking; the answer then has startDate, endDate and days too. Its person must be free on every one of its days, and each resource its service needs is held for them; it takes no extras and does not repeat. notifyClient: false keeps its client unmessaged, as for any booking. Requires a valid API key scoped to this org. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_booking. Parameters: - serviceId (body, required): An active, online-bookable service id from GET /services. - startAt (body, optional): An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00Z"), in whole minutes. A time with no offset is a 422 TIME_NEEDS_OFFSET with an example on the business's clock; a date that does not exist or seconds other than :00 are TIME_INVALID. Send startAt or localTime, exactly one. - name (body, required): Customer name, 2 to 80 characters (trimmed). - email (body, required): A valid email address. - phone (body, required): 6 to 30 characters; digits, spaces and + ( ) - only. - staffId (body, optional): Specific staff id. Omit to let the system assign a free team member. - notes (body, optional): Free text, max 500 characters. - partySize (body, optional): How many people are coming, 1 to 50. Restaurants: only a table that seats the party is used, and the booking records the covers. A service that takes a group: no more than its most, in a room that seats them all, still with a person, and priced per head when the service is. Omit for a booking for one seat, which is every appointment-style booking. - resourceId (body, optional): A specific table (or room) of this business to prefer. Honoured only while it is genuinely free for that time; otherwise the smallest one that fits the party is assigned. An id that is not this business's is ignored. - repeat (body, optional): Book this visit and repeats of it as one series: { "everyDays": 14, "visits": 6 } or { "monthly": true, "visits": 6 }, where visits counts every visit, this one included. POST /appointments (a key with bookings:write): every 1 to 365 days or monthly, 2 to 26 visits, each repeat checked against the calendar. POST /book: only what the business lets clients repeat online (its services, every 1 to 4 weeks or monthly, up to its most visits), else 422 with nothing booked. A repeat that is not free is left out and listed with why, never forced in; only the first visit can need a deposit. The answer then has a series: { id, every, bookedCount, skippedCount, visits: [{ index, startAt, status: booked | skipped, appointmentId?, ref?, code?, reason? }] }. Omit to book one visit. - marketingConsent (body, optional): Only when the customer agreed to get marketing email from this business: { "source": "website_form", "wording": "the exact words they agreed to" } (source up to 60 characters, wording 10 to 2000). Recorded as their consent, with the time and those words (Canada's anti-spam law asks for that proof). Omit it when they did not agree: nobody is opted in by default, and a customer already on file keeps the choice they made. Malformed is a 422 with nothing booked. - addOnIds (body, optional): Extras to add, up to 20: ids from the service's addOns in GET /services (only the extras the business offers with that service are listed there). One the service does not take under the business's combination rules (an extra it does not offer, or two that are never together) is a 409 with the reason, e.g. "Gloss can't be added to 4 braids.", and nothing is booked. Each extra is added to the price; one with addsTime also makes the booking longer by its durationMin, so ask GET /availability with the same addOnIds first. Omit to book no extras. - locationId (body, optional): The branch this booking is for, recorded on the appointment so the customer is told the right address. Omit for a business with one address. An id that is not this business's, or names a branch that is currently closed, is ignored, and the booking then follows the assigned team member's own branch. - requestDeposit (body, optional): POST /appointments only. true asks the client for a deposit, as the staff booking form can: the booking is confirmed and waits on its deposit (the service's, by the business's deposit policy), and the client is sent a secure pay link to the business's own Stripe Checkout by email (and by text when they agreed to texts). Refused before anything is booked when the business cannot take card payments (409, reason no_payments), the service takes no deposit (422, reason no_deposit) or there is no email to send the link to (422, reason no_email). The answer then has depositRequest: { sent: true, amountCents, emailedTo, texted, expiresAt } or { sent: false, reason, message } (the booking is still made; send the link with POST /appointments/{id}/deposit-request). Omit for a booking with no deposit asked for, exactly as before. - additionalStaffIds (body, optional): For a service two or more of the team do at once (peopleNeeded on GET /services): the others on the booking besides staffId, as the New booking form's Also with names them, ids from GET /staff, up to peopleNeeded minus one. Omit to let the engine pick whoever else does it and is free. The answer then has additionalStaffIds. A 422 with nothing booked for a service one person does, an id that is not one of this business's active team, or staffId itself. - notifyClient (body, optional): POST /appointments only. false makes a booking whose client Bookatu never messages, for a business that writes to its own clients: no confirmation, booking request or decline, reminder, ask to confirm they are coming, thank-you or review request, move or cancellation notice, deposit or payment request, "did you make this booking?" check or Quick swap message, by email or text, while it stays off. Someone who may edit the calendar can switch it on or off on the booking's page, and each change is in the audit log; on again, the next message due goes, never the ones held while it was off. The team's own alerts and the webhooks are unchanged. Marketing still follows the client's own consent, so leave marketingConsent out for a client Bookatu should never write to. A series (repeat) made with it is quiet on every visit. Left out, the confirmation follows the business's client message switches (GET /client-messages): under 'Only send client messages when we press Send', or with the confirmation switched off, it is held and never sent later. true sends the confirmation (and, with requestDeposit: true, the deposit link) even while those switches would hold it, as the team pressing Send does. The answer's clientMessage says what became of the confirmation: sent (sent, or going out just after the answer), pending (its text waits for the business's quiet hours to end), held (the message switches held it, or the business is in test mode or not live yet), not_sent (nothing went: the client has no email address and gets no text) or off (notifyClient: false). Refused with requestDeposit: true (422, fieldErrors.notifyClient), since the pay link is sent to the client. The keyless doors (POST /book, POST /visits/book) do not take it: a booking made there always tells the person who booked. - startDate (body, optional): For a service that lasts whole days (a trip) only, and then instead of startAt or localTime: its first day, YYYY-MM-DD, on the business's own calendar. Send endDate or days with it. The trip covers its first to last day in full: it starts at the first day's midnight on the business's clock and ends at the midnight after the last day, whatever the clocks do in between, and holds its person (staffId, or nobody when left out) for every one of those days. Sent for a service of minutes it is a 422 (fieldErrors.startDate). - endDate (body, optional): With startDate: the trip's last day, YYYY-MM-DD, inclusive (1 to 8 Dec is endDate 2026-12-08, 8 days). Not before startDate, and not with days. - days (body, optional): With startDate, instead of endDate: how many days the trip lasts, a whole number from 1 to 60, the first day included. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. Errors: - 400: The request body is not valid JSON. - 422: Validation failed: the response includes a fieldErrors map naming each invalid field (e.g. email, phone). Also returned when startAt is not a parseable ISO 8601 date-time, or names a date too far away to book (code TIME_INVALID: send a date in the next few years). - 422: code NOT_ON_TEAM at fieldErrors.staffId: the staffId is not on the business's team ("That person isn't on your team. Choose someone who is, or Any available."). Pick a staffId from GET /staff, or leave it out for anyone free. Nothing is booked. - 409: The time is outside opening hours, in the past, further ahead than clients can book, or not free (without bookings:override), the service is unavailable / inactive, or that exact staff member is already booked at that instant. With requestDeposit, also when the business cannot take card payments (reason no_payments). A trip whose first day has passed. Nothing is booked. For a trip, also when its person is already booked on those days ("Sam is already booked on those days."), or no resource of a kind it needs is free on them; nothing is booked. - 429: The key's booking window, or the business's day of bookings through its keys and connected apps, is used up. Retry-After says when to try again. Nothing is booked. - 422: With requestDeposit: it is not true or false, the service takes no deposit (reason no_deposit), or there is no email to send the pay link to (reason no_email). With additionalStaffIds: the service is done by one person, an id is not one of this business's active team or is staffId, or there are more than it needs (fieldErrors.additionalStaffIds). With notifyClient: it is not true or false, or it is false with requestDeposit: true (fieldErrors.notifyClient). For a service that lasts whole days: a time sent instead of startDate (fieldErrors.startDate, or fieldErrors.startAt with startDate too), a date that is not YYYY-MM-DD and real (fieldErrors.startDate or fieldErrors.endDate), no endDate or days (fieldErrors.endDate), an endDate before startDate, endDate and days together (fieldErrors.days), more than 60 days, or a repeat (fieldErrors.repeat). For a service of minutes: any of startDate, endDate or days (fieldErrors.startDate). Nothing is booked. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or it is a key made before scopes that is read-only (creating a booking needs a read-write key). - 404: No business exists for the {slug}. - 500: Unexpected server error. - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "serviceId": "svc_abc123", "startAt": "2026-06-10T09:00:00Z", "name": "Alex Smith", "email": "alex@example.com", "phone": "+64 21 555 0100" }' ``` Example response: ``` { "ok": true, "ref": "MV-7QK2M9", "appointmentId": "apt_abc123", "status": "confirmed", "needsPayment": false, "clientMessage": "sent" } // When a deposit is required, status is "pending" and a payLink is returned: { "ok": true, "ref": "MV-7QK2M9", "appointmentId": "apt_abc123", "status": "pending", "needsPayment": true, "clientMessage": "sent", "payLink": "https://bookatu.com/maison-vera/book/success?apt=apt_abc123" } ``` ### POST /api/v1/{slug}/appointments/{id}/cancel: Cancel a booking Requires an API key. Needs the bookings:write scope. Cancel a booking. Scoped to the key's org, so a key for one business can never touch another's data. Fires the booking.cancelled webhook and re-offers the freed slot to the waitlist. A paid deposit follows the business's cancellation policy, as when the client cancels: inside the notice window it is kept, and the forfeited flag is true. Send refundDeposit: true to refund it whatever the policy says. Cancelling an already-cancelled booking is idempotent. A key that cancels many bookings in a few minutes is stopped for a while (429) and the owner is told. Requires a valid API key scoped to this org. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool cancel_booking. Parameters: - id (path, required): The appointment id to cancel. - reason (body, optional): Optional cancellation reason, truncated to 200 characters and stored on the booking. - refundDeposit (body, optional): Optional. true refunds a paid deposit whatever the notice policy says. Left out, the policy decides. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or it is a key made before scopes that is read-only (cancelling needs a read-write key). - 404: No business exists for the {slug}, or no booking with that id in this business (body { ok: false, error: "Booking not found" }). - 400: The booking exists but could not be cancelled; error says why. - 422: refundDeposit is not true or false (fieldErrors.refundDeposit). Nothing is cancelled. - 429: The key cancelled too many bookings in a short time. Retry-After says when to try again. Nothing is cancelled. - 500: Unexpected server error. - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/cancel \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "reason": "Customer requested" }' ``` Example response: ``` { "ok": true, "id": "apt_abc123", "forfeited": false } ``` ### GET /api/v1/{slug}/appointments/{id}/checkout: What a booking comes to at checkout (MGR hand-off) Requires an API key. Needs the checkout:read scope, on a key made with it ticked. For a point of sale that is not Bookatu's (Moneris MGR, or any other): start checkout from a booking and carry it into your sale rather than ringing it up again by hand. The answer is the sale Bookatu's own point of sale would open with: the booking and its ref, the client, who it is with, each line (the service, then each extra; every service of a visit of several services) at its booked price and discount with the person credited for it (staffId, staffName), each line's tax and the tax lines as the point of sale would charge them (tax.mode: included in the prices, added on top at checkout, or none), the deposit already paid (depositPaidCents) and dueCents: what is left to take, tax added on top included and the deposit taken off. Charge exactly dueCents, then POST the sale back to the same address. checkout.allowed says whether it can be checked out now; when not, checkout.blocked says why (not_live: finished, cancelled or a no-show; deposit_pending: the client is still paying an online deposit; already_checked_out: then sale is the sale that closed it, whichever point of sale took it; invoiced: it is on an invoice, which is how it is paid, so do not take money for it at a point of sale). Each line's lineId is stable while the booking is open; name it to credit a line to someone else when you post the sale. The client comes by id (customer.id); their name, email and phone come too only when the key also has customers:read. A visit of several services is one sale under its first service, whichever service's id you ask with. Requires an API key made with the checkout:read scope ticked (the scope needs See everyone's calendar). Changes nothing. The person who made the key must still have "See everyone's calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_checkout. Parameters: - id (path, required): The appointment id (from GET /appointments or GET /appointments/{id}). Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it does not carry the checkout:read scope (the body names it as missingScope). Only a key made with checkout:read ticked carries it: a key made before scopes never does, whatever its access level. - 404: No business exists for the {slug}, or no appointment with that id in this business (the same 404 either way). - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/checkout \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "version": 1, "appointment": { "id": "apt_abc123", "ref": "MV-7QK2M9", "status": "confirmed", "startAt": "2026-06-10T21:00:00.000Z", "endAt": "2026-06-10T22:10:00.000Z", "serviceName": "Cut", "customerId": "cus_xyz", "staffId": "stf_sam", "source": "online", "visitId": null }, "customer": { "id": "cus_xyz", "name": "Jane Doe", "email": "jane@example.com", "phone": "+16045550100" }, "staff": { "id": "stf_sam", "name": "Sam" }, "currency": "CAD", "lines": [ { "lineId": "apt_abc123:service", "kind": "service", "appointmentId": "apt_abc123", "label": "Cut", "qty": 1, "unitCents": 4000, "discountCents": 400, "totalCents": 3600, "taxCents": 432, "serviceId": "svc_cut", "staffId": "stf_sam", "staffName": "Sam" }, { "lineId": "apt_abc123:add_on:1", "kind": "add_on", "appointmentId": "apt_abc123", "label": "Head massage", "qty": 1, "unitCents": 1500, "discountCents": 0, "totalCents": 1500, "taxCents": 180, "serviceId": "svc_massage", "staffId": "stf_sam", "staffName": "Sam" } ], "subtotalCents": 5500, "discountCents": 400, "totalCents": 5100, "tax": { "mode": "added", "taxCents": 612, "lines": [ { "rateId": "gst", "label": "GST", "rateMilli": 5000, "taxCents": 255 }, { "rateId": "pst", "label": "PST", "rateMilli": 7000, "taxCents": 357 } ] }, "depositPaidCents": 2000, "dueCents": 3712, "checkout": { "allowed": true, "blocked": null }, "sale": null } // A booking already checked out: dueCents 0, checkout.blocked // "already_checked_out", and sale is the sale that closed it: // "sale": { "id": "sale_x1y2z3", "receipt": "X1Y2Z3", "at": "2026-06-10T22:12:00.000Z", "source": "moneris_mgr", "externalSaleId": "MGR-000123", "method": "Card", "tender": "card", "collectedCents": 3712, "saleTotalCents": 3712, "tipCents": 500, "products": [] } // // sale.source is "bookatu" for Bookatu's own point of sale (externalSaleId // null), else the name the outside point of sale posted. tax.lines[].rateId is null for a business // with one tax inside its prices. customer has only id without customers:read. ``` ### POST /api/v1/{slug}/appointments/{id}/checkout: Post an outside sale back: the booking is checked out (MGR hand-off) Requires an API key. Needs the checkout:write scope, on a key made with it ticked. The sale your point of sale took for the booking. The booking is checked out exactly as Bookatu's own point of sale checks it out: one sale linked to the booking (its receipt number on Bookatu's side), a line for the service and each extra credited to who did it, the booking's payment on the ledger (so it drops off Payments owed), the tip and who got it, and the booking is completed, with the thank-you, loyalty points and booking.completed webhook every completed booking gets. It is idempotent on externalSaleId: the same sale posted again (a retry after a dropped connection) finds the sale it made, answers replayed: true and writes nothing more, so it is always safe to retry. amountCents must be the checkout's dueCents: a sale for a different amount is refused with the amount it comes to (amount_mismatch), because two points of sale that disagree on the price cannot both be right in the books; change the booking's price in Bookatu first. A tip is recorded only when the business has switched on Accept tips at checkout, as at its own point of sale (sale.tipCents says what was). Products you sell with it stay in your own system. Fires booking.checked_out to the endpoints subscribed to it. The answer is the checkout payload as GET now returns it, with ok and replayed. Requires an API key made with the checkout:write scope ticked (the scope needs Edit the calendar). Parameters: - id (path, required): The appointment id. For a visit of several services, any of its services: the whole visit is checked out. - externalSaleId (body, required): Your point of sale's own id for the sale, 1 to 100 printable characters without spaces. The idempotency key: unique per business and point of sale, so it can close one booking only. Never a card number: one that looks like a card number is refused (400, reason card_number). - source (body, optional): Which point of sale took it, e.g. "moneris_mgr": lower-case letters, digits, dot, dash or underscore, up to 40. Defaults to "external". "bookatu" is Bookatu's own point of sale and is refused, and so is a name that looks like a card number (400, reason card_number). - amountCents (body, required): What you took for the booking, in whole cents, tip excluded: the checkout's dueCents (0 when the deposit covered it all). - currency (body, optional): ISO 4217 code; when given it must be the business's currency. - tender (body, required): How it was paid: card, cash or other. Recorded as Bookatu's point of sale records its own (Card, Cash, Other). - tipCents (body, optional): The tip, in whole cents, beside the amount and never inside it. Omit or 0 for none. - tipSplit (body, optional): Who got the tip: [{ staffId, amountCents }], adding up to tipCents, each person once and on the business's team. Omit to split it by the business's own rule. - lines (body, optional): Who did a line, when it was not the booking's person: [{ lineId, staffId }], lineId from the checkout payload, staffId one of the business's active team (GET /staff). Lines not named stay credited as booked. Errors: - 400: The request body is not valid JSON, or externalSaleId or source looks like a card number (reason card_number; fieldErrors names the field, never the number). Card numbers are never accepted. Nothing was recorded. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it does not carry the checkout:write scope (the body names it as missingScope). Only a key made with checkout:write ticked carries it: a key made before scopes never does, whatever its access level. - 404: No business exists for the {slug}, or no appointment with that id in this business. - 409: Nothing was recorded, and reason says why: amount_mismatch (amountCents is not what the booking comes to; expectedCents and currency say what it does), already_checked_out (another sale closed it; saleId names it), external_sale_used (that externalSaleId from this point of sale is already another booking's sale), lines_changed (a lineId is not one of the booking's lines: it changed since you read it), not_live (finished, cancelled or a no-show), deposit_pending (the client is still paying an online deposit) or invoiced (it is on an invoice, which is how it is paid). - 422: Nothing was recorded: a field is malformed (fieldErrors names each; a staffId in lines that is not on the team is one), the currency is not the business's (reason currency), or the tip or its split does not add up (reason tip or tip_split). - 503: Checking bookings out from another point of sale is still being switched on for this business (its database is being updated). Nothing was recorded; retry shortly with the same externalSaleId. - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/checkout \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "externalSaleId": "MGR-000123", "source": "moneris_mgr", "amountCents": 3712, "currency": "CAD", "tender": "card", "tipCents": 500, "lines": [{ "lineId": "apt_abc123:add_on:1", "staffId": "stf_mia" }] }' ``` Example response: ``` { "ok": true, "replayed": false, "version": 1, "appointment": { "id": "apt_abc123", "ref": "MV-7QK2M9", "status": "completed", ... }, "lines": [ ...each line with the person it is now credited to... ], "depositPaidCents": 2000, "dueCents": 0, "checkout": { "allowed": false, "blocked": "already_checked_out" }, "sale": { "id": "sale_x1y2z3", "receipt": "X1Y2Z3", "at": "2026-06-10T22:12:00.000Z", "source": "moneris_mgr", "externalSaleId": "MGR-000123", "method": "Card", "tender": "card", "collectedCents": 3712, "saleTotalCents": 3712, "tipCents": 500, "products": [] } } // The same externalSaleId posted again: the same answer with "replayed": true, // and nothing written. A refusal is { ok: false, error, reason, ... }. ``` ### POST /api/v1/{slug}/appointments/{id}/deposit-request: Send the deposit pay link again Requires an API key. Needs the bookings:write scope. For a booking the business made (by phone or walk-in, or POST /appointments with requestDeposit) that is waiting on the deposit it asked the client for: send the client the pay link again. The Stripe Checkout before is closed first, so a client holding two links can never pay twice, and the new link is open for a day. Paying is marked by Stripe's webhook, exactly as an online deposit, and the deposit then comes off the bill at checkout. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool send_deposit_link. Parameters: - id (path, required): The booking waiting on its deposit. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no booking with that id in this business. - 409: The booking is not waiting on a deposit the business asked for (reason not_waiting), the client already paid it (paid), the client has no email (no_email), the business cannot take card payments now (unavailable), or the booking's client is not messaged (client_messages_off: no link is made, since it would only reach them as a message). - 502: Stripe or the email did not answer (reason stripe or not_sent). Try again in a moment. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/deposit-request \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "appointmentId": "apt_abc123", "sent": true, "amountCents": 2000, "emailedTo": "jane@example.com", "texted": false, "expiresAt": "2026-06-02T03:12:00.000Z" } ``` ### POST /api/v1/{slug}/appointments/{id}/deposit-request/cancel: Stop asking for the deposit Requires an API key. Needs the bookings:write scope. The client will pay in person after all: the pay link stops working and the booking no longer waits on a deposit, so it can be edited and checked out. Refused once the client has paid it. The booking itself is never cancelled. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool stop_deposit_request. Parameters: - id (path, required): The booking waiting on its deposit. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no booking with that id in this business. - 409: The client already paid it (reason paid), or the booking is not waiting on a deposit (not_waiting). - 502: Stripe did not answer, so the link is still open (reason stripe). Try again in a moment. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/deposit-request/cancel \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "appointmentId": "apt_abc123" } ``` ### GET /api/v1/{slug}/booking-requests: List booking requests waiting for an answer Requires an API key. Needs the bookings:read scope. At a business that approves online bookings before they are confirmed: the requests that can be answered now, oldest first. kind booking is a client's new booking, pending and holding its time; kind move is a client's move of a confirmed booking, which keeps its own time until the move is accepted (requestedStartAt, requestedStaffName). deadline is when it is declined for the business if nobody answers. A request whose deposit is still being paid is not listed until it is. A visit of several services is one request, under its first service. The client comes by id; customer (their name, email and phone) only for a key that also has customers:read. A request for a service that needs two or more kinds of resource at once also has resources: every room, chair or machine it holds, { id, name, kind }, its own room first, as on GET /appointments. Requires an API key with bookings:read. The same as the MCP tool list_booking_requests. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}. - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/booking-requests \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "requests": [ { "id": "apt_abc123", "ref": "MV-7QK2M9", "kind": "booking", "customerId": "cus_xyz", "serviceName": "Gel Manicure", "staffId": "stf_abc", "staffName": "Anna", "startAt": "2026-06-10T21:00:00.000Z", "durationMin": 60, "requestedStartAt": null, "requestedStaffName": null, "requestedAt": "2026-06-08T02:00:00.000Z", "deadline": "2026-06-10T02:00:00.000Z", "depositPaidCents": 0, "priceCents": 7500, "notes": null } ] } ``` ### POST /api/v1/{slug}/booking-requests/{id}/accept: Accept a booking request Requires an API key. Needs the bookings:write scope. The booking is confirmed, with everything a confirmed booking gets (the client's confirmation, the calendar entry), or the client's move is carried out after its time is checked again, exactly as Accept on the Requests list. A request is answered once: a second answer, from anyone, is 409. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool accept_booking_request. Parameters: - id (path, required): The request's id (from GET /booking-requests). Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no request with that id in this business. - 409: It has already been answered, its deposit is still being paid, its time has passed (it can only be declined), or the time a move asked for is no longer free. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/booking-requests/apt_abc123/accept \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "id": "apt_abc123", "kind": "booking", "status": "confirmed" } ``` ### POST /api/v1/{slug}/booking-requests/{id}/decline: Decline a booking request Requires an API key. Needs the bookings:write scope. A booking is cancelled as the business (any deposit refunded, the time freed for the waitlist); a move is dropped and the booking keeps its time. Either way the client is emailed, with the note when one is given. Answered once. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool decline_booking_request. Parameters: - id (path, required): The request's id (from GET /booking-requests). - reason (body, optional): A note for the client, up to 500 characters. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no request with that id in this business. - 409: It has already been answered, or its deposit is still being paid. - 422: reason is longer than 500 characters (fieldErrors). - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/booking-requests/apt_abc123/decline \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "reason": "We are closed that day, sorry." }' ``` Example response: ``` { "ok": true, "id": "apt_abc123", "kind": "booking", "status": "cancelled" } ``` ### GET /api/v1/{slug}/class-sessions: List class sessions Requires an API key. Needs the bookings:read scope. The business's class sessions, soonest first, with how full each is. By default the scheduled sessions still to start, up to 100. A business that does not run classes lists none. At a business with two or more branches, each session also has locationId: the branch it is held at (its own, else its class's, else the main branch); its start and end are on that branch's clock. Requires an API key with bookings:read. The same as the MCP tool list_class_sessions. Parameters: - from (query, optional): Start of the window: YYYY-MM-DD (the start of that day in the business's timezone) or ISO 8601. Defaults to now when to is not given. - to (query, optional): End of the window, exclusive: YYYY-MM-DD (the start of that day in the business's timezone) or ISO 8601. - serviceId (query, optional): One class (a group service of this business); another id is 404. - status (query, optional): scheduled (the default), cancelled or all. - limit (query, optional): 1 to 200, default 100. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or serviceId is not one of its classes. - 422: from, to, status or limit is malformed (fieldErrors). - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/class-sessions?from=2026-06-01&to=2026-07-01" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "sessions": [ { "id": "cls_abc123", "serviceId": "svc_yoga", "className": "Sunrise yoga", "staffId": "stf_abc", "resourceId": null, "startAt": "2026-06-10T18:00:00.000Z", "endAt": "2026-06-10T19:00:00.000Z", "capacity": 12, "enrolledCount": 9, "spotsLeft": 3, "priceCents": 2000, "status": "scheduled", "seriesId": null } ] } ``` ### GET /api/v1/{slug}/class-sessions/{id}/roster: Who holds a place on a class session Requires an API key. Needs the bookings:read scope. The session, and everyone holding a live place on it, in sign-up order: each place's enrolmentId, the client's id, its status (booked, attended, no_show) and how it was paid (payment: paid_online, checkout_open, pay_at_door, free, refunded or forfeited). A cancelled place is off the roster. The client comes by id; customer (name, email, phone) only for a key that also has customers:read. At a business with two or more branches, the session also has locationId, as GET /class-sessions lists it. Requires an API key with bookings:read. The same as the MCP tool get_class_roster. Parameters: - id (path, required): The session's id (from GET /class-sessions). Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no class session with that id in this business. - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/class-sessions/cls_abc123/roster \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "session": { "id": "cls_abc123", "serviceId": "svc_yoga", "className": "Sunrise yoga", "staffId": "stf_abc", "resourceId": null, "startAt": "2026-06-10T18:00:00.000Z", "endAt": "2026-06-10T19:00:00.000Z", "capacity": 12, "enrolledCount": 9, "spotsLeft": 3, "priceCents": 2000, "status": "scheduled", "seriesId": null }, "roster": [ { "enrolmentId": "enr_abc123", "customerId": "cus_xyz", "status": "booked", "payment": "paid_online", "depositStatus": "paid", "depositPaidCents": 2000, "priceCents": 2000, "source": "online", "createdAt": "2026-06-01T03:12:00.000Z" } ] } ``` ### POST /api/v1/{slug}/class-sessions/{id}/roster: Put a phone or walk-in client on a class session Requires an API key. Needs the bookings:write scope. Through the roster's own code, as Add on the session page: the client already on file is matched by email (then phone), or added; they are never opted in to marketing through the API (record their choice on their profile); nothing is taken, so the place is paid at the door; their ticket is emailed when they have an email and the session is still to come. A full session stays full: 409 with the spots left, and nothing is written. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool add_class_attendee. Parameters: - id (path, required): The session's id. - name (body, required): The client's name, 2 to 80 characters. - email (body, optional): Their email, for their ticket and to match them. - phone (body, optional): Their phone number, to match them. - source (body, optional): phone (the default) or walk_in. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 400: The request body is not valid JSON. - 404: No business exists for the {slug}, or no class session with that id in this business. - 409: The session is full or cancelled, or they already hold a place on it. Nothing was written. - 422: The details are malformed (fieldErrors names each: name, email, phone, source). - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/class-sessions/cls_abc123/roster \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Pat Visitor", "email": "pat@example.com", "source": "phone" }' ``` Example response: ``` { "ok": true, "sessionId": "cls_abc123", "enrolmentId": "enr_def456", "customerId": "cus_pat", "name": "Pat Visitor", "matched": false, "emailed": true } // matched is true when an existing client was found by email or phone (their // name on file is kept); emailed says whether their ticket went out. ``` ### POST /api/v1/{slug}/class-sessions/{id}/roster/{enrolmentId}/cancel: Cancel one person's place on a class session Requires an API key. Needs the bookings:write scope. Their spot is freed, what they paid comes back as account credit (creditedCents), and they are emailed, exactly as Remove on the roster and as cancelling the whole session does for each person. A place marked attended or a no-show is refused until the mark is undone. One audit row names the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool cancel_class_place. Parameters: - id (path, required): The session's id. - enrolmentId (path, required): The place (from the roster). Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, no class session with that id, or that place is not on this session. - 409: The place is marked attended or a no-show (undo the mark first), or was already taken off. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/class-sessions/cls_abc123/roster/enr_abc123/cancel \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "sessionId": "cls_abc123", "enrolmentId": "enr_abc123", "creditedCents": 2000 } ``` ### POST /api/v1/{slug}/class-sessions/{id}/roster/{enrolmentId}/attendance: Mark who came to a class session Requires an API key. Needs the bookings:write scope. attended is the very state the ticket scan at the door sets; no_show records that they did not come; booked undoes a mark. The headcount, what they paid and their client record are untouched. The same mark again changes nothing (changed: false). A change is one audit row naming the key. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool mark_class_attendance. Parameters: - id (path, required): The session's id. - enrolmentId (path, required): The place (from the roster). - mark (body, required): attended, no_show or booked. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 400: The request body is not valid JSON. - 404: No business exists for the {slug}, no class session with that id, or that place is not on this session. - 409: The place was cancelled, so it cannot be marked. - 422: mark is not attended, no_show or booked (fieldErrors). - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/class-sessions/cls_abc123/roster/enr_abc123/attendance \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "mark": "attended" }' ``` Example response: ``` { "ok": true, "sessionId": "cls_abc123", "enrolmentId": "enr_abc123", "status": "attended", "changed": true } ``` ### GET /api/v1/{slug}/reports/earnings: Staff earnings and commission Requires an API key. Needs the reports:read scope. What Reports > Staff earnings shows, as JSON: each person's completed visits and the products they sold, their commission under the business's rules on the day of each (tiered rules counted from the start of the pay period), refunds and voids taking commission back, and tips; in total, by period and line by line (up to 500 lines; linesTruncated says when there are more, and the totals always cover them all). Booth renters earn no commission and are listed apart (boothRenter), with employeeTotals and renterTotals beside the totals. Clients are never named. Reads only. Requires an API key with reports:read (the scope needs See analytics & earnings). The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_earnings. Parameters: - range (query, optional): this_week, last_week, this_month, last_month, 30d, 90d, year; custom with from and to. Defaults to this_month. Days are the business's own (its timezone). - from (query, optional): First day, YYYY-MM-DD, for range=custom. - to (query, optional): Last day, YYYY-MM-DD, for range=custom (included). - by (query, optional): day, week (from Monday) or month: the periods to total by. Defaults to week. - staff (query, optional): One person's id (GET /staff, or anyone ever on the team). Someone not on this business's team is 404. staffId is accepted as another name for staff, as MCP and the answer's query.staffId call it; when both are sent, staff is used. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the reports:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or staff is not one of its team. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports/earnings?range=last_month&by=week" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "query": { "range": "last_month", "from": "2026-05-01", "to": "2026-05-31", "groupBy": "week", "staffId": null, "label": "Last month" }, "currency": "CAD", "totals": { "visits": 41, "serviceSalesCents": 312000, "serviceCommissionCents": 124800, "productUnits": 9, "productSalesCents": 27000, "productCommissionCents": 2700, "refundsSalesCents": -4000, "refundsCommissionCents": -1600, "commissionCents": 125900, "tipsCents": 18500 }, "hasBoothRenters": false, "employeeTotals": { ... }, "renterTotals": { ... }, "hasRules": true, "people": [{ "staffId": "stf_abc", "name": "Anna", "boothRenter": false, "visits": 23, "commissionCents": 70100, ... }], "periods": [{ "key": "2026-04-27", "label": "27 Apr", "from": "2026-04-27", "to": "2026-05-03", "totals": { ... }, "people": [ ... ] }], "lines": [{ "id": "visit:apt_abc123", "source": "visit", "at": "2026-05-02T21:00:00.000Z", "staffId": "stf_abc", "appliesTo": "service", "label": "Cut + Head massage", "ref": "MV-7QK2M9", "receipt": "X1Y2Z3", "appointmentId": "apt_abc123", "saleId": "sale_x1y2z3", "category": "Hair", "units": 1, "salesCents": 5100, "commissionCents": 2040, "tipCents": 0, "ruleId": "crl_abc", "boothRenter": false }], "linesTruncated": false } ``` ### GET /api/v1/{slug}/reports/tips: Tips Requires an API key. Needs the reports:read scope. What Reports > Tips shows, as JSON: the tips taken at checkout by person and by period, each row of the record (who got what, by which rule, and any adjustment and its reason), and each tipped sale with how it is split now. config says whether the business takes tips and its rule. Up to 500 entries and sales (entriesTruncated). Reads only. Requires an API key with reports:read. The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_tips. Parameters: - range (query, optional): this_week, last_week, this_month, last_month, 30d, 90d, year; custom with from and to. Defaults to this_month. Days are the business's own (its timezone). - from (query, optional): First day, YYYY-MM-DD, for range=custom. - to (query, optional): Last day, YYYY-MM-DD, for range=custom (included). - by (query, optional): day, week (from Monday) or month: the periods to total by. Defaults to week. - staff (query, optional): One person's id. Someone not on this business's team is 404. staffId is accepted as another name for staff, as MCP and the answer's query.staffId call it; when both are sent, staff is used. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the reports:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or staff is not one of its team. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports/tips?range=this_month" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "query": { "range": "this_month", "from": "2026-06-01", "to": "2026-06-30", "groupBy": "week", "staffId": null, "label": "This month" }, "currency": "CAD", "config": { "enabled": true, "rule": "service_share", "presets": [1000, 1500, 2000] }, "totalCents": 18500, "people": [{ "staffId": "stf_abc", "name": "Anna", "tipsCents": 11000 }], "periods": [{ "key": "2026-06-01", "label": "1 Jun", "from": "2026-06-01", "to": "2026-06-07", "totalCents": 6000, "people": [ ... ] }], "entries": [{ "id": "tal_abc", "saleId": "sale_x1y2z3", "receipt": "X1Y2Z3", "staffId": "stf_abc", "name": "Anna", "amountCents": 500, "rule": "service_share", "adjustmentId": null, "reason": null, "at": "2026-06-02T22:12:00.000Z", "method": "Card", "bookingRef": "MV-7QK2M9", "appointmentId": "apt_abc123" }], "entriesTruncated": false, "sales": [{ "saleId": "sale_x1y2z3", "receipt": "X1Y2Z3", "at": "2026-06-02T22:12:00.000Z", "method": "Card", "tipCents": 500, "appointmentId": "apt_abc123", "bookingRef": "MV-7QK2M9", "current": [{ "staffId": "stf_abc", "name": "Anna", "amountCents": 500 }], "rule": "service_share", "adjusted": false }] } ``` ### GET /api/v1/{slug}/reports/deposits: Deposit reconciliation Requires an API key. Needs the reports:read scope. What Reports > Deposits shows, as JSON: each deposit taken (online when the client booked, by a pay link the business sent, or from account credit) and what became of it: taken off the bill at checkout (applied), kept for a no-show or late cancellation (kept), refunded to the card or as credit, still held for a visit to come (held), or still held on a booking that is over (unresolved, worth a look); with Stripe's own record beside each (stripeCheck) and in total. Every total balances because every row does. Refunded is read from the payments record. A refund that failed later is not counted as refunded: the money is back with the business. A cancelled or no-show booking whose deposit was refunded in part has depositStatus part_refunded: what went back is refundedCents and the rest is keptCents. A fee kept when some of a booking's people cancelled, or what a cancel of the whole booking kept, is in keptCents, not heldCents or appliedCents. A refund the business still has to send, or one not yet back from Stripe, is in unresolvedCents with a note until it lands, never in keptCents. Up to 500 rows (rowsTruncated). The client is not named. Reads only. Requires an API key with reports:read. The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_deposit_report. Parameters: - range (query, optional): 30d, 90d, month, last_month, year, all; custom with from and to. Defaults to 90d. Days are the business's own (its timezone). - from (query, optional): First day, YYYY-MM-DD, for range=custom. - to (query, optional): Last day, YYYY-MM-DD, for range=custom (included). - by (query, optional): day, week (from Monday) or month: the periods to total by. Defaults to month. - basis (query, optional): taken (the default: by the day the deposit was taken) or visit (by the visit's day). Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the reports:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports/deposits?range=month&basis=taken" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "query": { "range": "month", "basis": "taken", "groupBy": "month", "from": "2026-06-01", "to": "2026-06-30", "label": "This month" }, "currency": "CAD", "totals": { "bookings": 12, "takenCents": 24000, "takenOnlineCents": 20000, "takenPayLinkCents": 2000, "takenCreditCents": 2000, "appliedCents": 16000, "keptCents": 2000, "refundedCents": 2000, "heldCents": 4000, "unresolvedCents": 0, "refundUnconfirmedCents": 0 }, "periods": [{ "key": "2026-06", "label": "Jun 2026", "fromKey": "2026-06-01", "toKey": "2026-06-30", "bookings": 12, ... }], "rows": [{ "appointmentId": "apt_abc123", "ref": "MV-7QK2M9", "serviceName": "Cut", "staffName": "Anna", "visitAt": "2026-06-10T21:00:00.000Z", "status": "completed", "depositStatus": "paid", "method": "online", "takenCents": 2000, "takenAt": "2026-06-01T03:12:00.000Z", "bookedCents": 2000, "stripeCents": 2000, "stripeRefundCents": 0, "stripeCheck": "matches", "appliedCents": 2000, "appliedAt": "2026-06-10T22:12:00.000Z", "receipt": "X1Y2Z3", "keptCents": 0, "keptReason": null, "keptAt": null, "refundedCents": 0, "refundedAt": null, "refundedTo": null, "refundUnconfirmedCents": 0, "heldCents": 0, "unresolvedCents": 0, "notes": [] }], "rowsTruncated": false, "stripe": { "bookedCardCents": 22000, "stripeCardCents": 22000, "stripeRefundCents": 2000, "checks": { "matches": 11, "not_card": 1, "missing": 0, "unrecorded": 0, "more": 0, "less": 0 }, "byDate": { ... } } } ``` ### GET /api/v1/{slug}/audit-log: The audit log Requires an API key. Needs the audit:read scope, on a key made with it ticked. Who did what in the business, and when, newest first, as the Audit log page shows it: bookings, clients, money, loyalty and gift cards, classes, sign-ins, team access, keys, webhooks, settings and downloads. Each row names who acted (a team member with their email and role, an API key, a connected app, a client online, a client's AI assistant, or Bookatu itself), what was done to which record, a summary, what changed (notes, secrets and bank details by name only), and where it came from for a team member, key or app. The client a row is about is named by id (clientId). Filters and pages as the page takes them. Reading it writes nothing. Requires an API key made with the audit:read scope ticked, by someone the business lets manage it (owners and admins on the standard grid); it stops working if they lose that right or leave. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_audit_log. Parameters: - actor (query, optional): user:, api_key:, app:, client, system, assistant (every client's AI assistant) or one of them as assistant:ai:chatgpt. - action (query, optional): One action (booking.cancelled) or a whole area (booking.*). - target (query, optional): What it was done to: booking, client, invoice, api_key, settings, class, ... - targetId (query, optional): That record's id. - from (query, optional): First day, YYYY-MM-DD, in the business's timezone. - to (query, optional): Last day, YYYY-MM-DD, included. - page (query, optional): Page number, from 1. - pageSize (query, optional): Rows a page, 1 to 200 (default 50). hasMore says whether there is another page. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it does not carry the audit:read scope (the body names it as missingScope). Only a key made with audit:read ticked carries it: a key made before scopes never does, whatever its access level. - 404: No business exists for the {slug}. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/audit-log?action=booking.*&from=2026-06-01" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "events": [ { "id": "aud_abc123", "at": "2026-06-02T09:30:00.000Z", "action": "booking.cancelled", "actionLabel": "Booking cancelled", "actor": { "type": "user", "id": "usr_abc", "name": "Alex Owner", "email": "alex@example.com", "role": "owner", "roleLabel": "Owner" }, "target": { "type": "booking", "id": "apt_abc123" }, "clientId": "cus_xyz", "summary": "MV-7QK2M9 cancelled (Gel Manicure, Wed 10 Jun 2026, 9:00 am)", "changes": [{ "field": "status", "to": "cancelled" }], "ip": "203.0.113.7", "userAgent": "Mozilla/5.0 ..." } ], "page": 1, "pageSize": 50, "hasMore": false, "filters": { "action": "booking.*", "from": "2026-06-01" } } ``` ### POST /api/v1/{slug}/customers/{id}/tags: Tag a client Requires an API key. Needs the customers:write scope, on a key made with it ticked. Put one of the business's tags on a client, by the tag's id or its name. Changes nothing else about the client. Org-scoped: a client or a tag of another business is 404 and nothing is written. Answers the client's tags as they now stand. Needs the opt-in customers:write scope: only a key made with "Tag clients" ticked carries it, never a key made before scopes or a connected app. A read-only key is refused. Parameters: - id (path, required): The client's id (from GET /customers). - tagId (body, optional): The tag's id (from tags on GET /customers). Send this or name. - name (body, optional): An existing tag's name, whatever its case. Tags are made on the Tags page, never through the API. The tag must be for clients (or both). Errors: - 400: The body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, it does not carry customers:write (the body names it as missingScope; a key made before scopes never does), or it is read-only. - 404: No client with that id in this business, or no tag with that id or name (code TAG_NOT_FOUND). - 422: Neither tagId nor name was sent (code TAG_REQUIRED), or the tag is for bookings only (code TAG_WRONG_KIND). - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/customers/cus_xyz/tags \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "VIP" }' ``` Example response: ``` { "ok": true, "id": "cus_xyz", "changed": true, "tags": [{ "id": "tag_vip123", "name": "VIP", "color": "indigo" }] } // changed is false when nothing needed doing (the tag was already on, or already off). ``` ### DELETE /api/v1/{slug}/customers/{id}/tags/{tagId}: Untag a client Requires an API key. Needs the customers:write scope, on a key made with it ticked. Take a tag off a client. Already off answers changed: false. Org-scoped like the POST. Needs the opt-in customers:write scope, on a key made with it ticked. Parameters: - id (path, required): The client's id. - tagId (path, required): The tag's id. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, it does not carry customers:write (missingScope), or it is read-only. - 404: No client with that id in this business, or no tag with that id (code TAG_NOT_FOUND). - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X DELETE https://bookatu.com/api/v1/maison-vera/customers/cus_xyz/tags/tag_vip123 \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "id": "cus_xyz", "changed": true, "tags": [] } // changed is false when nothing needed doing (the tag was already on, or already off). ``` ### POST /api/v1/{slug}/appointments/{id}/tags: Tag a booking Requires an API key. Needs the bookings:write scope. Put one of the business's tags on a booking, by the tag's id or its name. Changes nothing else about the booking and sends no email or webhook. Org-scoped: a booking or a tag of another business is 404 and nothing is written. Answers the booking's tags as they now stand. Needs bookings:write; a read-only key is refused. Parameters: - id (path, required): The appointment id (from GET /appointments). - tagId (body, optional): The tag's id (from tags on GET /appointments). Send this or name. - name (body, optional): An existing tag's name, whatever its case. Tags are made on the Tags page, never through the API. The tag must be for bookings (or both). Errors: - 400: The body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, it lacks bookings:write (the body names it as missingScope), or it is read-only. - 404: No booking with that id in this business, or no tag with that id or name (code TAG_NOT_FOUND). - 422: Neither tagId nor name was sent (code TAG_REQUIRED), or the tag is for clients only (code TAG_WRONG_KIND). - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/tags \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "tagId": "tag_bridal456" }' ``` Example response: ``` { "ok": true, "id": "apt_abc123", "changed": true, "tags": [{ "id": "tag_bridal456", "name": "Bridal", "color": "rose" }] } // changed is false when nothing needed doing (the tag was already on, or already off). ``` ### DELETE /api/v1/{slug}/appointments/{id}/tags/{tagId}: Untag a booking Requires an API key. Needs the bookings:write scope. Take a tag off a booking. Already off answers changed: false. Org-scoped like the POST. Needs bookings:write. Parameters: - id (path, required): The appointment id. - tagId (path, required): The tag's id. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, it lacks bookings:write (missingScope), or it is read-only. - 404: No booking with that id in this business, or no tag with that id (code TAG_NOT_FOUND). - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X DELETE https://bookatu.com/api/v1/maison-vera/appointments/apt_abc123/tags/tag_bridal456 \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "ok": true, "id": "apt_abc123", "changed": true, "tags": [] } // changed is false when nothing needed doing (the tag was already on, or already off). ``` ### GET /api/v1/{slug}/sandbox/outbox: The test outbox (sandbox only) Requires an API key. Needs the customers:read scope. Test mode: what a sandbox business would have sent, newest first. Every email, text, WhatsApp message (and voice or push message) a sandbox sends, to clients or to its own team, is kept here and never sent: booking confirmations, reminders, receipts, staff alerts, inbox replies, scheduled reports. The newest 500 are kept. Filter by channel and by time, and page with limit and nextCursor. The answer says livemode false. Only for a sandbox (a live business answers 404 NOT_A_SANDBOX), with the sandbox's TEST key (bk_test_): a live key is refused with 403 LIVEMODE_MISMATCH. Requires an API key with customers:read (the messages carry client addresses). 30 calls a minute per sandbox, all its test keys together. Over MCP, the sandbox_outbox tool reads the same, within the same limits. Parameters: - channel (query, optional): email, sms, whatsapp, voice or push. - since (query, optional): Only messages kept at or after this ISO 8601 time. - limit (query, optional): Messages a page, 1 to 100 (default 50). - cursor (query, optional): The nextCursor of the page before, for the next (older) page. Errors: - 401: The API key is missing or invalid. - 403: LIVEMODE_MISMATCH: a live key (bk_live_) sent to a sandbox, or a test key sent to a live business (the body says keyLivemode and businessLivemode). Otherwise: the key belongs to a different business ("Forbidden"), or it lacks the customers:read scope (the body names it as missingScope). - 404: NOT_A_SANDBOX: the {slug} is a live business, which has no test outbox, no test payments and nothing to simulate. Or no business exists for the {slug}. - 422: A filter is not valid: channel not one of the five, since not a time, or limit outside 1 to 100 (fieldErrors names each). - 429: More than 30 calls a minute to this sandbox, all its test keys together (Retry-After says when to try again). - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/your-test-salon/sandbox/outbox?channel=email&limit=20" \ -H "Authorization: Bearer bk_test_YOUR_KEY" ``` Example response: ``` { "messages": [ { "id": "sbo_8xKq2...", "channel": "email", "kind": "booking_confirmation", "to": "pat.example@example.com", "subject": "You're booked in at Test Salon", "text": null, "html": "...", "appointmentId": "apt_abc123", "customerId": "cus_xyz", "createdAt": "2026-10-30T09:15:00.000Z", "meta": { "dedupeKey": "booking_confirmation:apt_abc123" } }, { "id": "sbo_3Lm9...", "channel": "sms", "kind": "reminder_24h", "to": "+15555550123", "subject": null, "text": "Test Salon: reminder of your Cut tomorrow at 10:00 am.", "html": null, "appointmentId": "apt_abc123", "customerId": "cus_xyz", "createdAt": "2026-10-30T09:14:00.000Z", "meta": {} } ], "nextCursor": "MjAyNi0xMC0zMFQwOToxNDowMC4wMDBafHNib18zTG05", "livemode": false } ``` ### POST /api/v1/{slug}/sandbox/simulate/{event}: Simulate an event (sandbox only) Requires an API key. Needs the bookings:write scope. Test mode: make something happen to one of a sandbox's bookings, through the same code a real payment, cancellation or clock would run. {event} is one of: deposit.paid, payment.failed, checkout.expired, booking.client_cancelled, booking.no_show, reminders.due. deposit.paid: Pays the booking's open test checkout, as the test checkout page's "Pay (test)" does: checkout.session.completed runs through the Stripe webhook's own handler, the booking is confirmed with its deposit paid, the confirmation goes to the outbox and booking webhooks are sent. payment.failed: Declines the test card on the booking's open checkout, as "Decline (test)": the checkout stays open (as on Stripe's page) and nothing else changes; the answer says so (result.declined true, result.changed false). checkout.expired: Abandons the booking's open checkout, as "Abandon": checkout.session.expired runs, and an online booking held for its deposit is let go (cancelled as deposit_abandoned) and its time offered to the waitlist. booking.client_cancelled: The client's own cancellation (the manage page's), with the business's cancellation window, deposit rule, late-cancellation fee, emails and the booking.cancelled webhook. booking.no_show: Marks the booking a no-show. A no-show fee the cancellation policy sets is queued for the owner, as at a live business (result.fee): nothing charges it but the owner's Charge on the test business's No-show fees screen, which charges the client's saved TEST card: paid for a card saved with "Save test card", declined (card_declined) for one saved with "Save a card that will decline". reminders.due: Time passing: the booking's reminder email and reminder texts are sent as if now were its start minus each lead the business set (reminderHoursBefore, and its own text times). A booking reminded already is not reminded again. The answer gives the booking as it is now, the ids of the outbox messages the event kept (outbox), the webhook events it sent (webhooks) and what the event itself reported (result). Messages sent after the answer (a webhook retry, an email the system sends a moment later) still appear in GET /sandbox/outbox. Only for a sandbox (a live business answers 404 NOT_A_SANDBOX) and only for a booking of that sandbox (any other id is 404 APPOINTMENT_NOT_FOUND), with its TEST key (bk_test_): a live key is refused with 403 LIVEMODE_MISMATCH. Requires an API key with bookings:write. 10 calls a minute and 500 a day per sandbox, all its test keys together. Over MCP, the sandbox_simulate tool takes the same events, within the same limits. Parameters: - event (path, required): deposit.paid, payment.failed, checkout.expired, booking.client_cancelled, booking.no_show, reminders.due. - appointmentId (body, required): The id of a booking of this sandbox. Errors: - 400: UNKNOWN_SIMULATION: {event} is not one of the six (the body lists them as events). Or the body is not JSON. - 401: The API key is missing or invalid. - 403: LIVEMODE_MISMATCH: a live key (bk_live_) sent to a sandbox, or a test key sent to a live business (the body says keyLivemode and businessLivemode). Otherwise: the key belongs to a different business ("Forbidden"), or it lacks the bookings:write scope (the body names it as missingScope). - 404: NOT_A_SANDBOX: the {slug} is a live business, which has no test outbox, no test payments and nothing to simulate. Or no business exists for the {slug}. - 404: APPOINTMENT_NOT_FOUND: this sandbox has no booking with that appointmentId (a live business's booking is never found here). - 409: NO_OPEN_CHECKOUT: deposit.paid, payment.failed or checkout.expired on a booking with no open test checkout (it takes no deposit online, or its checkout is already paid or expired). SIMULATION_REFUSED: the client's cancellation is not allowed (the business's own rules: too late, a closed booking...), with the refusal. STRIPE_TEST_MODE: the payment is in Stripe test mode, which the simulator cannot pay, decline or abandon: deposit.paid, payment.failed or checkout.expired on a booking whose checkout is in Stripe test mode, or deposit.paid or payment.failed on a booking that still owes its deposit online and has no open test checkout while the sandbox's new payments go through Stripe test mode (pay on Stripe's checkout page with a test card instead). - 422: appointmentId is missing (fieldErrors). - 429: More than 10 calls a minute, or 500 a day, to this sandbox, all its test keys together (Retry-After says when to try again). - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST "https://bookatu.com/api/v1/your-test-salon/sandbox/simulate/deposit.paid" \ -H "Authorization: Bearer bk_test_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "appointmentId": "apt_abc123" }' ``` Example response: ``` { "ok": true, "event": "deposit.paid", "appointment": { "id": "apt_abc123", "status": "confirmed", "depositStatus": "paid", "depositCents": 2000, "depositPaidCents": 2000, "startAt": "2026-11-04T21:00:00.000Z", "endAt": "2026-11-04T21:30:00.000Z", "customerId": "cus_xyz", "checkoutSessionId": "cs_test_sbx_9Fh2..." }, "outbox": ["sbo_8xKq2...", "sbo_Qw71..."], "webhooks": ["booking.confirmed"], "result": { "checkoutSessionId": "cs_test_sbx_9Fh2..." }, "livemode": false } ``` ### GET /api/v1/{slug}/sandbox/payments: The test payments (sandbox only) Requires an API key. Needs the reports:read scope. Test mode: every payment a sandbox business made in test mode, newest first, as its admin's Test payments page lists them. No card was charged and no money moved: the payment simulator made each one, through the same code a real payment runs. kind is one of: checkout, a test checkout (a deposit, a class place, the shop, a gift card, a package, a print, gallery extras or an invoice): paid, declined (the test card was declined and it is still open), abandoned (it expired) or open; payment, the payment a paid checkout made: paid, refunded or partly_refunded; card_hold, a card saved for later at the card step: card_saved, or open while it waits for the card; no_show_charge, a no-show or late-cancellation fee charged to a saved test card: paid, declined, refunded or partly_refunded; refund, a refund of a test payment: refunded. Each has its outcome, amountCents (whole cents of its currency; null for a card hold, which takes no money), refundedCents, currency, description (the checkout's own line items), the booking it belongs to (appointmentId) and the booking or sale it belongs to (belongsTo: booking, class_place, order, gift_card, package, invoice or gallery_photos, with its id when there is one), the checkout and payment it came through, and when it was made. Nothing in it names a client: no name, email or phone. Filter by kind and by time, and page with limit and nextCursor. The answer says livemode false, and paymentsMode: simulated, or stripe_test while the sandbox's new payments go through Stripe test mode (those are listed in its Finance, not here). Only for a sandbox (a live business answers 404 NOT_A_SANDBOX), with the sandbox's TEST key (bk_test_): a live key is refused with 403 LIVEMODE_MISMATCH. Requires an API key with reports:read (the payments are the business's money, as the money reports are). 30 calls a minute per sandbox, all its test keys together. Over MCP, the sandbox_payments tool reads the same, within the same limits. Parameters: - kind (query, optional): checkout, payment, card_hold, no_show_charge, refund. - since (query, optional): Only payments made at or after this ISO 8601 time. - limit (query, optional): Payments a page, 1 to 100 (default 50). - cursor (query, optional): The nextCursor of the page before, for the next (older) page. Errors: - 401: The API key is missing or invalid. - 403: LIVEMODE_MISMATCH: a live key (bk_live_) sent to a sandbox, or a test key sent to a live business (the body says keyLivemode and businessLivemode). Otherwise: the key belongs to a different business ("Forbidden"), or it lacks the reports:read scope (the body names it as missingScope). - 404: NOT_A_SANDBOX: the {slug} is a live business, which has no test outbox, no test payments and nothing to simulate. Or no business exists for the {slug}. - 422: A filter is not valid: kind not one of the five, since not a time, or limit outside 1 to 100 (fieldErrors names each). - 429: More than 30 calls a minute to this sandbox, all its test keys together (Retry-After says when to try again). - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/your-test-salon/sandbox/payments?kind=checkout&limit=20" \ -H "Authorization: Bearer bk_test_YOUR_KEY" ``` Example response: ``` { "payments": [ { "id": "cs_test_sbx_9Fh2...", "kind": "checkout", "outcome": "paid", "amountCents": 2000, "refundedCents": 0, "currency": "NZD", "description": "Deposit · Cut", "appointmentId": "apt_abc123", "belongsTo": { "type": "booking", "id": "apt_abc123" }, "checkoutSessionId": "cs_test_sbx_9Fh2...", "paymentIntentId": "pi_test_sbx_4Kd8...", "createdAt": "2026-10-30T09:15:00.000Z", "updatedAt": "2026-10-30T09:16:10.000Z" }, { "id": "re_test_sbx_7Qp1...", "kind": "refund", "outcome": "refunded", "amountCents": 2000, "refundedCents": 0, "currency": "NZD", "description": "Refund: Deposit · Colour", "appointmentId": "apt_def456", "belongsTo": { "type": "booking", "id": "apt_def456" }, "checkoutSessionId": "cs_test_sbx_2Lm7...", "paymentIntentId": "pi_test_sbx_8Hs3...", "createdAt": "2026-10-30T09:12:00.000Z", "updatedAt": "2026-10-30T09:12:00.000Z" } ], "nextCursor": "MjAyNi0xMC0zMFQwOToxMjowMC4wMDBafHJlX3Rlc3Rfc2J4Xzd", "paymentsMode": "simulated", "livemode": false } ``` ### POST /api/v1/{slug}/appointments/{id}/reschedule: Move a booking Requires an API key. Needs the bookings:write scope. Move a booking to a new time, and optionally to a different team member. The new time is re-checked exactly as a client's own reschedule is, so a time that is not free is refused rather than double-booked. The time is startAt with its offset, or localTime ("2026-11-04T09:00") on the business's clock or a named timeZone; a time with no offset is refused with TIME_NEEDS_OFFSET, one the clocks skip with TIME_DOES_NOT_EXIST (and nextValid), one they show twice with TIME_AMBIGUOUS (and both candidates). The answer's when is the booked start as a When, on the business's clock and, when their zone is known, the client's. Requires a read-write key. Needs the bookings:write scope. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is not found. Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool reschedule_booking. Parameters: - id (path, required): The booking to move (from list_appointments). - startAt (body, optional): New start: an instant with its offset (RFC 3339, e.g. 2026-08-14T02:30:00Z). A time with no offset is refused (TIME_NEEDS_OFFSET). Send startAt or localTime, not both. - staffId (body, optional): Optional. Move it to this team member (from list_staff). Omit to keep whoever it is with. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset, "2026-11-04T09:00", read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is refused with TIME_DOES_NOT_EXIST and nextValid; one they show twice with TIME_AMBIGUOUS and both candidates, so resend startAt with the offset meant. - timeZone (body, optional): Optional, with localTime only. The IANA zone of a place the localTime is on, such as America/Toronto. Abbreviations (EST), offsets (+13:00) and Etc/ zones are refused with UNKNOWN_TIME_ZONE. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the bookings:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/appointments/abc123/reschedule" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool reschedule_booking", "livemode": true } ``` ### GET /api/v1/{slug}/products: List products Requires an API key. Needs the catalog:read scope. List every retail product in the catalog, active and inactive. Needs the catalog:read scope. Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool list_products. Parameters: - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/products" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "products": [ ... ], "nextCursor": null, "livemode": true } ``` ### POST /api/v1/{slug}/products: Add a product Requires an API key. Needs the catalog:write scope. Add a retail product (prices in dollars; optional tracked stock with an opening-stock ledger entry). Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_product. Parameters: - name (body, required): Product name (2-120 characters). - priceDollars (body, required): Retail price in dollars (0-100000). - description (body, optional): Optional description (max 2000 characters). - category (body, optional): Optional category. Defaults to 'Retail'. - compareAtDollars (body, optional): Optional 'was' price in dollars for a strike-through. 0 = none. - costDollars (body, optional): Optional wholesale unit cost in dollars (what the business pays). - sku (body, optional): Optional stock-keeping unit (max 80 characters). - barcode (body, optional): Optional barcode (EAN/UPC). Must be unique within the business. - brand (body, optional): Optional brand name (max 80 characters). - stock (body, optional): Optional initial on-hand quantity (whole number). Omit for an untracked product. - lowStockAt (body, optional): Optional reorder point: flag low stock at or below this quantity. - purchasable (body, optional): Optional. Show a Buy-now button on the public site. - shippable (body, optional): Optional. Collect a shipping address at checkout. - featured (body, optional): Optional. Feature this product. - active (body, optional): Optional. Whether the product is live. Defaults to true. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/products" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"name":"...","priceDollars":1}' ``` Example response: ``` { "...": "the same answer as the MCP tool create_product", "livemode": true } ``` ### PATCH /api/v1/{slug}/products/{id}: Update a product Requires an API key. Needs the catalog:write scope. Update only the provided fields of a product; a stock change records a ledger adjustment. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool update_product. Parameters: - id (path, required): Product id from list_products. - name (body, optional): New name (2-120 characters). - priceDollars (body, optional): New retail price in dollars. - description (body, optional): New description (max 2000 characters). - category (body, optional): New category. - compareAtDollars (body, optional): New 'was' price in dollars. 0 = none. - costDollars (body, optional): New wholesale unit cost in dollars. - sku (body, optional): New SKU. - barcode (body, optional): New barcode. Must be unique within the business. - brand (body, optional): New brand. - stock (body, optional): New on-hand quantity (whole number). - lowStockAt (body, optional): New reorder point. - purchasable (body, optional): Show a Buy-now button on the public site. - shippable (body, optional): Collect a shipping address at checkout. - featured (body, optional): Feature this product. - active (body, optional): Whether the product is live. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/products/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool update_product", "livemode": true } ``` ### POST /api/v1/{slug}/products/{id}/receive: Receive stock Requires an API key. Needs the catalog:write scope. Record a delivery into a stock-tracked product and log the restock movement. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool receive_stock. Parameters: - id (path, required): Product id from list_products (must track stock). - quantity (body, required): Units received (whole number, 1 or more). - unitCostDollars (body, optional): Optional unit cost in dollars for this delivery, stored on the movement. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/products/abc123/receive" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"quantity":1}' ``` Example response: ``` { "...": "the same answer as the MCP tool receive_stock", "livemode": true } ``` ### POST /api/v1/{slug}/services: Add a service Requires an API key. Needs the catalog:write scope. Add a standard bookable service (duration in minutes, prices in dollars), with how clients meet you for it (meetingType) and its own notice to cancel or change (noticeHours) when you send them. A new service is never a trip, so a destination or an itinerary is refused. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_service. Parameters: - name (body, required): Service name (2-120 characters). - durationMin (body, required): Duration in minutes (5-600). - priceDollars (body, required): Price in dollars (0-100000). - description (body, optional): Optional description (max 2000 characters). - category (body, optional): Optional category. Defaults to 'General'. - depositDollars (body, optional): Optional booking deposit in dollars. 0 = no deposit. - bookableOnline (body, optional): Optional. Whether customers can book it online. Defaults to true. - active (body, optional): Optional. Whether the service is live. Defaults to true. - meetingType (body, optional): Optional. How clients meet you for this service: place (at your place), venue (an address set on each booking), client (at the client's place), online (a call link), trip (a trip and its itinerary) or none (no meeting, the work is delivered). null works it out from the service: a trip, a video service, else your address. online also gives its bookings a Google Meet link when the business has Google connected and video meetings on, and any other type stops it; null leaves that as it is. - noticeHours (body, optional): Optional. The notice a client gives to cancel or change a booking of this service for free, in whole hours (0 to 8760, a year; 720 is 30 days). null uses the business's free cancellation window. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/services" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"name":"...","durationMin":1,"priceDollars":1}' ``` Example response: ``` { "...": "the same answer as the MCP tool create_service", "livemode": true } ``` ### PATCH /api/v1/{slug}/services/{id}: Update a service Requires an API key. Needs the catalog:write scope. Update only the provided fields of a service; null clears meetingType, noticeHours, destination or itinerary. A destination and an itinerary are only for a trip (a service that lasts whole days), never more days than it lasts. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool update_service. Parameters: - id (path, required): Service id from list_services. - name (body, optional): New name (2-120 characters). - durationMin (body, optional): New duration in minutes (5-600). - priceDollars (body, optional): New price in dollars. - description (body, optional): New description (max 2000 characters). - category (body, optional): New category. - depositDollars (body, optional): New booking deposit in dollars. - bookableOnline (body, optional): Whether customers can book it online. - active (body, optional): Whether the service is live. - meetingType (body, optional): Optional. How clients meet you for this service: place (at your place), venue (an address set on each booking), client (at the client's place), online (a call link), trip (a trip and its itinerary) or none (no meeting, the work is delivered). null works it out from the service: a trip, a video service, else your address. online also gives its bookings a Google Meet link when the business has Google connected and video meetings on, and any other type stops it; null leaves that as it is. - noticeHours (body, optional): Optional. The notice a client gives to cancel or change a booking of this service for free, in whole hours (0 to 8760, a year; 720 is 30 days). null uses the business's free cancellation window. - destination (body, optional): Optional, for a trip only (a service that lasts whole days). The trip's destination, one line of up to 120 characters. null or "" clears it. - itinerary (body, optional): Optional, for a trip only (a service that lasts whole days). The trip's days in order, each a title and an optional note, no more days than the trip lasts. null or [] clears it. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/services/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool update_service", "livemode": true } ``` ### GET /api/v1/{slug}/blog-posts: List blog posts Requires an API key. Needs the content:read scope. List the business's blog posts (drafts and published), newest first: lean rows without bodies; optional status filter. Needs the content:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool blog_list_posts. Parameters: - status (query, optional): Optional filter: all, draft or published. Defaults to all. - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/blog-posts" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "posts": [ ... ], "nextCursor": null, "livemode": true } ``` ### GET /api/v1/{slug}/blog-posts/{id}: Read a blog post Requires an API key. Needs the content:read scope. Get one blog post in full, markdown body included, by id or slug (drafts visible to the owner). Needs the content:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool blog_get_post. Parameters: - id (path, required): Post id from blog_list_posts. - slug (query, optional): The post's slug (unique within this business). Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/blog-posts/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool blog_get_post", "livemode": true } ``` ### POST /api/v1/{slug}/blog-posts: Write a blog post Requires an API key. Needs the content:write scope. Write a blog post (markdown body; slug auto-derived and unique per business). Saves a draft unless publish is true. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool blog_create_post. Parameters: - title (body, required): Post title (2-140 characters). - body (body, required): Post body as markdown (max 50000 characters). - excerpt (body, optional): Optional short summary shown on the blog index and in previews (max 300 characters). - coverImageUrl (body, optional): Optional cover image URL. Must be http(s). - publish (body, optional): Optional. true publishes immediately; omit or false to save a draft. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/blog-posts" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"title":"...","body":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool blog_create_post", "livemode": true } ``` ### PATCH /api/v1/{slug}/blog-posts/{id}: Update a blog post Requires an API key. Needs the content:write scope. Update only the provided fields of a post (the slug never changes) and optionally flip its status via an explicit draft/published field. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool blog_update_post. Parameters: - id (path, required): Post id from blog_list_posts. - title (body, optional): New title (2-140 characters). The slug does not change. - body (body, optional): New markdown body (max 50000 characters). - excerpt (body, optional): New excerpt (max 300 characters). Empty string clears it. - coverImageUrl (body, optional): New cover image URL (http(s) only). Empty string removes the cover. - status (body, optional): Optional explicit status: draft or published. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/blog-posts/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool blog_update_post", "livemode": true } ``` ### POST /api/v1/{slug}/blog-posts/{id}/publish: Publish a blog post Requires an API key. Needs the content:write scope. Publish a draft post; the first publish stamps publishedAt and a re-publish keeps the original date. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool blog_publish_post. Parameters: - id (path, required): Post id from blog_list_posts. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/blog-posts/abc123/publish" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool blog_publish_post", "livemode": true } ``` ### POST /api/v1/{slug}/blog-posts/{id}/unpublish: Unpublish a blog post Requires an API key. Needs the content:write scope. Take a post off the public blog (back to draft), keeping its content and original publish date. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool blog_unpublish_post. Parameters: - id (path, required): Post id from blog_list_posts. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/blog-posts/abc123/unpublish" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool blog_unpublish_post", "livemode": true } ``` ### GET /api/v1/{slug}/forms: List forms Requires an API key. Needs the content:read scope. List the business's intake / consent forms: lean rows with field, attachment and response counts, never full field schemas; optional active/inactive filter. Needs the content:read scope. Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool forms_list. Parameters: - status (query, optional): Optional filter: all, active or inactive. Defaults to all. - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/forms" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "forms": [ ... ], "nextCursor": null, "livemode": true } ``` ### GET /api/v1/{slug}/forms/{id}: Read a form Requires an API key. Needs the content:read scope. Get one form in full, including its complete field schema and the services it is required before. Needs the content:read scope. The same as the MCP tool forms_get. Parameters: - id (path, required): Form id from forms_list. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/forms/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool forms_get", "livemode": true } ``` ### POST /api/v1/{slug}/forms: Create a form Requires an API key. Needs the content:write scope. Create an intake / consent form from a hard-validated field schema (the real builder field types; choice fields need 2+ options; bad fields are rejected, never silently dropped). Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool forms_create. Parameters: - name (body, required): Form name (1-160 characters). - description (body, optional): Optional description (max 2000 characters). - fields (body, required): The form's fields in display order (1-24 items). See the tool description for the exact shape. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/forms" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"name":"...","fields":[]}' ``` Example response: ``` { "...": "the same answer as the MCP tool forms_create", "livemode": true } ``` ### PATCH /api/v1/{slug}/forms/{id}: Update a form Requires an API key. Needs the content:write scope. Update only the provided parts of a form (a fields array replaces the stored one; active shows/hides it). Service attachment changes go through the attach/detach tools. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool forms_update. Parameters: - id (path, required): Form id from forms_list. - name (body, optional): New name (1-160 characters). - description (body, optional): New description (max 2000 characters). Empty string clears it. - fields (body, optional): Replacement field array (same shape and validation as forms_create). - active (body, optional): Whether the form is live. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/forms/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool forms_update", "livemode": true } ``` ### POST /api/v1/{slug}/forms/{id}/services: Require a form for a service Requires an API key. Needs the content:write scope. Require a form before a service (clients complete it when booking). Both ids must belong to the business; idempotent. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool forms_attach_to_service. Parameters: - id (path, required): Form id from forms_list. - serviceId (body, required): Service id from list_services. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/forms/abc123/services" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"serviceId":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool forms_attach_to_service", "livemode": true } ``` ### DELETE /api/v1/{slug}/forms/{id}/services/{serviceId}: Stop requiring a form for a service Requires an API key. Needs the content:write scope. Stop requiring a form before a service. Removes the requirement only; the form and responses stay. Idempotent. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool forms_detach_from_service. Parameters: - id (path, required): Form id from forms_list. - serviceId (path, required): Service id from list_services. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X DELETE "https://bookatu.com/api/v1/maison-vera/forms/abc123/services/serviceId_abc" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool forms_detach_from_service", "livemode": true } ``` ### GET /api/v1/{slug}/forms/{id}/responses: List form responses Requires an API key. Needs the customers:read scope. Summary rows for one form's responses: response id, customer display name and submission time only. Clients' actual answers never leave the admin dashboard (privacy posture). Needs the customers:read scope. The person who made the key must still have "Export data" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool forms_list_responses. Parameters: - id (path, required): Form id from forms_list. - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the customers:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/forms/abc123/responses" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "responses": [ ... ], "nextCursor": null, "livemode": true } ``` ### GET /api/v1/{slug}/campaigns: List email campaigns Requires an API key. Needs the content:read scope. List email campaigns (drafts through sent): lean rows with status, audience segment and counts, never bodies. Needs the content:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool campaigns_list. Parameters: - status (query, optional): Optional filter: all, draft, scheduled, sending or sent. Defaults to all. - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/campaigns" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "campaigns": [ ... ], "nextCursor": null, "livemode": true } ``` ### GET /api/v1/{slug}/campaigns/{id}: Read an email campaign Requires an API key. Needs the content:read scope. Get one campaign in full, body markup included. Audiences are segment names; recipient email addresses are never returned. Needs the content:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool campaigns_get. Parameters: - id (path, required): Campaign id from campaigns_list. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/campaigns/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool campaigns_get", "livemode": true } ``` ### POST /api/v1/{slug}/campaigns: Draft an email campaign Requires an API key. Needs the content:write scope. Draft an email campaign (subject, composer-markup body, audience segment). Saved as a draft and nothing more: there is no send or schedule tool. Sending stays an owner action in the dashboard. Requires a read-write key. Needs the content:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool campaigns_create_draft. Parameters: - subject (body, required): Email subject line (2-200 characters). - body (body, required): Body in the composer's markup (max 50000 characters). - audience (body, optional): Optional audience segment: all, recent, lapsed or vip. Defaults to all. - imageUrl (body, optional): Optional header image URL. Must be http(s). - accentColor (body, optional): Optional #rrggbb accent for the header and button. Omit for the brand color. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the content:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/campaigns" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"subject":"...","body":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool campaigns_create_draft", "livemode": true } ``` ### GET /api/v1/{slug}/reports: Business report Requires an API key. Needs the reports:read scope. Business performance for a period vs the period before: revenue, bookings, chair time used, revenue per open hour, rebook and no-show rates, with service/staff/category/channel breakdowns. Read-only. Needs the reports:read scope. The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_report. Parameters: - range (query, optional): Window to report on. Defaults to 30d. - staff (query, optional): Staff ids to limit to. Omit for everyone. - categories (query, optional): Service categories to limit to. - channels (query, optional): Booking sources to limit to, e.g. online, walk_in, admin. - clientType (query, optional): Limit to clients first seen inside the window, or to established ones. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the reports:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_report", "livemode": true } ``` ### GET /api/v1/{slug}/reports/findings: Findings from the numbers Requires an API key. Needs the reports:read scope. Ranked, data-computed findings about the business (severity, headline, detail, suggested action): what the numbers mean, not prose. Read-only. Needs the reports:read scope. The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_findings. Parameters: - range (query, optional): Window to assess. Defaults to 30d. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the reports:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports/findings" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_findings", "livemode": true } ``` ### GET /api/v1/{slug}/reports/capacity: Chair time by hour Requires an API key. Needs the reports:read scope. Chair time by day of week and hour in the business's own timezone: where the week is full and where it is empty. Read-only. Needs the reports:read scope. The person who made the key must still have "See analytics & earnings" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_capacity. Parameters: - range (query, optional): Window to measure. Defaults to 30d. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the reports:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/reports/capacity" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_capacity", "livemode": true } ``` ### GET /api/v1/{slug}/webhooks: List webhooks Requires an API key. Needs the webhooks:read scope. List the business's webhook endpoints: url, subscribed events, active flag and last delivery status. Signing secrets are never returned. Needs the webhooks:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool webhooks_list. Parameters: - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the webhooks:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/webhooks" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "webhooks": [ ... ], "nextCursor": null, "livemode": true } ``` ### POST /api/v1/{slug}/webhooks: Add a webhook Requires an API key. Needs the webhooks:write scope. Register a public https endpoint to receive signed event POSTs; returns the HMAC signing secret once. Unknown event names are rejected. Requires a read-write key. Needs the webhooks:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool webhooks_create. Parameters: - url (body, required): Public https URL to receive event POSTs, e.g. https://your-agent.example.com/hooks/bookatu. - events (body, optional): Optional event names to subscribe to (unknown names are rejected). Omit for all events. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the webhooks:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/webhooks" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"url":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool webhooks_create", "livemode": true } ``` ### POST /api/v1/{slug}/webhooks/{id}/disable: Switch off a webhook Requires an API key. Needs the webhooks:write scope. Switch an endpoint off: deliveries stop, the endpoint and its history are kept. No delete tool exists; resuming or removing is an owner action in the dashboard. Requires a read-write key. Needs the webhooks:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool webhooks_disable. Parameters: - id (path, required): Webhook id from webhooks_list. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the webhooks:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/webhooks/abc123/disable" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool webhooks_disable", "livemode": true } ``` ### GET /api/v1/{slug}/whoami: Who am I working for Requires an API key. The business, the person the credential is held to and their role, its scopes, livemode, and what never goes through an AI. On a key or connected app Bookatu support set up for the business, person has no id and no email, its name says it is Bookatu's platform owner, role is the role it acts with (owner, or the maker's own role once they join the team), and credential.onBehalfOf names the business. Any key of the business, no scope. Any API key of this business may call it: it needs no scope. The same as the MCP tool whoami. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/whoami" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool whoami", "livemode": true } ``` ### GET /api/v1/{slug}/search: Search the business Requires an API key. One search across clients, bookings, services, products, the team, the dashboard's pages and the help centre, each kind held to the credential's own scopes; results link into the dashboard. Any key of the business. Any API key of this business may call it: it needs no scope. The same as the MCP tool search. Parameters: - query (query, required): What to look for: a name, an email, a phone number, a service or product name, or words for a screen. 2 to 100 characters. - kinds (query, optional): Optional. Only these kinds. Omit for every kind this connection may read. - limit (query, optional): Optional. At most this many results of each kind, 1 to 10 (default 5). Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/search?query=..." \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool search", "livemode": true } ``` ### GET /api/v1/{slug}/how-do-i: How do I Requires an API key. How to do something in Bookatu: the closest matching admin tasks, each with plain steps, a link to the exact page and card, whether a tool does it, and its help guide. Any key of the business. Any API key of this business may call it: it needs no scope. The same as the MCP tool how_do_i. Parameters: - question (query, required): What the person wants to do, in their own words, in any of the 14 languages. Up to 500 characters. - language (query, optional): Optional. The language to answer the help guides' steps in, as a code: en, cs, da, de, es, fi, fr, it, ja, nb, nl, pl, pt or sv. Omit for the business's own language. - limit (query, optional): Optional. At most this many tasks, 1 to 5 (default 3). Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/how-do-i?question=..." \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool how_do_i", "livemode": true } ``` ### GET /api/v1/{slug}/open: Open in Bookatu Requires an API key. The link to a dashboard screen, by task, path, section or tool, with why it is done there (never through an AI, or finished by the person on another site). Any key of the business. Any API key of this business may call it: it needs no scope. The same as the MCP tool open_in_bookatu. Parameters: - screen (query, required): The task or screen: words, a dashboard path, a settings section or a tool's name. Up to 200 characters. - id (query, optional): Optional. A record's id, for a screen of one record (a client, a booking, a form, a sale). Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/open?screen=..." \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool open_in_bookatu", "livemode": true } ``` ### GET /api/v1/{slug}/help: Help centre Requires an API key. The help centre's guides for a question, in the business's language, with their screens, and what an AI never does here. Any key of the business. Any API key of this business may call it: it needs no scope. The same as the MCP tool get_help. Parameters: - question (query, optional): Optional. What to find help on, in any of the 14 languages. Up to 500 characters. - language (query, optional): Optional. The language to answer the help guides' steps in, as a code: en, cs, da, de, es, fi, fr, it, ja, nb, nl, pl, pt or sv. Omit for the business's own language. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/help" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_help", "livemode": true } ``` ### GET /api/v1/{slug}/approvals/{id}: Where an approval has got to Requires an API key. Where a change waiting for a person's approval has got to (pending, approved, declined, used or expired), with the page it is approved on. Needs the approved tool's own scope. Any API key of this business may call it: it needs no scope. The same as the MCP tool get_approval. Parameters: - id (path, required): The approvalId an APPROVAL_REQUIRED answer gave. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/approvals/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_approval", "livemode": true } ``` ### POST /api/v1/{slug}/service-categories/rename: Rename a service category Requires an API key. Needs the catalog:write scope. Rename a service category, or merge it into another: every service in it moves. Answers how many moved. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool rename_service_category. Parameters: - from (body, required): The category as it is spelt now (from list_services). - to (body, required): The new name, or the category to merge into. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/service-categories/rename" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"from":"...","to":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool rename_service_category", "livemode": true } ``` ### POST /api/v1/{slug}/stock-deliveries: Receive a delivery Requires an API key. Needs the catalog:write scope. Receive a whole supplier delivery into stock, 1 to 40 lines, all or nothing. Requires a read-write key. Needs the catalog:write scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool bulk_receive_stock. Parameters: - items (body, required): One line per product delivered, 1 to 40. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the catalog:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/stock-deliveries" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"items":[]}' ``` Example response: ``` { "...": "the same answer as the MCP tool bulk_receive_stock", "livemode": true } ``` ### POST /api/v1/{slug}/products/{id}/sales: Record an in-person sale Requires an API key. Needs the pos:write scope, on a key made with it ticked. Record a product sold in person: its stock drops and the sale counts at its price. Takes no payment. Needs pos:write. Needs the pos:write scope, on a key made with it ticked. Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool sell_product. Parameters: - id (path, required): The tracked product (from list_products). - qty (body, optional): How many were sold, a whole number from 1 (default 1). - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the pos:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/products/abc123/sales" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool sell_product", "livemode": true } ``` ### POST /api/v1/{slug}/time-blocks: Block time Requires an API key. Needs the bookings:write scope. Block time on the calendar for one team member or the whole business, ending no later than the last day clients can book (a longer block is refused with 422; make it on the calendar). A burst of blocks from one key is refused with 429. Requires a read-write key. Needs the bookings:write scope. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool block_time. Parameters: - staffId (body, optional): Optional. One team member (from list_staff). Omit for the whole business. - startAt (body, required): When the block starts: an ISO 8601 time with its offset (2026-11-05T13:00:00+13:00), or the business's own clock time without one (2026-11-05T13:00), read strictly: a time the clocks skip is refused as TIME_DOES_NOT_EXIST and one they show twice as TIME_AMBIGUOUS. - endAt (body, required): When it ends, after the start: an ISO 8601 time with its offset (2026-11-05T13:00:00+13:00), or the business's own clock time without one (2026-11-05T13:00), read strictly: a time the clocks skip is refused as TIME_DOES_NOT_EXIST and one they show twice as TIME_AMBIGUOUS. - reason (body, optional): Optional. Up to 200 characters, such as Lunch. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the bookings:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/time-blocks" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"startAt":"...","endAt":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool block_time", "livemode": true } ``` ### POST /api/v1/{slug}/appointments/{id}/notes: Add a booking note Requires an API key. Needs the bookings:write scope. Add to a booking's internal note, never shown to the client. Requires a read-write key. Needs the bookings:write scope. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is not found. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool add_booking_note. Parameters: - id (path, required): The booking (from list_appointments or search). - note (body, required): The text to add, up to 2,000 characters. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the bookings:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/appointments/abc123/notes" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"note":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool add_booking_note", "livemode": true } ``` ### POST /api/v1/{slug}/customers: Add a client Requires an API key. Needs the customers:manage scope, on a key made with it ticked. Add a client: a name, and an email and phone when given. Never sets marketing consent. Needs customers:manage. Needs the customers:manage scope, on a key made with it ticked. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_customer. Parameters: - name (body, required): The client's name. - email (body, optional): Optional. Their email address. - phone (body, optional): Optional. Their phone number, with its country code. - notes (body, optional): Optional. Notes for the team. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the customers:manage scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/customers" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"name":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool create_customer", "livemode": true } ``` ### PATCH /api/v1/{slug}/customers/{id}: Update a client Requires an API key. Needs the customers:manage scope, on a key made with it ticked. Change a client's name, email, phone or notes. Never changes marketing consent. Needs customers:manage. Needs the customers:manage scope, on a key made with it ticked. Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool update_customer. Parameters: - id (path, required): The client (from list_customers or search). - name (body, optional): Optional. Their new name. - email (body, optional): Optional. Their email address; empty clears it. - phone (body, optional): Optional. Their phone number; empty clears it. - notes (body, optional): Optional. Notes for the team; empty clears them. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the customers:manage scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/customers/abc123" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool update_customer", "livemode": true } ``` ### POST /api/v1/{slug}/customers/{id}/notes: Add a client note Requires an API key. Needs the customers:manage scope, on a key made with it ticked. Add to a client's notes. Needs customers:manage. Needs the customers:manage scope, on a key made with it ticked. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool add_customer_note. Parameters: - id (path, required): The client (from list_customers or search). - note (body, required): The text to add, up to 2,000 characters. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the customers:manage scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/customers/abc123/notes" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"note":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool add_customer_note", "livemode": true } ``` ### POST /api/v1/{slug}/announcements: Post an announcement Requires an API key. Needs the marketing:write scope, on a key made with it ticked. Post a notice on the storefront's What's on board, live at once. Needs marketing:write. Needs the marketing:write scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_announcement. Parameters: - title (body, required): A short, clear title, up to 140 characters. - body (body, optional): Optional. The notice itself. - linkUrl (body, optional): Optional. A link for the notice. - linkLabel (body, optional): Optional. The link's words. - pinned (body, optional): Optional. Keep it at the top. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the marketing:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/announcements" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{"title":"..."}' ``` Example response: ``` { "...": "the same answer as the MCP tool create_announcement", "livemode": true } ``` ### GET /api/v1/{slug}/client-messages: Which messages clients get Requires an API key. Needs the messages:read scope, on a key made with it ticked. Which automatic emails and texts the business's clients get: manualOnly ("Only send client messages when we press Send") and each message type with its email and text switches, their defaults and where each is kept. Read-only. Needs the messages:read scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_client_messages. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the messages:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/client-messages" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "...": "the same answer as the MCP tool get_client_messages", "livemode": true } ``` ### PATCH /api/v1/{slug}/client-messages: Change which messages clients get Requires an API key. Needs the messages:write scope, on a key made with it ticked. Turn automatic client emails and texts on or off: manualOnly, and types by key with email and sms true or false. Unknown or fixed types and channels are refused with fieldErrors. Audited. Sending the same again changes nothing. Needs the messages:write scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool set_client_messages. Parameters: - manualOnly (body, optional): true: only send client messages when the team presses Send; held messages are never sent later. false: automatic messages go again, each by its own switch. - types (body, optional): Message type keys from get_client_messages, each with email and/or sms true or false. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the messages:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X PATCH "https://bookatu.com/api/v1/maison-vera/client-messages" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool set_client_messages", "livemode": true } ``` ### GET /api/v1/{slug}/client-messages/held: Messages held by your settings Requires an API key. Needs the messages:read scope, on a key made with it ticked. The client messages the business's switches held back, newest first: key (the switch key PATCH /client-messages takes), type, channel, reason (switched_off or manual_only), when, and the booking and client ids. Never sent later by itself: Send now (POST /client-messages/held/{id}/send) sends one. No addresses or message words. Read-only. Needs the messages:read scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool list_held_client_messages. Parameters: - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the messages:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/client-messages/held" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "held": [ ... ], "nextCursor": null, "livemode": true } ``` ### POST /api/v1/{slug}/client-messages/held/{id}/send: Send a held client message Requires an API key. Needs the messages:write scope, on a key made with it ticked. Send now on one held client message: it goes by its own channel only, as the team's press, with the switches left as they are. A second call answers alreadySent: true and sends nothing more. Refusals use the Settings page's own words, with a reason: 404 not_found when it is not a held message of this business; 409 in_flight while an earlier press is still sending it; 422 too_late, not_sent (no email or number, or messages off for the client; or a text the text service would not take) or texts_off (the business cannot send this text now); 500 send_failed, to try again. Audited. Needs the messages:write scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool send_held_client_message. Parameters: - id (path, required): The held message's id, from list_held_client_messages. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the messages:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 404: The id is not a message this business held (reason not_found: "That message is not held any more."). - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 409: An earlier press is still sending that message (reason in_flight): check again in a moment. Nothing more is sent. A send that never finished is let go after 15 minutes. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 422: Too late to send it: the day has passed, or the booking was cancelled or moved (reason too_late). - 422: It cannot go: the client has no email or number for it, or messages are off for them or for this booking (reason not_sent). Also a text the text service would not take, and a text that may already have reached the client, which is never sent twice, each in its own words. - 422: A held text the business cannot send now (reason texts_off): its texts are off or not on its plan, or Bookatu's numbers do not send that text, or do not text the client's country yet. - 429: Past a rate limit: wait Retry-After seconds. - 500: It could not be sent just now (reason send_failed): try again. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/client-messages/held/abc123/send" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool send_held_client_message", "livemode": true } ``` ### GET /api/v1/{slug}/enquiries/held: Website enquiries held for you Requires an API key. Needs the customers:read scope. The website enquiries held for the business because the key that sent them could not add enquiries any more (its maker is not on the team, or their role lost the right), newest first: the reason, the key it came with, the person's name, email and phone, the trip, dates, people, message and reference. Each is kept 30 days. Read-only. Needs the customers:read scope. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Answers one page at a time: limit (1 to 200, default 50) and cursor, the nextCursor of the page before; nextCursor is null on the last page. The same as the MCP tool list_held_enquiries. Parameters: - limit (query, optional): Optional. How many to answer, 1 to 200. Send it (or cursor) to page the list; nextCursor then says where the next page starts. Leave both out for the whole list. - cursor (query, optional): Optional. The nextCursor of the page before, for the next page. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the customers:read scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/enquiries/held" \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "held": [ ... ], "nextCursor": null, "livemode": true } ``` ### POST /api/v1/{slug}/enquiries/held/{id}/release: Move a held enquiry into Leads Requires an API key. Needs the enquiries:write scope, on a key made with it ticked. Move one held website enquiry into Leads, as the website form would have: the same lead and the New enquiry alert, and it is held no more. One whose reference reached Leads since answers duplicate: true and makes no second lead. The person who wrote is not sent anything. Audited. Needs the enquiries:write scope, on a key made with it ticked. The person who made the key must still have "Manage the business" on the business's Roles & permissions, as on the tool's own screen; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same body within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and changes nothing again; the same key with another body is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool release_held_enquiry. Parameters: - id (path, required): The held enquiry's id, from list_held_enquiries. - dryRun (body, optional): Optional. true: change nothing, and answer what this call would do instead: the record it touches, who is told (an email or text to a client, the public site) and what changes. Call again without it to make the change. Errors: - 401: The API key is missing or invalid. - 403: The key is another business's, or lacks the enquiries:write scope (missingScope names it), or the person who made it may no longer do this (code MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM), or Bookatu has suspended the business (code BUSINESS_SUSPENDED). Every refusal says what to do next. - 404: No business exists for the {slug}, or the record is not this business's. - 404: The id is not a website enquiry this business holds now, or it was released, deleted or kept its 30 days already (reason not_found: "That enquiry is not held any more."). - 409: The Idempotency-Key was used with another body (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). - 422: An argument is not valid (fieldErrors names each), or the tool refused the change, in its own words and code. Or the Idempotency-Key header is longer than 200 characters, or has spaces or characters that are not printable (code INVALID_IDEMPOTENCY_KEY). - 429: Past a rate limit: wait Retry-After seconds. Example request: ``` curl -X POST "https://bookatu.com/api/v1/maison-vera/enquiries/held/abc123/release" \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 2f1c7e9a-your-own-key" \ -d '{}' ``` Example response: ``` { "...": "the same answer as the MCP tool release_held_enquiry", "livemode": true } ``` ### GET /api/v1/{slug}/walk-in: Walk-in wait now No authentication required. The business's live walk-in wait: the answer its booking page, its walk-in widget and the MCP tool get_walk_in_wait give for the same moment. Worked out from its calendar for today, on its own clock, as a walk-in is served: the team's in-person bookings count and the minimum notice does not apply (online booking keeps it, so the booking page may offer a later first time). Or set by hand by the team (mode manual, with manual.setAt and manual.expiresAt) until it lapses. state is no_wait (the earliest start is within 5 minutes: walk in now), wait (5 to 90 minutes away; waitMin is rounded up to 5), busy (more than 90 minutes away; nextAt says when), full_today (open now, nothing fits before closing), closed (closed now; closed.opensAt says when it opens, null when no opening is in the next 14 days) or not_taking (set by hand). waitMin and nextAt beside state are the shortest wait. busy gives counts only (staffBusy of staffWorking with a client, appointmentsLeftToday) when the business shows them; no client or team member is ever named. services lists up to 12 walk-in services in menu order, each with its own state, waitMin, nextAt and bookUrl (its booking page on today's date; null for a service not booked online). Every time is an instant in UTC; timeZone is the business's clock. A business with walk-in wait times off answers 200 with status off and no numbers. Kept about a minute. Parameters: - serviceId (query, optional): One walk-in service (an id from services); omit for every walk-in service. An id that is not one of this business's walk-in services is 404 SERVICE_NOT_FOUND. - locationId (query, optional): One of this business's branches: the wait at that branch, on its own clock. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected, and the answer is the whole business's. Errors: - 404: No published business with that slug, or serviceId names no walk-in service of this business (code SERVICE_NOT_FOUND). - 429: Too many requests from this address (Retry-After says when to try again). - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/walk-in ``` Example response: ``` { "status": "on", "mode": "automatic", "state": "wait", "waitMin": 20, "nextAt": "2026-11-03T01:20:00.000Z", "updatedAt": "2026-11-03T01:02:00.000Z", "timeZone": "Pacific/Auckland", "busy": { "staffBusy": 3, "staffWorking": 4, "appointmentsLeftToday": 6 }, "services": [ { "id": "svc_cut", "name": "Cut", "state": "wait", "waitMin": 20, "nextAt": "2026-11-03T01:20:00.000Z", "bookUrl": "https://bookatu.com/maison-vera/book?service=svc_cut&date=2026-11-03" }, { "id": "svc_beard", "name": "Beard trim", "state": "busy", "nextAt": "2026-11-03T03:30:00.000Z", "bookUrl": "https://bookatu.com/maison-vera/book?service=svc_beard&date=2026-11-03" } ], "livemode": true } // Turned off: { "status": "off", "livemode": true } ``` ### PUT /api/v1/{slug}/walk-in/manual: Set the walk-in wait by hand Requires an API key. Needs the bookings:write scope. Set the walk-in wait by hand, as the team does from the dashboard: minutes (0 to 240; 0 is no wait) or notTaking true, for the whole business (or one branch while branches are on), until it lapses: expiry 1h, 2h or end_of_day (midnight at the end of the business's day), the business's own default when left out. Replaces the wait set before. Within about a minute GET /walk-in, the booking page and MCP give mode manual with manual.setAt and manual.expiresAt (the walk-in widget at its next refresh, within about two), and the booking page says when the team updated it; once it lapses the wait is worked out from the calendar again. Answers the walk-in answer as it now stands. Recorded in the audit log, naming the key. Refused with 409 WALK_IN_OFF while the business has walk-in wait times off. Needs bookings:write; a read-only key is refused. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool set_walk_in_wait. Parameters: - minutes (body, optional): Minutes a walk-in would wait, a whole number from 0 to 240. Send this or notTaking. - notTaking (body, optional): true: not taking walk-ins right now. Send this or minutes. - expiry (body, optional): 1h, 2h or end_of_day. The business's own default (Settings, Walk-ins) when left out. - locationId (body, optional): One of this business's branches: the wait at that branch, on its own clock. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected, and the answer is the whole business's. Errors: - 400: The body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation (or the other mode: LIVEMODE_MISMATCH), it lacks bookings:write (the body names it as missingScope), or it is a read-only key made before scopes. - 404: No business with that slug. - 409: Walk-in wait times are turned off for this business (code WALK_IN_OFF). - 422: Neither or both of minutes and notTaking: true, minutes not a whole number from 0 to 240, or an unknown expiry (fieldErrors names the field). - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X PUT https://bookatu.com/api/v1/maison-vera/walk-in/manual \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "minutes": 30, "expiry": "2h" }' ``` Example response: ``` { "status": "on", "mode": "manual", "state": "wait", "waitMin": 30, "updatedAt": "2026-11-03T01:02:00.000Z", "timeZone": "Pacific/Auckland", "manual": { "setAt": "2026-11-03T01:02:00.000Z", "expiresAt": "2026-11-03T03:02:00.000Z" }, "busy": { "staffBusy": 3, "staffWorking": 4, "appointmentsLeftToday": 6 }, "services": [ { "id": "svc_cut", "name": "Cut", "state": "wait", "waitMin": 30, "bookUrl": "https://bookatu.com/maison-vera/book?service=svc_cut&date=2026-11-03" } ], "livemode": true } ``` ### DELETE /api/v1/{slug}/walk-in/manual: Back to the automatic walk-in wait Requires an API key. Needs the bookings:write scope. Take off the wait set by hand, for the whole business (or one branch while branches are on), so the wait is worked out from the calendar again at once. Answers the walk-in answer as it now stands, with cleared true when a wait set by hand was in force and false when there was none. Recorded in the audit log, naming the key, when one was cleared. Works while walk-in wait times are off too (the answer is then status off). Needs bookings:write; a read-only key is refused. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool clear_walk_in_wait. Parameters: - locationId (query, optional): One of this business's branches: the wait at that branch, on its own clock. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected, and the answer is the whole business's. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation (or the other mode: LIVEMODE_MISMATCH), it lacks bookings:write (the body names it as missingScope), or it is a read-only key made before scopes. - 404: No business with that slug. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X DELETE https://bookatu.com/api/v1/maison-vera/walk-in/manual \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "cleared": true, "status": "on", "mode": "automatic", "state": "no_wait", "waitMin": 0, "nextAt": "2026-11-03T01:05:00.000Z", "updatedAt": "2026-11-03T01:05:00.000Z", "timeZone": "Pacific/Auckland", "services": [ { "id": "svc_cut", "name": "Cut", "state": "no_wait", "waitMin": 0, "nextAt": "2026-11-03T01:05:00.000Z", "bookUrl": "https://bookatu.com/maison-vera/book?service=svc_cut&date=2026-11-03" } ], "livemode": true } // cleared is false when no wait set by hand was in force. ``` ### POST /api/v1/{slug}/enquiries: Send an enquiry from your website form Requires an API key. Needs the enquiries:write scope, on a key made with it ticked. One enquiry from the business's own website form, sent from its server (or Zapier or Make) after its own spam check. It lands in Leads as an enquiry, whether or not the business has a public page, and is never a client or a booking until the team books them in. Send an email, a phone or both; every other field is optional. Fields it does not know are ignored, so an extra field never breaks a send. The whole body can be up to 64 KB. A new enquiry answers 201 with its id (lead_enq_ and 16 characters). The same reference again, from any of the business's keys, answers 200 with the first enquiry's id and duplicate true, and makes nothing new; two sends at once with one reference make one enquiry. Bookatu emails nobody about it and texts nobody: not the person who enquired, and not the business, whose own form already emails it. It shows in Leads and on the dashboard home. A test copy takes its own bk_test_ key on its sbx- address, and its enquiries stay in its own Leads. Parameters: - email (body, optional): An email address the business can reply to, up to 200 characters, kept lowercased. Send an email, a phone or both: with neither, the answer is 422 on fieldErrors.email. - phone (body, optional): A phone number in any format, up to 40 characters, with the country code for an overseas number (like +94 77 123 4567). It is read with the business's own country, as the dashboard reads one. Send an email, a phone or both. - name (body, optional): The person's name, up to 120 characters. Without one the enquiry has no name until the business books them in. - tripId (body, optional): A trip's code, as GET /enquiries/trips lists it (svc_ and 16 characters). It never changes when the trip is renamed. Must be one of this business's trips (services of whole days), else 422 on fieldErrors.tripId. A trip switched off in Bookatu is still taken: the enquiry is kept with that trip's name, linked to no trip (trip.matched false). When sent, trip is not read. Only trips can be linked: a business with no trips leaves tripId out and sends what the enquiry is about as trip. - trip (body, optional): The trip's name as the website shows it, when there is no tripId, up to 200 characters. It is matched to one of this business's active trips ignoring capitals and spaces; with no match it is kept as written, linked to no trip (trip.matched false). A business with no trips sends what the enquiry is about here. - preferredStart (body, optional): The first day they would like, YYYY-MM-DD, today or later where the visitor is: the business's own yesterday is taken too, as a visitor in another time zone may still be on it. - preferredEnd (body, optional): The last day they would like, YYYY-MM-DD, on or after preferredStart, and only with a preferredStart. - people (body, optional): How many people, a whole number from 1 to 100. 0 is read as not sent, as a form's blank number field often arrives as 0. - quote (body, optional): The price the website showed them, in cents: { "currency": "NZD", "perPersonCents": 245000, "totalCents": 490000 }. currency must be the business's own currency (else 422 on fieldErrors["quote.currency"]); send perPersonCents, totalCents or both, each a whole number from 0 to 10,000,000. A quote with neither amount is read as not sent. When a team member who can set prices books them in, the booking starts at this price: the total, else the price per person times the people booked (an amount of 0 is not used). Anyone else books it at the list price, and the price can be changed on the booking after saving. So work the quote out on your own server from your own prices, and never pass on a figure the visitor's browser worked out or could change. - message (body, optional): Their message, up to 5,000 characters, kept in full. - answers (body, optional): Every other question on the form, as a list of { "question": "...", "answer": "..." }: up to 20, each question up to 200 characters and each answer up to 1,000. An answer may be text, a number, true or false, or a list of them (a question with several choices), kept as one line joined by commas. A question left unanswered is not kept. - reference (body, optional): The website's own id for this entry (a form tool's entry number, or a new UUID): 1 to 64 letters, digits, dots, dashes and underscores. Strongly recommended: the same reference again answers 200 with the first enquiry, so a retry never makes a second one. - page (body, optional): The address of the page the form was on, http:// or https://. Kept without its query string or fragment, and up to 500 characters without them. Leads shows its site name. Errors: - 400: The body is not JSON, or not a JSON object. Do not retry it as it is. - 401: No key, or a key that does not exist, has expired or was revoked. - 403: The key belongs to another business, or it is a key of the other mode (code LIVEMODE_MISMATCH: a bk_test_ key sent to a live address, or a bk_live_ key sent to a test copy's sbx- address). Or it lacks enquiries:write (the body names it as missingScope). Or the AI & API add-on is off: "Enable the AI & API add-on". A test copy has the add-on on already. Or Bookatu has suspended the business, so its API keys are switched off: the body has code BUSINESS_SUSPENDED and the words "This business is suspended, so its API keys are switched off. Contact Bookatu support." When the key carries enquiries:write but that scope is switched off (the person who made the key is not on the business's team, or their role lost the right), a good enquiry is held for the business for 30 days. The answer is this same 403 whether it was held or not. The business's owners and admins are told, and can release it into Leads. Make a new key on the Developer API page to stop it. - 404: No business with that slug. - 413: The body is over 64 KB (65,536 bytes). Shorten the long fields. - 422: A field is wrong, or there is neither an email nor a phone. fieldErrors names each field, like { "email": "..." }: a tripId that was never one of this business's trips, a quote in another currency, a first day before yesterday on the business's calendar or a last day before the first are refused here too. Nothing is kept. Do not retry it as it is. - 429: Too many calls this minute, or today, from this key or for this business. Wait the seconds in the Retry-After header, then send again with the same reference. - 500: Something went wrong on our side (details are never shown). Send again later with the same reference: nothing is duplicated. Example request: ``` curl -X POST https://bookatu.com/api/v1/your-business/enquiries \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "reference": "WEB-1042", "name": "Ava Thompson", "email": "ava@example.com", "phone": "+64 21 555 0142", "tripId": "svc_4kT9qLm2Xw7pRb1N", "preferredStart": "2027-02-15", "preferredEnd": "2027-02-23", "people": 2, "quote": { "currency": "NZD", "perPersonCents": 245000, "totalCents": 490000 }, "message": "We would love a slower pace.", "page": "https://example.com/contact", "answers": [ { "question": "Who is travelling?", "answer": "Two adults" } ] }' ``` Example response: ``` { "id": "lead_enq_V1StGXR8Z5jdHi6B", "status": "received", "duplicate": false, "trip": { "id": "svc_4kT9qLm2Xw7pRb1N", "name": "Mountain lakes trek", "matched": true }, "livemode": true } // 201 for a new enquiry. The same reference again: 200, the first enquiry's id, "duplicate": true. // A trip name with no match: "trip": { "id": null, "name": "As they wrote it", "matched": false }. // No trip at all: "trip": { "id": null, "name": null, "matched": false }. ``` ### GET /api/v1/{slug}/enquiries/trips: List the trip codes for enquiries Requires an API key. Needs the enquiries:write scope, on a key made with it ticked. This business's active trips (services of whole days), each with the code an enquiry sends as tripId, its name and how many days it lasts, in the business's own order. Never a price. A trip's code never changes when it is renamed. A test copy's trips have their own codes, and a test copy reset gives them new ones, so list them again with the live key at go-live and after a reset. Reading writes nothing. Errors: - 401: No key, or a key that does not exist, has expired or was revoked. - 403: The key belongs to another business, or it is a key of the other mode (code LIVEMODE_MISMATCH: a bk_test_ key sent to a live address, or a bk_live_ key sent to a test copy's sbx- address). Or it lacks enquiries:write (the body names it as missingScope). Or the AI & API add-on is off: "Enable the AI & API add-on". A test copy has the add-on on already. Or Bookatu has suspended the business, so its API keys are switched off: the body has code BUSINESS_SUSPENDED and the words "This business is suspended, so its API keys are switched off. Contact Bookatu support." - 404: No business with that slug. - 429: Too many calls this minute, or today, from this key or for this business. Wait the seconds in the Retry-After header, then send again with the same reference. - 500: Something went wrong on our side (details are never shown). Send again later with the same reference: nothing is duplicated. Example request: ``` curl https://bookatu.com/api/v1/your-business/enquiries/trips \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "trips": [ { "id": "svc_4kT9qLm2Xw7pRb1N", "name": "Mountain lakes trek", "days": 8 }, { "id": "svc_Zp3cV8nQe1Ls6YtA", "name": "Coast by train", "days": 5 } ], "livemode": true } ``` ### GET /api/v1/{slug}/agent/business: Business details and policies, for an assistant No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. The business's city and area (never a street address), its time zone and the time there now, this week's opening hours, its branches, its booking policies, and whether a time can be held here (agentBooking.available). Parameters: - locationId (query, optional): A branch of the business, from branches. - language (query, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. - clientTimeZone (query, optional): The person's IANA time zone, such as America/Toronto: times are given on their clock as well as the business's. Ask for their city when unsure. Errors: - 400: INVALID_PARAMS: a query parameter the endpoint does not take, one given twice, or one outside its type or range. violations names each, at most five. - 404: BUSINESS_NOT_FOUND: no business has that {slug}, or the {slug} is not a slug as it stands (a link or a web address is not one here). - 409: BUSINESS_NOT_AGENT_BOOKABLE: the business does not take bookings from assistants. bookingPageUrl is where the person books it themselves. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/agent/business?clientTimeZone=America/Toronto" ``` Example response: ``` { "slug": "maison-vera", "name": { "text": "Maison Vera", "writtenIn": "en", "source": "business" }, "kind": "Hair salon", "city": { "text": "Auckland", "writtenIn": "en", "source": "business" }, "country": "NZ", "timeZone": "Pacific/Auckland", "currency": "NZD", "policies": { "freeCancellationHours": 24, "lateCancelKeepsDeposit": false, "approval": "none", "sentences": ["Free cancellation up to 24 hours before."] }, "agentBooking": { "available": true, "depositsInChat": false }, "bookingPageUrl": "https://bookatu.com/maison-vera/book", "client": { "timeZone": "America/Toronto", "source": "given" }, "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } // Also now, hoursThisWeek, branches, speaks and storefrontLanguage. Each time // is a When: utc, and the business's clock and the person's. ``` ### GET /api/v1/{slug}/agent/services: Services and prices, for an assistant No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. Each service the business offers assistants: its name, description, length and price, any deposit, and bookVia. bookVia assistant means a time can be held through this API; bookVia website means the person books it on the business's own page at bookingPageUrl. Parameters: - query (query, optional): Words to look for in a service's name, category or description. - category (query, optional): Only the services of this category. - locationId (query, optional): Only the services of this branch. - limit (query, optional): 1 to 50, 20 when not given. more says whether there are others. - language (query, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. - clientTimeZone (query, optional): The person's IANA time zone, such as America/Toronto: times are given on their clock as well as the business's. Ask for their city when unsure. Errors: - 400: INVALID_PARAMS: a query parameter the endpoint does not take, one given twice, or one outside its type or range. violations names each, at most five. - 404: BUSINESS_NOT_FOUND: no business has that {slug}, or the {slug} is not a slug as it stands (a link or a web address is not one here). - 409: BUSINESS_NOT_AGENT_BOOKABLE: the business does not take bookings from assistants. bookingPageUrl is where the person books it themselves. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/agent/services?query=cut" ``` Example response: ``` { "business": { "slug": "maison-vera", "name": { "text": "Maison Vera", "writtenIn": "en", "source": "business" } }, "services": [ { "id": "svc_abc123", "name": { "text": "Cut and blow-dry", "writtenIn": "en", "source": "business" }, "duration": { "minutes": 60, "display": "1 hr" }, "price": { "amountMinor": 6500, "currency": "NZD", "display": "NZ$65.00" }, "deposit": null, "bookVia": "assistant", "remote": false } ], "more": false, "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } ``` ### GET /api/v1/{slug}/agent/availability: Open times, for an assistant No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. Open times for one service over up to 14 days from dateFrom, each on the business's clock and, with clientTimeZone, on the person's too, with the price at that time. A time with bookVia assistant has a slotId: hold it with POST /agent/holds within 30 minutes. Quote times from their display fields as given. Parameters: - serviceId (query, required): A service id from GET /agent/services. - dateFrom (query, required): The first day, YYYY-MM-DD, on the business's calendar unless dateClock says client. - dateTo (query, optional): The last day, YYYY-MM-DD: 14 days in all at most. - dateClock (query, optional): client or business: whose calendar the dates are on (the business's when not given). - partOfDay (query, optional): morning, afternoon or evening. - staffId (query, optional): A person, when the client wants one. - locationId (query, optional): A branch of the business. - addOnIds (query, optional): Extras by id, at most 5: repeat the parameter or separate them with commas. - partySize (query, optional): How many people, 1 to 10. - limit (query, optional): 1 to 40, 12 when not given. - clientTimeZone (query, optional): The person's IANA time zone, such as America/Toronto: times are given on their clock as well as the business's. Ask for their city when unsure. - language (query, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. Errors: - 400: INVALID_PARAMS: a query parameter the endpoint does not take, one given twice, or one outside its type or range. violations names each, at most five. - 404: BUSINESS_NOT_FOUND: no business has that {slug}, or the {slug} is not a slug as it stands (a link or a web address is not one here). - 409: BUSINESS_NOT_AGENT_BOOKABLE: the business does not take bookings from assistants. bookingPageUrl is where the person books it themselves. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. - 400: TIME_INVALID, UNKNOWN_TIME_ZONE or WINDOW_TOO_LONG: a date that is not one, a time zone that is not an IANA name, or more than 14 days. - 409: SERVICE_NOT_AVAILABLE: no such service, or not one an assistant can book. bookingPageUrl is where the person books it. Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/agent/availability?serviceId=svc_abc123&dateFrom=2026-11-06&clientTimeZone=America/Toronto" ``` Example response: ``` { "business": { "slug": "maison-vera", "name": { "text": "Maison Vera", "writtenIn": "en", "source": "business" }, "timeZone": "Pacific/Auckland" }, "service": { "id": "svc_abc123", "name": { "text": "Cut and blow-dry", "writtenIn": "en", "source": "business" }, "duration": { "minutes": 60, "display": "1 hr" } }, "window": { "from": "2026-11-06", "to": "2026-11-06", "datesAreOn": "business" }, "bookVia": "assistant", "slots": [ { "slotId": "eyJvIjoib3JnX2FiYyIsInMiOiJzdmNfYWJjMTIzIn0.Hk3x9Qe", "start": { "utc": "2026-11-05T21:00:00Z", "primary": "business", "business": { "timeZone": "Pacific/Auckland", "local": "2026-11-06T10:00:00+13:00", "display": "Fri 6 Nov, 10:00" } }, "end": { "utc": "2026-11-05T22:00:00Z", "primary": "business", "business": { "timeZone": "Pacific/Auckland", "local": "2026-11-06T11:00:00+13:00", "display": "Fri 6 Nov, 11:00" } }, "staff": { "id": "stf_abc123", "name": { "text": "Ana", "writtenIn": "en", "source": "business" } }, "branch": null, "price": { "amountMinor": 6500, "currency": "NZD", "display": "NZ$65.00" }, "bookVia": "assistant" } ], "days": [{ "date": "2026-11-06", "status": "open" }], "more": true, "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } // Also client, bookingPageUrl, notes, warnings and freeCancellationRule. ``` ### POST /api/v1/{slug}/agent/holds: Hold a time and email the person to confirm it No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. Holds a time from GET /agent/availability for up to 15 minutes and emails the person, who confirms it with the link in the email or by reading the 6-digit code from it to the assistant (POST /agent/holds/{holdId}/confirm). Nothing is booked until they confirm, and no payment is taken. Send the person's own name and email address, their time zone and an Idempotency-Key header: a retry with the same key and details answers with the same hold, and another request under a used key is a new one. To change a time you already held, release the earlier hold with POST /agent/holds/{holdId}/release first. The answer always has bookingPageUrl, and while the time is held nextStepIfNoEmail says what to do if no email comes. The slotId must be one of this {slug}'s times. Parameters: - Idempotency-Key (header, required): 16 to 64 visible characters: the same key for a retry of the same hold, a new one for a new hold. - slotId (body, required): A slotId from GET /agent/availability, used within 30 minutes. - client (body, required): { name, email, phone? }: the person's own details, as they gave them. They confirm from that email address. - clientTimeZone (body, required): The person's IANA time zone, such as America/Toronto: times are given on their clock as well as the business's. Ask for their city when unsure. - partySize (body, optional): How many people, when the time was found for more than one: the same partySize. - language (body, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. Errors: - 400: IDEMPOTENCY_KEY_REQUIRED: no Idempotency-Key header (the key goes there, never in the body). - 400: SLOT_INVALID: not a slotId, or one of another business than the {slug}'s. INVALID_CLIENT or UNKNOWN_TIME_ZONE: the person's details or time zone. - 400: INVALID_BODY: the body is not JSON, or not a JSON object. INVALID_PARAMS: a field the endpoint does not take, or one outside its type or range (violations names each, at most five). - 413: INVALID_BODY: the body is over 64 KB. - 415: INVALID_BODY: the Content-Type is not application/json. - 404: BUSINESS_NOT_FOUND: the slotId's business is gone. - 409: SLOT_TAKEN: the time went; alternatives lists up to three others. SLOT_EXPIRED: the slotId is over 30 minutes old. - 400: IDEMPOTENCY_MISMATCH: a key that cannot be used, such as one with spaces. Send a new key of 16 to 64 visible characters. - 409: HOLD_LIMIT: as many times are held as may be for now, at the business, by this caller or by the caller's network there (open now, or made in the last day), or across the platform in the last day. bookingPageUrl is the business's own booking page. - 409: BUSINESS_NOT_AGENT_BOOKABLE or SERVICE_NOT_AVAILABLE: send the person to bookingPageUrl. BUSINESS_NOT_AGENT_BOOKABLE also comes while holds at the business are paused for a while after unusual activity. They start again by themselves. - 422: EMAIL_NOT_ACCEPTED: a time cannot be held for that email address, such as one from a throwaway email service. - 429: RATE_LIMITED also comes here for a while after unusual activity on this caller's earlier holds. Wait retryAfterSec seconds. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/agent/holds \ -H "Content-Type: application/json" \ -H "Idempotency-Key: 4f9c1e7a-hold-0001" \ -d '{ "slotId": "eyJvIjoib3JnX2FiYyIsInMiOiJzdmNfYWJjMTIzIn0.Hk3x9Qe", "client": { "name": "Jane Doe", "email": "jane@example.com" }, "clientTimeZone": "America/Toronto" }' ``` Example response: ``` { "holdId": "hld_V1StGXR8Z5jdHi6BmyT3aQ", "status": "awaiting_client", "heldUntil": { "utc": "2026-11-04T21:15:00Z", "primary": "client", "business": { "timeZone": "Pacific/Auckland", "local": "2026-11-05T10:15:00+13:00" }, "client": { "timeZone": "America/Toronto", "local": "2026-11-04T16:15:00-05:00" } }, "sentTo": "j***@example.com", "confirmWays": ["code", "link"], "booking": { "businessName": { "text": "Maison Vera", "writtenIn": "en", "source": "business" }, "serviceName": { "text": "Cut and blow-dry", "writtenIn": "en", "source": "business" }, "price": { "amountMinor": 6500, "currency": "NZD", "display": "NZ$65.00" }, "approvalNeeded": false }, "messageForUser": "This time is held for you until Thu 5 Nov, 10:15, but it is not booked yet. An email to j***@example.com is on its way if that address can take email from us. To book, open the link in it or tell your assistant the 6-digit code. If nothing arrives within a few minutes, you can book on the business's booking page instead.", "bookingPageUrl": "https://bookatu.com/maison-vera/book?service=svc_abc123&via=ai:other", "nextStepIfNoEmail": "If the person has no email from Bookatu for this time after a few minutes, give them bookingPageUrl so they can book on the business's own page.", "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } // booking also has start, end, and staffName when the person chose someone. ``` ### GET /api/v1/{slug}/agent/holds/{holdId}: Where a held time stands No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. The status of a hold: awaiting_client (with heldUntil), confirming, expired, released, slot_taken or unavailable, and for a confirmed one where the booking stands now (confirmed, requested, declined, cancelled, completed, or confirmed at its new time when it was moved), with its ref. It gives the business, the service and the start, and no personal details. Ask when the person wants to know, not in a loop. Parameters: - holdId (path, required): The holdId POST /agent/holds answered with. - language (query, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. Errors: - 400: INVALID_PARAMS: a query parameter the endpoint does not take, or a holdId that is not one. - 404: HOLD_NOT_FOUND: no hold has that holdId at the business of the {slug}. A hold of another business is not found here. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. Example request: ``` curl https://bookatu.com/api/v1/maison-vera/agent/holds/hld_V1StGXR8Z5jdHi6BmyT3aQ ``` Example response: ``` { "status": "confirmed", "ref": "MV-7QK2M9", "businessName": { "text": "Maison Vera", "writtenIn": "en", "source": "business" }, "serviceName": { "text": "Cut and blow-dry", "writtenIn": "en", "source": "business" }, "start": { "utc": "2026-11-05T21:00:00Z", "primary": "business", "business": { "timeZone": "Pacific/Auckland", "local": "2026-11-06T10:00:00+13:00" } }, "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } ``` ### POST /api/v1/{slug}/agent/holds/{holdId}/confirm: Confirm a held time with the person's code No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. Books the held time with the 6-digit code from the email the person was sent (spaces are left out). The answer is confirmed, or requested when the business looks at new bookings before accepting them, with the booking's ref. If someone else took the time first, it is slot_taken with up to three alternatives. Send only a code the person read to you. Each hold and each caller has a window of confirms a minute, counted before the hold is read and shared with the booking server. POST only: a GET is a 405. Parameters: - holdId (path, required): The holdId POST /agent/holds answered with. - code (body, required): The 6-digit code from the email, as the person read it out. - language (body, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. Errors: - 400: INVALID_BODY: the body is not JSON, or not a JSON object. INVALID_PARAMS: a field the endpoint does not take, or one outside its type or range (violations names each, at most five). - 413: INVALID_BODY: the body is over 64 KB. - 415: INVALID_BODY: the Content-Type is not application/json. - 404: HOLD_NOT_FOUND: no hold has that holdId at the business of the {slug}. A hold of another business is not found here. - 409: HOLD_EXPIRED: the hold ran out or was let go. BUSINESS_NOT_AGENT_BOOKABLE or SERVICE_NOT_AVAILABLE: the business stopped taking this booking from assistants since the hold; send the person to bookingPageUrl. - 422: CODE_WRONG: not the code; attemptsLeft says how many tries are left. CODE_LOCKED: no tries left, so the person confirms with the link in the email. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. - 503: TRY_AGAIN: Bookatu's side failed and the hold is still live. Try again. Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/agent/holds/hld_V1StGXR8Z5jdHi6BmyT3aQ/confirm \ -H "Content-Type: application/json" \ -d '{ "code": "246813" }' ``` Example response: ``` { "status": "confirmed", "ref": "MV-7QK2M9", "booking": { "businessName": { "text": "Maison Vera", "writtenIn": "en", "source": "business" }, "serviceName": { "text": "Cut and blow-dry", "writtenIn": "en", "source": "business" }, "price": { "amountMinor": 6500, "currency": "NZD", "display": "NZ$65.00" } }, "nextStep": "The booking is made. A confirmation email is on its way to you.", "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } // booking also has start and end. A wrong code is HTTP 422: // { "ok": false, "error": "This code is not right. Tries left: 3.", "code": "CODE_WRONG", "attemptsLeft": 3 } ``` ### POST /api/v1/{slug}/agent/holds/{holdId}/release: Release a held time No authentication required. For an assistant helping a person book who cannot use MCP: the public booking server's tool for the same job, as REST. No API key, and none is ever read. The answer is the tool's result as JSON; a refusal is { ok: false, error, code }, error being the person's words in their language, with any extras beside it. While assistant booking is paused, every call is a 503 CHANNEL_PAUSED. Ends a hold that is still waiting, so the time is free again. Any other hold is left as it is, and the answer says where it stands. It never cancels a confirmed booking: the person does that with the business. The body may be empty. POST only: a GET is a 405. Parameters: - holdId (path, required): The holdId POST /agent/holds answered with. - language (body, optional): The language to answer in (BCP 47). Accept-Language is read when it is not given. Errors: - 400: INVALID_BODY: the body is not JSON, or not a JSON object. INVALID_PARAMS: a field the endpoint does not take, or one outside its type or range (violations names each, at most five). - 413: INVALID_BODY: the body is over 64 KB. - 415: INVALID_BODY: the Content-Type is not application/json. - 404: HOLD_NOT_FOUND: no hold has that holdId at the business of the {slug}. A hold of another business is not found here. - 429: RATE_LIMITED: past one of the caller's windows, which this API and the booking server share. Wait retryAfterSec seconds (also the Retry-After header). - 503: CHANNEL_PAUSED: assistant booking is paused on the platform. Nothing was read or counted. Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/agent/holds/hld_V1StGXR8Z5jdHi6BmyT3aQ/release \ -H "Content-Type: application/json" \ -d '{}' ``` Example response: ``` { "status": "released", "meta": { "language": "en", "languageSource": "argument", "generatedAt": "2026-11-04T21:00:00.000Z" } } ``` ### GET /api/v1/{slug}/visits/availability: Open starts for a visit of several services No authentication required. The starts a visit of several services fits (a colour, then a cut) across a date window: the booking page's own question, answered by the same code. The services run back to back: the first on the business's booking grid, each next one the moment the one before ends, each checked as a booking of it on its own would be (someone who does it and is free, its room, the hours and breaks, the business's buffer). Each slot lists every service with who does it and when; the same person carries on from one service to the next where they can. Only at a business that lets clients book several services in one visit (GET /business has visits); anywhere else it is a 409 with code not_offered. Book a returned startAt with POST /visits/book and the same serviceIds, staffId and addOnIds: a time offered here is a time it takes. Each time also comes as when: { utc, primary, business: { timeZone, local, utcOffset, abbr, display }, client } with the offset in force on that day (a slot after the clocks change carries the new one), on the business's clock (the branch's at a branch) and, when the client's zone is known, on theirs (client is null otherwise; dayDiffers says their date is another day). Quote display rather than converting a time yourself. A slot a surcharge covers (a public holiday or a busy time the business charges more for) also has priceCents, surcharges (label, amountType, amount, amountCents) and totalCents, the price at that time, to show the client before they book; other slots have none of these. No authentication required. Parameters: - serviceIds (query, required): Two to four different services from GET /services, in the order they are done (the first one first). Comma-separated. - from (query, required): Start date, YYYY-MM-DD. - to (query, required): End date, YYYY-MM-DD. Must be on or after from, and at most 60 days later. - staffId (query, optional): The team member the client picked: they do every service they do, and the rest go to whoever is free. Omit for anyone. - addOnIds (query, optional): Extras for the first service, comma-separated ids from its addOns on GET /services. One with addsTime makes it longer, and the next services start that much later. - locationId (query, optional): One of this business's branches. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected. - clientTimeZone (query, optional): The client's own time zone, the IANA zone of a place (America/Toronto): each slot's when then gives the time on their clock too. Abbreviations (EST, which would be read as Panama), offsets (+13:00) and Etc/ zones are refused with code UNKNOWN_TIME_ZONE (400): ask the person which city they are in. Never guessed from the request. Errors: - 400: from/to are not YYYY-MM-DD, from is later than to, or the range exceeds 60 days. Or from or to is a date that does not exist, such as 30 February ("Use a real date in YYYY-MM-DD format."), or is too far away ("Ask for dates in the next few years."). - 404: No business exists for the {slug}. - 409: Nothing to offer, and code says why: not_offered (the business books one service at a time online), or cant_combine: these services cannot be one visit, with reason (repeated, unavailable: not offered online, add_on: an extra, class, video, team: a service two or more people do at once) or, when it is one of the business's combination rules, error naming the two ("4 braids and 6 braids can't be booked together.") and combo { kind, first, second }. - 422: serviceIds is not two to four services (fieldErrors.serviceIds), or more than 20 addOnIds. - 500: Unexpected server error (details are never leaked). Example request: ``` curl "https://bookatu.com/api/v1/maison-vera/visits/availability?serviceIds=svc_colour,svc_cut&from=2026-06-10&to=2026-06-12" ``` Example response: ``` { "org": { "name": "Maison Vera", "slug": "maison-vera", "timezone": "Pacific/Auckland" }, "days": [ { "date": "2026-06-10", "open": true, "slots": [ { "startMin": 540, "startAt": "2026-06-09T21:00:00.000Z", "services": [ { "serviceId": "svc_colour", "staffId": "stf_anna", "startAt": "2026-06-09T21:00:00.000Z", "endAt": "2026-06-09T22:30:00.000Z", "durationMin": 90 }, { "serviceId": "svc_cut", "staffId": "stf_anna", "startAt": "2026-06-09T22:30:00.000Z", "endAt": "2026-06-09T23:00:00.000Z", "durationMin": 30 } ] } ] } ] } // startMin is minutes from local midnight; startAt is the visit's start, the // UTC instant to book. A day shut or past the booking horizon reads exactly as // it does on GET /availability. ``` ### POST /api/v1/{slug}/visits/book: Book a visit of several services (online source) No authentication required. The customer-facing call for a visit of several services, exactly as the booking page books one: the whole visit or none of it, in one transaction, each service an appointment of its own with its person, time and price, sharing one visitId. The client gets one confirmation listing every service, one discount shared across the services, and, at a business that approves online bookings, one request (approvalRequested). Only at a business that lets clients book several services in one visit (else 409 not_offered, nothing booked); the services must be ones it offers online, and its combination rules hold. Like POST /book it takes no key, so it holds to the same rules: startAt is read strictly (TIME_NEEDS_OFFSET, TIME_INVALID), or localTime is sent instead (TIME_DOES_NOT_EXIST, TIME_AMBIGUOUS), an email match changes nothing, a marketing yes waits for the client's own confirmation, a visit that takes a deposit is refused with 409 and code DEPOSIT_NEEDS_BOOKING_PAGE with bookingPageUrl (nothing booked), so is one with a service the business requires a card saved to hold (409, code CARD_REQUIRED_USE_BOOKING_PAGE, with bookingPageUrl), booking terms the business has set must be accepted (acceptTerms: true, else 422 TERMS_NOT_ACCEPTED with the terms to show), the business's booking questions are answered once for the whole visit as answers (a required one without an answer is 422 ANSWERS_REQUIRED with missingQuestionIds, an unreadable answer 422 ANSWERS_INVALID), a paused business answers BOOKING_PAUSED, and the same per-address and per-business caps apply. The appointmentId in the answer is the person's private key to their booking: never show it, store it or put it in a chat. A visit booked at a surcharged time (a public holiday or a busy time the business charges more for) also has priceCents (the visit's total, the surcharge included) and surcharge: { label, amountCents }; a visit without one has neither. To retry safely after a timeout, send an Idempotency-Key header: the same key with the same email and body within 24 hours answers what the first call answered, with idempotentReplay: true and the Idempotent-Replayed header, and books nothing more. A key is never shared between two people, as it is held per email. A replay does not carry manageKey (the client has it in their confirmation email), and carries a note saying so. With no Idempotency-Key, the very same request (the same email and every field the same) sent again within two minutes books nothing more either: it answers 200 with the first booking, idempotentReplay: true and the Idempotent-Replayed header, without manageKey, and with a note saying so. Any other body, or the same one once the first booking is cancelled, books as normal. Still send an Idempotency-Key when you retry: it holds for 24 hours, not two minutes. No authentication required. Parameters: - serviceIds (body, required): Two to four different services from GET /services, in the order they are done (the first one first). - startAt (body, optional): An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00.000Z") or "2026-06-10T21:00:00+12:00", in whole minutes. Read strictly: no offset is a 422 with code TIME_NEEDS_OFFSET and an example on the business's clock; a date that does not exist, seconds other than :00 or anything else is a 422 with code TIME_INVALID. Nothing is booked or moved either way. Send startAt or localTime, exactly one. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. - name (body, required): Customer name, 2 to 80 characters (trimmed). - email (body, required): A valid email address. - phone (body, required): 6 to 30 characters; digits, spaces and + ( ) - only. - notes (body, optional): Free text, max 500 characters, written on every service of the visit. - marketingConsent (body, optional): Only when the customer agreed to get marketing email from this business: { source, wording }, as on POST /book. Omit when they did not: nobody is opted in by default. - staffId (body, optional): The team member the client picked, as asked of GET /visits/availability: they do every service they do. Omit for anyone. - addOnIds (body, optional): Extras for the first service (ids from its addOns), up to 20, held to the business's combination rules. - locationId (body, optional): One of this business's branches. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected. - acceptTerms (body, optional): true once the person has read and accepted the business's booking terms. Required, as true, while the business has set terms: without it the answer is 422 with code TERMS_NOT_ACCEPTED and terms ({ text, version }) to show them, and nothing is booked. Show terms.text as plain text. A business with no terms never asks, and ignores it. - termsVersion (body, optional): The terms.version the person was shown (the SHA-256 of the text). When sent and it is not the version in force (the business changed its terms meanwhile), the answer is the same 422 TERMS_NOT_ACCEPTED with the terms in force, so they are shown again. - answers (body, optional): The person's answers to the business's booking questions, as { [questionId]: answer }, the questions GET /services lists on each service (questions). A string for text (up to 300 characters), textarea (up to 2000), radio (one of its options), number (a plain decimal) and date (YYYY-MM-DD); a list of its options for checkboxes; true or false for yes_no. Every required question must be answered: else the answer is 422 with code ANSWERS_REQUIRED and missingQuestionIds, and nothing is booked. An answer that cannot be read is 422 with code ANSWERS_INVALID and invalidAnswers ({ [questionId]: too_long | not_an_option | not_a_number | not_a_date | not_yes_or_no | bad_value }). An answer to a question the booking does not ask is ignored. The answers are kept for the business only: never echoed back, never in a webhook. A business with no questions never asks, and ignores it. - clientTimeZone (body, optional): The client's own time zone, the IANA zone of a place (America/Toronto), kept on the booking so their emails and pages show their clock too; the answer's when gives the time on both clocks. Abbreviations (EST, which would be read as Panama), offsets (+13:00) and Etc/ zones are refused with code UNKNOWN_TIME_ZONE (422, nothing booked): ask the person which city they are in. Never guessed from the request. - Idempotency-Key (header, optional): Optional. 16 to 64 visible characters, a new one for each booking the person makes and the same one when you send that booking again (after a timeout, say). A retry with the same key, email and body within 24 hours answers what the first call answered, with idempotentReplay: true, and books nothing more. Browsers may send it (CORS allows it). Errors: - 400: The request body is not valid JSON. - 404: No business exists for the {slug}. - 409: Nothing was booked, and code says why: not_offered (the business books one service at a time online), cant_combine: these services cannot be one visit, with reason (repeated, unavailable: not offered online, add_on: an extra, class, video, team: a service two or more people do at once) or, when it is one of the business's combination rules, error naming the two ("4 braids and 6 braids can't be booked together.") and combo { kind, first, second }, no_longer_fits (the whole visit does not fit at that start; line is the service that does not, 0 for the first), taken (someone took it in the moment since it was checked), DEPOSIT_NEEDS_BOOKING_PAGE (the visit takes a deposit, which only the booking page at bookingPageUrl can take), CARD_REQUIRED_USE_BOOKING_PAGE (the business requires a card saved to hold it, which only the booking page at bookingPageUrl can do) or BOOKING_PAUSED (the business is not taking online bookings right now). - 422: Validation failed: fieldErrors names each field (serviceIds, startAt, name, email, phone, marketingConsent). A startAt with no offset has code TIME_NEEDS_OFFSET and an example in the business's zone; one that is not a real RFC 3339 date-time on a whole minute has code TIME_INVALID. At a business with booking terms, a visit without acceptTerms: true (or with a termsVersion that is not the one in force) has code TERMS_NOT_ACCEPTED and terms { text, version } to show. At a business with booking questions, a required question left without an answer has code ANSWERS_REQUIRED and missingQuestionIds (the ids, in the order asked); an answer that cannot be read has code ANSWERS_INVALID and invalidAnswers. Nothing is booked. - 422: code NOT_ON_TEAM at fieldErrors.staffId: the staffId is not on the business's team ("That person isn't on your team. Choose someone who is, or Any available."). Pick a staffId from GET /staff, or leave it out for anyone free. Nothing is booked. - 429: Too many booking attempts (the same caps as POST /book: per address, and per business a day). The response carries Retry-After. - 400: IDEMPOTENCY_MISMATCH: the Idempotency-Key is not 16 to 64 visible characters, or it was used with the same email for a different booking in the last 24 hours. Send a new key. Nothing was booked. - 409: IDEMPOTENCY_IN_PROGRESS: the first request with this Idempotency-Key is still running. Try again after Retry-After. - 409: BOOKING_IN_PROGRESS: with no Idempotency-Key, the same booking was sent a moment ago and is still being made. Wait retryAfterSec seconds (the Retry-After header says the same), then send it again: it answers the first booking. - 500: Unexpected server error (details are never leaked). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/visits/book \ -H "Content-Type: application/json" \ -d '{ "serviceIds": ["svc_colour", "svc_cut"], "startAt": "2026-06-09T21:00:00.000Z", "name": "Alex Smith", "email": "alex@example.com", "phone": "+64 21 555 0100" }' ``` Example response: ``` { "ok": true, "visitId": "vis_abc123", "ref": "MV-7QK2M9", "appointmentId": "apt_colour", "status": "confirmed", "needsPayment": false, "services": [ { "appointmentId": "apt_colour", "ref": "MV-7QK2M9", "serviceId": "svc_colour", "serviceName": "Colour", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T21:00:00.000Z", "endAt": "2026-06-09T22:30:00.000Z", "durationMin": 90, "priceCents": 12000, "status": "confirmed" }, { "appointmentId": "apt_cut", "ref": "MV-8RL3N4", "serviceId": "svc_cut", "serviceName": "Cut", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T22:30:00.000Z", "endAt": "2026-06-09T23:00:00.000Z", "durationMin": 30, "priceCents": 3500, "status": "confirmed" } ] } // At a business that approves online bookings, status is "pending" and // approvalRequested is true until it answers. appointmentId and ref are the // visit's first service, which its confirmation and manage link speak through. // A visit that takes a deposit is refused (409, code DEPOSIT_NEEDS_BOOKING_PAGE, // with bookingPageUrl) and nothing is booked, as is one the business requires // a card saved to hold (409, code CARD_REQUIRED_USE_BOOKING_PAGE, with // bookingPageUrl). At a business with booking terms, a visit without // acceptTerms: true is a 422 with code TERMS_NOT_ACCEPTED and the terms. At a // business with booking questions, a visit without a required answer is a 422 // with code ANSWERS_REQUIRED and missingQuestionIds. ``` ### POST /api/v1/{slug}/visits: Book a visit of several services (the team's) Requires an API key. Needs the bookings:write scope. Book a visit of several services with the business's own key, as the team's New booking form does: each service with the person named for it (or whoever is free), back to back from startAt. The whole visit is booked or none of it, with one confirmation to the client. Every service must fit at its time with its person, its room and its hours, inside the business's opening hours, not in the past and no further ahead than its clients can book, and nobody is ever double-booked. A key made with the opt-in bookings:override scope may book it off the booking grid, past that horizon and over the calendar's busy time, as the team's form does. The visit counts against the key's booking window and the business's day of bookings made through its keys and connected apps; past either the answer is 429 with Retry-After, and nothing is booked. When it does not fit, the 409 says which service (line), when and with whom. The business's combination rules hold, naming the two. A service of the visit that needs two or more kinds of resource at once also has resources: every room, chair or machine it holds, { id, name, kind }, its own room first. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool create_visit. Parameters: - services (body, required): Two to four different services, in the order they are done: [{ serviceId, staffId?, addOnIds? }]. staffId is the team member who does that service (from GET /staff; omit for whoever is free); addOnIds its extras (ids from its addOns on GET /services). - startAt (body, optional): An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00Z"), in whole minutes. A time with no offset is a 422 TIME_NEEDS_OFFSET with an example on the business's clock; a date that does not exist or seconds other than :00 are TIME_INVALID. Send startAt or localTime, exactly one. - name (body, required): Customer name, 2 to 80 characters (trimmed). - email (body, required): A valid email address. - phone (body, required): 6 to 30 characters; digits, spaces and + ( ) - only. - notes (body, optional): Free text, max 500 characters, written on every service of the visit. - marketingConsent (body, optional): Only when the customer agreed to get marketing email from this business: { source, wording }, as on POST /book. Omit when they did not: nobody is opted in by default. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. - locationId (body, optional): One of this business's branches. An id that is not this business's, or names a branch that is currently closed, is ignored rather than rejected. Errors: - 400: The request body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. A key made before scopes that is read-only is refused too. - 404: No business exists for the {slug}. - 409: Nothing was booked, and code says why: cant_combine: these services cannot be one visit, with reason (repeated, unavailable: not offered online, add_on: an extra, class, video, team: a service two or more people do at once) or, when it is one of the business's combination rules, error naming the two ("4 braids and 6 braids can't be booked together.") and combo { kind, first, second }, no_longer_fits (line is the service that does not fit, and error says when and with whom, e.g. "Anna isn't free for Cut at 10:30.") or taken. - 422: Validation failed: fieldErrors names each field (services, startAt, name, email, phone, marketingConsent). - 422: code NOT_ON_TEAM at fieldErrors.staffId: the staffId is not on the business's team ("That person isn't on your team. Choose someone who is, or Any available."). Pick a staffId from GET /staff, or leave it out for anyone free. Nothing is booked. - 429: The key's booking window, or the business's day of bookings through its keys and connected apps, is used up. Retry-After says when to try again. Nothing is booked. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/visits \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "services": [ { "serviceId": "svc_colour", "staffId": "stf_anna" }, { "serviceId": "svc_cut", "staffId": "stf_sam" } ], "startAt": "2026-06-09T21:00:00.000Z", "name": "Alex Smith", "email": "alex@example.com", "phone": "+64 21 555 0100" }' ``` Example response: ``` { "ok": true, "visitId": "vis_abc123", "ref": "MV-7QK2M9", "appointmentId": "apt_colour", "status": "confirmed", "needsPayment": false, "services": [ { "appointmentId": "apt_colour", "ref": "MV-7QK2M9", "serviceId": "svc_colour", "serviceName": "Colour", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T21:00:00.000Z", "endAt": "2026-06-09T22:30:00.000Z", "durationMin": 90, "priceCents": 12000, "status": "confirmed" }, { "appointmentId": "apt_cut", "ref": "MV-8RL3N4", "serviceId": "svc_cut", "serviceName": "Cut", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T22:30:00.000Z", "endAt": "2026-06-09T23:00:00.000Z", "durationMin": 30, "priceCents": 3500, "status": "confirmed" } ] } // The same shape as POST /visits/book. A team booking takes no online deposit. ``` ### GET /api/v1/{slug}/visits/{id}: Get one visit Requires an API key. Needs the bookings:read scope. One visit of several services, scoped to the key's business: its services in order, each with its booking (appointmentId, ref), who does it, when, its price and status, and the visit's start, end, length and price (of the services not cancelled). appointmentId and ref are the service the visit speaks through: its first, or its first still on. A booking's visitId (GET /appointments) names its visit. The client comes by id. A service of the visit that needs two or more kinds of resource at once also has resources: every room, chair or machine it holds, { id, name, kind }, its own room first. A visit booked with a surcharge also has surcharge: { label, amountCents }, part of priceCents. Requires an API key with bookings:read. The person who made the key must still have "See everyone's calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). The same as the MCP tool get_visit. Parameters: - id (path, required): The visit id (vis_…): a booking's visitId, or POST /visits's. Errors: - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:read scope (the body names it as missingScope), or its maker can no longer do what the scope needs. - 404: No business exists for the {slug}, or no visit with that id in this business (the same 404 either way). - 500: Unexpected server error (details are never leaked). Example request: ``` curl https://bookatu.com/api/v1/maison-vera/visits/vis_abc123 \ -H "Authorization: Bearer bk_live_YOUR_KEY" ``` Example response: ``` { "id": "vis_abc123", "appointmentId": "apt_colour", "ref": "MV-7QK2M9", "status": "confirmed", "customerId": "cus_xyz", "startAt": "2026-06-09T21:00:00.000Z", "endAt": "2026-06-09T23:00:00.000Z", "durationMin": 120, "priceCents": 15500, "services": [ { "appointmentId": "apt_colour", "ref": "MV-7QK2M9", "serviceId": "svc_colour", "serviceName": "Colour", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T21:00:00.000Z", "endAt": "2026-06-09T22:30:00.000Z", "durationMin": 90, "priceCents": 12000, "status": "confirmed" }, { "appointmentId": "apt_cut", "ref": "MV-8RL3N4", "serviceId": "svc_cut", "serviceName": "Cut", "staffId": "stf_anna", "staffName": "Anna", "startAt": "2026-06-09T22:30:00.000Z", "endAt": "2026-06-09T23:00:00.000Z", "durationMin": 30, "priceCents": 3500, "status": "confirmed" } ] } ``` ### POST /api/v1/{slug}/visits/{id}/reschedule: Move a whole visit Requires an API key. Needs the bookings:write scope. Move a visit of several services so it starts at startAt: every service keeps its person, its length and its place in the order, and is checked again at its new time as the team's own calendar checks it (it may start off the booking grid and past the online horizon, but it must fit with every person, room and the hours). All of them move or none does; nothing is ever double-booked. The client is told once, the reminders follow the new times, each old time is offered to the waitlist, and each service fires booking.rescheduled. The answer is the visit as GET /visits/{id} now reads it, with the resources each service needing two or more kinds now holds, and when, its new start as a When. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool reschedule_visit. Parameters: - id (path, required): The visit id. - startAt (body, optional): An instant with its offset (RFC 3339), such as a startAt from GET /availability ("2026-06-10T09:00:00Z"), in whole minutes. A time with no offset is a 422 TIME_NEEDS_OFFSET with an example on the business's clock; a date that does not exist or seconds other than :00 are TIME_INVALID. Send startAt or localTime, exactly one. - localTime (body, optional): Instead of startAt: a wall-clock time with no offset ("2026-11-04T09:00"), read on the business's clock (the branch's, at a branch) or on timeZone. A time the clocks skip that day is a 422 TIME_DOES_NOT_EXIST with nextValid, one they show twice a 422 TIME_AMBIGUOUS with both candidates (as When objects): resend startAt with the offset meant. - timeZone (body, optional): With localTime only: the IANA zone of a place it is on (America/Toronto). Abbreviations, offsets and Etc/ zones are a 422 UNKNOWN_TIME_ZONE. Errors: - 400: The request body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. A key made before scopes that is read-only is refused too. - 404: No business exists for the {slug}, or no visit with that id in this business. - 409: The whole visit does not fit at that start (error says so, and nothing moved), or every service of it is cancelled, finished or a no-show. - 422: startAt is missing, is not a parseable ISO 8601 date-time, or is in the past (fieldErrors.startAt). - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/visits/vis_abc123/reschedule \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "startAt": "2026-06-11T01:00:00.000Z" }' ``` Example response: ``` { "ok": true, "visit": { "id": "vis_abc123", "startAt": "2026-06-11T01:00:00.000Z", "endAt": "2026-06-11T03:00:00.000Z", "services": [ ... ] } } ``` ### POST /api/v1/{slug}/visits/{id}/cancel: Cancel a whole visit Requires an API key. Needs the bookings:write scope. Cancel every service of a visit still on, as the business. Its first service is cancelled as any booking is (the deposit it holds refunded or kept by the business's notice policy: forfeited says which; refundDeposit: true refunds it anyway), the rest go with it, the client is told, each freed time is offered to the waitlist and each service fires booking.cancelled. cancelled is how many services were cancelled. Cancelling a visit already cancelled is idempotent (alreadyCancelled: true). A key that cancels many in a few minutes is stopped for a while (429) and the owner is told. Requires an API key with bookings:write. The person who made the key must still have "Edit the calendar" on the business's Roles & permissions, as on the tool's own screen, a key made before scopes included; if they lost it, or left the team, it is refused (403, MAKER_LACKS_PERMISSION or MAKER_NOT_ON_TEAM). A booking outside the column of a key's maker who cannot see everyone's calendar is answered as one the business does not have, and nothing is done. Send dryRun: true in the body (or ?dryRun=true) to see the record it touches, who is told and what would change, with nothing changed. Send an Idempotency-Key header (1 to 200 characters) to retry safely: the same key with the same request within 24 hours answers what the first call answered, with Idempotent-Replayed: true, and does nothing again; the same key with another request is refused (409, IDEMPOTENCY_KEY_REUSED). Recorded in the audit log, marked as made through the API. The same as the MCP tool cancel_visit. Parameters: - id (path, required): The visit id. - reason (body, optional): Optional reason, up to 200 characters, stored on each service. - refundDeposit (body, optional): Optional. true refunds a paid deposit whatever the notice policy says. Left out, the policy decides. Errors: - 400: The request body is not valid JSON. - 401: The API key is missing or invalid. - 403: The key belongs to a different organisation, or it lacks the bookings:write scope (the body names it as missingScope), or its maker can no longer do what the scope needs. A key made before scopes that is read-only is refused too. - 404: No business exists for the {slug}, or no visit with that id in this business. - 409: The visit could not be cancelled (error says why). - 422: refundDeposit is not true or false (fieldErrors.refundDeposit). Nothing is cancelled. - 429: The key cancelled too many bookings in a short time. Retry-After says when to try again. Nothing is cancelled. - 500: Unexpected server error (details are never leaked). - 409: The Idempotency-Key was used with another request (IDEMPOTENCY_KEY_REUSED), or the first call with it is still running (IDEMPOTENCY_IN_PROGRESS). Example request: ``` curl -X POST https://bookatu.com/api/v1/maison-vera/visits/vis_abc123/cancel \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "reason": "Client rang" }' ``` Example response: ``` { "ok": true, "visitId": "vis_abc123", "cancelled": 2, "forfeited": false } // Again: { "ok": true, "visitId": "vis_abc123", "cancelled": 0, "alreadyCancelled": true, "forfeited": false } ``` Machine-readable spec: https://bookatu.com/api/openapi.json. Human documentation with examples: https://bookatu.com/en-nz/developers ## Check out from another point of sale (Moneris MGR) A business that takes payment on another point of sale, such as Moneris MGR, can start checkout from a Bookatu booking and post the sale back, so nobody rings up the visit twice and the booking, the sale, who did the work and the money all line up in Bookatu as if its own point of sale had taken it. 1. Make an API key with the checkout scopes ticked (See what a booking comes to at checkout, and Check bookings out from another point of sale), and See bookings so your point of sale can list the day's bookings with GET /appointments. Add See clients if your point of sale should get the client's name and contact details. 2. When a client comes to pay, start checkout from their booking: read GET /appointments/{id}/checkout and ring up its lines. Each line is the service or an extra at its booked price and discount, with who did it, and dueCents is exactly what to take (tax added on top included, the deposit already taken off). 3. Take the money on your terminal, then POST the sale to the same address with your own sale id as externalSaleId. Bookatu checks the booking out with the same code its own point of sale uses. Retrying with the same externalSaleId is always safe. 4. Subscribe a webhook endpoint to booking.checked_out to hear about every checkout, including the ones taken at Bookatu's own point of sale, so your point of sale never takes the same visit twice. ## Visits of several services A client can book several services in one visit, one straight after another (a colour, then a cut), with the same person or different people. Each service is a booking of its own, sharing a visitId, and the visit is one thing to the client: booked all or nothing, with one confirmation, one deposit and one manage link. 1. Read GET /business: visits is there, with the most services one visit takes, when the business lets clients book several services in one visit. GET /services says which services go together: combinations.onlyWith lists the only other services a service shares a visit with, and combinations.neverWith the ones it is never booked with (a 4 braids and a 6 braids, say). 2. Ask GET /visits/availability with the services in order (serviceIds), and the team member the client picked if they picked one. Each slot lists every service with who does it and when, back to back. 3. Book a slot's startAt with POST /visits/book and the same services. The business's own key books a visit with POST /visits instead, naming each service's person, within the business's open hours and booking horizon. 4. Read, move and cancel the whole visit with GET /visits/{id}, POST /visits/{id}/reschedule and POST /visits/{id}/cancel; each booking's visitId on GET /appointments names its visit. The client's own /booking/{id} calls move and cancel the whole visit too, from any of its services. Over MCP, the same is get_visit_availability, create_visit, get_visit, reschedule_visit and cancel_visit. ## Rooms and equipment A business sets up its rooms, chairs and machines as resources, each of a kind (Room, Laser). A service can need one kind, which a booking of it holds as its room, or two or more kinds at once: a laser facial needs a treatment room and a laser machine. The booking engine offers a time only when a person and one free resource of each kind are free together, holds each of them for the booking's whole length, and never books one resource twice. 1. Read GET /services: a service that needs two or more kinds lists them as resourceKinds, in order (for example ["Room", "Laser"]); the first is the kind of the booking's own room. A service that needs one kind or none has no resourceKinds. Over MCP, list_services says the same. 2. Ask GET /availability as for any service: every slot it returns has one free resource of each kind, and its resourceIds are the free ones of the first kind. Book a slot's startAt with POST /book, or with POST /appointments and the business's key; resourceId prefers one of those, and the engine gives one free resource of each other kind. 3. Read what a booking holds on GET /appointments and GET /appointments/{id}, or over MCP with list_appointments: resources lists every room, chair or machine it holds, { id, name, kind }, its own room first. POST /appointments answers with it too, and each service of a visit has it on POST /visits, GET /visits/{id} (get_visit) and POST /visits/{id}/reschedule. 4. Moving a booking through the API (POST /booking/{id}/reschedule or MCP reschedule_booking) keeps each of its resources where it is still free and gives another of the same kind where it is not; moving a whole visit (POST /visits/{id}/reschedule) gives each of its services a free one of each kind. A time with none of a kind free is refused and nothing changes. Cancelling frees them all. Webhook payloads are unchanged: read the booking with your key to see what it holds. ## Webhooks Each delivery is signed with HMAC-SHA256 over the string "{timestamp}.{rawBody}", hex-encoded. Verify it before trusting the body. Events: - booking.created: A booking is created (online, admin or via the API). - booking.cancelled: A booking is cancelled (by staff, the customer, or the API). - booking.completed: A booking is marked complete after the visit. - booking.rescheduled: A booking is moved to a new time (startAt is the new time). - order.paid: A shop order is paid (fires once per order; the buyer's contact details are never in the payload). - form.submitted: A client completes an intake / consent form (fires once per response; answers and signature never leave the admin dashboard). - campaign.sent: An email campaign finishes sending (from the dashboard or the scheduler; recipient addresses are never in the payload). audience is the segment it went to: all, recent, lapsed, vip, or tag for a "Clients tagged" audience, which never says which tag (tags are the team's internal labels). - booking.checked_out: A booking is checked out, at Bookatu's own point of sale or by another point of sale through POST /appointments/{id}/checkout, with the sale that closed it. Sent only to an endpoint that asks for it by name: an endpoint taking all events never gets it. Same payload as GET /appointments/{id}/checkout, the client by id only. Delivery: Up to 3 attempts at once, 500ms then 1000ms apart. If all of them fail, the delivery is queued and tried up to 10 more times: the first within a few minutes, then with the gap doubling from about a minute, so the last try comes several hours after the event. After that it is given up. A test business's deliveries are retried fewer times. Every retry sends the same body with the same id. A queued retry is signed with the time it is sent. A delivery succeeds on any 2xx response; non-2xx responses, timeouts and network errors are retried. Each attempt times out after 4 seconds. Redirects are not followed (redirect: error). Endpoints must be public https URLs: localhost, .local / .internal / .localhost hosts and private, reserved, loopback and cloud-metadata IP ranges are rejected (SSRF protection), both when the endpoint is saved and again at send time. Privacy: Payloads carry no customer contact details. Booking events name the client (customerId), who does it (staffId, null when nobody is assigned) and the branch (locationId, null for a business with one address) by id only. Fetch the full record from GET /appointments with your API key when you need more. Headers on every delivery: - X-Bookatu-Event: The event name, e.g. booking.created. - X-Bookatu-Event-Id: The event's id (evt_...), the same as id in the body. It is the same on every attempt of one event, so use it to skip a delivery you already handled. - X-Bookatu-Signature: t={unixSeconds},v1={hmacSha256Hex}. Use t when recomputing the signature. - X-Bookatu-Attempt: Delivery attempt number, 1 to 13. The queued retries carry on counting from the first attempts. - User-Agent: Bookatu-Webhooks/1 - Content-Type: application/json The endpoint secret is shown once when the endpoint is created and starts with whsec_. Verify every delivery: recompute the signature over {timestamp}.{rawBody} and compare it, in a timing-safe way, to the v1 value in X-Bookatu-Signature. ```js import crypto from "node:crypto"; // rawBody is the exact bytes you received (do not re-serialize). // secret is your endpoint secret (whsec_...). // t comes from the X-Bookatu-Signature header: "t=,v1=". function verify(rawBody, t, v1, secret) { const expected = crypto .createHmac("sha256", secret) .update(`${t}.${rawBody}`) .digest("hex"); const a = Buffer.from(expected); const b = Buffer.from(String(v1)); // timingSafeEqual throws on buffers of different lengths: refuse those. return a.length === b.length && crypto.timingSafeEqual(a, b); } ``` Payloads: booking.created: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.created", "sentAt": "2026-06-01T03:12:00.000Z", "data": { "id": "apt_abc123", "ref": "MV-7QK2M9", "service": "Gel Manicure", "startAt": "2026-06-10T21:00:00.000Z", "durationMin": 60, "priceCents": 7500, "status": "pending", "staffId": "stf_sam", "customerId": "cus_xyz", "locationId": null } } ``` booking.cancelled: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.cancelled", "sentAt": "2026-06-02T09:30:00.000Z", "data": { "id": "apt_abc123", "ref": "MV-7QK2M9", "service": "Gel Manicure", "startAt": "2026-06-10T21:00:00.000Z", "status": "cancelled", "staffId": "stf_sam", "customerId": "cus_xyz", "locationId": null } } ``` booking.completed: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.completed", "sentAt": "2026-06-10T23:05:00.000Z", "data": { "id": "apt_abc123", "ref": "MV-7QK2M9", "service": "Gel Manicure", "startAt": "2026-06-10T21:00:00.000Z", "status": "completed", "staffId": "stf_sam", "customerId": "cus_xyz", "locationId": null } } ``` booking.rescheduled: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.rescheduled", "sentAt": "2026-06-03T11:00:00.000Z", "data": { "id": "apt_abc123", "ref": "MV-7QK2M9", "service": "Gel Manicure", "startAt": "2026-06-12T21:00:00.000Z", "status": "confirmed", "staffId": "stf_sam", "customerId": "cus_xyz", "locationId": null } } ``` order.paid: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "order.paid", "sentAt": "2026-06-04T02:20:00.000Z", "data": { "id": "ord_abc123", "description": "2 items", "amountCents": 5400, "currency": "nzd", "items": [ { "productId": "prd_a1", "product": "Repair Shampoo", "quantity": 1 }, { "productId": "prd_b2", "product": "Leave-in Conditioner", "quantity": 1 } ] } } ``` form.submitted: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "form.submitted", "sentAt": "2026-06-05T20:41:00.000Z", "data": { "formId": "frm_abc123", "formName": "New client intake", "responseId": "frs_def456", "customerId": "cus_ghi789", "appointmentId": "apt_jkl012" } } ``` campaign.sent: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "campaign.sent", "sentAt": "2026-06-06T09:00:00.000Z", "data": { "campaignId": "cmp_abc123", "subject": "Winter offers are live", "audience": "recent", "sent": 182, "recipients": 187 } } ``` booking.checked_out: ``` { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.checked_out", "sentAt": "2026-06-10T22:12:01.000Z", "data": { "version": 1, "appointment": { "id": "apt_abc123", "ref": "MV-7QK2M9", "status": "completed", "startAt": "2026-06-10T21:00:00.000Z", "endAt": "2026-06-10T22:10:00.000Z", "serviceName": "Cut", "customerId": "cus_xyz", "staffId": "stf_sam", "source": "online", "visitId": null }, "customer": { "id": "cus_xyz" }, "staff": { "id": "stf_sam", "name": "Sam" }, "currency": "CAD", "lines": [ { "lineId": "apt_abc123:service", "kind": "service", "appointmentId": "apt_abc123", "label": "Cut", "qty": 1, "unitCents": 4000, "discountCents": 400, "totalCents": 3600, "taxCents": 432, "serviceId": "svc_cut", "staffId": "stf_sam", "staffName": "Sam" } ], "subtotalCents": 4000, "discountCents": 400, "totalCents": 3600, "tax": { "mode": "added", "taxCents": 432, "lines": [{ "rateId": "gst", "label": "GST", "rateMilli": 5000, "taxCents": 180 }, { "rateId": "pst", "label": "PST", "rateMilli": 7000, "taxCents": 252 }] }, "depositPaidCents": 2000, "dueCents": 0, "checkout": { "allowed": false, "blocked": "already_checked_out" }, "sale": { "id": "sale_x1y2z3", "receipt": "X1Y2Z3", "at": "2026-06-10T22:12:00.000Z", "source": "moneris_mgr", "externalSaleId": "MGR-000123", "method": "Card", "tender": "card", "collectedCents": 2032, "saleTotalCents": 2032, "tipCents": 500, "products": [] } } } ``` ## MCP server for AI agents Endpoint: POST https://bookatu.com/api/mcp (MCP over JSON-RPC 2.0). Authenticate with the same API keys as the REST API ("Authorization: Bearer bk_live_YOUR_KEY" or "X-Api-Key: bk_live_YOUR_KEY"), or via OAuth 2.1 with PKCE (used by MCP clients like Claude's custom connector; discovery at https://bookatu.com/.well-known/oauth-authorization-server). Every call is automatically scoped to one business. Every tool but the help tools needs one scope (bookings:read, customers:read, reports:read, catalog:write, ...): a key can only call the tools of its scopes, tools/list shows only those, and anything else returns 403 naming the scope it needed. The help tools (whoami, search, how_do_i, open_in_bookatu, get_help, get_approval) need no scope, and any key of the business may call them. Keys made before scopes keep their access level: read tools work with any of them; write tools need a read-write key; the tools of the opt-in scopes (get_audit_log, get_checkout, sell_product, create_customer, update_customer, add_customer_note, create_announcement, get_client_messages, set_client_messages, list_held_client_messages, send_held_client_message, release_held_enquiry) need a key made with those scopes ticked. There are deliberately no delete tools: removing data stays a human action in the admin dashboard. A sandbox (a test business a developer makes) also lists these tools, never a live business: sandbox_outbox, sandbox_payments, sandbox_simulate, sandbox_reset; sandbox_reset wipes the sandbox's made-up data and seeds it again, with its own test key only. Every successful tool result says livemode in structuredContent (false at a sandbox), and every tool result, a refusal included, in result._meta["com.bookatu/livemode"]. See https://bookatu.com/developers/testing-ai-agents.md. Errors and retries. For a client that sends a 2025 MCP-Protocol-Version header (2025-03-26 or later), a refusal the agent can act on, such as a slot that was just taken, comes back as a tool result with isError: true and error.code. So do arguments a tool cannot read: the code is INVALID_PARAMS, with fieldErrors naming each argument and what is wrong with it, so the model can correct them and call again. A client that sends no such header gets the JSON-RPC error it always did, -32602 for bad arguments. A missing scope, a read-only credential, a rate limit and an unknown tool stay JSON-RPC errors whatever the version. Every write tool says idempotentHint: true on the ones that change nothing more when called again with the same arguments (cancel_booking is one; a second call may answer that it was already done), false on the rest. To retry any write safely after a timeout, send the same idempotencyKey. Loading fewer tools. Add toolsets to the server's address, for example /api/mcp?toolsets=booking,classes, to load only those tool families, so the agent reads a shorter list. The toolsets are the family ids: booking, commerce, blog, forms, campaigns, storefront, reports, webhooks, classes, audit and help. The help tools and get_business come with every set, so toolsets=help alone loads only those. Only those tools are listed by tools/list and callable by tools/call; a call to any other answers the unknown-tool error, -32601, with data.code NOT_IN_TOOLSET and the family it is in. A toolset only narrows: the key's scopes still decide what the connection reaches. A name that is not a toolset is refused with -32602, naming the valid ones. With no toolsets, every tool the key's scopes allow is loaded, as before, and whoami says which toolsets a connection loaded. ### Booking and clients Services, open slots, bookings, customers and upcoming appointments. - list_services: List all active bookable services, each with the extras offered with it (addOns) at a business that has extras, its combination rules (combinations: onlyWith, neverWith) when it has any, how many people it needs at once (peopleNeeded) when that is more than one, and the kinds of resource it needs at once (resourceKinds) when that is two or more, and the booking questions it asks (questions, in the order asked, as GET /services lists them) at a business that asks any, and how clients meet you for it (meetingType) and the notice a booking of it needs (noticeHours). Scope: catalog:read. - get_availability: Get open slots for a service over a date range (max 60 days), with durationMin, how long each slot is. Optional addOnIds asks for the longer booking when an extra adds its time. Each slot also has local, its start with the offset in force on its own date on the one timeZone the answer names, and clientLocal on clientTimeZone when that is given. A slot a surcharge covers (a public holiday or a busy time the business charges more for) also has priceCents, surcharges (label, amountType, amount, amountCents) and totalCents, the price at that time, to show the client before they book; other slots have none of these. A from or to that is a date that does not exist, such as 30 February, or one too far away, is refused as Invalid params (-32602) in the words GET /availability uses ("Use a real date in YYYY-MM-DD format.", "Ask for dates in the next few years."). Scope: availability:read. - create_booking: Book an appointment for a customer; returns a ref. A service that takes a deposit is refused with DEPOSIT_NEEDS_BOOKING_PAGE and bookingPageUrl (the business's booking page, where the customer books it and pays the deposit), and nothing is booked. Optional repeat ({ everyDays | monthly, visits }) books a series, each repeat checked and a clash left out and listed. Optional marketingConsent ({ source, wording }) only when the customer agreed to marketing email; without it they are not opted in. Optional addOnIds adds extras, refused with the reason when the service does not take one. Optional clientTimeZone (a place's IANA zone) is kept on the booking. Optional answers ({ questionId: answer }) answers the business's booking questions (list_services lists them on each service), read exactly as answers on POST /book: a required question left out is refused with ANSWERS_REQUIRED and missingQuestionIds, an answer that cannot be read with ANSWERS_INVALID and invalidAnswers, and nothing is booked; ask the person and send their answers, or send them to bookingPageUrl. The answers are never echoed back or sent in a webhook. The time is startAt with its offset, or localTime ("2026-11-04T09:00") on the business's clock or a named timeZone; a time with no offset is refused with TIME_NEEDS_OFFSET, one the clocks skip with TIME_DOES_NOT_EXIST (and nextValid), one they show twice with TIME_AMBIGUOUS (and both candidates). The answer's when is the booked start as a When, on the business's clock and, when their zone is known, the client's. Optional asStaff: true books as the team does, for the business's own assistant through a key or app whose maker may Edit the calendar: a service that takes a deposit is booked and never held for one, and a time that is not free is still refused. Requires a read-write key. Scope: bookings:write. - list_customers: List all customers in the org. Scope: customers:read. - list_appointments: List upcoming pending and confirmed appointments. Returns each booking's id for reschedule_booking and cancel_booking, its visitId when it is one service of a visit (get_visit), additionalStaffIds when two or more of the team do it at once, and resources (every room, chair or machine it holds, { id, name, kind }) when its service needs two or more kinds of resource at once. A booking whose client asked to swap out of a late cancellation (Quick swap) has swap: { status (requested, claimed, withdrawn or expired), requestedAt, cutoffAt, closedAt, claimedAppointmentId }. Times also come as timeZone plus start and end When objects, with the offset in force at each instant. Scope: bookings:read. - list_staff: List the bookable team members: id, name, title, active and bookable. Scope: staff:read. - reschedule_booking: Move a booking to a new time, and optionally to a different team member. The new time is re-checked exactly as a client's own reschedule is, so a time that is not free is refused rather than double-booked. The time is startAt with its offset, or localTime ("2026-11-04T09:00") on the business's clock or a named timeZone; a time with no offset is refused with TIME_NEEDS_OFFSET, one the clocks skip with TIME_DOES_NOT_EXIST (and nextValid), one they show twice with TIME_AMBIGUOUS (and both candidates). The answer's when is the booked start as a When, on the business's clock and, when their zone is known, the client's. Requires a read-write key. Scope: bookings:write. - cancel_booking: Cancel a booking, as the business. The slot goes back on offer and the client is sent no message about it; the reply says whether a paid deposit was kept under the business's notice policy (refundDeposit: true refunds it anyway). Requires a read-write key. Scope: bookings:write. - create_service: Add a standard bookable service (duration in minutes, prices in dollars), with how clients meet you for it (meetingType) and its own notice to cancel or change (noticeHours) when you send them. A new service is never a trip, so a destination or an itinerary is refused. Requires a read-write key. Scope: catalog:write. - update_service: Update only the provided fields of a service; null clears meetingType, noticeHours, destination or itinerary. A destination and an itinerary are only for a trip (a service that lasts whole days), never more days than it lasts. Requires a read-write key. Scope: catalog:write. - list_booking_requests: List the booking requests waiting for the business's answer (a new online booking, or a client's move of a confirmed one), oldest first, each with when it lapses, and resources when its service needs two or more kinds of resource at once. The client by id; their name and contact details only with customers:read. Times also come as timeZone plus start and end When objects, with the offset in force at each instant. A move's asked-for time is requestedStart and requestedEnd, and when it lapses is answerBy, as When objects. Scope: bookings:read. - accept_booking_request: Accept a booking request: the booking is confirmed or the move carried out, and the client told unless the business's message settings hold it, as Accept on the Requests list. Answered once. Requires a read-write key. Scope: bookings:write. - decline_booking_request: Decline a booking request, with an optional note for the client: a booking is cancelled as the business (any deposit refunded), a move is dropped. The client's email follows the business's message settings; notifyClient true sends it all the same. Requires a read-write key. Scope: bookings:write. - send_deposit_link: Send the pay link again for a deposit the business asked for on a booking it made; the link before is closed first, so it can never be paid twice. Requires a read-write key. Scope: bookings:write. - stop_deposit_request: Stop asking for the deposit on a booking the business made (the client will pay in person): the link stops working. Requires a read-write key. Scope: bookings:write. - get_checkout: What a booking comes to at checkout, for a point of sale that is not Bookatu's: each line with who did it, price, discount, tax, deposit paid and dueCents; once checked out, the sale that closed it. Only a key made with the checkout:read scope ticked. Read-only. Scope: checkout:read. - get_visit_availability: The starts a visit of several services fits, one after another, with who does each service and when. Only at a business that lets clients book several services in one visit; two services it keeps apart are refused with the reason. Each slot also has local, its start with the offset in force on its own date on the one timeZone the answer names, and clientLocal on clientTimeZone when that is given. The last service's endAt is when the visit ends. A slot a surcharge covers (a public holiday or a busy time the business charges more for) also has priceCents, surcharges (label, amountType, amount, amountCents) and totalCents, the price at that time, to show the client before they book; other slots have none of these. A from or to that is a date that does not exist, such as 30 February, or one too far away, is refused as Invalid params (-32602) in the words GET /visits/availability uses ("Use a real date in YYYY-MM-DD format.", "Ask for dates in the next few years."). Read-only. Scope: availability:read. - create_visit: Book a visit of several services as the booking page does: the whole visit or none of it, one confirmation and, where the business approves online bookings, one request. Only at a business that lets clients book several services in one visit. A visit that takes a deposit is refused with DEPOSIT_NEEDS_BOOKING_PAGE and bookingPageUrl (the business's booking page), and nothing is booked. Optional answers ({ questionId: answer }) answers the business's booking questions (list_services lists them on each service), read exactly as answers on POST /book: a required question left out is refused with ANSWERS_REQUIRED and missingQuestionIds, an answer that cannot be read with ANSWERS_INVALID and invalidAnswers, and nothing is booked; ask the person and send their answers, or send them to bookingPageUrl. The answers are never echoed back or sent in a webhook. Each question is asked once for the whole visit. The time is startAt with its offset, or localTime ("2026-11-04T09:00") on the business's clock or a named timeZone; a time with no offset is refused with TIME_NEEDS_OFFSET, one the clocks skip with TIME_DOES_NOT_EXIST (and nextValid), one they show twice with TIME_AMBIGUOUS (and both candidates). Requires a read-write key. Scope: bookings:write. - get_visit: Read a visit of several services: each service in order with its booking, who does it, when, its price and status (and resources, every room, chair or machine it holds, when it needs two or more kinds at once), and the visit's start, end and total. Read-only. Scope: bookings:read. - reschedule_visit: Move a whole visit to a new start: every service keeps its person and length and is checked again at its new time, so all of them move or none does. The time is startAt with its offset, or localTime ("2026-11-04T09:00") on the business's clock or a named timeZone; a time with no offset is refused with TIME_NEEDS_OFFSET, one the clocks skip with TIME_DOES_NOT_EXIST (and nextValid), one they show twice with TIME_AMBIGUOUS (and both candidates). Requires a read-write key. Scope: bookings:write. - cancel_visit: Cancel every service of a visit still on; the client is told once, and the reply says whether a paid deposit was kept under the business's notice policy (refundDeposit: true refunds it anyway). Requires a read-write key. Scope: bookings:write. - get_business: The business's time zone, the time there now as a When, its weekly opening hours, the next seven days' openings as When ranges with one-off dates applied, closures (one-off dates in the next 90 days and time the whole business is blocked), its branches with their own zones and hours, and its booking policies. A When is { utc, primary, business: { timeZone, local, utcOffset, abbr, display }, client }, with the offset in force at that instant; quote display rather than converting a time yourself. Read-only. Scope: catalog:read. - get_walk_in_wait: The business's walk-in wait now, the same answer as GET /walk-in: worked out from its calendar as a walk-in is served, or set by hand by the team. state is no_wait (the earliest start is within 5 minutes: walk in now), wait (5 to 90 minutes away; waitMin is rounded up to 5), busy (more than 90 minutes away; nextAt says when), full_today (open now, nothing fits before closing), closed (closed now; closed.opensAt says when it opens, null when no opening is in the next 14 days) or not_taking (set by hand). status off (with message) while the business has it turned off, and no numbers then. Counts only, never names. Read-only. Scope: availability:read. - set_walk_in_wait: Set the walk-in wait by hand (minutes 0 to 240, or notTaking), until it expires (1h, 2h or end_of_day; the business's default when left out), as PUT /walk-in/manual does. Refused as WALK_IN_OFF while turned off. Audited. Requires a read-write key. Scope: bookings:write. - clear_walk_in_wait: Back to the automatic walk-in wait now, as DELETE /walk-in/manual does; cleared says whether a wait set by hand was in force. Audited. Requires a read-write key. Scope: bookings:write. - rename_service_category: Rename a service category, or merge it into another: every service in it moves. Answers how many moved. Requires a read-write key. Scope: catalog:write. - block_time: Block time on the calendar for one team member or the whole business, ending no later than the last day clients can book (a longer block is refused with 422; make it on the calendar). A burst of blocks from one key is refused with 429. Requires a read-write key. Scope: bookings:write. - add_booking_note: Add to a booking's internal note, never shown to the client. Requires a read-write key. Scope: bookings:write. - create_customer: Add a client: a name, and an email and phone when given. Never sets marketing consent. Needs customers:manage. Scope: customers:manage. - update_customer: Change a client's name, email, phone or notes. Never changes marketing consent. Needs customers:manage. Scope: customers:manage. - add_customer_note: Add to a client's notes. Needs customers:manage. Scope: customers:manage. - get_client_messages: Which automatic emails and texts the business's clients get: manualOnly ("Only send client messages when we press Send") and each message type with its email and text switches, their defaults and where each is kept. Read-only. Scope: messages:read. - set_client_messages: Turn automatic client emails and texts on or off: manualOnly, and types by key with email and sms true or false. Unknown or fixed types and channels are refused with fieldErrors. Audited. Sending the same again changes nothing. Scope: messages:write. - list_held_client_messages: The client messages the business's switches held back, newest first: key (the switch key PATCH /client-messages takes), type, channel, reason (switched_off or manual_only), when, and the booking and client ids. Never sent later by itself: Send now (POST /client-messages/held/{id}/send) sends one. No addresses or message words. Read-only. Scope: messages:read. - send_held_client_message: Send now on one held client message: it goes by its own channel only, as the team's press, with the switches left as they are. A second call answers alreadySent: true and sends nothing more. Refusals use the Settings page's own words, with a reason: 404 not_found when it is not a held message of this business; 409 in_flight while an earlier press is still sending it; 422 too_late, not_sent (no email or number, or messages off for the client; or a text the text service would not take) or texts_off (the business cannot send this text now); 500 send_failed, to try again. Audited. Scope: messages:write. - list_held_enquiries: The website enquiries held for the business because the key that sent them could not add enquiries any more (its maker is not on the team, or their role lost the right), newest first: the reason, the key it came with, the person's name, email and phone, the trip, dates, people, message and reference. Each is kept 30 days. Read-only. Scope: customers:read. - release_held_enquiry: Move one held website enquiry into Leads, as the website form would have: the same lead and the New enquiry alert, and it is held no more. One whose reference reached Leads since answers duplicate: true and makes no second lead. The person who wrote is not sent anything. Audited. Scope: enquiries:write. ### Products and stock The retail catalog: products, pricing and stock movements, deliveries in and products sold at the point of sale. - list_products: List every retail product in the catalog, active and inactive. Scope: catalog:read. - create_product: Add a retail product (prices in dollars; optional tracked stock with an opening-stock ledger entry). Requires a read-write key. Scope: catalog:write. - update_product: Update only the provided fields of a product; a stock change records a ledger adjustment. Requires a read-write key. Scope: catalog:write. - receive_stock: Record a delivery into a stock-tracked product and log the restock movement. Requires a read-write key. Scope: catalog:write. - bulk_receive_stock: Receive a whole supplier delivery into stock, 1 to 40 lines, all or nothing. Requires a read-write key. Scope: catalog:write. - sell_product: Record a product sold in person: its stock drops and the sale counts at its price. Takes no payment. Needs pos:write. Scope: pos:write. ### Blog The business's public blog: draft, publish, update and unpublish posts. - blog_list_posts: List the business's blog posts (drafts and published), newest first: lean rows without bodies; optional status filter. Scope: content:read. - blog_get_post: Get one blog post in full, markdown body included, by id or slug (drafts visible to the owner). Scope: content:read. - blog_create_post: Write a blog post (markdown body; slug auto-derived and unique per business). Saves a draft unless publish is true. Requires a read-write key. Scope: content:write. - blog_update_post: Update only the provided fields of a post (the slug never changes) and optionally flip its status via an explicit draft/published field. Requires a read-write key. Scope: content:write. - blog_publish_post: Publish a draft post; the first publish stamps publishedAt and a re-publish keeps the original date. Requires a read-write key. Scope: content:write. - blog_unpublish_post: Take a post off the public blog (back to draft), keeping its content and original publish date. Requires a read-write key. Scope: content:write. ### Intake and consent forms Build and manage intake/consent forms and attach them to services. Response listings are summaries only; clients' answers never leave the admin dashboard. - forms_list: List the business's intake / consent forms: lean rows with field, attachment and response counts, never full field schemas; optional active/inactive filter. Scope: content:read. - forms_get: Get one form in full, including its complete field schema and the services it is required before. Scope: content:read. - forms_create: Create an intake / consent form from a hard-validated field schema (the real builder field types; choice fields need 2+ options; bad fields are rejected, never silently dropped). Requires a read-write key. Scope: content:write. - forms_update: Update only the provided parts of a form (a fields array replaces the stored one; active shows/hides it). Service attachment changes go through the attach/detach tools. Requires a read-write key. Scope: content:write. - forms_attach_to_service: Require a form before a service (clients complete it when booking). Both ids must belong to the business; idempotent. Requires a read-write key. Scope: content:write. - forms_detach_from_service: Stop requiring a form before a service. Removes the requirement only; the form and responses stay. Idempotent. Requires a read-write key. Scope: content:write. - forms_list_responses: Summary rows for one form's responses: response id, customer display name and submission time only. Clients' actual answers never leave the admin dashboard (privacy posture). Scope: customers:read. ### Email campaigns (draft only) Draft email campaigns. There is no send or schedule tool; sending stays an owner action in the dashboard. - campaigns_list: List email campaigns (drafts through sent): lean rows with status, audience segment and counts, never bodies. Scope: content:read. - campaigns_get: Get one campaign in full, body markup included. Audiences are segment names; recipient email addresses are never returned. Scope: content:read. - campaigns_create_draft: Draft an email campaign (subject, composer-markup body, audience segment). Saved as a draft and nothing more: there is no send or schedule tool. Sending stays an owner action in the dashboard. Requires a read-write key. Scope: content:write. ### Storefront notices Post a notice on the storefront's What's on board, live at once. Only a key made with the marketing:write scope ticked. - create_announcement: Post a notice on the storefront's What's on board, live at once. Needs marketing:write. Scope: marketing:write. ### Reports Read-only business performance: period reports, ranked findings and weekly capacity, staff earnings and commission, tips, and deposit reconciliation. - get_report: Business performance for a period vs the period before: revenue, bookings, chair time used, revenue per open hour, rebook and no-show rates, with service/staff/category/channel breakdowns. Read-only. Scope: reports:read. - get_findings: Ranked, data-computed findings about the business (severity, headline, detail, suggested action): what the numbers mean, not prose. Read-only. Scope: reports:read. - get_capacity: Chair time by day of week and hour in the business's own timezone: where the week is full and where it is empty. Read-only. Scope: reports:read. - get_earnings: Staff earnings for a date range: each person's visits and products sold, commission under the business's rules, refunds and voids, and tips, by period and line by line. Read-only. Scope: reports:read. - get_tips: Tips for a date range: by person and period, each row of the record, and each tipped sale with its split now. Read-only. Scope: reports:read. - get_deposit_report: Deposit reconciliation for a date range: each deposit taken and what became of it (applied at checkout, kept, refunded, held), with Stripe's record beside it. Read-only. Scope: reports:read. ### Webhooks List, register and disable signed webhook endpoints. Signing secrets are shown once and never returned again. - webhooks_list: List the business's webhook endpoints: url, subscribed events, active flag and last delivery status. Signing secrets are never returned. Scope: webhooks:read. - webhooks_create: Register a public https endpoint to receive signed event POSTs; returns the HMAC signing secret once. Unknown event names are rejected. Requires a read-write key. Scope: webhooks:write. - webhooks_disable: Switch an endpoint off: deliveries stop, the endpoint and its history are kept. No delete tool exists; resuming or removing is an owner action in the dashboard. Requires a read-write key. Scope: webhooks:write. ### Classes Class sessions and their rosters: who holds a place, adding a phone or walk-in client, taking someone off, and marking who came. - list_class_sessions: List the business's class sessions, soonest first, with capacity, enrolledCount and spotsLeft; by default the scheduled ones still to start. At a business with two or more branches, each session also has locationId: the branch it is held at (its own, else its class's, else the main branch); its start and end are on that branch's clock. Times also come as timeZone plus start and end When objects, with the offset in force at each instant. Scope: bookings:read. - get_class_roster: Who holds a place on a class session: each place's enrolmentId, the client's id, status (booked, attended, no_show) and how it was paid. Names and contact details only with customers:read. The session's times as in list_class_sessions. Scope: bookings:read. - add_class_attendee: Put a phone or walk-in client on a class session (matched by email or phone, never opted in to marketing, ticket emailed). A full session stays full. Requires a read-write key. Scope: bookings:write. - cancel_class_place: Take one person off a class session: the spot is freed, what they paid comes back as account credit, they are emailed. Requires a read-write key. Scope: bookings:write. - mark_class_attendance: Mark a place attended, no_show, or back to booked. Requires a read-write key. Scope: bookings:write. ### Audit log Who did what in the business, and when. Only a key made with the audit:read scope ticked. - get_audit_log: The audit log, newest first: who did what and when, and what changed; filter by who, what and dates. Only a key made with the audit:read scope ticked. Read-only. Scope: audit:read. ### Help and finding things Any key of the business, with no scope: who the connection is and what it may do, one search across the business, the steps and the exact screen for any task, the help centre, and where an approval has got to. - whoami: The business, the person the credential is held to and their role, its scopes, livemode, and what never goes through an AI. On a key or connected app Bookatu support set up for the business, person has no id and no email, its name says it is Bookatu's platform owner, role is the role it acts with (owner, or the maker's own role once they join the team), and credential.onBehalfOf names the business. Any key of the business, no scope. Scope: none (any key). - search: One search across clients, bookings, services, products, the team, the dashboard's pages and the help centre, each kind held to the credential's own scopes; results link into the dashboard. Any key of the business. Scope: none (any key). - how_do_i: How to do something in Bookatu: the closest matching admin tasks, each with plain steps, a link to the exact page and card, whether a tool does it, and its help guide. Any key of the business. Scope: none (any key). - open_in_bookatu: The link to a dashboard screen, by task, path, section or tool, with why it is done there (never through an AI, or finished by the person on another site). Any key of the business. Scope: none (any key). - get_help: The help centre's guides for a question, in the business's language, with their screens, and what an AI never does here. Any key of the business. Scope: none (any key). - get_approval: Where a change waiting for a person's approval has got to (pending, approved, declined, used or expired), with the page it is approved on. Needs the approved tool's own scope. Scope: none (any key). ### Sandbox-only tools (test mode) - sandbox_outbox: Test mode only: listed at a sandbox (test) business. Read the sandbox's test outbox: every email, text, WhatsApp message, call and push notification it would have sent to a client or its team, kept and never sent, newest first. The same messages, filters and cursor as GET /api/v1/{slug}/sandbox/outbox: optional channel (email, sms, whatsapp, voice or push), since (an ISO 8601 time), limit (1 to 100, default 50) and cursor (the nextCursor of the page before). Each message has id, channel, kind (such as booking_confirmation or reminder_24h), to, subject, text, html, appointmentId, customerId, createdAt and meta. Use it to check what a client was told after a booking, a change or a cancellation. Needs customers:read. Scope: customers:read. - sandbox_payments: Test mode only: listed at a sandbox (test) business. Read the sandbox's test payments: every simulated payment it made in test mode, newest first, with nothing charged and no money moved. paymentsMode says how its new payments go: simulated, or stripe_test, whose payments are made in Stripe test mode and listed in the business's Finance, not here. kind is checkout (a test checkout: paid, declined, abandoned or open), payment (the payment a paid checkout made: paid, refunded or partly_refunded), card_hold (a card saved for later: card_saved or open), no_show_charge (a no-show or late-cancellation fee charged to a saved test card: paid, declined, refunded or partly_refunded) or refund (refunded). The same payments, filters and cursor as GET /api/v1/{slug}/sandbox/payments: optional kind, since (an ISO 8601 time), limit (1 to 100, default 50) and cursor (the nextCursor of the page before). Each payment has id, kind, outcome, amountCents (null for a card hold), refundedCents, currency, description, appointmentId, belongsTo (the booking or sale it belongs to: type and id), checkoutSessionId, paymentIntentId, createdAt and updatedAt, and never a client's name, email or phone. Use it to check what a test checkout, a refund or a no-show charge did. Needs reports:read. Scope: reports:read. - sandbox_simulate: Test mode only: listed at a sandbox (test) business. Make one event happen now to one of the sandbox's own bookings, through the same code as the real thing: deposit.paid (its open test checkout is paid), payment.failed (the test card is declined and nothing else changes), checkout.expired (the checkout is abandoned and a booking held for its deposit is let go), booking.client_cancelled (the client's own cancellation, under the business's rules), booking.no_show (marked a no-show; a fee the policy sets waits for the owner) or reminders.due (its reminders go out as if their time had come). Takes event and appointmentId (from create_booking or list_appointments). Answers the booking as it is now, the ids of the outbox messages the event kept (read them with sandbox_outbox), the webhook events it sent and what the event reported. A booking of any other business is APPOINTMENT_NOT_FOUND. The same events, refusals and limits as POST /api/v1/{slug}/sandbox/simulate/{event}. Needs bookings:write. Scope: bookings:write. - sandbox_reset: Test mode only: listed at a sandbox (test) business, to its own test key. Wipe the sandbox and fill it with fresh sample data: every booking, client, service and message made since is gone. It keeps its id, slug, test keys, webhook endpoints and connected apps, so this key goes on working. The same reset as POST /api/developer/sandboxes/{id}/reset with the sandbox's test key: only a bk_test_ key of this sandbox with bookings:write, never a connected app. Answers the sandbox: id, slug, name, timezone, currency, createdAt, lastActiveAt, expiresAt, adminUrl, storefrontUrl and apiBaseUrl. Ask the person before you reset. Scope: bookings:write. ### Examples ```sh # Discover tools curl -X POST https://bookatu.com/api/mcp \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' ``` ```sh # Call a tool curl -X POST https://bookatu.com/api/mcp \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "get_availability", "arguments": { "serviceId": "svc_abc123", "from": "2026-06-10", "to": "2026-06-14" } } }' ``` ## Docs MCP server *No key needed* A second MCP server reads Bookatu's own documentation: the help centre, in every language it is translated into, the blog, the engineering blog and these developer docs, and the public plans and prices. It needs no API key and no sign-in, and it can only read, so any MCP client can connect to it. It never sees a business's data. To act on a business, use the MCP server above. **Endpoint** ``` https://bookatu.com/api/mcp/docs ``` | Tool | Description | | --- | --- | | `search_help` | Search the Bookatu help centre, the plain-language guides to every feature, in any of its 14 languages. Returns the guides that match, closest first, with their summary, page, markdown copy and the dashboard screen each is set up on. | | `get_help_article` | Get one help guide in full by its slug: what the feature is, why it helps and the real steps to use it, in the language asked for, with its page and its dashboard screen. | | `search_blog` | Search the Bookatu blog for business owners (a translated post in the language asked for), or the engineering blog with section "engineering". Returns the posts that match, closest first, with their excerpt, date, page and markdown copy. | | `get_blog_post` | Get one blog or engineering post in full by its slug, as markdown, with its author, dates, tags and page. | | `search_developer_docs` | Search the Bookatu developer docs: every REST endpoint, the webhooks and their events, the MCP servers and their tools, and the guides (authentication, CORS, rate limits). Returns the parts that match, closest first, with a short snippet, their place on /developers and the markdown copy. | | `get_plans` | Get what Bookatu costs, as the pricing page states it: each plan's monthly price, billed monthly and billed yearly, how many active clients it covers, the commission, the optional add-ons, the length of the trial and the currency. Takes no arguments. | ```sh # No key needed curl -X POST https://bookatu.com/api/mcp/docs \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "search_help", "arguments": { "query": "how do I take a deposit", "language": "en" } } }' ``` Every answer names the page it came from and its markdown copy, so an agent can cite the page. It is rate limited per IP, like the public REST endpoints. ## Public booking MCP server *No key needed* A public Model Context Protocol (MCP) server for people's own AI assistants. An assistant can look up a business on Bookatu from its booking link, check its free times and hold one, and the person confirms by email. Bookatu never takes payment in a chat. It is for a person's own AI assistant, helping that person book. To act on a business you run, use the MCP server above. It needs no API key and no sign-in, and its name in the initialize handshake is Bookatu Booking. **Endpoint** ``` https://bookatu.com/api/mcp/book ``` **Server card** ``` https://bookatu.com/api/mcp/book/server-card ``` | Tool | Description | | --- | --- | | `get_business` | Use this when a person wants to book with a business on Bookatu and you need its details first. Give the business as its Bookatu name, a bookatu.com link to it, or its own website address. Returns its city and area (never a street address), its time zone and the time there now, this week's opening hours, its branches, its booking policies and whether a time can be held here. Do not use for searching for a business by place or by what it offers. | | `list_services` | Use this when you know the business and the person wants to see what it offers. Returns each service's name, description, length and price, any deposit, and how it is booked: bookVia assistant means a time can be held here, and bookVia website means the person books on the business's own page at bookingPageUrl. Filter with query or category, or pick a branch with locationId. Do not use for health or medical treatments: businesses that offer them are not on this server. | | `check_availability` | Use this when the person has chosen a service and wants to know when it can be done. Returns open times over up to 14 days, each on the business's clock and, when you pass clientTimeZone, on the person's clock too, with the price at that time. A time marked bookVia assistant has a slotId to pass to hold_booking within 30 minutes. Quote times from the display fields as given. Do not use for holding or booking a time: only hold_booking holds one. | | `hold_booking` | Use this when the person has picked a time from check_availability and said yes to its price and the cancellation policy. Holds that time for up to 15 minutes and emails the person, who confirms it with the link in the email or by reading you the 6-digit code from it. Nothing is booked until they confirm. Pass the person's own name and email address, their time zone and an idempotencyKey: a retry with the same key and details returns the same hold. To change a time you already held, release the earlier hold with release_hold first. Do not use for holding a time for someone who has not given you their own email address, or for taking a payment. | | `confirm_booking` | Use this when the person reads you the 6-digit code from the email hold_booking sent them. Books the held time: the answer is confirmed, or requested when the business looks at new bookings before accepting them, with the booking's reference. If someone else took the time first, it offers up to three other times. A wrong code is refused and says how many tries are left. Do not use for a code the person did not give you themselves, or to try codes. | | `get_booking_status` | Use this when the person asks whether a held time was confirmed, or where their booking stands now. Pass the holdId hold_booking returned. Returns the status (such as awaiting_client, confirmed, requested, declined, cancelled or moved), the business and service, and the start time. It returns no personal details. Do not use for checking again and again in a loop; ask when the person wants to know. | | `release_hold` | Use this when the person no longer wants a time you held for them and has not confirmed it. Ends the hold at once, so the time is free again. Do not use for cancelling a confirmed booking: release_hold only ends a hold that is still waiting, and the person cancels a booking with the business. | | `find_businesses` | Use this when a person wants to book something on Bookatu and has no business in mind yet. Give the country and at least one of service, name or place (a town, city or area the person named, never their own position). Returns up to 10 businesses that chose to be found here, in name order, each with its city and area (never a street address), the languages it speaks, its lowest price, the services that match and its booking page. No business pays to be listed or placed. Do not use for a business you already know: pass it to get_business. | ```sh # No key needed curl -X POST https://bookatu.com/api/mcp/book \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "get_business", "arguments": { "business": "the-business-slug" } } }' ``` An assistant can hold a time only at a business that has chosen to take bookings from assistants. Nothing is booked until the person confirms: Bookatu emails them a code and a link, and they give the code to their assistant or open the link. A service an assistant cannot hold comes back with the business's booking page, to send the person there. For the person, in their own language: how to add this server to their assistant, and what each tool does there. [Book with your assistant](https://bookatu.com/en-nz/ai/book-with-your-assistant). ## Connect from Claude *OAuth 2.1* Claude's custom connectors use OAuth rather than a pasted key, and the MCP server supports that flow natively. You sign in with your normal Bookatu account, pick which business to connect and whether Claude may write or only read, and Claude receives its own revocable token for that one business. Your password and your other businesses are never shared. 1. In Claude, open Settings → Connectors → Add custom connector. 2. Enter `https://bookatu.com/api/mcp` as the server URL and continue. 3. Claude sends you to Bookatu to sign in. You must be an owner or admin of the business you connect, with a confirmed email. 4. Choose the business, the access level (read and write, or read only) and whether the app may see your clients' names, emails and phone numbers: a box on the consent page that stays unticked unless you tick it. Then approve. Without that box ticked, `list_customers` answers 403 naming `customers:read`, and booking requests, class rosters and form responses come without the client's details. To change your answer later, connect the app again. The same rules apply as with API keys: every tool is scoped to the connected business, read-only connections are refused on any write tool, and there are no delete tools at all. Disconnect any time from Settings → Developer API → Connected apps in your dashboard, or from Claude's connector settings. The flow is the standard MCP authorization stack for any other OAuth-capable MCP client too: discovery at `/.well-known/oauth-authorization-server` and `/.well-known/oauth-protected-resource`, dynamic client registration, authorization code with PKCE, and refresh token rotation. ## Build an agent on Bookatu *The closed loop* An AI agent can run a Bookatu business end to end with two primitives: MCP tools to act (read data, create bookings, manage the catalog, draft campaigns) and signed webhooks to react (a POST arrives at the agent when something happens). Tools in, events out. That closes the loop: the agent no longer needs a human to tell it that a booking was cancelled or an order was paid. ### 1. Get a read-write API key Create one in the admin dashboard under Settings, then Developer API. The key scopes every tool call to that business; a read-only key can call every read tool but no write tool. ### 2. Subscribe to events (the agent can do this itself) Call the webhooks_create MCP tool with a public https URL your agent listens on. The response contains the HMAC signing secret exactly once. webhooks_list shows what is wired up, webhooks_disable switches an endpoint off, and the owner sees every endpoint and delivery in the dashboard. ### 3. Verify and react Each delivery is signed (X-Bookatu-Signature) and named (X-Bookatu-Event). Verify the signature, then decide: a booking.cancelled can trigger a get_availability call and a waitlist offer; an order.paid can trigger receive_stock planning; a form.submitted can trigger the pre-visit checklist. ### 4. Act through tools, within the guardrails Every write is org-scoped and velocity-capped, there are no delete tools, campaigns can only be drafted (sending stays owner-confirmed in the dashboard), and clients' form answers never leave the admin UI. An agent can run the business without being able to wreck it. ### Worked example: an agent that refills cancelled slots ```sh # The agent registers where it wants events delivered (once, at setup) curl -X POST https://bookatu.com/api/mcp \ -H "Authorization: Bearer bk_live_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "webhooks_create", "arguments": { "url": "https://agent.example.com/hooks/bookatu", "events": ["booking.cancelled"] } } }' # → { "webhook": { "id": "whk_...", ... }, "secret": "whsec_..." } (secret shown once) ``` ```http # Later, a client cancels. Bookatu POSTs to the agent's endpoint: POST /hooks/bookatu HTTP/1.1 X-Bookatu-Event: booking.cancelled X-Bookatu-Event-Id: evt_9Xq2LmT4vB7nR1sK X-Bookatu-Signature: t=1780000000,v1=3f1c...9ab2 Content-Type: application/json { "id": "evt_9Xq2LmT4vB7nR1sK", "event": "booking.cancelled", "sentAt": "2026-07-30T02:14:00.000Z", "data": { "id": "apt_abc123", "ref": "MV-7QK2M9", "service": "Gel Manicure", "startAt": "2026-08-02T21:00:00.000Z", "status": "cancelled", "staffId": "stf_sam", "customerId": "cus_xyz" } } ``` ``` # The agent verifies the signature, then acts through MCP again: # confirm the freed slot is really open... { "name": "get_availability", "arguments": { "serviceId": "svc_...", "from": "2026-08-02", "to": "2026-08-02" } } # ...and rebook it for the next customer who asked for that time. { "name": "create_booking", "arguments": { "serviceId": "svc_...", "startAt": "2026-08-02T21:00:00.000Z", "name": "Mia Chen", "email": "mia@example.com", "phone": "+64211234567" } } ``` > **What the loop deliberately cannot do** > > What the loop deliberately cannot do: anything that never goes through an AI (signing in, giving anyone access, the bank details clients pay into, saying yes to AI using client details, closing the business; whoami and get_help answer the list, each line with the screen it is done on), make a change that needs a person's approval without their yes (such a tool takes an approvalId, and answers APPROVAL_REQUIRED with the link where they approve it), read clients' form answers, or touch another business (the org is resolved from the key, and endpoint URLs must be public https, so events can never be routed to internal infrastructure). Other writes run when they are called: cancelling or declining a booking refunds a paid deposit, as when the team does it, so check with the owner first, and send dryRun to see who is told. Webhook payloads carry ids and names, not customer contact details; fetch full records with your key when you need them. ## Testing with a sandbox A sandbox is a test business inside Bookatu, made for building and testing an integration. It answers the same API with the same booking rules and sends the same webhooks as a live business, but nothing it does reaches a real person or moves real money: every message it would send is kept in its test outbox, and every payment goes through a simulated checkout. ### What a sandbox is Each sandbox is a business of its own with a slug of its own, so the calls you make to a live business work on it unchanged: `https://bookatu.com/api/v1/{slug}/...`. It is marked as a test business everywhere: a Test mode banner on every page of its admin, a Test business ribbon on its booking pages that asks visitors not to enter real personal details (as does a short notice right above the client details on its booking page and in its widget), and `livemode: false` on every API answer. A sandbox can never be turned into a live business, and a live business can never become a sandbox. A sandbox is never listed anywhere public: not in the Bookatu directory or its search, not in sitemaps, not on Google or Bing, and its pages are never indexed. It is not billed and has no trial. ### Make a sandbox Sign in with any verified Bookatu account (a business owner's, or a developer's with no business at all) and open your sandboxes at [/developers/sandbox](https://bookatu.com/en-nz/developers/sandbox). Pick a name, a business type (it decides the sample data: see What is in it, below), a time zone and a currency (your browser's are filled in) and accept the test-mode terms. You can have up to 3 sandboxes at a time. A sandbox can't be made in a currency with no minor unit, such as JPY or KRW: Bookatu takes no card payments in those yet, so making one answers `400` with `INVALID_CURRENCY`. Or make one from your own code, signed in with your Bookatu login: the web session, or the account token `POST /api/mobile/auth/login` returns, sent as `Authorization: Bearer ...`. ```http POST /api/developer/sandboxes Content-Type: application/json Authorization: Bearer YOUR_ACCOUNT_TOKEN { "name": "Acme test salon", "timezone": "Pacific/Auckland", "currency": "NZD", "acceptTestModeTerms": true } ``` ```http HTTP/1.1 201 Created Content-Type: application/json { "sandbox": { "id": "org_...", "slug": "sbx-ab12cd34", "name": "Acme test salon", "timezone": "Pacific/Auckland", "currency": "NZD", "createdAt": "2026-10-30T02:00:00.000Z", "lastActiveAt": "2026-10-30T02:00:00.000Z", "expiresAt": "2026-11-29T02:00:00.000Z", "adminUrl": "https://bookatu.com/sbx-ab12cd34/admin", "storefrontUrl": "https://bookatu.com/sbx-ab12cd34", "apiBaseUrl": "https://bookatu.com/api/v1/sbx-ab12cd34" }, "testKey": { "key": "bk_test_...", "prefix": "bk_test_AbCd", "scopes": ["bookings:read", "bookings:write", "customers:read", "..."], "expiresAt": "2027-01-28T02:00:00.000Z" } } ``` `acceptTestModeTerms` must be `true`: a sandbox is for building and testing, with made-up people and data only. `industry` is optional (`salon` when left out): it is the business type, and decides the sample data the sandbox is made with and reset to. A sandbox's first key comes with it: every scope its owner may give (the opt-in ones included), valid for 90 days, shown once in the page or in the 201 answer that made the sandbox. It is never put in a URL. Store it (`testKey.key`) like any other secret. | Call | What it does | | --- | --- | | `GET /api/developer/sandboxes` | Your sandboxes, each with when it expires. | | `POST /api/developer/sandboxes` | Make one: `201` with the sandbox and its first test key. | | `POST /api/developer/sandboxes/{id}/reset` | Wipe it and fill it with fresh sample data. Its id and slug, its keys, its webhook endpoints and its connected apps are kept. | | `DELETE /api/developer/sandboxes/{id}` | Delete it and everything in it. | One exception, for CI: POST /api/developer/sandboxes/{id}/reset also takes that sandbox's own test key (bk_test_, as Authorization: Bearer or X-Api-Key) when it has the bookings:write scope, so a test run can reset its sandbox with a key you can revoke, and never anyone's login. It resets that sandbox only; its keys are kept, so the same key goes on working. Another sandbox's key gets 404 NOT_FOUND, and a key without the scope 403 MISSING_SCOPE. Keep the account token out of CI: it opens every business its login belongs to (through the phone app's API too), lasts 30 days and needs a two-step code at each sign-in when two-step is on. For automation that makes sandboxes, use a login of its own with no business. Over MCP, the same test key resets its sandbox with the sandbox_reset tool. ```http POST /api/developer/sandboxes/{id}/reset Authorization: Bearer YOUR_SANDBOX_TEST_KEY ``` A refusal says why in `code`: | Status | Code | When | | --- | --- | --- | | 401 | `UNAUTHORIZED` | Not signed in, an expired account token, or an API key instead of your login (on a reset, a test key that is revoked, expired or made up). | | 403 | `MISSING_SCOPE` | A reset with a test key that does not have bookings:write; missingScope names it. | | 403 | `FORBIDDEN_ORIGIN` | A write by session cookie that did not come from Bookatu's own pages. | | 403 | `EMAIL_NOT_VERIFIED` | Your email address is not confirmed yet. | | 403 | `SANDBOX_CREATION_DISABLED` | Making sandboxes is switched off on the platform at the moment. | | 400 | `TEST_MODE_TERMS_NOT_ACCEPTED` | acceptTestModeTerms was not true. | | 400 | `INVALID_TIME_ZONE` | timezone is not an IANA zone name. | | 400 | `INVALID_CURRENCY` | currency is not one a sandbox can use. | | 400 | `INVALID_INDUSTRY` | industry (optional, default salon) is not one of Bookatu's business types. | | 400 | `INVALID_BODY` | The body is not a JSON object. | | 409 | `SANDBOX_LIMIT_REACHED` | You already have three sandboxes. | | 409 | `TEST_COPY` | On a reset: this is a business's test copy, which is reset from that business's Developer API page. | | 429 | `RATE_LIMITED` | More than five made by you, or ten from your address, in a day. Retry-After says when. | | 404 | `NOT_FOUND` | The id is not one of your sandboxes (or, on a reset with a test key, not that key's own sandbox). | Three sandboxes at a time each. Five may be made a day by one person and ten from one address (a delete doesn't give one back). ### What is in it - Its sample data is its business type's (industry, salon when left out), and a reset seeds the same type again. By type: - Salon (salon, the default): three people (two stylists and a therapist); Women's cut and blow-dry, Men's cut, Full colour (takes a deposit), Balayage (asks "Have you coloured your hair in the last three months?"), Express facial, Relaxing massage and Deep conditioning treatment (an extra, offered with every service, that adds 15 minutes); booking terms; a waitlist entry. - Dental clinic (clinic): two dentists and a dental hygienist; Surgery 1 and Surgery 2, rooms every service needs; Check-up and clean, New patient exam (longer), Emergency appointment (short notice: the clinic takes bookings from 30 minutes ahead) and Whitening consultation (takes a deposit); every booking asks "Are you a new patient?" (required) and "Anything we should know before your visit?"; booking terms; past and upcoming appointments, each in a surgery, and a waitlist entry. - Restaurant (restaurant): ten tables of two to eight seats in three sections (Main room, Window, Courtyard), laid out on the floor plan; lunch and dinner sittings (Tuesday to Saturday 12:00 to 15:00 and 17:30 to 22:00, Sunday lunch); Table reservation, Window table, Courtyard table and Tasting menu (priced per person, with a deposit per person), each needing a table: send partySize, and only tables that seat the party are offered and used; every booking asks "Any special requests?" and "Is it a special occasion?"; booking terms (tables are held for 15 minutes); reservations at lunch and dinner with their covers. - Tennis coach (coach): two coaches; Court 1 and Court 2, one for every lesson and group; Private lesson, Semi-private lesson for two (partySize up to 2, priced per player), and two weekly groups with places and four upcoming sessions each, Cardio tennis and Junior squad; every booking asks "What is your level?" (a choice, required); a rain policy as the booking terms; lessons past and upcoming, and places booked on the groups. - Personal trainer (trainer): two trainers; Free intro consultation (no charge), 1:1 session (45 min), 1:1 session (60 min), Partner session for two (partySize up to 2, priced per person) and Small-group bootcamp (a weekly group with places and four upcoming sessions); every booking asks "Where would you like to train?" (Studio or Outdoors at the park, required); booking terms; sessions past and upcoming. - Any other business type (spa, studio, photographer, freelancer, other): the sample every sandbox had before, with no extra and no booking terms: three people with weekly hours inside the business's own (weekdays 9 to 6, Saturday 9 to 4); seven services, one taking a deposit (and only that one), one asking a booking question and one a weekly class with four upcoming sessions. - Five made-up clients, every email at an example domain and every phone in a range reserved for fiction (+1 NXX 555 01XX, +44 7700 900XXX), opted in to texts so the Outbox shows what they would have been sent. - Bookings in the past (completed, and a no-show) and the next few days (confirmed), and places booked on its classes. Every time is in the zone you picked, inside the hours of the person or the business; every price in the currency you picked, in minor units. - Sample payments, so Finance and Test payments start with real-looking numbers: deposits paid online through the test checkout on some upcoming bookings and on the no-show (kept, half of it refunded: the one refund), the completed visits paid in person (by card or in cash), and one sale at the point of sale of a sample product, sold at the desk only. They are recorded as the real thing is (the payments ledger, the booking's deposit, the sale at the point of sale) and announce nothing: no message and no webhook. GET /sandbox/payments lists them, and a reset makes them again. - Where a sample asks booking questions or has booking terms, POST /book needs the person's answers (answers) and acceptTerms: true, exactly as at a live business that set them: without them it answers ANSWERS_REQUIRED or TERMS_NOT_ACCEPTED and books nothing. A restaurant's tables and the lessons and sessions for two take partySize: GET /availability with partySize offers only times with a table or court that seats the party, POST /book with partySize seats them there, and a price per person is charged for each of them. - Each seeded booking has a manage key, as every booking made today does, and its key, like a real client's, is only ever given to the person who booked: with a seeded booking's id alone, GET /booking/{id} answers the read-only view and its availability, reschedule and cancel calls answer 403 MANAGE_KEY_REQUIRED, exactly as at a live business. To build and test managing a booking, make one with POST /book (its answer carries manageKey) or take the k from the manage link in its confirmation in the Outbox. - The card-required rule (CARD_REQUIRED_USE_BOOKING_PAGE) is the business's cancellation policy, not a service's, so it starts off: switch on Require a card under Settings to try the card step, and every priced service then needs one. The made-up clients' emails are at reserved example domains (such as example.com) and their phone numbers in reserved fiction ranges, so nothing can ever reach a real person. Change anything you like, in its admin or through the API. Reset puts the sample data back. ### Test keys and livemode A sandbox issues only test keys, which start `bk_test_`, and a live business only live keys, which start `bk_live_`. Make and revoke them in the sandbox's admin at `/{slug}/admin/api`, with the same scopes as live keys, and use one exactly as you would a live key: `Authorization: Bearer bk_test_...` or `X-Api-Key`. Every JSON answer says `livemode`: `false` from a sandbox, `true` from a live business. Every answer also carries the `Bookatu-Livemode` header, the one to read when an answer is not a JSON object. On the MCP server a result says it in `_meta["com.bookatu/livemode"]`; the header is there on every answer, streamed ones included. A test key sent to a live business, or a live key sent to a sandbox, is refused before anything runs, on every endpoint, the keyless ones included: ```http HTTP/1.1 403 Forbidden Content-Type: application/json { "ok": false, "error": "...", "code": "LIVEMODE_MISMATCH", "keyLivemode": false, "businessLivemode": true, "livemode": true } ``` A front end that calls the keyless endpoints, with no key at all, can send `Bookatu-Livemode: false` on every request: a call that reaches a live business is then refused the same way, so a test build can never book at a real business. An app connected through OAuth to one of your own sandboxes is a test connection: the consent page lists your sandboxes marked (test), never anyone else's; the token answer says livemode: false; MCP calls with it say livemode false. Connections to live businesses get livemode: true in the token answer, and are otherwise unchanged. A connection is pinned to the API version current when it was approved. Testing an AI agent? Point it at the sandbox through the MCP server, with its test key or a connected app, and it gets four tools of its own: the outbox, the test payments, the simulator and reset. See [Test your AI agent](https://bookatu.com/en-nz/developers/testing-ai-agents). ### The test outbox Nothing a sandbox sends leaves Bookatu. Every email, text message, WhatsApp message, call and push notification it would send to a client or to its team is kept in its test outbox instead: read it in the sandbox's admin at `/{slug}/admin/outbox`, or with `GET /api/v1/{slug}/sandbox/outbox` (a test key with `customers:read`; filter with `channel`, `since` and `limit`, and page with `cursor`, the `nextCursor` of the page before). It keeps the newest 500 messages. ```sh curl "https://bookatu.com/api/v1/sbx-ab12cd34/sandbox/outbox?channel=email&limit=20" \ -H "Authorization: Bearer bk_test_YOUR_KEY" { "messages": [ { "id": "sbo_...", "channel": "email", "kind": "booking_confirmation", "to": "mia@example.com", "subject": "You're booked in", "text": "...", "html": "...", "appointmentId": "apt_...", "customerId": "cus_...", "createdAt": "2026-10-30T02:05:00.000Z", "meta": {} } ], "nextCursor": null, "livemode": false } ``` The one message a sandbox really sends is the warning to you, its maker, before it expires. ### Payments: the simulated checkout A sandbox never reaches a real card or a real payment account. Where a live business sends a client to pay (a deposit, a gift card, the shop), a sandbox sends them to a simulated checkout page with three buttons: Pay (test), Decline (test) and Abandon. Pay (test) completes the payment; Decline (test) shows a declined card and leaves the checkout open, as a real one does; Abandon lets it expire. Each takes the same path as a real payment, so the booking, its webhooks and its emails (in the outbox) go through the real states: paid, failed and expired. The keyless API hands a deposit or a card to save to the booking page, as at a live business: POST /book answers 409 DEPOSIT_NEEDS_BOOKING_PAGE or CARD_REQUIRED_USE_BOOKING_PAGE with bookingPageUrl. A sandbox's booking page is open to anyone (its other storefront pages are yours only), so your front end can follow that link from any browser, signed in or not, to the simulated checkout. Where a service needs a card saved to hold the booking, the card step offers Save test card and Save a card that will decline, and a no-show fee charged later succeeds or fails by the card saved. These pages have buttons only: never type a real card number into a sandbox. Every kind of checkout works this way: deposits, class places, gift cards, the shop, packages, prints, gallery extras and invoices. Refunds of test payments are simulated too. Memberships (subscriptions) can't be bought in test mode yet. Every test payment is listed in the sandbox's admin under Test payments (`/{slug}/admin/test-payments`, beside the Outbox), and by `GET /api/v1/{slug}/sandbox/payments` (a test key with `reports:read`; filter with `kind` and `since`, and page with `limit` and `cursor`, the `nextCursor` of the page before). Each is a checkout, a payment, a card hold, a no-show charge or a refund, with its outcome (paid, declined, abandoned, card saved, refunded), its amount and currency, when it was made and the booking or sale it belongs to. Nothing in it names a client. ```sh curl "https://bookatu.com/api/v1/sbx-ab12cd34/sandbox/payments?kind=checkout&limit=20" \ -H "Authorization: Bearer bk_test_YOUR_KEY" { "payments": [ { "id": "cs_test_sbx_...", "kind": "checkout", "outcome": "paid", "amountCents": 5000, "refundedCents": 0, "currency": "NZD", "description": "Deposit · Full colour", "appointmentId": "apt_...", "belongsTo": { "type": "booking", "id": "apt_..." }, "checkoutSessionId": "cs_test_sbx_...", "paymentIntentId": "pi_test_sbx_...", "createdAt": "2026-10-30T02:05:00.000Z", "updatedAt": "2026-10-30T02:06:00.000Z" } ], "nextCursor": null, "livemode": false } ``` A new sandbox already has some, made with its sample data: deposits paid online on some of its bookings (the no-show's kept, half of it refunded), its completed visits paid in person and one sale at the point of sale, so Finance reads like a real business's. They announce nothing (no message, no webhook), and a reset makes them again. A test business can also take its payments through Stripe test mode instead of the simulator, where it is offered. Its owner connects a Stripe test account on the Test payments page and turns Stripe test mode on there. New checkouts then open Stripe's own checkout page, and card steps show Stripe's card form on the booking page. There you use one of Stripe's test cards, such as 4242 4242 4242 4242. No real money moves. These payments are listed in the business's Finance, not under Test payments: GET /sandbox/payments and sandbox_payments list the simulated ones, and their paymentsMode says how new payments go (simulated, or stripe_test). Payments made before a switch keep working as they were. ### Make things happen: the simulator Some events would otherwise mean waiting, or a client doing something. `POST /api/v1/{slug}/sandbox/simulate/{event}` makes them happen now, at a sandbox only (a test key with `bookings:write`; at a live business the answer is `404` with `code: "NOT_A_SANDBOX"`). | Event | What happens | | --- | --- | | `deposit.paid` | Pays the booking's open test checkout, as the test checkout page's "Pay (test)" does: checkout.session.completed runs through the Stripe webhook's own handler, the booking is confirmed with its deposit paid, the confirmation goes to the outbox and booking webhooks are sent. | | `payment.failed` | Declines the test card on the booking's open checkout, as "Decline (test)": the checkout stays open (as on Stripe's page) and nothing else changes; the answer says so (result.declined true, result.changed false). | | `checkout.expired` | Abandons the booking's open checkout, as "Abandon": checkout.session.expired runs, and an online booking held for its deposit is let go (cancelled as deposit_abandoned) and its time offered to the waitlist. | | `booking.client_cancelled` | The client's own cancellation (the manage page's), with the business's cancellation window, deposit rule, late-cancellation fee, emails and the booking.cancelled webhook. | | `booking.no_show` | Marks the booking a no-show. A no-show fee the cancellation policy sets is queued for the owner, as at a live business (result.fee): nothing charges it but the owner's Charge on the test business's No-show fees screen, which charges the client's saved TEST card: paid for a card saved with "Save test card", declined (card_declined) for one saved with "Save a card that will decline". | | `reminders.due` | Time passing: the booking's reminder email and reminder texts are sent as if now were its start minus each lead the business set (reminderHoursBefore, and its own text times). A booking reminded already is not reminded again. | ```sh curl -X POST https://bookatu.com/api/v1/sbx-ab12cd34/sandbox/simulate/deposit.paid \ -H "Authorization: Bearer bk_test_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "appointmentId": "apt_..." }' ``` The answer gives the booking as it is now, the ids of the outbox messages the event kept (`outbox`), the webhook events it sent (`webhooks`) and what the event itself reported (`result`). The booking must be the sandbox's own: an id from any other business is a `404` with `code: "APPOINTMENT_NOT_FOUND"`. An unknown event is `400` `UNKNOWN_SIMULATION` (the answer lists the events), a booking with no open test checkout to pay, decline or abandon is `409` `NO_OPEN_CHECKOUT`, a cancellation the business's rules don't allow is `409` `SIMULATION_REFUSED`, and a payment event on a checkout in Stripe test mode is `409` `STRIPE_TEST_MODE`. A checkout in Stripe test mode is paid on Stripe's own page, not by the simulator. On a booking whose checkout is in Stripe test mode, deposit.paid, payment.failed and checkout.expired answer 409 STRIPE_TEST_MODE. While new payments go through Stripe test mode, deposit.paid and payment.failed on a booking that still owes its deposit online and has no open test checkout answer the same. Pay on Stripe's checkout page with a test card instead, or switch the business back to simulated payments. A booking with its own simulated checkout works as before. In Stripe test mode, booking.client_cancelled answers before Stripe sends charge.refunded for a deposit it refunds. ### Webhooks from a sandbox Webhooks are the one thing a sandbox does send out. Register an endpoint on the sandbox (in its admin, or with `webhooks_create` over MCP) and its events are delivered to you, signed as a live business's are, so one receiver can tell the two apart by `livemode`. Every webhook payload has a top-level livemode field: true for a live business's event, false for a sandbox's (test mode). The same is sent as the X-Bookatu-Livemode header ("true" or "false"). A retried delivery resends the same bytes, so it says the same. A sandbox's webhooks are sent to your endpoints like a live business's, through the same address checks (public https only), with smaller limits: up to 5 endpoints, 300 deliveries an hour, 3 retries, and Send test 10 times a minute. ### Expiry, reset and delete A sandbox nobody uses is deleted after 30 days without an API call with its key or a visit to its admin, and you get an email 7 days before. Using it again starts the 30 days again. Reset wipes everything in it and fills it with fresh sample data, keeping its id and slug, its keys, its webhook endpoints and its connected apps. Delete removes it and everything in it at once. Both are on your sandboxes page and in the developer API above. ### Limits - No Bookatu billing: it has every feature of the Scale plan and is never charged. It is never on a trial or paused. - Small fixed ceilings, whatever the plan says: 50 AI operations a month (and one daily budget shared by all sandboxes), half a gigabyte of gallery storage, 200 marketing emails a month (to its Outbox), 200 rows an import. - It can't connect Twilio, WhatsApp, Messenger, Instagram, Google Calendar, QuickBooks or a Stripe account, have a custom domain, add team members or staff logins, use the managed AI assistant, or have a referral link. - It is never in discover, search, the sitemap, the platform's directories or social proof. Its storefront pages are for you (and Bookatu support) only, marked Test business and never indexed; its booking page (/{slug}/book, where POST /book's DEPOSIT_NEEDS_BOOKING_PAGE and CARD_REQUIRED_USE_BOOKING_PAGE answers send a client), the group session pages it links its classes to (/{slug}/sessions/{serviceId}), its test checkout and the pages its Outbox links to (a client's booking, confirm, review, claim, swap and the like) are open to anyone with the link, so your own front end can be tested end to end by anyone on your team. Its booking widget is shown only on the domains you list under Settings. A sandbox has lower rate limits than any live business, whatever its plan: 25 calls a minute and 1,000 a day per test key, and 30 a minute per address on its keyless endpoints, which also keep a live business's booking caps. Its outbox and the simulator have small budgets of their own. See [Rate limits](https://bookatu.com/en-nz/developers/rate-limits). When it works, see [Going live](https://bookatu.com/en-nz/developers/going-live) to switch to a live business's key. ## Test your AI agent Before an AI agent books, moves or cancels anything at a real business, run it against a sandbox. A sandbox answers the MCP server with the same tools and the same booking rules as a live business, and four tools of its own for checking what the agent did. Nothing it does reaches a real person or moves real money. ### Why test against a sandbox - Mistakes stay in the sandbox. A wrong time, a double booking or a cancellation the agent should not have made touches made-up clients only. - Nothing leaves Bookatu. Every confirmation, reminder and notice the agent causes is kept in the sandbox's test outbox, where the agent, or you, reads it with `sandbox_outbox`. - Payments are simulated. A deposit is paid, declined or abandoned with `sandbox_simulate`, never with a card, and `sandbox_payments` lists every test payment with what became of it. - Every answer says it is a test: the `Bookatu-Livemode` header is `false` on every answer, and `result._meta["com.bookatu/livemode"]` is `false` on every tool result, a refusal included. A successful result's `structuredContent` says `livemode: false` too. - Every run can start from the same place. `sandbox_reset` puts the sample data back. Make a sandbox first, and keep its first test key: see [Testing with a sandbox](https://bookatu.com/en-nz/developers/testing). ### Connect an MCP client The business MCP server has one address for every business, `https://bookatu.com/api/mcp` (Streamable HTTP, JSON-RPC 2.0, POST only). The business is the one the credential belongs to, so a sandbox's credential reaches that sandbox and nothing else. There are two ways in. With the sandbox's test key: send it as `Authorization: Bearer bk_test_...` on every request (or as `X-Api-Key`). Send `Bookatu-Livemode: false` too where your client can: a call that would reach a live business, with a live key pasted in by mistake, is then refused before anything runs. ```http POST https://bookatu.com/api/mcp Authorization: Bearer bk_test_YOUR_KEY Bookatu-Livemode: false Content-Type: application/json MCP-Protocol-Version: 2025-06-18 {"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}} ``` With OAuth: a client that supports it signs in instead. It registers itself (dynamic client registration), sends you to Bookatu's consent page and gets a token of its own. Pick the sandbox there: your sandboxes are listed beside your businesses, marked (test). The token answer says `livemode: false`, and so does every MCP answer the connection gets. Tick the box that shares clients' names, emails and phone numbers when the agent should read the outbox (`sandbox_outbox` needs `customers:read`). A connected app can call every tool but `sandbox_reset`, which takes the sandbox's own test key. A credential or a call of the other mode is refused as a JSON-RPC error, with `LIVEMODE_MISMATCH` in `error.data.code`, never as a result: ```http HTTP/1.1 403 Forbidden Content-Type: application/json { "jsonrpc": "2.0", "id": 1, "error": { "code": -32000, "message": "This call asked for test mode (Bookatu-Livemode: false), and this is a live business. Test calls reach sandbox businesses only.", "data": { "code": "LIVEMODE_MISMATCH", "keyLivemode": false, "businessLivemode": true } } } ``` ### Claude Desktop Claude Desktop, and Claude in a browser, adds a remote MCP server as a custom connector. In Claude, open Customize > Connectors and choose Add custom connector: ``` Customize > Connectors > Add custom connector Name: Bookatu sandbox Remote MCP server URL: https://bookatu.com/api/mcp Authentication: Sign in now OAuth client: Register automatically ``` Claude then sends you to Bookatu: sign in, pick your sandbox (marked (test)), choose read and write, and approve. Where your organization has the Request headers section (a beta in Claude's dialog), you can use the test key instead: choose No sign-in, then add the header `authorization` with the value `Bearer bk_test_YOUR_KEY`, the word Bearer and its space included. A header name of your own needs Anthropic's approval first, so `Bookatu-Livemode` can't be added there; the test key on its own can only ever reach its sandbox. Claude's own steps: [Add a connector that isn't in the directory](https://claude.com/docs/connectors/custom). ### Cursor Cursor reads MCP servers from `.cursor/mcp.json` in a project, or `~/.cursor/mcp.json` for every project, and fills in `${env:NAME}` in a server's `url` and `headers`. Keep the key in your environment, never in the file: ```json { "mcpServers": { "bookatu-sandbox": { "url": "https://bookatu.com/api/mcp", "headers": { "Authorization": "Bearer ${env:BOOKATU_TEST_KEY}", "Bookatu-Livemode": "false" } } } } ``` Then set `BOOKATU_TEST_KEY` to your test key in the environment Cursor starts from. Leave `headers` out and Cursor signs in with OAuth instead (authorization code with PKCE, dynamic client registration), which opens Bookatu's consent page. Cursor's own reference: [Model Context Protocol (MCP)](https://cursor.com/docs/context/mcp). ### MCP Inspector The MCP Inspector is the reference tool for trying an MCP server by hand (it needs Node 22.19 or newer). Its CLI calls one method and prints the answer: ```sh npx @modelcontextprotocol/inspector --cli https://bookatu.com/api/mcp --transport http \ --header "Authorization: Bearer bk_test_YOUR_KEY" \ --method tools/list npx @modelcontextprotocol/inspector --cli https://bookatu.com/api/mcp --transport http \ --header "Authorization: Bearer bk_test_YOUR_KEY" \ --method tools/call --tool-name sandbox_outbox --tool-arg limit=5 ``` Or open its web client on the server with `npx @modelcontextprotocol/inspector --server-url https://bookatu.com/api/mcp --transport http`, add the `Authorization` header in the server's settings (or sign in with OAuth), and call the tools from its Tools tab, where each tool's annotations and outputSchema show beside it. The Inspector's own reference: [MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector). ### Things to ask your agent A short run that goes through a booking from start to end. Ask in plain words, and check each answer against what the tools returned: 1. Find a free time: "When could I book a haircut on Tuesday afternoon?" The agent calls `list_services` and `get_availability` (and `get_business` for the opening hours), and answers with times from the slots, on the business's clock. 2. Book it: "Book it for Mia, mia@example.com, +1 613 555 0142." `create_booking` answers the booking's `ref` and `appointmentId`. A sandbox's clients are made up: use an address at example.com and a number in a range kept for fiction. 3. Check the confirmation: "What was she sent?" `sandbox_outbox` shows the message that would have gone out (its `kind` is `booking_confirmation`), with its subject, its text and the booking's `appointmentId`. 4. Simulate the deposit paid: "The client has paid the deposit." `sandbox_simulate` with `deposit.paid` pays the booking's open test checkout: the deposit is paid, the answer lists the outbox messages and webhooks it caused, and `sandbox_payments` shows the checkout as paid. A booking needs an open test checkout for this, one opened on the sandbox's booking page or by a deposit the business asked for (`POST /api/v1/{slug}/appointments` with `requestDeposit: true`). `create_booking` books no service that takes a deposit (in the salon sample data, Full colour; a dental clinic's Whitening consultation; a restaurant's Tasting menu): it answers `DEPOSIT_NEEDS_BOOKING_PAGE` with `bookingPageUrl` and books nothing, as at a live business, so open that link to book it on the booking page and reach the test checkout there. 5. Cancel: "Cancel Mia's booking." `cancel_booking` cancels it as the business and says whether a deposit was kept. A cancellation by the business sends the client no message, so `sandbox_outbox` has no message to her about it: if she should hear, the agent or the business tells her. `sandbox_simulate` with `booking.client_cancelled` is the client's own cancellation instead, under the business's window, fees and notices; that one emails the client a cancellation notice, kept in the outbox, when the business has "Email clients when they cancel online" turned on in its settings. 6. Start again: "Reset the sandbox." `sandbox_reset`, with the sandbox's test key only, puts the sample data back. A good agent asks you first. ### What the sandbox tools return | Tool | Scope | Returns | | --- | --- | --- | | `sandbox_outbox` | `customers:read` | `messages` (newest first: `id`, `channel`, `kind`, `to`, `subject`, `text`, `html`, `appointmentId`, `customerId`, `createdAt`, `meta`), `nextCursor` and `livemode: false`. | | `sandbox_payments` | `reports:read` | `payments` (newest first: `id`, `kind`, `outcome`, `amountCents`, `refundedCents`, `currency`, `description`, `appointmentId`, `belongsTo`, `checkoutSessionId`, `paymentIntentId`, `createdAt`, `updatedAt`), `nextCursor`, `paymentsMode` (`simulated`, or `stripe_test` while new payments go through Stripe test mode) and `livemode: false`. | | `sandbox_simulate` | `bookings:write` | `ok`, `event`, `appointment` (`id`, `status`, `depositStatus`, `depositCents`, `depositPaidCents`, `startAt`, `endAt`, `customerId`, `checkoutSessionId`), `outbox` (message ids), `webhooks` (event names), `result` and `livemode: false`. | | `sandbox_reset` | `bookings:write` | `sandbox` (`id`, `slug`, `name`, `timezone`, `currency`, `createdAt`, `lastActiveAt`, `expiresAt`, `adminUrl`, `storefrontUrl`, `apiBaseUrl`) and `livemode: false`. | They are in `tools/list` only at a sandbox, and only for a credential that may call them. Each has a title and every MCP annotation: `sandbox_outbox` and `sandbox_payments` are read-only and idempotent, each with an outputSchema its `structuredContent` fits; `sandbox_simulate` and `sandbox_reset` are destructive and not idempotent, and `sandbox_simulate` is open-world, since a sandbox's webhooks reach your endpoints. A refusal the agent can act on is a tool error: for a client that sends a 2025 `MCP-Protocol-Version` header, a result with `isError: true` and `error.code` (`VALIDATION_FAILED` with `fieldErrors`, `APPOINTMENT_NOT_FOUND`, `NO_OPEN_CHECKOUT`, `SIMULATION_REFUSED`, `STRIPE_TEST_MODE`, or `UNKNOWN_SIMULATION` with the six `events`); for one that sends none, the JSON-RPC error `-32602` with the code in `error.data`. A missing scope is `403` naming `missingScope`, and a spent budget `429` with `retryAfterSec`. Every other tool works at a sandbox as at a live business. A successful result says `livemode` in its `structuredContent` too, `false` here, and the text block says what it always said; a refusal (`isError: true`) has no `livemode` in its `structuredContent`, so read it there from `result._meta["com.bookatu/livemode"]` or the `Bookatu-Livemode` header. ### Limits - A test key is held to 25 calls a minute and 1,000 a day, the sandbox's keys together. Every answer carries `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset` and `RateLimit-Policy`, and a `429` carries `Retry-After`. - `sandbox_outbox`: 30 calls a minute per sandbox, and 30 a minute per key, shared with GET /sandbox/outbox. The outbox keeps the newest 500 messages. - `sandbox_payments`: 30 calls a minute per sandbox, and 30 a minute per key, shared with GET /sandbox/payments. - `sandbox_simulate`: 10 calls a minute and 500 a day per sandbox, and 10 a minute per key, shared with POST /sandbox/simulate/{event}. - `sandbox_reset`: 30 resets a day per address, shared with POST /api/developer/sandboxes/{id}/reset. Only the sandbox's own `bk_test_` key with `bookings:write`, never a connected app or a live key. - The sandbox tools reach only the sandbox the credential belongs to: a booking of any other business is `APPOINTMENT_NOT_FOUND`. A live business never lists them, and called there, each is an unknown tool. - Messages are kept, never sent, and cards never charged, so a real delivery can't be tested: read the outbox instead. Webhooks are the one thing a sandbox sends, to your own endpoints, with `livemode: false`. - A sandbox has no Twilio, WhatsApp, Google Calendar or live Stripe connection (only Stripe test mode, where it is offered), and memberships can't be bought in test mode yet. The rest is in [Testing with a sandbox](https://bookatu.com/en-nz/developers/testing). When the agent works, see [Going live](https://bookatu.com/en-nz/developers/going-live): the same tools at a live business, with its live key, and no sandbox tools. ## Rate limits Every call to the v1 REST API and the MCP servers is counted against one or more windows (a minute, a day) per key, per business or per address. Each answer says where the call stands, and a call past a limit is refused with `429` and told when to try again. ### The headers on every answer Bookatu sends the fields of the IETF RateLimit header draft (draft-ietf-httpapi-ratelimit-headers), one set on every answer: | Header | What it says | | --- | --- | | `RateLimit-Limit` | The limit of the window closest to running out. | | `RateLimit-Remaining` | Calls left in that window. | | `RateLimit-Reset` | Seconds until that window starts again. | | `RateLimit-Policy` | Every window the call was counted against, as limit;w=seconds, shortest first: `30;w=60, 2000;w=86400` is 30 a minute and 2,000 a day. | | `Retry-After` | On every `429`: seconds to wait before trying again. | | `Request-Id` | An id for this one call, made by Bookatu. Quote it when you report a problem. | A browser may read all of them: they are listed in `Access-Control-Expose-Headers`. ```http HTTP/1.1 200 OK RateLimit-Limit: 30 RateLimit-Remaining: 29 RateLimit-Reset: 60 RateLimit-Policy: 30;w=60, 2000;w=86400 Bookatu-Version: 2026-10-30 Bookatu-Livemode: true Request-Id: req_V1StGXR8Z5jdHi6B ``` ### The limits | What | Counted per | Limit | | --- | --- | --- | | Calls with a live key or connected app, Solo plan (standard tier) | Each key, and the business's keys together | 30 a minute, 2,000 a day | | Calls with a live key or connected app, Studio plan (standard tier) | Each key, and the business's keys together | 60 a minute, 10,000 a day | | Calls with a live key or connected app, Pro plan (standard tier) | Each key, and the business's keys together | 180 a minute, 50,000 a day | | Calls with a live key or connected app, Scale plan (standard tier) | Each key, and the business's keys together | 600 a minute, 250,000 a day | | Calls with a live key on the raised tier | That key, and its business's keys together while it calls | 4 times the plan's numbers above | | Website enquiries (POST /enquiries, GET /enquiries/trips) | Each key, and the business's enquiries together, apart from its other keys' calls | The plan's numbers above (30 a minute and 2,000 a day on Solo), counted on their own | | Public calls with no key (business, services, staff, availability, book), Solo plan | Each address, at each business | 60 a minute, 5,000 a day | | Public calls with no key (business, services, staff, availability, book), Studio plan | Each address, at each business | 120 a minute, 20,000 a day | | Public calls with no key (business, services, staff, availability, book), Pro plan | Each address, at each business | 300 a minute, 100,000 a day | | Public calls with no key (business, services, staff, availability, book), Scale plan | Each address, at each business | 600 a minute, 500,000 a day | | Bookings through POST /book and POST /visits/book | Each address, at each business | 5 per 10 minutes, 15 a day | | Bookings through the keyless doors, every address together | Each business | 40 a day | | The booking-management calls under /booking/{id} | Each address | 30 per 5 minutes for the two reads, 10 per 10 minutes each for reschedule and cancel | | GET /api/v1/discover | Each address | 60 per 5 minutes | | Bookings made with a key or connected app (create_booking, create_visit, POST /appointments and POST /visits), each visit of a repeat series counting; the MCP catalog writes together | Each key or connected app | 30 per 10 minutes for bookings, 60 per 10 minutes for catalog writes | | Calls with a key or app token that does not verify, and calls refused for a key of the other mode, across the whole API | Each address | 1,200 a minute (a call with no key at all is never refused here; only its business's own limits refuse it) | | Calls with a test key (bk_test_), whatever the tier | Each test key, and the sandbox's keys together | 25 a minute, 1,000 a day | | Public calls with no key at a sandbox | Each address, at each sandbox | 30 a minute, 1,000 a day | | GET /sandbox/outbox | Each sandbox | 30 a minute | | GET /sandbox/payments | Each sandbox | 30 a minute | | POST /sandbox/simulate/{event} | Each sandbox | 10 a minute, 500 a day | | Making a sandbox (POST /api/developer/sandboxes); resetting one | Each address; each person | 10 made a day per address and 5 per person, at most 3 at once; 20 calls to make one a day per address, refused ones included; 30 resets a day per address | A key is held to the plan of the business it belongs to. Keyless calls are counted per address at each business, so one busy client never uses up another's budget, and a key sent to a keyless endpoint is not counted on the key. A call refused before the endpoint counts it (a key without the endpoint's scope, another business's key, a business that is not found) is not counted on the key either. An answer the MCP server sends before it counts the call (the `notifications/initialized` 202, a parse error) says your key's windows as they stand. ### Standard and raised Every key is on the standard tier: its plan's numbers above. A Bookatu platform admin can put a live key on the raised tier, which gives that key, and its business's keys together while it calls, 4 times the plan's numbers: 120 a minute instead of 30 on Solo. Ask Bookatu support when your integration needs it, naming the key's prefix and the business. Only a platform admin can change a tier, and every change is in the business's audit log. Test keys are always held to the sandbox's limits, whatever their tier: raised never raises a test key. ### When you get a 429 The answer is a `429` with `Retry-After`, the headers above, and a body saying when to retry. Its words differ by endpoint; the status and `Retry-After` never do. Over MCP it is a JSON-RPC error `-32000`, `Rate limit exceeded`, with `error.data.retryAfterSec`. ```http HTTP/1.1 429 Too Many Requests Retry-After: 17 RateLimit-Limit: 30 RateLimit-Remaining: 0 RateLimit-Reset: 17 RateLimit-Policy: 30;w=60, 2000;w=86400 { "ok": false, "error": "Rate limit exceeded", "retryAfterSec": 17, "livemode": true } ``` - Wait at least `Retry-After` seconds before calling again. - Back off exponentially on repeated `429` and `5xx` answers, with jitter (a random part in each wait), so many clients do not retry in step. - Watch `RateLimit-Remaining` and slow down before it reaches 0. - Cache what rarely changes: `GET /business`, `/services` and `/staff`. - Use webhooks to learn about changes instead of polling for them. ```js async function call(url, init, attempt = 0) { const res = await fetch(url, init); if ((res.status === 429 || res.status >= 500) && attempt < 5) { const retryAfter = Number(res.headers.get("Retry-After")) || 2 ** attempt; const jitter = Math.random() * 1000; await new Promise((r) => setTimeout(r, retryAfter * 1000 + jitter)); return call(url, init, attempt + 1); } return res; } ``` ## Versioning The API has versions named for the day they were released, such as `2026-10-30`. Your integration keeps the behaviour of the version it is on until you choose to move; what is added in the meantime reaches every version. ### The versions | Version | Status | Sunset | What it is | | --- | --- | --- | --- | | `2026-10-30` | current | Not announced | The first named version: the v1 REST API, the MCP server and webhooks as they stood on 2026-10-30, with test mode, rate-limit headers on every answer and the Bookatu-Version header. Every key and connected app made before versioning is pinned to it. | New keys and apps are pinned to `2026-10-30`. Every change, and every version, is in the [changelog](https://bookatu.com/en-nz/developers/changelog). ### Asking for a version Send `Bookatu-Version` with the version your integration was written and tested against. Every answer says the version it was answered in, in the same header. ```sh curl https://bookatu.com/api/v1/{slug}/services \ -H "Bookatu-Version: 2026-10-30" HTTP/1.1 200 OK Bookatu-Version: 2026-10-30 ``` Without the header, a call made with a key or a connected app is answered in the version it is pinned to, and a call with neither in the oldest version still supported (`2026-10-30` today). A version that does not exist, has been switched off, or is not a date is refused before anything runs: ```http HTTP/1.1 400 Bad Request Content-Type: application/json { "ok": false, "error": "Bookatu-Version \"2025-01-01\" is not a version this API answers in. ...", "code": "UNSUPPORTED_API_VERSION", "supportedVersions": ["2026-10-30"], "livemode": true } ``` Over MCP the same refusal is a JSON-RPC error whose `data` carries the `code` and `supportedVersions`. ### Pinning A key is pinned to the version current when it is made, and a connected app to the version current when it is approved. Every key and app made before versions existed is pinned to `2026-10-30`. The header overrides the pin for one call, so you can try a newer version before you move; to move for good, send the header on every call, or make a new key, which is pinned to the current version. A key pinned to a version that has since been switched off is answered in the oldest version still supported, never refused for it. ### What changes, and when - An additive change needs no new version and reaches every version: a new endpoint, a new optional parameter, a new field in an answer or a webhook payload, a new error code where a call could already be refused, a new header. Write clients that ignore fields they do not know. - A breaking change ships only in a new version: a field removed or renamed, a type or a meaning changed, a parameter made required, a default or a status code changed. - A version is supported for at least 12 months after the next one is released. - A version's deprecation, with the date it is switched off, is announced at least 6 months before that date: in the [changelog](https://bookatu.com/en-nz/developers/changelog), and on every answer in it. ### Deprecation headers An answer in a deprecated version carries three headers: | Header | What it says | | --- | --- | | `Deprecation` | When the version was deprecated: `@` and a Unix time (RFC 9745). | | `Sunset` | The day it stops being served, as an HTTP date (RFC 8594). | | `Link` | Its changelog entry, with `rel="deprecation"`. | ```http Bookatu-Version: 2026-10-30 Deprecation: @1811808000 Sunset: Thu, 01 Jun 2028 00:00:00 GMT Link: ; rel="deprecation"; type="text/html" ``` An example only: no version is deprecated today. Look for `Deprecation` in your logs or monitoring; it is your notice to move. ## Changelog Newest first. Each entry is dated by the change that made it and has its own place on this page to link to. Changes before `2026-10-30` shipped before API versions existed, so no version was named for them; the ones that could break a client written against what came before are marked Breaking. How versions work: [Versioning](https://bookatu.com/en-nz/developers/versioning). ### GET /business says what the business's own page shows 2026-11-16 · After release 17 - `GET /api/v1/{slug}/business` adds `emailBase64` (the business's email in base64, as its page hands it to the browser, only while the business shows it publicly, else `null`; never the plain address), `links` (its website and profiles, each `type`, `url` and `display`), `tagline` and `logoUrl` (`null` when not set). - It adds `storefront`: `cover` (the page's first photo, else `null`), `photos` (the gallery in order, each `url`, `caption` and a focal point), `team` (whether the page shows its team), `trips` (the trips of whole days the page shows, each with `days`, `priceCents`, `priceLabel` and the `enquireUrl` of its enquiry page), `enquireUrl` (while there are trips, else `null`) and `map` (`caption`, `query` and `directionsUrl` while the address is shown, else `null`). - A trip stays display only: `GET /services` never lists one and `POST /book` refuses one, as before. - Additive: the same API version. ### Public booking MCP server: limits per network, email trouble kept to where it came from, and notifications counted 2026-11-14 · After release 17 - `hold_booking` (and `POST /api/v1/{slug}/agent/holds`) can answer `HOLD_LIMIT` when the caller's network has made as many holds at the business in the last day as it may, as well as for the business's own holds and the caller's. `bookingPageUrl` is the business's own booking page, as before. - Trouble with hold emails is now kept to the holds it came from, not the whole platform. After unusual activity on a caller's holds, that caller gets `RATE_LIMITED` from `hold_booking` for a while (wait `retryAfterSec`). After unusual activity on a business's holds, `hold_booking` answers `BUSINESS_NOT_AGENT_BOOKABLE` there with `bookingPageUrl` for a while, and holds start again by themselves. One caller's trouble no longer answers `CHANNEL_PAUSED` at every business. - Notifications, and requests the server cannot read (a body that is not JSON, or one that is not a single JSON-RPC request with a method), are counted in a short window per caller. Past it the answer is HTTP `429` with JSON-RPC error `-32000` "Rate limit exceeded", `error.data.code` `RATE_LIMITED`, `error.data.retryAfterSec` and `Retry-After`. - `find_businesses` is limited per network instead of across the whole platform, so a busy caller somewhere else no longer stops a search. When a business's times are asked for often, `check_availability` answers more callers instead of `RATE_LIMITED`, sometimes with times worked out a little before. - No answer changes shape: the same codes, in the same words. ### OAuth: a code redeemed for its own resource, client_id on every refresh, and discovery documents kept by caches 2026-11-14 · After release 17 · Breaking - `POST /api/oauth/token` with `grant_type=authorization_code`: when the request names a `resource` and the authorization request named one, they must be the same address (upper or lower case and a trailing slash make no difference). Another is refused with `400`, `error` `invalid_target` and "The resource does not match the authorization request.", before the code is used, so it can still be redeemed as it was approved. - A `refresh_token` grant names its `client_id`, as OAuth 2.1 asks of a public client. A refresh without it can be refused with `400`, `error` `invalid_request` and "client_id is required.". That refusal does not use up the refresh token: send it again with `client_id`. /auth.md says both. - The OAuth discovery documents (`/.well-known/oauth-authorization-server`, `/.well-known/oauth-protected-resource` and `/.well-known/oauth-protected-resource/api/mcp`) and the MCP server cards (`/api/mcp/server-card` and `/api/mcp/docs/server-card`) answer `Cache-Control: public, max-age=3600, s-maxage=86400`: a shared cache may keep them a day, and a browser an hour as before. Each stays the same until Bookatu next deploys. - The same API version. ### The website widget's times and the docs MCP server's body size 2026-11-14 · After release 17 - Website widget: when one address asks for a business's times too often in a short while, the widget shows no times, asks the visitor to wait a moment and try again, and sends the page an `error` event with code `velocity`. The list of error codes is unchanged. - Docs MCP server (`/api/mcp/docs`): a body too large for any of its tools is answered `413` with JSON-RPC `-32600` "Request body too large" before it is read in full, and it is not counted against the address. - Additive: the same API version. ### Bad input answered in plain words, a suspended business's keys, and the same booking sent twice 2026-11-14 · After release 17 · Breaking - A key of a business Bookatu has suspended now answers every REST call with `403`, `code` `BUSINESS_SUSPENDED` and `livemode`, and the words "This business is suspended, so its API keys are switched off. Contact Bookatu support." It was a `401`, which read as a wrong key. The MCP server still answers `401`. - `POST /api/v1/{slug}/appointments/{id}/cancel` answers a booking id this business does not have with `404` and `{ ok: false, error: "Booking not found" }`. It was a `400`. A booking that exists but cannot be cancelled is still a `400`. `GET /booking/{id}/availability`, `POST /booking/{id}/reschedule` and `POST /booking/{id}/cancel` answer an unknown booking with the same body, as `GET /booking/{id}` does. - `POST /book` and `POST /visits/book` with no `Idempotency-Key`: the very same request (the same email and every field the same) sent again within two minutes books nothing more. It answers `200` with the first booking, `idempotentReplay: true` and the `Idempotent-Replayed` header, without `manageKey` (the client has it in their confirmation email) and with a `note` saying so. While the first is still being made the answer is `409` with `code` `BOOKING_IN_PROGRESS`, `retryAfterSec` and `Retry-After`. Any other body, or the same one once the first booking is cancelled, books as before. Send an `Idempotency-Key` to retry for longer. - A day that does not exist (such as `2026-02-30`), or one too far away, sent as `from` or `to` to `GET /availability`, `GET /visits/availability` or `GET /booking/{id}/availability` is now a `400` that says which, in plain words, and MCP `get_availability` and `get_visit_availability` refuse it as Invalid params (`-32602`). Before, it was a server error. A `startAt` too far away to book is `422` `TIME_INVALID`: send a date in the next few years. - A `staffId` that is not on the business's team is `422` with `code` `NOT_ON_TEAM` at `fieldErrors.staffId` on `POST /book`, `POST /appointments`, `POST /visits/book` and `POST /visits`, and on MCP for a visit, and nothing is booked. Pick one from `GET /staff`, or leave it out. - `GET /reports/earnings` and `GET /reports/tips` take `?staffId=` as well as `?staff=`, as MCP and the answer's `query.staffId` call it. When both are sent, `staff` is used. An id not on the team is the same `404`. - Bad input to the booking doors, REST and MCP is a `400` or `422` in plain words at the field, never a `500` or the validator's own text. - The same API version: every version gets these at once. ### MCP: a key whose maker left answers nothing, and tools/list matches what a key may call 2026-11-14 · After release 17 · Breaking - A key made before scopes whose maker is no longer on the business's team is refused every MCP tool with `MAKER_NOT_ON_TEAM`, a read included, and `tools/list` offers it none. The REST API already refused it. A key Bookatu support set up for the business, and a key that records nobody, are unchanged. - `tools/list` leaves out every write a read-only key made before scopes would be refused, so the list and the calls follow one rule. - An unknown tool name always answers `-32601` Unknown tool. - The same API version. Replace a key made before scopes with a scoped key made by someone who stays on the team. ### OAuth: request mistakes shown on Bookatu's page, and limits on token and revoke 2026-11-14 · After release 17 · Breaking - Breaking for an app that read the error redirect: every mistake in an authorize request (a wrong or missing `response_type`, no PKCE, a plain PKCE method, a `resource` that is not this MCP server) is shown on Bookatu's page. No `error=invalid_request` or `error=invalid_target` callback goes back to the app. Only the `code`, and `access_denied` when the person says no, go back to its `redirect_uri`. - A parameter sent twice in an authorize request is refused on that page too, and a `code_challenge` must be 43 to 128 characters, as RFC 7636 says. - Registration refuses a `redirect_uri` with a fragment (a bare `#` too), and a registration mistake names its field. - `/api/oauth/token` and `/api/oauth/revoke` have limits of their own. Past them the answer is `429` with `error` `too_many_requests` and `Retry-After`. - A business Bookatu has suspended cannot be connected. - The same API version. /auth.md says all of it. ### Keys and connected apps Bookatu support sets up for a business 2026-11-14 · After release 17 - Bookatu support can set a business up with an API key, or connect an app for it, without being on its team. Such a credential acts on that business's behalf, with what the business's owner role could give there, or with the maker's own role once they join the team. A sandbox never gets one. - `whoami` (REST `GET /api/v1/{slug}/whoami`, and MCP) answers such a credential with `person` `{ id: null, name: "Bookatu platform owner", email: null, role }`, `role` being the role it acts with, and `credential.onBehalfOf` `{ id, name }`, the business. - The business's Developer API page and Connected apps card say who made it and on whose behalf. The owner can revoke it like any other key, and it stops at once. - Additive: the same API version. Every other key and app answers `whoami` as before. ### Website enquiries: held, not lost, when the key's scope is off 2026-11-14 · After release 17 - `POST /api/v1/{slug}/enquiries`: when the key is the business's own, live and carries `enquiries:write`, but the scope is off because of who made the key (they are not on the team, or their role lost the right), a valid enquiry is now held for the business for 30 days instead of lost. The answer is the same `403` with `missingScope` as before, held or not. Fix the key all the same: a held enquiry is not in Leads until the business moves it there. - `GET /api/v1/{slug}/enquiries/held` (`customers:read`) lists the business's held enquiries, newest first: `id`, `reason` (`maker_not_on_team`, `maker_lacks_permission` or `scope_off`), `scope`, `keyId` and `keyName`, `name`, `email`, `phone`, `tripId` and `trip`, `people`, `preferredStart`, `preferredEnd`, `message`, `reference`, `heldAt` and `expiresAt`. - `POST /api/v1/{slug}/enquiries/held/{id}/release` (`enquiries:write`) moves one into Leads as the website form would have: the same lead and the New enquiry alert. It answers `released: true`, `id`, `leadId` and `duplicate` (`true` when its reference reached Leads since, and no second lead was made). One that is not held here now is `404` with `reason` `not_found`. - MCP: `list_held_enquiries` and `release_held_enquiry`, on the same scopes. Both need the key's maker to have Manage the business, and the list Export data too, as every client read does. The in-app assistant can list them, and release one after the owner confirms it on its card. Nothing deletes a held enquiry but a person signed in, or its 30 days. - The first time a key or connected app that worked before is refused because of its maker, or a key holds a website enquiry, the business's owners and admins are told on their alerts and by email, at most once a day for each. - Additive: the same API version. ### Services: an online meeting gives its bookings the call link 2026-11-14 · After release 17 - `POST /api/v1/{slug}/services` and `PATCH /api/v1/{slug}/services/{id}` (`catalog:write`), and the MCP tools `create_service` and `update_service`: `meetingType` `online` now also gives the service's bookings a Google Meet link, when the business has Google connected and video meetings on. Any other `meetingType` stops it. `null`, or leaving `meetingType` out, leaves it as it was. - The service editor works the same way: How clients meet you is its one control for this, so a service set up there and one set up through the API behave alike. - Same API version: no field is added or removed, and a service nobody changes keeps what it had. ### Client messages: Send now on a held message 2026-11-14 · After release 17 - `POST /api/v1/{slug}/client-messages/held/{id}/send` (`messages:write`) sends one message the business's switches held, now, as the team pressing Send now on Settings, Client messages. `{id}` is a held message's `id` from `GET /client-messages/held`. Only that message goes, on its own channel: an email sent this way leaves its held text held. The switches stay as they are. - It answers `sent: true` with the message's `id`, `key`, `type`, `name`, `channel`, `appointmentId` and `customerId`, and `alreadySent`: `true` when it had already gone, by an earlier press, and nothing more was sent. A message that is not held here (another business's, or one that was never held) is `404` with `reason` `not_found`; one too late to send (its day has passed, or the booking was cancelled or moved) is `422` with `too_late`; one with nowhere to go (no email address or number, or messages are off for the client or the booking), or a text the text service would not take, is `422` with `not_sent`; a held text the business cannot send now (its texts are off or not on its plan, or Bookatu's numbers do not send that text) is `422` with `texts_off`; one an earlier press is still sending is `409` with `in_flight`, to check again in a moment, and nothing more is sent (a send that never finished is let go after 15 minutes); a send that fails for a moment is `500` with `send_failed`, to try again. Each in the words Settings shows. - MCP: `send_held_client_message`, on the same scope, with the same answers and refusals. `dryRun: true` sends nothing and answers what the real call would now: the message it would send, or the same refusal. It names the client only to a key that can also read clients (`customers:read`). Each real send is in the business's audit log. - The in-app assistant can send one too, only after the owner confirms it on its card. It never changes the switches. - Keys that already have `messages:write` can now send a held message too, with nothing to change on the key. On the Developer API page the scope is now called "Change which messages clients get, and send held ones", and its description says so. - Additive: the same API version. A held message is still never sent later by itself. ### Services: how clients meet you, and a notice of their own 2026-11-14 · After release 17 - `POST /api/v1/{slug}/services` and `PATCH /api/v1/{slug}/services/{id}` (`catalog:write`), and the MCP tools `create_service` and `update_service`, take `meetingType`: `place`, `venue`, `client`, `online`, `trip` or `none`, or `null` to work it out from the service. They also take `noticeHours`, the service's own notice to cancel or change for free, a whole number from 0 to 8760, or `null` for the business's free cancellation window. - `PATCH /services/{id}` and `update_service` also take a trip's `destination` (one line, up to 120 characters) and `itinerary` (its days in order, each `{ title, note? }`, never more days than the trip lasts). Both are for a trip only, a service that lasts whole days. On any other service, and on every new service, they are refused with `422` and `fieldErrors` naming the field. `null`, `""` and `[]` clear them. - A value the service editor would refuse is refused the same way, in its words, with `422` and `fieldErrors` (MCP: Invalid params naming the field). Their answers carry the four fields as stored, `null` when unset. - `GET /services`, `GET /services/{id}` and the MCP tool `list_services` say on every service `meetingType` (as its booking page tells clients, `null` when nothing says) and `noticeHours` (the notice a booking of it needs: its own, else the business's window). - `GET /booking/{id}`: `policy.cancellationWindowHours` is now the booking's own notice, its service's when the service has one, else the business's window as before. - Additive: the same API version. A service with no notice of its own answers exactly the window it did. Treat a `meetingType` you do not know as `null`. ### Client messages: read and change which messages a business's clients get 2026-11-14 · After release 17 - `GET /api/v1/{slug}/client-messages` (`messages:read`) answers the business's client message switches: `manualOnly` (Only send client messages when we press Send) and `types`, each message with its `key`, `name`, `trigger`, whether it can be switched off, and `on` and `default` for each of its channels, `email` and `sms`. - `PATCH /api/v1/{slug}/client-messages` (`messages:write`) changes them, with a body such as `{ "manualOnly": true }` or `{ "types": { "": { "sms": false } } }`. An unknown type or channel, a value that is not `true` or `false`, and a message that cannot be switched off answer `422` with `fieldErrors`. Sending what is already so changes nothing. Each change is in the business's audit log. - `GET /api/v1/{slug}/client-messages/held` (`messages:read`) lists the messages the switches held, newest first: `key` (the switch key `PATCH` takes), `type` (the send's own name, for example `reminder_24h` for the key `reminder`), `name`, `channel`, `reason` (`manual_only` or `switched_off`), `heldAt`, `appointmentId` and `customerId`. Automatic replies and missed-call texts the switches paused are listed too. Never an address and never a message's words. A held message is never sent later. - MCP: `get_client_messages`, `set_client_messages` and `list_held_client_messages`, on the same scopes. Both scopes are opt-in and need Manage the business: a key has them only when its maker ticks them. - `POST /api/v1/{slug}/appointments` answers `clientMessage`, what became of the confirmation: `sent` (sent, or going out just after the answer), `pending` (its text waits for quiet hours), `held` (the business's switches held it, or the business is in test mode or not live yet), `not_sent` (no email address and no text) or `off` (`notifyClient` was `false`). `notifyClient: true` sends the confirmation as a press, whatever the switches say; left out, it follows them. - `POST /api/v1/{slug}/booking-requests/{id}/decline` and MCP `decline_booking_request` take `notifyClient`: `true` emails the client the decline even while the business's switches would hold it; left out, the email follows them. - Additive: the same API version. A business that changes nothing gets every message as before. ### Keyed bookings held to open slots, the deposit policy on keyed cancels, and the manage link's own limit 2026-11-12 · After release 17 · Breaking - `POST /api/v1/{slug}/appointments` and `POST /visits` with a key are held to the business's open slots: inside its opening hours, not in the past, no further ahead than its clients can book, and free. Otherwise the answer is `409` and nothing is written, the client included. A key made with the new opt-in `bookings:override` scope (Book at any time) books as Book anyway does on the calendar, for importing bookings from another system. - `POST /appointments/{id}/cancel` follows the business's deposit policy, as when the client cancels: inside the notice window a paid deposit is kept and `forfeited` is `true`. Send `refundDeposit: true` to refund it whatever the policy says. - `429` with `Retry-After` can now also come from the key's booking window (each visit of a repeat counts), a day of bookings made through the business's keys and connected apps, a burst of keyed cancels or time blocks, and on `POST /booking/{id}/reschedule` and `POST /booking/{id}/cancel` from the manage link's own limit, the same one the manage-booking page has. Nothing is booked, moved or cancelled. - Keyed time blocks stop at the business's booking horizon. - The same API version: every version gets these at once. ### Checkout from another point of sale: a card number in the sale id or the point of sale's name is refused 2026-11-12 · After release 17 - `POST /api/v1/{slug}/appointments/{id}/checkout` (`checkout:write`) refuses a body whose `externalSaleId` or `source` looks like a card number, with `400` and `reason` `card_number`. `fieldErrors` names the field and never repeats the number. Nothing is recorded. - Card numbers are never accepted there. Send your point of sale's own sale id, and its name such as `moneris_mgr`. An `externalSaleId` with spaces was already refused with `422`; one that looks like a card number now answers `400` instead. - Additive: the same API version. A body with no card number in either field posts exactly as before. Treat a `reason` you do not know as a sale that was not recorded. ### Docs MCP server: get_plans 2026-11-11 · After release 17 - The docs MCP server has `get_plans`: the public plans and prices, the add-ons and the trial length, the same facts as /pricing. It takes no arguments, needs no key, and is read-only and idempotent. - Each plan comes with its monthly price billed monthly and billed yearly, how many active clients it covers (`null` is no limit), and the line /pricing shows under its name. Every plan takes unlimited staff. - Additive: the same API version. ### MCP: load only some tool families with ?toolsets=, and longer server instructions 2026-11-11 · After release 17 - The business MCP server takes `?toolsets=` with the tool family ids from /developers (`booking`, `commerce`, `blog`, `forms`, `campaigns`, `storefront`, `reports`, `webhooks`, `classes`, `audit`), for example `/api/mcp?toolsets=booking,classes`. Only those families are listed by `tools/list` and callable by `tools/call`, plus the help tools and `get_business`. - It only narrows: the key's scopes still decide what a connection reaches. A call to a tool outside the loaded families is the unknown-tool error `-32601` with `data.code` `NOT_IN_TOOLSET`. A name that is not a family is refused with `-32602`, naming the valid ones. With no `toolsets`, nothing changes. `whoami` says which toolsets a connection loaded. - `initialize`'s instructions now also say to call `get_business` first, to find ids with `search` or a list tool, to preview a change with `dryRun`, and which of `create_booking`, `create_visit` and `add_class_attendee` fits which case. - Additive: the same API version. ### MCP: bad arguments the model can correct, and idempotentHint on every write 2026-11-11 · After release 17 - On protocol 2025-03-26 or later (the `MCP-Protocol-Version` header), arguments a tool cannot read come back as a tool result with `isError: true` and `error.code` `INVALID_PARAMS`, with the same message as before and `fieldErrors` naming each argument, so the model can correct them and call again. This applies to the business server and the docs server. - A client that sends no such header sees no change: bad arguments are still the JSON-RPC error `-32602` with the same message. A missing scope, a read-only credential, a rate limit and an unknown tool stay JSON-RPC errors on every version. - Every write tool now says `idempotentHint` in its annotations: `true` on the writes that change nothing more when called again with the same arguments (`cancel_booking`, `cancel_visit`, `cancel_class_place`, `mark_class_attendance`, `clear_walk_in_wait`, `stop_deposit_request`, `forms_attach_to_service`, `forms_detach_from_service` and `rename_service_category`), `false` on the rest. Read tools are unchanged. To retry any write safely, send the same `idempotencyKey`. - The same API version. How an MCP error comes back follows the MCP protocol version your client sends in `MCP-Protocol-Version`, not `Bookatu-Version`, as tool errors already did: that header, not a new API version, is how a client keeps the old shape. This is the one place the versioning policy defers to the MCP protocol version. ### A Request-Id on every answer 2026-11-11 · After release 17 - Every answer of the REST API and the MCP servers carries a `Request-Id` header, an id for that one call (`req_...`). Quote it when you report a problem, so the call can be found. Error answers carry it too, including the ones sent before your call reaches an endpoint, such as `LIVEMODE_MISMATCH` and `UNSUPPORTED_API_VERSION`. - A call that fails on our side is answered a 500 with the `Request-Id` too: `{ ok: false, error: "Internal server error" }` on the REST API, and a JSON-RPC internal error (`-32603`) on the MCP servers. It never says what went wrong inside: quote the id instead. - Browsers may read it: it is listed in `Access-Control-Expose-Headers`. The OpenAPI document names it on every response. - The id is made by Bookatu for each call. A `Request-Id` header you send is ignored. - Machine error codes for the common refusals are planned separately. - Additive: the same API version. A client that ignores headers it does not know sees no change. ### Safe retries on POST /book and POST /visits/book 2026-11-11 · After release 17 - `POST /book` and `POST /visits/book` take an optional `Idempotency-Key` header, 16 to 64 visible characters. A retry with the same key, client email and body within 24 hours answers what the first call answered, with `idempotentReplay: true` and the `Idempotent-Replayed` header, and books nothing more. Send a new key for each booking, and the same key when you send that booking again after a timeout. - A key is held per client email, so two people who send the same key never get each other's answer. The same key and email with a different body is refused with 400 `IDEMPOTENCY_MISMATCH`, as is a key that is not 16 to 64 visible characters, and nothing is booked. A retry while the first call is still running is 409 `IDEMPOTENCY_IN_PROGRESS` with `Retry-After`. - A replay does not carry `manageKey`: the client has it in their confirmation email. - Browsers may send the header: both endpoints allow it in CORS. - Additive: the same API version. Without the header both endpoints behave exactly as before. ### Webhook event ids, booking ids in payloads, and the retry schedule written down 2026-11-11 · After release 17 - Every webhook body now starts with `id` (`evt_...`), and the new `X-Bookatu-Event-Id` header carries the same value. One event has one id: the same on every endpoint it goes to and on every retry of it, so a receiver can skip a delivery it already handled. A Send test event has its own id too. - `booking.created`, `booking.cancelled`, `booking.completed` and `booking.rescheduled` add `staffId` (null when nobody is assigned) and `customerId`, and `locationId` (null for a business with one address). A move sends who has the booking now. Ids only: still no names or contact details. - The docs said up to 3 attempts. In fact a delivery whose first 3 attempts fail is queued and tried up to 10 more times over several hours, and `X-Bookatu-Attempt` runs from 1 to 13. The docs now say so. - Additive: the same API version. A receiver that ignores fields and headers it does not know sees no change. ### Website enquiries: send your own form's enquiries into Leads 2026-11-11 · After release 17 - `POST /enquiries` takes one enquiry from a business's own website form, sent from its server (or through a tool such as Zapier). It lands in Leads as an enquiry, whether or not the business has a public page. It is not a client or a booking until the team books them in, and Bookatu emails and texts nobody about it. - Send an `email`, a `phone` or both. Every other field is optional, and fields it does not know are ignored. A new enquiry answers 201 with its `id`. Send a `reference` too, your form's own id for the entry: the same `reference` again answers 200 with the first enquiry's id and `duplicate: true`, so a retry never makes a second one. - To link an enquiry to a trip, send its `tripId` as `GET /enquiries/trips` lists it: each active trip's code, name and number of days, in the business's own order. Or send the trip's name as `trip`. It is matched to one of the business's trips, and kept as written when nothing matches. A business with no trips sends what the enquiry is about as `trip`. - A wrong field, or neither an email nor a phone, is 422 with `fieldErrors` naming each field, and nothing is kept. - Both need a key with the new `enquiries:write` scope (Add enquiries). It is opt-in: no key made before it has it. A test copy takes its own `bk_test_` key, and its enquiries stay in its own Leads. - Additive: the same API version. ### The public booking MCP server, for people's own AI assistants 2026-11-06 · After release 17 - A third MCP server, at `https://bookatu.com/api/mcp/book`, for an assistant helping a person book, with no key and no sign-in. It looks up a business from its booking link with `get_business`, reads its services with `list_services` and its free times with `check_availability`, and holds one with `hold_booking`. - Nothing is booked until the person confirms by email: Bookatu emails them a code and a link, and the assistant passes the code to `confirm_booking`, or the person opens the link. `get_booking_status` says where a hold stands, and `release_hold` lets one go. - Only a business that chose to take bookings from assistants can be held. A service an assistant cannot hold, one that takes a deposit for example, comes back with the business's booking page to send the person to. - Its card is at `https://bookatu.com/api/mcp/book/server-card`, and the same tools are REST endpoints under `/api/v1/{slug}/agent` for an assistant that cannot use MCP. `find_businesses` is listed while the directory of businesses that chose to be found is open. Additive: nothing changes on the REST API, the business MCP server or the webhooks. ### REST: an endpoint for each MCP tool, the help tools, approvals, Idempotency-Key and dryRun 2026-11-06 · After release 17 · Breaking - The REST API serves an endpoint for each MCP tool that had none, under `/api/v1/{slug}`: products and stock, services, blog posts, forms, campaigns, reports, webhooks, time blocks, booking and client notes, clients, point-of-sale sales and storefront notices among them. Each asks the same scope as its MCP tool and the same of the person who made the key, and answers as the tool does. A list answers one page at a time, with `limit`, `cursor` and `nextCursor`. - The help tools are on REST too: `GET /whoami`, `GET /search`, how do I, open in Bookatu, get help and `GET /approvals/{id}`. Any key of the business may call them, with no scope. - A change that needs a person's approval answers `403` with `code` `APPROVAL_REQUIRED`, an `approvalId` and the link where someone at the business approves it. Call again with the same body and that `approvalId` (or the `Bookatu-Approval-Id` header). The other refusals are `APPROVAL_PENDING`, `APPROVAL_DECLINED`, `APPROVAL_USED`, `APPROVAL_EXPIRED`, `APPROVAL_MISMATCH` (another key asked for it) and `APPROVAL_NOT_FOUND` (`404`). - Every keyed write takes an `Idempotency-Key` header, 1 to 200 printable characters with no spaces: a retry with the same key and body within 24 hours answers what the first call answered (`Idempotent-Replayed`). The same key with another body is `409` `IDEMPOTENCY_KEY_REUSED`; while the first is still running, `409` `IDEMPOTENCY_IN_PROGRESS`; a key that cannot be used, `422` `INVALID_IDEMPOTENCY_KEY`. - `dryRun` (in the body, or `?dryRun=true`) is honoured on every write: it changes nothing and answers what the call would do and who would be told. - New opt-in scopes, carried only by a key made with them ticked: `customers:manage` (add and change clients), `pos:write` (record sales at the point of sale) and `marketing:write` (post storefront notices). - `/api/tools/openapi.json` is an OpenAPI 3.1 file of these endpoints, generated from the tool registry. `/api/openapi.json` still has the whole API. - Breaking on the endpoints the API had before for an MCP tool: a key made before scopes whose maker lost the right, or left the team, now gets `MAKER_LACKS_PERMISSION` or `MAKER_NOT_ON_TEAM` there, as on MCP, and a key whose maker sees only their own calendar column gets another column's booking answered as an id the business does not have. A key that records nobody keeps its access level. ### Checkout from another point of sale: invoiced, a new checkout.blocked value and 409 reason 2026-11-05 · After release 17 - A business can now put a booking on an invoice, which is how that booking is then paid. `GET /api/v1/{slug}/appointments/{id}/checkout` (`checkout:read`) answers `checkout.allowed: false` with `checkout.blocked` `invoiced` for a booking on a live invoice, or a visit with one of its bookings on one. Do not take money for it at your point of sale. - `POST /api/v1/{slug}/appointments/{id}/checkout` (`checkout:write`) refuses such a booking with `409` and `reason` `invoiced`, naming the invoice in its message. Nothing is recorded. - Additive: the same API version. Treat a `checkout.blocked` or `409` reason you do not know as a booking you cannot check out. A booking that is on no invoice, which every booking was before this change, reads and posts exactly as before. ### Stripe test mode for test businesses: paymentsMode on the test payments reads, and 409 STRIPE_TEST_MODE from the simulator 2026-11-04 · After release 17 - A test business (a sandbox or a test copy) can take its payments through Stripe test mode instead of the simulator, where Bookatu offers it. Its owner connects a Stripe test account on the Test payments page and turns Stripe test mode on there. New checkouts then open Stripe's own checkout page, and card steps show Stripe's card form on the booking page. Both take Stripe's test cards such as `4242 4242 4242 4242`, and no real money moves. Those payments are listed in the business's Finance, not under Test payments. - `GET /api/v1/{slug}/sandbox/payments` and the `sandbox_payments` MCP tool carry `paymentsMode` after `nextCursor`: `simulated`, or `stripe_test` while the sandbox's new payments go through Stripe test mode. Both still list the simulated payments only, and the two answers stay the same as each other. - `POST /api/v1/{slug}/sandbox/simulate/{event}` and the `sandbox_simulate` MCP tool answer `409` with `code: "STRIPE_TEST_MODE"` for `deposit.paid`, `payment.failed` or `checkout.expired` on a booking whose checkout is in Stripe test mode, and for `deposit.paid` or `payment.failed` on a booking that still owes its deposit online and has no open test checkout while new payments go through Stripe test mode. A booking that takes no deposit online, or whose deposit is paid, still answers `NO_OPEN_CHECKOUT`. Over MCP it is refused as the simulator's other refusals are, with the code `STRIPE_TEST_MODE`. Pay on Stripe's checkout page with a test card instead. A booking with its own simulated checkout runs as before. - Additive: the same API version. Nothing changes for a test business on simulated payments, which every one is until its owner turns Stripe test mode on, or at a live business. ### MCP: each tool asks what its dashboard screen asks of the key's maker 2026-11-03 · After release 17 · Breaking - On the business MCP server, each tool now asks the person who made the key, or approved the connected app, what its own screen in the dashboard asks on the business's Role permissions, as well as the key's scope. A catalog or blog write needs Manage the business, for example, and `forms_list_responses` needs Export data. A call their role does not allow is `403` with `error.data.code` `MAKER_LACKS_PERMISSION` and the permission it needed; once they leave the team it is `MAKER_NOT_ON_TEAM`. `tools/list` leaves out the tools they would be refused. - A key made before scopes that records who made it is held to that person the same way. One that records nobody keeps its access level. - The tools that act on one booking or visit are held to that person's own calendar column: another column's booking is answered as an id the business does not have. - `create_booking` takes `asStaff`: the booking is made as the team makes it (a service that takes a deposit is booked and never held for one, and team members kept off the booking page can be booked). It needs the maker to have Edit the calendar, and the time must still be free (`BOOKING_REFUSED`). A key that records nobody cannot use it: `AS_STAFF_NEEDS_MAKER`. - Breaking for a key whose maker's role lacks a tool's screen right, or who left the team: calls that worked before are now refused. The same API version. ### Trips that span days: startDate, endDate and days on POST /appointments and the appointment reads 2026-11-02 · After release 17 - A service can last whole days (1 to 60) instead of minutes: a trip. `POST /appointments` (`bookings:write`) books one by its days, `startDate` (`YYYY-MM-DD`, the business's calendar) with `endDate` (inclusive) or with `days`, instead of `startAt` or `localTime`. It covers those days in full on the business's clock, whatever the clocks do in between, is priced once per booking, holds its person (or nobody, without `staffId`) and the resources its service needs for every one of them, takes no extras and does not repeat. The answer has `startDate`, `endDate` and `days`. - Refused with `422` naming the field, nothing booked: a time for a service of days, a date that is not real `YYYY-MM-DD`, no `endDate` or `days`, an `endDate` before `startDate`, `endDate` and `days` together, more than 60 days, a `repeat`, or any of the three for a service of minutes. `409` when the trip's person is already booked on those days, or no resource of a kind it needs is free on them. - `GET /appointments` and `GET /appointments/{id}` carry `startDate`, `endDate` and `days` on a trip, after `notifyClient`; every other booking reads exactly as before. - Only the business books a trip: the keyless doors (`GET /services`, `GET /availability`, `POST /book`, `POST /visits/book`) never list or book a service of days. Additive: the same API version, and nothing changes for a service of minutes. ### A sandbox's test payments: GET /sandbox/payments and the sandbox_payments MCP tool 2026-11-02 · After release 17 - `GET /api/v1/{slug}/sandbox/payments` lists every payment a sandbox made in test mode, newest first, as its admin's new Test payments page (beside the Outbox) does: checkouts, the payments they made, card holds, no-show charges and refunds (`kind`), each with its `outcome` (`paid`, `declined`, `abandoned`, `open`, `card_saved`, `refunded` or `partly_refunded`), `amountCents` and `currency`, `refundedCents`, `description`, the booking it belongs to (`appointmentId`) and the booking or sale (`belongsTo`), its checkout and payment ids, and when it was made. Nothing in it names a client. - Filter with `kind` and `since`, and page with `limit` (1 to 100) and `cursor`, as on `GET /sandbox/outbox`; a filter that is not valid is `422` with `fieldErrors`. It takes a sandbox's test key with `reports:read`, the money reports' scope, and allows 30 calls a minute per sandbox and per key. A live business answers `404` with `code: "NOT_A_SANDBOX"`, and a key of the other mode `403` with `code: "LIVEMODE_MISMATCH"`. - At a sandbox, the business MCP server's `tools/list` adds `sandbox_payments` after `sandbox_outbox`, for a credential with `reports:read`: the same payments, filters, cursor and limits, read-only and idempotent, with an `outputSchema`. A live business never lists it, and its `tools/list` is unchanged. - Additive: the same API version, and nothing changes at a live business. ### Quiet bookings: notifyClient on POST /appointments and the appointment reads 2026-11-02 · After release 17 - `POST /appointments` (`bookings:write`) takes `notifyClient`. `false` makes a booking whose client Bookatu never messages, by email or text: no confirmation, booking request or decline, reminder, ask to confirm, thank-you or review request, move or cancellation notice, deposit or payment request, "did you make this booking?" check or Quick swap message. The team's own alerts and the webhooks are unchanged, and marketing still follows the client's own consent. A series (`repeat`) made with it is quiet on every visit. `true`, or left out, is the usual booking. - Anything but `true` or `false` is `422` with `fieldErrors.notifyClient`, and so is `notifyClient: false` with `requestDeposit: true`, since the pay link is sent to the client. Nothing is booked. - `GET /appointments` and `GET /appointments/{id}` carry `notifyClient` on every booking, after `createdAt`. `POST /appointments/{id}/deposit-request` answers `409` with `reason: "client_messages_off"` for a booking whose client is not messaged, and makes no link. - The keyless doors (`POST /book`, `POST /visits/book`) do not take `notifyClient`: a booking made there always tells the person who booked. Additive: the same API version, and nothing changes for a booking made without it. ### Walk-in wait time: GET /walk-in, PUT and DELETE /walk-in/manual, and three MCP tools 2026-11-02 · Release 17 - New keyless `GET /walk-in`: the live walk-in wait of a business (`status`, `mode`, `state`, `waitMin`, `nextAt`, `updatedAt`, `timeZone`, `manual`, `closed`, `busy` counts and each walk-in service with its `bookUrl`), the same answer as its booking page, its walk-in widget and MCP give for the same moment, kept about a minute. A business with it off answers `{ "status": "off" }` with no numbers, and a `serviceId` that is not one of its walk-in services is 404 `SERVICE_NOT_FOUND`. Counts only: no client or team member is ever named. - New `PUT /walk-in/manual` (`minutes` 0 to 240 or `notTaking: true`, and `expiry` `1h`, `2h` or `end_of_day`) and `DELETE /walk-in/manual`, for a key with `bookings:write`: the wait set by hand until it lapses, and back to the automatic wait (`cleared`). `PUT` answers 409 `WALK_IN_OFF` while walk-in wait times are off. Each set and clear is in the audit log, naming the key. - Three MCP tools after `get_business`: `get_walk_in_wait` (`availability:read`, the same rule as `get_availability`, with `message` beside `status: "off"`), and `set_walk_in_wait` and `clear_walk_in_wait` (`bookings:write`). - New error codes `SERVICE_NOT_FOUND` and `WALK_IN_OFF`. Additive: the same API version, and nothing changes for a business that never turns walk-in wait times on. ### MCP create_booking and create_visit take the person's answers to the business's booking questions 2026-11-02 · Release 17 - `create_booking` and `create_visit` take an optional `answers` object, `{ [questionId]: answer }`: the person's answers to the business's booking questions, with the same shape, validation and limits as `answers` on `POST /book` (for a visit, each question once for the whole visit). Until now neither tool took answers, so a service with a required question could not be booked over MCP at all. - `list_services` lists each service's booking questions as `questions`, in the order they are asked, exactly as `GET /services` does. A business that asks none lists none, so its answer is unchanged. - A required question left out is refused with `ANSWERS_REQUIRED` and `missingQuestionIds`, an answer that cannot be read with `ANSWERS_INVALID` and `invalidAnswers`, and nothing is booked, with `bookingPageUrl` beside them as before. The message now tells the agent to ask the person the questions and send their answers, or to send the person to `bookingPageUrl`. - The answers are kept for the business only: never echoed back in a tool result and never in a webhook payload. Additive: the same API version. ### MCP create_booking and create_visit refuse a service that takes a deposit, with the booking page to send the customer to 2026-10-31 · Release 15 hotfix · Breaking - Over MCP, `create_booking` and `create_visit` no longer book a service (or a visit) that takes a deposit. They refuse it with `code: "DEPOSIT_NEEDS_BOOKING_PAGE"` and `bookingPageUrl`, the business's booking page (opened on the service for `create_booking`), where the customer books it and pays the deposit, as `POST /book` and `POST /visits/book` do. Nothing is written: no booking, no held slot, no client record and no message. - The refusal is a tool error (`isError: true`, `structuredContent.error` with `code`, `message` and `bookingPageUrl`; no `livemode` there, as on every refusal: it is in `result._meta`) for a client that sends a 2025 `MCP-Protocol-Version` header, and the JSON-RPC error with `code` and `bookingPageUrl` in `error.data` otherwise. A sandbox answers the same, with its test key. - There is no `payLink` in either tool's answer any more. Before this change such a booking was made `pending` and answered with a `payLink` to the booking's success page, which takes no payment, so the customer could not pay and the slot was held until it was released. A service that takes no deposit books exactly as before, and the team's REST `POST /appointments` (with `requestDeposit`) is unchanged. - At a business whose booking page is not published yet, `bookingPageUrl` shows the customer a coming soon page until the owner publishes it, so the refusal there also carries `bookingPagePublished: false`, and its message says to publish the booking page first. - Marked breaking, as the same change to `POST /book` was (2026-10-29), yet given to every version at once rather than held for a new one: the `payLink` opened a page that takes no payment, so there is no working behaviour for an older version to keep. ### The business MCP server at a sandbox: three test tools, livemode in structuredContent, and LIVEMODE_MISMATCH 2026-10-30 · Release 15 - At a sandbox, `tools/list` adds three tools after the rest, each only for a credential that may call it: `sandbox_outbox` (`customers:read`: the test outbox, as `GET /sandbox/outbox` answers it), `sandbox_simulate` (`bookings:write`: the six events of `POST /sandbox/simulate/{event}`, for the sandbox's own bookings only) and `sandbox_reset` (the sandbox's own `bk_test_` key with `bookings:write`, never a connected app). Each shares its REST twin's limits. A live business never lists them, and its `tools/list` is unchanged. - Every successful tool result says `livemode` in `structuredContent` (`false` at a sandbox, `true` at a live business), and a write now answers with `structuredContent` too: its text's JSON plus `livemode`. The text block is unchanged. A refusal (`isError`) has no `livemode` in `structuredContent`; `result._meta["com.bookatu/livemode"]` says it on every tool result, and the `Bookatu-Livemode` header on every answer. - Over MCP, a credential of the other mode than its business, or a call whose `Bookatu-Livemode` header names the other kind, is refused before anything runs: `403`, the JSON-RPC error `-32000`, with `error.data.code: "LIVEMODE_MISMATCH"`, `keyLivemode` and `businessLivemode`. - A guide to testing an AI agent against a sandbox, from Claude Desktop, Cursor or the MCP Inspector: `/developers/testing-ai-agents`. ### Version 2026-10-30: API versions, rate-limit headers and test mode 2026-10-30 · Release 15 · version `2026-10-30` - The first named API version, `2026-10-30`. Send `Bookatu-Version: 2026-10-30` to ask for it; every answer says the version it was answered in, in `Bookatu-Version`. Every key and connected app made before this release is pinned to it, and a new one is pinned to the version current when it is made. - A `Bookatu-Version` that is not a version the API answers in is refused before anything runs: `400` with `code: "UNSUPPORTED_API_VERSION"` and `supportedVersions`. - Every answer of the v1 API and the MCP servers carries `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` for the window closest to its limit, and `RateLimit-Policy` naming every window the call was counted against; every `429` carries `Retry-After`. A browser may read all of them (`Access-Control-Expose-Headers`). - Each key is now also counted on its own, at its plan's numbers, beside its business's keys together: a key on the standard tier, every key unless Bookatu changes it, sees no change, and a call refused before the endpoint counts it (a missing scope, another business's key) is not counted on the key, as before. A Bookatu platform admin can put a live key on the raised tier. - Test mode: sandbox businesses with sample data and `bk_test_` keys. Every JSON answer says `livemode` (`true` at a live business, `false` at a sandbox) and every answer the `Bookatu-Livemode` header; a test key at a live business, or a live key at a sandbox, is `403` with `code: "LIVEMODE_MISMATCH"`, and a sandbox-only call at a live business answers `code: "NOT_A_SANDBOX"`. - The optional request header `Bookatu-Livemode: false` (or `true`) says which kind of business a call means to reach: a call to a business of the other kind is `403` with `code: "LIVEMODE_MISMATCH"` before anything runs, so a front end on the keyless endpoints built against a sandbox can never book at a live business. Browsers may send it. - Sandboxes are made, listed, reset and deleted with the developer account API, `/api/developer/sandboxes`, signed in with a Bookatu login (never an API key); making one needs `acceptTestModeTerms: true`. A sandbox's own test key with `bookings:write` may reset that sandbox, so CI needs no login. - `GET /sandbox/outbox` lists what a sandbox would have sent (kept, never sent), and `POST /sandbox/simulate/{event}` makes `deposit.paid`, `payment.failed`, `checkout.expired`, `booking.client_cancelled`, `booking.no_show` or `reminders.due` happen to one of its bookings. Both answer at a sandbox only, with its test key. - Every webhook payload has a top-level `livemode` field, and every delivery the `X-Bookatu-Livemode` header; a connected app's token answer says `livemode` too. ### Booking questions 2026-10-30 · Release 14 - `questions` on `GET /services`, `GET /services/{id}` and `GET /business`: the questions a business asks when someone books. - `answers` on `POST /book` and `POST /visits/book`. A required question left unanswered is `422` with `code: "ANSWERS_REQUIRED"` and `missingQuestionIds`; an answer of the wrong type or length is `422` with `code: "ANSWERS_INVALID"` and `invalidAnswers`. Nothing is booked. - A service that cannot be booked online is refused as an unknown one before its questions are checked, so a hidden service's questions are never named. ### Client and booking tags 2026-10-30 · Release 14 - `tags` on `GET /customers`, `GET /appointments` and `GET /appointments/{id}`. - `POST` and `DELETE` `/customers/{id}/tags` (the new opt-in `customers:write` scope) and `/appointments/{id}/tags` (`bookings:write`) put the business's tags on a client or a booking and take them off. - The business MCP server's `list_customers` does not name tags; the keyed REST reads do. - Webhooks: `campaign.sent`'s `audience` may now be `tag`, for a campaign sent to the clients with a tag, beside `all`, `recent`, `lapsed` and `vip`. It never says which tag (tags are the team's internal labels). A receiver that checks `audience` against a fixed list should add `tag`. ### Surcharges on public holidays and busy times 2026-10-30 · Release 14 - A slot at a time the business charges more for carries `priceCents` (the price before the surcharge), `surcharges` (`label`, `amountType`, `amount`, `amountCents`) and `totalCents`; every other slot has none of these fields. - A booking made at such a time is priced at its `totalCents`, and its answer carries `surcharge: { label, amountCents }`. The business MCP server's availability tools say the same. ### Card holds and booking terms on the keyless doors 2026-10-30 · Release 13 - A service the business requires a card saved to hold is refused on `POST /book` and `POST /visits/book` with `409` and `code: "CARD_REQUIRED_USE_BOOKING_PAGE"`, with the `bookingPageUrl` to send the person to; nothing is booked. - A business that has set booking terms needs `acceptTerms: true` on `POST /book` and `POST /visits/book`; without it the answer is `422` with `code: "TERMS_NOT_ACCEPTED"` and the terms to show. ### Website widget events, version 1 2026-10-30 · Release 13 - The website widget dispatches `bookatu:` browser events and `bookatu_` dataLayer events (ready, service_selected, staff_selected, time_selected, booked, request_sent, handoff, error, closed) with a payload marked `v: 1`, carrying a booking reference rather than the appointment id; deep links (`data-date`, `data-promo`, `data-lang`, `data-staff`, `data-branch`), a pinned loader `/embed.v1.js` and an allow-list of the sites that may frame it. ### Manage keys: the appointment id alone no longer changes a booking 2026-10-29 · Release 12 · Breaking - A booking made from this release on carries a manage key: `POST /book` and `POST /visits/book` answer `manageKey`, and the client's emailed links carry it as `k`. - The `/booking/{id}` calls take it as `?k=` or the `X-Manage-Key` header. With the id alone, `GET /booking/{id}` answers a read-only status (`access: "view"`), and availability, reschedule and cancel answer `403` with `code: "MANAGE_KEY_REQUIRED"`. A booking made before keeps being managed on its id alone. ### localTime on the keyless doors 2026-10-29 · Release 12 - `POST /book`, `POST /visits/book` and `POST /booking/{id}/reschedule` take `localTime` (with an optional `timeZone`) instead of `startAt`; a `TIME_NEEDS_OFFSET` refusal now points to it. ### Webhook delivery and OAuth refresh tokens 2026-10-29 · Release 12 - Every webhook delivery, retry and test event resolves the endpoint's name and is refused if any of its addresses is loopback, private, link-local or otherwise reserved, then connects to the address it checked. Redirects are never followed: a `3xx` is a failed delivery. - A connected app's code is spent, and its refresh token rotated, in one step: a refresh token used twice is a replay, and the whole token family is revoked. ### Rate limits enforced by default 2026-10-29 · Release 11 · Breaking - The API, MCP and booking limits are enforced by default: a call past one is refused with `429` and `Retry-After`. Until this release they were only logged, and every call went through. - `POST /api/oauth/register` has limits of its own: 20 registrations per address a day and 2,000 a day across everyone. ### The business MCP server: protocol versions, annotations, times and get_business 2026-10-29 · Release 11 - The business MCP server negotiates `2025-06-18`, `2025-03-26` and `2024-11-05`, answers `ping`, `-32601` for an unknown method and any `notifications/*` with `202` and no body (never counted against the key). Tools carry titles and annotations, read tools an `outputSchema` and `structuredContent`; with a 2025 `MCP-Protocol-Version` header a tool's own refusal is a result with `isError` and `error.code`. - `get_business`; `timeZone` and `When` objects on the reads; `create_booking` and `reschedule_booking` answer `when`. Public text carrying someone else's email or phone is refused with `PUBLIC_TEXT_CONTAINS_CONTACT_DETAILS`. - `get_availability` and `get_visit_availability` answer compactly: `timeZone` once, each slot's `local` time, and an optional, strictly checked `clientTimeZone`. ### Connected apps see client contacts only by consent 2026-10-29 · Release 11 - A connected app gets `customers:read` only when the owner ticks the client-contacts box on the consent page. Connections approved before keep exactly what they had. ### The keyless booking doors hardened 2026-10-29 · Release 10 · Breaking - `POST /book` and `POST /visits/book` take at most 5 bookings per address per business in 10 minutes and 15 a day, and 40 a day per business from every address together. One more is refused with `429` and `Retry-After`, and nothing is booked. - A service that takes a deposit is refused with `409` and `code: "DEPOSIT_NEEDS_BOOKING_PAGE"` and `bookingPageUrl`; `payLink` is no longer in the answer of `POST /book`. - `startAt` is read strictly, as RFC 3339 with its offset: a time with no offset is `422` `TIME_NEEDS_OFFSET` with an example, anything else unreadable `422` `TIME_INVALID`. A paused business answers `BOOKING_PAUSED`. ### Times and zones: when, localTime and clientTimeZone 2026-10-29 · Release 10 · Breaking - `GET /availability` and `GET /visits/availability` give each slot a `when` object and say `timeZone` and `datesAreOn`, and take `clientTimeZone`. `POST /book` and `POST /visits/book` take `clientTimeZone` (an abbreviation or offset is `422` `UNKNOWN_TIME_ZONE`) and answer `when`; `GET /booking/{id}` answers `when`. - `POST /appointments`, `POST /visits` and `POST /visits/{id}/reschedule` take `localTime` and refuse a time with no offset; a wall-clock time the clocks skip is `TIME_DOES_NOT_EXIST` with `nextValid`, one they show twice `TIME_AMBIGUOUS`. ### Unpaid deposit holds 2026-10-29 · Release 10 - A booking held until its deposit is paid cannot be moved by the client: `POST /booking/{id}/reschedule` answers `409` with `blocked: "deposit_unpaid"`. An unpaid hold is released when its Checkout expires. ### Visits, the checkout hand-off and opt-in scopes 2026-10-22 · Release 5 - The `/visits` endpoints: a visit of several services, booked, read, moved and cancelled as one (`GET /visits/availability`, `POST /visits/book`, and the keyed `/visits` calls). - The opt-in scopes `checkout:read`, `checkout:write` and `audit:read`, carried only by a key made with them ticked: for another point of sale checking bookings out, and for the audit log. - The opt-in `booking.checked_out` webhook event. ### Scoped API keys 2026-10-22 · Release 4 - Each key has scopes, picked when it is made; every key-protected endpoint and MCP tool needs one, and a call outside the key's scopes is `403` naming the `missingScope`. A key made before scopes keeps its access level. ### Rate limits on the API and the MCP server 2026-06-19 · Release 4 or earlier - Per-plan limits on the v1 REST API and the MCP server (per business, per key on the MCP server, per address and business on the public endpoints), with `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and `Retry-After` on a `429`. Logged rather than enforced until release 11: a call past a limit still went through. ## Going live A sandbox and a live business answer the same API in the same way, so going live is a change of key and of business, not of code. Go through this list before you switch. ### Switch to a live key 1. The live business's owner or an admin makes a live key in its admin, at `/{slug}/admin/api`, with the scopes your integration needs and no more. It starts `bk_live_` and is shown once. 2. Store it as a secret, in your server's secret manager or environment: never in browser or mobile code, and never in a URL. 3. Point your integration at the live business's slug: `https://bookatu.com/api/v1/{slug}`. 4. Replace the `bk_test_` key with it. A test key at a live business is refused with `403` `LIVEMODE_MISMATCH`, so a key left behind fails loudly rather than quietly. 5. When the business needs the AI & API add-on for its keys (it is included on the Scale plan), the owner turns it on first; without it a keyed call answers `403` `Enable the AI & API add-on`. ### Checklist - The live key is stored as a secret on your server only, and no test key is left in your production configuration. - The live key was made from an account that will stay on the business's team. A key stops working when the person who made it leaves the team or their role loses the right it needs (`403` `MAKER_NOT_ON_TEAM` or `MAKER_LACKS_PERMISSION`), and website enquiries sent with it are held for the business instead of reaching Leads. A key Bookatu support set up for the business acts on its behalf instead, and `whoami` shows that. - Your webhook endpoints are made again on the live business: a sandbox's endpoints and their signing secrets do not carry over. Each live endpoint has its own signing secret, shown once; verify every delivery with it. - Your code checks `livemode` (or the `Bookatu-Livemode` header) and never treats a `livemode: false` answer or webhook as real, nor a `livemode: true` one as a test. - You send `Bookatu-Version` with the version you tested against, so a later version never changes what you get. - You handle `429`: wait `Retry-After` seconds and back off with jitter (see [Rate limits](https://bookatu.com/en-nz/developers/rate-limits)). - Deposit, card-hold and no-show flows were tried with the simulated checkout and the simulator, a declined card and an expired checkout included. - No test data is copied into the live business: its clients, bookings and services are its own, and a sandbox's made-up clients must never be imported. - A front end on the keyless endpoints no longer sends `Bookatu-Livemode: false`. - Your error handling reads `code` (such as `TIME_NEEDS_OFFSET`, `DEPOSIT_NEEDS_BOOKING_PAGE`, `CARD_REQUIRED_USE_BOOKING_PAGE` or `MANAGE_KEY_REQUIRED`) rather than the words, which may change. ### After you switch Keep the sandbox for testing your next change, and reset it when its data gets in the way; it is deleted after 30 days without use, with a warning 7 days before. Watch the [changelog](https://bookatu.com/en-nz/developers/changelog), and your logs for a `Deprecation` header. ## Comparisons - [Bookatu vs Fresha: the 0% commission alternative](https://bookatu.com/en-nz/compare/vs-fresha): Fresha now charges a monthly subscription plus a 20% fee on new marketplace clients. Bookatu takes 0% commission. Every price links to its source. - [Fresha alternatives in 2026: prices, fees and who each one suits](https://bookatu.com/en-nz/compare/fresha-alternatives): Fresha alternatives with real prices: Timely, Booksy, Vagaro, Square, GlossGenius, Setmore, Goldie, Kitomba and Bookatu, each linked to its pricing page. - [Bookatu vs Booksy: predictable pricing, no booking commission](https://bookatu.com/en-nz/compare/vs-booksy): Booksy is US$29.99 a month plus US$20 for each extra staff member, with an optional 30% Boost fee on new clients. Bookatu takes 0% commission. Sources linked. - [Bookatu vs Vagaro: priced by clients, not calendars](https://bookatu.com/en-nz/compare/vs-vagaro): Vagaro is priced per location by bookable calendars, from AU$45 a month in Australia. Bookatu prices by active clients with 0% commission. Sources linked. - [Bookatu vs Square Appointments: booking that works in New Zealand](https://bookatu.com/en-nz/compare/vs-square-appointments): Square does not process card payments in New Zealand. Bookatu takes deposits in NZ through your own Stripe account, with 0% commission. - [Bookatu vs Timely: a price that does not grow with your team](https://bookatu.com/en-nz/compare/vs-timely): Timely is priced per staff member; Bookatu is priced by active clients, with 0% commission. Prices for New Zealand and the US, each linked to its source. ## Blog Every post on the blog in full, newest first: articles for salon, spa and studio owners. ### Try a test copy of your business before you go live Make a private copy of your business and book yourself the way a client would. Nothing in it reaches a real client, and no real money moves. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/try-a-test-copy-of-your-business-before-you-go-live · markdown: https://bookatu.com/blog/try-a-test-copy-of-your-business-before-you-go-live.md > **The short version** > > - A test copy is a private copy of your setup to practise on. Nothing in it reaches your clients. > - Press Test in the switch at the top of your admin to make one and open it. > - Every email and text the copy would send waits in its Outbox for you to read. > - Payments in the copy are simulated. You can connect Stripe test mode on its Test payments page to pay with Stripe's test cards. > - Memberships can't be bought in test mode. Before you share your booking link, you probably want to see it the way a client does. That means booking a time and reading the confirmation that follows. Doing that on your real business is awkward. A pretend booking sits in your calendar, and an email could reach someone real. A test copy gives you somewhere safe to try all of it. It looks and works like your business, and nothing in it reaches your clients. #### What a test copy is It is a second, private version of your business. It copies your setup: locations, services, classes, packages, memberships, products, forms, team, hours, time off, booking questions, terms, branding and settings. Then it adds a few sample clients and bookings, so the calendar isn't empty. It never copies your real clients or anything they have booked or bought. Payments, messages, integrations and keys stay behind too. Your team comes across as people clients can book, without their logins. Only your owners, and admins who can manage the business, can open the copy. Changes you make in the copy stay in the copy, and your real business is never touched. #### Make your test copy 1. **Press Test.** At the top of your admin there is a switch with two sides. One reads Not live yet, or Live once you have gone live. The other reads Test. Press Test. Bookatu makes the copy and opens it, with the note Test copy made. 2. **Check you are in the copy.** A banner across the top reads Test copy of, then your business name. Your browser tab starts with TEST, so you can tell the two apart. 3. **Go back when you are done.** Press Exit test in the banner. You land on the same page of your real business. Press Test again any time to return to the copy. Owners can make a copy, and so can admins who can manage the business. Your email address needs to be confirmed first. You can also make one from Settings, API & monitoring, on the Test mode card. That card is where you reset the copy or delete it later. #### Book yourself, as a client would In the copy, choose View site from the menu to open its booking page. Only the people who can open the copy can use it. Anyone else who opens the address gets a page saying it is a test page, with nothing to book. Now book something the way a client would. If you run a pilates studio, try a first class as a beginner. If you hire out kayaks, book a weekend three weeks away. Use a made-up name and email address. A Test business ribbon on the page reminds you not to enter real details. Go back to the copy's Calendar and the booking is there, as a real one would be. Move it or cancel it. None of it reaches anyone. #### Read the messages your clients would get A test copy never sends an email or a text. Everything it would have sent is kept in its Outbox, in the menu. Open it to read the confirmation your client would get, exactly as it would arrive. If something reads wrong, fix it on your real business. Then open Settings, API & monitoring on your real business, press Reset on the Test mode card and type reset. The copy takes your setup again and its sample clients and bookings start over. Book once more and check the Outbox. #### Pay a test deposit Payments in a test copy are simulated at first. No money moves and Stripe is not involved. When a service takes a deposit, the copy opens a test checkout with buttons instead of a card form, such as Pay (test) and Decline (test). Try a decline too, so you know what a client sees when a card fails. Every test payment is listed on the copy's Test payments page, in the menu: paid, declined, abandoned or refunded, with the booking it belongs to. ##### See Stripe's own checkout with a test card If you would like to see the real Stripe checkout page, open Test payments and choose Connect a Stripe test account. Fill in Stripe's pages with Stripe's test details only. Never enter your real ID or bank account there. When Stripe says the account is ready, choose Turn on Stripe test mode. From then on, new payments in the copy open Stripe's checkout page. You pay with one of Stripe's test cards, and the payment shows in the copy's Finance page. No real money moves. Choose Switch back to simulated payments whenever you like. If Test payments has no Payments card, Stripe test mode isn't offered for your business, and simulated payments are what the copy uses. > **Good to know** > > Memberships can't be bought in test mode, with simulated payments or with Stripe test mode. Packages, gift cards and deposits can. #### Your real business before you go live Until you go live, your real business is quiet too. Its booking page is private, and messages to clients are held, never sent later. That is what Not live yet at the top of your admin means. Your team can still add bookings from the calendar. So use the copy to try things as a client, and your real business to finish setting up. When you are happy, press Go live. > The best time to find a typo in your confirmation email is before a client does. #### Questions owners ask ##### Will a test booking show in my real calendar? No. The copy is a separate business with its own calendar. Nothing booked there appears in yours. ##### Can a client find my test copy? No. It is never listed or shown in search engines, and its booking page opens only for the people who can open the copy. ##### I changed my prices. Does the copy update by itself? No. Press Reset on the Test mode card, under Settings, API & monitoring, and the copy takes your current setup again. ##### How do I get rid of it? Press Delete on the same card and type delete to confirm. The copy goes for good. Your business is not touched. #### Where to start Press Test at the top of your admin and book your first test appointment. For the rest of the setup, read Go live in a day: the first-run setup checklist for new owners. If clients will pay you in person, Go live without Stripe, and choose what clients can change online explains how. ### Run two or more locations from one account Opening a second site? Add each one as a branch, with its own address, hours and team. Your booking page asks clients where they want to go, and your calendar shows one site at a time or all of them. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/run-two-or-more-locations-from-one-account · markdown: https://bookatu.com/blog/run-two-or-more-locations-from-one-account.md > **The short version** > > - Add each site under Settings, Branches. The first branch you add becomes your primary one. > - Each branch has its own address, phone, email, time zone and opening hours. > - Tie staff, services and rooms to a branch, or leave them shared so every branch offers them. > - Once two branches take bookings, your booking page asks clients which one they want first. > - Pick one branch at the top of your admin to see only that site. > - Branches are set up and picked on the web. The phone app has no branch picker. A second site is good news. It can also double the admin. A pilates studio opens a room across town. A kayak hire adds a base at the other end of the lake. Either way, there are now two sets of hours and two teams to keep straight. You don't need a second account for that. In Bookatu each site is a branch of the same business. You keep one client list and one admin, and each branch keeps the things that are really its own. #### Add your branches Open Settings, then Branches. Only owners and admins who can manage the business see it. While you run one site, the page says there is nothing to set up. Press I have opened a second site. Bookatu explains what will change before anything does. Then press Add the branch. 1. **Add your first site.** Start with the address you already have. Fill in Branch name (what your team calls it, often the suburb), Suburb & city, Street address, Phone and Email. The first branch you add becomes your primary branch, used wherever one address is needed, like receipts. 2. **Set its time zone and hours.** Timezone decides what today means at this branch. Opening hours are for this branch only. Other sites keep their own. Press Add branch to save it. 3. **Add the new site.** Press Add a branch and do the same for your second address. If it isn't open yet, switch off Taking bookings until it is. Nothing is deleted while it is off. Nothing changes for clients until two branches are taking bookings. Until then your booking page looks exactly as it did. #### Decide who works where Further down the Branches page, Who works where lists your staff, services and rooms. Tick a branch to tie someone or something to that site. Leave every box empty and it belongs to no branch, which means it is offered at all of them. You can select several rows and set them together. Everything starts shared. So a massage therapist who works only at the new site needs a tick there. A service you offer everywhere can stay as it is. A treatment room or a court that exists at one address should be tied to that address, so it is never offered at the other. #### What your clients see With two or more branches taking bookings, your booking page starts by asking which one the client would like to visit. Each branch shows whether it is open now and its hours today. After that, the services, the team and the free times are only those of the chosen branch. Times are shown on the branch's own clock. A client whose own clock is different, say a tourist booking a surf lesson before they fly in, sees the branch's time and what that is on their own clock. To send people straight to one branch, open Website widget, under Grow. In the builder, set At to the branch. Leave it on Let them choose to keep the question. #### Classes and the waitlist A class can belong to a branch. Set Branch on the class itself, or on each date when you add sessions. Where there is a choice, clients pick which branch's classes to see. A yoga studio with a morning flow at both sites lists each one under its own branch, on that branch's clock. The waitlist knows the branch too. When a client joins, it records the branch they chose, or asks. A place that frees up is only offered to people waiting for that branch, or for any branch. Your Waitlist page names the branch on each entry and can filter by it. #### Run your day one site at a time Once you have two branches, a branch picker appears at the top of your admin. It starts on All branches. Pick one and your Calendar, Clients and Waitlist show only that site. A banner says which branch you are looking at, so half your diary never seems to vanish. You can still book anyone anywhere. When you add a booking yourself, the New booking form has a Branch field. And the bookings export on the Calendar can be cut to one branch when your bookkeeper asks for it. > **Good to know** > > Branches are set up and picked in your admin on the web. The phone app has no branch picker, so do branch by branch work on the web. > Two front doors, one business behind them. #### Questions owners ask ##### Does a single site need to do anything? No. With one address there is nothing to set up, and nothing changes. Branches only matter once you open a second site. ##### Do my clients have to sign up again for the new site? No. It is one business with one client list. A student who has had lessons at one tutoring centre can book at the other with the same details. ##### Can I close one branch for a while? Yes. Edit the branch and switch off Taking bookings. It stops taking bookings and nothing is deleted. Switch it back on when you reopen. ##### What happens if I remove a branch? Its staff, services and rooms go back to being shared. Removing a branch never deletes staff, services or bookings. #### Where to start Open Settings, then Branches, and add your first site. If each person at the new site keeps different hours, Choose who does each service, and give each person their own hours shows how to set them. For classes, A class timetable that fills its own spots covers the rest. ### Approve online bookings before they are confirmed Some bookings deserve a quick look before you say yes. Here is when approval helps, when it gets in the way, and how to accept or decline a request in Bookatu. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/approve-online-bookings-before-they-are-confirmed · markdown: https://bookatu.com/blog/approve-online-bookings-before-they-are-confirmed.md > **The short version** > > - Turn it on in Settings, under Booking approval. > - Choose every online booking, or only new clients. > - The client is told the booking is requested, and their time is held until you answer. > - Accept or decline from Booking requests, or from the booking on your calendar. > - A request nobody answers is declined for you after the hours you choose. Most bookings should be confirmed straight away. A client picks a time and gets an email. A step in between only slows them down. Some bookings are different, though. A four-hour bridal makeup trial. A first lesson with a tutor who wants to know the year level before agreeing. For these, a quick look before you say yes saves an awkward phone call later. #### When approval makes sense - Long or big jobs. When one booking takes half your day, it is worth checking the details before you commit to it. - New clients you would like to know a little first. A massage therapist might read a new client's answers to the booking questions. A tutor might check the subject and level. - Bookings that need something from you. A room to set up, or a guide to line up for a group tour. - A business run by one or two people, where a busy week can fill faster than you can plan for. #### When it gets in the way Every hour a request waits is an hour the client could book somewhere else. If most of your bookings are short and routine, approval adds a step for nobody's benefit. If what worries you is people not turning up, a deposit usually does more than an approval step. Our guide How to Take Deposits for Appointments: A Practical Guide explains how. The two work together, too: a deposit is taken when the request is made. #### Every online booking, or only new clients You choose who waits. With Every online booking, every client who books online waits for you. With Only new clients, only the people you have not seen yet wait. A new client is one with no visit and no confirmed booking with you. Your regulars are confirmed straight away, as before. The choice applies to your whole business, not one service at a time. If only your longest service needs a check, Only new clients is often the gentler fit, because regulars already know how it works. #### Switch it on 1. **Open Booking approval.** Go to Settings and choose Booking approval. 2. **Turn it on.** Turn on Approve online bookings before they are confirmed. Under Which online bookings, choose Every online booking or Only new clients. 3. **Decide about moves.** Turn on Client moves need approval too if a client moving a confirmed booking from their booking link should wait for your answer. The booking keeps its time until you accept the new one. 4. **Set how long a request waits.** Under Decline unanswered requests after, set the number of hours. It starts at 48. Press Save booking approval. This covers bookings clients make on your booking page, your website widget and the booking API. Bookings your team makes are never held, and neither is a client taking a place you offered from the waitlist. #### What the client sees When they finish booking, the page says Requested. We'll confirm soon. It tells them their time is held until then, and that they will get an email as soon as you answer. If they paid a deposit, it says the deposit is refunded in full if you can't take the booking. Their booking link shows the same thing, waiting for you to confirm. When you accept, they get your usual confirmation. When you decline, they get an email with your note, if you wrote one. #### Answer a request Once approval is on, Booking requests appears in your menu, just after Calendar. A count at the top of your admin shows how many are waiting. The list is oldest first, and each request says when it has to be answered by. - Press Accept to confirm it. The client gets their normal confirmation. - Press Decline to say no. You can add a note for the client, such as: we're closed that day, but Thursday is free. The time is freed, any deposit is refunded and the client is emailed. Requests are on your Calendar too, marked Request. Open one and you can accept or decline it from there. Anyone who can edit the calendar can answer. Someone who only sees their own calendar sees only their own requests. #### Nothing waits forever A request holds its time, so it can't sit there for good. Half way to its deadline, your team is reminded once. If nobody answers by the deadline, the request is declined for you, the time is freed and the client is told. A request also lapses at its own start time, whichever comes first. > **Good to know** > > Quick swap, which lets a client who cancels late offer their time to someone on your waitlist, isn't offered while you approve online bookings first. > A quick yes is still a yes. It just comes from you. #### Questions owners ask ##### Do bookings I make myself need approving? No. Bookings your team makes are confirmed as soon as you make them. ##### What happens to a deposit if I decline? It is refunded. The client is emailed to say the request was declined, with your note if you added one. ##### Can my regulars skip the wait? Yes. Choose Only new clients. Anyone who has visited or has a confirmed booking with you is confirmed straight away. ##### What if I'm away for a few days? Requests nobody answers are declined for you after the hours you set, and the client is told. If you would rather they wait longer, raise the number under Decline unanswered requests after before you go. #### Where to start Open Settings, then Booking approval, and choose who should wait. Every step is in the help article Booking requests and approval. To learn more about new clients before they arrive, read Ask clients your own questions when they book. ### Show your live walk-in wait time on your website Tell drop-in clients how long the wait is before they leave home. Bookatu works it out from your calendar and shows it on your booking page and your own website, right next to your booking button. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/show-your-walk-in-wait-time-on-your-website · markdown: https://bookatu.com/blog/show-your-walk-in-wait-time-on-your-website.md > **The short version** > > - Turn it on in Settings, under Walk-ins, and tick the services a walk-in can have. > - The wait is worked out from your calendar, so your bookings and breaks count. > - It can show in a Walk-ins card on your booking page, and in a small widget you paste into your own website. > - Set the wait by hand from your Dashboard when the room tells a different story. > - No client or team member is ever named. Anyone thinking of walking in has one question before they leave home: how long will I wait? A barber or a bike repair workshop that takes walk-ins hears it on the phone all day, usually while the team is busy with someone else. Put the answer where people already look. Your booking page and your website can show the wait right now, next to the button to book. Someone who doesn't want to wait can book a time instead. #### How the wait is worked out Bookatu reads your calendar the way a walk-in would actually be served. Your bookings, buffers, breaks, blocked time, opening hours and rooms all count. Team members who take bookings only in person count too. Your minimum notice doesn't apply, because a walk-in is already at the door. Clients see a plain line. Walk in now, no wait. About 20 min wait. Busy, next opening around 3:40 pm. When the day is full it says No walk-in openings left today, and when you are closed it says when you open next. #### Switch it on 1. **Open Walk-ins.** Go to Settings and choose Walk-ins, then turn on Show a live walk-in wait. 2. **Pick your walk-in services.** Under Walk-in services, tick the services a walk-in can have. Nothing is worked out until at least one is ticked. Classes and extras are left out, and invite-only services are never shown as walk-ins. 3. **Choose what to show.** Show it on my booking page adds a Walk-ins card near the top of your page. Show how busy you are adds a line such as 3 of 4 staff with clients. 4. **Save.** Press Save Walk-ins. You can also tick Walk-in service on a service's own page, once walk-in wait times are on. #### On your booking page The Walk-ins card sits near the top of your booking page. It shows the wait now and each walk-in service's own wait. For a service clients can book online, a Book this time link sits beside it. A client who would rather not queue for a gel manicure can take the free time and arrive when it starts. #### On your own website Below the settings, The walk-in widget for your website gives you a snippet to copy. There is one for all your walk-in services together, and one for each service on its own. Paste it where the wait should show. Next to your Book now button is a good spot. The widget keeps itself up to date while the page is open. It follows your website widget settings for where it may be shown, so if your booking widget works on your site, this will too. To show it in another language, add lang= and a two-letter code, such as de or fr, to its address. A bike hire counter could put the widget on its home page, so riders can see whether to come now or book a slot for later. A massage studio that takes drop-ins could put it on its prices page. #### When the calendar doesn't know Sometimes the room tells a different story. Three friends walk in together, or a skin fade takes longer than planned. Your calendar can't see that, so you can set the wait yourself. On your Dashboard, the Walk-in wait panel shows exactly what clients see right now. Press No wait, ~15 min, ~30 min, ~45 min or 60+ min, or type the minutes yourself. Press Not taking walk-ins if you need to stop for the day. Under Lasts, choose 1 hour, 2 hours or To the end of the day. Clients see that the wait was updated by the team, and how long ago. When it lapses, the wait is worked out from your calendar again. Press Back to automatic to do that sooner. The panel shows to anyone who can edit the calendar, and A wait set by hand lasts, in Settings, sets the length it starts on. > **Good to know** > > Clients see the wait and a few counts, nothing more. No client or team member is ever named, wherever the wait appears. #### For developers and agencies If someone else builds your website, they can read the same wait from Bookatu's API and show it in their own design. It is listed in the developer docs. Whatever they build, the answer is the one your booking page shows. > Answer the question before the phone rings. #### Questions owners ask ##### Does it name my staff or my clients? No. It shows counts only, such as how many staff are with clients and how many appointments are still to go today. ##### Can I show the wait for one service only? Yes. Each walk-in service has its own snippet, under The walk-in widget for your website. ##### What if we stop taking walk-ins early? Press Not taking walk-ins in the Walk-in wait panel on your Dashboard. Your page and widget then say Not taking walk-ins right now. ##### What happens if I turn it off? Nothing shows on your booking page, and the widget says walk-in wait times are turned off. Turn it back on whenever you like. #### Where to start Open Settings, then Walk-ins, and tick your walk-in services. To put a booking button beside the wait, read Add a Book Now button to your website or Instagram bio. For clients already at your counter, The QR code on your counter that books clients while you work shows another way in. ### How to invoice a client or a company for a booking When a company pays for the booking, it wants an invoice. Here is how to bill a booking from your calendar, by payment link or by an invoice paid by bank transfer, with the tax and deposit already worked out. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/invoice-a-client-or-company-for-a-booking · markdown: https://bookatu.com/blog/invoice-a-client-or-company-for-a-booking.md > **The short version** > > - Turn on Invoices in Settings, under Messaging & retention. > - Open a booking, tap Invoice and choose who pays: the client, or a company. > - Send a payment link they pay by card, or an invoice they pay by bank transfer. > - The tax and any deposit already paid come from the booking, so the total matches your point of sale. Some bookings are not paid for by the person who turns up. A company books headshots for its new starters. A school pays your tour company for a class trip. The money comes from an accounts team, and an accounts team wants an invoice with a number on it. In Bookatu you can bill a booking straight from your calendar. You do not retype anything into a separate invoice tool. #### A payment link or an invoice: which one? Bookatu has two ways to bill. A payment link is for someone who will pay by card now. They get an email with a Pay now button, and the money goes to your own Stripe account, the same as a deposit does. An invoice is for a business that pays by bank transfer on its own schedule. It has a number, a due date, their purchase order reference and your bank details. It takes no card, so you can send one whether or not you have connected Stripe. #### Turn on invoices first Invoices are off until you switch them on. Open Settings, choose Messaging & retention, turn on Invoices and tap Save settings. If they are off, a booking's Payment section says so and links you there. Then add your bank details. Open Finance, fill in How clients pay you and tap Save payment details. An invoice shows them under How to pay. Without them, the company has nowhere to send the money. Raising an invoice needs the Manage the business and See analytics & earnings permissions. Owners and admins have both from the start. #### Invoice a booking from your calendar 1. **Open the booking.** Tap the booking on the Calendar. In its Payment section, tap Invoice. You can also tap Invoice on the booking's own page, beside Check out. That is how you bill a tour that runs over whole days. 2. **Choose who pays.** Pick The client, or A company. For a company you have billed before, pick it from the list. For a new one, tap Add a new company and fill in the company, a contact name, their accounts email and their address. Add a PO reference if they gave you one. 3. **Choose how they pay.** Pick Payment link to be paid by card online, or Invoice to be paid by bank transfer. For an invoice, choose the payment terms and Bookatu shows the due date. 4. **Check the lines.** The booking's service and extras are already there, and cannot be edited here. Tap Add a line for anything else. To put more of the same client's bookings on one invoice, tap Add another appointment. The button uses your own word for a booking, such as session or shoot. 5. **Send it.** The button reads Send to, then their email address. With no email on file, it reads Create invoice instead, and you can copy the link and send it yourself. #### The tax and the deposit are already right An invoice for a booking uses the same tax your point of sale would charge for it. If your prices include tax, it shows the tax inside the total. If they do not, the tax is added on top, and a payment link charges that full total. A deposit the client already paid shows as Deposit applied, and the invoice asks only for the Balance due. Nobody is billed twice for the same money. Some bookings cannot go on an invoice. The invoice shows each one with its reason: - Checked out at the point of sale - Already on an invoice - Already paid - Paid from a pack or a membership - Deposit still being paid #### After you send it The booking now shows its invoice number, the amount and Awaiting payment or Paid, with Open invoice beside it. A payment link still waiting to be paid has Copy link, so you can paste it into a text or a WhatsApp message. A company can open the invoice from the email, then print it or save it as a PDF for its records. When the transfer lands in your bank, open Finance and tap Mark paid on that invoice. If you ticked the wrong one, Not paid after all puts it back. To chase a late one, Send again sends the same invoice, with the same number, to the same address. > The booking already knows what it cost and what was paid. The invoice should start from there. #### Bill for something that is not a booking Not everything you are owed comes from a booking. A product someone took home, or a session agreed over text, can be billed from Finance. Under Invoices, pick Payment link or Invoice a company, add your lines and send it. #### Questions owners ask ##### Do I need Stripe to send an invoice? Not for an invoice paid by bank transfer. A payment link takes a card, so it needs Stripe connected. Until then, the Payment link choice offers Set up card payments, and you can send an invoice instead. ##### Can I put several bookings on one invoice? Yes, for the same client. In the invoice, tap Add another appointment (or session, or your own word for a booking) and pick from their other bookings. A booking that cannot be billed is shown with the reason. ##### What happens to a deposit the client already paid? It comes off. The invoice shows it as Deposit applied and asks only for the balance. ##### How do I mark a bank transfer as paid? Open Finance, find the invoice under Invoices and tap Mark paid. A payment link paid by card marks itself paid. #### Where to start Turn on Invoices, add your bank details on Finance, then open your next company booking and tap Invoice. The help articles Invoice a company that pays by bank transfer and Send a client a payment link go step by step. For how tax shows on a payment link, read our post Print or email receipts at the point of sale, and tax rates to three decimals. ### Booth rent or commission: how to pay your team, tips included Some of your team work for commission, some rent a chair or a room from you. Here is how the two differ, how to set each one up in Bookatu, how tips are shared and what to download on pay day. The Bookatu team · 2026-11-11 · Grow your business · https://bookatu.com/en-nz/blog/booth-rent-or-commission-pay-your-team · markdown: https://bookatu.com/blog/booth-rent-or-commission-pay-your-team.md > **The short version** > > - On commission, the client pays you and you pay the person a share. On booth or chair rent, they keep their takings and pay you rent. > - Set commission under Money, then Commission rules. Mark a renter on their card under Settings, then Team. > - Tips are off until you turn them on at the point of sale. Each tip is split by the rule you choose, and never earns commission. > - On pay day, Payroll lists each pay period person by person, with files for your payroll system. There are two common ways to work with the people who serve your clients. A stylist or a personal trainer can work for you on commission. Or they can rent a chair or a room from you and run their own diary. Plenty of businesses have both. Bookatu keeps the two apart, so a renter's money never ends up in your team's pay. #### Booth rent or commission: what is the difference? On commission, the client pays your business. You pay the person a share of what they sold, usually a percentage. You set the prices, and their bookings are your takings. On booth or chair rent, the person keeps what their clients pay. You charge them a fixed rent on a set schedule, such as weekly or monthly. Your income from them is the rent, whether their week was busy or quiet. #### Which one suits your business? Commission tends to suit people who are building a client list, and businesses that bring in most of the clients themselves. You earn more in a busy week, and you carry the quiet ones. Rent tends to suit someone with a loyal following who wants to set their own hours. You know what is coming in each month. In return, you have less say over how they work. > **The legal bit** > > Whether someone counts as an employee or as a renter depends on where you are and how you work together. So does how tips and rent are taxed. Ask an accountant or an employment adviser. Bookatu records the arrangement you set up. It does not decide it for you. #### Set up commission Open Money, then Commission rules. Under Set a rule, pick Who (everyone, or one person) and For (every service, one category, one service, or the same for products). Choose A percentage, or A fixed amount per visit or item, enter the Amount and tap Save rule. The most specific rule wins. A person's own rule beats the rule for everyone. Within either, a rule for one service beats one for its category, which beats one for everything. Commission is worked out after discounts and before tax and tips. A change applies from today. Every earlier day keeps the rule it had, so a pay period you have already paid never changes. Nobody earns commission until you set a rule. Want to reward your busiest people? Under Set a tiered rule, the rate steps up once someone sells more in a pay period, like tax brackets. Under Goal bonuses, you pay a fixed bonus when their sales reach a target. #### Set up a booth or chair renter 1. **Open their card.** Go to Settings, then Team, and tap the pencil on the person's card. Scroll to the Pay section. 2. **Mark them as a renter.** Tick the box that says they rent a booth or chair. Enter the Rent and choose when it is Due: Every week, Every two weeks or Every month. 3. **Pick the start day.** Set Renting from to today or a later day, then tap Save pay. Their first rent is due on that day. Their card now shows a Booth renter badge. From that day they earn no commission or goal bonus, and they keep their own takings and tips. Their bookings stay on your calendar as before. If they move to commission later, untick the box, pick the day under Stops renting from and tap Save pay. Earlier days keep the rent and commission they had. #### Tips: who gets what Tips are off until you switch them on. Open the Point of sale page and scroll to the Tips card. Turn on Accept tips at checkout, set your Suggestions as percentages, choose How a tip is split and tap Save tip settings. By default, a tip follows each person's share of the services. On a booking with one person, the whole tip goes to them. You can split it equally between everyone on the sale instead, or by each person's share of the whole sale, products included. At checkout you can also tap Enter amounts and type each person's share. A tip goes on top of the bill. It earns no commission and is not part of the sale's total. If a split was wrong, open the sale under Money, then Tips, and use Change the split. You type the new amounts and say Why. The change is kept as an adjustment on the day you make it, so a week you have already paid keeps its figures. > The number you pay should be the number on the screen, with every line under it saying why. #### Pay day Open Money, then Staff earnings, and tap Payroll at the top. It shows one pay period at a time, person by person. Employees show their hours booked, sales, commission, goal bonus, tips and total. Booth renters have their own table showing the Rent owed, with a Rent statement for the period. Pay periods are calendar months until you change them. Under Pay periods, choose how often you pay and the date they start from, then tap Save pay periods. Under Download for your payroll system, the Payroll CSV holds everyone and every figure. The Wagepoint earnings file and the ADP paydata file hold your employees only, laid out for those systems. Add each person's Payroll number on their card first, so the files match them. Downloads need the Export data permission and are recorded in your audit log. > **Good to know** > > - No-shows and cancellations earn nothing. A refund after a visit takes back the same share of its commission, in the pay period of the refund. > - A service booked in whole days, like a multi-day tour, is the business's own takings. It earns nobody commission, even with a guide on it. > - Renters are left out of the Wagepoint and ADP files. The Payroll CSV includes them, marked as Booth renter. > - Seeing pay needs the See analytics & earnings permission, which owners and admins have from the start. Changing rules needs Manage the business too. #### Questions owners ask ##### Is booth rent or commission better for a salon or studio? Neither is better everywhere. Commission suits a business that brings in the clients and wants a say in how the work is done. Rent suits experienced people with their own following, and gives you a steady income. Many businesses run both, and Bookatu keeps them apart. ##### Can I have renters and commissioned staff at the same time? Yes. Each person is set up on their own card. Staff earnings and Payroll list renters apart from employees. ##### Do booth renters get their tips? Yes. A renter keeps their own tips. Tips your point of sale takes for them show in their row on Payroll, and their total there is those tips less the rent due in that pay period. ##### Does Bookatu pay my team? No. Bookatu works out the figures and gives you files for your payroll system. You pay your team the way you do today. #### Where to start Set one commission rule for everyone, then mark any renters on their cards. Turn tips on if you want them. At the end of your first pay period, open Payroll and check the figures before you download. The help article Set up a booth or chair renter has every step for renters. Set tiered commission and goal bonuses and Set pay periods and download payroll cover the rest. If you want to know how tip records are kept, our engineering post An append-only tip ledger explains it. ### Use a spare tablet as a customer screen for totals and tips A screen facing the client shows each item and the total as you ring up a sale, and lets them pick a tip themselves. Here is how to set one up on Bookatu's point of sale with a tablet or a second monitor. The Bookatu team · 2026-11-11 · Product · https://bookatu.com/en-nz/blog/use-a-tablet-as-a-customer-display · markdown: https://bookatu.com/blog/use-a-tablet-as-a-customer-display.md > **The short version** > > - On the Point of sale page, tap Customer display beside Scan. > - Open it in a second window on this computer, or pair a tablet that faces the client. > - The client sees each item, any discount, the tax and the total as you ring up the sale. > - At a booking's checkout they can pick a tip on the screen. Nothing is added until you accept it. A client at the counter wants to see what they are paying for. Turning your laptop round works once or twice. A screen that faces them shows the sale as you ring it up, and lets them choose a tip without you reading the options out. On Bookatu's point of sale, that screen can be a tablet you already own or a second monitor. You do not need a special display. #### What the client sees Between sales, the screen shows your logo and business name with a short welcome message. As you ring up a sale, each item appears with its amount. Below them come the subtotal and any discount, each tax and the total. If you attached a client to the sale, the screen greets them by first name. When you check out a booking, a deposit the client already paid comes off, and the screen shows what is left To pay. Say a client at your nail bar paid a deposit online and adds a bottle of polish. They see the polish, the deposit taken off and the balance. The screen never shows card details or contact details. A client's surname, email and phone number stay on your side. Its words follow your Storefront language in Settings. #### Set it up Open the Point of sale page: tap Sell on Products, or Point of sale on your Dashboard. Then tap Customer display, beside Scan. You have two choices. 1. **A second screen on this computer.** Tap Open on this computer. The display opens in a new window. Drag it to the monitor facing the client and make it full screen. 2. **A tablet facing the client.** Tap Pair a tablet and follow the steps on screen. Once it is paired, the tablet shows each sale you ring up on this computer. To change the welcome message, scroll down the Point of sale page to the Customer display card. Fill in Message on the idle screen and tap Save display settings. Left empty, the screen says Welcome. Changing it needs the Manage the business permission. #### Let the client choose the tip Tips are offered when you check a booking out, once Accept tips at checkout is on in the Tips card on the same page. At checkout, tap Ask on the customer display. The client sees your suggestions, each with what it comes to, plus no tip and an amount of their own. When they tap one, your side shows what they chose, such as The client chose 15%. Tap Accept tip to add it, or Ignore. Nothing is added to the bill until you accept. The tip is then split between your team by the rule you set in the Tips card. For how that works, read our post Booth rent or commission: how to pay your team, tips included. > Nobody enjoys being asked about a tip out loud. Let the screen ask. #### A receipt, if they want one When you record the sale, the screen says thank you and shows what was paid. It asks Would you like a receipt? The client taps Printed, By email or No receipt, and your side shows what they asked for. You print or email it from the point of sale as usual, and the screen goes back to your welcome message. > **Good to know** > > The customer display shows the sale and takes the client's choices. It charges nothing. Bookatu's point of sale records money you have already taken, in cash or on your own card machine. #### One more thing for retail: print your own barcode labels If you sell products, you can print price labels with a barcode from Products. Open a product's menu and tap Print labels. Or tick several products and tap Print labels in the bar that appears. After you receive a delivery, Print labels gives you one label for each unit received. Each label shows the barcode, the name and the price, and the SKU if you tick it. Pick your label size, for a Dymo, Brother or Zebra label printer or an A4 sheet of 21 labels, and print from your browser. A product with no barcode can get one. On the product, tap Make a barcode and it gets a shop code your point of sale can scan. That needs the Manage the business permission. #### Questions owners ask ##### Do I need to buy a customer display screen? No. A tablet with a web browser, or a second monitor plugged into the computer you sell from, does the job. ##### Can clients pick a tip on the customer display? Yes, when you check out a booking with Accept tips at checkout turned on. Tap Ask on the customer display, and accept their choice on your side. ##### Can the customer display take card payments? No. It shows the sale and the client's choices. Take the card on your own card machine, then pick Card when you record the sale. #### Where to start Open the Point of sale page, tap Customer display and try Open on this computer with a test sale. The help article Sell and check out at the point of sale covers the rest of the point of sale. To keep your stock right as well, read How to do a stocktake from your phone, no clipboard needed and Receive a whole delivery by photographing the supplier invoice. ### Let clients book repeat appointments and group bookings online Regulars can book the same time every week or month in one go, and a group can book together in a single booking. Here is how to switch each one on in Bookatu, and what your clients see. The Bookatu team · 2026-11-11 · Recurring revenue · https://bookatu.com/en-nz/blog/repeat-appointments-and-group-bookings-online · markdown: https://bookatu.com/blog/repeat-appointments-and-group-bookings-online.md > **The short version** > > - In Settings, open Repeat bookings online, switch it on and pick which services clients can repeat, and how often. > - A client books the first visit as usual, then ticks Repeat this booking. Each date is checked before they confirm. > - Turn on Take a group in one booking on a service, and your booking page asks How many people? > - One person on your team serves the whole group, and the price can be per person. Some clients come back on a rhythm. A student sees their tutor every Tuesday. A runner books a sports massage once a month. Others arrive in a group, like four friends booking a surf lesson together. Both used to mean a message to you and some typing on your side. Now clients can do both from your booking page. #### Let regulars repeat their booking online Repeat bookings online is off until you switch it on, and nothing changes for a service you leave unticked. To set it up: 1. **Open the setting.** Go to Settings and choose Repeat bookings online. Turn on Let clients repeat their booking online. 2. **Pick the services.** Under Services clients can repeat, tick the ones that suit a regular rhythm. A weekly lesson or a monthly treatment fits well. A one-off consultation probably does not. 3. **Pick how often.** Under How often clients can pick, tick the choices you want to offer, such as Every week or Every month. A monthly repeat falls on the same date each month. 4. **Set the most visits.** Set Most visits in one go, counting the first visit, then tap Save repeat bookings. Changing it needs the Manage the business permission, which owners and admins have from the start. #### What your client sees The client picks a service and a time as usual. On the review step, a service you ticked shows Repeat this booking, as long as it is booked on its own rather than with other services. They tick it, then choose How often and the number of Visits in all. Bookatu checks each date before they confirm, by the same rules your booking page uses. A day you are closed is left out, and so is a time already taken or a date further ahead than you take bookings. The client sees which visits Can be booked and which are Not available, with the reason. Each repeat is the same service with the same person. If they chose anyone free, Bookatu finds whoever is free for each date. Extras and promo codes stay on the first visit. Only the first visit takes a deposit. If that deposit is never paid, the repeats are released too, so no time sits held for nobody. The client gets one confirmation that lists every visit. Later, they can cancel one visit, or that visit and all the later ones, from their booking link. Your usual rules for online changes still apply. > **Good to know** > > If you approve online bookings before they are confirmed (Settings, then Booking approval), you answer a repeat series once. Accept the first visit and the repeats are accepted with it. Decline it and the series ends. Our post Approve online bookings before they are confirmed explains how approval works. #### Let a group book together A group booking is one booking for several people, served by one person on your team. A pottery studio's birthday party works this way, and so does a family photo shoot. 1. **Open the service.** Go to Catalog, open your services list and tap Edit on the service. 2. **Turn on group booking.** Turn on Take a group in one booking, and fill in Up to how many people? 3. **Decide how it is priced.** Turn on Price is per person if the price and deposit are for each person. A group of six is then charged six times. Leave it off when the price is for the booking, however many people come. Then tap Save changes. Your booking page now asks How many people? for that service, up to the most you set. Times are offered only when the booking fits. If the service needs a room, each room it uses has to seat the whole group, so set how many people each room fits. The New booking form in your admin asks the same question. > The group books once, and one person on your team looks after them all. #### A group booking is not a class A class runs at set times, and each person books their own place in it. A group booking is one booking that the group makes together, at a time that suits them. If you run a timetable, read our post A class timetable that fills its own spots. It is also different from a service that needs two of your team at once, such as a couples massage. That is People needed at once, on the same service form. The help article Book a service that needs two or more people explains it. #### Questions owners ask ##### Can clients book recurring appointments online? Yes, once you turn on Repeat bookings online and tick the services. On the review step, the client ticks Repeat this booking and picks how often and how many visits. They see which dates can be booked before they confirm. ##### What happens if one of the repeat dates is not free? It is left out, and the client sees why, for example Closed that day. The other dates are still booked. Nothing is forced into your calendar. ##### Do clients pay a deposit for every repeat visit? No. Only the first visit takes a deposit. ##### Can I still book repeat appointments for a client myself? Yes. Open one of their bookings, and the See you again? card books a run of visits for them. The help article Recurring and standing appointments shows how. #### Where to start Pick the one service your regulars book most often and turn on Repeat bookings online for it. If groups ask you to book together, turn on Take a group in one booking on the service they ask about. Then book a test on your own booking page to see what clients see. ### Can an AI assistant book an appointment for you? Only at a Bookatu business that has switched it on. There, your assistant finds a free time and holds it, Bookatu emails you a code and a link, and nothing is booked until you confirm. Bookatu never asks you to pay inside a chat. The Bookatu team · 2026-11-07 · Grow your business · https://bookatu.com/en-nz/blog/can-an-ai-assistant-book-an-appointment-for-you · markdown: https://bookatu.com/blog/can-an-ai-assistant-book-an-appointment-for-you.md > **The short version** > > - Only at a Bookatu business that has switched it on. > - There, your assistant can find a free time and hold it for you. > - Bookatu emails you a code and a link. Nothing is booked until you give the code to your assistant, or open the link and press "Confirm booking". > - Bookatu never asks you to pay inside a chat. You pay any deposit on the business's booking page. > - If you did not ask for a time, the email links to a page with a "This wasn't me" button. Only at a Bookatu business that has switched it on. There, your assistant can find a free time and hold it, and you confirm from your email. You need an assistant that lets you add a connector by its web address. A held time is kept from other assistants, but the business can still fill it until you confirm, so confirm soon. #### What do I need for my AI assistant to book at a Bookatu business? - An AI assistant that lets you add a connector by its web address. Some offer this only on some plans. - The address of Bookatu's public booking server, https://bookatu.com/api/mcp/book. - No Bookatu account and no key. - The business's Bookatu booking link. #### How do I add Bookatu to my AI assistant? 1. **Find the connector settings.** In your assistant's settings, find where to add a custom connector by its web address. 2. **Paste the address.** Paste https://bookatu.com/api/mcp/book as the server address. It needs no key and no sign-in. The server calls itself Bookatu Booking, and if your assistant asks you to name it, any name you will recognise is fine. 3. **Allow it.** Your assistant may ask you before each step it takes with Bookatu. Allow it when it does. #### How do I book a time with my AI assistant? Give your assistant the business's booking link, and say which service and which day suit you. Bookatu gives it each free time on the business's clock, and on yours when you are somewhere else. You pick one, and your assistant passes on your name and email, and a phone number if you give one. #### How do I confirm a time my AI assistant held? Give the code from Bookatu's email to your assistant, or open the link in the email and press "Confirm booking". Opening the link books nothing by itself. A held time lasts only a short while, so confirm soon. Then the business's usual confirmation follows. If the business accepts bookings by hand, your booking reaches it as a request, and you get an email when it answers. #### What if the business does not take bookings from AI assistants? Bookatu tells your assistant, and gives it the business's booking page link to pass on. The same happens for a service that needs more than a time, such as a deposit or a form, which you book on the business's booking page. #### What does my AI assistant share, and how do I know an email is from Bookatu? - Your assistant gets what the business's public booking page shows, without its street address. Bookatu takes your name and email from it, and a phone number if you give one. - When you confirm, the business gets your name and email, as it would from its booking page. - Bookatu never asks you to pay inside a chat. If a chat asks you for money for a booking, the request did not come from Bookatu. - If you did not ask for a time, press "This wasn't me" on the page the email links to. If you pressed it by mistake, "Allow assistants again" on the same page lets these emails reach you again. - What Bookatu keeps when your assistant holds a time is described at bookatu.com/privacy#ai-assistants. #### Questions clients ask ##### Can my AI assistant book at any business? Only at a Bookatu business that has switched it on. Elsewhere it depends on the business's booking system. ##### Do I need a Bookatu account to book with my AI assistant? No. You need an assistant that can add a connector, and your email to confirm. ##### Can I pay a deposit to my AI assistant? No. Bookatu never asks you to pay inside a chat. Bookatu gives your assistant the business's booking page link, and you pay the deposit there. ##### What if my held time is taken before I confirm the booking? Nothing is booked at that time. When you confirm through your assistant, Bookatu can offer it other free times, or you can pick another time and hold it again. ##### Which language does Bookatu write to me in when my AI assistant holds a time? Bookatu's emails about the held time, and the page you confirm on, are in your language when your assistant tells Bookatu which one, in any of the 14 languages Bookatu speaks. The business's own confirmation and reminders come in its language, and service names stay as the business wrote them. #### Where to start Run a business? Read Can my clients book me from their own AI assistant? ### Can my clients book me from their own AI assistant? Only once you switch it on. Then a client's own AI assistant can find your free times and hold one through Bookatu's public booking server, and the client confirms by email before the booking reaches you. Here is what clients see and how to switch it on or off. The Bookatu team · 2026-11-06 · updated 2026-11-07 · Grow your business · https://bookatu.com/en-nz/blog/can-my-clients-book-me-from-their-own-ai-assistant · markdown: https://bookatu.com/blog/can-my-clients-book-me-from-their-own-ai-assistant.md > **The short version** > > - Only once you switch it on. > - Bookatu emails the client a code and a link. Nothing is booked until they give the code to their assistant, or open the link and press "Confirm booking". > - Bookatu never takes payment in a chat. A service with a deposit is booked on your booking page. > - It is off until you switch it on, and you can switch it off or keep single services out at any time. People hand more of their everyday errands to an AI assistant, and an appointment is one of them. With this switched on, a client's assistant can get as far as holding a time with you, and the client still confirms it themselves. #### What is Bookatu's public booking server? It is an MCP server that a person's own AI assistant can connect to. MCP is an open protocol that lets AI assistants use other software's tools. Through it, an assistant can look up a business on Bookatu from its booking link, see its free times and hold one for the person. The client needs no Bookatu account and no key. The server is at https://bookatu.com/api/mcp/book, and it calls itself Bookatu Booking. #### What does my client see when their AI assistant holds a time? 1. **They give their assistant your booking link.** Bookatu gives the assistant your free times for the service they want, on your clock, and on theirs when they are somewhere else. 2. **An assistant holds a time for the client.** It passes on the client's name and email, and a phone number if they give one. A held time is kept from other assistants, but your booking page and your team can still book it. 3. **Bookatu emails the client a code and a link.** Nothing is booked until they give the code to their assistant, or open the link and press "Confirm booking". Opening the link books nothing by itself. The page also has a "This wasn't me" button, for an email they did not expect. 4. **Nothing is booked until the client confirms.** Once they confirm, it is a normal booking, with your usual confirmation and reminders, and you get their name and email as you would from your booking page. If you accept bookings by hand, even only from new clients, it arrives as a request. #### What stays the same when a client's AI assistant books me? - Your free times, and your minimum notice before a booking. - Your prices. If a price changes before the client confirms, nothing is booked at the old price. - Your approval setting. If you accept bookings by hand, even only from new clients, every booking from an assistant arrives as a request. - Your confirmation and reminders, sent as they are for any other booking. A new client who books this way gets no texts, since texts need the client's own yes. #### Which services can a client's AI assistant book? A plain timed service. Anything that needs more than a time is booked on your booking page instead: a deposit, a card held for your no-show policy, a required intake form or booking question, two or more team members, more than one kind of room or equipment at once, a trip, a class or workshop, an extra, or a group bigger than the service takes. If you have booking terms, that goes for every service, since the client agrees to them on your booking page. Bookatu tells the assistant when a service is booked on your booking page, and gives it the link to pass on. You can also keep any service out on the settings page, and clients can still book it on your booking page. #### Which businesses can let clients' AI assistants book them? Any business with a live booking page, on any plan and during its free trial too. It does not matter how long you have been on Bookatu or how many bookings you have had. Bookatu does not let assistants book health or medical care. If any of your services is health or medical care, assistants cannot book your business at all, and the settings page says so. If something is still in the way, such as a booking page that is not live yet, the settings page lists it with a link to the page where you fix it. Once nothing is in the way, the switches unlock. #### How do I let clients' AI assistants book me? 1. **Open Settings, then Clients' AI assistants.** If the page lists something in the way, follow its link and fix that first. The switches unlock once nothing is in the way. 2. **Tick "None of my services are health or medical care".** Tick it only when it is true of your business. Assistants can't book health services, and Bookatu records who ticked it and when. 3. **Switch on "Let clients' AI assistants book me".** Then save your changes. From then on, an assistant can hold a time with you when a client gives it your booking link. 4. **Check "What an assistant sees".** It shows what an assistant is told when it looks you up, and which services it can hold a time for. The help guide at https://bookatu.com/en-nz/help/let-clients-book-from-their-ai walks through each part of the page. #### How do I stop AI assistants booking me? Open Settings, then Clients' AI assistants, switch "Let clients' AI assistants book me" off and save your changes. To keep only some services out, pick them on the same page instead and save. A time an assistant is still holding is checked again when the client confirms, so nothing is booked after you switch it off. #### What does a client's AI assistant see about my business? Only what your public booking page shows, without your street address. An assistant using Bookatu's public booking server never sees your client list or other clients' bookings. Bookatu gives it your business's name, your town and area, your opening hours, your services and prices, and your phone number only if your booking page shows it. Bookatu's emails about the held time, and the page the client confirms on, are in the client's language when their assistant tells Bookatu which one, in any of the 14 languages Bookatu speaks. Your own confirmation and reminders come in your business's language, and service names stay as you wrote them. #### Questions owners ask ##### Does a client's AI assistant take payment? No. Bookatu never takes payment in a chat. A service that needs a deposit is booked on your booking page, and the deposit is paid there. ##### What if a client says they did not ask an AI assistant to hold a time? The email Bookatu sends them links to a page with a "This wasn't me" button. Pressing it means nothing can be booked from that hold, and for a while Bookatu sends that address no more of these emails. Your settings page counts these under "Client said it wasn't them". ##### Will a time held by an AI assistant block my booking page? No. Your booking page and your team can still book that time. If they do, nothing is booked over it when the client confirms, and Bookatu can offer the client's assistant other free times instead. ##### Can AI assistants find my business without my booking link? Only through a separate switch, "List me when assistants search", and only once listing is open to your business. If you switch it on before then, your settings page says "Listing opens soon". Without it, an assistant can still hold a time with you when a client gives it your booking link. ##### Does letting clients' AI assistants book me cost extra? There is no add-on for it, and it works during your free trial too. Bookatu takes no commission on bookings made this way. #### Where to start The help guide at https://bookatu.com/en-nz/help/let-clients-book-from-their-ai walks through the settings page. For what an assistant can do with Bookatu, see https://bookatu.com/en-nz/ai/assistants, and developers will find the server described at https://bookatu.com/en-nz/developers#mcp-book. For the services that stay on your booking page, read https://bookatu.com/en-nz/help/your-booking-page and https://bookatu.com/en-nz/help/deposits. ### AI receptionist or AI assistant: what is the difference? Bookatu's AI receptionist, the assistant in your admin and your own AI assistant do different jobs. Here is what each one does and what none of them can do. The Bookatu team · 2026-11-05 · updated 2026-11-06 · Grow your business · https://bookatu.com/en-nz/blog/ai-receptionist-or-ai-assistant-what-is-the-difference · markdown: https://bookatu.com/blog/ai-receptionist-or-ai-assistant-what-is-the-difference.md > **Update, 6 November 2026** > > Besides the three kinds of AI in this post, there is now a fourth. At a business that has switched it on, a client's own AI assistant can find a free time and hold one through Bookatu's public booking server, and the client confirms by email. Bookatu never takes payment in a chat. Read Can my clients book me from their own AI assistant? > **The short version** > > - Auto-reply is Bookatu's receptionist. It answers new clients' messages from your real services, prices and hours, and sends your booking link. > - The assistant in your Bookatu admin proposes each change. You confirm it, and you can undo it afterwards. > - If an AI assistant app you already use can connect to an MCP server, you can connect it to your Bookatu account. #### What is the difference between an AI receptionist and an AI assistant for a salon, spa or studio? An AI receptionist replies to your clients' messages for you. An AI assistant works for the person using it. In your Bookatu admin, that person is you or someone on your team with the Admin role. The receptionist answers when a new client messages your business and points them to your booking page. The assistant in your Bookatu admin helps with the work inside Bookatu, such as moving a booking or adding a service, and it changes nothing until you confirm. #### What does Bookatu's AI receptionist do? Bookatu's receptionist answers the first message of a new conversation from your real services, prices and hours. When someone asks about booking, your hours or your prices, the reply includes your booking link. It does not book. It sends your booking link, and the client picks a free time on your booking page. It passes a complaint, a refund request or a request to speak to someone to your team, and it politely declines questions that have nothing to do with your business. You switch it on in Inbox, then Channels, with the Auto-reply new chats setting, which is part of every plan. By text or WhatsApp, it replies only when you send from your own number on an account you pay for. The guide is at https://bookatu.com/en-nz/help/ai-receptionist. #### What does the assistant in my Bookatu admin do? The assistant in your Bookatu admin is a chat that does everyday tasks for you when you ask in plain words. It can book and move appointments, add clients and services, and read a supplier invoice into stock from a photo. It shows each change on a card first. Nothing is saved until you tap Confirm, and you can undo a change from the chat afterwards. Only the business owner and people on your team with the Admin role can use it, and your staff do not see it. There is more about it at https://bookatu.com/en-nz/ai. #### Can I connect my own AI assistant to my Bookatu account? Yes, if your assistant app can connect to an MCP server by its web address. Bookatu runs one for your account. Through it, Bookatu lets an AI assistant app you connect check your availability and make or move bookings for you. You connect it by signing in to Bookatu from the assistant, or with an API key you make in Settings. When you sign in, you choose Read only or Read and write, and whether it may see your clients' names and contact details. Bookatu never lets it do more than that connection allows. What it reads goes to the AI provider you use, under that provider's terms. You can disconnect it at any time in Settings. The page at https://bookatu.com/en-nz/ai/assistants shows how to connect one and whether connecting costs extra on your plan. The guide at https://bookatu.com/en-nz/help/api-and-mcp explains the API and the MCP server. #### What is MCP, and do I need to know it? MCP stands for Model Context Protocol. It is an open protocol that lets AI assistants use other software's tools, and you do not need to know it to use Bookatu's AI. An MCP server is the software's side of that. It lists the actions an assistant may take, and the software stays in charge of what each action is allowed to do. Bookatu runs one for your own account, and an assistant reaches it only after you sign in or give it an API key. Bookatu also runs one that only reads its help guides, blog and developer docs, and that one needs no key. Auto-reply and the assistant in your admin need no MCP setup at all. Connecting your own assistant takes the server's web address and either a sign-in to Bookatu or an API key. #### Which Bookatu AI should I start with? Start with auto-reply if new clients message you while you are busy. Start with the assistant in your admin if your time goes on tasks such as moving bookings or adding services. If an AI assistant app you already use for other work can connect to an MCP server, you can connect it to your account. Bookatu then lets it check your availability and move bookings, as far as the connection allows. #### What can't an AI do in my Bookatu account? Bookatu sets the same limits for auto-reply, the assistant in your admin and any assistant you connect. - Bookatu does not let any of them take a payment. - Bookatu gives none of them a way to delete your client list or your past bookings. #### Questions owners ask ##### Is an AI receptionist the same as an AI booking assistant? No. An AI receptionist replies to your clients' messages for you, and on Bookatu it sends your booking link so the client books for themselves. An AI assistant works for whoever uses it, and the assistant in your Bookatu admin can book a client in for you once you confirm. ##### Can I use Bookatu's AI receptionist and AI assistant together? Yes. They do different jobs and run side by side. Auto-reply answers new clients' messages, and the assistant in your admin helps you with the work inside Bookatu. ##### Does an AI receptionist cost extra on Bookatu? Auto-reply, Bookatu's receptionist, is part of every plan. Below it on the Channels page is a second setting, AI receptionist, for more natural replies, and the page says what that one needs. The page at https://bookatu.com/en-nz/pricing lists every add-on. ##### Do I need to understand MCP to use AI with Bookatu? No. Auto-reply is a setting and the assistant in your admin is a chat. Only connecting your own AI assistant uses MCP, and it takes a web address and a sign-in or an API key. #### Where to start Go to Inbox, then Channels, and turn on Auto-reply new chats. The guide at https://bookatu.com/en-nz/help/ai-receptionist explains what it answers. To see what the assistant in your admin can do, read https://bookatu.com/en-nz/ai. To see which AI assistant apps you can connect, and how, start at https://bookatu.com/en-nz/ai/assistants. ### How do I get my business found on ChatGPT and other AI assistants? People ask AI assistants where to book. Here is what those assistants read, and what your booking page on Bookatu already gives them. The Bookatu team · 2026-11-05 · updated 2026-11-06 · Grow your business · https://bookatu.com/en-nz/blog/get-your-business-found-by-ai-assistants · markdown: https://bookatu.com/blog/get-your-business-found-by-ai-assistants.md > **Update, 6 November 2026** > > What has changed for clients' own AI assistants is in Can my clients book me from their own AI assistant? > **The short version** > > - AI assistants search the web and read the pages they find. A person can also give their assistant your link. > - Your booking page on Bookatu shows your services, prices and opening hours as text. > - Google says a Business Profile can help you show up in its AI answers. Add your booking link to it, and keep its details the same as on your booking page. > - Google says you need no llms.txt file or special markup, and a large study found markup made no clear difference to AI citations. To get your business found on ChatGPT and other AI assistants, make sure the pages they read about you are complete and give the same details. For a salon, spa or studio on Bookatu, that starts with your booking page and your Google Business Profile. #### How do AI assistants find a salon, spa or studio? AI assistants that answer from the web search it, then read the pages they find. A person can also give their assistant a link and ask about it, and the assistant opens that page. So an assistant usually finds you the way a search engine does. The work that helps people find you on Google and Bing helps with assistants too. #### Can AI assistants read my booking page on Bookatu? Once your booking page is published, Bookatu lets search engines read it. As of November 2026, it also lets in the crawlers ChatGPT, Claude and Perplexity use to search the web and to open a page someone asks about. Bookatu asks the crawlers that collect pages to train AI models to stay off your booking page, because what is on it is yours. As of November 2026, Google uses one setting both for training Gemini and for letting the Gemini app answer from a page, so the Gemini app is asked to stay off too. Google Search and its AI features can still use your page. Bookatu can also add your booking page to the sitemap it gives Google and Bing. Open Settings, then SEO & analytics, and switch on List my booking page in search. It stays off until you switch it on, and search engines can find a published booking page without it. #### What should my booking page show so AI assistants get it right? The same things a new client needs to know, written out as words: - Each service with a name a client would use, how long it takes and its price. You add these under Catalog, in the list named for your kind of business, such as Services or Treatments. - Your opening hours, under Settings, Opening hours. - Your address and your City or town, under Settings, Business details. - Prices and details as text. A price list in a photo is easy for an assistant to miss. Bookatu shows each service with how long it takes and its price, your opening times and your address as text on your booking page. So filling them in is most of the work. Under Settings, SEO & analytics, you can also write the title and short description your page gives search engines. #### Does a Google Business Profile help my business show up in AI answers? Google says it can, in Google Search. As of November 2026, Google's guide to its AI features says a Business Profile can help your services show up in its AI answers and in its other results. Keep your name, address and hours the same there as on your booking page, and add your booking link. To get the link, open Grow, then Google & social, in Bookatu. Bookatu is not one of Google's booking providers, so the link opens your own booking page. An appointment booked from it shows Came via Google, so you can see what your profile brings in. The same page has a link for Bing Places for Business. #### Do I need llms.txt or special markup for AI assistants? Google says no for its own AI features, and the studies so far point the same way for other assistants. As of November 2026, Google says its AI features in Search need no special markup and no AI text files. In June 2026 it added that an llms.txt file neither helps nor hurts how a site shows in Search. An llms.txt file is a plain text guide to a website, written for AI tools. Markup is code in a page that labels its facts for machines. A study by Ahrefs published in May 2026 found no clear rise in AI citations for pages that added markup. Another Ahrefs study, published in June 2026, found that almost every llms.txt file it checked got no requests in May. So put your effort into the words on your booking page. #### Does being mentioned on other sites help with AI assistants? It seems to. Studies published in 2025 found that brands mentioned and linked to across the web tend to show up more often in AI answers. They show that the two go together, but they did not test whether one leads to the other. For a local business, that could be a write-up in the local paper, or a brand you stock listing you as a stockist. When someone mentions you, ask them to link to your booking page. #### Questions owners ask ##### Does Bookatu stop ChatGPT from reading my booking page? No. As of November 2026, once your booking page is published, Bookatu lets in the crawlers ChatGPT uses to search the web and to open a page someone asks about. It asks the crawlers that collect pages to train AI models, OpenAI's included, to stay off your booking page. ##### Can Bookatu get my business recommended by ChatGPT? No one can promise that, because each assistant decides what it shows. As of November 2026, Bookatu lets ChatGPT's search crawler read your published booking page, with your services, prices and hours as text. ##### How do I add my booking link from Bookatu to my Google Business Profile? In Bookatu, open Grow, then Google & social, and copy your Google link. The Google card there shows, under How to add it, where the link goes in your Business Profile. #### Where to start This week, open your booking page with View site and read it as a new client would. Check that every service has a price and says how long it takes, and that your hours are right. Then add your booking link to your Google Business Profile. The help articles at https://bookatu.com/en-nz/help/your-booking-page and https://bookatu.com/en-nz/help/get-booked-on-google-and-social walk through your booking page and your Google link. ### Track website bookings in Google Analytics and Meta Track bookings in Google Analytics, Tag Manager or the Meta pixel, with each booking's price, from your website widget. Client details are never sent. The Bookatu team · 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/track-website-bookings-in-google-analytics · markdown: https://bookatu.com/blog/track-website-bookings-in-google-analytics.md > **The short version** > > - The pop-up, inline menu and floating button tell your page each step. > - A booking carries its service, price and currency, and counts once. > - Tick your Google tag or Meta pixel in the builder. > - No event carries your client's name, email or phone. To track bookings in Google Analytics, use the events the Bookatu website widget sends to the page it sits on. Your tags can then count each booking as a conversion, with its value. #### What the widget tells your website Each step is an event: ready, service_selected, staff_selected, time_selected, booked, request_sent, handoff, error and closed. A request_sent is a booking request, when you approve bookings first. A handoff means the visitor went on in a new tab, for example to pay a deposit. A booking also carries the service, start time and time zone, its value and currency, and a reference made for your analytics. The value is the service's price before any promo code or surcharge. The reference is not the booking's id, and it opens nothing. #### Count each booking once, with its value A booking fires once, even if the confirmation or the whole page reloads in the same tab. With Google tag ticked, it arrives in Google Analytics as bookatu_booked, with its value, currency and the reference as the transaction id. With Meta pixel ticked, it counts as Schedule. #### How to switch it on 1. **Open the builder.** Go to Grow, then Website widget, and choose Pop-up, Inline menu or Floating. The plain Button opens your booking page in a new tab instead. 2. **Tick your tags.** Under Also tell your own analytics tags, tick Google tag, Meta pixel or both. 3. **Paste the new snippet.** Press Copy and paste it on your site in place of the old one. 4. **Test it.** Publish the page and make a test booking. Site builders often block scripts in preview mode. The widget only calls tags your site already loads, so your cookie banner stays in charge. ##### Using Tag Manager Tag Manager needs nothing ticked. Each event arrives on the dataLayer as bookatu_ plus its name, with the details under bookatu. So a trigger on the custom event bookatu_booked counts bookings. The older names bookatu:booked and bookatu_booking_complete still fire. #### Links that open at the right offer In the builder, Opens on a day and Promo code go into the snippet, in every mode. A code only counts while it is live. An expired or used-up one is left off, and the booking still goes through. Your booking page reads ?date= and ?promo= too. Our post Promo codes that fill a quiet week and tell you what worked helps you choose one. #### See which campaign sent the booking When the page with your widget was reached from a link with utm_source, utm_medium or utm_campaign, the booking shows it under Came via. An ad click from Google or Meta is marked, but its click id is never stored, so Bookatu doesn't upload offline conversions to your ad account. #### Questions owners ask ##### Does the widget send my clients' names or emails to Google or Meta? No. No event carries a name, email, phone or note. ##### Will a booking be counted twice if the client refreshes the page? No. Each booking fires once, even when the whole page reloads in the same tab. #### Where to start Open Grow, then Website widget, tick your tag and make a test booking. Our help article Add booking to your own website shows where to paste the snippet, and our post Add a Book Now button to your website or Instagram bio covers the button. ### Add a public holiday surcharge to online bookings Add a public holiday surcharge, or charge more at busy times, and show it before clients book. New Zealand and Australian holidays are built in. The Bookatu team · 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/public-holiday-surcharge-for-online-bookings · markdown: https://bookatu.com/blog/public-holiday-surcharge-for-online-bookings.md > **The short version** > > - Add a rule in Settings, Surcharges: a percent of the price or a fixed amount. > - Pick dates, tick Use public holidays for New Zealand or Australia, or add weekly times. > - Clients see it on the times, on the review before they book, and on their confirmation and receipt. > - Bookings already made keep their price. To add a public holiday surcharge, make a rule in Settings, Surcharges. Bookatu marks every time it covers and shows the extra before the client books. Until you add a rule, prices are the same on every day and at every time. #### Tell clients before they book A surcharged time shows a badge, such as +15%, with a line saying what it is for. The review shows the surcharge on its own line before the total, and your website widget shows the total with it too. It is then on the confirmation, the reminder and the receipt. If a time now costs more than the page showed, say because you added a rule while the client was booking, the booking is refused with a reason. Nothing is charged. It is still worth checking the consumer rules where you are. #### How to switch it on 1. **Open Surcharges.** Go to Settings, open Surcharges and press Add a surcharge. 2. **Name it.** Name clients see is shown beside the price, like Public holiday surcharge. 3. **Set the amount.** Under Kind, choose Percent of the price or Fixed amount, then enter it. 4. **Choose when.** Pick Dates on the calendar, tick Use public holidays and choose your country, or add a weekly time under Every week, such as Sunday afternoons. 5. **Check and save.** Keep Every service ticked or choose services. Read the preview, then press Add surcharge. Press Switch off to pause a rule and keep it. Changing rules needs Manage the business. #### Which public holidays are included Use public holidays covers the national public holidays of New Zealand or Australia, 2026 to 2028, with the Mondayised and observed days. Regional anniversary days and state holidays are not on the list, so pick those on the calendar. Clients are told which holiday it is, like Public holiday surcharge (Christmas Day). Outside New Zealand and Australia, pick your own dates. #### How the amount is worked out - When two surcharges cover the same time, only the higher one applies. - A percent is of your list price before any promo code, and a code never comes off the surcharge. - A fixed amount is added once per booking. - A booking that costs nothing is never surcharged. - A percent deposit is worked out on the total, surcharge included. A flat deposit stays the same. #### Questions owners ask ##### If I add a Christmas surcharge now, do bookings already made change? No. Bookings already made keep the price they were made with, even when you change or switch off a rule. ##### What if a client moves their booking onto a public holiday? Nothing is added. A moved booking keeps the smaller of its old surcharge and the new time's, so a move off a holiday drops it. ##### Can my team waive the surcharge? Yes, on the New booking form, if their role has Refund orders. The waiver is recorded in the audit trail with their name. #### Where to start Add one rule for the next public holiday and check the preview. If you would rather close that day, our post Close on public holidays and set holiday hours shows how. Our help article Deposits covers deposits, and our post How to Price Your Services Without Guessing helps with the price underneath. ### Close on public holidays and set holiday hours Close on New Zealand or Australian public holidays in one go, open on a day you are usually shut, or change one date's hours. Your weekly hours stay as they are. The Bookatu team · 2026-10-30 · Product · https://bookatu.com/en-nz/blog/close-on-public-holidays-and-set-holiday-hours · markdown: https://bookatu.com/blog/close-on-public-holidays-and-set-holiday-hours.md > **The short version** > > - Special dates is linked from Settings, Opening hours. > - Close a date, open one you usually close, or change one date's hours. Your weekly hours stay as they are. > - Close on public holidays adds the national holidays of New Zealand or Australia, up to the end of 2028. > - Bookings already on those dates stay booked. To close on New Zealand or Australian public holidays, open Special dates, pick your Country under Close on public holidays and press the button. To change a single day, add a special date. Clients can only book what is open, on your booking page and your website widget. #### Set special opening hours for one date 1. **Open Special dates.** Go to Settings, then Opening hours, and follow the Special dates link. 2. **Pick the date.** Under Add a special date, choose the Date. 3. **Choose the hours.** Under That day, pick Closed all day, or Open, with these hours and set Opens and Closes. 4. **Save.** Press Save date. Saving a date that is already special replaces its hours. Press Remove on a date and it goes back to your weekly hours. Changing special dates needs Edit the calendar. Other roles can only view them. #### Close on every public holiday in one go Under Close on public holidays, pick the Country. The preview lists every date it will close, from today to the end of 2028, and the button says how many. Press it and they all appear in your list, each with the holiday's name. It only closes dates. A date you have already set stays as you set it, and pressing it again adds nothing. ##### What the list includes For New Zealand, the national public holidays, Matariki included, and the Mondayised days when a holiday falls on a weekend. Both days are listed, so remove the one that does not apply to you. For Australia, the seven national public holidays and their national weekend substitutes. ##### What it leaves out New Zealand's regional anniversary days, and Australia's state and territory holidays. Easter Saturday and Sunday are left out too, and so is the Monday some states add when Anzac Day falls on a weekend. Add the ones you keep as special dates. Outside New Zealand and Australia, add your holidays the same way. #### Bookings already on that date A special date changes what clients can book. It never cancels or moves a booking already made. The list shows how many bookings sit on each date, so check them on the calendar and contact those clients. #### Special date, blocked time or a surcharge? - The whole business is closed or on different hours: add a special date. - One person is away: block their time on the calendar. Our help article Blocking off time shows how. - You are open but charge more: add a surcharge. Our post Add a public holiday surcharge to online bookings explains it. #### Questions owners ask ##### Will closing a public holiday cancel the bookings already on it? No. They stay booked, and the list shows how many are on each date. ##### Does it include Matariki and the Mondayised days? Yes. Matariki is on the New Zealand list, and so are the Mondayised days, each named. ##### Do I need to do this every year? The list runs to the end of 2028, so one press covers every national holiday on it until then. #### Where to start Open Special dates and preview the holidays for your country. Our help article Setting your opening hours covers your weekly hours, and our post Set the hours you actually work (and let clients book around them) helps you choose them. ### Client and booking tags: label, filter and email Client tags are your team's labels, like VIP or Bridal. Put them on clients and bookings, see them on the calendar, and email the subscribed clients who have one. The Bookatu team · 2026-10-30 · Product · https://bookatu.com/en-nz/blog/client-and-booking-tags · markdown: https://bookatu.com/blog/client-and-booking-tags.md > **The short version** > > - Make your tags once, from the Tags button on Clients. > - Put them on clients, bookings or both. Booking tags show on the calendar, client tags on the client list. > - Filter your client list by tag, or email the subscribed clients who have one. > - Tags are for your team. They don't show on your booking pages or in client emails. Client tags are your team's own labels, like VIP, Patch test done or Bridal. Make one once. A client's tags show on the client list, and a booking's tags on the calendar and the booking. #### How to switch it on 1. **Open Tags.** Go to Clients and press Tags. 2. **Name it.** Under Add a tag, type a Name of up to 40 characters. 3. **Choose where it goes.** Under For, pick Clients and bookings, Clients only or Bookings only. Then pick a Colour. 4. **Save.** Press Add tag. You can use it straight away. You can keep up to 200 tags. Making and changing them needs Manage the business. Deleting one also needs Delete records, and a tick to confirm when it is in use. #### Tag a client or a booking On a client's page, pick a tag under Add a tag and press Add. A booking's page works the same way, and the New booking form has Tags (optional) to tick as you book. Tagging a booking needs Edit the calendar. Calendar entries and the client list show up to two chips, then a count of the rest. Short calendar entries show coloured dots instead. The booking panel lists every tag in full. #### Filter your client list by tag On Clients, tap a tag in the Tags row to see who has it. Tap another, and the list narrows to clients who have both. #### Email clients by tag In Grow, Newsletters, choose an audience such as Clients tagged Bridal. It follows the same opt-in rules as every other audience, so only clients who said yes to marketing get it. A deleted tag sends to nobody. #### Who sees tags Tags don't show on your booking pages or in client emails, and they are left out of AI assistants and webhooks. Apps you connect with an API key that can read clients or bookings do see them. A client who downloads or asks for their data sees the tags on them, so name tags as you would say them to the client. #### Questions owners ask ##### Can I use a tag for allergies? Keep medical details out of tags. Add them to the client's record as Allergy or reaction instead, which is always shown first. ##### What happens to tags when I merge two client records? The record you keep carries every tag either one had, each once. ##### Do tags show up in my exports? Booking tags do. Export bookings (CSV) on the calendar adds a Tags column when a booking in the file has one, for someone with See analytics & earnings, Export data and See everyone's calendar. The client list's Export CSV has no tags. #### Where to start Make three tags you already say out loud at the desk, and put them on today's clients. Our help article Client notes and photos covers what belongs in the record instead, and our post Salon staff permissions: what each role should see explains Manage the business and Edit the calendar. ### Ask clients your own questions when they book Custom booking questions let you ask clients a few things of your own, like hair length or the occasion. Here is how, and when an intake form fits better. The Bookatu team · 2026-10-30 · Product · https://bookatu.com/en-nz/blog/custom-booking-questions · markdown: https://bookatu.com/blog/custom-booking-questions.md > **The short version** > > - Open Catalog, then Forms, and press Booking questions. The same button is on your Services page. > - Ask a question for all services or for one. > - Answers can be short or long text, a single or multiple choice, yes or no, a number or a date. > - Your team reads the answers on the booking. > - Nothing changes until you add a question. Health details belong in an intake form. Custom booking questions let you ask clients a few things of your own while they book. They appear on the Your details step of your booking page and in your website widget. Apps that book through the API have to answer the required ones too. #### A booking question or an intake form? Use a booking question for a quick fact that helps you plan. Is your hair past your shoulders? Is this your first visit? How many are in the bridal party? Use an intake form for health history, allergies, medication, consent or anything clinical. A form is kept apart from the booking and signed by the client. The question editor says the same, and a question that reads as medical is flagged when you save it. Our post Client intake forms your clients can finish on a phone shows how forms work. #### How to add a question to your booking form 1. **Open Booking questions.** In your admin, open Catalog, then Forms, and press Booking questions. You need Manage the business to add questions. 2. **Choose who is asked.** Under Asked for, pick All services or one service. 3. **Choose the answer.** Under Answer, pick Short text, Long text, Single choice, Multiple choice, Yes / no, Number or Date. For a choice, type one option a line under Choices. 4. **Write the question.** Type your Question. Add Help text if it needs a reason, like So we book enough time. 5. **Save it.** Tick Clients must answer it to book online if it has to be answered, then press Add question. Use Up and Down to set the order. #### Where your team reads the answers - On the booking's own page, under Booking questions. Anyone who can edit the calendar can fill them in or change them there. - In the calendar's booking panel, as a short summary. - In Export bookings (CSV) on the calendar, one column per question, for someone who can see everyone's calendar. - In the client's own data export. Each answer keeps the question as the client saw it. So rewording a question later never changes an answer already given. #### Questions owners ask ##### How many booking questions can I ask? Up to 10 for any one service, counting its own questions and the ones for all services. ##### Do bookings I make myself need answers? No. Your team can leave any question blank on bookings they make, or fill the answers in. ##### What happens on a waitlist or Quick swap claim? A one-tap claim has nowhere to answer. If the service has a required question, the client is sent to your booking page to answer it and book there. Optional questions are not asked on a claim. ##### Do repeat bookings ask the questions again? No. A repeat booked online keeps the first visit's answers on every visit it sets up. #### Where to start Add one optional question to your most-booked service, make a test booking, and read the answer on the booking. When a client books several services in one visit, each question is asked once. Our post Let clients book multiple services in one appointment explains those visits, and our help article Intake and consent forms covers the health side. ### Booking terms clients tick before they book Add a booking terms and conditions checkbox to your booking page. Clients tick it before booking online, and each booking keeps the version they accepted. The Bookatu team · 2026-10-30 · Product · https://bookatu.com/en-nz/blog/booking-terms-clients-tick-before-they-book · markdown: https://bookatu.com/blog/booking-terms-clients-tick-before-they-book.md > **The short version** > > - Write your terms once in Settings, under Booking terms. > - Your booking page and website widget show them above Confirm, with a box the client ticks. > - Each booking keeps when the terms were accepted, and which version. > - Leave it empty and nobody is asked. Bookings you make yourself are never asked. > - Booked by and the History card show who made a booking and what changed since. To add a terms and conditions checkbox, open Settings and choose Booking terms. Once you save some terms, every online booking needs a tick before the client can confirm. #### Why a tick box beats terms in your footer A policy in your footer is easy to miss. A box above Confirm puts your rules in front of clients at the moment they commit: when to arrive, what happens if they run late, a patch test before colour. For help with the wording, see our post Salon Cancellation Policy Examples You Can Copy Today. #### How to add your booking terms 1. **Open Booking terms.** Go to Settings and choose Booking terms, under Essentials. 2. **Paste your terms.** Type or paste them into Your booking terms. It is plain text, up to 5,000 characters, and line breaks are kept. 3. **Save.** Press Save booking terms. The note under the box shows the version in force now. 4. **Check it.** Open your booking page and look above Confirm. Saving terms needs Manage the business, which owners and admins have by default. #### What clients see Your terms appear above Confirm on your booking page and in your website widget, with a box that starts unticked. The client must tick it to book. Clients taking a time from your waitlist or from a Quick swap see the same box. Apps that book through the API have to say the client accepted. #### Proof a client accepted your terms Open a booking and you see Terms accepted, with the date and a short version code. The same record is in the client's data export. Any change to the words makes a new version, and bookings already made keep the one their client accepted. If you change the terms while a client has the page open, they are asked to read them and tick again. Keep a copy of each version you use. #### See who made a booking, and what changed Each booking shows Booked by on its page and in the calendar panel, with how it came in. It names a team member, Client online, an API key or connected app by the name you gave it, or AI assistant, with who on your team confirmed it when someone did. A client is never named. The History card on the booking lists each change, who made it and when, on your business's clock. It is shown to roles with Manage the business: owners always, and admins by default. Our post Salon staff permissions: what each role should see explains the roles. #### Questions owners ask ##### Do clients tick the box when I book them in myself? No. Bookings you or your team make are never asked. ##### What happens to old bookings when I change my terms? Nothing. Each keeps the version its client accepted, and new bookings take the new one. ##### Can I put links or formatting in my terms? No. Terms are plain text and always shown as text. Line breaks are kept, so short paragraphs work well. #### Where to start Paste the policy you already use into Booking terms and make a test booking. Then read our post How to handle late cancellations without losing clients. ### Block a room, or repeat blocked time every week Recurring blocked time repeats every week, for up to two years. You can also take one treatment room or chair out of online booking without closing. The Bookatu team · 2026-10-30 · Product · https://bookatu.com/en-nz/blog/block-a-room-or-repeat-blocked-time · markdown: https://bookatu.com/blog/block-a-room-or-repeat-blocked-time.md > **The short version** > > - Open Calendar. The Blocked times card is under the calendar. > - Under Block, choose Everyone, a team member, or a room or chair. > - A blocked room only takes away the services that need it. > - Tick Repeats weekly to repeat a block on the days you pick, for up to two years. > - Remove one day, that day and the ones after it, or the whole series. To block a room, choose it under Block in the Blocked times card on your calendar. To make blocked time recur, tick Repeats weekly before you press Block time. You need Edit the calendar to do either. #### How to block a treatment room or chair 1. **Open Blocked times.** Go to Calendar and scroll to the Blocked times card. 2. **Set the time.** Choose the First day and Last day, then From and To, or tick All day. 3. **Pick the room.** Under Block, choose it from A room or chair, which lists the rooms and chairs you have set up. Add a reason if you like, such as Deep clean. 4. **Block it.** Press Block time. Only services that need that room lose those times. If another room of the same kind is free, the booking goes there instead. When every room of that kind is blocked, those times go. Services that need no room are not touched. In the day view, a Rooms and chairs strip shows what holds each room. If your team books into a blocked room from the admin, they are warned first and can press Book anyway. A class in a blocked room is flagged, never cancelled. #### How to repeat blocked time every week 1. **Tick Repeats weekly.** First day becomes Starting. 2. **Choose the days.** Pick one or more days under Repeats weekly on. 3. **Choose how often.** Under Every, pick Week, 2 weeks, 3 weeks or 4 weeks. 4. **Set Until.** It is set about three months ahead, and can go up to two years. Then press Block time. A weekly block keeps to your clock. A 9:00 to 10:00 block stays 9:00 to 10:00 when daylight saving starts or ends. If you change your business's time zone, weekly blocks keep their times on the new clock. #### How to remove one day or the whole series Remove a weekly block from its day on the calendar, then choose This one, This and following, or The whole series. The days of a weekly block can't be dragged. #### Blocked time, a break or a special date? - A lunch break the whole business takes belongs in Opening hours, in Settings. One person's break goes in their own hours on Team. - A day the whole business shuts, like a public holiday, is a special date. Open Special dates from Opening hours. - Anything else that comes round each week, like a team meeting or fortnightly training, is a weekly block. #### Questions owners ask ##### Does blocking a room cancel bookings already in it? No. Bookings already in that room stay put, so move them yourself if you need to. ##### Does a weekly block move when the clocks change? No. It stays at the same time on your business's clock. ##### Can I block every other week? Yes. Under Every, choose 2 weeks. The weeks in between stay free. #### Where to start Block the room you know is out next week, then make your weekly team meeting a repeating block. Our help article Blocking off time has the steps. For a week of leave as one entry, see our post Check clients in, edit bookings and block time off from your calendar. ### Run a gift card offer with a promo code A gift card promo code takes money off what the buyer pays, while the card keeps its full value. Plus how to email, resend or replace a card. The Bookatu team · 2026-10-30 · Recurring revenue · https://bookatu.com/en-nz/blog/gift-card-offer-with-a-promo-code · markdown: https://bookatu.com/blog/gift-card-offer-with-a-promo-code.md > **The short version** > > - Tick Can be used on gift cards on a promo code. Every code starts with it off. > - The buyer pays less. The card keeps its full value. > - Online gift card sales are paid by card and need Stripe connected. > - From a card's page, resend its email or reissue it with a new code. A gift card promo code lowers the price a buyer pays, never the value on the card. Use it for a Christmas offer, like 10% off gift cards bought this week. #### Price down, value kept For example, with a 10% code a $100 card costs the buyer $90 and is worth $100 when spent. The card records the code and what it took off. A code that would make a card free is refused. #### How to set up a gift card promo code 1. **Open Promo codes.** In your admin, open Grow, then Promo codes. 2. **Make the code.** Under Create a code, set the Code, Type and Value. Add Max uses and Expires to keep the offer short. 3. **Tick Can be used on gift cards.** Then press Create code. For a code you already have, press Allow on gift cards in the list. Switching a code on or off for gift cards needs Manage the business. #### What buyers see While you have a live code on gift cards, your gift card page shows a Promo code field. An applied code shows what the buyer pays and what the card is worth. A code that has expired, is used up or isn't for gift cards is refused with a clear message. Your code's Expires date and Max uses still apply. A use is held while the buyer pays, and counted once the payment goes through. If they don't pay, the checkout closes after 30 minutes and the use comes back after that. The Promo codes list shows uses held at checkout and the gift cards each code sold. #### Give, resend or replace a gift card To give a card away, use Issue a gift card under Catalog, Gift cards, which needs Manage the business. Tick Email it to them, which starts unticked. The recipient gets the same email as a paid card. Your note stays on the card's record and is never emailed. Each card's page shows its History, from payment to emails, redemptions and voids. Under Do something with this card: - Resend email sends it again to the recipient on file, up to three times a day. - Reissue with a new code voids the old code and moves what is left to a new one. It is emailed to the recipient if there is an address on file. Neither works for a card that is void, used up or expired. Resend needs Adjust loyalty and gift cards, and Reissue needs Manage the business too. With Export data, Download CSV on the Gift cards page includes the promo code and discount. #### Questions owners ask ##### Can clients use my booking promo codes on gift cards? Only the codes you switch on. Can be used on gift cards is off for every code until you tick it. ##### If I refund a gift card, does the code get its use back? No. The use stays counted, just as a refunded booking's code stays used. #### Where to start Make one code for gift cards, give it Max uses and an end date, and put it in your next newsletter. Our post Gift cards: a quiet cash-flow engine for small studios has more ideas, and our help article Promo codes and discounts covers codes for bookings. ### Build on Bookatu safely with a booking API sandbox A sandbox is a test business with sample data and bk_test_ keys. Partners and agencies can test a booking API integration without real clients or real money. The Bookatu team · 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/booking-api-sandbox-for-partners-and-agencies · markdown: https://bookatu.com/blog/booking-api-sandbox-for-partners-and-agencies.md > **The short version** > > - A sandbox is a test business of your own, with sample staff, services, clients and bookings. > - It answers the same API, with the same booking rules, as a live business. > - Its keys start bk_test_, and a test key sent to a live business is refused. > - Messages go to a test outbox, and payments are simulated. If you build booking tools for salons, spas or clinics, you may have tested on a real business before. A practice booking lands in a real calendar, and a confirmation reaches a real inbox. A sandbox ends that: it is a test business inside Bookatu, and nothing it does reaches a real client or moves real money. #### What a sandbox is Each sandbox is a business of its own, with its own slug, so the calls you would make to a live business work on it unchanged. A Test mode banner runs across its admin, and a Test business ribbon on its booking page asks visitors not to enter real personal details. It is never listed anywhere public, never indexed and never billed. #### How to make a sandbox 1. **Sign in.** Use any confirmed Bookatu login. You don't need a business on Bookatu. 2. **Open your sandboxes.** Go to /developers/sandbox. You can have up to three at a time. 3. **Pick the basics.** Choose a name, a time zone and a currency, and accept the test-mode terms. 4. **Keep the first key.** It comes with the sandbox, has every scope, lasts 90 days and is shown once. Prefer code? POST /api/developer/sandboxes makes one, signed in with your Bookatu login rather than an API key. #### What is already in it A new sandbox has three team members, seven services and five made-up clients, with bookings past and upcoming, a class and a waitlist entry. One service takes a deposit and one asks a booking question. Every client email is at an example domain, and every phone number is in a range kept for fiction. Times are in your zone and prices in your currency. A reset puts it all back and keeps your keys, webhook endpoints and connected apps. #### Test keys, live keys and livemode A sandbox issues only test keys, which start bk_test_. A live business issues only live keys, which start bk_live_. Send either to the wrong kind of business and the call is refused with 403 LIVEMODE_MISMATCH before anything runs, on every endpoint, the keyless ones included. Every answer from a sandbox carries the Bookatu-Livemode header, and every JSON answer says livemode: false. Building a front end on the keyless endpoints? Send Bookatu-Livemode: false with each request, and a test build can never book at a real business. ```sh curl https://bookatu.com/api/v1/sbx-k3v9q2m1/services -H "Bookatu-Livemode: false" ``` #### What leaves a sandbox, and what never does Every email, text, WhatsApp message and push notification it would send is kept in its test outbox. Read it in the admin, or with GET /api/v1/{slug}/sandbox/outbox. Payments go to a test checkout with buttons, never a card number. Two things do leave: webhooks to the endpoints you register, marked livemode: false, and an email to you a week before an unused sandbox is deleted. It goes after 30 days with no API call on its keys and no visit to its admin. #### Questions owners ask ##### Will my developer's testing ever reach my clients? No. A sandbox has its own made-up clients, its messages stay in its outbox, and a test key can't be used on your business at all. ##### Does my agency need my login to build for me? No. They build against a sandbox made with their own login. When it works, you or an admin on your team make them a live key, with only the scopes they need. ##### Can a sandbox become my real booking page? No. A sandbox can never be turned into a live business, and a live business can never become a sandbox. #### Where to start Make a sandbox, list its services with the test key, book a time and read the confirmation in the outbox. Our developer guides Testing with a sandbox and Going live cover the rest. Our post AI agents and your booking data: what a key lets in, and what it never touches explains keys for owners. ### Test an AI booking agent against a sandbox over MCP Point your AI agent at a Bookatu sandbox through the MCP server. It books and cancels for made-up clients, and no real client or real money is ever touched. The Bookatu team · 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/test-an-ai-booking-agent-in-a-sandbox · markdown: https://bookatu.com/blog/test-an-ai-booking-agent-in-a-sandbox.md > **The short version** > > - Connect with a sandbox's test key, or sign in with OAuth and pick the sandbox. > - The agent gets the same tools and booking rules as at a live business, plus three sandbox tools. > - Every message it causes stays in the outbox, and payments are simulated. > - A live business never lists the sandbox tools. An AI agent that books appointments chooses for itself which tool to call. You want to watch it find a time, book and cancel before it does any of that at a real business. A sandbox gives it somewhere safe to practise, and gives you a way to test an MCP server integration from start to finish. #### Connect your MCP client The business MCP server has one address for every business: https://bookatu.com/api/mcp. A credential reaches only its own business, so a sandbox's test key reaches that sandbox and nothing else. Send the key as a Bearer token, and send Bookatu-Livemode: false where your client allows it, so a live key pasted in by mistake is refused before anything runs. ```http POST https://bookatu.com/api/mcp Authorization: Bearer bk_test_YOUR_KEY Bookatu-Livemode: false Content-Type: application/json MCP-Protocol-Version: 2025-06-18 {"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}} ``` With OAuth, the client signs in instead, and Bookatu's consent page lists your sandboxes marked (test). Claude Desktop adds the server as a custom connector, Cursor reads it from its MCP config file, and the MCP Inspector calls each tool by hand. Our developer guide Test your AI agent has the setup for each. #### The three sandbox tools - sandbox_outbox reads every message the sandbox kept instead of sending, newest first. It needs customers:read. - sandbox_simulate makes one event happen to one booking: a deposit paid, a card declined, a checkout abandoned, the client cancelling, a no-show, or reminders coming due. - sandbox_reset wipes the sandbox and puts the sample data back. It takes the sandbox's own test key, never a connected app. They appear in tools/list only at a sandbox. At a live business each name is an unknown tool, so its tool list stays exactly as it was. #### A test run, start to finish 1. **Find a time.** Ask for a haircut slot on Tuesday afternoon. The agent should call list_services and get_availability, and answer on the business's clock. 2. **Book it.** Ask it to book Mia, with an email at example.com. create_booking answers a ref and an appointmentId. 3. **Check what she was sent.** sandbox_outbox shows the confirmation that would have gone out. 4. **Cancel it.** cancel_booking cancels as the business, and the client is sent no message about it. If your agent says she was told, you have found a bug. 5. **Start again.** Ask it to reset the sandbox. A good agent asks you first. To test a client's own cancellation, use sandbox_simulate with booking.client_cancelled. It emails her a notice, kept in the outbox, only when Email clients when they cancel online is on in the sandbox's settings. That setting starts off. #### Read livemode and the refusals At a sandbox, every answer carries the Bookatu-Livemode header, set to false. Every tool result, a refusal included, says livemode in its _meta, and a successful one says it in structuredContent too. A refusal comes back with its code, such as APPOINTMENT_NOT_FOUND for a booking that is not the sandbox's, or NO_OPEN_CHECKOUT when deposit.paid finds no open test checkout. A good agent reads the code and tries something else. #### Questions owners ask ##### Can an agent tested in a sandbox touch my real business? Not with its test credential, which reaches its own sandbox only. To work on your business, it needs a live key or a connection you approve. ##### Will my clients get test messages? No. A sandbox's clients are made up, and its messages are kept, never sent. ##### Will the sandbox tools show up at my business? No. They exist only at a sandbox, and your business's tool list stays as it was. #### Where to start Make a sandbox, connect your client with its test key and run the five steps above. When the agent behaves, our developer guide Going live covers the switch to a live key. ### Test booking webhooks and simulate payments in a sandbox Run a whole booking lifecycle in a Bookatu sandbox: a test checkout, a simulator for payments, cancellations and reminders, and webhooks marked livemode false. The Bookatu team · 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/test-booking-webhooks-and-simulated-payments · markdown: https://bookatu.com/blog/test-booking-webhooks-and-simulated-payments.md > **The short version** > > - A sandbox's payments go to a test checkout with three buttons: Pay (test), Decline (test) and Abandon. > - Each one runs the same handling as a real payment, so bookings reach the real states. > - The simulator makes an event happen now: a deposit paid, a client cancelling, a no-show, or reminders coming due. > - Webhooks reach your endpoints signed, with livemode: false. Payments and webhooks are often the hardest parts of a booking integration to test. A deposit needs a card, a reminder needs a day to pass, and a cancellation needs a client who changes their mind. In a Bookatu sandbox you can make each happen when you choose, with no real money. #### The test checkout Where a live business sends a client to pay, a sandbox sends them to a test checkout with three buttons and nothing to type. - Pay (test) completes the payment, and a booking held for its deposit is confirmed. - Decline (test) shows a declined card and leaves the checkout open, as a real one does. - Abandon lets the checkout expire, and a booking held for its deposit is let go. Every kind of checkout works this way, from deposits to gift cards and invoices, and refunds are simulated too. Memberships can't be bought in test mode yet. Where a booking needs a card saved, the card step has buttons as well: Save test card, and Save a card that will decline. #### Make things happen with the simulator POST /api/v1/{slug}/sandbox/simulate/{event} makes an event happen now to one of the sandbox's own bookings, through the same code as the real thing. It takes a test key with bookings:write. - deposit.paid pays the booking's open test checkout. - payment.failed declines the test card, and nothing else changes. - checkout.expired abandons the checkout. - booking.client_cancelled is the client's own cancellation, under the business's rules. - booking.no_show marks a no-show. A fee the policy sets waits for the owner, as at a live business. - reminders.due sends the booking's reminders as if their time had come. ```sh curl -X POST https://bookatu.com/api/v1/sbx-ab12cd34/sandbox/simulate/deposit.paid \ -H "Authorization: Bearer bk_test_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "appointmentId": "apt_..." }' ``` The answer gives the booking as it is now, the ids of the outbox messages the event kept and the webhook events it sent. #### Webhooks from a sandbox Besides its maker's expiry warning, webhooks are the one thing a sandbox sends out. Add an endpoint on the sandbox's Developer API page, at a public https address, and its events reach you signed, as a live business's do. Every payload has a top-level livemode field, false for a sandbox, and the X-Bookatu-Livemode header says the same. So one receiver can take both and never mistake a test booking for a real one. A sandbox's webhooks keep to smaller limits: up to 5 endpoints, 300 deliveries an hour, 3 retries, and Send test 10 times a minute. #### A booking lifecycle in five steps 1. **Add an endpoint.** On the Developer API page, add your receiver and keep its signing secret. 2. **Book the deposit service.** On the sandbox's booking page, book Full colour. Your endpoint gets booking.created, and you reach the test checkout. 3. **Decline, then pay.** Press Decline (test), then Pay (test). The booking is confirmed, and its confirmation is in the outbox. 4. **Bring the reminder forward.** Simulate reminders.due, then read the reminder in the outbox. 5. **Cancel as the client.** Simulate booking.client_cancelled. Your endpoint gets booking.cancelled, and the answer says whether the deposit was kept. #### Questions owners ask ##### Can a test payment ever charge a real card? No. A sandbox has no real payment account, and its checkout and card step have buttons only. No card number is ever asked for. ##### Will my live webhook endpoints get test events? Only if someone adds them to a sandbox. A sandbox's events go to the endpoints registered on that sandbox, each marked livemode: false. ##### Does the simulator work on my real business? No. At a live business it answers 404 NOT_A_SANDBOX, and in a sandbox it acts only on that sandbox's own bookings. #### Where to start Add one endpoint, book the deposit service and press Decline (test) before Pay (test). Our developer guide Testing with a sandbox lists every event and refusal. For deposits at a live business, read our post How deposits stop no-shows (and what an empty chair really costs). ### How to handle late cancellations without losing clients How to handle late cancellations: when to charge the fee, when to waive it, what to say, and how to pass the time to someone on your waitlist instead. The Bookatu team · 2026-10-29 · updated 2026-10-30 · Reduce no-shows · https://bookatu.com/en-nz/blog/how-to-handle-late-cancellations · markdown: https://bookatu.com/blog/how-to-handle-late-cancellations.md > **The short version** > > - Decide your rule before the message arrives, not while you are reading it. > - You have three fair options: charge the fee, waive it under a written grace rule, or let the time pass to someone who wants it. > - Whichever you choose, offer the time to your waitlist straight away. > - Apply the same rule to everyone. Being consistent matters more than being strict. A client messages at eight in the morning to say they can't make their ten o'clock. Your policy says the fee applies. Do you charge it, let it go, or try to save the slot? The best way to handle late cancellations is to decide in advance, then give every client the same answer. Here is how to handle a late cancellation. Check that it really is late. Choose charge, waive or swap, using the rules below. Send a short, kind reply. Then offer the time to your waitlist before it is lost. #### What counts as a late cancellation A cancellation is late when it comes inside your cancellation window, the notice you ask for, such as 24 or 48 hours. Your window decides it, not how busy you are that day. A cancellation 30 hours ahead with a 24-hour window is not late, even if it stings. It is not a no-show, either. A client who cancels late has told you, so you can still fill the time. In Bookatu, your Free cancellation window and Keep the deposit on a late cancellation, under Deposits & cancellations, decide when cancelling counts as late, together with any late-cancellation fee. Our help article Cancellations and your cancellation window walks through them. #### How to handle a late cancellation: charge, waive or swap Nearly every late cancellation ends in one of three answers. Decide ahead of time which situations get which. ##### When to charge the fee Charging is fair when the client knew the rule and you lose the time because of it. It is usually the right call when: - Your policy was shown when they booked, so the fee is no surprise. - The time can't be filled, such as a long colour or a treatment you have already prepared for. - It keeps happening. A client who cancels late every few weeks costs you more than one slot. Charge it calmly and offer a new time. The fee covers lost time. It isn't a punishment. ##### When to waive it Waiving is fair for genuine illness, an emergency, or a first late cancellation from a client with a clean record. The trap is waiving it for the clients you like and charging the ones you don't. The fix is a written grace rule that applies to everyone, such as one waived late cancellation per client per year, and illness always waived. Then a waiver is part of your policy, not a favour. If a deposit has already been kept and you decide to give it back, our help article Refunds and cancellation charges shows how. ##### When a swap beats both Sometimes the client wants out and someone else wants in. If a client on your waitlist would happily take that exact time, nobody needs to pay. The client who can't come is let off, the waiting client gets the appointment they wanted, and your chair stays full. #### What to say: three short replies you can adapt Keep it short and warm. Thank them, say what happens next, and offer a way forward. When the fee applies: > Thanks for letting me know, and I hope all is well. As it's inside our 24-hour window, the late fee applies this time. I'd love to see you soon. Would Thursday at 2 or Friday at 11 suit you? When you waive it under your grace rule: > Thanks for the heads-up, and I hope you feel better soon. We waive one late cancellation a year, so there's no fee this time. Just let me know when you'd like to rebook. When you offer the time to your waitlist: > Thanks for telling me. I'll offer your time to someone on our waitlist. If they take it, there's no fee. If nobody does, you're still booked in and can cancel then with the usual fee. Swap in your own window, days and wording. If you keep a deposit rather than charge a fee, say that instead. #### Fill the time before it's lost A late cancellation only costs you money if the time stays empty. The quickest way to fill it is to offer it to people who have already said they want to come in. Speed matters most, so a one-tap link beats a phone call. And stop offering once the time is too close for anyone to get there. In Bookatu, when a booking is cancelled, the freed time is offered automatically to your top waiting clients, ranked by what they have spent with you, each with a claim link. The first to claim it gets the time, and nothing is double-booked. If the service takes a deposit, that client pays it to keep the time. Our help article Fill cancellations automatically with the waitlist covers the setup, and our post Turn a cancellation into a booking with the waitlist has more on building the list. #### Let clients swap out instead of cancelling A waitlist fills a time once it is free. Quick swap starts one step earlier. A client who would pay a fee or lose their deposit can offer their time to your waitlist before they cancel, while they stay booked. 1. **The client asks to swap out.** When cancelling now would cost them a fee or their deposit, the page behind the Manage my booking button shows Ask to swap out beside Cancel (fee applies). They confirm with Yes, offer my time, and can Withdraw my request until someone takes it. 2. **Your waitlist hears about it.** Up to five waiting clients who want that service that day get a one-tap link by email, and by text when they have agreed to texts and texting is set up. Your best-spending clients go first. 3. **The first to tap takes it.** They get the same time with the same team member, room and equipment, and pay their own deposit if one is due. 4. **The client who asked is released.** They are cancelled with no late-cancellation fee. Their deposit is refunded to their card or the credit they paid with, or kept as account credit, whichever you choose. If nobody takes the time before offers stop, the client stays booked, is told so, and can still cancel with the usual fee. Stop offers before the start can be set from 1 to 336 hours, and is 2 unless you change it. You get an alert and an email when a swap goes through. Quick swap is off by default. Turn it on in Settings, under Quick swap, in Essentials. It needs the Manage the business permission, which owners and admins have from the start. It isn't offered for classes or group bookings, or while you approve online bookings first, among a few other cases the help article lists. For the full walkthrough, read our post Quick swap: let a late cancellation go without the fee, or the help article Let a client swap out of a late cancellation. > Decide the rule once, and every late message becomes a two-minute reply. #### Keep it consistent - Show the policy at booking, and again in the confirmation and reminder, so nobody can say they didn't know. Our post Salon Cancellation Policy Examples You Can Copy Today has wording to start from. - Keep your grace rule written down next to the policy, so anyone who answers messages for you applies it the same way. - Notice who cancels late. Once a year is life. Once a month is a pattern. For the few clients who cancel late again and again, a deposit is fairer than a stricter rule for everyone. The No-show shield in Bookatu asks for a deposit only from clients who are a real risk. Our guide How to Take Deposits for Appointments: A Practical Guide covers amounts and wording. #### Questions owners ask ##### Should I charge a late cancellation fee every time? Not necessarily. Treating everyone the same matters more. A written rule that charges by default, with a clear grace rule, is fairer than being strict one week and letting it slide the next. ##### Is it fair to charge a fee when a client is sick? Many owners waive it for genuine illness, because they would rather a sick client stayed at home. If you do, put it in your written rule so it applies to everyone. ##### How do I waive a cancellation fee without setting a precedent? Make the grace part of your written policy, for example one waived late cancellation per client per year, and say so in your reply. The client hears that this is the rule, not a favour. ##### Can a client cancel late without paying if someone else takes their time? With Quick swap turned on in Bookatu, yes. Once a waiting client takes their time, they are released with no late-cancellation fee. ##### What happens to the deposit if someone on the waitlist takes the slot? You choose. Refund it to their card or the credit they paid with, which is where it starts, or keep it as account credit. The client who takes the time pays their own deposit if one is due. #### Where to start Write down your rule: your window, when the fee applies, and your grace rule. Make sure your waitlist is easy to join, and turn on Quick swap if you want late cancellers to have a fair way out. Every Bookatu plan includes all the core booking features, and the pricing page shows what you would pay. ### Let clients book multiple services in one appointment How to let clients book multiple services in one appointment: back-to-back times, one deposit, sensible combinations and a single checkout at the point of sale. The Bookatu team · 2026-10-29 · Grow your business · https://bookatu.com/en-nz/blog/book-multiple-services-in-one-appointment · markdown: https://bookatu.com/blog/book-multiple-services-in-one-appointment.md > **The short version** > > - A combined visit should only offer times where every service fits, back to back. > - Each service can have its own person, so a colour with one stylist and a cut with another is still one booking. > - The client should get one confirmation, one reminder, one deposit and one checkout. > - Set rules so combinations you can't do are never offered in the first place. To let clients book multiple services in one appointment, your booking system has to do three things. It adds the services up and only offers start times where they all fit, one straight after another. It sends each service to the right person. And it treats the result as one visit: one confirmation, one deposit and one sale at the point of sale. Without that, clients book a colour and a cut separately and hope the times line up, or they ring you. This guide covers what a good combined booking looks like, the rules worth setting, and how to switch it on in Bookatu. #### Why one visit beats several separate bookings Two separate bookings look fine until the day. Then the problems show: - The times don't line up, so the client waits forty minutes between a colour and a cut. - Gaps open up in your day that nobody else can book. - Two confirmations and two reminders make the client wonder if they booked twice. - Two deposits feel like a lot to pay up front. - At the point of sale, someone has to put both bookings on one bill. One visit fixes all of this. The client books what they want, the way they would say it: a colour, then a cut. #### What a good multi-service booking needs Whatever system you use, this is the checklist worth holding it to: 1. **Back-to-back times only.** Every start time on offer is one where each service fits straight after the one before. 2. **A person for each service.** Each service can go to a different team member, or to whoever is free. 3. **One confirmation and one reminder.** Listing every service with its time. 4. **One fair deposit.** Enough to protect your time, not the price of the whole day. 5. **Rules for what goes together.** So nobody can book two services you would never do in one sitting. 6. **Extras that take real time.** An extra that takes fifteen minutes should make the booking fifteen minutes longer. 7. **One sale at checkout.** With each service credited to the person who did it. #### How back-to-back times are worked out First the services are put in order and their lengths added up. A 90-minute colour followed by a 45-minute cut is a visit of two hours and fifteen minutes. Then the system looks for start times where the person doing the colour is free for its 90 minutes, and the person doing the cut is free for the 45 minutes straight after. If either of them is busy, that start time isn't offered. So a combined visit can show fewer times than a single service. That is the point. Every time the client sees is one that really works, with no waiting around in between. #### Decide what can and can't be booked together Not every combination makes sense. A good system lets you say so once, instead of fixing odd bookings by hand. ##### Services that only go with certain others Some services only make sense next to particular others. A toner might only go with a colour, or a brow tint with a brow shape. Limiting these keeps the choices short. ##### Services that must never be booked together Some pairs can't happen in one sitting. A client wants 4 braids or 6 braids, not both. Mark these as never together, and they can't be booked as one visit. ##### Extras and add-ons, and when an extra should add time Extras are the small things added to a service, such as a scalp massage or a gloss. Some take no extra time. Others take ten or fifteen minutes and should make the booking longer, or your next client starts late. #### Deposits for a combined visit Deposits are where combined bookings often go wrong. If the system simply adds up every service's deposit, a client booking three services faces a large payment before they walk in, and may not book at all. A better rule puts a ceiling on it. In Bookatu there is one deposit for the visit: each service's deposit added up, but never more than the first service's price. If you use the No-show shield, it can still adjust the deposit for each client, as it does for a single booking. For deposit amounts in general, our guide How to Take Deposits for Appointments: A Practical Guide goes further. #### Moving, cancelling and checking out a visit To the client a visit is one thing, so they handle it as one. From their booking link they move or cancel the whole visit at once. A move keeps each person, and counts once against your Most times one booking can be moved online setting. If you have Client moves need approval too turned on, the client is asked to contact you to move a visit. Your team has more freedom. On the calendar each service is its own booking, marked Visit 1/2, Visit 2/2 and so on. Dragging or cancelling one there changes only that service. To take payment, tap Check out on any service in the visit. It becomes one sale, with a line for each service, credited to the person who did it. #### How to let clients book multiple services in Bookatu 1. **Turn it on.** Open Settings, then Several services in one visit. Turn on Clients can book several services in one visit and tap Save. It needs the Manage the business permission, which owners and admins have by default. 2. **Set your combination rules.** Open Catalog, then Services, and tap Edit on a service. Under Combination rules, choose In the same visit (Any other service, or Only the services I choose), tick anything it is Never with, and pick which extras go with it under Extras offered with it. Tap Save combination rules. 3. **Mark the extras that take time.** An extra is a service with Offer as an add-on switched on. On its own rules, turn on Adds its time to the booking if it makes the appointment longer. It is off by default. 4. **Try it as a client.** On your booking page, pick a first service. On the date and time step, tap Add another service. A visit takes up to 4 services. Only times where the whole visit fits are shown, and the review lists each service with its start time and price. Never with holds both ways round. A combination that isn't allowed is refused with the reason, for example 4 braids and 6 braids can't be booked together. Your team can always book a visit, whatever the setting. On New booking, or when you drag across a staff column on the Calendar, pick the first service and tap + Add another service. Each row has its own person or Any available. If the visit doesn't fit, the form names the service, the time and the person causing the problem. On the booking widget on your website, Book several services in one visit opens your full booking page in a new tab. Our help articles Book several services in one visit and Set which services can be booked together have every detail. > Clients don't think in services. They think in visits, so let them book one. #### When to keep services separate A combined visit is for one client having several services, one after another. A few things are better booked on their own: - A service that needs two or more people at once, such as two stylists on one client. In Bookatu it is always booked on its own, never as part of a visit. Our help article Book a service that needs two or more people explains how it works. - Classes and group sessions. They work differently, and have no combination rules. - Restaurant reservations, which are one booking for a party rather than a run of services. #### Questions owners ask ##### Can a client book a cut and colour with two different stylists in one visit? Yes. Each service in a visit can have the same person or a different one. On your team's New booking form, each row has its own person or Any available. ##### How many services can a client book in one appointment? In Bookatu, a visit is 2 to 4 different services for one client, back to back. That covers most real combinations, such as a colour, a toner, a cut and a blow-dry. ##### How is the deposit worked out when a client books several services? Each service's deposit is added up, but the total is never more than the first service's price. ##### Can I stop certain services being booked together? Yes. Each service has its own Combination rules. Choose Only the services I choose under In the same visit to limit what it goes with, or tick services under Never with to keep two apart. ##### Can a client move just one service of the visit? Not online. From their booking link the client moves or cancels the whole visit. Your team can change a single service on the calendar, by dragging or cancelling just that one. #### Where to start Check the combination rules on the services your clients most often pair. Then turn on Several services in one visit and book one yourself, the way a client would. Every Bookatu plan includes all the core booking features, and the pricing page shows what you would pay. ### Salon blog ideas: 30 topics worth writing about 30 salon blog ideas from client questions, the seasons and your own street, plus how to turn one into a finished post with the AI you already use. The Bookatu team · 2026-10-29 · Grow your business · https://bookatu.com/en-nz/blog/salon-blog-ideas · markdown: https://bookatu.com/blog/salon-blog-ideas.md > **The short version** > > - The best salon blog posts answer a question a client has asked you this month, with details only you know. > - Pick from the 30 ideas below, grouped by where they come from rather than by month. > - Write at a pace you can keep up. > - End every post with a clear way to book. Stuck for salon blog ideas? Start with the questions clients ask you at the chair. How long will this last? What do I do before I come in? Is this the right treatment for me? If one client asks, others are searching for the answer, and a local business that does the work is a good place to find it. Below are 30 ideas for hair salons, barbers, spas, nail and lash studios, clinics and studios that run classes. Change the wording to fit your services and add what only you know. #### Does a blog help a salon get found? It can, if the posts are useful. People often search for answers before they search for a business. Someone wondering how long a lash lift lasts may be days from booking one. A clear answer on your own site gives them a reason to land there, and to trust you before they book. There are no guarantees, and a blog is not the whole picture. When someone searches for a salon near them, your Google Business Profile and your reviews are usually what they see first. Our guide Get found on Google: local SEO for salons and studios covers those. A blog works alongside them, answering the questions people ask before they choose. #### Where good salon blog ideas come from You already have more ideas than you think. Keep a note on your phone for a month and add to it whenever one of these comes up: - Questions at the chair or in a consultation. If you have answered it twice, it is a post. - Aftercare you explain at the end of every appointment. - The notes clients leave when they book, like first time or getting married. - The calendar. Weddings, holidays and the change of season bring the same questions every year. - Things you fix, like a home colour gone wrong. They show what people try first. #### 10 ideas from the questions clients ask These are the easiest to write, because you already know the answers. - How long does it last? Say what is usual for colour, gel or a lash lift, and what makes it last longer. - How do I look after it at home? The aftercare you explain at every appointment, written down once. - How should I get ready for my appointment? Clean or unwashed hair, make-up or none, what to wear, when to arrive. - What happens at my first visit? Who greets them, the consultation, how long it takes and how paying works. - Why do you ask for a patch test? When you need one, how it works at your place and how far ahead to come in. - How often should I rebook? The usual gap between visits for each service. - Which one is right for me? Two services clients mix up, side by side. Balayage or highlights. A lash lift or extensions. - What is included in the price? The consultation, the toner, the finish, taking off an old set. - What should I bring? Reference photos, the products they use at home, glasses for a brow appointment. - What if I need to cancel or I am running late? Your policy explained kindly, with the reasons behind it. #### 6 ideas for occasions and seasons Seasons flip between hemispheres. Summer starts in December in Auckland and Sydney, and in June in London, Dublin and Toronto. Write for your clients' season, and publish a few weeks before it starts. - Weddings: when to book a trial, how far ahead to book the day, and how to book the bridal party. - School formals and proms: a timeline for the weeks before, and how to book a group. - Getting ready for the holidays: when the end-of-year rush starts at your place, and which times go first. - Summer hair and skin: what sun, salt water and pool water do to colour and condition, and what helps. - Winter: dry hair and hands, and the treatments clients book when it turns cold. - Back to work or back to school: quick, low-upkeep looks for a busy month. #### 4 local ideas Local posts are the ones nobody else can write. Use real details only. Never make up an event, a partner or a quote. - Getting here: parking, the nearest bus or train stop, which door to use, and whether there are stairs. - Your neighbourhood: where to get a coffee before an appointment, or lunch after. - Local events you take part in: a market stall, a charity day, a school fundraiser. - People you work with: a photographer, a florist, a wedding planner. Ask them first. #### 4 ideas that show your work - Meet the team: one post per person, with what they love doing. Ask what they are happy to share. - Behind a service: what actually happens during a balayage, a hot towel shave or a facial, step by step. - Before and after: a real result and how you got there, shared only with the client's clear permission. Photos on a client's profile in Bookatu are private to your team, so ask before any of them goes on your blog. - Products you use and why: what is on your shelf and what you look for in it. Say why you chose it, not what it cures. #### 6 ideas by type of business - Barbers: how to keep a fade sharp between cuts, or a beard guide for the first month of growing one. - Spas and massage: what to expect at a first massage, and how to choose between two treatments. - Nails: how to make a manicure last, and why it is worth coming in to have a set taken off. - Lash and brow: how to wash, sleep and swim in the first days after a lash lift or a new set. - Skin and beauty clinics: how to get ready for a treatment, and what to ask at a consultation. Leave anything medical to the consultation itself. - Studios and classes: what to bring to a first class, and how to choose the right level. #### How to turn an idea into a good post 1. **Put the question in the title.** Use the words a client would type, like How long does a lash lift last? A clever title is harder to find. 2. **Answer it early.** Give the short answer in the first few lines. The detail can come after. 3. **Add what only you know.** Your products, your process, your street. This is what makes the post yours. 4. **Give one clear next step.** End with a way to book the service the post is about. One invitation is enough. 5. **Read it as a client would.** Cut anything that sounds like an advert, check every fact, and make no medical claims or promises about results. #### Draft it faster with the AI you already use Once you have an idea, the blank page is the slow part. If you use ChatGPT, Claude, Gemini or another AI, the Bookatu blog editor sets it up for you. Open Blog, in the Grow part of your admin menu, and start a New post. Tap Use your own AI, give it a Title and a few words under What should it cover?, then tap Generate prompt and Copy prompt. Paste that into your AI, copy its whole reply, paste it under Paste the AI's answer and tap Fill the post. Bookatu fills in the title, excerpt, body, search title, search description and tags. The prompt carries only your business name, type, city and website language, never anything about your clients. Nothing is saved until you press Save draft or Publish, and it uses no Bookatu AI credits. For the prompt itself and how to edit what comes back, read the companion post How to write a salon blog post with ChatGPT or Claude. The help article Write blog posts with your own AI covers the feature step by step. Pick one idea from the list, the one a client asked about most recently, and write it this week. #### Questions owners ask ##### How often should a salon post on its blog? As often as you can keep up. A steady pace beats a burst of posts followed by months of nothing. One good post a month is a reasonable place to start, and the 30 ideas above will last you more than two years at that pace. ##### How long should a salon blog post be? Long enough to answer the question properly, and no longer. An aftercare post can be short. A wedding guide may need more room. The prompt Bookatu builds asks the AI for 600 to 1,200 words unless your brief says otherwise. ##### Can I use ChatGPT to write my salon blog? Yes, as a first draft. Check every fact, change anything that does not sound like you, and add your own details before you publish. The companion post How to write a salon blog post with ChatGPT or Claude walks through it. ##### Will my blog posts show up on Google? Nobody can promise that. In Bookatu, every published post has its own page, with the search title and description you set under Search & sharing and the article details search engines read. While your booking page is not live yet, its posts tell search engines not to list them. ### How to write a salon blog post with ChatGPT or Claude How to write a salon blog post with ChatGPT, Claude or Gemini: the prompt to use, what to check before you publish, and how to keep it sounding like you. The Bookatu team · 2026-10-29 · Grow your business · https://bookatu.com/en-nz/blog/write-a-salon-blog-post-with-chatgpt · markdown: https://bookatu.com/blog/write-a-salon-blog-post-with-chatgpt.md > **The short version** > > - Tell the AI who the post is for, who you are and where, the tone, what it must not make up, and the shape you want back. > - Edit the draft the way a client would read it. Check every fact and add what only you know. > - Write the search title and description for a person scanning a page of results. > - In Bookatu, Use your own AI builds that prompt for you and fills in the post when you paste the answer back. You can write a salon blog post with ChatGPT, Claude or Gemini, and the first draft is often decent. It is only as good as what you tell it, though. Ask for a blog post about balayage and you get something that could come from any salon, anywhere. Give it your business, your reader and your rules, and you get something you can work with. If you are still deciding what to write about, start with Salon blog ideas: 30 topics worth writing about. #### What AI is good at, and what only you know AI is good at shape. It can turn a rough idea into a post with a clear opening, sensible headings and a tidy ending in seconds, and suggest five titles when you are stuck on one. What it does not know is your business: your prices, your products, your opening hours, your team, or that the car park behind you closes early. When an AI does not know something, it often fills the gap with something that sounds right. That is how a post ends up offering a free consultation you have never offered. So split the work. Let the AI do the shape. You bring the facts. #### Build a prompt that gets a usable draft A good prompt answers five questions before the AI has to guess. ##### Who the post is for Say who will read it: your clients, and people nearby thinking of booking with you. A post for a nervous first-timer reads differently from one for a regular who wants the detail, so say which one you mean. ##### Your business, type, city and language Give the business name, what kind of business it is, the city and your website's language. That is enough for the AI to write for the right place, with the right spelling. Leave out anything private. ##### Tone and length Describe the voice in a few words, such as plain, warm and practical, and say how long you want it. Somewhere between 600 and 1,200 words suits most how-to posts. ##### What it must not invent This is the line that saves you the most editing. Tell it not to make up prices, offers, opening hours, staff names or anything else about your business, and to write in general terms where a fact is needed. Tell it to make no medical or legal claims, either. ##### The shape of the answer Ask for every part you need, by name: a title, a one or two sentence excerpt, the body with headings, a search title, a search description and a few tags. Then nothing gets forgotten, and you can paste each part where it goes. #### A blog post prompt to copy into ChatGPT or Claude Fill in the brackets and paste it into any AI. Keep the brackets to public details about your business. ```text Write a blog post for my business's website. About my business: - Name: [business name] - Type: [hair salon, barber, spa, nail studio...] - City: [city] - Language: [for example, English with UK spelling] Readers: my clients, and people nearby thinking of booking with me. Topic: [the question the post answers] Points to cover: [two or three points] Rules: - Plain, warm, practical tone. Short sentences. - 600 to 1,200 words, with ## headings. - Answer the question in the first paragraph. - Do not make up prices, offers, opening hours, staff names or other facts about my business. Where a fact is needed, write in general terms. - No medical or legal claims. - No client names or personal details. - End with one sentence inviting readers to book. Reply with: 1. Title 2. Excerpt (one or two sentences) 3. Body 4. Search title (about 60 characters) 5. Search description (about 160 characters) 6. Five short lowercase tags ``` If the draft misses, don't start again. Tell the AI what to change: shorter, less formal, more about aftercare. #### Edit the draft like a client would read it Read the draft through once as a client deciding whether to book. Then fix it. - Check every fact: times, prices, products, how long a result lasts. If it is not true at your place, take it out. - Cut the filler. AI drafts often open by saying how important the topic is, and close by saying it again. Delete both. - Cut the repeats. If two sections say the same thing, keep the better one. - Add one real detail to each section, like the product you use or the question a client asked. - Keep one clear next step, such as booking the service the post is about. - Take out anything that reads like medical or legal advice, and any client's name or story. Last, read it out loud. If a sentence is hard to say, it is hard to read. #### Search title, description and tags These are what a person sees before they click, so write them for someone scanning results. - Search title: about 60 characters, so it shows in full. Lead with the words someone would search, like the service and your city. - Search description: about 160 characters. One or two plain sentences on what the post answers, and why your business is worth a look. - Tags: a few short, lowercase topics that group your posts. In Bookatu these sit under Search & sharing in the post editor, with counters for about 60 and 160 characters. Leave the search title and description blank and Bookatu uses the post's title, with your business name, and its excerpt instead. #### Skip the copy-paste in Bookatu: Use your own AI If your blog is on Bookatu, the editor builds that prompt for you, and fills in the post when you paste the answer back. 1. **Open the editor.** Open Blog, in the Grow part of your admin menu, and tap New post, or open a post you are working on. Owners and admins see Blog in the menu. 2. **Describe the post.** Tap Use your own AI. Type a Title, from 2 to 140 characters, and a few words under What should it cover? 3. **Copy the prompt.** Tap Generate prompt, then Copy prompt. Paste it into ChatGPT, Claude, Gemini or any other AI. 4. **Paste the reply back.** Copy the AI's whole reply, paste it under Paste the AI's answer and tap Fill the post. A bit of chat around the answer is fine. 5. **Check what came in.** The title, excerpt, body, search title, search description and tags are filled in. If the post already has different words, you are asked Replace what is there? first. 6. **Save or publish.** Filling never saves. Tap Save draft to come back to it, or Publish to put it live. On a post that is already live, Save changes publishes your edits straight away. Like the one above, the prompt tells the AI not to make up facts about your business and to make no medical or legal claims. It carries only your business name, type, city and website language, never anything about your clients. If the reply cannot be read, nothing changes and you are told what to fix. The excerpt stops at 300 characters, the search title at 70 and the search description at 200, with up to 6 lowercase tags, and raw HTML is removed. None of it uses Bookatu AI credits, because Bookatu is not running the AI. You are. The help article Write blog posts with your own AI has every step, and our post Write your blog with the AI you already use introduces the feature. #### Or run your blog from your AI app with MCP If you work in an AI app that connects to other tools, such as Claude Desktop, you can skip the editor for drafting. Bookatu has an MCP server, a standard way for AI apps to connect to the software you use. Owners and admins make a key in API & monitoring, in the Settings part of the admin menu. Tick See posts, forms and email drafts and Write posts, forms and email drafts, tap Create key, then tap Copy config and paste it into your AI app. Then ask in plain words. Your AI can list your posts, open one, write a new one, update it, publish it or take it off your blog. - A new post stays a draft unless your AI is asked to publish it. - It can never delete a post. That stays with you, in the admin. - Editing a post never changes its web address, so links you have shared keep working. - It cannot set the search title, search description or tags. Set those in the editor, under Search & sharing. Our help article Manage your blog from an AI tool has the details, and Developer API and AI agents (MCP) covers keys in general. To try it the simple way, open Blog, tap New post, then tap Use your own AI. #### Questions owners ask ##### Which AI is best for writing blog posts: ChatGPT, Claude or Gemini? Any of them can write a good first draft, so use the one you already know. The prompt above works the same in each, and so does the one Bookatu builds. ##### Is it safe to paste client information into ChatGPT? Don't paste it. A blog post never needs a client's name, notes or booking history. The prompt Bookatu builds carries only your business name, type, city and website language. ##### Will search engines mind that AI helped write the post? What matters is that the post is accurate and useful to a local reader. A post you have checked, corrected and filled with your own details is worth publishing, whoever wrote the first draft. A generic one is not. ##### Does using my own AI use Bookatu AI credits? No. Bookatu is not running the AI, so Use your own AI uses no Bookatu AI credits. ##### Can my AI publish posts on its own? Only with write access: a key with Write posts, forms and email drafts ticked, or an app you approved with Read and write. Even then, a new post is saved as a draft unless your AI is asked to publish it, and it can never delete a post. You can revoke the key, or disconnect the app, on API & monitoring at any time. ### Cyber security checklist for salons, spas and clinics A plain cyber security checklist for salons, spas and clinics: own logins, two-step, passkeys, shared screens, old keys and staff who have left. The Bookatu team · 2026-10-29 · Product · https://bookatu.com/en-nz/blog/cyber-security-checklist-for-salons · markdown: https://bookatu.com/blog/cyber-security-checklist-for-salons.md > **The short version** > > - Most risk is everyday: a screen left signed in, a shared password, a leaver who can still sign in, a forgotten key. > - Give everyone their own login, and turn on two-step login for the whole team. > - Make shared computers sign out on their own, and remove people properly on the day they leave. > - Once a month, look at who and what has access. In Bookatu, the Security page works it out for you. A cyber security checklist for a salon, spa or clinic does not need to be long. What protects your client records and your takings is simple: one login per person, a second step at sign-in, screens that do not stay open, and a clean exit when someone leaves. Below are nine checks for any booking system, then how the Bookatu Security page works most of them out from your own data. #### Where the real risk is in a small business Forget the hacker in a dark room. For a small appointment business, the risk is usually ordinary: - The front desk computer that stays signed in all day. - One password shared by the whole team, still known by people who have left. - Someone who has left and can still sign in from their phone. - An app connected once, with a key that still works. - A password reused from another site, so a leak elsewhere opens your door too. None of these needs a clever attacker, only someone forgetting. At stake are your clients' contact details, history and notes, and often the money too. Each gap has a plain fix. #### The salon cyber security checklist 1. **Everyone has their own login.** So you know who did what. 2. **Two-step login for the whole team.** A stolen password is not enough on its own. 3. **Owners and admins use a passkey or two-step.** They can change settings and money. 4. **Shared computers sign out on their own.** A screen left open does not stay open. 5. **Each role sees only what it needs.** Fewer people can see the sensitive parts. 6. **People who leave are removed properly.** Nothing of theirs keeps working. 7. **Keys and connected apps are still needed.** And only read where reading will do. 8. **Everyone with a login still uses it.** A login nobody uses is a door nobody watches. 9. **The basics beyond your booking system.** Locked screens, updates, safe email and guest Wi-Fi. ##### 1. Everyone has their own login A shared login hides who cancelled a booking or gave a refund, and when one person leaves, everyone's password has to change. Give each person their own, trainees included. Check your logins against your team. In Bookatu they are under Who can sign in, on Team, and our help article Adding your team shows how to add someone. ##### 2. Two-step login for the whole team Two-step login asks for a short code from an app on your phone after the password, so a guessed or leaked password is not enough on its own. In Bookatu the owner can turn on Require two-step login for everyone, on Two-step login for your team, linked from Privacy & security and from the Security page. The help article Securing your account: two-factor and team logins covers setting it up. ##### 3. Owners and admins use a passkey or two-step An owner or admin can change settings, the team and money, so protect these logins first. A passkey is the easiest way: Face ID, Touch ID, Windows Hello, a phone or a security key instead of a password. In Bookatu it counts as two-step login, and the help article Sign in with a passkey shows how to add one. ##### 4. Shared computers sign out on their own The reception computer is the one most often left signed in. The fix is a time limit, after which the booking system signs the person out. In Bookatu that is Auto sign-out after inactivity, on the Security page: 15 minutes, 30 minutes, 1 hour or 2 hours. Our guide Front desk computer security for salons and clinics covers the shared desk in depth. ##### 5. Each role sees only what it needs A trainee may not need client contact details, and not every stylist needs your revenue reports. When each role has only what it needs, fewer people can see or change the sensitive parts. In Bookatu the owner sets this on Role permissions, from the Team page. Our guide Salon staff permissions: what each role should see covers choosing them. ##### 6. People who leave are removed properly Someone who leaves may have made an API key, connected an app or synced a calendar. Remove their access on the day, and close all of it. In Bookatu, Remove and sign out, on their row under Who can sign in, does it in one go, while the plain Remove button leaves their keys and apps working. Our Staff offboarding checklist for salons and studios covers the whole process. ##### 7. API keys and connected apps are still needed, and only read where reading will do Every API key and connected app is a door into your business, even one made for a trial nobody finished. Revoke anything idle, and give apps that only need to look a key that can only read. In Bookatu these live on API & monitoring. The help article Developer API and AI agents (MCP) explains them, and AI agents and your booking data: what a key lets in, and what it never touches goes further. ##### 8. Everyone with a login still uses it A login nobody has used for months usually belongs to someone who has left, and if it were misused, nobody would notice. Remove anyone who no longer needs access. In Bookatu, every sign-in is listed in the Audit log. ##### 9. Beyond the booking system These habits cost nothing: - Lock computers, tablets and phones with a PIN or fingerprint, and let screens lock themselves. - Install updates for the operating system and the browser when they are offered. - Turn on two-step login for your business email, which can usually reset every other password. - Be wary of links in messages you did not expect. If in doubt, open the site yourself. - Give clients a guest Wi-Fi network, separate from the one your computers and point of sale use. - Use a password manager, so every password can be long and different. > Most security is remembering. A checklist remembers for you. #### Run the checklist on the Bookatu Security page In Bookatu, open Security, in the Settings part of your admin menu. The Security checklist shows a score, such as 5 of 7 checks passed. Each check is worked out from your own team, keys and settings, says in one sentence what it found, and has a button to the page that fixes it. It covers most of the list above: two-step login, passkeys for owners and admins, API keys unused for 90 days, keys and apps that can change things, anything left behind by people who have left, and auto sign-out. From late January 2027 it also flags anyone who has not signed in for 90 days. A check that does not apply to you, such as API keys when you have none, is left out rather than failed. Where a fix is the owner's alone, an admin is told who can make it. Below, Everything in one place links to every other security setting. The help article Check your security on the Security page has the details, and our post Passkeys, auto sign-out and a Security page for teams gives the tour. #### A short monthly routine A few minutes once a month is plenty for most small teams. 1. **Open Security.** Check the score, and read anything with a warning sign. 2. **Fix the first warning.** Tap its button and do it now. 3. **Review keys and apps.** On API & monitoring, revoke anything nobody recognises or uses. 4. **Check the team list.** Make sure everyone under Who can sign in still works with you, in the right role. Start today: open Security, fix the first warning, and add a passkey for yourself. It takes a few seconds. #### Where client data rights live Data rights are what your clients can ask for: a copy of their data, or for it to be deleted. In Bookatu clients can do both from their own account. The help articles Privacy requests and data deletion and Exporting your data cover your side, and GDPR without the panic: what Bookatu handles for your salon explains how a deletion runs. This checklist is practical advice, not legal advice. #### Questions owners ask ##### What is two-step login, and should my staff use it? It asks for a second thing after your password, usually a short code from an app on your phone. Yes, everyone should use it. In Bookatu the owner can require it for the whole team, and a passkey counts as two-step login. ##### Is a passkey safer than a password? For most people, yes. There is nothing to remember and nothing anyone can phish, because it needs your fingerprint, face or PIN on the device that holds it. ##### How often should I check who has access to my booking system? Once a month is a sensible habit, and straight away when someone leaves or changes role. The Bookatu Security page flags API keys unused for 90 days. ##### What should I do when a staff member leaves? Remove their access and sign them out on the day they go, then change any shared password they knew. Our Staff offboarding checklist for salons and studios has the full list. ##### Who can see the Security page? Owners and admins. Some fixes, such as requiring two-step login for everyone, are the owner's alone, and admins are told so. ### Staff offboarding checklist for salons and studios A staff offboarding checklist for salons and studios: what to do when someone leaves, from logins, keys and calendar sync to their bookings and clients. The Bookatu team · 2026-10-29 · Product · https://bookatu.com/en-nz/blog/staff-offboarding-checklist · markdown: https://bookatu.com/blog/staff-offboarding-checklist.md > **The short version** > > - Before their last day, list everything they can get into, from the booking system to the alarm code. > - On the day they go, remove their access to the booking system first. > - Hand their upcoming bookings to someone else without cancelling them, and tell those clients yourself. > - Change any password or code they knew. > - A few days later, check that nothing they set up is still running. When someone hands in their notice, or leaves without warning, the access side is easy to get half right. Their login goes, but a shared password, a calendar sync or an old app key carries on. A staff offboarding checklist makes sure nothing is forgotten, whether you have two chairs or twenty. It works with any booking system, with Remove and sign out in Bookatu as the worked example. #### Before their last day If you have notice, use it. Make a list of everything they can get into. It is usually more than you think. - Their login to your booking system, and any shared login they use, such as one for the front desk. - Shared passwords: the business email, the Wi-Fi, supplier and wholesaler accounts, your website. - Email: their own address on your domain, or access to a shared inbox. - Your social media accounts, and any tools used to post to them. - Your Google Business Profile, if they were added as a manager. - Calendar syncs and apps they connected to your booking system. - Card machine and point of sale logins. - Door keys, alarm codes, a locker or a safe. Then plan their upcoming bookings: who will see each client, and how you will tell them. A client who has seen the same person for years deserves a kind word, not a surprise. If they rent a booth or chair from you, set the day their rent stops. In Bookatu, untick that they rent a booth or chair and pick the day under Stops renting from, in the Pay section of their card on Team. The help article Set up a booth or chair renter shows where. #### Staff offboarding checklist: the day they leave Do it in this order. The booking system comes first, because it holds your client list. 1. **The booking system.** Remove their login and sign them out. Close anything they set up, such as keys, apps and calendar syncs. 2. **Shared passwords.** Change every password they knew, starting with the business email, because email can reset almost everything else. 3. **Social media and Google.** Remove them as an admin or manager of your social accounts and your Google Business Profile. 4. **Email.** Close their address, or forward it to someone who will answer clients. Take them out of any shared inbox. 5. **The point of sale and card machine.** Remove their login, or change the shared code. 6. **Keys and codes.** Collect their keys and change the alarm code. If a key is missing, think about the locks. If they leave suddenly, do the first step straight away, from your phone if you have to. The rest can follow later that day. #### Their upcoming bookings and clients Do not cancel their bookings. A cancelled booking is a client who may not come back. Move each one to someone who can do the service, or leave it unassigned and reassign it on the calendar. In Bookatu each booking keeps its time, and nothing is cancelled. Take them off your booking page too, so no new client books someone who has gone, but keep their history for whoever sees the client next. Then tell the clients. Moving a booking to someone else at the same time sends the client no message in Bookatu, so a short personal note from you is the way to do it. Say who they will see instead, that the time has not changed, and that they can choose someone else if they would rather. > **A message you can adapt** > > Hi Sam, just so you know, Jo has moved on from the salon. Your appointment on Friday at 2pm is still booked, now with Alex. If you would rather see someone else, reply and we will sort it. Staying in touch is how your business keeps those relationships. The post Your clients are yours: why your salon should own its client relationships goes further. #### How Remove and sign out works in Bookatu In Bookatu, Remove and sign out does the booking system part in one go. Open Settings, then Team, and scroll to Who can sign in. Tap Remove and sign out on their row. 1. **Read the summary.** Before anything changes, you see their upcoming bookings, the keys and apps they made, and their calendar connections. 2. **Choose what happens to their bookings.** Move them to a team member who can be booked, or leave them unassigned for you to reassign on the calendar. If the person you choose already has a booking at one of those times, that one is left unassigned instead. 3. **Take them off the booking page.** Leave Take them off the booking page too ticked, so clients can no longer book them. Their card moves to Removed with its history, and can be restored. 4. **Confirm.** Tap Remove and sign out with their name. They are signed out of this business on their next click, on the web and in the phone app. 5. **Read the Done screen.** It lists what was moved, revoked and turned off, and anything left to sort out, such as classes they teach. When you confirm, API keys they made stop working, apps they approved are disconnected, their Google Calendar is disconnected from this business and their calendar link is turned off. Other businesses they belong to are not affected, and the removal is recorded in your Audit log. The owner, and admins who can manage the team, see the button on other people's rows, never on their own, and an admin never sees it on an owner's. Handing bookings over also needs someone who can edit the calendar. The help article Remove someone from your team and sign them out has every detail, and Moving or reassigning a booking covers the calendar side. > **Good to know** > > The plain Remove button beside it only removes the login. Their keys and apps keep working, and the Security page shows Nothing left behind by people who have left until you revoke them on API & monitoring. When someone leaves, Remove and sign out is the one to use. #### After they have gone A few days later, check that nothing slipped through. - Open the Security page. If anything they made is still live, Nothing left behind by people who have left appears, with a button to review it. - If anything worries you, look through their last few weeks in the Audit log, which lists downloads, client changes and settings saves with who made them. - Check that every service they did is still given to someone who can be booked. The post Choose who does each service, and give each person their own hours explains how. - If they were an admin, check who else has that role, and whether your Role permissions, from the Team page, still suit the team you have now. - If they had your whole-business calendar link on their phone, open Calendar sync and tap Get a new link under Whole business. The post See your bookings in Google Calendar, Outlook or Apple Calendar explains the links. - Change any shared login you could not get to on the day, such as a supplier account. If someone has left in the past year, it is worth a look today. Open Security in Bookatu and see whether anything was left behind. #### The people side, briefly A short exit conversation helps: what is in progress, which clients need a handover, and anything they know that you do not, such as a regular's preferences or a supplier contact. Ask them to add handover notes to each client's record before they go, where the next person will see them. Final pay, holiday pay, notice and paperwork follow your country's employment rules, which differ from place to place. Check with your accountant or your local employment authority. This post covers access only, and is not legal advice. #### Questions owners ask ##### What happens to a stylist's bookings when they leave? That is your choice. With Remove and sign out in Bookatu, you move them to another team member, or leave them unassigned to reassign on the calendar. Nothing is cancelled. ##### Can a former employee still see my client list? Not once you have removed them with Remove and sign out. They are signed out of your business on their next click, on the web and in the phone app. Anything they downloaded or wrote down before they left is another matter, which is one reason to give each role only what it needs. ##### Does removing someone affect other businesses they work at? No. It applies to your business only. If they also work at another business on Bookatu, they stay signed in there. ##### Can I undo it if I remove the wrong person? Mostly. Their booking page card moves to Removed with its history, and you can restore it. To let them sign in again, give them a login from Team, under Give someone a login. Revoked keys and apps stay revoked, and moved bookings stay where you put them. ##### Do I need to change shared passwords when someone leaves? Yes, for anything they knew. The more of your business that uses one login per person, the less there is to change, because you remove one person instead of changing a password for everyone. ### Front desk computer security for salons and clinics Front desk computer security, step by step: a login for each person, auto sign-out after inactivity, passkeys for quick sign-in and a screen out of view. The Bookatu team · 2026-10-29 · Product · https://bookatu.com/en-nz/blog/front-desk-computer-security · markdown: https://bookatu.com/blog/front-desk-computer-security.md > **The short version** > > - Give everyone their own sign-in, and make it quick with a passkey. > - Have the booking system sign people out after a few minutes with nothing happening. > - Lock the screen whenever you step away. > - Angle the screen away from the waiting area and the counter. > - In Bookatu, turn on Auto sign-out after inactivity on the Security page, and have each person add a passkey. A shared front desk computer is the busiest screen in a salon, spa or clinic, and the one most likely to be left signed in. Good front desk computer security is simple: one sign-in per person, made fast with passkeys, an automatic sign-out after a few idle minutes, and a few habits at the desk. None of it has to slow the desk down. Here is the setup for any booking system, then the settings in Bookatu. #### Why the front desk is the weak spot Think about a normal day at reception. Someone signs in first thing, and the screen stays open through the morning rush, lunch and the afternoon. Several people use it, often on one login. Clients stand at the counter while you take payment, and the waiting area may have a clear view. On that screen sit client names, phone numbers and notes, today's appointments, and often the takings. Nobody has to break in. They only have to walk past at the wrong moment, or sit down while the desk is empty. The fixes below close those gaps one at a time. #### Give everyone their own sign-in One shared login for the front desk feels quicker. It costs you more than it saves. - You lose the record of who did what. A refund, a deleted booking or a changed price could have been anyone. - You cannot remove one person. When someone leaves, you change the password and tell everyone else the new one. - Everyone gets the same access, so a trainee covering the desk sees whatever the shared login sees. Give each person their own login, and let their role decide what they can see. In Bookatu you add people from Team, as the help article Adding your team explains, and the owner decides what each role can do on Role permissions. Our guide Salon staff permissions: what each role should see goes into choosing them. #### Make signing in quick with passkeys The usual reason for a shared login is speed. Nobody wants to type a long password between clients. Passkeys fix that. A passkey signs you in with Face ID, Touch ID, Windows Hello, your phone or a security key, instead of a password. There is nothing to remember and nothing anyone can phish. It belongs to the person, not the business. In Bookatu, every team member can add their own. Owners and admins do it on Privacy & security, in the Passkeys card. Everyone else taps Two-step login at the top of the admin and finds Your passkeys. Adding one first asks you to prove it is you, with your password, a two-step code or a recent Google sign-in. Each person can have up to 20, so every device can have its own. Next time, tap Sign in with a passkey on the sign-in page, or pick it when the browser offers it in the email field. Signing in with a passkey counts as two-step login, even where the owner requires two-step login for everyone. Because it belongs to the person, it signs them in to every business they work with on Bookatu. The help article Sign in with a passkey has each step. > **On a shared computer** > > A passkey saved on the shared computer itself is protected by that computer's PIN or fingerprint. If the whole team unlocks the computer the same way, anyone at the desk could use it. On a shared machine, a passkey on each person's own phone, or a security key on their keyring, is the natural choice, because it leaves with them. Most up-to-date browsers can use a passkey from your phone, usually by showing a code to scan. #### Sign people out automatically Even with separate logins, someone will forget to sign out. An automatic sign-out after inactivity catches that. After a set time with nothing happening, the booking system signs the person out, so a screen left open does not stay open. In Bookatu this is Auto sign-out after inactivity, on the Security page. Under Sign people out after, choose 15 minutes, 30 minutes, 1 hour or 2 hours without activity, then tap Save. It is off until an owner or admin turns it on, and the help article Sign people out automatically after inactivity covers it step by step. - A minute before the time runs out, the person sees Still there? with a countdown. Stay signed in keeps them in, and Sign out now signs them out straight away. - Only real activity counts: a click, a key press, a tap, scrolling or moving the mouse. A page refreshing itself in the background does not. - Activity in any tab of the same browser keeps the person signed in. - Someone signed out this way sees a note on the sign-in page saying why. - It applies to your business on the web. The phone app stays signed in, and another business the person works at is not affected. - Turning it on signs nobody out straight away, because everyone's clock starts from that moment. The change is recorded in the Audit log. #### Choosing the timeout There is no single right number. It is a trade-off between convenience and how long a screen can sit open with nobody there. - On a desk used every few minutes, a short time rarely gets in the way, because the activity keeps people signed in. It still signs the screen out soon after the desk goes quiet. - On a desk that is busy in bursts, a longer time means fewer sign-ins after each quiet spell, and a screen left open for longer when nobody is there. - A computer in a back office that clients never enter is less exposed than one on the counter. - The setting covers everyone in your business on the web, so choose the time that suits your most exposed screen, usually the one at the front. If you are unsure, start shorter and see how the team gets on. With passkeys, signing back in takes seconds, so a short time costs less than it used to. #### Habits beyond the booking system The booking system is one layer. These habits protect the computer itself. - Lock the screen when you step away. On Windows, press the Windows key and L. On a Mac, press Control, Command and Q. - Set the computer to lock itself after a few minutes, as a backstop. - Give each person their own account on the computer, or use the browser's guest mode, so nobody's sign-ins or history are left for the next person. - Do not let the browser save passwords on a shared computer. - Install updates for the operating system and the browser when they are offered. - Angle the screen so the waiting area and the counter cannot read it. A privacy filter helps where you cannot move it. - Keep the front desk computer on your own Wi-Fi, and give clients a separate guest network. > A screen at reception should be quick for your team and dull for everyone else. #### Set up front desk computer security in Bookatu 1. **Turn on auto sign-out.** Open Security, in the Settings part of your admin menu. Under Auto sign-out after inactivity, choose a time and tap Save. 2. **Add your own passkey.** Owners and admins: open Privacy & security and find Passkeys. Tap Add a passkey, give it a name, and confirm it is you. 3. **Ask each person to add theirs.** Everyone else taps Two-step login at the top of the admin and finds Your passkeys. Nobody can add a passkey for someone else. 4. **Check your score.** Back on Security, Auto sign-out after inactivity now passes. Work down anything else with a warning sign. Start with the first step today. It protects the desk even on the day someone forgets. For the rest of the business, the Cyber security checklist for salons, spas and clinics has the whole list, and our post Passkeys, auto sign-out and a Security page for teams tours the page. #### Questions owners ask ##### How long should auto sign-out be on a shared computer? It depends on how busy the desk is and who can see it. Bookatu offers 15 minutes, 30 minutes, 1 hour or 2 hours, with a warning a minute before. A screen in view of clients usually suits a shorter time. ##### Can staff share one login at the front desk? They can, but you lose the record of who did what, everyone gets the same access, and you cannot remove one person without changing the password for everyone. One login each, with passkeys to keep it quick, is better. ##### Does auto sign-out affect the phone app? No. It applies to your business on the web. The phone app stays signed in as it does today. ##### Does working in another tab keep me signed in? Yes. Activity in any tab in the same browser counts. A page refreshing itself in the background does not. ##### What is a passkey, and do my staff need one? A passkey signs you in with your fingerprint, face, PIN, your phone or a security key, instead of a password. Nobody has to have one, but it makes separate sign-ins quick, which makes one login each workable at a busy desk. Anyone on the team can add their own. ### Salon staff permissions: what each role should see Set salon staff permissions with care: what owners, managers, front desk and stylists should see and change, what stays locked, and when to review it. The Bookatu team · 2026-10-29 · updated 2026-10-30 · Product · https://bookatu.com/en-nz/blog/salon-staff-permissions · markdown: https://bookatu.com/blog/salon-staff-permissions.md > **The short version** > > - Give each person their own login, with the access their job needs and no more. > - Keep the money, the setup and the team with the owner or a trusted manager. > - In Bookatu, permissions are set for each role, not each person: Owner, Admin, Staff and Trainee. > - Look at it again whenever someone joins, changes job or leaves. Salon staff permissions decide who on your team can see and change what: the calendar, client messages, your takings, refunds, prices and settings. The simple rule is to start from each person's job and give them what it needs. A stylist needs their own appointments. A front desk needs the whole calendar. Very few people need your earnings report, or the power to change your prices. Below are a starting grid for a typical salon, the few things never to hand down, and how Role permissions works in Bookatu, including one limit: each switch applies to everyone with a role, not to one person. #### Start from the job, not the person It is tempting to give a trusted senior stylist everything. But the question isn't trust. It is what their job needs. Someone who never gives refunds doesn't need a refund button. Less access means fewer mistakes, and less to undo if a login is ever misused. This only works if everyone has their own login. With one shared login, everyone has the same access and you can't tell who did what. Separate logins let you match access to each job, and remove one person cleanly when they leave. Our help article Adding your team shows how to give someone a login. #### The four roles and what they are for When you give someone a login in Bookatu, you choose one of four roles: - Owner: full access, always. An owner keeps every permission, and no switch can take it away. - Admin: manager level. By default, admins have every permission except Manage billing. - Staff: view and operate. By default, staff see a read-only calendar of their own column and can fulfil orders. They don't see your takings or the client inbox, and can't permanently delete records. - Trainee: the checklist only. A trainee lands on the team checklist and sees nothing else. Our help article Add a trainee who only sees the checklist covers it. The defaults are a sensible start, and the owner can change them for Admin, Staff and Trainee. #### The decisions that matter These are the switches worth thinking through for each role. ##### Who can see the money See analytics & earnings shows revenue, reports and who is earning what. It is off for Staff by default. Turn it on and everyone with that role sees your takings. ##### Who sees everyone's calendar, and who only their own Without See everyone's calendar, a person sees only their own appointments. That suits most stylists and therapists. A front desk needs to see everyone, because they book for the whole team. ##### Who can book, move and cancel Edit the calendar lets someone book, reschedule, block time and cancel. Staff have a read-only calendar until you turn it on. A front-desk login usually needs it with See everyone's calendar. Our post Check clients in, edit bookings and block time off from your calendar shows how to set one up. ##### Who can give money back Refund orders lets someone issue refunds to clients and waive a surcharge on a booking. Adjust loyalty and gift cards lets them add or remove points by hand, void gift cards and resend a gift card's email. Reissuing a card also needs Manage the business. Staff can still redeem both. Both move money or credit. Staff don't have either by default. ##### Who can read client messages Client inbox lets someone read and reply to client messages. Those threads can hold personal details, so it is off for Staff by default. ##### Who can download client lists and delete records Export data lets someone download client lists and reports. Delete records lets them permanently delete services, products, forms and more. A downloaded list can leave the building, and a deleted record can't come back, so keep these with the fewest people. ##### Who can change prices, services and settings Manage the business covers your services, prices, settings and hours. Every change to your setup, from Settings and the team to packages, promo codes, products, forms and the blog, checks your own grid for the person's role. So a switch you turn off really is off. #### A starting grid of salon staff permissions These are suggestions, not rules. Adjust them to how your salon runs. - Front desk: the Staff role, with Edit the calendar and See everyone's calendar turned on. Add Client inbox if they answer messages. Leave See analytics & earnings, Refund orders, Export data and Delete records off. - Stylist or therapist: the Staff role. They see their own appointments. Turn on Edit the calendar only if you are happy for them to book and move appointments themselves. - Manager: the Admin role. By default an admin can change your setup, manage the team, give refunds and export data. Manage billing stays with the owner. - Junior or apprentice: the Trainee role, until they need the calendar. One thing to plan around: a switch applies to everyone with that role. If your front desk and your stylists are both Staff, turning on See everyone's calendar for the front desk shows it to your stylists too. For many salons that is fine. If it isn't, the choice is which role each job belongs in. #### What should never be handed down Some things stay with the owner whatever you do, and Bookatu holds the line for you: - The owner always keeps full access. No switch can take it away. - Manage team and Manage billing can never be given to Staff or Trainee. The server enforces this too, so a crafted request can't get around the locks. - Only the owner can change Role permissions. Anyone else who tries to save a change is told Only the owner can change permissions. Beyond the locks, give the Admin role only to people you would trust with the keys to the shop. And consider requiring two-step login for the whole team. The owner can do that from Two-step login for your team, linked below the Role permissions grid. #### How to set it up in Bookatu 1. **Give each person a login.** Open Team. Under Who can sign in, fill in Give someone a login, choose their role and press Add login. 2. **Open Role permissions.** On the Team page, the owner sees Role permissions beside Who can sign in. It opens a grid with every switch for every role. 3. **Turn on what each role needs.** Switch permissions on or off for Admin, Staff and Trainee. Locked cells can't be changed: the owner's column is always on, and Manage team and Manage billing stay off for Staff and Trainee. 4. **Save.** Tap Save changes. If you want to start again, Reset to defaults puts every switch back where it began, ready to save. As the page says, changes apply to everyone with that role. Each saved change is recorded in the Audit log as Permissions changed. > Give people the access their job needs, and nothing they would have to explain. #### Review it when people change Look at permissions again whenever: - Someone joins. Start them on the least access their job needs. A trainee can move to Staff later. - Someone is promoted. Change their role, rather than giving their whole current role more switches. - Someone leaves. On the Team page, tap Remove and sign out on their row. It removes their login, stops the API keys and apps they made, and disconnects their calendar sync in one step. Our help article Remove someone from your team and sign them out has the details. The Security page, in the Settings part of your admin menu, is worth a look now and then. It scores how well protected your business is and links each fix. Our help article Check your security on the Security page explains each check, and our post Passkeys, auto sign-out and a Security page for teams covers what it adds. #### Questions owners ask ##### Should front desk staff see sales and revenue? Usually not. Takings and reports sit behind See analytics & earnings, which is off for Staff by default. Turning it on shows them to everyone with the Staff role, so most salons keep it with the owner and a manager. ##### Can a stylist see only their own appointments? Yes, and that is the default. Staff see only their own column unless See everyone's calendar is turned on for the Staff role. ##### Who should be allowed to give refunds? Keep Refund orders with owners and managers. Admins have it by default and Staff don't. If a front-desk person often gives money back, consider the Admin role for them, rather than turning it on for every Staff login. ##### Can I give one team member more access than the others in the same role? No. Each switch applies to everyone with that role. To give one person more, change their role, for example from Staff to Admin, and check that role's switches suit them. ##### Can my manager change what each role is allowed to do? No. Only the owner can change Role permissions. A manager in the Admin role can manage the team by default, but not the grid itself. #### Where to start Open Team, then Role permissions, and read down the Staff column. For each switch, ask whether everyone with that role needs it for their job. Turn off what they don't, tap Save changes, and make sure everyone has a login of their own. Then you know exactly who can see what. ### Quick swap: let a late cancellation go without the fee Quick swap lets a client who must cancel late offer their time to your waitlist. If someone takes it, they pay no late fee and your chair stays full. The Bookatu team · 2026-10-28 · updated 2026-10-29 · Product · https://bookatu.com/en-nz/blog/quick-swap-late-cancellations-without-the-fee · markdown: https://bookatu.com/blog/quick-swap-late-cancellations-without-the-fee.md > **The short version** > > - A client inside your late-cancellation window can ask to swap out instead of cancelling. > - Their time is offered to matching clients on your waitlist, while they stay booked. > - The first to take it gets the same time with the same person. The client who asked pays no fee and keeps their deposit. > - If nobody takes it before offers stop, they stay booked, and can still cancel with the usual fee. > - Quick swap is off by default. Switch it on in Settings, under Quick swap. A late cancellation is awkward for everyone. A client messages on the morning of their appointment: a sick child, a shift they could not swap, a car that will not start. Your policy says the fee applies, and it is there for a good reason. But charging it can cost you a regular, and letting it go costs you the time and the money. Quick swap is a third way. The time goes to someone on your waitlist who wants it. Nobody pays a fee, and the chair stays full. #### What the client sees Clients open their booking from the Manage my booking button in their emails. With Quick swap on, and only when cancelling now would cost them a late-cancellation fee or their deposit, the page offers an Ask to swap out button. The cancel button beside it reads Cancel (fee applies), so the choice is plain. Underneath, a short note headed Can't make it? Swap out instead says what will happen. Their time is offered to people on the waitlist. They stay booked until one of them takes it. It says what becomes of their deposit, and by when offers stop. They confirm with Yes, offer my time. Until someone takes it, they can change their mind with Withdraw my request. #### What your waitlist sees Bookatu offers the time to matching clients on your Waitlist, up to five at a time, each with a one-tap link by email. Clients who have agreed to texts get it by text too, when texting is set up. Anyone who joins the list later is offered it as well, until offers stop. A waiting client is never offered the same time twice, and the client who asked is never offered their own time. The link opens a page headed A spot is up for grabs. The first person to tap Take this spot gets it. They are booked into the same time, with the same person, room and equipment. If the service takes a deposit, they pay their own on the next screen, as for any online booking. The time is never free for anyone else in between. The old booking lets go of it only at the moment the new one takes it. #### What the client who asked gets When someone takes the time, the client who asked is released. Their booking is cancelled with no late-cancellation fee, and they get an email to say so. Their deposit is never lost. You choose what happens to it, under Their deposit, when a swap goes through: - Refund it, to their card or to the credit they paid with. This is where it starts. - Keep it as account credit for their next booking. A refund that Stripe refuses stays on the booking for you to handle. If nobody takes the time before offers stop, the client stays booked and is told so. They can still cancel then, with your usual fee. #### What you see On the Calendar, a booking with an open ask is marked Swap asked. Open it and a Quick swap card shows where it stands: Swap out asked, with the time offers stop, then Swapped with a link to the new booking, or Withdrawn, or Closed. The new client's booking has its own Quick swap card, marked From the waitlist, linking back. When a swap goes through, you get an alert and an email. It names both clients and the new booking, and says what happened to the deposit. #### Switch it on Quick swap is off by default. Until you switch it on, late cancellations, fees and deposits work exactly as they do today. - Open Settings and choose Quick swap, under Essentials. - Turn on Let clients swap out of a late cancellation. - Set Stop offers before the start, in hours, from 1 to 336. It starts at 2, because a waiting client needs time to get to you. - Choose what happens to the deposit. - Tap Save Quick swap. Offers stay open after your normal online changes close, right up to that cutoff. Changing these settings needs the Manage the business permission, which owners and admins have from the start. > **Good to know** > > Quick swap isn't offered while you approve online bookings first, under Booking approval. It is also not offered for classes, group bookings, bookings away from your premises or with travel, or a booking still waiting for a deposit or your answer. A visit of several services swaps as a whole, to a waiting client who wants all of it. > The fee was never the point. A full chair was. #### Two things worth checking - Your Free cancellation window and Keep the deposit on a late cancellation, under Deposits & cancellations. Together with any late-cancellation fee, they decide when cancelling counts as late, and so when a client is offered the swap. - Your Waitlist. Quick swap can only pass a time to someone who is waiting for it, so it works best when clients have a list to join. Every step is in the help article Let a client swap out of a late cancellation. For when to charge a late fee, when to waive it and what to say, read our guide How to handle late cancellations without losing clients. ### Passkeys, auto sign-out and a Security page for teams A new Security page scores your business and links each fix. Add passkeys for the whole team, auto sign-out for shared computers and one-step offboarding. The Bookatu team · 2026-10-28 · updated 2026-10-29 · Product · https://bookatu.com/en-nz/blog/passkeys-and-a-security-page-for-your-team · markdown: https://bookatu.com/blog/passkeys-and-a-security-page-for-your-team.md > **The short version** > > - Security, in the Settings part of your admin menu, shows a checklist worked out from your own team, keys and settings, with a fix beside each check. > - Auto sign-out signs people out of your business after 15 minutes, 30 minutes, 1 hour or 2 hours with no activity. > - Everyone on your team can add a passkey and sign in with Face ID, Touch ID, Windows Hello, a phone or a security key. It counts as two-step login. > - Remove and sign out takes someone off your team in one go: their login, their keys and apps, their calendar sync, and a choice for their upcoming bookings. Security in a salon is rarely about hackers. It is the front-desk computer left signed in over lunch. A stylist who left in spring and still has a login. An API key made for an app nobody uses any more. Small things, and easy to forget. The new Security page puts them in one place. #### A checklist made from your own business Open Security from the Settings part of your admin menu. At the top is the Security checklist, with a score such as 4 of 6 checks passed and a bar that fills as you go. Every check is worked out from your own team, keys and settings, not a generic list. Each one says in a sentence what your data shows, with a button to the page that fixes it. The checks include: - Two-step login required for the team, and whether everyone on the team actually uses it. - Owners and admins use two-step login, and each has a passkey or two-step login, since they can change settings, the team and money. - No API keys sitting unused for 90 days, and no keys or connected apps that can change things where reading would do. - Nothing left behind by people who have left: keys and apps made by someone no longer on your team. - Auto sign-out after inactivity. A check that does not apply to you is left out, rather than shown as failing. With no API keys, you are not marked down for them. Some fixes only the owner can make, such as requiring two-step login for everyone. An admin is told who can, instead of getting a link that goes nowhere. Below the checklist, Everything in one place links to each security setting where it already lives: two-step login, passkeys, Role permissions, the Audit log, API keys and connected apps, and your data. The Security page is open to owners and admins. #### Auto sign-out for the front-desk computer A shared computer at reception is the easiest way in. Someone signs in first thing, and by the afternoon anyone walking past could open your client list. Auto sign-out closes that gap. On the Security page, under Auto sign-out after inactivity, set Sign people out after to 15 minutes, 30 minutes, 1 hour or 2 hours without activity, then tap Save. It is off until you choose. - A minute before, people see a warning and can stay signed in with one tap. - It applies to everyone on your team in this business, wherever they are signed in on the web. - Turning it on signs nobody out straight away. - The phone app is not affected. It stays signed in as it does today. Only real activity counts: a click, a key press or a scroll. A page refreshing itself in the background does not keep someone signed in. Anyone signed out this way sees a note on the sign-in page saying why. #### Sign in with a passkey A passkey lets you sign in with Face ID, Touch ID, Windows Hello, your phone or a security key, instead of typing a password. There is nothing to remember and nothing anyone can phish. Owners and admins add one from Privacy & security, under Passkeys. Everyone else on the team taps Two-step login at the top of the admin and finds Your passkeys. Tap Add a passkey and give it a name, so you can tell your devices apart. Confirm it is you with your password or a two-step code, then let your device check your fingerprint, face or PIN. If you sign in with Google, there is no password to check, so you may be asked to sign out and in again first. Next time, tap Sign in with a passkey on the sign-in page. Where your browser supports it, your passkey is also offered as you start typing your email. Signing in with a passkey counts as two-step login, so it meets the rule even when you require two-step login for the whole team. Your password, Google sign-in and two-step login keep working as they do now. A passkey belongs to you, not to the business, so it signs you in to every business you work with on Bookatu. Rename or remove one at any time, for example when a phone is lost. #### Remove someone who has left, in one step When someone leaves, their login is only part of it. There may be API keys they made, apps they connected, a Google Calendar synced to your bookings, and appointments still under their name. Go to Team and, under Who can sign in, tap Remove and sign out on their row. Before anything changes, Bookatu shows what will happen: - Their login here is removed, so they are signed out of this business on their next click, on the web and in the phone app. - API keys they made stop working, and apps they approved are disconnected. - Their Google Calendar is disconnected from this business, and their calendar link is turned off. If they have upcoming bookings, you choose what happens to them: move them to someone else who can be booked, or leave them unassigned to reassign on the calendar. Each keeps its time, and nothing is cancelled. If the person you choose is already booked at one of those times, that booking is left unassigned instead. You can take them off the booking page too. Their card moves to Removed with its history, and can be restored. When it is done, a summary lists what was moved, revoked and turned off, and anything still waiting for you, such as a class that needs a new instructor. It is for this business only: other businesses they belong to are not affected. Owners and admins who manage the team can use it, but never on their own row, and an admin cannot use it on an owner. > Most security is not clever. It is remembering the small things, and now a page remembers them for you. #### Where to start Open Security and work down the checklist. If you have a shared computer at the front desk, turn on auto sign-out first. Then add a passkey for yourself. It takes a few seconds. For every step, see the help articles Check your security on the Security page, Sign in with a passkey, and Remove someone from your team and sign them out. ### Write your blog with the AI you already use The blog editor builds a prompt for ChatGPT, Claude or Gemini. Paste the reply back and the post fills itself in for you to check, with no AI credits used. The Bookatu team · 2026-10-28 · updated 2026-10-29 · Product · https://bookatu.com/en-nz/blog/write-your-blog-with-the-ai-you-already-use · markdown: https://bookatu.com/blog/write-your-blog-with-the-ai-you-already-use.md > **The short version** > > - In the blog editor, Use your own AI turns a title and a short brief into a prompt for ChatGPT, Claude, Gemini or any other AI. > - Paste the AI's reply back and Fill the post writes the title, excerpt, body, search title, search description and tags. > - Nothing is saved until you press Save draft or Publish, and it uses no AI credits. > - Prefer to stay in your AI app? Connect it to Bookatu with an API key and it can draft, update and publish posts, but never delete one. A blog on your own site gives local clients something to find on Google, and a reason to trust you before they book. The hard part is the writing. Plenty of owners already have an AI they like and know how to talk to. Bookatu's own Write it for me button is still in the editor. Now, if you would rather use yours, the editor meets you halfway. #### The prompt Bookatu builds Open Blog, in the Grow part of your admin menu, and start a New post, or open one you are working on. At the top of the editor, tap Use your own AI. Give it a Title, and a few words under What should it cover?: who it is for, the main points, anything to mention. Tap Generate prompt, then Copy prompt. The prompt is written for the AI rather than for you, so it looks a little technical. It tells the AI: - Who the post is for: your clients, and people thinking of booking with you. - Your business name, type, city and language, so it writes in the language of your website. - To keep the tone plain, warm and practical, and to make no medical or legal claims. - Not to make up prices, offers, opening hours or staff names, and to leave out client names and personal details. - How long each part may be, and to reply in a fixed shape Bookatu can read. Only those public business details go into the prompt. Nothing about your clients ever does. #### Paste the answer back Paste the prompt into ChatGPT, Claude, Gemini or any AI, and copy its whole reply. Back in Bookatu, paste it under Paste the AI's answer and tap Fill the post. The editor fills in the title, the excerpt and the body. The search title, search description and tags go under Search & sharing. A reply with a bit of chat around the answer is fine. If Bookatu cannot read it, nothing changes, and it asks you to copy the AI's whole reply. If the post already has words the answer would overwrite, Bookatu asks first: Replace what is there? Choose Yes, replace, or Keep what is there. #### Review, then publish Filling the post never saves it. The note says Filled in. Review it, then save. Read it the way a client would. Add the details only you know, like your prices or the products you use, because the AI was told not to guess them. Then press Save draft to come back to it later, or Publish to put it on your blog. The body comes in with the editor's simple formatting: headings, paragraphs, lists, bold and links. Raw HTML does not come through. Add a cover image yourself if you want one. None of this uses AI credits, because Bookatu is not running the AI. You are, in the app you already use. > Your AI writes the first draft. You decide what goes live. #### Or run the blog from your AI app If you work in an AI app that connects to other tools, such as Claude Desktop or Claude Code, you can skip the copying. Bookatu has an MCP server, a standard way for AI apps to connect to the software you use. Open API & monitoring, in the Settings part of your admin menu, and make a key. For the blog, tick See posts, forms and email drafts and Write posts, forms and email drafts, then tap Create key. Tap Copy config and paste it into your AI app. Your key is already in it, so there is nothing to fill in. Owners and admins can make keys. Then ask in plain words. Your AI can list your posts, open one, write a new one, update it, publish it or take it off your blog. A new post starts as a draft unless you ask for it to go live straight away. - It can never delete a post. Removing one stays with you, in the admin. - Editing a post never changes its web address, so links you have shared keep working. - A key can do only what its scopes allow. Revoke it on the same page whenever you like. #### Which one to use Write it for me is the quickest, right inside the editor. Use your own AI suits you if you already have a favourite AI and want to use it. The MCP route suits owners who already do their work in an AI app and would rather ask for a post than open the editor. All three land in the same place: a post you read, change and publish yourself. The help articles Write blog posts with your own AI and Manage your blog from an AI tool have every step. For prompt tips that work in any AI, read How to write a salon blog post with ChatGPT or Claude. ### Booking clients in another time zone, with both clocks labelled A client booking a video consult from abroad, or a visit ahead of a trip, now sees times on a clock that is clearly labelled. You keep your own clock with theirs beside it. A phone number typed from abroad, the way people write it there, gets that country's code. And a moved booking emails the client the new time with a calendar file. The Bookatu team · 2026-10-21 · Product · https://bookatu.com/en-nz/blog/booking-clients-in-another-time-zone · markdown: https://bookatu.com/blog/booking-clients-in-another-time-zone.md > **The short version** > > - A client booking from another time zone sees times on a labelled clock: their own first for a video booking, yours first in person. > - You keep your own clock. Where the client's clock differs, their time is one extra line. > - A client abroad who types their phone number the way people write it there gets that country's code. > - A moved booking emails the client the new time, the old one, and a calendar file. Say you run a skin clinic with short video consults. A new client finds you from overseas and books one for Tuesday at nine. If nothing on the page says whose Tuesday, or whose nine, they will read it on their own clock. That is a reasonable thing to do. It is also how people log on hours early, or a day late. The same question catches a visitor booking ahead of a trip: a massage, a cut and colour, or a table for the week they land. Bookatu now answers it for them. #### One rule for which clock comes first When a client books on your booking page or Website widget, Bookatu notes the time zone their phone or computer is set to. It keeps that with the booking, so later emails and reminders can use it. Then one rule decides which clock comes first. - Video calls show the client's clock first, because that is where they will be sitting. That covers any service set to Online meeting under How clients meet you, and any booking that carries a video link. - Visits in person show your clock first, because that is where they will be standing. Theirs comes second, to help them plan the trip. - When the two clocks read the same, or Bookatu does not know where they are, they see your clock alone, still labelled. That last case covers bookings you add yourself in the admin. Bookatu only learns a client's time zone when they book on your booking page or Website widget. #### What the client sees while booking On your booking page, take a service set to Online meeting. When the client's clock differs from yours, the whole date and time step moves onto theirs. The days start from their today and the times are their times. A note above them reads "Times shown in your time", with their city and zone. The review screen shows their day and time first, then the same moment in your city. For a visit in person, the times stay on your clock, because that is the clock on your wall when they walk in. The note above them names your city. If their phone or computer is on another clock, two things change. The note asks them to double-check the time. And once they pick a time, a line under it does the sum: your time, and what that is on their clock. #### What lands in their inbox The confirmation email follows the same rule. The main time carries its zone label. Where the two clocks differ, a quieter line underneath gives the same moment on the other clock, with its city. The reminder does the same, with the time in large type. A text reminder carries one labelled clock, to stay short. The confirmation also carries a calendar file, which their calendar shows on whatever clock their phone is set to. The Manage my booking button in that email opens their booking. If they open it on yet another clock, say on a stopover, the page adds a line starting "On your clock". It gives the time where they are. #### What you see Your Calendar and the rest of your admin show your own clock. When a client booked from a clock that differs, you get one extra line. Open the booking and look under Booking details. Below the Date and Start time you will see Client's time, with their day, time, zone and city. The New booking email you get when a client books online has a Client's time row too. So when they message to check a time, you can answer in theirs without working it out. #### Phone numbers typed from abroad Clients abroad type their number the way they would at home, usually without a country code. Bookatu now also reads it with the country their time zone points to. A number written the way people write it there is saved with that country's code. Your local clients are not affected. A number written the way people write it in your country reads the same as it always did. A regular who books while travelling keeps their usual number. A number typed with a plus and a country code keeps the code it was typed with. Numbers you type yourself, in a client's Phone field, are read with your own country first. So start an overseas number with a plus and its country code. #### When a booking moves The client now hears when their booking moves. It does not matter who moved it: you on your Calendar, or the client from their booking. They get an email marked Booking moved. It shows the new time by the same rule as their confirmation, and the old time under Previously. A fresh calendar file is attached. It is for the same booking they saved, so their calendar can update that entry instead of adding a second one. Reminders reset too, so if one already went out for the old time, a new one goes out for the new time. Only a real move sends the email. Change only who is doing it, or how long it takes, and the client gets no email. When a client moves a video call themselves, the new times are on their own clock. Under Move your booking to, they see the new time on both clocks before anything changes. The move happens only when they tap Yes, move my booking. > You keep your clock. They get theirs. The label says which is which. #### Two things worth checking - Your Country code and Timezone in Settings, under Region & currency. Your clock and the reading of local phone numbers both start there. - Online meeting under How clients meet you, on each service you run by video. It is what puts the client's clock first. Nothing else needs turning on. The next client who books from another time zone sees a time they can read at a glance. You see theirs next to yours. ### Choose who does each service, and give each person their own hours Limit a service to the people who actually do it, from the service or from the person. Give anyone on your team their own working week, with a break if they take one. And add a photo to every card, so clients can see who they are booking. The Bookatu team · 2026-10-21 · Product · https://bookatu.com/en-nz/blog/assign-services-and-hours-to-each-staff-member · markdown: https://bookatu.com/blog/assign-services-and-hours-to-each-staff-member.md > **The short version** > > - Choose who does each service, on the service or on each person's card. Clients are only offered the people you chose. > - Switch on Own hours for anyone who works a different week. Their hours and break replace the business's on their days. > - The Services list and the Team page show who does what, and who has their own hours. > - Add a photo to each card. Clients see it on your home page and when they choose who to book with. Most teams are not interchangeable. Your colourist does colour, the newest stylist is not doing extensions yet, and one therapist works late on Thursdays. Your booking page should know that, so nobody is offered for a service they do not do, or at a time they are not in. #### Choose who does a service Open Services in your admin and tap a service to edit it. Depending on your type of business, your admin menu may call it something else, such as Treatments, Sessions or Classes. Just above the Available online switch is a new question, Who can do this service: - Everyone on the team. Anyone who takes bookings, including people you add later. New services start here. - Only the people I choose. Tick who does it, and clients booking online are only offered them. Then tap Save changes. If you tick nobody, the form asks you to pick at least one person, or choose Everyone. Services that run at set times as a group, and add-ons, do not have this question. A group class is run by whoever is on each session, and an add-on is always booked with something else. #### Or choose from the person Open Team, tap the pencil on someone's card, and tick what they do under Services this person does. This is handy when someone joins or learns a new treatment. Unticking a service that everyone does keeps it for the rest of the team. What the card will not do is leave a service with nobody who takes bookings. If a change would do that, the card names the service and asks you to choose who does it on the service first, or keep it ticked. Nothing on the card is saved until that is sorted. Once a service has its own list, someone you add later is not on it until you tick it on their card or choose them on the service. A new person's card starts ticked on every service that everyone does. #### See who does what at a glance On the Services list, a service limited to some people has a label that starts with Only, followed by their names. If nobody left on its list can be booked, say because they were all removed from the team, it reads Nobody bookable instead. On the Team page, each card says All services or a count such as 3 of 8 services. Anyone on their own week has an Own hours badge. #### Give each person their own hours Open someone's card and there is now an Own hours switch next to Working hours. With it off, the person is booked in the business's opening hours on the days ticked, as before. Turn it on and the day ticks become a full week, the same editor you use for Opening hours in Settings. The week starts as the business's opening hours on the days they already work, so you only change what is different. Each day has its own Open switch, start and finish, and Copy puts one day's hours onto other days. The days you switch on become their working days. On those days, their hours replace the business's. They can start before you open, finish after you close, or work a day you are normally shut, and nobody else's times move. If you change your Opening hours later, their week stays as it is. ##### One break a day Tap + Break on an open day to add one, shown as Closed between two times. If the business closes for lunch, their week starts with the same break, which you can move or remove just for them. Your booking page will not offer a time that runs into it. If a break does not make sense, the day says what is wrong and how to fix it, and the card will not save until you do. Switch Own hours off to put someone back on the business's hours. #### Where their hours count These all use their own hours: - Your booking page. Their times start at their own start time and step by your Slot interval in Settings. With 30 minutes, a 9:15 start gives 9:15, 9:45 and so on. - The last check when a client books, so a time inside their break is turned away. - The times suggested when you or your team book a client in from the admin. - Tools and AI assistants you connect to Bookatu. Processing time, rooms and blocked time work inside their hours as they always have. One-off changes still come first. Drag the business's hours for one date in the calendar, apply it to just that day, and everyone is booked inside those hours on that date. > **Good to know** > > If you run a restaurant, table reservations always follow your business's opening hours, whatever a host's own week says. #### Put a face to every name The card also has a Photo field. Tap Choose file or drag a photo in. The box asks for a square one, about 400 × 400, as a PNG, JPG or WEBP up to 5 MB. Large photos are resized for you. The photo saves with the rest of the card. Clients see the photo in the team section of your home page, with each person's name, title and short bio. They see it again on your booking page when they choose who to book with. Anyone without a photo shows their initials on their calendar colour. To hide the team section, switch off Team under What customers see in Settings, then tap Save visibility. If a photo you added before is not showing, add it again. > A client should only ever be offered someone who does the service, at a time that person is actually in. Changing who does what, or someone's own hours, needs the Manage the business permission, which owners and admins have from the start. There is no need to set it all up at once. Start with whatever causes the most back and forth at the desk. ### Check clients in, edit bookings and block time off from your calendar Mark a client as arrived from the calendar, change a booking's service, length or price after it is made, and block a whole week of leave as one entry. Restaurants can take a party size and a table on phone bookings, and front-desk logins can book when you allow it. The Bookatu team · 2026-10-21 · updated 2026-10-30 · Product · https://bookatu.com/en-nz/blog/check-clients-in-and-edit-bookings-from-your-calendar · markdown: https://bookatu.com/blog/check-clients-in-and-edit-bookings-from-your-calendar.md > **The short version** > > - Tap a booking on the calendar and press Check in when the client arrives. > - Edit booking changes the service, length or price of a pending or confirmed booking. > - Blocked times takes a First day and a Last day, so a week of leave is one entry. > - On phone bookings, restaurants are asked for the Party size and can pick a Table. > - Turn on Edit the calendar in Role permissions and a front-desk login can book. Most of a working day happens on the calendar. A client walks in. A trim turns into a cut and colour. Someone needs next week off. This update is about those moments. #### Check clients in from the calendar When a client arrives, tap their booking on the Calendar and press Check in. The panel then shows Checked in and the time. Undo check-in clears a wrong tap. The calendar now shows who is in. The Day view puts a small tick in front of the time and name, and the Week view shows Checked in on the booking. The same buttons are in the Actions card when you open the booking with Full details. Checking in only notes the time. It does not change the status, email the client or touch a deposit. If two people tap it, the first time stands. It works on pending, confirmed and completed bookings, but not on cancelled ones or no-shows. #### Change a booking after it is made Plans change once the client is in the chair. A massage runs long, or you agree a new price on the day. Open the booking with Full details and press Edit booking in the Actions card. You can change: - Service. It brings its own length and price, the same price a new booking would get. - Length (minutes). The form shows the new end time. - Service price. The price before any discount, without extras. The start time, the person and the client stay put. To move a booking, use Reschedule. Extras stay on the bill. A percentage discount is worked out again on the new price, and a fixed amount off stays the same. You see the new total before you save, and it can never drop below what the client has already paid. If the change runs into the person's next booking, blocked time, a break or closing time, you get a warning first. Press Save anyway if that is fine. A room or table is different. If another booking already holds it at that time, the change is refused. Each edit adds a line to the booking's Internal notes saying what changed and who did it. A connected Google Calendar updates too. The client is not emailed, so tell them if the price changed. Edit booking is offered on pending and confirmed bookings, but not while a deposit is still being paid online. To type a price of your own, a role also needs the Refund orders permission. #### Block a whole stretch of time off in one go The Blocked times card under the calendar has a First day and a Last day. Under Block, pick Everyone, one team member, or a room or chair, and press Block time. To make it happen every week, tick Repeats weekly. - Tick All day to block whole days, midnight to midnight, in your business's time zone. - Or set From and To. The block runs from the From time on the first day to the To time on the last, nights included. - One entry can cover up to a year. However long it is, it is one entry, and one Remove gives every day back. A weekly block asks whether to remove one day, that day and the following ones, or the whole series. Clients can't book that time online. The calendar shows each day blocked in the Day and Week views. Those days can't be dragged, so to change the dates, remove the entry and add it again. #### Restaurants: party size and a table on phone bookings When a guest rings, book them from New booking, or drag across the calendar and choose Book a reservation. For restaurants, the form now asks for the Party size. It starts at 2, as on your booking page. Other kinds of business see the same form as before. If the service needs a table, the times on offer follow the party. Say every table big enough for four is taken at seven, but a table for two is free. Then seven is offered to a couple, but not to a group of four. A Table list appears too. It shows only the tables that service uses, and a table too small for the party can't be picked. Leave it on Any table that fits and the party gets the smallest free table that seats them. If the one you pick is taken at that time, they get the smallest free table that fits instead. #### Front-desk logins that can book Someone on your front desk may take bookings all day but not need the rest of the admin. Here is how to set that up. Go to Team. Under Who can sign in, fill in Give someone a login, choose the Staff role and press Add login. Then open Role permissions, turn on Edit the calendar for Staff, and press Save changes. Staff see only their own appointments by default, so you will usually want See everyone's calendar on too. Only the owner can change these, and each switch applies to everyone with that role. A Staff login with Edit the calendar can book phone clients, move and reschedule bookings, block time, check clients in and edit bookings. It works the other way too. Turn it off for a role, Admin included, and that role can no longer change the calendar. A login without it sees View only on the calendar, and the booking panel drops the buttons it can't use. The New booking page explains why it can't book, and who to ask. > Your calendar should show what is really happening in the room, not just what was planned last week. Apart from those role switches, there is nothing new to set up. The next time a client walks in, tap their booking and press Check in. ### Go live without Stripe, and choose what clients can change online If clients pay you in person rather than online, your booking page no longer needs Stripe to go live. And a new section in Settings lets you decide whether clients can cancel or move a booking online, how close to the start, and how many times a booking can be moved. The Bookatu team · 2026-10-21 · Product · https://bookatu.com/en-nz/blog/online-booking-pay-in-person · markdown: https://bookatu.com/blog/online-booking-pay-in-person.md > **The short version** > > - Your booking page can now go live without Stripe, as long as you do not take deposits or sell products online. > - Without Stripe, you need a confirmed email, a service clients can book online, a team member to book with, and a phone number or email. > - Settings, Booking page shows what is in the way, and how to fix each thing. > - A new section, Online changes by clients, lets you choose when clients can cancel or move a booking online, and how many times a booking can be moved. > - If you already use Stripe, going live works as before. The new settings change nothing until you change them. Plenty of businesses take payment in person: a card machine at the counter, cash, or a bank transfer. Until now, going live on Bookatu meant connecting Stripe first, even if you never take money online. That rule has changed. #### When you still need Stripe Stripe is how Bookatu takes card payments online. To go live, you now need it only if you take deposits or sell products online. Open Settings, Booking page. If Stripe is in the way, the panel lists what needs it, each with a link to switch it off: - Deposits, when a service clients book online would actually be charged one. The link is Turn deposits off. - Products clients can buy in your online shop. The link is Stop selling products online. Turn these off and Stripe is no longer needed. If you would rather keep them, connect Stripe instead. One thing to check: new accounts start with Ask for a deposit to confirm a booking switched on. If you take payment in person and have not changed it, that is the one to turn off. #### What your page needs without Stripe Asking for Stripe also kept half-built pages off the web. Without it, Bookatu checks three things instead, so a client who opens your page finds something to book and a way to reach you. If any are missing, the panel lists them, each with a link to the right page: - Add a service clients can book online - Add a team member clients can book - Add a phone number or email clients can reach you on Your email also has to be confirmed. If it is not yet, the panel shows a Resend confirmation email button where the Publish button would be. When nothing is left in the way, press Publish booking page. The Private label changes to Published, and your page is live. #### What clients see without Stripe Clients book as normal and pay you in person. Your booking page does not ask them for a deposit. Paid group classes are the exception. Without Stripe, they cannot be booked online. When a client picks a paid class, the button reads Online payment unavailable, with a note asking them to contact you directly. Gift cards, packages and memberships do not stop you going live, and neither do paid classes. Where gift cards, packages or memberships show, a client sees This business hasn't set up online payments yet instead of the button to buy or join. No money is taken online. When you are ready to take deposits, connect Stripe and switch deposits on. Until you connect, Settings, Deposits & cancellations shows a Connect Stripe link just below the deposit switch. It also says plainly that clients book without paying a deposit. > Take payment the way you already do. Your booking page no longer makes you open an account you do not need. #### Decide what clients can change online Confirmation and reminder emails carry a link to the client's booking. That page has two buttons, Choose a new time and Cancel booking. Until now they were always there, right up to the start. The new section, Settings, Online changes by clients, lets you set the rules: - Clients can cancel online. Switch it off and clients are asked to call or email you to cancel. - Clients can move their booking online. Switch it off and they are asked to call or email you for a new time. - Stop online changes before the start. A number of hours, up to 336, which is two weeks. 0 keeps changes open until the start. - Most times one booking can be moved online. Up to 20. 0 means no limit. Press Save online changes. The rules apply to every upcoming booking, including ones made before you saved. The defaults are what clients could always do, so nothing changes until you change it. #### What your client sees When a change is allowed, the buttons are there as before. If you set a cut-off, the Cancellation policy box tells the client until when they can make changes online. If you set a limit, it shows how many online moves that booking has left. When a change is not allowed, its button is not shown at all. In its place, the client sees a short reason, such as This booking can't be moved online. Below it is a line asking them to contact you, with the phone number and email from your Business details, ready to tap. Your email shows there even if Show on your storefront is off for it. Only someone with that booking's own link can open the page, and you have just asked them to get in touch. The rules are checked again when the client presses a button, not only when the page loads. So a page left open past your cut-off still cannot make the change. #### Three details worth knowing - The cut-off is not your free cancellation window. The Free cancellation window under Deposits & cancellations decides whether a deposit is kept. Stop online changes before the start decides whether a change can be made online at all. - Only moves a client makes online count towards the limit. Moves you make on the calendar never do. - If you use Ask clients to confirm the day before, a client can still answer Can't make it, even after your cut-off or with online cancelling switched off. The slot is then freed. You asked the question, and an honest no is better than a no-show. #### Where to find it Both are in Settings, under Essentials: Booking page to go live, and Online changes by clients for the new rules. If your page is still private and you are not sure why, the help article Why my booking page is not live yet walks through each step. ### Print or email receipts at the point of sale, and tax rates to three decimals Every sale at the point of sale now has a receipt you can print or email. Here is how that works, plus barcode scanners that end with Tab, opening the cash drawer, tax rates like 14.975%, and invoice payment links that charge the full total. The Bookatu team · 2026-10-21 · Product · https://bookatu.com/en-nz/blog/print-or-email-receipts-at-your-salon-till · markdown: https://bookatu.com/blog/print-or-email-receipts-at-your-salon-till.md > **The short version** > > - Every sale at the point of sale now has a receipt, printed on an 80 mm receipt printer or emailed to the client. > - Attach a client at the point of sale or after the sale, and the sale goes on their profile. > - Barcode scanners that end a scan with Tab now work, just like ones that end with Enter. > - A cash drawer plugged into your receipt printer can open as each receipt prints. > - Tax rates take three decimals, so 14.975% stays 14.975%. > - If your prices exclude tax, invoice payment links now charge the full total. A client buys a bottle of shampoo on the way out and asks for a receipt. Here is what is new at the point of sale, and a few money details that have to be exact. #### A receipt for every sale Ring up a sale on the Point of sale page (the Sell button on Products) and tap Record sale. The "Sale recorded" message now has two buttons, Print receipt and Email receipt. Sales made in Sell mode on the Scan station get them too. Each receipt shows: - Your business name, address and phone, and your tax registration number if you have one. - A receipt number, and the date and time. - Each item, with quantity and unit price when more than one was bought. - The subtotal and discount, when you gave one. - The total, the tax inside it when your prices include tax, and how it was paid. The receipt is saved with the sale, so a later reprint shows the same items, prices and tax as on the day. Recent sales, further down the page, lists your last ten sales to reprint or email. It shows takings, so only people with the "See analytics & earnings" permission see it. #### Printing uses the printer you already have Printing goes through your browser's print dialog, so it uses whatever receipt printer your computer already prints to. Make that printer the default and pick its 80 mm roll paper once in the dialog. The receipt is 72 mm wide, the printable width of an 80 mm roll, and only the receipt prints. To have each receipt come up on its own, turn on "Print a receipt when a sale is recorded". It sits in the "Receipt printer and cash drawer" card at the bottom of the Point of sale page. It is off by default, and only people with the "Manage the business" permission can change it. The print dialog then opens by itself, once per sale, so a refresh does not print twice. Someone still presses Print unless the browser is set to print straight to the default printer, which the card explains. The setting covers every device that records a sale. #### How the cash drawer opens A web page cannot open a cash drawer by itself. But most drawers plug into the receipt printer. The printer's driver, the software that runs it on your computer, can open the drawer each time it prints. So look for a cash drawer or open drawer option in your printer driver's settings, and switch it on. Then turn on "Print a receipt when a sale is recorded". The drawer now opens as each receipt prints. > Your browser prints the receipt. Your printer opens the drawer. #### Email it, and the sale joins their history To email a receipt, the sale needs a client with an email address. Attach one before you record the sale, with "Attach client (for a receipt by email)", or afterwards, when you tap Email receipt. Search by name, email or phone, or tap "+ New client" and add a name plus an email or phone number. Someone already on file with that email or phone is picked instead of being added twice. New clients added at the point of sale are saved without marketing consent, because asking for a receipt is not asking for offers. The email matches the paper receipt and uses your Storefront language, like your other client emails. A second tap does not send it twice, and an address that bounced before is not tried again. Anyone with the "See analytics & earnings" permission then sees the sale in the client's Purchase history, counted in their Lifetime spend. A sale already tied to one client cannot be moved to another. #### Scanners that end with Tab A USB or Bluetooth barcode scanner acts like a very fast keyboard. It types the code, then presses Enter or, on plenty of scanners, Tab. A scan ending in Tab now works just like one ending in Enter. That holds on the Point of sale page, the Scan station, Receive stock, Count stock and a product's Barcode box. Bookatu tells a scanner from a person by speed. When you press Tab yourself, it still moves you to the next box. #### Tax rates with three decimals Some rates do not stop at a whole number. In Quebec, GST and QST together come to 14.975%. On the Tax page, the Rate (%) box now takes up to three decimals. Bookatu stores that exact rate and calculates with it. You enter it as one combined rate. It is never rounded to 15%, whether on the Tax page, on the visit receipts clients open from their account, or on the point of sale receipt. When that receipt shows tax, it writes the rate the way your language does, so a French one reads 14,975 %. The sums are exact too. Tax is worked out in whole cents, and half a cent always rounds up. So 14.975% of $100.00, which is $14.975, becomes $14.98. #### Invoice payment links charge the full total If "Charge tax" is on and "Prices include tax" is off on the Tax page, tax is added on top of each invoice. Payment links sent from Finance now charge that full total. The tax shows as its own line on the payment page, named with your Tax name, such as GST or VAT. The total is fixed when you send the invoice. If the client opens the link weeks later, it charges the same total, even if your rate has changed since. If your prices include tax, nothing changes. > **Good to know** > > The point of sale records money already taken, in cash or on your own card machine. It does not take cards itself. If your prices exclude tax, it charges them as listed and adds no tax, so its receipts show no tax line. None of this changes how you ring up a sale. Tap the products, record it, and the receipt is ready when the client asks. ### Every booking and what they bought, on one client profile A client's profile now counts every booking they have with you, shows what they bought beyond their appointments, keeps a postal address, and holds on to the note you typed when you first added them. Here is what changed and where to find it. The Bookatu team · 2026-10-21 · Product · https://bookatu.com/en-nz/blog/full-client-history-on-one-profile · markdown: https://bookatu.com/blog/full-client-history-on-one-profile.md > **The short version** > > - A client's bookings list now counts every booking they have with you, and you can open the older ones too. > - A new Purchase history card shows what they bought outside their appointments, and the payments recorded for them. > - Lifetime spend now adds those purchases to completed appointments, and shows both parts. > - Clients have a Postal address you can type, import and export. > - Saving Client details leaves the note you typed when you first added the client exactly as it was. A client profile is where you go for quick answers. How long have they been coming? What did they buy last time? Where do you post their gift card? Some of those answers used to live somewhere else. Now they are on the profile. #### Every booking, not just the newest 100 The profile used to load a client's newest 100 bookings and count only those. A long-standing regular could never show more than 100. Now the counts at the top of the card cover every booking they have with you, past and upcoming, whatever its status. The list still opens on the newest 100. When there are more, a line such as Showing the latest 100 of 260 appointments says so. Show 100 more adds the next hundred. When more than another hundred are waiting, Show all 260 puts the whole list on one page, up to 5,000 bookings. The card's name follows your kind of business. A salon, spa or clinic sees Appointments, a studio sees Classes, a trainer sees Sessions and a restaurant sees Bookings. #### What they bought, in one card Just below the bookings list is a new Purchase history card. It lists what the client bought outside their appointments, newest first, each with its date and amount: - Shop orders - Invoices - Gift cards they bought, and ones someone else bought that they redeemed - Packs - Memberships, from joining through each renewal - Point of sale purchases A sale at the point of sale shows up once the client is attached to it. One way is the Attach client (for a receipt by email) button on the Point of sale screen. Below the purchases, Payments lists the payments on record for the client. That includes booking deposits, cash or bank transfers recorded against them, and refunds, which show as minus amounts. At the top of the card, Purchases and Payments recorded each have a total, and so does each kind that has something counted. The two totals are kept apart on purpose. A shop order appears once as the thing bought and once as its payment, so adding them together would count it twice. ##### What counts toward the total Greyed lines are listed so the history is complete, but they are not counted. That covers refunded or cancelled orders, and invoices that are open, void or refunded. It also covers voided gift cards, and gift cards somebody else bought that this client redeemed. Packs and memberships count once a payment for them is on record. ##### Matched by email or link, never by name A purchase shows on a profile when it is linked to that client, or carries their email. That means the email on their record, or on the client account linked to it. Bookatu never matches by name, so two clients who share a name are never mixed up. A client with no email on their record or account only shows what is linked to them directly. Nothing from another business ever appears. #### Lifetime spend, with its parts showing The Lifetime spend tile used to show completed appointments only. It now adds the purchases that count, and the line under it shows both parts, for example $1,240.00 appointments + $180.00 purchases. The first part uses your word for a booking, so a studio sees classes. > **Good to know** > > A pack, membership or gift card counts as a purchase when it is bought. A completed appointment it pays for later still counts at its booked price. That is why the tile shows both parts, so you can see what the total is made of. #### Who sees the money Purchase history and the purchases part of Lifetime spend follow the See analytics & earnings permission. Owners and admins have it from the start. Staff do not, so they see Lifetime spend as before: completed appointments only, labelled that way. An owner can turn it on for Staff on the Role permissions page, linked from the Team page. It also opens your revenue and reports to that role, so treat it as a decision about your books as a whole. #### A place for their postal address Clients now have a Postal address. The box is on the form you open with Add client on the Clients page, and in Client details on their profile. It is a single box, so any country's format fits. Once saved, it shows in the profile header with their phone and email. It travels with the rest of their details: - Import data reads a single Address column, or separate columns for street, suburb, city, state, postcode and country, and joins them into one address. - A row with only a state or a country gets no address. If the Address column already names the city, it is not added twice. - Export CSV on the Clients page now ends with an Address column, so every column you already had stays where it was. - Export data (JSON), under Privacy & data on the profile, includes it too. #### Notes that stay put Say you typed an allergy in Notes when you first added a client. Saving their Client details now leaves that note exactly as it was. That note lives in the Record, the card below Client details. It is the oldest entry, so you will find it at the bottom of Full history. Client details now says what it is for: Keep their contact details and address up to date. To add something new, use Add to record. Anything saved as Allergy or reaction, or pinned, always shows under Read first. The note from the day you added them is a plain Note and cannot be pinned. If it is an allergy, it is worth adding again as Allergy or reaction. > A profile should answer the question you opened it for, without sending you somewhere else for the rest. #### Where to find it Open Clients and pick anyone. For owners and admins there is nothing to switch on. If you are moving from another tool, Import data now picks up addresses from your file too. ### Your waitlist now hears about more than cancellations Cancellations are no longer the only thing that reaches your waitlist. Time freed by a moved booking, an unpaid deposit or a no-show marked before the start is offered too, waiting clients can get more than one offer, and repeat bookings check your diary first. The Bookatu team · 2026-10-21 · updated 2026-10-30 · Product · https://bookatu.com/en-nz/blog/automatic-waitlist-for-appointments · markdown: https://bookatu.com/blog/automatic-waitlist-for-appointments.md > **The short version** > > - A freed time now goes to your waitlist when a booking is cancelled or moved, a deposit is never paid, or you mark a no-show before the start. > - It is only offered if a client could really book it. > - A client who misses an offer stays on the list, for up to 3 automatic offers and never the same opening twice. > - A new standing series checks each repeat visit against your diary, and you choose whether a clash is booked and flagged or skipped. A gap in your day can come from more than a cancellation. A client moves their booking to Thursday. Someone books online and never pays the deposit. A client rings to say they cannot make it this afternoon, and you mark a no-show. Until now, only a cancellation sent offers to your waitlist by itself. Now all of these do. #### Four ways a freed time reaches your list Bookatu offers the time to your waitlist when: - A booking is cancelled, by you, your team or the client. - A booking is moved, by you or by the client online. Moving it to another team member at the same time counts too. - An online booking's deposit is never paid. Once a day, Bookatu releases these unpaid holds. - You tap Mark no-show before the appointment starts. For each opening, Bookatu looks for waiting clients who asked for that service, or for any service. If they gave dates, the day has to fall inside them. It ranks them by what they have spent with you, longest waiting first when two are level. Up to five of them are sent the opening by email, with a one-tap claim link. Clients who have agreed to texts get it by text too, when texting is set up and your plan includes it. The link works for up to six hours, and the first to claim the time gets it. On a service that takes a deposit, their claim is held while they pay it. #### Only openings a client can really book Before anything goes out, Bookatu checks the freed time the way your booking page would. It has to be still ahead, inside your opening hours and fully free. It also has to fit your Minimum notice and Book up to settings, under Settings, Booking rules. A booking nudged fifteen minutes later still covers part of its old time, so nobody is told. So an opening inside your Minimum notice is not offered, since nobody could book it on your page either. Automatic offers also cover one-to-one services only, not seats in a group class. #### More than one chance for each client A client who does not take an opening now stays on the list for the next one. So does a client who tapped a moment after someone else claimed it. Each client gets at most 3 automatic offers, and never the same opening twice. On the Waitlist page, their card shows a badge such as Offered 1 of 3 and when the last opening was sent. After the third, it says automatic offers used up. You can still tap Offer a slot to message them yourself, and those messages do not count towards the 3. Automatic offer emails and texts now give the time as well as the date, with your time zone. #### A list that tidies itself A client stays on the list until they book or their last date passes. After that date they leave the Waitlist page and get no more offers. Bookatu also matches each waiting client to your client list, by email and then by phone number. So regulars who join from your public form now show their lifetime badge, and what they have spent counts when an opening is offered. Once a matched client has a confirmed booking for the service they asked for, inside their dates, they come off the list as booked. Any booking counts if they asked for any service, and it does not matter who made it. A booking still waiting on its deposit does not count until it is paid. Mark booked and Remove work as before. #### Repeat bookings that check your diary A standing series books several visits at once, so a clash is easy to miss. You set one up from the See you again? card on a booking, or by ticking Repeat this appointment on the New booking page. Both now check each repeat visit against your opening hours and breaks, closed days, the team member's days off, blocked-out time, other bookings and the gap you keep between them, and free rooms. Then you choose what a clash means, under If a visit clashes on the card or If a repeat clashes on the form: - Book it anyway and flag it. This is the default, since you are choosing these times on purpose. The visit shows Booked, clashes, with the reason. The one exception is a visit that starts at the very same time as another booking with the same team member. That date is skipped. - Skip it. The date is left out, and the list says why. Reasons are plain, such as Closed that day or No free room then. The summary also asks you to check any flagged visits on the calendar. #### Change a whole series in one go Each visit the series booked has a Part of a standing series card. It now offers: - End the series after this appointment. Later visits are cancelled and the series ends. - Cancel all remaining appointments. Every visit still to come is cancelled, even when you start from a past booking. - Change the time of upcoming appointments. Pick a New time and either This appointment and the later ones or Every upcoming appointment. Dates stay the same, and the client is told each new time. For a move, the clash choice reads Move it anyway and flag it or Leave it where it is. Ending or cancelling asks you to confirm first. Every freed time goes to your waitlist under the same rules as any other opening. The wording follows your business type, so you may see session, class or reservation instead of appointment. Only roles with Edit the calendar turned on, under Team, Role permissions, see these buttons. > A gap in the diary is only lost if nobody hears about it. #### What to do now There is nothing new to switch on. Some clients who were sent an offer before this change may reappear on your Waitlist page. They can be offered openings again, because an offer no longer takes anyone off. Tap Remove for anyone who no longer needs a place. ### See your bookings in Google Calendar, Outlook or Apple Calendar Each team member can now see their bookings in the calendar app they already use, or connect their own Google Calendar. Here is how it works, who can see what, and what it does not do. The Bookatu team · 2026-10-21 · updated 2026-10-22 · Product · https://bookatu.com/en-nz/blog/sync-salon-bookings-to-google-outlook-apple-calendar · markdown: https://bookatu.com/blog/sync-salon-bookings-to-google-outlook-apple-calendar.md > **The short version** > > - A new Calendar sync page makes private links that Outlook, Microsoft 365, Apple Calendar and Google Calendar can subscribe to. Each team member can have one, and so can the whole business. > - Staff can now connect their own Google Calendar. Bookatu adds their new bookings to it, straight away or once the deposit is paid, and moves or removes them when they are rescheduled or cancelled. > - Busy times in a team member's connected Google Calendar can now keep clients from booking them. Events in Outlook, Apple Calendar or any app that uses the link do not block bookings. > - The link shows the service and the client's first name only. No contact details, notes or prices. > - Who can see what follows your Role permissions, on Calendar sync, the Dashboard and the bookings list. Your bookings live in Bookatu. The rest of your day lives in the calendar on your phone: the school run, the supplier visit, the dentist. The new Calendar sync page puts your bookings in that calendar too, on every device you use. #### Two ways in One is a private link that you add once to Outlook, Microsoft 365, Apple Calendar or Google Calendar. The other is for Google users: connect your Google Calendar directly, and Bookatu adds your new bookings to it. In Google, use one or the other, or every booking shows twice. Group sessions and workshops are not included in either. #### Where to find it - Settings: Calendar sync is listed under Grow. - Team page: when you edit a team member, the Google Calendar section links to it. - Bookings list: staff will find a Calendar sync button at the top, next to Calendar and New booking. In a salon, spa or clinic this list is called Appointments. Everyone who can sign in to your admin can open it. Trainees keep to their checklist. #### Your own calendar link Under Your calendar, tap Create my calendar link. The new link is shown once, so copy it straight away. Bookatu keeps only a scrambled fingerprint of it, not the link itself, so it cannot be shown again. If you lose it, tap Get a new link. Then add it to your calendar app: - iPhone, iPad or Mac: tap Open in Apple Calendar when the link appears. Or, on a Mac, open Calendar and choose File, then New Calendar Subscription, and paste it. - Google Calendar: on a computer, click + next to Other calendars, choose From URL and paste the link. It shows on your phone too. - Outlook and Microsoft 365: in Outlook on the web, choose Add calendar, then Subscribe from web, and paste the link. Your calendar then shows your bookings from the last seven days to 180 days ahead, with your blocked time and any closures for the whole business. A booking waiting for confirmation is marked tentative. Cancelled bookings and no-shows drop out. If a booking moves, or is handed to a colleague, the calendar follows. Google and Outlook check a subscribed link for changes every few hours, so a new booking can take a while to appear. #### What the link says about your clients A calendar app copies what it holds to every device and account it syncs with. So the link says as little as it can: the service and the client's first name. No surname, email, phone number, notes or price. Each booking also carries its reference and a link to it in Bookatu, which only opens for someone signed in to your admin. #### Keep the link to yourself Anyone who has the link can read that calendar, so treat it like a password. If it gets out, tap Get a new link, and the old one stops working at once. To stop it altogether, tap Turn off and confirm with Yes, turn it off. Calendars using that link stop updating. The page also shows when each link was made and when a calendar app last fetched it. When you remove someone from the team, their link stops working too. #### Connect your own Google Calendar If you live in Google, you can skip the link. In the same Your calendar section, tap Connect my Google Calendar and sign in to Google. You come straight back to Calendar sync. From then on, your new bookings go into your main Google calendar, straight away, or once the deposit is paid if the booking needs one. When a booking is rescheduled or cancelled, Bookatu moves or removes it. Staff can now do this themselves, but only for their own calendar. Connecting a colleague's still happens on the Team page and needs Manage the business, which owners and admins have by default. Disconnect removes your connection and takes back Bookatu's access at Google too. #### When your calendar shows you busy With Google connected, busy times in your main Google calendar now keep clients from booking you. This is on for calendars connected from now on, and off for those connected earlier. An owner or admin can turn it on or off for each person on the Team page. Bookatu sees when your events start and end, never their titles, descriptions, places or guests. Events marked Free do not count, and your team can still book over a busy time. If Google cannot be reached, Bookatu uses what it last read, and bookings go ahead. The link still runs one way: events in Outlook, Apple Calendar or any app that uses it do not block bookings. Block that time on the Calendar page instead, if your role has Edit the calendar. Moving or deleting an event in a calendar app never changes a booking. #### Who sees what Calendar sync follows your Role permissions, which the owner sets from the Team page. Two settings decide most of it: See everyone's calendar and Manage the business. Owners and admins have both by default. Staff have neither. - Everyone looks after their own link and their own Google connection. - The Whole business section needs both settings. Its link puts every team member's bookings and blocked time in one calendar, showing who each booking is with. It suits a screen at the front desk. - The Team links section needs both too. Make a link for someone without a login, or turn off one that has got out. Each row shows whether that person has Google connected. The Dashboard and the bookings list follow your Role permissions too. Without See everyone's calendar, a person sees only their own bookings. Without See analytics & earnings, they see no money: no takings, no prices, no revenue chart. Downloads of reports, products and stock need Export data. > The link carries just enough to recognise a booking at a glance. Everything else stays behind your sign-in. To try it, open Calendar sync, tap Create my calendar link and add it to your phone. If you run the business, also tap Create the business link, under Whole business, for the front desk. ### What happens when a client asks us to delete their data A client can request deletion from their own account, confirm it by email, and change their mind for 48 hours. Here is the whole lifecycle, including what stays behind and why. The Bookatu team · 2026-07-27 · Product · https://bookatu.com/en-nz/blog/what-happens-when-a-client-asks-us-to-delete-their-data · markdown: https://bookatu.com/blog/what-happens-when-a-client-asks-us-to-delete-their-data.md > **The short version** > > - Clients request deletion themselves, from their own account on your booking page. It never arrives as a vague email you have to interpret. > - The request is confirmed twice: they type their name, then tap a link sent to the email address on their file. > - After confirming there is a 48 hour cooling-off window with a big Cancel button. > - Payment and invoice records are kept because tax law requires it, with the personal details stripped out of them. > - You see every request on one screen in your dashboard, with where it stands and how many days you have left to respond. Sooner or later a client asks you to delete their data. Under GDPR they are entitled to, and in most booking tools that request lands as an email you now have to act on by hand: dig out their records, work out what you are actually allowed to remove, and remember to reply before the legal clock runs out. We built this differently. In Bookatu the whole thing runs as a proper lifecycle, and this post walks through it exactly as it happens, because if you run a salon in Europe you should know precisely what your software does in your name. #### It starts in their account, not your inbox Every client with a booking history at your salon has their own account on your booking page. Alongside their appointments and gift cards sits a Privacy section with two entries: Download my data and Delete my data. The download is instant and self-explanatory. The deletion is a bigger deal, so it starts with an explanation instead of a button. Before anything is armed, the screen says in plain words what will be erased: their profile, visit history, photos, forms, messages and reviews. It also says what will not be erased and why, so nobody discovers the tax-law part after the fact. Then comes the first check. To submit the request, the client types their own name, exactly as it appears on their account. A typo does not pass. That is a small hurdle for someone who means it, and that is the point: it filters out the idle tap without slowing down a real decision. ![A client's account page on a salon booking site, scrolling to the Privacy section and starting a deletion request with a typed-name confirmation](https://bookatu.com/blog/gdpr/request-deletion-poster.jpg) *01 · The request starts in the client's own account: a plain explanation first, then their name typed out to confirm they mean it.* #### The email double-check Submitting the form deletes nothing. Bookatu emails the address on the client's file with a confirmation link, and the request only moves forward once that link is tapped. This is the identity check: whoever asked also has to hold the inbox. If the link is never tapped, the request quietly expires after 48 hours and the account stays exactly as it was. Tapping the link opens a page that states, one more time, what is about to happen. Two buttons: confirm the deletion, or cancel the request on the spot. ![The emailed confirmation page for a data deletion request, offering a final yes or a cancel button before the cooling-off period begins](https://bookatu.com/blog/gdpr/confirm-cooling-off-poster.jpg) *02 · The emailed link opens a final yes-or-no page. Nothing has been deleted yet, and cancelling here ends the request.* #### 48 hours to change their mind Even after the email is confirmed, nothing runs for another 48 hours. The client's account shows the exact date the erasure will happen and a large Cancel button that works until that moment. People do change their minds. A regular who asked for deletion in a moment of frustration can undo it a day later with one tap, and nothing is lost, because nothing had been removed yet. When the window ends, Bookatu checks the account once more before running. If something changed in the meantime, say the client booked a fresh appointment during the cooling-off, the request does not run blindly. It moves to your queue instead, with the reason stated. #### The whole lifecycle at a glance 1. **They ask.** From the Privacy section of their own account, typing their name to confirm they mean it. 2. **They confirm by email.** A link goes to the address on their file. Nothing happens until it is tapped, and an untapped link expires after 48 hours. 3. **They can change their mind.** A 48 hour cooling-off window with a Cancel button, and the exact run date shown in their account. 4. **The erasure runs.** The account is checked again, personal data is removed, and financial records are kept with the personal details stripped. 5. **Everyone gets a record.** The client receives a confirmation email, and the completed request stays in your dashboard with its dates. #### What is erased, and what stays When the request completes, the client's profile and contact details are permanently deleted, along with their visit history, photos, form responses, messages and reviews. Past appointments stop being about a person and become anonymous entries, so your reports still add up but no longer say who sat in the chair. > **The legal bit** > > Invoices and payment records are not deleted, because tax law in most countries requires businesses to keep financial documents for a set period, usually around seven years. GDPR's right to erasure explicitly makes room for legal obligations like this. So Bookatu keeps the financial paperwork but strips the personal details from it: the invoice survives as a business record, and the person it pointed to is gone. Where a request cannot be met in full, the record says so rather than pretending otherwise. #### What you see on your side Every request appears on the Privacy and security screen of your dashboard from the moment it is raised. You can see where each one stands: waiting for the email confirmation, in its cooling-off window, held for your review, completed, cancelled or expired. Each active request also carries a quiet countdown, because GDPR expects a response within a month and the screen keeps you honest about it. Most requests never need you at all. The ones that do are held with the reason in plain words: the client still has an upcoming appointment, still owes money, or still has an active saved-card agreement with you. Once that is settled, you complete the request yourself. Before anything runs you see a preview of exactly what will be deleted and what will be kept with the personal details removed, and then you type the client's name to confirm. The same ritual the client went through, on your side of the counter. ![The Privacy and security screen in the salon dashboard, where deletion requests are listed with their status and a response countdown](https://bookatu.com/blog/gdpr/org-queue-poster.jpg) *03 · The owner's side: every request on the Privacy and security screen, with its status and a countdown for the legal response window.* > A deletion request is not an accusation. It is a client exercising a right, and good software makes that unremarkable. If you want the full picture of what Bookatu handles under GDPR, including the instant data download and the export of your own business, we wrote a companion piece for owners, GDPR without the panic, and the page at https://bookatu.com/en-nz/gdpr walks through the same flows with the actual screens. The short version is simple: when a client asks to be forgotten, your software should already know what to do. ### GDPR without the panic: what Bookatu handles for your salon Clients serve themselves a copy of their data, deletion requests run on rails with a 30-day countdown in your dashboard, and you can export your whole business any day. GDPR when the software does its share. The Bookatu team · 2026-07-27 · Product · https://bookatu.com/en-nz/blog/gdpr-without-the-panic · markdown: https://bookatu.com/blog/gdpr-without-the-panic.md > **The short version** > > - Your clients can download their data and request deletion from their own account, without writing to you. > - Deletion requests confirm themselves by email, wait out a 48 hour cooling-off, and usually complete on their own. > - Only requests that need a human decision reach you, each with a plain reason and a 30-day countdown. > - We only erase records we can provably link to the person asking. If we cannot prove it, we keep it and say so. > - You can download your whole business as one file, any day you like. If you run a salon in the EU, and in Germany more than anywhere, GDPR is not an abstract worry. Clients ask about their data. Some ask for a copy of it. Occasionally one asks you to delete it, and that is the moment most booking software leaves you alone with a legal obligation and a search box. This post is the plain-language tour of what Bookatu actually does for you. No badges and no absolutes, just how it works. #### The right of access, served instantly GDPR gives every client the right to a copy of the data you hold about them. In Bookatu they do not have to ask you for it. Signed into their account on your booking page, they tap Download my data and receive one readable file with their profile, appointments, invoices, payments and consents. It arrives instantly. There is no ticket to us and no task for you, and the right that most tools turn into paperwork becomes a button. ![A client's account on a salon booking page, opening the Privacy section and downloading a copy of their data as a single file](https://bookatu.com/blog/gdpr/download-my-data-poster.jpg) *01 · Right of access, self-service: a client downloads everything the salon holds about them as one file, straight from their account.* #### Deletion requests arrive on rails The right to erasure is the one owners worry about, so we built it as a lifecycle rather than an inbox. A client requests deletion from their own account and types their name to confirm it. Then they tap a link we email to the address on their file, so the person asking is provably the person who holds the account. After that comes a 48 hour cooling-off window with a cancel button for changed minds. Only then does anything run. Your dashboard shows every request from the moment it is raised, on the Privacy and security screen. Each one carries its status and a countdown, because the law expects a response within a month and you should not have to remember that yourself. Most requests complete on their own. The ones that reach you are held for a stated reason, such as an upcoming appointment or an unpaid balance, and once that is settled you review and complete them. Before anything is erased you see exactly what will be deleted and what will be kept in anonymized form, and you type the client's name to make it final. ![The deletion request queue on the Privacy and security screen of the salon dashboard, with statuses and the 30-day response countdown](https://bookatu.com/blog/gdpr/org-queue-poster.jpg) *02 · The deletion queue in your dashboard: status, the honest reason a request is waiting, and the 30-day response countdown.* #### We only erase what we can prove is theirs Here is a rule we treat as non-negotiable: Bookatu only erases records it can provably link to the person asking. An appointment tied to their account. An invoice with their client record behind it. What we never do is guess by name. If your books contain a walk-in called Anna M. and we cannot prove she is the Anna M. who asked, that record stays, and the completed request says so plainly instead of hiding it. That can sound less impressive than a promise to delete everything. It is also the only honest way to do it. Deleting by name-matching means one day erasing the wrong person's history, which is its own data-protection failure. When a request cannot be met in full, the right answer is a truthful report, not a quiet guess. The same honesty applies to money. Financial records are not deleted, because tax law requires you to keep them, usually for about seven years. Instead they are anonymized: the invoice survives for your accountant, and the person it pointed to does not. #### Your own data has an exit door too GDPR thinking should not stop at your clients. As the owner you can download your entire business from the same Privacy and security screen: profile and settings, services, products, team, clients, appointments, campaigns, posts and forms, in one file. Payment credentials and connected-account keys are never in it. You can run it once per day, and a confirmation email goes out each time, so an export can never happen without your knowledge. It is your business. A platform that believes that should hand you the whole copy without making you ask a human for permission. > **Good to know** > > The page at https://bookatu.com/en-nz/gdpr walks through both rights with the real screens, and our privacy policy describes the same flows in longer sentences. For the client's side of a deletion request told step by step, read the companion post, What happens when a client asks us to delete their data. #### What stays your responsibility None of this makes GDPR someone else's problem. We build the controls, but you decide what you collect, how long you keep it, and how you answer your clients. Bookatu is not a certification and this post is not legal advice. What the software can do is make the mechanical part run properly, the requests, the deadlines, the deletions themselves and the records of them, without you building a process from scratch. That is the part a booking platform should own, so we do. > Honesty is the feature. A salon that can say exactly what happens to a client's data has an answer most competitors do not. ### Let Claude book your clients: Bookatu's MCP server in practice Bookatu runs an MCP server, so an MCP-capable assistant like Claude can see your services, check live availability and create real bookings with a key you issue. Here is how that works, in plain words. The Bookatu team · 2026-07-23 · updated 2026-11-06 · Grow your business · https://bookatu.com/en-nz/blog/book-clients-with-claude-mcp · markdown: https://bookatu.com/blog/book-clients-with-claude-mcp.md > **Update, 6 November 2026** > > This post is about connecting your own AI assistant to your account with a key. For your clients' own AI assistants, read Can my clients book me from their own AI assistant? > **The short version** > > - Bookatu runs an MCP server, the open protocol that lets AI assistants such as Claude Desktop and Claude Code use real tools. > - You connect an assistant with an API key from your admin. The key is the permission, and you can revoke it at any moment. > - A connected agent can list your services, check live availability and create bookings. Deposits and your booking rules still apply. > - The full technical reference lives on the Bookatu developers page. This post is the plain-language walk-through. It is a Thursday afternoon and a regular emails: can she get her usual gel manicure some time Friday morning. Nothing about answering is hard. You open the calendar, find a slot, create the booking, type a reply. Four small steps, at a moment when you do not have a hand free. Now imagine typing one line to an assistant instead. Book Priya's usual gel manicure on Friday morning. The assistant checks your real availability, places the booking, and hands you a reference to send back. That is what Bookatu's MCP server makes possible. #### MCP in one paragraph MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant use tools a piece of software offers it, rather than guessing about your business from whatever it can find online. The software publishes a short list of actions, the assistant calls them, and the software stays in charge of what each action is allowed to do. Bookatu publishes its booking basics this way. Any assistant that speaks MCP can connect, and that includes Claude Desktop, Claude Code and a growing number of other agents. #### Connecting takes one key In your Bookatu admin you create an API key. It is shown to you exactly once, and Bookatu stores only a fingerprint of it rather than the key itself, so save it somewhere safe the way you would a password. You then point your assistant's MCP configuration at the Bookatu endpoint with that key, and you are connected. There is nothing to install on Bookatu's side and no separate agent account. The key identifies your business, so everything the agent sees is yours and only yours. Keys come in two strengths. A read-only key can look things up but can never book or change anything, which makes it the right choice for tools that only need to see your data. A read-write key can also create bookings. You can give a key an expiry date, and you can revoke it from the admin at any time, at which point it stops working immediately. #### What a connected agent can do The tool list an agent gets is short and deliberate: - See your services: names, durations and prices, so it knows what a gel manicure is and how long it takes. - Check availability: the real open slots for a service across the dates you ask about, up to 60 days at a time. - Create a booking: place a client into a slot with their name and contact details, and get back a booking reference. - Look up your clients: so it can use Priya's email and phone from your records instead of asking you to type them. - List upcoming appointments: so it can answer questions like what does Friday look like. There is no tool for deleting anything, and nothing that touches your billing, your account or anyone else's business. #### A realistic run-through Back to Priya. You type: find Priya's usual gel manicure a slot on Friday morning and book her in. The assistant lists your services and finds the gel manicure and its duration. It pulls Friday's open slots and sees a 10am free. It looks Priya up in your client list for her contact details, calls the booking tool, and comes back with a reference. The appointment is now in your calendar and on Priya's client record, exactly as if she had booked through your page. The part worth noticing is what it did not do. The availability it saw was your live availability, with your opening hours, existing appointments and buffer times already accounted for, so it could not offer a slot you cannot work. And if that 10am had been taken in the seconds between checking and booking, the booking is refused rather than double-booked, and the assistant simply picks another slot. #### Deposits still apply If the service takes a deposit, an agent cannot talk its way past your policy. The booking is created as pending, and the response includes a payment link to pass to the client, who pays the same way they would after booking on your page. Your no-show protection works the same no matter who, or what, placed the booking. > An agent gets a short list of things it may do. Everything else about your business is simply not on the table. #### You stay in control The key is the whole relationship. You created it, Bookatu records when it was last used so you can see what is connecting, and revoking it shuts the door on the spot. A booking made through MCP follows the same rules as one made on your page: real availability, your minimum notice, your deposit policy. Connected agents do not get a back door. They get the front door, with a key you cut and can take back. If you want the deeper detail, the endpoint, the tool descriptions and copy-paste examples are all on the Bookatu developers page. And if none of your tools speak MCP yet, nothing changes for you. Your booking page, reminders and calendar work exactly as before. The server is simply there for the day you want to type book Priya in on Friday somewhere other than your admin. ### Your next client might not use your website: when people ask ChatGPT (or any AI agent) to book People are starting to hand whole errands to AI assistants, and booking an appointment is a natural errand to hand over. What agent-ready means for a salon, and how Bookatu keeps you bookable when the one doing the booking is software. The Bookatu team · 2026-07-23 · updated 2026-11-06 · Grow your business · https://bookatu.com/en-nz/blog/when-clients-ask-chatgpt-to-book · markdown: https://bookatu.com/blog/when-clients-ask-chatgpt-to-book.md > **Update, 6 November 2026** > > What has changed for clients' own AI assistants is in Can my clients book me from their own AI assistant? > **The short version** > > - People increasingly ask AI assistants to run errands end to end, and booking an appointment is a natural errand to hand over. > - An assistant can only book you if a machine can read you: clear services, structured live availability and a real way to place the booking. > - Every Bookatu business already has that: a public booking API, machine-readable docs and an MCP server for agents that support it. > - One honest note up front: this piece is about where behaviour is heading. There is no Bookatu ChatGPT integration to announce, and we say so plainly below. Think about how new clients have found you over the years. Word of mouth, then the phone book, then Google, then an Instagram bio with a link in it. Every one of those shifts looked niche right up until it was normal. The next shift is already visible in how people use their phones: they are not just asking AI assistants questions, they are handing them errands. And an appointment is a classic errand. #### From answers to errands The first wave of AI assistants answered questions. The current wave is being built to finish tasks. People already ask ChatGPT and assistants like it to plan a trip or compare their options, and every major assistant maker is working on letting them complete the last step instead of stopping at advice. Booking an appointment sits near the front of that queue because it is small and mildly annoying, which is exactly the kind of job people love to delegate. Nobody can honestly tell you how fast this becomes everyday behaviour, and you should be suspicious of anyone quoting precise numbers about it. The direction, though, is not really in doubt. #### The business an agent cannot see An assistant running an errand takes the easiest path that finishes the job. If your services live in a photo, your availability lives in your head and booking happens over DM, an agent acting for a client has nowhere to stand. It cannot negotiate a DM thread on a stranger's behalf. Meanwhile the business down the road with published services and live, structured availability is a job an agent can finish in seconds. Nobody sends you a rejection letter when this happens. The errand just quietly completes somewhere else. #### What agent-ready actually means Strip away the buzzwords and agent-ready comes down to four things: - Services a machine can read: names, durations and prices as data, not just prose on a page. - Availability that is structured and live: actual open slots a program can query, not an invitation to message you. - A way to complete the booking: a public endpoint or an agreed protocol, so the agent can finish the job rather than handing its human a phone number. - Policies enforced by the booking flow itself: deposit and notice rules that apply to every booking, whoever or whatever placed it. #### How Bookatu keeps you bookable Every Bookatu business has this today, without switching anything on. Your booking page sits on top of a public API: software can read your business profile, your services, your team and your live availability, and place a booking through the same flow your page uses, deposit rules included. Those docs are published for machines as well as people. And for the newer breed of agent, Bookatu runs an MCP server, the open protocol assistants such as Claude Desktop use, so an MCP-capable agent can connect with a key you issue and work with your bookings directly. #### Where ChatGPT honestly fits Today there is no book-on-Bookatu button inside ChatGPT, and we would rather say that plainly than let you infer one. When precision matters, the accurate sentence is this: MCP-capable agents can already connect to Bookatu and book, and the public booking API is open to any software that can make a web request. ChatGPT belongs in this story as the clearest sign of where consumer behaviour is going, because an enormous audience is getting comfortable asking one interface to handle things. When assistants like it start completing bookings at scale, they will do it through exactly the kind of structured, public booking data Bookatu already exposes for your business. #### What you can do this week None of the preparation is exotic, because what agents need is what search engines and humans in a hurry already reward. - Fill in your profile properly: hours, address, and services with honest names, durations and prices. - Keep your availability true: if the calendar says 2pm is free, 2pm should really be free. - Set the policies you want enforced: your deposit and cancellation rules then hold for every booking, agent-made or not. > An assistant running an errand takes the easiest path. Structured availability is what makes you the easiest path. You do not need to bet on any particular assistant winning, and you should not have to rebuild your booking setup every time the way people search shifts. What you need is a booking page that is also, underneath, a machine-readable business. That is what Bookatu gives every business by default. However your next client shows up, in person, on your page or through an agent they trust, the answer is the same: yes, that slot is free, and it is now theirs. ### AI agents and your booking data: what a key lets in, and what it never touches Bookatu has two doors for AI: the assistant inside your admin and outside agents that connect with an API key. What each one can do, how keys and scoping work, and the lines nothing is allowed to cross. The Bookatu team · 2026-07-23 · updated 2026-11-06 · Grow your business · https://bookatu.com/en-nz/blog/ai-agents-and-your-booking-data · markdown: https://bookatu.com/blog/ai-agents-and-your-booking-data.md > **Update, 6 November 2026** > > Bookatu now also runs a public booking server for clients' own AI assistants. A client's assistant needs no key to use it, and an assistant using it never sees your client list. At a business that has switched it on, an assistant can find a free time and hold one, and the client confirms by email before anything is booked. Read Can my clients book me from their own AI assistant? > **The short version** > > - Bookatu has two separate doors for AI: an assistant inside your admin, and outside agents that connect through the API with a key you issue. > - The inside assistant works behind your login. It proposes changes, you confirm them, and nearly everything can be undone. > - Outside agents get exactly what their key allows, read-only or read-write, always scoped to your business alone. > - No key can delete your records, touch your plan or billing, change who can log in, or see another business on the platform. Letting AI anywhere near your client list deserves a clear-eyed look. Your booking data is your business: who your clients are and when they come in. So before you connect anything, it is worth understanding exactly how Bookatu lets software in, and where the walls are. There are two doors, and they are deliberately different. #### Inside: the assistant behind your login The first door is the assistant built into the Bookatu admin. It lives behind your login, works in plain words, and follows one rule everywhere: it proposes, you confirm. Ask it to book a client or move an appointment and it shows you exactly what it is about to do before anything happens. Confirm and it goes through, and nearly every change can be undone in a tap afterwards. It is for you and your team, not the public, and it is the right tool for running your day, the small changes that pile up across a shift. #### Outside: the key is the contract The second door is for software that lives outside the admin: a tool you already use, a custom integration, an MCP assistant like Claude Desktop. All of it comes in through the API, and the unit of trust there is the API key. A few properties do most of the work: - You issue it. Keys are created in your admin, by you, and shown exactly once. Bookatu stores only a fingerprint, never the key itself. - It has a strength. A read-only key can look but not touch. Creating a booking takes a read-write key. Give each connection the least it needs. - It leaves a trail. Bookatu records when each key was last used, so you can see what is actually connecting. - It dies on command. Revoke a key and it stops authenticating immediately. You can also set an expiry when you create it. #### Scoped to your business, always Every key belongs to exactly one business. Whatever an agent asks for, the request is resolved against your business and nothing else. A key issued for one business can never read another's data, and there is no request an outside agent can make that crosses that line. Even the webhook notifications Bookatu can send to your other tools are deliberately lean: they carry no client contact details, and software that wants the full record has to come back through the API with your key. #### What a key-holding agent can and cannot do With a read-only key, an agent can read your services and prices, your live availability, your client list and your upcoming appointments. That is enough for a reporting dashboard or an assistant that answers what does my week look like. With a read-write key, it can also act: create a booking, or cancel one through the API. Bookings it creates follow the same rules as your booking page: real availability, your minimum notice and your deposit policy. A deposit-taking service booked by an agent comes back pending with a payment link for the client, not confirmed for free. And here is the list that matters most, the things no key unlocks because they do not exist as agent-facing capabilities at all: deleting your clients or your history, changing your plan or billing, managing logins or staff permissions, and reaching any other business on the platform. There is no super-key to leak. Those capabilities simply are not on the menu. > Give a reporting tool a read-only key and it can look all day without being able to change a thing. #### Which door for which job Use the inside assistant when you are the one driving: moving a three o'clock while your hands are full, or blocking out Friday afternoon. It proposes, you confirm, you can undo. Use a key when software is driving: your own dashboard pulling appointments, or an MCP assistant on your laptop booking clients in. Start every new connection with a read-only key, and upgrade it to read-write only when the tool genuinely needs to book. The point of all this is not paranoia. It is that saying yes to useful AI is much easier when the worst case is small and the exits are clearly marked. Connect an agent, watch what it does, and if you ever stop trusting it, revoke the key and it is gone. The full technical detail, endpoints, key scopes and examples, is on the Bookatu developers page, and keys are issued from your admin dashboard. Your data stays yours. An agent just gets a key, and only to the rooms you chose. ### Run your salon from a chat: book, reschedule and block time by typing The Bookatu admin has an assistant you can talk to in plain words. Type what you want and it books, reschedules or blocks time for you, shows you the change first, and never touches your calendar until you confirm. The Bookatu team · 2026-07-17 · Grow your business · https://bookatu.com/en-nz/blog/run-your-salon-from-a-chat · markdown: https://bookatu.com/blog/run-your-salon-from-a-chat.md > **The short version** > > - Open the assistant, type what you want in plain words, and it books, reschedules or blocks time for you. > - It always shows you the change first. Nothing lands in your calendar until you confirm it. > - It reads your real availability, so it will not offer a slot you cannot work or double-book a chair. > - Nearly every change can be undone, and it runs inside the monthly AI allowance shown on your usage page. It is a Tuesday and you are halfway through a colour. Your phone buzzes on the counter. A regular wants to move her Thursday appointment to Friday, and while you are at it you remember you need to block Friday afternoon for a dentist trip. None of that is hard. It is just a few small trips into the admin, and right now your hands are full. So it waits, and by the time you are free you have half-forgotten the details. #### Type it the way you would say it The Bookatu admin has an assistant you can talk to in plain words. You do not learn a command language or hunt through menus. You type the thing you would have said to a receptionist. Book Priya in for a gel manicure on Thursday at two. Move my three o'clock to Friday morning. Block Friday afternoon off. The assistant works out which appointment, which service and which slot you mean, and gets it ready. #### It shows you the change before it makes it This is the part that makes it safe to use while you are distracted. The assistant does not just go ahead. It proposes the change and shows you exactly what it is about to do: the client, the service, the day and the time. You read it, and if it is right you confirm. If it read you wrong, you correct it or throw it away. Nothing touches your calendar until you say yes. The model suggests, and you are the one who decides. Because it reads your real availability, the slot it offers is a slot you can actually work. It will not book two clients into the same chair at once, and it will not offer a time you have already blocked. If what you asked for does not fit, it tells you instead of forcing it. #### The jobs it saves you the most on - Booking. Give it the client, the service and roughly when, and it finds the slot and sets up the appointment for you to confirm. - Rescheduling. Tell it which appointment to move and where to, and it shifts it and frees the old slot back up. - Blocking time. Ask it to hold an afternoon, a morning or a whole day, and that time stops being bookable until you open it again. These are the small interruptions that pile up across a shift. On their own each takes a minute. Added up across a busy week they are the reason you are still doing admin after closing. > The assistant is not there to run your salon for you. It is there so the ten small changes a day stop waiting until you are too tired to make them. #### It stays on your side of the counter This assistant is for you and your team, not your clients. It lives in the admin, behind your login, and it only does the jobs you have given it. It is not answering the public or improvising your policies at a stranger. It is a faster way for the person who runs the business to run the business. And if it ever does something you did not mean, there is an Undo. One tap puts things back the way they were. That safety net is what lets you use it without hovering over every change. #### What it costs to try The assistant runs inside the monthly AI allowance that comes with your plan, and your usage page shows how much of it you have used. Nothing is charged silently. If running your admin by typing a sentence sounds better than tapping through screens with your hands full, you can start free and try it on your own calendar. The next time your phone buzzes mid-service, you can deal with it in one line and get back to the chair. ### Receive a whole delivery by photographing the supplier invoice A box arrives with a paper invoice. Photograph it, send it to the assistant, and it reads the lines, matches them to the stock you already carry, and proposes the receipt for you to confirm. Sold something? Tell it, and the count drops. The Bookatu team · 2026-07-17 · Grow your business · https://bookatu.com/en-nz/blog/receive-stock-from-a-photo-of-the-invoice · markdown: https://bookatu.com/blog/receive-stock-from-a-photo-of-the-invoice.md > **The short version** > > - A delivery arrives with a paper invoice. Photograph it, send the photo to the assistant, and it reads the lines for you. > - It matches each line to a product you already stock and proposes adding the new quantities to your counts. > - You check the proposed receipt and confirm. Your stock levels do not move until you do. > - Sold something off the shelf? Tell the assistant and it drops that item's count, with an Undo if you tap wrong. The box from your supplier lands between two clients. Inside is the usual paper invoice, a dozen lines of product codes and quantities. The honest way to keep your stock accurate is to sit down and add each line to your counts. The real way, on a busy day, is to promise yourself you will do it later, lose the invoice under the counter, and let your numbers drift until a stocktake sets them straight. #### Photograph the invoice, let the assistant read it There is a shorter path. Open the assistant in your admin, take a photo of the invoice or packing slip, and send it. It reads the lines, the product names and the quantities that came in. You do not type any of it. A minute of retyping per delivery, gone. #### It receives into the stock you already have The clever part is not reading the page. It is matching what it read to your actual shelf. For each line, the assistant looks for the product you already stock and lines it up, rather than inventing a fresh product that happens to share a name. So a delivery of the argan oil you have sold for a year tops up the argan oil you already have, instead of creating a second one next to it. Anything genuinely new, a line you have never carried, it flags for you to add rather than guessing. This is what keeps a stock list clean over time. Duplicates are how inventory quietly becomes useless: two entries for the same bottle, each holding half the real count. By resolving every line to something that already exists, the assistant keeps your list honest. #### You confirm before anything moves As with everything the assistant does, it proposes the receipt and waits. You see the list it is about to apply, this product and this many in, laid out against the box in front of you. Fix a number if the photo caught it wrong, then confirm. Your counts do not change until you do. If you confirm and then spot a mistake, Undo reverses the whole receipt in one tap. > The point is not that a machine read your invoice. It is that your stock is right again by the time the kettle boils. #### Selling is just as quick The same assistant handles the other direction. When you sell something off the shelf that did not go through the point of sale as a normal sale, you can just say so. Sold two of the argan oil. It proposes dropping that product's count by two, you confirm, and your shelf number matches your shelf again. Small corrections like this are the ones that never get done on paper, and they are the ones that make a stocktake painful. Doing them in a sentence, as they happen, is how the count stays true. #### Stock that keeps itself honest Accurate stock is not glamorous, but it is the difference between reordering on time and finding out you are out of someone's favourite mid-appointment. Letting the assistant read your deliveries and take your quick corrections means the count stays close to reality without a clipboard evening. It runs inside the AI allowance on your plan, shown on your usage page, with nothing charged silently. If a shelf that counts itself sounds useful, you can start free and try it with your next delivery. ### Set up a new service, its consent form and a deposit in one go A new treatment usually means three separate trips into settings: the service, the consent form, the deposit. Describe it once and the assistant lays all three out as a plan for you to check, with the pieces already wired together. The Bookatu team · 2026-07-17 · Grow your business · https://bookatu.com/en-nz/blog/set-up-a-service-consent-form-and-deposit-in-one-go · markdown: https://bookatu.com/blog/set-up-a-service-consent-form-and-deposit-in-one-go.md > **The short version** > > - Adding a treatment usually means three separate jobs: the service, its consent form, and a deposit rule. > - Tell the assistant once, in a sentence, and it lays out all three as a plan for you to check. > - The consent form comes as a draft you read before any client sees it, and the deposit is set on the service it just built. > - Approve the plan and it all goes live together, or change any step first. Undo is always there. You have decided to offer a new treatment. Something that needs a signed consent form and a deposit to hold the slot, because the products are expensive and a no-show hurts. In most booking software that is three trips into three different corners of the settings. Build the service. Go to forms and build the consent form. Go to booking rules and set the deposit. Each is simple on its own. Together they are the reason the new treatment sits on your to-do list for a fortnight. #### One sentence, one plan The assistant in your Bookatu admin can take the whole thing at once. Tell it what you want in plain words. Add a microneedling service, 60 minutes, $180, it needs a consent form, and take a 30% deposit to book. It does not fire off three disconnected changes. It lays out a plan, a short numbered list of what it is about to do, so you can see the shape of it before anything happens. #### The steps thread together What makes this more than three shortcuts is that the steps know about each other. The consent form it drafts is attached to the very service it just proposed. The deposit rule applies to that same service. You are not left to wire the pieces together afterwards. The assistant threads the output of one step into the next, so what you approve is a treatment that is ready to book, form and deposit included. The consent form arrives as a draft, not a finished thing pushed live behind your back. This is the same care Bookatu takes when you import a paper consent form: the questions, the acknowledgements and the place to sign are laid out for you to read and adjust before a single client sees them. You know your treatment and its risks better than any model does. The draft saves you the blank page, and you keep the final say on every line. #### You approve the whole thing, or any part of it Nothing goes live until you confirm. You can accept the plan as it stands, or change a step first. Make the deposit 20% instead of 30%. Add a question to the form. Trim the duration to 45 minutes. When it looks right, approve it and the service, its form and its deposit all take effect together. If you change your mind after, Undo rolls it back. > A new treatment should take one clear decision, not an afternoon of tab-hopping through settings you touch twice a year. #### Why do it in one go The pieces of a bookable treatment are easy to leave half-done. The service goes up, but the consent form waits, so the first client signs nothing. Or the form exists but no deposit is set, so the expensive no-show you were guarding against walks anyway. Setting them together, from one instruction, is how the treatment goes live actually finished, with the protection you meant it to have from the very first booking. #### Ready when you are This is the assistant doing what it is good at, the multi-step admin that is simple in each part and tiring as a set. It proposes, you confirm, and you can undo. It runs inside the AI allowance on your plan, shown on your usage page, with nothing charged silently. If you have a treatment you have been meaning to add properly, you can start free and set it up, form and deposit and all, in about the time it takes to describe it. ### Undo anything the assistant does, and never end up with duplicate clients Two fair worries about letting software make changes: that it does the wrong thing, and that it quietly messes up your client list. The assistant is built around both. Nearly every change undoes in a tap, and it picks the client you meant instead of inventing a new one. The Bookatu team · 2026-07-17 · Grow your business · https://bookatu.com/en-nz/blog/undo-anything-and-never-get-duplicate-clients · markdown: https://bookatu.com/blog/undo-anything-and-never-get-duplicate-clients.md > **The short version** > > - Almost every change the assistant makes can be undone in one tap, and the few that cannot are easy to adjust in Products, so trying it is close to risk-free. > - When you name a client, it finds the ones you already have and asks you to pick, instead of creating a new record. > - That pick-don't-type habit is what stops your client list filling up with two half-empty entries for the same person. > - It proposes, you confirm, and if a change was wrong, Undo puts things back the way they were. There are two fair worries about letting software make changes to your business. The first is that it does the wrong thing and you are left cleaning up. The second is quieter and worse over time: that it slowly makes a mess of your client list, a second Sarah here, a duplicate product there, until the list you rely on cannot be trusted. The Bookatu assistant is built around both of those worries rather than despite them. #### Undo is the whole point, not an afterthought Almost every change the assistant makes can be undone, and never with a support ticket. You tap Undo and the change is reversed, back to exactly where you were. The handful that do not undo in one tap, like receiving new stock, you can still adjust on the Products screen in a moment. That safety net changes how it feels to use. You are not weighing up whether it is worth the risk of letting it try. If the result is wrong, you put it back and move on. Trying costs you a tap. It works this way because the assistant proposes changes and you confirm them, and every confirmed change is remembered as its own step. So Undo is not a guess at reversing things. It knows precisely what it did and can take it back. #### Pick the client you meant, do not type a new one Here is where most tools quietly create the mess. You go to book Sarah, you type Sarah, and the software helpfully makes a booking against a brand new Sarah with no history, no email and no past visits. Now you have two Sarahs, and next time you are not sure which one is the real one. The assistant does the opposite. When you mention a client, it looks at the clients you already have and shows you the matches to choose from. You pick the right Sarah from the ones on file. It does not conjure a new record just because you typed a name. Only when there genuinely is no match does it offer to add someone new, and even then it shows you first. #### The same habit protects your catalogue This pick-don't-type approach runs through everything, not just clients. Ask it to add stock to a product and it resolves to the product you already carry rather than a near-duplicate with a slightly different spelling. Book a service and it uses the one on your menu, not a new one that looks almost the same. The rule underneath is simple. Match what exists before making anything new, and show you the match before committing to it. > A clean client list is not a nice-to-have. It is the asset your whole business sits on, and it is worth guarding one record at a time. #### Why duplicates cost more than they look A duplicate client is not just untidy. It splits a person's history in two, so their visit count and their spend sit on separate records, and neither one tells the full story. Loyalty gets miscounted. A win-back message goes to the empty copy. The regular you have seen twenty times looks like a stranger. Every duplicate you avoid is a client whose history stays whole, which is exactly what you need when you want to look after them well. #### Safe to lean on Between an Undo on nearly every change and a habit of picking real records instead of inventing new ones, the assistant is something you can lean on without watching it like a hawk. It proposes, you confirm, and you can always step back. It runs inside the AI allowance on your plan, shown on your usage page, with nothing charged silently. If an admin helper that keeps your client list clean sounds like your kind of tool, you can start free and see how it handles your own. ### AI for your salon: the end of the blank description box Every description box in Bookatu now has a Write it for me button. It drafts the wording in your voice and keeps your real prices, with an Undo one click away. The Bookatu team · 2026-07-16 · Grow your business · https://bookatu.com/en-nz/blog/ai-writing-help-for-your-salon · markdown: https://bookatu.com/blog/ai-writing-help-for-your-salon.md > **The short version** > > - Every description box in the Bookatu admin now has a small Write it for me button, from service descriptions to the email sign-off. > - It writes the way you would talk to a client, and it keeps the facts you typed, so a $55 price stays $55. > - There is always an Undo, so trying it costs you nothing but a click. > - It runs inside the monthly AI allowance that comes with your plan, shown on your usage page. Nothing is charged silently. You know your best facial better than anyone. You can talk about it for ten minutes with a client in the chair. Then you open the admin, click into the description box, and nothing comes. The cursor blinks. You type a sentence and delete it. The box can stay empty for now, you decide. Half the empty description boxes in booking software are not empty because the owner has nothing to say. They are empty because writing about your own work is strangely hard. #### A small button on every box Every description box in the Bookatu admin now carries a small button. On an empty box it says Write it for me. On a box that already has text it says Polish my wording. Click it and a draft appears right where you would have typed. Keep it or edit it, and if you liked your version better, hit Undo and you are back exactly where you started. It is the same button everywhere, so once you have used it on one screen you know it on all of them: - Service and product descriptions, and the tagline at the top of your booking page. - Staff bios and the welcome text on your intake forms. - Package and membership descriptions, plus the note that goes out with a gift card. - Newsletter subject lines and the messages that win back lapsed clients. - Birthday messages and the sign-off at the bottom of your emails. #### It keeps your facts and drops the fluff The draft is written the way you would talk to a client, not the way software talks. It keeps the concrete details you entered, so a $55 price stays $55 and a 45-minute service stays 45 minutes. Names stay spelled the way you spelled them. And it deliberately avoids the tells of machine writing, the breathless adjectives and the copy that could belong to any business anywhere. If a draft would embarrass you out loud, it has failed at its one job. #### What that looks like in practice The examples below are invented, but they show the kind of lift you can expect. A nail salon service. You typed: Gel manicure, 45 min, $55. The draft: A gel manicure that keeps its shine for weeks. 45 minutes, $55. You walk out with nails you can forget about. A spa package. You typed: 3 x 60 min massage, $240. The draft: Three hour-long massages for $240, booked whenever suits you. Pay once and your next two visits are already sorted. A trainer bio. You typed: Sam, 10 years, strength and conditioning. The draft: Sam has spent ten years helping ordinary people get strong. Strength and conditioning is the day job. Making it fit around your week is the point. None of these drafts are precious. Change a word here and there, or undo the whole thing. What matters is that you are editing instead of staring at a cursor, and editing is the easy part. #### Polish what you already wrote The button is not only for empty boxes. If a description you wrote years ago has gone stale, or a win-back message reads a little stiff, Polish my wording keeps your meaning and tidies the sentences around it. It feels less like handing the writing over and more like having someone read it back to you. It is also the gentlest way to try the feature. Pick the one description you never liked and polish it. If the old version wins, Undo puts it back, and you have lost nothing but a minute. That matters more than it sounds. A booking page where every service reads clearly is a page where clients stop guessing what they are buying, and clients who are not guessing book with less back and forth. > Nobody opened a salon because they love writing descriptions. You opened it to do the work the descriptions describe. #### What it costs The writing help runs inside the monthly AI allowance that comes with your plan. Your usage page shows that allowance and how much of it you have used, alongside everything else on your account, so there are no surprises at the end of the month. Nothing is charged silently. Next time you meet a blank box, press the button. Read the draft out loud. If it sounds like you on a good day, keep it. If it does not, undo it and press the button again, or just fix the two words that feel off. Either way the box gets filled, and your booking page starts sounding like the person clients actually meet. ### Digital consent forms from the PDF you already use Waxing, peels, lash and microneedling all need signed consent. Upload the intake PDF you already use and Bookatu builds the digital form for you to check. The Bookatu team · 2026-07-16 · Grow your business · https://bookatu.com/en-nz/blog/digital-consent-forms-one-upload · markdown: https://bookatu.com/blog/digital-consent-forms-one-upload.md > **The short version** > > - Upload the consent or intake PDF you already use. Bookatu reads it and builds the digital version as a draft for you to check. > - A date of birth becomes a calendar picker and every consent statement becomes a box the client must tick. One signature field lands near the end. > - An optional clean-up pass fixes the labels the scan got wrong, so the draft needs less tidying before it goes live. > - Attach the finished form to the services that need it. Clients fill it in and draw their signature on their phone before the visit, and the signed answers are kept with the client in your admin. Walk into the back room of a beauty or skin clinic and somewhere there is a folder of forms. A waxing consent. A peel consent with the longer health section. One for lash lifts, another for microneedling, plus the intake sheet every new client fills in. Each one started as a Word document and gets printed whenever the tray runs low. The signed copies live in a drawer. Most of those forms are good. They have been tuned over years of real appointments, and the questions earn their place. What kept them on paper was the cost of moving them: rebuilding every field by hand in some form builder, one evening per form. Multiply that by the whole folder and the paper wins. Bookatu shortens the job to one upload per form. #### What one upload gets you Open the Forms page and upload the file you already hand out at reception. It needs to be a text based PDF, the kind you get when you export from Word or Google Docs, rather than a photo of a printed page. Bookatu reads the text and builds a draft of the digital form, part by part. - Questions become fields the client types an answer into. - Tick boxes stay tick boxes, and a yes or no question becomes a simple choice between the two. - A date of birth turns into a calendar picker, so nobody has to guess which date format you wanted. - Consent statements, the lines a client signs against, become boxes that must be ticked before the form will go through. - A signature field lands near the end, where people expect to sign. #### A clean-up pass for the labels Reading a PDF is never perfect. A label sometimes comes out with the line break in the wrong place, or a heading arrives in capitals that were only ever a font choice. There is an optional clean-up pass that tidies those labels for you, so the draft reads the way the paper form did. You still check everything yourself. The pass just means the checking is faster. #### You review it, then attach it to the right services Nothing goes live until you have read it. Open the draft, rename anything the reader got wrong, mark the fields that matter as required, and remove the question you stopped asking years ago. It is your form, arriving as a draft instead of a blank page. Then tick the services that need it. The peel consent goes on the peel, the lash form goes on the lash services, and a client booking a simple file and polish is never asked for either. Each treatment carries its own paperwork, and only its own. #### Filled in and signed on their phone When a client books a service with a form attached, they are asked to complete it before the visit. Their details fill themselves in from their client record where that makes sense, so they are not retyping a name and phone number you already have. They work down the questions, tick the consent lines, then draw their signature in a box with a finger, the same way they would sign at a card machine. It happens at home the day before, not on a clipboard in your reception. > A form that took an afternoon to write should not take another afternoon to move. #### The signed answers stay with the client Every submitted form is kept with the client in your admin. Before a repeat peel you can open their record and see what they told you last time, with the drawn signature and the time it went in. If anyone ever asks whether a client agreed to something, the answer is two taps away instead of somewhere in a filing cabinet. #### Editing it later is not a project Forms change. A new product means a new allergy question, or your insurer asks you to add a line. You can edit any form whenever you like: a palette of field types sits beside the editor, and you can insert a new field at any point in the form, not just at the bottom. The new allergy question goes exactly where it belongs, next to the others. If your reception folder holds five forms, this is an afternoon of uploads, not a week of rebuilding. Upload one, read the draft while the kettle boils, attach it, and move on to the next. The paper pile took years to grow. It does not take long to retire. ### AI booking software: what it should actually mean AI in booking software should hand you back an evening, not put on a show. Where Bookatu uses AI, and why every feature still works with it switched off. The Bookatu team · 2026-07-16 · Grow your business · https://bookatu.com/en-nz/blog/what-ai-booking-software-should-mean · markdown: https://bookatu.com/blog/what-ai-booking-software-should-mean.md > **The short version** > > - AI earns its place in booking software by saving you minutes on chores you already do, like reading a PDF form or cleaning up a client spreadsheet. > - The AI drafts, you approve. A description or a form built by AI is a suggestion until you have read it and said yes. > - Every AI feature in Bookatu has a plain path underneath, so imports and forms keep working with the AI switched off. > - Usage is metered and visible on your billing usage page, with no hidden fees, and you can bring your own AI key if you prefer. Somewhere in the last two years, every piece of software you pay for grew a sparkle button. Booking software caught it too, and now the ads promise an AI that runs your whole front desk. If you own a salon, a spa, a studio or a clinic, you have earned the right to be skeptical. A lot of what gets sold as AI-first is a chat window bolted onto the same old product. #### One test for any AI feature Here is the test we use at Bookatu before an AI feature ships: does it give an owner their evening back. Not a wow moment in a demo. An actual evening, the one you were going to spend re-typing a consent form into a form builder, or rewriting a service description until it stopped sounding stiff. AI costs real money to run, so it should be spent where the time is. If a feature cannot point at the minutes it saves, it does not go in. #### Where AI belongs: the paperwork Bookatu uses AI on the chores that quietly eat hours after closing. - Reading your paper consent form. Upload the PDF you already hand to clients and Bookatu builds the digital version as a draft: the questions, the tick boxes, the acknowledgements and the place to sign. You review every field before a client ever sees it. - Writing descriptions that sound like you. Tell it roughly what the service is and it drafts the wording. You edit until it reads like something you would say out loud, then you save it. Nothing publishes itself. - Cleaning up imported spreadsheets. Client lists arrive with every column name imaginable, and the smart pass lines your headings up with the right fields so fewer columns get dropped and fewer rows get skipped. Notice what these have in common. The AI works on your side of the counter, on admin that was always yours to do. It reads, it suggests, and then it waits for you. The AI drafts, you approve. #### Where AI should stay out of the way A lot of AI marketing runs the other direction. The pitch is an AI receptionist for your salon that answers the phone and handles the relationship while you work. Some of that is genuinely useful, like catching the 9pm enquiry that would otherwise drift to the salon down the road. But be honest about what brings your regulars back. They return because you remembered their kid's name and how strong they like their coffee, and no model does that for you. So whatever tool you are weighing up, hold it to the same rule: the AI can draft, and you approve. A suggested reply you can read and edit before it goes out is help. A machine improvising your cancellation policy at a stranger is a liability with your name on it. #### Every feature needs a plain path There is a quieter promise underneath all of this. Every AI feature in Bookatu has a non-AI path that does the same job. The PDF import falls back to a built-in reader, and the spreadsheet import still matches columns without the smart pass; you just check a few more of them yourself. Descriptions can always be typed the ordinary way. This matters more than it sounds. A feature that only works when the AI works is a feature that fails on the day you are busiest. It also means AI is never a paywall in Bookatu: if the smart help runs out partway through your setup, the setup finishes anyway. #### You can see the meter AI usage in Bookatu is metered, and the meter is yours to look at. Your billing usage page shows what the AI features have used, right alongside the rest of your account, with no hidden fees. You see an allowance running low before it runs out, rather than discovering it on an invoice. And if you would rather run things on your own terms, you can bring your own AI key and Bookatu will use that instead. It is your business. The tools should show their working. > The honest measure of AI in booking software is whether the owner got an evening back. So when the next demo shows you a sparkle button, ask the boring questions: what chore does this remove, and what happens when I switch it off. Then ask to see the meter. Software with good answers will not mind you asking. That is what AI-first should mean. The AI does the jobs you never wanted, quietly, and the front of house stays yours. ### Client intake forms your clients can finish on a phone Most intake forms are built for a desk and filled in on a phone. Here is how a phone-first form gets finished in a few minutes, signature and all. The Bookatu team · 2026-07-16 · Grow your business · https://bookatu.com/en-nz/blog/intake-forms-clients-can-finish-on-a-phone · markdown: https://bookatu.com/blog/intake-forms-clients-can-finish-on-a-phone.md > **The short version** > > - Bookatu forms show one question at a time, with a progress bar and an honest time estimate up front. > - Birthdays and dates come from a calendar picker, and choices are big cards you tap. > - Clients sign with a finger, right in the form, and required consent statements are plain tick boxes. > - If a submit goes wrong, nothing typed is lost. The form keeps every answer and points at the exact field to fix. Somewhere right now a client is sitting in a car park, pinching and zooming a consent form that was designed for a sheet of A4. The fields are the size of grains of rice. The keyboard covers half the page. She gets to question fourteen, the page reloads, and everything she typed is gone. She gives up and decides she will sort it at the desk. So the paperwork lands on you. The client arrives, someone hands over a clipboard, and the first ten minutes of the appointment go to admin instead of the treatment. Multiply that by a full day of bookings and it is a real cost, in time and in mood. #### Why forms die on a phone Most intake forms were never designed for the device they are actually filled in on. They are a desktop page, or a PDF of the paper version, squeezed onto a screen the size of a hand. The text needs zooming. The date field wants a format nobody can guess. And the whole thing is presented at once, forty questions stacked in one long scroll, which looks like homework. So people do the sensible thing and put it off. They will do it later on the laptop, they tell themselves, and later never comes. Or they push through to the end, hit submit, something times out, and every answer disappears. Nobody fills the same form in twice. That is the moment your completion rate quietly dies. #### One question at a time Bookatu intake and consent forms take the opposite approach. The client sees one question block at a time, with a progress bar so they always know how far along they are. Answer, tap next, and the following question slides in. It feels closer to replying to messages than to filling in paperwork, and that feeling is what keeps thumbs moving. The form is honest about the cost up front, too. Before the first question, the client sees an estimate of how long the whole thing takes. Typical forms come in at a few minutes, and saying so at the start is often the difference between started now and saved for never. #### Built for thumbs The parts of a form that usually hurt on a phone each get their own treatment. A birthday is picked from a calendar, so nobody has to guess whether you want the day or the month first. Multiple-choice questions are big cards you tap, sized for a thumb rather than a cursor. Required consent statements are written out in full next to a plain tick box, so a client can read exactly what they are agreeing to and tick it without zooming. And the signature is a real signature. The client draws it with a finger in a signature box, the same way they would sign a courier's handheld. No printing and scanning, and no typing a name into a box and calling it a signature. When the form reaches you, the signed waiver is there with the signature on it. > A form finished on the sofa the night before means a client who walks in relaxed and an appointment that starts on time. #### A mistake never wipes the form Things go wrong on phones. A signal drops in a lift. A required box gets missed three screens back. On most forms this is where the client loses everything and gives up. On a Bookatu form, nothing typed is lost. Every answer is kept, and the form points at the exact field that needs fixing, so a slip costs one correction instead of a restart. For the client it is a small thing. For your completion rate it is the whole game. #### The paperwork arrives done Attach a form to a service and every client who books that service gets it to fill in before they arrive. Details Bookatu already has from the booking, like the name and email, come pre-filled, so nobody types their own name twice. The client does the whole thing from the sofa the night before and taps submit, signature and all. For you, the change shows up at the front desk. The signed waiver is sitting in the client's record before they walk through the door. The first ten minutes of the appointment go to the appointment. And the person who arrives is one who spent a few quiet minutes on their phone last night, rather than one who just wrestled a clipboard in your waiting area. None of this is complicated. It is a form that respects the device it is filled in on and the person filling it. Get those two things right and the completion problem mostly solves itself. Clients finish the form because finishing is easy, and your day starts with the work instead of the admin. ### Import your forms and client list without the typing Moving to a new booking system usually means re-typing everything. Bookatu reads your existing consent form and your client spreadsheet for you, and it stays free even when the smart help runs out. The Bookatu team · 2026-07-15 · Grow your business · https://bookatu.com/en-nz/blog/import-your-forms-and-client-list-without-the-typing · markdown: https://bookatu.com/blog/import-your-forms-and-client-list-without-the-typing.md > **The short version** > > - Upload the consent form you already use as a PDF and Bookatu builds the digital version for you to check. > - Import your client list from any spreadsheet, even when the column names do not match ours. > - When smart help is switched on it cleans up what the reader gets wrong and matches your columns for you. > - It stays free. Each account gets a monthly allowance of smart help, and when that runs out the built-in reader takes over, so importing never stops or asks you to pay. The worst part of moving to new software is not learning it. It is the evening you lose re-typing the things you already had. Your consent form. Your client list. The intake questions you wrote years ago. Bookatu was built to take that evening back. #### Your paper form, read for you If you already hand clients a consent or intake form, you do not need to rebuild it by hand. Upload it as a PDF and Bookatu reads the text and lays out the digital version: the questions, the tick boxes, the places to sign. You get a draft to review, so you stay in control of every field before it goes live. ![Uploading a consent form PDF, with a panel showing the form being read and built](https://bookatu.com/help/forms-pdf-import.png) *Choose your PDF and Bookatu reads it and builds the form. You review the draft before anyone fills it in.* When the smart reader is on for your account, it does a second pass to fix what a plain scan gets wrong: a title that came out in scattered capitals, a question that ran into the next line, a tick box it nearly missed. You still review it. It just gives you a cleaner starting point. #### Your spreadsheet, matched for you Client lists never come in a tidy shape. One export calls it Full Name, another calls it Client, a third splits it into first and last. Bookatu matches your headings to the right fields for you, so a column called Mobile lands in the phone field and Email Address lands in email. Fewer dropped columns, fewer rows skipped, less cleaning up by hand. - Export your clients from your old system or your own spreadsheet. - Drop the file in. Bookatu lines the columns up with the right fields. - Rows that are missing a name are counted and skipped so nothing half-formed sneaks in. #### Free, and it stays free Smart help costs money to run, so plenty of tools put it behind an upgrade. We did the opposite. Every account gets a monthly allowance of smart help at no charge. When the allowance is used up, Bookatu falls back to the built-in reader that needs no allowance at all, so your import still works. The smart pass makes it more accurate. It is never the thing standing between you and getting set up. > The best software setup is the one you finish in an afternoon, not the one you dread for a week. Bring your forms and your clients as they are. Bookatu does the reading, you do the checking, and you keep your evening. ### Stop cropping heads off: focal points for photographers Your best frame is only as good as its crop. Set a focal point on each photo once, and every thumbnail, tile and hero on your booking page keeps the face, not the ceiling. A visual tour of the photographer storefront, with real screenshots. The Bookatu team · 2026-07-14 · Grow your business · https://bookatu.com/en-nz/blog/stop-cropping-heads-off-your-photos · markdown: https://bookatu.com/blog/stop-cropping-heads-off-your-photos.md > **The short version** > > - Your booking page opens with a photo mosaic built from your own gallery, so it reads like a portfolio, not a form. > - Every photo carries a focal point: drag a dot onto the part that matters and every crop keeps it in frame. > - One setting drives every crop, from the hero mosaic to the smallest thumbnail. > - Captions, ordering and removal all live on one gallery screen in your admin. Photographers get hit by a bug nobody else notices. Software loves neat rectangles, and photos refuse to be neat. The moment a layout crops your image into a wide tile or a square thumbnail, the default behaviour is to keep the centre. The centre is very often not where the person is. That is how a portfolio site ends up advertising a wedding photographer with a headless bride. #### A booking page that behaves like a portfolio On Bookatu, a photographer's public page leads with the work. The top of the page is a mosaic built from your gallery, with your name and city over the lead image and the rest arranged around it. Clients can open the whole set before they ever look at a price. #### The dot that saves the crop Every photo in your gallery has a draggable dot. Put it on the part that matters, a face, joined hands, the detail you want sold, and that point becomes the anchor for every crop of that image anywhere on the page. Wide hero, square tile, tiny thumbnail: the layout changes, the anchor does not. ![The gallery admin screen showing photos with draggable focal point dots and captions](https://bookatu.com/blog/shots/photographer-gallery-admin.png) *The gallery manager: a focal dot on each photo, a caption, and ordering controls. Set it once per image.* It is a ten-second habit when you upload. Drag the dot, write a short caption if the story needs one, done. From then on the software does the remembering, and the software never gets tired and centre-crops your newborn shot into a photo of a blanket. #### Small craft, real bookings - Lead with range: a wedding, a portrait, a brand shoot. The mosaic is your first conversation about what you do. - Put the focal dot on eyes for portraits, on hands for details, on the subject line for editorial work. - Captions double as quiet SEO: place names and session types read naturally to clients and crawlers alike. - Reorder seasonally. Spring minis up front in August, weddings up front in wedding season. > Clients do not book the photographer with the best work. They book the photographer whose work they saw properly. None of this needs a separate website, a page builder or a plugin. Upload, drag the dot, and the same page that shows your work takes the booking and the deposit. The portfolio and the diary finally live at the same address. ### Sell photography collections clients pay for upfront A family collection, a newborn-and-milestones package, a two-shoot brand bundle. Packages let clients pay once for a set of sessions, with built-in credit and a validity window, right on your booking page. The Bookatu team · 2026-07-14 · Recurring revenue · https://bookatu.com/en-nz/blog/photography-collections-clients-buy-upfront · markdown: https://bookatu.com/blog/photography-collections-clients-buy-upfront.md > **The short version** > > - A package bundles sessions into one upfront purchase: a price, a credit value, a session count and an optional validity window. > - The credit can be worth more than the price, which is how you sweeten commitment without discounting single sessions. > - Packages sell on your public booking page, so a client can buy the year of photos at 10pm on a Tuesday. > - You get the cash now and a client who has already decided to come back. Every photographer knows the client who loves the spring session, promises to book the beach one, and then evaporates until next year. It is not that they changed their mind about you. It is that every session is a fresh decision, and fresh decisions lose to busy calendars. Collections remove the deciding. #### What a package actually is On Bookatu a package is four numbers and a story. The story is the name and description: Family Collection, three sessions across the year. The numbers are the price the client pays today, the credit that lands on their account, how many sessions it covers, and how long it stays valid. Set them once and the package appears on your booking page for clients to buy. ![A photographer's public packages page showing three collections with prices and included sessions](https://bookatu.com/blog/shots/photographer-packages.png) *The demo studio's packages page: three collections, each with a price, included sessions and validity, bookable by the client.* The credit is the quiet lever. Price the Family Collection at 790 and load it with 900 of credit, and you have rewarded commitment without ever writing a discount on a single session. Your headline prices stay intact. The client who commits simply gets further. #### Collections photographers actually sell - Family Collection: spring, beach and holiday sessions in one purchase, so the year's photos are decided in January. - Newborn and first year: newborn, six months, one year. Parents love not having to remember to book while sleep-deprived. - Brand starter: two shoots six months apart, because a business's website needs fresh photos more than once. - Senior or graduation season: a session now, a session at the ceremony, one decision for the family. #### Why upfront changes the business The obvious win is cash flow: the money arrives before the work, which smooths the quiet months every photographer knows. The less obvious win is retention. A client with two prepaid sessions on their account does not shop around in October. They already chose you, back when choosing was easy. And a validity window keeps the arrangement honest, gently encouraging the bookings to actually happen this year. > A package is not a discount. It is a client deciding once instead of three times. Add one collection this week. Name it after the life it captures, price it at a fair commitment, and let it sit on your booking page doing the asking for you. ### Turn your paper consent form into one clients sign online You already have a consent form. Upload the PDF and Bookatu drafts the online version for you to check, so you are not rebuilding it field by field. The Bookatu team · 2026-07-14 · Grow your business · https://bookatu.com/en-nz/blog/turn-your-paper-consent-form-into-an-online-one · markdown: https://bookatu.com/blog/turn-your-paper-consent-form-into-an-online-one.md > **The short version** > > - On the Forms page, choose Import from PDF and upload your existing consent form. > - Bookatu reads the text and builds a draft form. Contact questions become fields that fill themselves in, and the lines a client signs against become consent statements they tick. > - The draft arrives switched off, so you can read it, fix anything and mark fields required before it goes live. > - It works best with a text based PDF exported from Word or Google Docs, up to ten megabytes. A scan or photo has no text to read, so build that one in the form editor instead. Almost every salon, clinic and studio already has a consent form. It is a Word document, or a PDF a previous manager made, or a page someone laminated for the front desk. The form is not the problem. The thing that stopped it going digital was the thought of retyping every question into a new tool. So the paper stayed, and clients kept filling it in on a clipboard. You do not have to retype it. If you have the file, you can start from it. #### Upload it and start from a draft, not a blank page Open Clients, then Forms, and you will see an Import from PDF panel next to the form builder. Choose your file and Bookatu reads the text and turns it into a draft form, question by question. A form that took an afternoon to write becomes a starting point you can have in front of you in a few seconds. ![The Import from PDF panel: choose a PDF and Bookatu builds the digital version to review](https://bookatu.com/blog/shots/consent-pdf-import.png) *Choose your existing PDF and start from a draft instead of a blank form.* #### What it does with your questions It does not just dump the text into one box. It reads the shape of the form and picks a sensible field for each part. - Name, email and phone become fields that fill themselves in from the client's booking, so they are not retyping what you already have. - A line the client signs against, like agreeing they understand the risks, becomes a consent statement they have to tick. - A yes or no question becomes a single choice, and a list to pick from becomes a set of options. - The signature line at the bottom becomes a box the client draws in with a finger. It also leaves out the parts that are for you, not the client. A therapist's skin analysis, a treatment plan, a box for staff notes: those are your working notes, not something the client fills in, so they are kept off the client's version. #### You read it before anyone else does The draft is switched off when it lands. Nothing is live until you say so. Read it top to bottom, rename a field, mark the ones that matter as required, delete a question you no longer ask. When it looks right, switch it on and tick the services that should require it. From then on it behaves like any form you built by hand. #### When to type it out instead The import reads text, so it needs a file that actually contains text. A PDF exported from Word or Google Docs is perfect. A photo of a printed page, or a scan, is just an image with no text underneath, so there is nothing to read. If that is all you have, it is quicker to build the form in the editor. Most consent forms are short, and the field types are there waiting. Either way you end up in the same place. A form your clients complete and sign on their phone before they arrive, with the answers kept against their booking. The difference is only how you got there, and if you already have the file, you do not have to start from nothing. ### Consent and aftercare forms for nail and beauty salons Patch tests, allergies, a health history and a photo permission. The record you want before a first appointment, filled in and signed on the client's phone. The Bookatu team · 2026-07-14 · Grow your business · https://bookatu.com/en-nz/blog/consent-forms-for-nail-and-beauty-salons · markdown: https://bookatu.com/blog/consent-forms-for-nail-and-beauty-salons.md > **The short version** > > - A consent form is your record that a client agreed to a treatment and told you anything that matters, like an allergy or a medication. > - Build one for the services that need it: a first lash lift, a tint, a wax, a builder gel set, a facial. > - The client fills it in and draws their signature on their phone before the appointment. > - Every signed form is kept on that client's profile, with the date, so you can look back before their next visit. A nail and beauty salon runs on skin and trust. Gel that could lift, a tint that could sting, a wax on an area that turns out to be sensitive. Most of the time it is completely fine. The form is for the times it is not, and for the client who genuinely forgot to mention the medication that thins their skin. It is also there for you. If a client ever says they were never asked, a signed form with a time on it is a calm end to the conversation. #### What goes on a beauty consent form Keep it to what changes what you do in the room. A long form gets skimmed, so ask for the things that matter and leave the rest. - Who they are and how to reach them, filled in from their booking. - A short health and skin checklist: allergies, skin conditions, medication, and pregnancy where it is relevant to the treatment. - A patch test question for tint and lash work, so you have a record of what was offered and chosen. - A couple of consent statements they tick, like understanding that mild redness can happen or that results are not guaranteed. - A photo permission, if you like to post your work, so you ask once and keep the answer. - A signature at the end, drawn with a finger. ![A treatment consent form on a phone, with a skin history checklist and a signature box](https://bookatu.com/blog/shots/consent-fill-mobile.png) *The client's view: their details are already in, and they sign at the bottom before they arrive.* #### A patch test you can show you offered For tints and lash treatments the advice is usually to patch test a day or two before a first appointment. Whatever you decide to do, the consent form is where you record it. A tick box and a consent statement capture that the test was offered and what the client chose. If there is ever a reaction, you are not relying on memory. #### Attach it only to the services that need it Not every service needs a form. A repeat gel manicure for a regular probably does not. A first lash lift, a tint, a wax or a facial probably does. You tick the services that require it, so a client booking one of those is asked to complete it before the visit, while a regular booking a familiar treatment is never bothered. #### Where the signed forms live Every signed form sits on the client's profile with the date it was signed. Before their next appointment you open their card and see what they told you last time, including their drawn signature and the exact time it went in. It is the client history you always meant to keep, without the folder of paper. ![A signed treatment consent form in the dashboard with the client's answers and drawn signature](https://bookatu.com/blog/shots/consent-admin-response.png) *The signed record, kept on the client's profile for next time.* One honest note. This is about keeping a good record, not legal advice. What you are required to hold, and for how long, depends on where you are and on your insurer, so it is worth a quick check. Bookatu's job is to give you a tidy place to hold it and an easy way for clients to sign. ### A consent form your clients sign on their phone No clipboard and no printer. The client opens a link, the easy fields are already filled, they draw their signature with a finger, and they are done. The Bookatu team · 2026-07-14 · Grow your business · https://bookatu.com/en-nz/blog/a-consent-form-your-clients-sign-on-their-phone · markdown: https://bookatu.com/blog/a-consent-form-your-clients-sign-on-their-phone.md > **The short version** > > - The client gets a link, on their booking confirmation or texted to them, and opens it on their phone. > - Their name, email, phone and the date are already filled in from the booking. > - They draw their signature in a box with a finger, tick the consent lines, and submit. > - You get the record with the drawn signature, their printed name and the exact time. The signature is the part people worry about, and fairly so. A photo of a paper form is not really signed. A name typed into a box is easy to argue with. So Bookatu asks the client to draw their signature, the same way they would sign the screen on a card machine. ![A signature box on a phone with a signature drawn in it and a Clear button](https://bookatu.com/blog/shots/consent-signature-drawn.png) *The client signs by drawing in the box. Clear wipes it if they want another go.* #### The client's side, start to finish There is nothing to download and no account to make. They open the link and the form is already titled for your business. - Their contact details are filled in, so they are not retyping what you already know. - They work down the questions: a checklist here, a yes or no there, a consent line to tick. - They draw their signature in the box, and tap Clear if they want to redo it. - They submit. If a required box was missed, the form says so instead of failing quietly. - They see a simple confirmation that their details are in. The form cannot be filled twice. Start to finish it is about a minute, done at home the evening before, not in your reception with a queue behind them. #### The bits that fill themselves in Name, email, phone and the appointment date come straight from the booking. It is the difference between a form that feels like homework and one that feels half done already. If anything is out of date, the client can correct it on the spot. #### What you are left holding The drawn signature is saved as an image, kept with the client's printed name, the exact time of signing and the booking it belongs to. It sits on the client's profile, ready for the next visit. For a treatment that needs a consent record, that is the record, and it is not in a drawer. #### For phone bookings and walk-ins When a booking does not come through your booking page, you are not stuck. Tap Get fill link on the forms page and text or email a fresh link. The same link works if you close it and come back, so a client can start it on the bus and finish it at home. The clipboard was never the point. The record was. Moving the signing onto the client's phone keeps the record and loses the paper. ### Money math in integer cents, and the discount that vanished We gave a fifty-cent discount and the ledger recorded none of it. Floating point was not even the culprit. A field guide to doing money arithmetic with integers: clamping, proration, and making a ledger of unit prices sum to the exact total. The Bookatu engineering team · 2026-07-13 · Engineering · https://bookatu.com/en-nz/blog/money-math-in-integer-cents · markdown: https://bookatu.com/blog/money-math-in-integer-cents.md > **The short version** > > - Store and compute money as integer cents. Floats are the famous bug; rounding policy is the real one. > - A prorated discount must reconcile: after rounding each line's share, push the leftover cents onto lines with room until the sum is exact. > - If a ledger stores one unit price per line, a discounted total that does not divide evenly cannot be represented. Split the line into two prices one cent apart. > - Clamp everything at the edges: discounts to the subtotal, quantities to stock, totals to zero. Every engineer learns early that 0.1 plus 0.2 is not 0.3, so we all store money as integer cents and feel safe. Then you build something real, like a percentage discount across a cart, and discover that integers only solve the first problem. The second problem is that division does not care about your ledger. #### The fifty cents that went missing Here is the setup that bit us, reduced to its bones. A cart holds 100 units of a one-dollar item. The customer gets fifty cents off the order. The subtotal is 10,000 cents, the discount is 50 cents, and the discounted total is 9,950 cents. So far, nothing but integers. Now record that sale in a ledger that stores a unit price per line, the way accounting systems like to. The discounted unit price is 9,950 divided by 100, which is 99.5 cents. That is not an integer, so it gets rounded to 100. The ledger now says 100 units at 100 cents: a full-price sale. The discount did not shrink. It vanished, while the interface promised the customer 9,950 and the books said 10,000. ```js // The trap: one rounded unit price cannot represent every total. const subtotal = 100 * 100; // 10000c const discounted = subtotal - 50; // 9950c const unit = Math.round(discounted / 100); // 100c ... the discount is gone console.log(unit * 100); // 10000c, not 9950c // The fix: split the line into two prices one cent apart. const qty = 100; const base = Math.floor(discounted / qty); // 99c const rem = discounted - base * qty; // 50 units get one extra cent // rem units at (base + 1), the rest at base: // 50 * 100 + 50 * 99 === 9950 ✓ exact, and every price is an integer ``` The split looks fussy until you see what it buys. Fifty units at 100 cents plus fifty units at 99 cents equals exactly 9,950. Every row still stores an honest integer unit price, the quantities still add up, and the sum of the ledger equals the number on the receipt to the cent. Nothing about that is possible with a single rounded price. #### Proration needs a reconciliation pass The same disease appears one level up when an order-level discount spreads across several lines. Give each line its proportional share and round, and the shares will sum to almost the discount. Sometimes one cent over, sometimes one under, occasionally spot on, which is the worst outcome of all because it hides the bug from casual testing. ```js // Prorate by share, then push the rounding leftover onto lines with room. let allocated = 0; for (const line of lines) { line.discount = Math.min( line.subtotal, Math.round((discount * line.subtotal) / orderSubtotal), ); allocated += line.discount; } let remainder = discount - allocated; // may be negative for (const line of lines) { if (remainder === 0) break; const room = remainder > 0 ? line.subtotal - line.discount : line.discount; const move = Math.min(Math.abs(remainder), room) * Math.sign(remainder); line.discount += move; remainder -= move; } // invariant: sum(line.discount) === discount, and no line goes negative ``` Two details in that loop earned their keep the hard way. The remainder spreads across any line with capacity, not just the last line, because the last line can be a six-cent item with no room to absorb three leftover cents. And each share is capped at its own line subtotal, because a discount larger than the line implies a negative unit price, and negative unit prices are how a ledger starts lying in the other direction. ![A point-of-sale screen showing a subtotal, a ten percent discount, and the exact discounted total](https://bookatu.com/blog/shots/pos-discount-light.png) *The boring receipt is the whole point: subtotal, discount, and a total the ledger reproduces to the cent.* #### Clamp at every edge - Discounts clamp to the range from zero to the subtotal. A hundred and ten percent off is a typo, not a refund. - Parse user-entered amounts defensively: empty and non-numeric mean zero, never NaN in the middle of arithmetic. - Quantities clamp to what exists. Money code inherits every inventory bug upstream of it. - Test the totals that do not divide evenly. Three items at ten dollars with a dollar off is a better test than any round number. None of this is glamorous, which is exactly why it slips through review. The arithmetic looks correct because it is correct, right up until integer division quietly throws away a remainder someone was owed. Write the invariant down, sum of parts equals the whole, and make a test hold the door. > Integers keep money honest. Reconciliation keeps integers honest. ### A seeded sandbox beats a copy of production Our whole local environment is an in-process Postgres that boots from empty, applies real migrations, and fills itself with a convincing fake salon. No production credentials on laptops, no real client data in screenshots, and a demo that never goes stale. The Bookatu engineering team · 2026-07-13 · Engineering · https://bookatu.com/en-nz/blog/seeded-sandbox-instead-of-prod-data · markdown: https://bookatu.com/blog/seeded-sandbox-instead-of-prod-data.md > **The short version** > > - Local development runs an embedded, in-process Postgres. Blank credentials mean it is physically impossible to touch production by accident. > - The database is rebuilt from the same migration files production uses, so schema drift shows up on a laptop before it shows up in a deploy. > - A seed script creates a believable business: services, staff, clients, bookings, stock. Realistic enough to find real bugs. > - Fake data can go anywhere: screenshots, blog posts, bug reports, demos. Production data can go nowhere. There is a moment in every small team's life when someone suggests pointing local development at a copy of the production database, because the fake data feels thin and the real bugs only happen with real records. It is a tempting idea with a long tail of regret: credentials spread across laptops, client names in screenshots, a test email job that one day finds real addresses. We went the other way and never looked back. #### An entire Postgres inside the process Embedded Postgres builds have gotten genuinely good. Our app decides at startup: if real database credentials exist in the environment, use the hosted database; if they are blank, spin up an in-process Postgres that lives in a local folder. Development machines simply never have the credentials, so the failure mode of a misconfigured laptop is a fresh empty database, not a production incident. ```js // Choose the database at runtime. Blank env = embedded, local, harmless. function makeDb() { const url = process.env.DATABASE_URL; if (url) return connectHosted(url); // In-process Postgres persisted to a local folder const client = new EmbeddedPostgres('./.pgdata'); return drizzle(client, { schema }); } ``` The rebuild path matters as much as the engine. We recreate the local database by applying the same migration files that production ran, in order, from the first one. That single decision has caught a family of bugs for free: a migration that assumed a column from a later file, a schema change that worked against a stale snapshot but not from scratch. If the laptop cannot build the schema from history, the next deploy could not either. #### Seed a business, not rows The difference between useless and useful fake data is narrative. Our seed script does not insert ten users named test. It creates a salon with a name, staff with specialties, services with honest prices and durations, clients with visit histories, upcoming appointments, retail products with stock levels and a ledger behind them. The pages look inhabited, which means layout bugs, empty states, and awkward truncation show up the way they would for a real customer. ![A booking dashboard filled with seeded example data: revenue, appointments and client activity](https://bookatu.com/blog/shots/dashboard-light.png) *Everything in this screenshot is fiction. That is exactly what makes it publishable.* That last property is easy to underrate. Every screenshot in our docs, our blog, and our bug reports comes from the seeded sandbox. Nobody has to squint at an image asking whether a client name slipped through, because there are no client names to slip. The safest redaction process is having nothing to redact. #### What to get right - Make the safe path the default path. Developers should have to go out of their way to reach real data, not out of their way to avoid it. - Neutralize side effects too: email, payments and storage keys stay blank locally, so a loop over seeded clients can never message a real person. - Seed the states you dread: the brand-new account, the fully booked day, the out-of-stock product, the client with one visit years ago. - Keep the seed in code review. When a feature adds a table, the seed grows with it, or the sandbox quietly rots. The payoff compounds. New teammates run two commands and have a working business to poke at. Visual QA can photograph every page without a privacy review. And the demo environment is always five minutes from pristine, because pristine is just a rebuild away. > Production data answers questions. Seeded data lets you ask them safely. ### The dropdown that refused to be clicked A menu rendered perfectly, sat exactly where it should, and swallowed every click. The culprit was an entrance animation that never really ended. A short tour of CSS stacking contexts, animation fill modes, and how to hunt bugs you cannot see. The Bookatu engineering team · 2026-07-11 · Engineering · https://bookatu.com/en-nz/blog/the-dropdown-that-refused-to-be-clicked · markdown: https://bookatu.com/blog/the-dropdown-that-refused-to-be-clicked.md > **The short version** > > - animation-fill-mode: both keeps applying the final keyframe forever, and an applied transform makes the element a permanent stacking context. > - That traps every dropdown inside the animated container: its z-index can no longer compete with later siblings that have their own stacking contexts. > - Ending the keyframe at transform: none does not save you. Browsers compute the filled value as an identity matrix, which still counts as a transform. > - Entrance animations on containers should fill backwards, not both. The natural end state already equals the final keyframe. We shipped a dropdown menu that could not be clicked. It opened fine. It rendered in the right place, fully visible, correct z-index, no console errors. Clicks went straight through it into the panel underneath, as if the menu were a ghost. If you have ever fought a bug like this, you already know the disorienting part: everything looks right, and nothing works. #### Finding out who is actually on top The first honest answer came from the browser, not from reading code. document.elementFromPoint tells you which element really receives a click at a coordinate. We pointed it at the centre of a menu item, and it returned a card that sat later in the page. The menu was visually on top and physically underneath. ```js // Who really gets the click at this point? const item = document.querySelector('[role="menuitem"]'); const r = item.getBoundingClientRect(); const top = document.elementFromPoint(r.x + r.width / 2, r.y + r.height / 2); console.log(top === item || item.contains(top)); // false -> something covers it // Walk the ancestors and list everything that creates a stacking context for (let el = item; el; el = el.parentElement) { const cs = getComputedStyle(el); const reasons = []; if (cs.transform !== 'none') reasons.push('transform'); if (cs.filter !== 'none') reasons.push('filter'); if (cs.backdropFilter !== 'none') reasons.push('backdrop-filter'); if (cs.opacity !== '1') reasons.push('opacity'); if (cs.position !== 'static' && cs.zIndex !== 'auto') reasons.push('z-index'); if (reasons.length) console.log(el.className, reasons); } ``` The walk found it. The header that contained the menu reported a transform, even though no stylesheet gave it one. The only transform anywhere near it was an entrance animation, a little fade-and-rise that had finished half a second after page load. #### Fill modes outlive their animations animation-fill-mode: both means the element holds the first keyframe before the animation starts and keeps the last keyframe after it ends. Keeps, forever. If any keyframe animates transform, the finished animation still applies a transform, and a transformed element becomes a stacking context. Every descendant's z-index is now trapped inside it, competing only with local siblings, never with the rest of the page. Our page had panels after the header that used backdrop-filter, which creates its own stacking context. Two sealed boxes, and paint order between them decided by tree order, not by the z-index we kept raising in confusion. The menu could have had z-index a million. Inside its box, nobody outside could hear it. Here is the trap inside the trap. We changed the final keyframe to transform: none, reasoning that the retained value would then be harmless. The computed style still reported a matrix. Browsers resolve an applied animation's transform as a matrix value, and identity matrix still counts as a transform for stacking purposes. The stacking context survived our fix. ```css /* BAD: the finished animation keeps applying its last keyframe forever. The header remains a stacking context for the life of the page. */ .enter { animation: rise 0.5s ease-out both; } /* GOOD: fill backwards only. The element returns to its natural state after the animation, which is identical to the final keyframe anyway. */ .enter { animation: rise 0.5s ease-out backwards; } @keyframes rise { from { opacity: 0; transform: translateY(10px); } to { opacity: 1; transform: none; } } ``` #### The rule we wrote down Entrance animations on containers fill backwards, never both. Backwards covers the only gap that matters, the frames before a delayed animation starts. Once the animation ends, the element detaches from it completely and stops being a stacking context. The visual result is identical because a well-built entrance ends at the element's natural state. ![A dropdown menu opening correctly above frosted glass panels in a dark dashboard](https://bookatu.com/blog/shots/stock-menu-open-dark.png) *After the fix: the menu paints above the frosted panels and, more to the point, catches its own clicks.* - Trust elementFromPoint over your eyes. Visual order and hit-testing order can disagree, and only one of them takes the click. - When z-index stops making sense, stop raising it and start hunting stacking contexts. The ancestor walk above takes a minute. - Audit what your finished animations leave behind. getComputedStyle on a quiet page tells you what is still applied. - Filled transforms are transforms, even when the keyframe says none. > The animation was half a second long. Its side effect had no end time at all. ### Dashboard charts with zero dependencies We built the trend lines, sparklines, and category bars on our dashboard as plain inline SVG. No chart library, a few hundred lines total, dark mode for free. Here is the case for hand-rolled charts, and for when you should absolutely not do this. The Bookatu engineering team · 2026-07-11 · Engineering · https://bookatu.com/en-nz/blog/dashboard-charts-with-zero-dependencies · markdown: https://bookatu.com/blog/dashboard-charts-with-zero-dependencies.md > **The short version** > > - A dashboard's charts are usually a handful of shapes: a line, an area, some bars. That is a few dozen SVG elements, not a library. > - Coloring strokes and fills with CSS variables means the charts follow your theme automatically, including dark mode. > - You own every state: empty, one data point, reduced motion, screen readers. > - Reach for a library when you need interactivity, scales, or chart types you would otherwise reinvent badly. When we added an inventory dashboard, the obvious move was to install a chart library. The popular ones are excellent. They are also large, opinionated about theming, and built to handle a thousand cases when we needed four: a two-series trend line, a per-row sparkline, a stock-level bar, and a category breakdown. We wrote them as inline SVG instead, and the whole set came in smaller than most libraries' type definitions. ![An inventory dashboard with a trend chart, category breakdown and ranked list in light theme](https://bookatu.com/blog/shots/inventory-control-center-light.png) *Four hand-rolled charts: trend lines, a segmented category bar, ranked value bars, and per-row sparklines.* #### A chart is a path Strip away the tooling and a line chart is one string: an SVG path built from your values. Map each point's index to x, each value to y, and join them. The only subtlety worth writing down is padding: map the maximum value a few pixels below the top edge, or the stroke at your peak gets sliced in half by the viewBox. ```js const W = 300, H = 80, PAD = 3; // top pad so the peak stroke is not clipped const max = Math.max(1, ...values); const x = (i) => (i / (values.length - 1)) * W; const y = (v) => PAD + (H - PAD) * (1 - v / max); const d = values .map((v, i) => `${i === 0 ? 'M' : 'L'}${x(i).toFixed(1)} ${y(v).toFixed(1)}`) .join(' '); // ``` #### Dark mode costs nothing The quiet win is theming. Our design tokens are CSS variables, and SVG strokes and fills accept them like any other property. stroke="var(--color-primary)" means the chart recolors itself the instant the theme flips, with no chart-level theme config, no duplicate palette, and no drift between the charts and the rest of the interface. When we later adjusted our dark palette, the charts followed without being touched. ![The same inventory dashboard rendered in dark theme](https://bookatu.com/blog/shots/inventory-control-center-dark.png) *The same components in dark mode. No chart was edited; the CSS variables did the work.* #### You own the edges Libraries are generous with features and stingy with edge cases that are yours alone. What should a sparkline do with one data point? What does the trend chart say when a business is brand new and every value is zero? Hand-rolled components make these decisions explicit and cheap: an honest empty state with a sentence, a flat line instead of a crash, a text summary next to every chart for screen readers, and a single prefers-reduced-motion media query that turns the draw-in animation off. - Give every chart an aria-label and a plain-language summary. The SVG is decoration; the sentence is the data. - Animate strokes with stroke-dashoffset for a draw-in effect, and gate it behind prefers-reduced-motion. - Keep math and markup together. A chart component you can read top to bottom in one screen is a chart you can fix at 11pm. - Design the empty state first. New accounts see it more than any other state. #### When you should use a library Hand-rolling stops being clever the moment requirements grow real teeth. Zooming and brushing, log scales, stacked areas with proper interpolation, axes with smart tick placement, canvas rendering for tens of thousands of points: these are solved problems, and solving them again by hand is how a two-day feature becomes a two-month hobby. Our rule is simple. If the chart is presentation, write the SVG. If the chart is an instrument the user operates, take the dependency and be glad someone maintains it. > The best chart library for four small charts turned out to be a for loop. ### Test the pixels: screenshot QA for a small team Our test suite was green and the dropdown was unclickable. Unit tests cannot see stacking bugs, dark-theme breakage, or mobile overflow. Here is the small screenshot rig that now looks at every surface for us, and the visual bugs it catches that tests never will. The Bookatu engineering team · 2026-07-11 · Engineering · https://bookatu.com/en-nz/blog/test-the-pixels-screenshot-driven-qa · markdown: https://bookatu.com/blog/test-the-pixels-screenshot-driven-qa.md > **The short version** > > - Green tests prove the logic works. They say nothing about whether a human can see or click the result. > - A screenshot rig is small: a seeded local environment, one saved login, a loop over pages, themes and viewports. > - Pair the images with programmatic checks: elementFromPoint proves a button is clickable, getBoundingClientRect proves an input fits the screen. > - Then actually look at the screenshots. The looking is the test. We adopted this the honest way: after shipping visual regressions that a single screenshot would have caught. A frosted panel that came out pale on dark backgrounds. A menu that rendered but could not be clicked. A search field that existed at phone width as a 65 pixel sliver. Every one of them sailed through a green test suite, because the suite was testing functions and the bugs lived in pixels. #### The rig is smaller than you think Ours is a seeded local environment full of convincing fake data, one headless login whose session is saved to disk so nothing throttles, and a loop: pages times themes times viewports. Desktop and phone, light and dark, every surface that matters. The whole thing is a short script, and a full sweep produces a folder of images in a few minutes. ```js import { chromium } from 'playwright'; const browser = await chromium.launch(); const ctx = await browser.newContext({ storageState: 'auth.json', // login once, reuse everywhere viewport: { width: 1440, height: 900 }, }); const page = await ctx.newPage(); for (const [name, url] of PAGES) { await page.goto(BASE + url, { waitUntil: 'load' }); for (const theme of ['light', 'dark']) { await page.evaluate((t) => document.documentElement.setAttribute('data-theme', t), theme); await page.screenshot({ path: `shots/${name}-${theme}.png`, fullPage: true }); } } ``` #### Screenshots plus proof Images catch what eyes catch. For interaction bugs you want the browser to testify. Two one-liners do most of the work: elementFromPoint at the centre of a control tells you what would really receive the click, and getBoundingClientRect tells you whether the control actually fits the viewport it claims to support. We now assert both for anything that has burned us. ```js // Is the menu item really clickable, or is something invisible covering it? const hit = await page.evaluate(() => { const el = document.querySelector('[role="menuitem"]'); const r = el.getBoundingClientRect(); const top = document.elementFromPoint(r.x + r.width / 2, r.y + r.height / 2); return el === top || el.contains(top); }); // Does the search input actually fit a 390px phone? const fits = await page.evaluate(() => { const r = document.querySelector('input[name="q"]').getBoundingClientRect(); return r.right <= window.innerWidth && r.width > 200; }); ``` #### Both themes, every time Dark mode bugs are a category of their own because they hide from developers who work in one theme. A hardcoded near-white fill looks intentional on a light page and radioactive on a dark one. Flipping the theme attribute inside the same page visit costs one line and doubles your coverage. We treat any surface that has not been photographed in both themes as untested. ![A booking dashboard photographed in light theme](https://bookatu.com/blog/shots/dashboard-light.png) *The same page, photographed twice per sweep. Light...* ![The same booking dashboard photographed in dark theme](https://bookatu.com/blog/shots/dashboard-dark.png) *...and dark. Hardcoded colors have nowhere to hide when both frames exist.* #### What it catches - Stacking-context bugs: rendered, visible, and unclickable. Only a hit-test sees these. - Theme leaks: light surfaces glowing on dark pages, charts that vanish, illustrations with baked-in backgrounds. - Phone overflow: fixed bars covering content, inputs clipped to slivers, headlines cut mid-sentence. - Copy in context: the truncation, the contradiction, the sentence that a linter will never flag. None of this replaces the unit suite. The suite proves the money math; the screenshots prove a human can reach the button that triggers it. A small team does not have a QA department, but a folder of fresh screenshots reviewed before every release is a decent imitation of one. The test is the looking. > Tests pass is a statement about your functions. The screenshot is a statement about your product. ### Loyalty points that quietly bring clients back A points program does not need punch cards or a separate app. Turn on loyalty, set what a visit and a dollar are worth, and let regulars earn their way to a credit they will come back to spend. The Bookatu team · 2026-07-11 · Recurring revenue · https://bookatu.com/en-nz/blog/loyalty-points-that-bring-clients-back · markdown: https://bookatu.com/blog/loyalty-points-that-bring-clients-back.md > **The short version** > > - Loyalty is built in: clients earn points for joining, for each visit, and for what they spend. > - You set the numbers. A common setup is 50 points for signing up, 20 per visit, and 1 point per dollar. > - When a client reaches your redeem level, their points turn into a credit toward a visit. > - There is nothing to print and nothing for the client to install. It just accrues. Mel kept a box of stamped cards behind the counter for two years. Ten stamps, one free blow-dry. The trouble was that the cards lived in handbags and glove boxes, half of them got lost, and the client who deserved the reward most was usually the one who forgot the card. The program cost her money and nobody felt rewarded. #### Points that track themselves With loyalty turned on, the earning happens on its own. A new client picks up a welcome bonus when they join. Every completed visit adds points. Spending adds points too, so the client who books the long colour appointment earns more than the quick fringe trim, which feels fair because it is. You choose the numbers in your settings, and you can keep them simple. The defaults are 50 points for signing up, 20 points per visit, and 1 point for every dollar spent, with 200 points converting into a 20 dollar credit. If that feels too generous or too stingy for your prices, change any of the numbers and the program follows. ![A calm, modern salon interior](https://images.unsplash.com/photo-1633681926022-84c23e8cb2d6?auto=format&fit=crop&w=1200&q=70) *The client never carries a card. Their points sit on their profile and add up on their own.* #### The credit is the comeback A discount you hand to everyone trains people to wait for discounts. A credit someone has earned works differently. It belongs to them, it has a number on it, and leaving it unspent feels like a waste. When a regular sees they are 40 points away from a credit, the next booking stops being a question of if and becomes a question of when. - Reward the behaviour you want. Points per visit favours frequency; points per dollar favours bigger services. Use both and you favour good clients, full stop. - Keep the redeem level reachable. A reward a client can touch within a few visits changes behaviour. One that takes a year does not. - Let the welcome bonus do its job. A new client with 50 points already has a reason to make it to visit two, which is where regulars are made. - Talk about it once. A line on your booking page and a mention at checkout is enough. The balance does the reminding after that. > The best loyalty program is the one nobody has to remember, including you. #### Turn it on and forget it Loyalty lives in your settings with plain-language controls: the signup bonus, points per visit, points per dollar, and what a redemption is worth. Set it once and it runs in the background while you work. Mel threw out the card box months ago. Her regulars did not lose anything this time, because there was nothing left to lose. ### Before and after photos, kept where you will actually find them Your camera roll is not a filing system. Keep before and after photos on the client's profile, private to your team by default, so last visit's work is one tap away at the next appointment. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/before-and-after-photos-on-the-client-profile · markdown: https://bookatu.com/blog/before-and-after-photos-on-the-client-profile.md > **The short version** > > - Add photos straight to a client's profile and tag each one as before, after, or general. > - Photos are private to your team by default. Nothing is public unless you choose to share it. > - You can share an individual photo to the client's own portal when you want them to have it. > - Next visit, the whole history is on the profile, not lost in someone's camera roll. Ask a lash artist where last month's client photos are and you will hear the same answer: somewhere in my phone. Between personal photos, other clients, and three angles of the same set, finding the right one mid-appointment means scrolling with one glove off while the client waits. The photos exist. The system does not. #### Photos that live with the client On Bookatu, photos attach to the client profile itself. Open the client, add the photo, tag it before or after, and give it a caption if the detail matters, like the colour formula or the curl and length used. At the next fill you open the same profile and the record is right there, in order, newest first. That changes the start of an appointment. Instead of asking a returning client what was done last time and trusting memory, you look. A colourist checks the exact shade that worked. A skin therapist compares this month against last month. A tattoo artist reviews the healed result before planning the next session. ![Close-up of detailed nail work](https://images.unsplash.com/photo-1604654894610-df63bc536371?auto=format&fit=crop&w=1200&q=70) *Work this good deserves better than page 47 of a camera roll.* #### Private first, shared on purpose Client photos are sensitive, so the default is conservative: everything you upload is visible to your team only. The client cannot see it, and neither can anyone else. When there is a photo the client would love, you share that one photo to their portal, where they can view it against their own visits. You stay in control of what leaves the back room. - Ask before you shoot. A quick yes makes everyone comfortable, and clients almost always say yes when the photo is for their own record. - Shoot the before even when it is unglamorous. The after only tells half the story without it. - Caption the details you will want later: products, settings, formulas, sizes. - Share the flattering after to the client's portal. It is a small delight, and it quietly reminds them what your work looks like. #### The record becomes the routine None of this needs a new habit beyond the one you already have, taking the photo. The only change is where it goes. Put it on the profile instead of the camera roll and every future appointment starts a step ahead, with the work in front of you instead of somewhere in your phone. ### The QR code on your counter that books clients while you work Every 'I'll book later' is a booking you might not get. A QR code on the counter, the mirror, or the window sends people straight to your booking page while the intention is still warm. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/qr-code-on-the-counter-that-books · markdown: https://bookatu.com/blog/qr-code-on-the-counter-that-books.md > **The short version** > > - Your admin has a ready-made QR code that opens your booking page directly. > - Print it for the counter, the mirror, the window, or the bottom of a price list. > - People scan with their phone camera and land straight on your services and times. > - The window copy works after hours too, when your door is shut but your calendar is not. Dre hears it a dozen times a week at the register: this was great, I will book my next one later. He used to hand over a card with the shop's name and hope. Some of those people came back. Plenty did not, not because the cut was bad, but because later is where intentions go to be forgotten. #### Catch the booking while it is warm The best moment to book the next visit is the moment someone is happy with this one. A QR code on the counter turns that moment into an action that takes seconds. The client points their camera, the booking page opens, they pick a time while their card is still in their hand. No app, no account, no typing an address. The code comes from the Share and QR page in your admin, already wired to your booking page. Print it any size. It works on a laminated card at the register, a sticker on the mirror, or a poster in the window. ![Phones on a table](https://images.unsplash.com/photo-1556656793-08538906a9f8?auto=format&fit=crop&w=1200&q=70) *The whole flow is camera, scan, book. The friction of 'later' never gets a chance.* #### Your window works the night shift A code in the window changes what a closed shop means. Someone walks past at 9pm, likes the look of the place, scans, and books Thursday. You find the booking in the morning. The window did the selling and the calendar did the paperwork while you were at home. - Counter card: the after-service booking, caught at peak happiness. - Mirror sticker: clients stare at your mirror for most of an appointment. Put the next visit in their eyeline. - Window poster: after-hours bookings from foot traffic you would otherwise never meet. - Price list footer: the person studying your prices is already halfway to booking. > A business card asks someone to remember you. A QR code asks them to book you. #### Five minutes, once Open Share and QR in your admin, print the code, and put it where eyes already go. That is the entire project. It costs a sheet of paper and it works every day after, including the days you are closed. ### Offer online sessions and let the video link make itself Mark a service as an online video call and every booking for it gets its own Google Meet link in the confirmation email. Here is how a personal trainer kept the clients that distance was costing him. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/offer-online-sessions-with-google-meet · markdown: https://bookatu.com/blog/offer-online-sessions-with-google-meet.md > **The short version** > > - Connect one business Google account, turn on one switch, and choose Online meeting under How clients meet you on each service you run by video. That is the whole setup. > - When a client books one of those services, a Google Meet link is created with the booking and arrives in their confirmation email. > - Your in-person services are untouched. Only the services you mark as online get a link, so a mixed week just works. > - The appointment also lands on the connected Google Calendar with the link attached, so both sides know where the session is. Marcus trains people out of a small studio behind his house. His problem was not finding clients. It was keeping the ones whose lives moved. One flies out every second week for work. One had a baby and could not get to the studio for months. One moved two hours up the country and still wanted to keep her programme going. In every case the training did not need to stop. The drive did. #### The link was the annoying part He tried running check-ins by video, and the sessions themselves worked fine. The admin around them did not. He would agree a time by text, then remember the night before to create a meeting link, then paste it into another text and hope it did not get buried. Twice a client sat waiting in a call Marcus had accidentally made under an old account. It was a five-minute job that still managed to go wrong about once a month, and it made online sessions feel second-class next to his studio ones. #### One service, marked as an online call In Bookatu the video link is a property of the service, not a chore per booking. Marcus added a service called Online check-in, 30 minutes, priced a little under a studio session. Then he changed three settings, once: - He connected one business Google account to Bookatu in his settings. Nobody on a team has to link a personal account for this to work. - He turned on the master switch in his booking rules, called "Add a Google Meet link to online bookings". - On the Online check-in service he chose Online meeting under How clients meet you and saved. His studio sessions stay on At your place. That is the entire setup. From then on, any booking for that service creates its own Google Meet link the moment the booking is made. Nothing to paste, and nothing to remember the night before. #### What the client gets Sarah, the client who moved away, books the check-in on his page the same way she used to book studio time. Her confirmation email tells her it is an online appointment and carries a Join the video call button, with the link written out underneath it in case the button does not load. When she adds the booking to her own calendar from the confirmation page, the link travels with it. At two o'clock on Thursday she taps the button and she is in the room. ![A flat lay of phones on a table](https://images.unsplash.com/photo-1556656793-08538906a9f8?auto=format&fit=crop&w=1200&q=70) *The link lives in the confirmation, so the client always knows where the session is.* #### What Marcus gets His side is just as quiet. The email that tells him Sarah booked has a Join the call link in it, and the appointment lands on the connected Google Calendar with the video link attached. On a bigger team there is a nice detail here: if a trainer has connected their own Google Calendar with sync turned on, that trainer's video bookings run through their account instead, so the calendar entry and the link stay with the right person. > The sessions were never the problem. The link was. Now the link makes itself. #### Where online sessions earn their keep An online service is not a lesser copy of the real thing. It is a different product with its own uses: - Check-ins between studio blocks, so a travelling client keeps momentum instead of restarting every month. - A short paid consult before a first session, so new clients arrive assessed and ready to train. - Programme reviews for clients who train alone at a gym near work and just need the plan adjusted. - The same idea works outside training. A skin clinic can run pre-treatment consults by video, and a tennis coach can walk a player through match footage. #### Keep the mix honest Choosing How clients meet you on each service matters more than it looks. Because each service is set on its own, a hybrid week needs no thought. Studio sessions stay exactly as they were. Online check-ins get a video link. A client never receives a Meet link for something that happens in person. Marcus did not move his business online. He added one online service next to his real ones, and the bookings run themselves. Video appointments are included on every Bookatu plan. If you have clients you have quietly lost to distance, add one online service this week and send them your booking page. The first booking will make the link for you. ### Ring up counter sales in a few taps, discount included A client at the counter wants the serum you just used and a top coat to go with it. Here is how to ring that up in a few taps, take 10 percent off on the spot, and have the sale land in your books the moment it happens. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/ring-up-counter-sales-with-a-discount · markdown: https://bookatu.com/blog/ring-up-counter-sales-with-a-discount.md > **The short version** > > - The Sell screen is a grid of your products. Tap what the client is buying and it is in the sale. > - Give a discount on the spot, as a percentage or a dollar amount, and see the new total before you record anything. > - Record the sale and stock drops that moment. There is no separate step to remember later. > - Every sale lands in a stock ledger with the price actually paid, ready to download as a CSV for your accountant. Tess runs a nail studio with a retail shelf beside the counter. Most days someone buys something on the way out. The trouble was never the selling. It was the recording. The client paid, the bottle left the shelf, and the sale lived in a notebook, or on a sticky note, or nowhere. Every few months Tess would count the shelf, find it did not match what she thought she had sold, and give up on working out why. Then one Thursday a regular finished her gel manicure, held up the cuticle serum Tess had used on her, and said she would take one home, plus a top coat to go with it. #### Two taps and the sale is on the screen Bookatu has a Sell screen in the admin, made for a phone at the counter. It is a grid of your products with big tiles, so it works with one thumb while a client is standing there. Tess tapped the serum tile, then the top coat tile, and both were in the sale. Tapping a tile again adds another one, and small plus and minus buttons fix a slip. Each tile shows the price and, for anything you track, how many are on the shelf. A sold-out product says so right on the tile and cannot be added, so you never ring up a bottle you do not have. If your shelf is bigger than a screen, a search box at the top narrows it by name, brand, or category. ![The Sell screen with two products in the sale and a 10 percent discount applied before recording](https://bookatu.com/blog/shots/pos-discount-light.png) *The Sell screen. Tap tiles to build the sale, set a discount, and see the new total before you record anything.* #### Ten percent off, decided at the counter The client is in every three weeks, so Tess wanted to take something off. At the bottom of the Sell screen there is a discount row. A small toggle picks between a percentage and a dollar amount, and a box takes the number. Tess tapped the percent side and typed 10. The bar underneath showed the subtotal, the discount coming off, and the new total, all before anything was recorded. If you type the wrong number, the total simply follows you while you fix it. The discount is also capped at the subtotal, so no typo can drag a sale below zero. #### Record it, and the shelf already knows The last step is how it was paid. There is a plain dropdown for Cash, Card, or Other, because the money itself moves the way it always did, through your card machine or into the cash drawer. Tess picked Card and tapped Record sale. The stock count dropped at that moment. The products page showed one less serum and one less top coat, and if that serum had just reached its reorder point it would already be wearing a Low stock tag. There is a quiet honesty check built in too. If the screen was stale and the last unit had already gone out, Bookatu records only what was really on hand, so a sale never claims a bottle that did not exist. Every recorded sale becomes a line in the stock ledger. Each line keeps: - The date and time, and which product went out. - The price each unit actually sold for, after the discount. Not the sticker price. - How it was paid and the discount you gave, in a short note like POS · Card · 10% off. - The reason for the movement, so a sale never gets mixed up with a delivery or a stock correction. #### The discount is split fairly, down to the cent Here is the part you would never want to do by hand. A 10 percent discount off the whole sale has to be shared between the serum and the top coat, and the cents rarely divide evenly. Bookatu spreads the discount across the items in proportion to what each one cost, then settles any leftover cent so the per-item prices in the ledger add up to exactly what the client paid. No line ever goes negative, and nothing gets rounded away. It sounds fussy, and it is, which is exactly why software should be the one doing it. Your ledger and the total on the screen always agree, to the cent. > The point of ringing up a sale is not the moment the money changes hands. It is that six months later you can say exactly what left the shelf and what it sold for. #### Tax time is a download, not a dig When your accountant asks about retail sales, the answer is a button. The ledger lives under Products, and it exports to a CSV with the date, the product, the quantity, the unit price, and the note that says how it was paid. Every counter sale you rang up through the year is already in there, discounts included. Tess used to reconstruct her retail takings from card statements and memory. Now the record is written at the same moment as the sale, by the same tap that rang it up. ![A close-up of a manicure in progress at a nail studio](https://images.unsplash.com/photo-1604654894610-df63bc536371?auto=format&fit=crop&w=1200&q=70) *The sale starts in the chair. Ringing it up should not take longer than the small talk.* None of this asks Tess to change how she works. The client still pays the way she always did. The difference is that the sale is now a fact in her books instead of a guess in her head. Two taps for the products, one number for the discount, one tap to record. The shelf count stays right, the ledger stays right, and there is nothing left to write down after the client has gone. ### Airy for a spa, bold for a barber: choosing a look for your booking page Your booking page should feel like your shop, not like a template. Bookatu comes with six shop-front looks. Pick one in settings, preview it in your own brand colour, and save. Your layout and your colours stay exactly where they are. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/choose-a-look-for-your-booking-page · markdown: https://bookatu.com/blog/choose-a-look-for-your-booking-page.md > **The short version** > > - Your public shop page comes with six looks. Pick one in settings, save, and that is what visitors see from then on. > - A look changes the feel of the page: the headline font, how rounded things are, and the colour glow at the top. Your layout and your brand colour stay put. > - Every shop starts on Auto, which tunes the style to your industry. Do nothing and you already have a sensible look. > - The picker previews every look in your own brand colour, so you see the difference before you commit. Lena runs a small day spa. Her brother Marco cuts hair three streets away. When Lena moved her bookings to Bookatu, Marco spent an evening poking at her page. He liked how it worked. He was less polite about the style. Her page read soft and calm, gentle corners, quiet colour, which was exactly right for a spa and exactly wrong for a barbershop. His words were roughly: if my page looks like a facial menu, my regulars will never let me hear the end of it. #### The same page has to carry very different shops This is a real problem for any booking platform. A spa, a barber, a tennis coach and a wedding photographer all need the same machinery underneath: services, staff, opening hours, payments. But the page should not feel the same to the person booking. A spa wants you to exhale. A barbershop wants to look sharp. When a platform hands everyone one template, somebody is always wearing the wrong outfit. So the Bookatu shop front comes with a set of looks, six of them, and you choose the one that fits. #### What a look actually changes A look works on feel, not structure. It sets the headline font and its weight, how rounded the cards and buttons are, and the soft wash of colour behind the top of your page. That narrow scope is deliberate. Because a look only touches those things, it can restyle your shop but it cannot break your layout. Your photos, your services, your prices and your reviews sit exactly where they were. - Auto, the default. Bookatu tunes the style to your industry, so a brand-new shop looks right on day one. - Editorial. Serif headlines, warm and unhurried, like a good magazine. Made for weddings, wellness and luxury salons. - Bold. Heavy, tight type with a vivid hero in your brand colour. Made for gyms, personal trainers and coaches. - Minimal. Thin type, lots of air, colour held back so your work leads. Made for photographers and studios. - Soft. Rounded and calm with a gentle glow. Made for spas, salons, nails and yoga. - Playful. Big round corners and a lively two-tone hero. Made for dance schools, kids classes and events. The suggestions are only suggestions. Nothing stops a nail salon going Bold or a barber going Editorial. It is your shop front, so it is your call. ![A Bookatu shop front page with services, opening hours and a booking button](https://bookatu.com/blog/shots/storefront-light.png) *A live Bookatu shop front. The look decides how this page feels. The services, the photos and the brand colour are yours either way.* #### Two clicks, honestly The picker lives in your settings under Shop-front look. Each look is a small card with a live preview drawn in your own brand colour. You are not imagining how Bold would sit with your deep green, you are looking at it. Tap the card, press Save look, and your public page wears it. Marco tried three on his first go. Bold, then Minimal, then Bold again. The whole detour took about a minute, and nobody touched a line of code or paid a designer. ![A barber chair in front of a mirror in a dark, sharp-looking shop](https://images.unsplash.com/photo-1503951914875-452162b0f3f1?auto=format&fit=crop&w=1200&q=70) *Same booking machinery as the spa three streets away, and a completely different feel.* > Every look is built around your brand colour. The type and the shapes change. The colour your clients already know does not. #### Why your colour never moves This matters more than it sounds. Your brand colour is the thing clients recognise from your sign, your cards and your Instagram. So the looks are built around it rather than painted over it. Pick Bold and that colour becomes a big confident wash behind your name. Pick Minimal and the same colour steps back to a hint. It is your colour doing the work either way, just at a different volume. #### And if you never touch the setting Then Auto quietly does the job. It reads what kind of business you run and tunes the page to match, which is why Lena barely used the picker at all. She opened it once, tapped Soft, and the change was gentle, because her page had already leaned calm from the start. That is the point of the whole feature. Owners who never think about design get a page that suits them anyway. Owners like Marco, who know exactly the feel they want, get a way to say so. Try a look with your morning coffee. If it is not you, pick another, or go back to Auto, and nothing else on your page will have moved. ### Promo codes that fill a quiet week and tell you what worked A code that expires tonight can fill this afternoon's chairs. Give it a channel and every booking it brings is counted, so next month you are not guessing whether the post worked. You read it in a table, in dollars. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/promo-codes-that-fill-quiet-weeks · markdown: https://bookatu.com/blog/promo-codes-that-fill-quiet-weeks.md > **The short version** > > - Create a code in about a minute: a percent or a dollar amount off, an expiry date, and a cap on how many times it can be used. > - Clients type the code when they book and the discount comes off before they pay. Expired or used-up codes are refused with a clear message. > - Give the code a channel, like Instagram, and every booking that uses it is counted under that channel on the same page. > - Copy a tracked share link for each place you post and see clicks next to bookings, so you know what people opened as well as what they booked. Priya runs a small nail salon. Saturday looks after itself. Tuesday does not. For a long time her plan for a slow Tuesday was to post something on Instagram and hope. Sometimes the day filled up a little, sometimes it did not, and she could never say whether the post had anything to do with it. Bookings do not arrive wearing a badge that says where they came from. So she stopped posting, because work she could not measure felt like work wasted. #### A code that only lives for a day On Monday night she opens Promo codes in her admin and creates one. The code is TUESDAY10. The type is percent off and the value is 10. She sets the expiry to Tuesday's date, which means the code works through the end of Tuesday and refuses everyone after that. She caps it at eight uses, because a discount is a cost, and eight bookings would fill her gaps without touching the weekend. Last, she sets the lead channel to Instagram. The whole form fits in one small card. It takes about a minute. The cap matters more than it looks. When the eighth booking uses the code, it flags as used up and stops being accepted. Priya does not have to watch a feed or switch anything off at the right moment. The limit she set on Monday night does the policing for her. #### The discount does its own maths Tuesday morning she posts a story. Today only, code TUESDAY10 when you book. A client taps through to her booking page, picks a manicure, types the code, and the price drops on the spot, before any card comes out. If someone tries the code on Wednesday it is politely refused, because it expired overnight. The urgency in her post was real, not theatre. One rule is worth knowing. A booking gets at most one discount, the best one on the table. If you also run a standing senior discount, a client who qualifies for both gets the better of the two, never both stacked. You cannot double-discount by accident, and the client always sees the fairer number. ![A nail technician painting a client's nails in a salon](https://images.unsplash.com/photo-1457972729786-0411a3b2b626?auto=format&fit=crop&w=1200&q=70) *A one-day code fills chairs you were paying for anyway.* #### Who actually sent the booking Here is the part that changes behaviour. Because Priya set the code's channel to Instagram, every booking that used TUESDAY10 lands under Instagram in a table on the same page called Where bookings come from. It lists each channel with its bookings and their booked value over the last 90 days. Not likes. Not reach. Bookings, in dollars. The page pairs that with tracked share links. She copies the link made for Instagram, puts it in her bio, and the page counts the clicks it gets. Clicks tell her what people opened. The bookings table tells her what paid. Even without a code, she can add a label to any booking link she shares, something like ?via=newsletter, and those bookings are counted under that channel too. > A discount with no name on it is a gift. A code with a channel is a test. #### Four ways to point a code at a quiet week - The one-day filler. Set the expiry to today, post it in the morning, and let it die at the end of the day. Some clients will use it to book later in the week, and that is still a booking you did not have on Monday. - A code per person. SARAH10 with the channel set to Sarah tells you whose word of mouth actually converts, which is worth knowing before you spend a dollar on ads. - The flyer test. Put a code with a strict cap on a cheap print run. If that channel is still empty after a month, you have your answer and it cost you very little. - The launch offer. A new treatment gets a code that expires in two weeks, so the first bookings and the first reviews arrive while the service is still new. #### End it without cleaning anything up Codes are easy to stop. Every code can be paused mid-offer and resumed later, and you can delete it when it is done. Expired and used-up codes mark themselves and stop working on their own. There is no batch of prices to put back, because the code never changed your prices. It only discounted the bookings that carried it. A month of Tuesdays later, Priya's promos page reads like a short report. What Instagram sent, and what it was worth. What the counter card with its own code sent, which in her case was nothing, so the counter card went in the bin. The next offer is not a hope posted into the void. It is a decision, made from a table that filled itself in while she worked. ### Your booking page speaks your clients' language Your clients should not have to book in a language they do not think in. Pick your booking page's language in one setting, let dates and prices follow, and keep your own dashboard in the language you prefer. The Bookatu team · 2026-07-11 · Grow your business · https://bookatu.com/en-nz/blog/booking-page-in-your-clients-language · markdown: https://bookatu.com/blog/booking-page-in-your-clients-language.md > **The short version** > > - Your booking page can run in English or in one of thirteen other languages. It is one setting, and the whole booking flow follows. > - The same setting controls how dates and prices are written, so a German page reads like a German page, not English with new words. > - Bookatu's own site and your dashboard follow you, not your clients. You can run the business in English while your clients book in German. > - Anything not translated yet shows in English instead of breaking, so the page always works. Linh runs a nail salon in Berlin. She grew up in the trade, her aunties all do nails, and most of her regulars are locals who think in German. Her old booking tool only spoke English. Clients could usually work it out. But every week a few gave up halfway and sent her a WhatsApp instead, and then she was back to typing appointments into her phone between sets. The bookings were coming in. They were just not coming in through the booking page. #### One setting, not a translation project In Bookatu the language of your booking page is a single setting. Open your settings, find Storefront language, and pick from the list. Linh picked Deutsch. From then on her booking page read in German. The service list, the picker for who does your nails, the calendar, the time slots, the confirmation screen. She translated nothing herself and she never touched her services. The names she gave them stay exactly as she wrote them, because those are her words. Everything around them switches. #### Dates and prices follow the language Language is more than the words on the buttons. A German client expects the date and the price to be written the German way, and a page that gets this wrong feels foreign even when every word is translated. So the storefront language setting carries formatting with it. Pick German and dates and prices come out the way German clients expect. The list also offers English in seven regional flavours, from New Zealand to Canada, and picking between those changes nothing about the words. It changes how dates and money are written, which is the part locals notice. The languages you can pick today: - English, in regional versions for New Zealand, Australia, the United Kingdom, the United States, Canada, Ireland and Singapore. - German, French, Spanish, Italian, Dutch and Portuguese. - Danish, Swedish, Norwegian, Finnish, Polish and Czech. - Japanese. One honest note. If some corner of the page has not been translated into a language yet, that piece shows in English rather than showing a blank. The page never breaks because of a missing word. ![A nail technician applying polish during a manicure](https://images.unsplash.com/photo-1457972729786-0411a3b2b626?auto=format&fit=crop&w=1200&q=70) *One setting changes the whole page. Your service names stay in your own words.* #### Your clients see their language, you see yours Here is the part owners usually miss, because most tools only have one language switch. Bookatu deliberately keeps two. Your booking page speaks the language of your business, the one you set for your clients. Bookatu's own pages and your admin dashboard follow you instead. There is a language picker on the site, your choice is remembered, and it never touches what your clients see. Linh reads her dashboard in English, because English is the language she has always used for business software. Her clients book in German. Neither side has to give anything up. > My clients book in German. I run the shop in English. Nobody has to switch for anybody. #### What if your clients speak two languages? Plenty of salons serve a mixed crowd, and Linh has a steady run of English speakers alongside her German regulars. The booking page shows one language at a time, so pick the one most of your bookings happen in. In practice this matters less than it sounds. The booking flow is short and visual. A client picks a service, picks a person, picks a time, and types their name. An English speaker can do that on a German page, especially since your service names are in whatever language you wrote them. And if your crowd shifts over the years, changing the page is the same single setting, not a rebuild. #### Set it in a minute If your clients speak a language your booking page does not, the fix is quick. Go to your settings, choose Storefront language, pick the language, save. Then open your own booking page and read it the way your clients will. Linh did this on a quiet Tuesday between appointments. The WhatsApp messages did not vanish overnight, and some regulars will always prefer to text a human. But the clients who used to stall halfway through an English page now finish in German, and every one of those is an appointment she no longer types in herself. ### Get the health history and consent signed before the client arrives A first facial should not start with a clipboard. Build your intake and consent form once, attach it to the right services, and clients fill and sign it on their phone before they walk in. The Bookatu team · 2026-07-11 · updated 2026-07-14 · Grow your business · https://bookatu.com/en-nz/blog/intake-consent-forms-before-clients-arrive · markdown: https://bookatu.com/blog/intake-consent-forms-before-clients-arrive.md > **The short version** > > - Build an intake or consent form once, with the fields you actually need. Short and long answers, tick boxes, single and multiple choice, dates, consent statements and a signature. > - Already have a paper form? Upload the PDF and Bookatu drafts the digital version for you to check. > - Tick the services that require it. When a client books one of those, the confirmation screen asks them to complete the form before their visit. > - Clients fill it on their phone and sign by drawing their signature with a finger. The answers are kept with the exact time they signed. > - Booked someone over the phone? Copy the form's link from your dashboard and text it to them. Priya runs a small skin clinic with two treatment rooms. For years, every first facial started the same way. The client arrived and got a clipboard in reception. Skin history on the front and medication questions on the back, with a consent line to sign at the bottom. Ten minutes later the form went into a drawer and the treatment finally began. She was selling a sixty minute facial and delivering fifty. The first thing a nervous new client experienced was paperwork. The fix was not a fancier clipboard. It was moving the questions to the day before, so the chair time is for the treatment. #### Build the form once, with the fields you actually need In Bookatu you build the form yourself, under Clients, then Forms. Give it a name, add a short description so clients know why you are asking, then add fields one by one. There are ten field types, and any field can be marked required, so the form cannot be submitted with that answer missing. - Short text, for quick answers like the name of their doctor. - Long text, for anything that needs room, like the skincare products they currently use. - Single choice or multiple choice, for a skin history checklist or picking one option from a set. - Dropdown, when you want one answer from a fixed list, like a skin type. - Consent statement, a line the client has to actively tick to agree to. - Date, for a date of birth or their last treatment. - Signature, where the client draws their signature to sign electronically. Priya kept hers short. Allergies, medications, previous reactions, a couple of consent statements, and the signature at the end. If a question did not change what she would do in the room, it did not make the form. If you already have a consent form on paper, you do not have to rebuild it from scratch. Upload the PDF and Bookatu reads it and drafts the digital version for you. Contact questions become fields that fill themselves in, and the lines a client signs against become consent statements they have to tick. You check the draft, adjust anything, then switch it on. ![The import screen: upload your consent PDF and Bookatu builds the digital version to review](https://bookatu.com/blog/shots/consent-pdf-import.png) *Already have a form on paper? Upload the PDF and start from a draft instead of a blank page.* #### Attach it to the services that need it When you save a form you tick the services that require it. Priya ticked her first facial and her peel, and left everything else alone. A regular booking a maintenance facial never sees it. From then on, when a client books one of those services, the booking confirmation screen shows one extra card. It says there is one quick step before the visit, with a button to complete the form. The client is already holding their phone, so the form gets done at home instead of in your reception. Each booking gets its own private link. It is a long random address, not something anyone could guess, and it stays tied to that client and that booking. If they close it and come back later, the same link still works. Once they have submitted, the page simply says the details are in, and the form cannot be filled twice. ![A prepared treatment room with fresh folded towels](https://images.unsplash.com/photo-1540555700478-4be289fbecef?auto=format&fit=crop&w=1200&q=70) *When the history and consent arrive before the client does, the room is ready for the treatment, not the paperwork.* #### A signature that happens on their phone The signature field is a box the client draws in with a finger, the same way they would sign a screen at a checkout. Every consent statement has to be ticked and every required field filled before the form will submit, so it cannot come back with the consent line skipped. The drawn signature is then kept with the client's printed name and the exact time of signing, tied to the booking. For a treatment that needs a consent record, you have one, and it is not in a drawer. ![A signed consent form in the dashboard, showing the answers and the client's drawn signature](https://bookatu.com/blog/shots/consent-admin-response.png) *What you see afterwards: the answers, the drawn signature, and the time it was signed.* > The first ten minutes of a new client's visit used to be admin. Now it is a conversation about their skin. #### For the client who booked over the phone Not every booking comes through the booking page. When Priya books someone over the phone, she taps Get fill link on the forms page and copies a fresh link to text or email. The same trick works when you want an existing client to sign an updated form after a policy change. Forms have an on and off switch too. Deactivate one and it stops being asked for, without deleting the answers you already collected. When Priya rewrote her peel consent, she switched the old form off and attached the new one to the service. #### Not just for clinics The same feature covers any question you are tired of asking at the door. - A patch test consent before a first colour appointment. - A health questionnaire before a first massage or personal training session. - Aftercare acknowledgement for lash, brow or tattoo work. - A simple photo permission, so you can ask once and keep the answer. #### What the first ten minutes are for now Priya's new clients walk past reception and straight into the room. She has read their answers before they arrive, so she opens with a question about their skin instead of a pen and a form. The hour she sells is the hour she delivers. The clipboard did not survive the change, and nobody misses it. ### Turn a cancellation into a booking with the waitlist Your best day is one text away from having a hole in it. Here is how the waitlist fills a Saturday cancellation in minutes, with the slot offered to the clients who already asked for it. The Bookatu team · 2026-07-11 · updated 2026-10-30 · Reduce no-shows · https://bookatu.com/en-nz/blog/turn-cancellations-into-bookings-with-the-waitlist · markdown: https://bookatu.com/blog/turn-cancellations-into-bookings-with-the-waitlist.md > **The short version** > > - Clients can join your waitlist straight from your booking page when the day they want is full, for a specific service or for any service. > - The waitlist screen shows everyone waiting, and regulars carry a badge with what they have spent with you, so you know who to offer first. > - Tap Offer a slot, type the time, and the offer goes out by email. Text and WhatsApp appear as options once you have connected them. > - When you cancel a booking in Bookatu, the freed slot is also offered to your best-matched waiting clients automatically, each with a one-tap claim link. The first to claim gets it. Mel runs a four-chair hair salon, and Saturday is her best day. This one was fully booked by Wednesday. Then at 9:40 in the morning a text arrived: her 2pm colour had a sick kid at home and could not come in. That was her longest, most valuable booking of the day, gone. The old routine was grim. Scroll through her phone trying to remember who had asked about Saturdays, message four people, then get two replies at 6pm when the day was already over. Most of the time the slot just died. #### A list of people who already said yes The waitlist flips that. It is a list of clients who have already told you they want in. On the Waitlist screen Mel sees everyone who is waiting, newest first. Each card shows the service they want, the dates and times that suit them, any note they left, and how long ago they joined. Her regulars carry one thing more: a badge showing what they have spent with her over time. When there is one slot and six people waiting, that badge answers the hard question. You can offer the spot to the client who has been coming in for years, not just whoever messaged last. #### Offer the slot in one tap Mel picks Priya, a colour regular with a healthy lifetime badge who had asked for exactly this kind of Saturday. She taps Offer a slot, types "Saturday at 2pm with Mel", and sends it. Priya gets a short message saying a spot has opened up, with the time and a link to book. Email works out of the box, with nothing to set up. If the salon has connected text or WhatsApp, those show up in a dropdown too, and Mel can pick whichever one Priya actually reads. The card gives her other ways to close it as well. There is a tap-to-call button if she would rather ring. There is a Book now button that opens a new appointment with the client and their service already filled in, for the ones who reply "yes, book me". Once the slot is taken, Mark booked clears that client off the list, and everyone else stays on it for the next opening. ![A calm salon interior with a row of empty chairs](https://images.unsplash.com/photo-1560066984-138dadb4c035?auto=format&fit=crop&w=1200&q=70) *One freed chair on a full Saturday. The waitlist already knows who wants it.* > The 2pm was rebooked before I had finished my ten o'clock blow wave. Nobody rang around and nobody begged on Instagram. #### The automatic version, for when you are mid-foil Mel likes choosing who gets the slot. If you would rather not think about it at all, cancelling the booking in Bookatu does the work for you. The moment a booking is cancelled, Bookatu looks for waiting clients whose request fits the freed slot. It checks the service, the staff member if they asked for one, and the date window they gave. Then it messages a small group of the best matches, ranked by how much each client spends with you, so your most loyal clients hear about the opening first. Each of those offers carries a claim link. The first client to claim it gets the slot. If the service takes a deposit, the slot is held while they pay it and released if they do not. If you have booking terms, they tick them first, and a service with a required booking question takes them to your booking page to answer it. Anyone who taps later sees that it has already been taken. Offers go out by email as standard, and if you have text messaging set up and the client has opted in, the offer goes by text as well. A client who has already been offered the opening is not pestered about it again. #### How clients join the list None of this works without names on the list, and Bookatu collects them at the exact moment of disappointment. When a client picks a day on your booking page and nothing is left, they see that you are fully booked, with a Join the waitlist button right there. The service they were trying to book carries over, already selected. You also get a public waitlist link you can share anywhere, like your Instagram bio or a reply to a DM. The join form takes about a minute. A client leaves: - Their name, plus a phone number or an email or both. - The service they want, or any service if they just want a chair. - The earliest and latest dates that work for them. - Whether mornings, afternoons or evenings suit, and a note if they have one. That detail is what makes offers feel personal instead of spammy. Someone who asked for a Saturday colour never gets pinged about a Tuesday trim. To switch the whole thing on, open Settings, find What clients see, and turn on Waitlist. #### A cancellation is only lost if the slot stays empty Cancellations are not going away. People get sick and plans fall over, usually on your busiest day. What you can change is what happens in the ten minutes after that text lands. With a waitlist, a cancellation becomes a message to someone who was hoping you would get in touch. The 2pm that fell out of Mel's Saturday went to a regular who was delighted to take it. The day stayed full, and nobody spent their lunch break ringing around. ### Know what your retail shelf is worth A salon that sells skincare, polish and haircare should be able to see what is running low and what the whole shelf is worth. Here is how to turn on stock tracking and read that one number. The Bookatu team · 2026-07-07 · Grow your business · https://bookatu.com/en-nz/blog/know-what-your-retail-shelf-is-worth · markdown: https://bookatu.com/blog/know-what-your-retail-shelf-is-worth.md > **The short version** > > - Put a stock number on any product you want to track. Leave it blank and that product is not tracked. > - The products page flags what is low and what is out, and shows a running total of what the whole shelf is worth at retail. > - That number helps you reorder on time, back up an insurance claim, sort out your tax, and spot stock that is not selling. > - Log deliveries as they arrive, and every change lands in a ledger you can export for your accountant. Nadia's salon has a shelf by the front mirror. Skincare on the top row, nail polish in the middle, haircare below. Clients pick things up while they wait, and a good week clears half of it. For three years that shelf was a bit of a mystery to her. She knew roughly what sold, but she could not have told you how many bottles of the leave-in conditioner were sitting there, or what the whole shelf was worth if someone asked. When her polish supplier rang to take a reorder, she guessed. Some weeks she ran out of the shade everyone wanted and sat on twelve of one nobody touched. #### Turn tracking on, one product at a time You do not have to track everything on day one. In Bookatu each product has a stock field. Type a number into it and that product is tracked from then on. Leave it blank and it is not tracked at all, which is fine for a tester or an add-on you are not counting. Nadia started with the ten things that actually move. Two cleansers, a serum, three polishes, a leave-in, a dry shampoo, and two hair oils. She counted what was on the shelf, typed those numbers in, and that was the whole setup. Each product can also carry a reorder point, the level where you want a nudge to buy more. Leave it blank and it defaults to three. When a product drops to or below that number it flags as low. When it hits zero it flags as out. You are setting the line once, not watching the shelf every day. #### See what is low, what is out, and what it is all worth Once a few products are tracked, the products page does the watching for you. Near the top there is a line that reads something like "Time to reorder: 2 out of stock, 3 running low", so you get the shortlist without scrolling. Anything at or under its reorder point wears a Low stock tag. Anything at zero wears an Out of stock tag. Nadia stopped finding out she was empty only when a client asked for the thing she had just sold the last of. ![A sleek, modern salon studio](https://images.unsplash.com/photo-1633681926022-84c23e8cb2d6?auto=format&fit=crop&w=1200&q=70) *The products page keeps the running count for you, so the shelf stops being a guess.* The products page now also shows a total stock value across everything you track. It is the plain sum of each product's on-hand quantity times its price, shown in your own currency. Eight cleansers at forty dollars and ten polishes at eighteen, and the total counts them all. This is a retail figure, the price you would sell it for, not what you paid your supplier. There is no separate cost field per product, so the value is your shelf priced as you sell it. The same figure rides along in the stock export too, with a retail value on every row, so the sheet you hand over already has the maths done. #### The number that matters One number sounds small until you need it. Here is where owners reach for it: - Reordering. When you can see which products are running low and roughly what each is worth, you place one sensible order instead of a panic buy or a shelf full of dead stock. - Insurance. If something goes wrong, a leak or a break-in, your insurer wants a value for the stock you lost. A shelf you can price on the spot is far easier to claim than a rough guess from memory. - Tax and end of year. Your accountant often needs a stock figure at a set date. Having it ready, with a ledger behind it, saves the shoebox reconstruction later. - Dead stock. The value line quietly shows you the money sitting still. If a shade has not moved in months, that is cash on a shelf, and now you can put it on sale or stop reordering it. > A shelf you cannot count is money you cannot see. #### Keep the count honest as deliveries land The count only stays right if you feed it. When a delivery arrives, open the receive-stock screen, log what came in, and those quantities add to what is already on the shelf. You can put a unit cost on each line if you want it for your own cost-of-goods notes. Nadia does hers while she unpacks the box, so the shelf on screen matches the shelf on the wall by the time the kettle has boiled. Everything that moves a count lands in the stock ledger. A sale, a delivery, an adjustment, a stocktake, a refund. Each row carries a plus or a minus, a reason, and a note, and you can export the lot as a CSV. That is what turns "I think we had about twenty" into a line your accountant can actually use. None of this asks for a big system or a spare afternoon. Put a number on the products you care about, glance at the reorder line when you open up, and let the value total tell you what your shelf is holding. The shelf stops being the corner of the salon nobody watches and becomes one you can plan around. ### How to do a stocktake from your phone, no clipboard needed A physical stock count without printing a list or sitting at a laptop. Walk the shelf, type what you actually count, and let the system correct your on-hand and log the difference so you can see what walked off. The Bookatu team · 2026-07-07 · Grow your business · https://bookatu.com/en-nz/blog/do-a-stocktake-from-your-phone · markdown: https://bookatu.com/blog/do-a-stocktake-from-your-phone.md > **The short version** > > - Open the Count stock page and type what you actually count as you walk the shelf. No clipboard and no laptop. > - Leave a product blank to skip it. Type a plain 0 to empty a shelf you have sold out of. > - The system corrects your on-hand and logs the difference to the ledger, so you can see what walked off. > - Every product shows when it was last counted, so month-end stops being a mystery. Most stocktakes start the same way. You print a list and grab a pen, then squint at a shelf while the phone rings. By the time the numbers reach a laptop and get typed in, half of them are wrong and you have lost an hour you did not have. So the count gets skipped, and you only find out something is off when you run out of a colour halfway through an appointment. #### Walk the shelf with the page in your hand The Count stock page is built for the shelf, not the desk. Open it on your phone and your product list is there, ready to fill in. You walk along and type what you actually count as you pick up each bottle. That is the whole method. There is no second app to sync and no spreadsheet to reconcile at the end. What you type on the shelf is what the system saves. #### Blank skips it, a zero empties it You will not count everything every time, and you should not have to. Leave a product blank and the count passes over it, leaving your on-hand exactly as it was. Only the products you type get touched. When you have genuinely sold out of something, type a plain 0 and that shelf is emptied. The difference is small but it matters. Blank means you did not check this one. Zero means you did, and there is none left. ![A bright, modern studio with a tidy retail shelf](https://images.unsplash.com/photo-1633681926022-84c23e8cb2d6?auto=format&fit=crop&w=1200&q=70) *The count lives on your phone, right there at the shelf. What you type is what gets saved.* #### The system does the maths and remembers the date When you save, the page compares what you counted against what it thought you had. It corrects the on-hand to match reality and writes the whole thing in one go. If you close the tab, nothing is left half done. Each product then shows when it was last counted, so at a glance you know what is fresh and what has not been checked in months. Your Low stock and Out of stock flags start telling the truth again, because the numbers behind them are real. #### See what walked off Here is the part that earns the five minutes. Every correction is written to your stock ledger as a count movement, with the plus or minus and a short reason. So you are not only fixing a number, you are keeping a dated record of the difference. If you expected twelve of a hand cream and counted nine, the ledger shows minus three against that product for that day. Do that each month and a pattern turns up. A line that is always short is worth a quiet look at your back bar. > A number that is quietly wrong every month is trying to tell you something. The ledger is where you finally hear it. Done as a habit, a monthly count gives you more than a tidy shelf: - A true on-hand figure, so your reorder flags fire at the right time instead of after you run out. - A dated record of every shortfall, ready to export to CSV when your accountant asks. - An early warning on the products that keep going missing, before the loss quietly adds up. - A five-minute job at the end of a shift instead of an afternoon lost to a clipboard. #### Make it a habit, not an event The reason to do this on your phone is that you will actually do it. A count you can finish in the last five minutes of a shift is a count that happens. Pick a rhythm that fits your week, the end of the month or every Friday, and walk the same shelf each time. Because the page remembers when each product was last counted, you can split it up. Do the polishes today and the retail wall tomorrow, and the ledger stitches the record together for you. None of this asks you to learn accounting. You count what is in front of you. The system handles the difference and the record builds itself. That is how a stocktake goes from the job you keep putting off to the short walk that shows you where your money actually went. ### Move your stock spreadsheet into Bookatu without retyping it You already keep your retail in a spreadsheet with columns like Brand, Item, SKU, In Stock and Price. Save it as a CSV and import it. Bookatu reads your column names as they are, matches on SKU so nothing duplicates, and a price-only sheet updates just prices. The Bookatu team · 2026-07-07 · Grow your business · https://bookatu.com/en-nz/blog/move-your-stock-spreadsheet-into-bookatu · markdown: https://bookatu.com/blog/move-your-stock-spreadsheet-into-bookatu.md > **The short version** > > - Export a CSV from your spreadsheet and import it. You do not retype your stock into Bookatu by hand. > - Bookatu reads common column names as they are, like Brand, Item, SKU, In Stock, Reorder At and Price. You do not rename your headers. > - A row whose SKU matches a product you already have updates that product instead of making a duplicate. > - A slim sheet with just name, SKU and price updates only prices. Your stock counts, photos and categories stay put. Say you already run your retail on a spreadsheet. One row per product, with columns for Brand, Item, SKU, In Stock, Reorder At, Price, and a Sale Price for the things you have marked down. It works. The last thing you want to hear is that moving to a real system means typing all of it in again, one product at a time, on a small screen after closing. So here is the good news. You do not have to. You can hand Bookatu the sheet you already keep. #### Save your sheet as a CSV, then import it A CSV is just your spreadsheet saved as plain text. In Excel or Google Sheets you pick Save As, or Download, and choose CSV. Then in Bookatu you go to your products page, open Import, and upload that file. Bookatu reads it row by row and creates a product for each one. Up to 500 rows go in at once. If you would rather start from what Bookatu already has, use Export first. That gives you a full stock sheet you can edit in your spreadsheet and send straight back through Import. #### You keep your own column names This is the part that saves the retyping. Most tools make you match their fields to yours before anything imports, which is its own little chore. Bookatu recognises the names people actually use. A column called Item or Product becomes the product name. In Stock becomes the number on hand. Reorder At becomes the point where a product flags as low. Brand, SKU and Price come across as themselves. You do not sit there renaming headers to match a template. You upload the sheet you already have. ![Retail shelf products, oils and a candle, in a calm salon](https://images.unsplash.com/photo-1556760544-74068565f05c?auto=format&fit=crop&w=1200&q=70) *Your shelf lives in a sheet today. It can live in Bookatu tomorrow without a single row retyped.* #### A Sale Price shows the old price struck through If your sheet has a Sale Price column, Bookatu treats it as the current selling price and shows the regular Price struck through next to it, the way a real markdown looks. It only does this when the sale price is actually lower than the regular one. Put the same number in both and nothing gets crossed out. So the retail markdowns you already track in your spreadsheet arrive looking like markdowns, not like two prices sitting side by side. #### Matching SKUs update, they do not duplicate The SKU is the code that makes this safe to do more than once. When you import, Bookatu looks at the SKU on each row. If that SKU already belongs to a product, the row updates that product. If the SKU is new, it makes a new product. So you can import today, sell for a month, then import an updated sheet next month and nothing doubles up. Same file, same SKUs, one clean update. - First move. Bring your whole spreadsheet in once and skip the manual entry. - A price change across a range. Send an updated sheet and let the matching SKUs take the new prices. - A new delivery of lines you already stock. Update the ones that match and add the genuinely new ones in the same file. - A seasonal markdown. Fill in the Sale Price column and re-import to show the old price struck through. #### A price-only sheet changes only prices Sometimes all you want to change is money, not the whole product. A slim sheet does exactly that. If you upload a file with just the name, SKU and price columns, Bookatu updates only those and leaves everything else alone. Your stock counts do not reset. Your photos, descriptions and categories stay where they are. This is the sheet to use when a supplier raises prices and you want the new numbers in without risking the rest of your catalogue. > Hand the system the sheet you already keep. That is the whole idea. None of this asks you to change how you already work. Keep your spreadsheet if you like it. Export a fresh copy from Bookatu whenever you want a clean stock sheet, edit it where you are comfortable, and send it back. The point is that your stock only gets typed once, and you already did that. Bookatu just meets your sheet where it is. ### The checklist that keeps every shift running the same You cannot be on the floor for every shift, and standards quietly slip when you are not. A daily checklist your team ticks off on their phones is the plain, boring fix that actually works. The Bookatu team · 2026-07-06 · Grow your business · https://bookatu.com/en-nz/blog/salon-daily-checklist-opening-closing · markdown: https://bookatu.com/blog/salon-daily-checklist-opening-closing.md > **The short version** > > - Write down the daily jobs once: opening, between clients, and closing. > - Your team opens the list on their phone and taps each task as they finish it. > - Every tick records who did it and when, so you can see the day at a glance. > - The list clears itself each morning, ready for the next shift. There is a version of your salon that only exists when you are standing in it. The tools go back in the steriliser without being asked. The reception desk gets wiped before the first client sits down. The last person out checks the back door and sets the alarm without thinking. You built those habits, and on the days you are there, they hold. Then you take a Tuesday off, or you are stuck in the treatment room all afternoon, and the salon runs a little looser. Nobody means for it to happen. A junior is not sure whether the lamps get wiped daily or weekly. A busy stylist forgets the towels are still in the machine. It is never a disaster, just a slow drift, and the first you hear of it is a client mentioning the bathroom was out of hand soap. #### Standards live in your head, and that is the problem Most salon owners keep the running of the place in their own head. You know the order things happen in, the little checks that keep it hygienic and calm, the jobs that only matter if they are done every single day. The trouble is that a head is a bad place to store a shared standard. Nobody else can read it. When a new starter joins, they learn it by watching, guessing, and being corrected, which is slow for them and tiring for you. A checklist takes what is in your head and puts it somewhere everyone can see. Not a laminated sheet that goes missing behind the desk, and not a paper pad that only you ever look at. A living list, on the phone that is already in every pocket, that says plainly: here is what a good day looks like, here is your part in it. #### What a good daily list actually contains The best lists are shorter than you expect and grouped by when things happen. You do not need a hundred rules. You need the handful of jobs that keep the place clean, safe and ready, split into the three moments of the day. - Opening: unlock and set the temperature, check the day's bookings, set up and sanitise each station, warm the wax pot, get the front desk client-ready. - Between clients: wipe the station, bin the single-use items, return metal tools to the steriliser, reset for the next person. The jobs that protect one client from the last. - Closing: deep clean the stations, run the final steriliser cycle, empty the bins, mop, cash up, lock up and set the alarm. > The point is not to police your team. It is to make the right thing the easy thing, on every shift, whoever is on. #### Why ticking it off on a phone changes things A paper checklist has one job: to be a list. A checklist on a phone can do more. When someone taps a task done, it records their name and the time. You are not standing over anyone, but at the end of the day you can glance at who did what and see the shift for what it was. If the closing jobs were all ticked by half past six, you know the place was left right. If a whole section is blank, you know to have a quiet word. It also resets on its own. Yesterday's ticks do not carry over. Every morning the team opens a fresh list, which is exactly how a daily standard should work. Nobody has to rub anything out or start a new page. #### It is really a training tool The quiet win is with your juniors. A new starter with a clear checklist stops asking whether the lamps get wiped daily, because the list already tells them. They can work through their jobs with confidence, and you can see at a glance that they did. Some owners give an apprentice a login that shows only the checklist and nothing else, so a brand-new team member has one simple, safe thing to focus on while they learn the rest. None of this is glamorous. It is opening the salon, keeping it clean, and closing it properly, done the same way every day whether you are there or not. That consistency is what a client feels the moment they walk in, and it is worth writing down. ### How to fill your weekly classes and keep them full A class at a fixed time with a spot limit is the easiest thing you sell, if people can see it, book it and pay for it without texting you. Here is how to turn a weekly class into a standing, self-filling booking. The Bookatu team · 2026-07-06 · Recurring revenue · https://bookatu.com/en-nz/blog/fill-your-weekly-classes-and-keep-them-full · markdown: https://bookatu.com/blog/fill-your-weekly-classes-and-keep-them-full.md > **The short version** > > - Set the class for a fixed day and time, with a limit on spots. > - Let people book and pay online, so a spot is only held once it is paid for. > - Set it to repeat, so next week's class is already there to book. > - The same regulars grab the same slot each week, and the class fills itself. A weekly class is a lovely thing to run and a fiddly thing to fill. The class itself is simple: same time, same place, a set number of people. The filling is where it goes sideways. You end up counting heads from a group chat, holding spots for people who said maybe, and chasing the ones who owe you for last week while you are meant to be teaching. It does not have to be like that. A class is actually the easiest thing you sell, because it is the same every week. Once you set it up properly, it can fill itself. #### Give the class a spot limit, and let the page count The first fix is to stop counting. Set the class up with a real limit, say ten spots. When eight people have booked, the page shows two left. When the tenth books, it shows full, and there is no way to squeeze in an eleventh. You never scroll back through a chat again. You open the page and see exactly who is coming. That little 'two spots left' does quiet work for you, too. People book faster when they can see a class is nearly full. It is not a trick, it is just true, and showing it turns a maybe into a booking. #### Take the money when they book The second fix is to take payment online at the moment someone books, not later. A spot is held once it is paid for, and not before. This is the single biggest change for most class-runners, because it ends the whole cash-and-owed mess in one go. No more twenty-dollar notes in a kit bag. No more trying to remember who paid and who keeps saying they will bring it next time. > A paid spot is a kept spot. When people pay to book, they turn up, and the ones who were never really coming quietly stop holding places. #### Set it to repeat, and let the regulars settle in The third fix is the one that makes a class fill itself. Set it to repeat weekly. Next Tuesday's class is already there to book, and the one after that. Your regulars can grab their usual slot a few weeks ahead, and some of them will book a month at a time. You get to watch your weeks fill up before they have even started, which is a very different feeling from wondering each Sunday whether anyone is coming. When someone new wants in but the class is full, put them on a waitlist instead of turning them away. If a regular drops out, the next person slides in, and you never teach to a half-empty room because of one no-show. #### Share it where your people already are The last piece is getting the class in front of people. You do not need a marketing budget. You need one link. Share the class link in your group chat, in your bio, in a story, in the message you send new enquiries. Every share sends people to a page where they can see the times, see how many spots are left, and book in seconds. If a class is private, for a members-only group or a closed clinic, you can keep it off your public page and share the link only with the people you want. Put those together, a spot limit, payment on booking, a repeating slot and a link you can share, and the weekly class stops being the fiddly part of your week. It becomes the reliable part, the standing booking that quietly refills itself while you get on with the teaching you actually love. ### Get clients rebooking before they leave the chair The best moment to book the next visit is while your client is still in front of you, happy and relaxed. Miss it, and you are relying on them to remember weeks later. Here is how to make rebooking the norm, not the exception. The Bookatu team · 2026-07-06 · Recurring revenue · https://bookatu.com/en-nz/blog/get-clients-rebooking-before-they-leave · markdown: https://bookatu.com/blog/get-clients-rebooking-before-they-leave.md > **The short version** > > - Ask for the next booking while the client is still with you, not after they leave. > - For clients on a rhythm, set the appointment to repeat so it books itself. > - Give people a link to book their own next visit whenever it suits them. > - A gentle reminder to lapsed clients brings back the ones who simply forgot. Here is a number that should bother you a little. A client who rebooks on the spot, before they walk out, is far more likely to actually come back than one who leaves saying they will call to sort it out. Same client, same happiness with the work, wildly different odds. The only thing that changed is when you asked. Rebooking is not really a marketing problem. It is a timing problem. The moment a client is most likely to book their next visit is the moment they are enjoying this one. Let that moment pass and you are relying on a busy person to remember, weeks later, to pick up the phone. Most of them mean to. Life gets in the way. #### Ask while they are still with you The simplest change costs nothing and works better than any campaign. Before the client stands up, book the next one. Colour clients on a six-week cycle, a fortnightly massage, a monthly cut. You already know roughly when they are due. So say it out loud: same time in six weeks? Then put it in the diary while they are nodding. If you take card payments, you can even take the deposit for the next visit there and then, which turns a friendly intention into a firm booking. The client leaves knowing exactly when they are next in, and you leave with a diary that is filling itself from the inside. #### For your regulars, let it repeat Some clients come like clockwork. The every-fourth-Saturday client. The Wednesday-lunchtime regular. For those, do not rebook one at a time. Set the appointment to repeat, so the next several are already in the diary, held for them. They never have to ask, and you never have a gap where their standing slot should be. > A repeating booking is the calmest kind of revenue. It is money you can see coming, from people who already love what you do. #### Give them a way to book themselves Not everyone wants to sort their next visit at the desk, and not everyone is due on a neat cycle. For them, the answer is a booking link they can use whenever it suits, at eleven at night when they remember, on the bus, whenever. Your page shows your real availability, so they pick a time that actually works and it lands in your diary. No phone tag, no back and forth, no front desk needed. The easier you make it to rebook, the more people do. #### And catch the ones who drifted However good you are at rebooking, some clients still slip through. They had a great visit, meant to come back, and then three months went by. These are not lost clients. They are forgetful ones, and they are the cheapest bookings you will ever win back, because they already like you. A short, warm message to a client you have not seen in a while does the trick. Not a hard sell. Just a hello, we would love to see you, here is a link to book whenever suits. Send it to the handful of people who have drifted past their usual gap, and a good number of them will book. It is the quietest, kindest form of marketing there is: reminding people who already chose you that the door is open. Put it together and rebooking stops being something you hope for and becomes something your day does on its own. Ask at the chair. Repeat for the regulars. Hand everyone a link. Nudge the ones who wandered off. None of it is clever. All of it is the difference between a diary you fill from scratch each week and one that mostly fills itself. ### Online booking for photographers: shoots, deposits and delivering the gallery How a wedding and portrait photographer stopped chasing enquiries over DM, took a deposit at the moment of booking, and delivered the finished gallery through the same link the client already had. The Bookatu team · 2026-07-05 · Grow your business · https://bookatu.com/en-nz/blog/online-booking-for-photographers · markdown: https://bookatu.com/blog/online-booking-for-photographers.md > **The short version** > > - Put your shoot types online so a client can pick a session, see the price, and book a date without a single DM > - Take a deposit at the moment of booking, so a held Saturday is a real commitment, not a maybe > - Deliver the finished photos through a private gallery the client logs into with their own email > - Sell the extras: let them favourite the shots they want beyond the included set and pay for the rest before the full-resolution download unlocks Maddie shoots weddings and family portraits out of a spare room in West Auckland. For the first two years her whole booking system lived in her Instagram DMs. Someone would message asking about a spring mini-session, she'd reply with prices, they'd go quiet, she'd follow up a week later, they'd say they were still keen, and somewhere in that slow back-and-forth half of them drifted off. The ones who did book sometimes forgot, because a message thread is not a commitment. #### A booking page that answers the questions for you The thing eating Maddie's evenings was answering the same three questions: what do you offer, how much is it, and are you free on this date. A booking page answers all three at once. She listed her session types the way a menu lists dishes: a classic portrait session, a mini-session, a full wedding day, each with a length and a price already on the card. A client opens the page, sees the price without asking, picks a date from her real availability, and books. No thread. No follow-up. She wakes up to a booked Saturday instead of a question about one. #### A deposit turns a maybe into a yes A held date with nothing behind it is the most expensive thing a photographer owns, because you turn other people away to keep it. So Maddie put a deposit on every session. When a client books, they pay a set amount up front, and the rest is due on the day. The money lands straight in her account, not held by a platform. The effect is not really about the cash. It's that a person who has paid a deposit shows up, and a person who hasn't sometimes doesn't. The no-shows that used to cost her a whole Saturday mostly stopped. > The deposit was never about the money on the day. It was about knowing the day was actually real. #### The gallery lives at the same link Here is the part that surprised her. The client who booked the shoot already has a login to Maddie's site, tied to the email they booked with. So when the edits are done, she uploads them into a private gallery on that same account, and the client sees their photos where they already expect to look. No new tool to learn, no third-party proofing site with its own password, no zip file that fills up an inbox. They open the link they already had, and there are their photos. The gallery does two jobs at once. It delivers the work, and it sells the extras. Maddie includes a set number of edited photos in the price, and the client hearts the ones they want. If they fall in love with more than the included set, the gallery shows exactly what the extras cost, they pay, and only then does the full-resolution download unlock. Until they do, every image is a watermarked, web-resolution proof. A determined person can screenshot a preview, but all they get is the watermarked version, which is the whole point. #### What she stopped doing - Answering price-and-availability DMs one at a time, at night, after a full day of shooting - Chasing deposits by bank transfer and reconciling who had actually paid - Paying for a separate proofing and gallery tool on top of everything else - Losing the extra-print and extra-photo sales that used to slip away in a follow-up email nobody sent None of this asks a photographer to become a business person overnight. You put your sessions online, you switch on a deposit, and you deliver the gallery where the client already is. The admin quietly moves off your evenings, the no-shows fade, and the extra sales that used to fall through the cracks turn up on their own. You get the evenings back for editing, or for not editing, which after a wedding season is its own kind of luxury. ### How to cut no-shows: deposits, reminders and a cancellation window people respect No-shows aren't bad luck, they're a system gap. Here's the three-part setup that turns a hopeful booking into one that actually turns up, without treating your good clients like suspects. The Bookatu team · 2026-07-05 · Reduce no-shows · https://bookatu.com/en-nz/blog/reduce-no-shows-deposits-reminders · markdown: https://bookatu.com/blog/reduce-no-shows-deposits-reminders.md > **The short version** > > - A reminder the day before catches the honest forgetters, which is most of them > - A deposit catches the rest, because people show up for money they've already put down > - A clear cancellation window gives people a fair way out and gives you the slot back in time to refill it > - Set it once and it runs quietly in the background, so you're not policing anyone A no-show feels personal, but it almost never is. Someone books on a Tuesday for a Saturday, life happens in between, and by the weekend the appointment has quietly fallen out of their head. They're not being rude. They just never got a nudge, never had any money on the line, and never had an easy way to cancel that didn't involve an awkward phone call. Fix those three things and the empty chairs mostly go away. #### The reminder catches the forgetters Most no-shows are not people avoiding you. They're people who forgot. A short email the evening before, with the time and the place and a one-tap way to rebook if they can't make it, catches the large majority of them before they become an empty slot. It costs you nothing to send and it does the work of a receptionist who never forgets and never sleeps. Turn this on first, before anything stricter, because it solves most of the problem on its own. #### The deposit catches the rest A reminder can't help you with the person who books three places for the same Saturday to keep their options open. For that you need a little money on the line. A deposit, even a small one, changes the maths: a booking someone has paid toward is a booking they keep, because walking away now costs them something real. You don't need to charge the full price up front. A modest deposit that comes off the final bill is enough to turn a casual hold into a real commitment, and the money goes straight to you. > You're not trying to punish anyone. You're trying to give the flaky booking a reason to become a real one. #### The cancellation window keeps it fair The last piece is the one people skip, and it's the one that keeps the whole thing feeling fair. Set a clear window: cancel more than a day ahead and your deposit comes back, cancel inside the window or don't show and it doesn't. Say it plainly at the point of booking so nobody is surprised. Now a genuine change of plans has an honest, no-drama way out, and you get the slot back with enough notice to offer it to someone on the waitlist. The client who cancels early is doing you a favour, and the policy quietly rewards them for it. #### Set it once, then leave it alone The best version of this runs without you thinking about it. The reminder sends itself the evening before. The deposit is taken at the moment of booking. The cancellation window enforces itself. You are not chasing anyone, not sending guilt-trip texts, not deciding case by case who owes you what. You set the rules once, in plain language, and then you get on with the actual work while the empty chairs quietly become full ones. ### Take bookings online without paying commission on every client Marketplace booking apps take a cut of every new client, forever. Here's why a booking page you own costs a flat fee instead, and what that difference adds up to over a year. The Bookatu team · 2026-07-05 · Recurring revenue · https://bookatu.com/en-nz/blog/zero-commission-online-booking · markdown: https://bookatu.com/blog/zero-commission-online-booking.md > **The short version** > > - Marketplace apps advertise 'free' booking, then take a percentage of every new client they send you, on every visit, for as long as that client keeps coming > - A booking page you own charges a flat monthly fee instead, so a client who visits twelve times a year costs you the same as one who visits once > - Your clients, their contact details and their booking history stay yours, not the platform's > - Payments go straight to your own account, minus the normal card processing fee, with no platform cut on top The pitch from the big marketplace apps sounds generous. Free to list, free to take bookings, only pay when we send you someone new. It sounds like they only win when you win. Then you read the fine print on 'new client', and you notice that a client counts as new the first time they book through the app, and that the commission is not a one-off finder's fee. It's a cut of that person's spending, on every visit, for as long as they keep booking through the app. You introduced them years ago and you're still paying rent on the relationship. #### What the commission actually costs Run the numbers on a single loyal client. Say they come in once a month and spend eighty dollars, and the marketplace takes twenty percent of new-client bookings. If the app decides that client is 'theirs', that's sixteen dollars a visit, nearly two hundred dollars a year, out of one regular. Now multiply by every regular the app has ever touched. The 'free' booking tool turns out to be the most expensive line in the business, and it grows every time a client is loyal, which is exactly backwards from how it should work. > You should not have to pay a platform a cut of your best client's tenth visit. You already earned that one. #### A flat fee doesn't punish loyalty A booking page you own works the other way around. You pay a flat monthly fee for the software, and then it's yours. A client who books once and a client who books fifty times cost you exactly the same, because the fee is for the tool, not a tax on the relationship. The more loyal your clients are, the better the deal gets, which is the incentive you actually want. Payments go directly to your own account, with only the normal card processing fee that any business pays, and no platform slice on top. #### The clients are yours, too There's a quieter cost to the marketplace model that doesn't show up on an invoice. On a marketplace, the client belongs to the platform. Their email, their phone number, their history, the ability to send them a win-back offer when they've been away, all of it sits behind the app's login. If you ever leave, you leave without them. On a booking page you own, the client list is yours. You can email them, reward them, bring them back, or move to different software entirely and take every one of them with you. #### When does the flat fee win Do the simple sum for your own shop. Take your rough monthly bookings, work out what a percentage app would skim off the ones it counts as theirs, and compare it to a flat monthly fee. For most businesses with even a handful of regulars, the flat fee wins the moment the second loyal client walks back through the door. After that, every repeat visit is one the platform used to tax and now doesn't, and that difference is yours to keep, reinvest, or simply not hand over. ### Run your dojo's weekly timetable online, from beginner class to rained-out park session How a small BJJ and striking gym swapped a whiteboard timetable for an online class schedule that books and pays for itself and handles rained-out outdoor sessions, then rewards the members who bring their friends along. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/martial-arts-dojo-class-booking · markdown: https://bookatu.com/blog/martial-arts-dojo-class-booking.md > **The short version** > > - Put your weekly timetable online so people can see every class and book and pay for a spot in one go > - Group sessions have a set date, a spots cap, a venue with directions, and a per-person price on the card > - Running an outdoor session? The card shows a live weather forecast, and if you call it off everyone gets auto-credited and emailed > - Private 1:1 lessons book like normal appointments, and happy members can pass a referral link that earns them a reward Hemi runs a small BJJ and striking gym above a hardware store in Hamilton. Four mats and a heavy bag in the corner. By the door, a whiteboard that used to hold the week's timetable in blue marker. For two years that whiteboard was the booking system. People would text him to ask if Tuesday's beginner class still had room, and he'd guess from memory and say yes. Sometimes fourteen people turned up for eight pairs of pads. #### The whiteboard was doing too much The trouble with a whiteboard is it can't count. It can't tell a new person that the Wednesday no-gi class is full, and it can't take their fifteen dollars while they're still keen enough to pay. Hemi was losing beginners in the hours it took him to get back to them after his day job. By the time he replied at nine at night, half of them had gone quiet. What he actually wanted was simple. He wanted every class on his weekly timetable to be something a stranger could find and book without talking to him first. A Tuesday beginner class at 6pm, eight spots, a set price, done. That's what a group session is on Bookatu. You set the date and the time, you set how many spots exist, you name the venue with its address and directions, and you put a per-person price on it. When those eight spots fill, the class closes itself. Nobody drives across town for a mat that's already full. #### A timetable that books itself Here's the part Hemi didn't expect to like so much. Once the week was up online, he stopped being the middleman. His storefront showed the whole timetable the way the whiteboard used to, except every class had a live spot count and a book button underneath it. Someone finds the gym on a Sunday afternoon, scrolls the week, sees three spots left in Monday's fundamentals class, books it, pays, and Hemi finds out when he next looks at his phone. No back and forth. No guessing. A group session card carries everything a person needs to actually show up in the right place: - The date and start time, so nobody books the wrong night - How many spots are left, counting down as people join - The venue address with directions, which matters when your gym is up a staircase behind a hardware store - The per-person price, paid at the time of booking so you're not chasing cash on the mat For the private stuff, Hemi does one-on-one lessons with a couple of competition guys and the odd nervous beginner who wants a solo hour before they'll set foot in a class. Those book like a normal appointment. Pick a time that works and lock it in, and it never touches the group timetable. Two different needs, one calendar, and Hemi isn't juggling two systems to run both. #### When the outdoor session gets rained out Every summer Hemi runs a Saturday morning conditioning session down at the park. Sprints and sandbags, the sort of thing that's miserable in the rain and brilliant in the sun. The problem with anything outdoors is the sky doesn't check with you first. > I used to send twenty texts on a Saturday morning telling people it was off. Now the forecast is right there on the class before they even book, and if I do call it, they've got their credit before I've packed the cones away. For outdoor group sessions, the card shows a live weather forecast right where people are deciding whether to book. If the morning turns and Hemi has to call it off, he cancels the session and everyone who paid is credited automatically and emailed to let them know. No refund spreadsheet, no awkward messages. Nobody feels like they got stiffed for fifteen bucks because the weather turned. The credit sits there ready for the next session they want. #### Let the room fill your room The best advertising Hemi ever had was a member dragging their mate along. That still happens, but now it counts for something. He can send a member a referral link, and when they bring someone in, the gym rewards them for it. A free class or a bit off their next month, whatever he decides is fair. The people who love the place get a reason to keep talking about it, and the whiteboard never could have done that. None of this made Hemi's gym bigger overnight. What it did was stop the small daily leaks. The beginner who would've drifted off waiting for a reply now books at midnight and shows up Monday. The rained-out Saturday crew don't feel cheated, and the regulars bring friends and get a little something back. And Bookatu doesn't take a cut of any of it, so the fifteen dollars a beginner pays is fifteen dollars Hemi keeps. #### Where to start If you've got a whiteboard doing too much, start by putting one week of your timetable online. Just the classes you already run, with real spot counts and a real price. See what it feels like when Monday's class fills without you touching your phone. You can add the outdoor sessions and the private lessons once the weekly rhythm is working, and the referral links after that. The mat's the same. You've just stopped being the thing standing between a keen beginner and their first class. ### How a kids gymnastics club runs weekly classes without losing its mind How a small kids gymnastics club runs weekly classes by age group without counting heads off a spreadsheet: group sessions with spots and venues, live weather and instant credit for outdoor sessions, and referrals that fill a term. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/gymnastics-club-booking · markdown: https://bookatu.com/blog/gymnastics-club-booking.md > **The short version** > > - Set up each weekly class as a bookable group session with a date, a spots limit, and a per-child price so parents pay when they book. > - Give every age group its own venue card with the address and directions, so nobody turns up to the wrong hall. > - Outdoor sessions show a live weather forecast, and if you call one off, every family is auto-credited and emailed. > - Keep private one-on-one coaching as normal appointments, and hand happy parents a referral link they can pass to school friends. Priya runs a small gymnastics club out of a community hall in Hamilton on Tuesday and Thursday afternoons. Tumble Tots at 3.30, the little ones aged three to five, then the six-to-eights, then a nine-plus group who are getting serious about their cartwheels. For two years she ran the whole thing off a spreadsheet, a class WhatsApp, and a shoebox of cash. It worked, sort of, until the term she counted fourteen kids booked for a class with room for ten, and had to send two families home in tears. #### Weekly classes are group sessions, not a long list of appointments The thing most booking tools get wrong for a club like Priya's is that they treat every kid as a separate one-off appointment. That falls apart fast when you run twelve children through the same mat at the same time. What she actually needed was a way to sell one class as one thing, with a fixed date and time, a cap on how many kids fit, and a price per child. That is exactly what a group session is on Bookatu. You create the Thursday four-to-five Tumble Tots class, you set it to ten spots, you set the price, and it goes live on your page. Parents see the class, see how many spots are left, book their child, and pay right there. When the tenth family books, it closes itself. No more counting heads on a Tuesday and doing the maths in a panic. Priya set up her whole term in an afternoon. Each age group became its own set of weekly classes, each with the right cap, because ten three-year-olds and ten nine-year-olds are very different amounts of chaos. The little ones' groups fill first, every single week. #### Every group has a venue, and the venue tells parents where to go Here is a small thing that turned out to matter a lot. Priya's older group moved to the bigger sports centre across town on Thursdays, because they needed the sprung floor and the beam. Two different halls, two different car parks, and two different sets of confused parents. A group session carries its own venue with its own address and directions. So the Thursday nine-plus class shows the sports centre address on the card, and the Tuesday classes show the community hall. A dad who has only ever done drop-off at the hall opens the class, sees the new address and the little note about parking round the back, and just goes to the right place. Priya stopped getting the frantic "where are you today" texts almost overnight. #### When the weather turns, nobody is out of pocket Priya added an outdoor holiday programme last summer. Cartwheels on the grass, a bit of tumbling in the park, the kind of thing that is lovely right up until the sky opens. Outdoor group sessions show a live weather forecast right on the card, so a parent booking a Saturday-morning park session can see for themselves what is coming. And when it does properly rain, she does not have to spend her evening working out who paid what and chasing refunds one by one. She opens the session, cancels it, and that is it. Everyone who booked gets automatically credited and emailed to let them know. The credit sits there ready for the next class. She told me the first time she did it she kept waiting for the awkward part, and there wasn't one. > I used to dread calling off a session because the refunds were half a day of admin. Now it's one tap and the parents already know before I've put the kettle on. #### Private coaching is just a normal booking Not everything is a group. Priya coaches a handful of kids one-on-one, the ones prepping for a competition or the nervous newcomer who needs a quiet half hour before joining the big class. Those are ordinary appointments. A parent picks a time that suits, books it, done. Same system, different shape, and she doesn't have to think about which is which. So her page ends up with a clean split that makes sense to a parent at a glance: - Weekly classes by age group, each with its spots and its own hall, booked and paid for in advance. - Outdoor holiday sessions with the forecast on the card and instant credit if she calls them off. - Private one-on-one coaching slots for the kids who need extra time. - A running credit balance for any family whose session got rained off, ready to spend on the next one. #### The parents do your marketing for you Gymnastics clubs grow at the school gate. One mum tells another that her daughter loves Thursdays, and suddenly there are three new kids. Bookatu leans into that with a referral link Priya can send to any parent, and a reward she sets for the ones who bring a friend along. She keeps it simple. A family who refers someone who books a full term gets a free class. She pastes the link into the class WhatsApp at the start of each term and lets it do its quiet work. Two of her Tuesday regulars came in that way this year. It costs her a class each, and it fills a whole term. #### You keep what you charge One last thing worth saying plainly, because it is the reason a lot of small clubs move over. Bookatu takes zero commission on your classes. The card fee from the payment processor is the card fee, and the rest is yours. For a club running on term fees and a lot of goodwill, that difference is a new set of mats by the end of the year. If you run classes by age group and you are still counting heads off a spreadsheet, try setting up one week the way Priya did. Build your Tuesday groups, cap them properly, put the hall address on each one, and send the booking link to your class chat. See how it feels to have the tenth spot close itself while you are making dinner. ### How a badminton club filled its courts with online session booking How a small Hamilton badminton club moved its weekly social and coached sessions online and got its Tuesday evenings back, using bookable group sessions with live spot counts, weather-aware cards, automatic credits, and referral rewards. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/badminton-club-online-booking · markdown: https://bookatu.com/blog/badminton-club-online-booking.md > **The short version** > > - Put your weekly social and coached badminton sessions online, so people book and pay their spot in a few taps > - Each session shows the date, the courts, how many spots are left, and even the forecast if you play outdoors > - If bad weather forces you to call one off, everyone gets an automatic credit and an email, no awkward messages from you > - Bookatu takes 0% commission, and you can hand regulars a referral link that rewards them for bringing a mate #### The Tuesday night that started it Priya runs a badminton club in Hamilton. Four courts and a good crowd, the kind of place where half the room knows each other and the other half will by the end of the night. She started it because she loved the game and hated how hard it was to just turn up and play somewhere friendly. For the first two years, her booking system was a WhatsApp group and a spiral notebook. Every Tuesday she ran a social session and every Thursday a coached one for improvers. People would message her all week. "Room for me Thursday?" "Can I bring my flatmate?" "Did you get my transfer?" "What time do we start?" She'd answer between her day job and dinner, crossing names off the notebook and chasing the ones who forgot to pay. Some nights twenty people showed up for eighteen spots. Other nights it rained and half the group just didn't come, and she never quite knew who to expect. The game was the easy part. Everything around it was the grind. #### What a session actually is Here's the shift that made things click for Priya. Instead of chasing people, she put each session up as its own thing people could book. A social session and a coached session are group sessions: a fixed date, a start time, a set number of spots, the venue address with directions, and a price per person. Someone opens the page, sees Thursday has six spots left, taps once, pays, and they're in. The spot count ticks down in front of them, so nobody has to ask if there's room. The one-to-one stuff works differently, and that's on purpose. When a member wants a private lesson with Priya, that's booked like a normal appointment against her calendar. Pick a time she's free, done. Group sessions fill a room. Private lessons fill an hour. Two different jobs, and the booking handles each the way it should. What Priya noticed first wasn't the tech. It was Tuesday evening. She'd stopped answering the same four questions on repeat, because the page answered them for her. #### The weather problem, mostly solved Some clubs play outdoors in summer, and Priya runs a casual outdoor social down at the local park courts when the weather's good. Outdoor badminton and wind are old enemies, so this used to be a guessing game. Now the forecast sits right on the session card. People booking Saturday's park session can see what the sky's meant to be doing before they commit, and Priya can see it too. When the forecast turns and she has to call one off, she cancels the session from her side and the rest happens on its own. Everyone who booked gets credited back automatically, and they each get an email letting them know. No group message she has to word carefully at nine at night. No shuffling through the notebook working out who paid and who didn't. The credit lands and the email goes out, and people just rebook for the next dry evening. > The first time I cancelled a rained-off session and didn't have to do anything after clicking the button, I sat there for a second waiting for the catch. There wasn't one. #### Where the growth quietly came from Priya wasn't trying to build an empire. She just wanted steady, full sessions and fewer no-shows. But a funny thing happens when booking is this easy. People bring people. Badminton is social by nature. Someone joins the Thursday coached session and gets a bit better, then wants their sister or their workmate along too. Priya started handing regulars a referral link they could text straight to a friend. When that friend books their first session, the club rewards the person who sent them. It costs Priya almost nothing and it turned her happiest members into the reason her sessions fill. She didn't have to run ads. She had forty people who already loved Tuesday nights, and she gave them an easy way to share it. A few things she'd tell you made the difference: - Every session shows spots left, so it books itself instead of needing her to confirm each person - Payment happens at the point of booking, which quietly ended the "I'll transfer you later" pile - The referral link turned regulars into recruiters without her nagging anyone - Because Bookatu charges 0% commission, the money from a full session is actually the money from a full session #### The part nobody markets The best thing Priya got back wasn't a number on a dashboard. It was her week. She reckons she was spending the better part of an evening every few days just administering a hobby she'd started for fun. Now the booking runs while she's cooking dinner. She shows up on the night and sets out the nets, and gets to be the person who loves badminton again, not the person answering DMs about it. Her club is fuller than it was, and the sessions that used to be a gamble now sell out mid-week. But if you ask her, she'll tell you the real win is that she looks forward to Tuesdays the way her members do. #### If this sounds like your club You don't have to change how you run your sessions. You just stop doing the manual bits around them. Put your next social night up as a bookable session and let people grab their spot and pay. See how the week feels when the notebook stays in the drawer. If it helps, start with one session this week and add the rest once you've felt how it works. That's genuinely how Priya began, with a single Thursday. ### How a Small Dance Studio Filled Its Weekly Ballet and Hip-Hop Classes A dance studio owner swaps her fraying group chat for weekly classes people book and pay into online, with capped spots and outdoor sessions that carry their own weather, filling the room through the dancers she already has. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/dance-studio-class-booking · markdown: https://bookatu.com/blog/dance-studio-class-booking.md > **The short version** > > - Put your weekly ballet and hip-hop classes online with a set day and time, plus a cap on spots, so people book and pay their place before they show up. > - Each class card carries its own venue address and directions, plus a live weather forecast when you run something outdoors. > - If a session gets rained off or you have to call it, one cancel button credits everyone back and emails them automatically. > - Send regulars a referral link and reward them when they bring a friend, which is how most small studios actually fill a room. Priya runs a dance studio above a hardware shop in Onehunga. Two rooms and one sprung floor. The kettle takes forever. She teaches ballet on Tuesday evenings and hip-hop on Thursdays, and until this year she ran the whole thing out of a spiral notebook and a group chat that had long since stopped making sense. #### The Thursday that broke the notebook Here is the moment she talks about. One Thursday in March, hip-hop was meant to hold fourteen. Priya counted heads as they came in and got to nineteen. Five people had seen the class mentioned in the chat and assumed there was room, so they turned up. Nobody had paid. Nobody was quite sure who was actually enrolled and who was just there because their mate said come along. She taught the class anyway, sweating more than the dancers, and spent the next morning chasing five separate payments over text. That is the thing about a weekly class. It is not really one booking, it is the same room filling and emptying over and over, and if you are tracking it by memory you will eventually get a Thursday like that one. The notebook was never going to scale past her own goodwill. #### A class is a thing people book, not a thing they wander into The shift that fixed it was small to describe and large to live with. Priya stopped treating each class as a vague standing invitation and started treating it as a proper thing with a shape. A set date. A start time. A hard cap on how many people can be in the room. A price per person. Once a class is set up that way, people book their spot the same way they would book a table, and they pay when they book. So Tuesday ballet is capped at twelve, and when the twelfth person books, it says full. Thursday hip-hop is capped at sixteen now, because she learned her lesson about the sprung floor and how many bodies it likes. Nobody arrives to a surprise. Priya walks in already knowing the count, already paid, and she can spend the walk up the stairs thinking about the class instead of the admin. > The first full Tuesday where I hadn't chased a single payment, I stood at the barre and genuinely didn't know what to do with the extra half hour of my brain. #### When the class moves outside In summer Priya runs a Saturday hip-hop session in the park by the water. Lovely when the weather plays along, miserable and slightly dangerous on a wet concrete slab when it doesn't. Because the park session is a proper outdoor class, its booking card carries two things the indoor ones don't need. It shows the venue address for the park with directions, because half the dancers have never had a reason to go to that particular corner of it. And it shows a live weather forecast right on the card, so someone booking on Wednesday can see what Saturday is shaping up to be. That forecast does quiet work. People stop messaging her to ask if it's still on. They can just look. And when the sky does turn on her, which it did twice last February, she opens the session and cancels it. Everyone who booked is credited back automatically and gets an email telling them so. No refund queue and no round of awkward individual messages. Nobody is left wondering if their money vanished with the rain. The credit lands and the email goes out, so Priya can get on with her Saturday. - The class card shows the exact venue and directions, so first-timers find the park corner without texting you. - A live forecast sits on the card for outdoor sessions, which cuts the is-it-still-on messages to nearly none. - One cancel button credits every booked dancer and emails them, so a rained-off Saturday doesn't become a Monday of refunds. - Credited dancers usually just rebook the next week, because the money never left their world in the first place. #### The one-to-one lessons still work the old-fashioned way Not everything Priya does is a group. She teaches private ballet lessons to a couple of teenagers prepping for exams, and those are just normal appointments. A parent picks a time that suits and books the one slot. Done. There is no cap to think about and no room to fill, because it is one dancer and one teacher. She likes that the group classes and the private lessons live side by side without her having to bolt two different systems together. The weekly stuff has spots and caps, the private stuff is a simple time booking, and both sit on the same page. #### How the room actually fills Here is the part Priya didn't expect to matter as much as it does. Most of her new dancers don't come from an ad. They come because someone already in the room dragged a friend along. So she leans into that on purpose. Every regular has a referral link she can send to a mate, and when that mate books their first class, the regular gets a reward on their own next booking. It costs Priya a little off one class and it fills two. It fits the way a dance studio really grows, which is one enthusiastic person telling another. She isn't buying strangers. She is thanking the dancers she already has for doing the thing they were going to do anyway, which is talk about the class they love with the people they like. #### What changed, in the end Priya still teaches ballet on Tuesday and hip-hop on Thursday. Same rooms, same kettle that takes forever. What's gone is the Friday morning of chasing payments and the quiet dread of a class she couldn't quite count. The notebook is in a drawer somewhere, retired with honours. She kept the sprung floor and the kettle and lost the parts that were never really the job. If your studio runs on memory and a group chat that's starting to fray, you don't have to change what you teach or how you teach it. You just give each class a shape people can book into and let the outdoor ones carry their own weather. Then let your regulars bring the next dancer through the door. Set up one week of classes and see how the first full Tuesday feels. ### Weekly swim lessons that book themselves: a learn-to-swim school's quiet Monday night How a small learn-to-swim school turned its repeating weekly classes into online group sessions parents book and pay for themselves, with live weather on every outdoor card and automatic credits when a lesson is rained off. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/swim-school-lesson-booking · markdown: https://bookatu.com/blog/swim-school-lesson-booking.md > **The short version** > > - A learn-to-swim school runs the same weekly lessons every term, so set them up once as bookable group sessions and let parents book and pay online. > - Each session shows the pool, the start time, how many spots are left, and the price per child, so a parent can sign up in under a minute. > - For outdoor pools, every session card carries a live weather forecast, and if you call off a wet week everyone gets auto-credited and emailed. > - Happy parents talk, so hand them a referral link and thank them with a reward when a friend books their first lesson. #### Marama and the Tuesday 4pm class Marama runs a small learn-to-swim school out of a community pool in Tauranga. Nothing fancy. Two lanes roped off on weekday afternoons and a whiteboard by the door. What she also has is a reputation among local parents for getting nervous five-year-olds from clinging to the wall to swimming a width by the end of term. Her problem was never the teaching. It was the Tuesday 4pm class. Same eight kids every week, same worried parents texting her to ask if it was still on this week, or whether little Ari could swap to Thursday when a birthday party clashed. Marama was running a real business on the back of a group chat and a spreadsheet she only half trusted. Some weeks she'd take a booking twice by accident. Some weeks she'd forget who had paid. The thing about weekly kids' lessons is that they are gloriously repetitive. The same class runs at the same time all term. That repetition is a gift once you stop treating every week as a fresh scramble and start treating the class as a thing people can book and pay for on their own. #### A weekly class is really a group session On Bookatu, that Tuesday 4pm class becomes a group session. You give it a set date and time, a cap on how many kids can join, the pool it runs at, and a price per child. Then you put it in front of parents and they book their own spot. No back-and-forth. No holding places in your head. Each session shows up as its own card, and the card does the explaining for you. A parent looking at next Tuesday sees exactly what they need to decide in a few seconds: - The start time and how long the lesson runs, so they can plan the drive from school pickup. - The pool it's at, with a proper address and directions, which matters when you teach across two venues. - How many spots are left, so a class filling up nudges them to book now instead of next week. - The price per child, sorted before they arrive, so nobody's fishing for cash on the poolside. When the class is full, it's full. The card stops taking bookings on its own, and Marama stops getting the 8pm text asking if there's room for one more. If she wants to run a school-holiday intensive or a one-off water-safety clinic, that's just another session with its own date and its own cap. The regular Tuesday class and the special events all live in the same place. #### The weather is the part everyone forgets Marama's second venue is an outdoor pool. Lovely in January, a genuine question mark in shoulder season. Half her admin used to be weather admin: checking the forecast on Monday night, then texting eight families one by one on Tuesday morning and hoping they all saw it before they loaded the kids in the car. For outdoor sessions, the card shows a live weather forecast right there next to the time. Parents can see for themselves that Thursday looks marginal, which cuts down the worried messages before they start. And when the sky actually opens up and Marama calls it off, she cancels the session with one action. Everyone booked into it is credited automatically and emailed to let them know. She doesn't chase refunds. She doesn't do the mental maths on who paid what. The credit sits ready for them to use on the next lesson, and she can go back to drying towels. > I used to dread a rained-out week because of the phone calls, not the rain. Now I cancel the session and the pool does the apologising for me. #### Not everything is a group, and that's fine Some of Marama's work isn't a class at all. A parent whose kid is anxious in deep water wants a private catch-up. An adult who never learned as a child wants quiet one-on-one lessons where no eight-year-old is watching. Those aren't group sessions with a spots limit. They're ordinary appointments. So Marama lists her 1:1 lessons the normal way, as bookable appointments against her own availability. A parent picks a free slot, books it and pays, done. The busy group classes and the quiet private sessions sit side by side on the same page, and she runs both from the same calendar without keeping two systems in her head. #### Let the happy parents do the talking Here's the part Marama didn't expect to matter as much as it did. Learn-to-swim runs on word of mouth. One parent watches their kid swim a width, tells three others at the school gate, and suddenly there's a waitlist. That conversation was already happening. She just wasn't getting any credit for it. Now she can send a parent their own referral link, and when a friend they've sent along books their first lesson, that parent gets a thank-you reward. It turns the school-gate chat into something she can actually see, and it rewards the families who were already doing her marketing for free. She isn't buying ads. She's thanking the mum who told everyone about the Tuesday class. #### Set it up once, then go teach The honest pitch is that a weekly swim school is a business that repeats itself, and repetition is easy to automate once the bookings and payments live in the same place as the wet-weather calls. Marama still stands in the shallow end every Tuesday coaxing a five-year-old off the wall. That part is hers and nobody can automate it. She just doesn't spend Monday night on the phone about it anymore. And because Bookatu takes zero commission on what she earns, the price she sets per child is the price that lands in her account. The pool doesn't quietly clip a slice off every lesson she teaches. If your terms look anything like Marama's, try setting up a single week as a group session, forecast and all, and share the link with the parents you already have. See how many book themselves in before you've finished your coffee. That first quiet Monday night is usually the moment it clicks. ### How a small reformer studio fills every machine without a single double-booked class How a small reformer pilates studio sells fixed-time classes online without ever overselling its machines and auto-credits everyone the moment a session is called off, all on a zero-commission booking platform that also turns happy regulars into referrals. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/pilates-reformer-class-booking · markdown: https://bookatu.com/blog/pilates-reformer-class-booking.md > **The short version** > > - Sell your reformer classes as fixed-time sessions online, with a hard cap on spots so you never oversell the eight machines you own. > - Every session shows the date, the studio address with directions, the price per person, and how many spots are left. > - If you ever call off a class, one tap cancels it and everyone is auto-credited and emailed, so nobody chases you for a refund. > - One-to-one lessons book like normal appointments, and happy regulars can be handed a referral link that quietly rewards them for bringing a friend. Priya runs a small reformer studio above a bakery in Wellington. Eight machines in one bright room, and a wait every Tuesday morning that used to spill out onto the landing. She loves the work. What she did not love was her phone. For the first year she took class bookings by text. Somebody would message at 6am asking if the 9:15 had room, and Priya would count heads in her head while pouring coffee and reply, only to get a second text from a different person asking the same thing, and suddenly two people were promised the last machine. She once had ten women turn up for eight reformers. That morning stuck with her. #### A class is not really an appointment Here is the thing most booking tools get wrong for a studio like Priya's. They treat everything as a one-on-one slot. But a reformer class is a group thing. It starts at a set time with a fixed number of machines, and it either has room or it doesn't. You are not selling Priya's calendar, you are selling eight spots in a room at 9:15 on Tuesday. That is exactly how Bookatu handles it. You set up the class as a group session. It has a date and a start time, a cap on spots, the studio address with directions built in, and one price per person. People find it and pay to hold their place, and they can see how many spots are left before they do. When the eighth person books, the ninth simply can't. No counting heads over coffee. The spots limit is the quiet hero. Priya set hers to eight and stopped thinking about it. The machines and the booking page now agree on the number, every single time, whether she is watching or not. #### What a client actually sees When one of Priya's regulars opens the studio page on her phone, the week is laid out plainly. Each class is a card. The Tuesday 9:15 card might say three spots left and list the price, with the address shown as a two-minute walk from the train. She taps to pay and she's in. She gets an email with the time, the door code, a little map link, and a reminder to bring grippy socks, so she is not texting Priya at 8:55 asking which entrance. A few of the sessions Priya runs are outdoors in summer, reformer-style mat classes in the Botanic Garden when the weather turns. For those, the card carries a live weather forecast, so somebody booking on Sunday for a Wednesday sunrise class can see what's coming. It is a small touch. It also cuts down on the day-of, is-this-still-on messages that used to pile up. #### Rain, and the thing that used to ruin Priya's evening Wellington weather does what it wants. Last February a southerly rolled in and Priya had to pull the outdoor sunrise class an hour before it started. In the old days that meant fourteen refunds and fourteen apologetic texts to send by hand, and a knot in her stomach about who she'd forgotten. Now she opens the session and cancels it. That's the whole job. Everyone who booked is credited automatically and emailed to let them know, and the credit sits ready for the next class they want. Priya doesn't touch a single refund by hand. She sent me a message the week she discovered this. > I cancelled a rained-out class from the car and by the time I got home it was all done. Nobody was cross. A few of them just rebooked for Thursday. That turns what used to be a bad night into a non-event. The tool does the tedious part so the owner can be a person about it. #### The one-to-one work still fits Group classes are the heart of the business, but Priya also does private sessions. New clients who want a proper assessment before they join a class. A dancer rehabbing a knee. Those aren't group things, so they don't book as classes. They book as normal appointments against Priya's own availability, one person at one time, the way any solo booking works. So her page carries both without either one feeling bolted on. A first-timer might book a private intro this week, then start dropping into the Tuesday class next week, all from the same page. #### Letting the regulars do the marketing Priya's best growth has never come from ads. It comes from a woman finishing a class feeling strong, and telling her friend at brunch about it. Bookatu just gives that a nudge you can actually track. Each regular can be handed their own referral link. When a friend books their first class through it, the studio rewards the person who sent it. Priya set hers up so a successful referral drops a credit onto the referrer's next class. She mentioned it once in a Tuesday cool-down and let it run. A few things her clients told her they liked about it: - The link is theirs to send however they like, by text or in a group chat, no codes to remember. - The reward only lands when the friend actually shows up and books, so it feels earned. - It rewards the people already in the room, the ones who were going to recommend the studio anyway. - It turned a nice word-of-mouth habit into something Priya could see happening. None of it is pushy. The regulars were already talking. This just says thank you in a way that shows up on their account. #### Why zero commission matters at this size A reformer class is not a huge ticket, and a studio with eight machines has a hard ceiling on how many bodies fit in a day. When a booking platform skims a cut off every single class, that adds up fast on thin numbers. Bookatu takes no commission on your bookings. The price a client pays for a spot is the price that reaches you, minus only what the card processor charges, which every business pays anyway. For Priya that meant the maths finally made sense. She wasn't renting her own room back from a middleman. The eight spots and the price were hers, and the growth from referrals was hers to keep. #### If your Tuesday mornings look like Priya's You don't need a big system to run a small studio well. You need the day-to-day to hold together, classes that never seat more people than you have machines and rain days that sort themselves out, and you need your happiest regulars to have an easy way to bring a friend. If that sounds like your week, set up one class the way you'd actually run it, an eight-spot Tuesday at 9:15, and send the link to the ten people already texting you. Watch what happens when the ninth booking politely bounces and nobody ends up standing in the doorway. That is usually the moment it clicks. ### How a bouldering gym filled its beginner classes without a single phone call Running intro nights and coached sessions gets messy fast when you track it in your head. Here is how one climbing gym owner moved every class online and got her evenings back. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/climbing-gym-classes-booking · markdown: https://bookatu.com/blog/climbing-gym-classes-booking.md > **The short version** > > - Intro nights and coached sessions become fixed-time classes people book and pay into online, so you stop chasing money on the night. > - Each class has its own date, spots limit, per-person price and venue, and the spots count down as people join. > - Private 1:1 coaching stays a normal appointment, booked whenever suits the climber. > - If you ever call one off, everyone is auto-credited and emailed, and regulars can be handed a referral link that rewards them for bringing a mate. Priya runs a bouldering gym in a converted warehouse on the edge of town. Two big walls and a temperamental coffee machine on cold mornings. The Tuesday intro night fills up if she is lucky and half-fills if she is not. For the first year she took bookings the way most gym owners do, which is to say she took them everywhere. A text here, a DM there. And more than once, a name scrawled on the back of a receipt she then lost. The intro night was the worst of it. Twelve mats on the floor, so twelve people, no more, because past that nobody gets a proper turn and the whole thing feels like a queue. But she never actually knew if it was twelve. She knew of maybe eight who had messaged and assumed two of those would flake. Then she opened the doors to find fifteen strangers who had all heard it was on and just showed up. Some nights she turned people away. Other nights three mats sat empty while she stared at the door. #### The problem was never climbing. It was counting. A beginner class works differently from a normal booking. It is not really one booking at a time. It is one evening that a group of people book into together, and the whole event only works if you know the number before anyone laces up. Priya had been treating each class like a private appointment, saying yes to people one by one in her messages. Then she tried to hold the running total in her head while she also brewed coffee and reset problems on the wall. That is the exact shape a group session is built for. You set the class once. A date and a time, a cap on how many spots, a price per person, and the venue with its address so newcomers can actually find the door. Then you share the link and let people book and pay into it themselves. The spots tick down in public. When the twelfth person joins, it closes, and Priya never has to send the awkward sorry-we-are-full message again because the class sends it for her by simply not being available. > I used to spend Tuesday afternoons doing arithmetic on the back of an envelope. Now I glance at my phone and see nine of twelve, and my afternoon is my own again. #### Money on the night was the other quiet headache Priya used to collect the class fee at the door. Cash from some and a card tap from others. And always one person who left their wallet in the car and swore they would sort it next week. Next week rarely came. She was not running a charity, but some evenings it felt close. When people pay when they book, that whole scene disappears. The money is already in before anyone arrives, so the person who shows up is a person who has decided to be there. Her no-show rate dropped almost the moment she switched, not because she got stricter, but because a paid spot feels like a plan and a free maybe feels like nothing. She also stopped standing at the door doing card taps while a class waited on her, which sounds small until it is your Tuesday. #### One weekend she moved the tougher stuff outside Come spring, Priya wanted to run a coached session on real rock at a crag about forty minutes out. Different beast entirely. Weather matters. The meeting point is a gravel car park rather than her front desk, so everyone needs to know where to actually stand at nine in the morning. She built it as a group session the same as the indoor ones, but this one carried its own venue with the car park address and a note about parking near the gate. Because it was outdoors, the class card showed a live weather forecast for that morning, so the people eyeing it could see for themselves what Saturday looked like before committing. No more fielding six separate texts asking whether it was still on if the sky looked iffy. And one Saturday it genuinely was not on. Rain came in sideways from the coast and the rock was a hazard, so she called it off. She cancelled the session, and that was the whole job. Everyone who had booked was credited automatically and got an email telling them so. Nobody was out of pocket and nobody had to chase her for a refund. She rescheduled for the following week with a clear conscience and a warm car. #### The 1:1 coaching stayed simple, because it should Not everything is a class. Priya also does private coaching, usually a climber working on a specific weakness who wants an hour of her full attention. That does not need a fixed date and a group of strangers. So those stay ordinary appointments. Someone picks a slot that suits them and books it, and it lands in her calendar next to everything else. Group energy for the intro nights and quiet focus for the one-on-ones, both living in the same place. What she likes is not having to explain the difference to anyone. A first-timer books the Tuesday intro. A returning climber books a private hour. Both feel like the same easy thing from where they sit, even though one is a shared event and the other is a solo booking. #### The best marketing turned out to be her own regulars Priya noticed that her fullest classes were always the ones where a regular dragged a friend along. Climbing is social in a way that spreads, and the person most likely to talk you into your first intro night is a mate who already goes. So she leaned into it. Her regulars get a referral link they can pass to friends, and when a friend books a class off that link, the regular gets a little something back for it. - The intro nights fill from word of mouth instead of ad spend, which suits a small gym. - Regulars feel looked after, because bringing people in actually earns them something. - New climbers arrive already knowing one friendly face on the mats. - Priya spends her marketing budget on better coffee instead of posts nobody reads. It is a gentle loop rather than a growth hack. She is not gaming anything. She just made it worth a regular's while to do the thing they were already doing, which was telling people the gym is good. #### Where Priya is now The Tuesday intro night is full most weeks and she knows the number by Sunday. The outdoor sessions run when the weather cooperates and quietly credit everyone when it does not, and private coaching ticks along in the gaps. She spends her time on the wall with people rather than on her phone doing sums, which is roughly why she opened a climbing gym in the first place. If your evenings look anything like Priya's old ones, the fix is not more discipline. It is letting the class hold its own count and its own money, and carry its own bad-weather plan. Try it with one session first. Set your next intro night as a group booking and share the link with the people who already come. Then see how it feels to walk in on the night already knowing exactly who is there. ### Your box already runs on a timetable. Let people book into it. A CrossFit box already runs on a fixed timetable. Here's how turning each class into a bookable, paid-for spot online ends the group-chat headcount and lets your best members bring their friends, with rained-off park sessions handled on their own. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/crossfit-box-class-booking · markdown: https://bookatu.com/blog/crossfit-box-class-booking.md > **The short version** > > - A CrossFit box runs on a fixed timetable, so classes are a natural fit: set a date, a time, a spot limit, and a price, and let people book their own place. > - Members book and pay on their phone in a few taps, then get a reminder before class rolls around, so you stop chasing texts about who's coming to the 6am. > - When you run a bootcamp in the park and the sky turns, you cancel the class and everyone is credited and emailed automatically. > - One-off 1:1 coaching stays a normal appointment, and a referral link gives your best members an easy way to bring a mate in. #### The whiteboard used to run the gym Meet Priya. She runs a small functional-fitness box in a converted warehouse on the edge of town, twelve classes a day, chalk on everything. For the first two years her whole booking system was a group chat and a laminated timetable by the door. It sort of worked. Then the 6am strength class blew up. Fourteen people would say they were coming, nine would show, and twice she had someone drive in for a class that was already full because she'd lost count somewhere around message forty. The Monday that broke her was simple. She'd programmed a heavy session, set out ten sets of bars, and then thirteen people walked in. Two of them she had to turn around at the door. One of those two had booked a babysitter to be there. Priya spent that evening doing sums on the back of a receipt and realised she wasn't running a gym, she was running a phone. #### A class is just a spot on the timetable, so treat it like one Here's the thing about a box. You already know your schedule cold. The 6am, the 9:30 for the parents after school drop-off, the lunchtime express, the after-work rush at 5:30. Every one of those is a fixed time, a room, a set number of spots, and a coach. Which is exactly what an online class booking is. On Bookatu you set each class up once: the date and time, how many spots are on the floor, the venue with its address, and the price per person. Members open your page to see the whole week laid out, then tap the class they want. The count ticks down in front of them. When the 6am hits ten, it says full, and nobody drives in for a bar that isn't there. Priya set her first week up on a Sunday night with a cup of tea. It took her about the length of two episodes of something she wasn't really watching. The quiet win is what stops happening. No more group chat pinging at 11pm. No more her doing a headcount in her head while she's coaching. The whiteboard can go back to being for the workout. #### Money that just arrives Priya used to sell class packs on trust and a spreadsheet. People would forget they'd run out. She'd feel awkward asking. Some months a good chunk of her income was just people meaning to pay her back. When a class is booked and paid for online, that whole dance disappears. Someone books the Thursday conditioning class, they pay for the Thursday conditioning class, done. And because Bookatu takes zero commission, the price a member pays is the price that lands with Priya, minus the normal card fee and nothing else. She worked out roughly what the old percentage-based platforms would have skimmed off a year of full classes and decided she'd rather spend it on a new rig. #### The morning it rained on the park session Priya runs a Saturday bootcamp in the park down the road when the weather's good. Sandbags and sleds out on the grass, and everyone flat on their back regretting their life choices. It's her most popular class and it's completely at the mercy of the sky. The outdoor classes show a live weather forecast right on the card, so when someone's deciding on a Thursday whether to book Saturday, they can see what's coming. And on the mornings it does turn, she doesn't have to fire off twenty apologetic texts. She opens the class and cancels it, and everyone who booked is credited straight back and emailed to say the session's off. No refunds to process by hand, no awkward wondering whether Dave saw the message. It's handled before she's finished her coffee. The first Saturday it rained after she moved to this, she said the strangest part was having nothing to do. She'd braced for an hour of admin and it took her about forty seconds. #### Not everything is a class, and that's fine Some of what Priya does isn't a group thing at all. A new member wants a 1:1 to learn how not to hurt themselves under a barbell. Someone's coming back from an injury and needs a private session before they rejoin the room. Those aren't classes with ten spots. They're one member with one coach, booked into a single slot. So those get booked the normal way, as a regular appointment against the coach's own availability. The member picks a time that's actually free and books it, and it never collides with anything. Same booking page, two different shapes of thing, and Priya doesn't have to think about which is which. Her members certainly don't. #### Let your best people bring their friends A box grows by word of mouth. Someone drags their flatmate along, the flatmate gets hooked, and now you've got two. Priya always knew this but never had a clean way to reward it. Now she can send a member their own referral link, and when a mate signs up through it, that member gets something back for it. She keeps it simple: - A free week for the person doing the referring, once their mate books their first class. - A discount on the newcomer's first class pack, so there's a reason to actually turn up. - A little leaderboard she jokes about, because these people are competitive to their bones. - A simple link they can text to whoever they were going to drag along anyway. > I stopped selling the gym. My members do it now, and I just make sure the door's easy to walk through. #### Where to start If you run a box, you don't need to reinvent how you coach. You already know your timetable better than any software ever will. The move is small: take the classes that are already in your head and put them on a page people can book and pay into. From there, the counting and the reminders run themselves, rained-off Saturdays included. Pick one class to start with. The busy one, the 6am or whatever yours is. Put next week's sessions up and share the link in your group chat one last time, then watch the spots fill without a single text landing on your phone. If it feels lighter, and it will, add the rest. Priya did it one class at a time over a fortnight, and the day she finally deleted the group chat she said it felt like putting down a bag she'd forgotten she was carrying. ### Running a weather-dependent park bootcamp without the 6am group-chat chaos How one park bootcamp swapped a chaotic group chat for proper bookable sessions, with the weather on the card and rainy mornings that credit everyone on their own. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/outdoor-bootcamp-group-training-booking · markdown: https://bookatu.com/blog/outdoor-bootcamp-group-training-booking.md > **The short version** > > - Put each fixed morning session online with a set time and a per-person price, cap the spots, and people book and pay in one go > - Add the park's address and directions to the session so nobody circles the car park at 6am looking for you > - Show a live weather forecast on each outdoor session so people book with their eyes open > - If the rain wins and you call it off, everyone is auto-credited and emailed, so no awkward refund chase #### A wet Tuesday and 40 unread texts Sam runs a bootcamp in a park in the eastern suburbs. Tuesday, Thursday and Saturday, 6am, rain or mostly shine. For the first two years he ran the whole thing off a group chat and his own memory. It worked, sort of, until the morning it very much didn't. One Tuesday the forecast turned overnight. Proper rain, the kind that turns the grass into soup. Sam called it off at 5am and fired a message into the group. By 6.15 he had 40-odd texts back. Some people never saw the message and drove down anyway. Two of them had paid for a 10-session pack and wanted to know if the cancelled morning came off their count. One woman asked, fairly, whether she was getting her money back or not. Sam spent his whole rest day doing refund maths in a notebook. He told me later the training was never the hard part. Standing in a field yelling encouragement at people doing burpees, that he loved. It was everything around it. Keeping track of who'd paid and who was coming, and reaching everyone when the weather ate the morning. #### A session is a real thing people book, not a maybe The thing that changed it for Sam was treating each morning as a proper bookable session rather than a standing invitation. A session on Bookatu has a date and a start time, a cap on how many spots there are, the park it runs in, and a price per person. People find it, see there are, say, four spots left, book their spot and pay right there. No chasing, no bank transfers with someone's initials in the reference field. Because there's a spots limit, the session simply closes when it's full. Sam capped his Saturday session at 16 because that's all he can coach well at once. When the sixteenth person books, that's it, it shows as full. He's not turning up to find 25 people and eight kettlebells. And the money side stops being a monthly headache. Everyone pays as they book, so by the time Sam laces up on Saturday morning the session is already paid for. He's not the guy standing in a park chasing a mate for the cash afterwards. #### Put the park on the card Sounds small, but it mattered more than Sam expected. Each session carries its own venue, the actual address plus a line of directions. His park has three entrances and only one of them lands you near the flat bit of grass he uses. So the session says exactly that. Park on Marine Parade and come in by the playground gate, where the orange flags are. New people used to text him the night before, a bit anxious, asking where exactly to go. That mostly stopped. The information lives on the session where they book, so they read it once and turn up in the right spot. First-timers being nervous is normal. Making them hunt for you in the dark isn't. #### The weather, out in the open For an outdoor bootcamp the weather is the whole game, so it sits right on the session card. Each outdoor session shows a live forecast for that morning. People booking on Thursday for Saturday can see what's coming and go in knowing exactly what they signed up for. Nobody's surprised, nobody feels tricked when it's a bit brisk. When it does turn genuinely ugly, Sam cancels the session and that's the end of the drama. Everyone who booked is credited automatically and gets an email telling them it's off. No group-chat pile-up, and no refund maths in a notebook on his day off. The credit sits there ready for them to put toward the next morning. Here's how he put it: > The first rainy Tuesday after I switched, I hit cancel from my kitchen and put the kettle on. That was the whole job. I kept waiting for the 40 texts and they never came. #### Not everything is a group thing A fair few of Sam's regulars also wanted one-on-one time. Someone coming back from a knee thing, someone training for a first half marathon who needed a plan that wasn't shouted across a field. Those aren't group sessions, they're ordinary appointments. So the 1:1s book like any normal appointment on his calendar, at a time that suits both of them, while the bootcamp mornings stay as capped group sessions. Same page, two different shapes, and Sam isn't juggling two systems to make it work. A quick way to picture what he runs now: - Group sessions in the park on Tuesday, Thursday and Saturday, capped and paid up front, with the weather on the card - Rainy-day call-offs that credit and email everyone on their own - One-to-one appointments for the people who want a bit of focused coaching - A single view of who's coming to each morning, without a group chat to babysit #### The quiet bit that grew it Bootcamps grow by word of mouth more than almost any other business I can think of. One person drags a mate along on a Saturday and suddenly there are three of them. Sam leaned into that on purpose. Every regular has a referral link they can send to a friend, and when that friend books their first session, the friend who brought them gets rewarded for it. He didn't make a big song and dance about it. It just sits there for the people who love the sessions anyway, and those are exactly the people who talk. A woman named Priya brought four of her running club over two months, which more than paid for her own training and gave Sam his most reliable Saturday crew. She'd have told them regardless. The link just meant she got something back for doing it. #### If your mornings live in a group chat You don't have to overhaul anything to start. Take one session, this Saturday's, and put it up with a time, a cap, the park's address and a price. Let a handful of your regulars book it and pay. Watch one wet morning get cancelled and credit everyone without you touching a thing. If it feels lighter than the group chat, and it will, move the rest across. Your job is coaching people in a park at dawn. The admin can look after itself while you do the part you actually signed up for. ### How a Weekend Golf Coach Filled His Saturday Clinics Without Chasing a Single Text Marcus runs group clinics at a driving range every Saturday morning. Here's how he stopped juggling payments and cancellations, and started letting people book and pay for a spot online in about a minute. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/golf-coaching-clinic-booking · markdown: https://bookatu.com/blog/golf-coaching-clinic-booking.md Marcus coaches golf at a driving range on the edge of Hamilton. Every Saturday morning he runs a group clinic, eight players out on the mats, working through the same fault most weekend golfers share, which is a swing that starts fine and falls apart under the weight of thinking too hard. He is good at it. What he was not good at, for a long time, was the part that happens before anyone picks up a club. > **The short version** > > - A weekend group clinic is a fixed date and time with a set number of spots, and people book and pay their share online before they show up. > - Each clinic has its own venue address and directions on the card, plus a live weather forecast because golf lives and dies by the sky. > - If the weather turns and you call it off, everyone is refunded automatically and gets an email, so no one is left chasing you. > - One-to-one lessons stay simple appointments, and happy players can be sent a referral link that rewards them for bringing a friend. #### The Saturday that broke him For about two years Marcus ran the whole thing off his phone. People would text him on a Wednesday asking if there was room this weekend. He would scroll back through his old messages trying to remember who had already said yes, then reply once he had a rough count. Then came the money. Some paid on the day in cash. Others forgot their wallet and paid him back the following week, if he remembered to ask. He was effectively running a small business through a group chat and his own memory, and both were getting full. The morning it tipped over was a wet one in April. He had eleven people who thought they were booked for eight spots. Three had cancelled by text but he had missed two of the messages. When the rain came in sideways at quarter to nine he had to stand in the car park calling people one by one to tell them not to bother driving over, and then spend Sunday sorting out who had paid for a clinic that never happened. He told me later that he loved the coaching and had come to quietly dread everything around it. #### Turning a clinic into something people can just book The fix was smaller than he expected. Instead of a clinic living inside his head, it became a thing on a page. He sets up the Saturday session with a date and a start time, and caps it at eight spots. He adds the range address so the directions sit right there on the card, which matters more than you would think because two of his regulars had turned up at the wrong range in his first month. He sets a price per person, then shares the link. From there, people book themselves in. They pick the clinic and pay their share online, and the spot count ticks down on its own. When it hits eight it says full, and nobody can squeeze in past that. Marcus does not have to count anything or remember anything. He opens the page on Saturday morning and there is his list, already paid and ready to go. > I used to spend more time being an accountant than a coach. Now I turn up and I know exactly who is coming, and the money is already sorted. I just teach. #### The weather does the worrying now Because a driving range is an outdoor business, the thing that used to keep Marcus up on Friday nights was the forecast. Now the clinic card carries a live weather forecast for the day, so anyone booking can see for themselves what Saturday is shaping up to look like. It quietly sets expectations. Someone booking a spot for a morning that shows heavy rain already knows what they might be signing up for, and Marcus fields far fewer nervous messages about whether it is still on. And when a morning really is a write-off, he does not stand in the car park with his phone anymore. He cancels the clinic in one go. Everyone who booked is credited back automatically and gets an email letting them know it is off. There is no refund spreadsheet and no awkward Sunday texts. Nobody is left wondering whether they lost their money. The players who got rained out one week are the same players who book again the next, partly because the cancellation was handled so cleanly they never had to think about it. #### Keeping the one-to-one lessons simple Not everything Marcus does is a group. He still takes private lessons through the week, usually people wanting to fix one specific thing before a club competition. Those are just normal appointments. Someone picks a time that suits them and books it, and it lands in his schedule alongside the clinics. He did not want two separate systems for two ways of teaching, and he does not have one. The group clinics and the private lessons sit in the same place, and his Saturday cap never gets blown out by a private booking sneaking into the same slot. The clinics carry the bulk of his weekend income, but the private lessons are often where a nervous beginner starts before they feel ready to stand next to seven other people. Having both easy to book in one spot means a first-timer can move from a quiet one-to-one into a Saturday group without any fuss, and without asking him to arrange anything by hand. #### Letting the regulars bring the crowd The part Marcus did not plan for was how his clinics started filling themselves. Golf is a social thing. People come off the mats after a good session and want their mate to feel the same. So he started sending his regulars a referral link they could pass on, and rewarding them when someone they sent along actually booked a clinic. - A regular finishes a Saturday clinic feeling sharp and texts the link to a golfing buddy that afternoon. - The friend books their own spot for next weekend straight off the link, paying online like everyone else. - The regular gets their reward for bringing someone new, so word of mouth actually pays them back. - Marcus watches a clinic that used to take a week of texts to fill quietly sell out on its own. He is not paying for ads. His best marketing is eight people who had a good morning and know exactly how to send the next person over. The link just makes that easy and gives them a reason to bother. #### What actually changed The clinics themselves look the same from the outside. Eight players on the same mats, working the same faults he has always gently corrected. What changed is everything around them. Marcus no longer runs his business from his memory. He does not chase anyone for money, and he does not stand in the rain making phone calls. He opens a page, sees who is coming, teaches, and goes home. On the weeks the weather turns, it sorts itself out and everyone is looked after. If your Saturdays look anything like his did, with more time spent counting heads and chasing payments than coaching, it might be worth setting up your next clinic as something people can just book and pay for online. Start with one session. Put the address and the forecast on it, and see how it feels to turn up already knowing your morning is full. ### Run 1:1 sessions and small-group training without the diary chaos A personal trainer's day only holds so many one-on-one hours. Here's how adding small-group sessions, booked and paid for online, lets you fill a morning with six people instead of one, without the back-and-forth. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/small-group-personal-training-booking · markdown: https://bookatu.com/blog/small-group-personal-training-booking.md > **The short version** > > - Keep your best clients on private 1:1 sessions, booked as normal appointments. > - Add small-group sessions with a set date, a start time, a spots limit and a per-person price, so one hour can earn from six people instead of one. > - Each session card shows the venue name, its address, directions and a live weather forecast, so nobody turns up to the wrong park in the rain. > - If the weather calls it off, you cancel the session and everyone is auto-credited and emailed, no refund admin on your Sunday. Marcus runs a small training setup out of a park in Onehunga, plus a hired studio two mornings a week. For three years he did everything one-on-one. Good work, steady clients, but his diary hit a ceiling. There are only so many hours before the sun comes up, and he was giving nearly all of them to single clients who each wanted the 6am slot. Demand was never the problem. His best hours simply couldn't hold more than one person at a time. #### The maths that keeps a trainer stuck Every trainer works this out eventually. If you charge, say, 80 dollars for a private session and you have twenty good hours a week, your week is capped at 1,600 dollars before you burn out or start turning people away. You can raise your prices, and you probably should at some point. But there is a quieter option that most people leave on the table. Some of the work you do one-on-one is honestly fine to do with a handful of people at once. A conditioning circuit. A beginner's strength morning. A mobility session. A Saturday clinic for the running crowd training for a half marathon. Marcus tried it the messy way first. He put a Saturday circuit up on his Instagram story, asked people to DM him, and spent the week chasing bank transfers and answering the same questions over and over. Who is coming. Where do we meet. What do I bring. Is it still on if it rains. By Friday he had a handful of maybes and a headache. The idea was right. The admin was killing it. #### Small-group sessions, booked like a class A group session is different from a private appointment, so it works differently. Instead of an open slot that one person claims, you set a fixed session with a date and a time. You give it a spots limit, say six or twelve, and a per-person price. People find it on your page, see how many spots are left, book their place and pay right there. When the last spot goes, it closes itself. No overbooking, no awkward 'sorry, we're actually full' message after someone has already turned up. That one change is what breaks the ceiling. Marcus's Saturday circuit at eight people times 25 dollars is 200 dollars for the same hour he used to sell once. He still runs his private sessions for the clients who want them, booked as normal appointments, and those stay premium. The group mornings just fill the hours that used to sit empty or hold a single person. #### Outdoor training and the weather problem If you train in a park, you already know weather is half the job. Marcus's group cards show the venue, its own address, a directions link, and a live forecast right on the card for the outdoor ones. So when someone is deciding whether to book Saturday's beach session, they can see it's meant to be clear, and they know exactly which entrance to the reserve to walk to. Fewer texts asking 'where do we actually meet', fewer people wandering the wrong end of the car park at ten to seven. And when the sky does open up, this is the part that saved Marcus his weekends. He opens the session, cancels it, and that's it. Everyone who booked is automatically credited and emailed. He isn't sitting there on Sunday night doing eight manual refunds and apologising in eight separate chats. The credit sits ready for the next session they book. One tap for him, a tidy heads-up for them. #### A week in Marcus's diary now The shape of his week changed without him working more hours. If anything he works slightly fewer, because the group mornings do more per hour. A typical week looks something like this: - Three early 1:1 sessions for his long-standing clients, booked straight into open slots with no messaging required. - Two small-group conditioning mornings at the park, capped at eight, weather forecast sitting on each card. - One Saturday beginners' clinic at the studio, indoors, so it runs whatever the sky does. - A quiet Sunday, because a rained-off session credits itself instead of eating his evening. #### Let your regulars bring the next ones The other thing that grew Marcus's groups wasn't advertising. It was his own clients. Group sessions are social by nature, and people who train together talk. So he started sending his regulars a referral link, the kind that rewards them when a friend books in. His Saturday crowd turned into his best marketing, because someone who has just had a good morning at the park is genuinely happy to tell a mate to come along. He didn't have to push it. The link just made the thing people already do a little easier, and gave them a small thank-you for it. > The week I stopped chasing transfers and started running actual sessions was the week the whole thing finally felt like a business, not a group chat. #### Where to start if this is you You don't have to rebuild your whole week. Pick one thing you already do privately that would work fine with a few people in it. A circuit, or a beginners' morning built around one specific goal. Set it up as a group session with a date, a cap, a price and a venue, put it on your page, and send it to the handful of clients you know would say yes. See how the first one goes. If a park session fills and the forecast turns on you, you'll find out how much lighter the cancel-and-credit flow feels than a night of manual refunds. That first full session is usually the moment it clicks, so start there and let the next ones follow. ### Booking that fills every class at your boxing gym A kickboxing coach was overbooking his Saturday class and quietly losing money to no-shows. Here is how putting each class online, forecast and all, sorted it out for him. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/boxing-gym-group-classes-booking · markdown: https://bookatu.com/blog/boxing-gym-group-classes-booking.md > **The short version** > > - Turn each class into something people can book and pay for online, with the date, time, spots left, and price all sitting on the card. > - Fill the room before the day instead of guessing who will turn up on the night. > - For outdoor sessions, show the live forecast on the card. If the weather calls it off you cancel once and everyone gets auto-credited. > - Keep private pad work as ordinary appointments, and hand your regulars a referral link that actually rewards them for bringing a mate. #### The Saturday that made Deacon rethink the whiteboard Deacon runs a kickboxing gym called Ironbridge, tucked into an old panelbeater's unit in Onehunga. Sixteen bags hang from the ceiling, and the 8am Saturday class is the one everyone wants. For two years he ran the sign-ups off a whiteboard by the door and a running thread of texts on his phone. One Saturday last winter it caught up with him. Twenty-two people wrapped their hands for sixteen bags. He had to turn four away at the door, including a woman who had driven in from Mangere for her first class. Two of the names on his list never showed, so the room was somehow both overbooked and short on money. He spent the drive home doing sums in his head and not liking the answer. The problem was never the coaching. It was that nobody, Deacon included, could see the real state of a class until the moment it started. #### Turn every class into something people book and pay for The fix was to stop treating a class like a mystery and start treating it like a ticket. On Bookatu, each class becomes a group session with a fixed date and time, a cap on spots, a venue, and a price per person. People find it, book their place, and pay right then. The spot count ticks down in front of them, so when it says two left, that is the truth. For Deacon that meant the 8am class was full and paid for by Thursday night. No more turning people away at the door, because the door had already sorted itself out online. And the folks who used to say maybe now either committed or they didn't, which honestly told him more than a vague yes ever had. - The date and start time, so nobody has to ask when the next one is. - How many spots are left, counting down as people book. - The venue address with directions, handy when you run a pop-up somewhere new. - The price per person, paid at the time of booking. Bookatu takes no commission on any of it, so the price a client pays is the price Deacon set. Nothing gets shaved off the top for the privilege of being booked. #### For the outdoor rounds, the weather is right there on the card In summer Deacon runs a Tuesday evening bootcamp down at the park by the water. Great for numbers, at the mercy of the sky. Outdoor group sessions carry a live forecast right on the booking card, so someone signing up on Sunday can see what Tuesday is shaping up to be. A bit of drizzle and the hardy ones still come. A southerly front rolling in and they can plan around it. When the weather genuinely wins, Deacon opens the session and cancels it. Everyone who booked gets credited automatically and an email lands in their inbox letting them know. He doesn't spend his evening replying to fifteen texts asking if it's still on, and nobody turns up to an empty, soaked field wondering where the coach went. > The first time it rained out a bootcamp and I just tapped cancel, the credits and the emails went out on their own. I sat there with a cup of tea like, that's it? #### Private lessons stay as simple as they should be Not everything is a group. Plenty of Deacon's income is the quiet one-on-one work. A nervous beginner who wants a private hour before they'll set foot in a class, or a fighter sharpening up before a card. Those book as normal appointments against his own calendar. Someone picks a time that's actually free, books it, and it's done. No back and forth, and no double-booking himself onto a Saturday he'd promised the family. #### Let your regulars bring the next ten people Here's the part Deacon didn't expect to matter as much as it did. His best marketing was never a flyer. It was the woman from the 8am class telling her sister it's the best hour of her week. So he started handing his regulars a referral link they can text straight to a mate. When that mate books their first class, the gym rewards the person who brought them. It costs him a little off one class, and it turns a room full of happy regulars into a room that quietly grows itself. The people who already love the place get a reason to spread the word, and a way to do it that takes ten seconds on the couch. #### If your classes feel busier than your books If any of this sounds like your gym, the whiteboard, the text thread, the cash tin, and the four people turned away at the door, it might be worth putting one class online and seeing how it feels. Pick your fullest session, the one people fight to get into, and let them book and pay for it ahead of time. See what a class that's full by Thursday night does to your Saturday morning. Deacon would tell you the quiet is the best part. ### Booking lessons and group classes without losing your evenings A guitar teacher's tale of taking 1:1 lessons and small group classes online, capping seats, taking payment up front, and turning a rained-off park session into one calm tap instead of an hour of refunds. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/music-school-lesson-booking · markdown: https://bookatu.com/blog/music-school-lesson-booking.md > **The short version** > > - Take 1:1 lesson bookings online so your evenings stop filling up with phone tag > - Run your group classes as fixed-time sessions people book and pay into up front > - Each session shows the venue, the address, how many spots are left, and the price per person > - Cancel a session in one tap and everyone gets their money back automatically, no awkward refund chats Marcus teaches guitar and a bit of ukulele out of a converted garage in Christchurch. He's good at it. Kids stick around for years, parents send their nieces and nephews, whole families end up cycling through, and every so often a nervous forty-year-old turns up wanting to finally learn the three chords behind every song they love. What Marcus was not good at, by his own cheerful admission, was the admin. His Tuesday nights used to end with a notebook full of half-legible times and a nagging worry that he'd double-booked the 5pm slot again. There were always a couple of texts he still hadn't answered. #### The thing that actually eats your evenings If you teach music, the teaching is rarely the hard part. The hard part is everything around it. Somebody wants to move their Thursday lesson to Friday. A parent asks, for the fourth time, whether there's space in the beginner group, and a new student messages at 10pm wanting to know what you charge and whether you take total beginners. Each message is small on its own. Put together, they turn into a second unpaid job you do from the couch. Online booking for your 1:1 lessons fixes most of that quietly. A student picks a slot you've actually marked as free, and it lands straight on your schedule. No back and forth, no double-booked 5pm. Marcus put his weekday afternoons and two evening blocks online and blocked out the school run. The reschedule texts basically stopped. People just moved their own lessons around inside the times he'd already said yes to. #### Group classes are a different animal, and they should be treated like one A one-to-one lesson is an appointment. A group class is an event. Same building, completely different shape. Ten people need to land on the same date at the same time in a room that only holds so many, and you'd quite like to be paid before they show up rather than chasing five-dollar notes at the door. So instead of trying to squeeze a class into an appointment slot, you post it as a session. You set the date and time, say how many spots exist, put in the venue with its address, and set a price per person. People book their own place and pay right then. When the last spot goes, the session closes itself. Marcus runs a Saturday morning "strum along" for adult beginners, capped at eight, and for the first time he could see at a glance who was coming and who'd paid. No spreadsheet. No mental maths at 8am with a coffee going cold. The little details are what make it feel professional to the person booking. The card shows the real address and directions, so nobody messages you asking where to park. It shows how many spots are left, which does something funny to all of us: "2 spots left" gets people off the fence faster than any discount you could offer. #### When you run something outdoors Not every music thing happens in a garage. Marcus does a summer session in the park, guitars and a picnic blanket, once the weather warms up. Outdoor plans and the sky have a complicated relationship. For any session you mark as outdoor, the booking card carries a live weather forecast, right there next to the date. People can see for themselves whether Saturday's looking kind. And when the forecast turns on you, which it will, you don't spend the morning writing ten apology messages and working out refunds one at a time. You cancel the session. That's the whole action. Everyone who booked gets credited automatically and gets an email telling them so. Their money's back and they already know it's off, so you got to keep your morning. Here's how Marcus put it after the first washout: > I used to dread cancelling anything because cancelling meant an hour of refunds and saying sorry. Now it's one tap and I go make breakfast. The park session gets rained off and honestly nobody minds, because they've already got the email and their credit before I've even put the kettle on. #### Where your next students actually come from Here's a thing every music teacher already knows but rarely leans on. Your best marketing is the parent standing in your doorway saying their kid loves it. Word of mouth is the whole game in this business. So make it easy to pass along. You can send any student or parent a referral link that's theirs. When someone they've sent books a lesson, that first person gets a reward you decide on. Marcus does a free lesson for every three people you bring in, and it turns out parents at the same primary school talk to each other constantly. He didn't run a single ad. He just gave his happiest families an easy way to do the thing they were already doing, and rewarded them for it. #### What this frees you up to do Put the boring stuff on rails and you get your actual life back. The software itself is beside the point. What matters is the four things it quietly hands you: - Your 1:1 lessons book themselves into slots you've already approved, so no more reschedule tennis - Your group classes take payment up front and cap themselves, so you walk in knowing exactly who's coming - A rained-off session becomes one tap and an automatic credit instead of an hour of apologies - Your happiest families get a simple link that turns their good word into new students And because Bookatu doesn't take a commission on your bookings, the money your students pay is the money you keep. For a teacher charging thirty or forty dollars a lesson, that difference is not small over a year. If your Tuesday nights currently end with a notebook and a nagging worry about the 5pm slot, maybe start where Marcus did. Put next week's lessons online and post one group class as a proper session, then see how quiet your phone gets. You can always add the park sessions once summer shows up. ### How one nail studio stopped drowning in messages and let clients book themselves A small Mount Eden nail studio was drowning in booking messages until it let clients book their own appointments and filled its slow days with group sessions that regulars now bring their friends along to. A plain, human look at how online booking and referrals grow a salon. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/nail-salon-online-booking-referrals · markdown: https://bookatu.com/blog/nail-salon-online-booking-referrals.md > **The short version** > > - Let clients book their own appointments online at any hour, without a single phone call > - Fill your quiet Tuesdays with group nail sessions people book and pay into ahead of time > - Send happy clients a referral link and reward them when a friend books > - Keep every cent you earn, because Bookatu never takes a commission #### The Sunday that broke Priya Priya runs a small nail studio on a side street in Mount Eden. Two chairs, a good coffee machine, a stack of well-thumbed magazines, and a window box she waters herself. She is brilliant with a gel finish and hopeless with a diary. For two years her booking system was her phone, and her phone did not respect her weekends. One Sunday she counted them. Nineteen messages. Some on Instagram, some on WhatsApp, one or two by text, and two on a Facebook page she forgot she had. A woman named Kate asked for a Thursday slot at 9am, then again at 9:14, then apologised for double-messaging. By the time Priya replied, Kate had booked somewhere else. That was the moment Priya decided the phone was not going to run her business anymore. #### The booking link that answers at 11pm She set up a page on Bookatu and put the link in her Instagram bio. Her services sat there in plain view, each with a price and a length. A client picks a treatment and books herself straight into one of Priya's actual free times. No back and forth. No screenshot of a calendar. It just happens. The part Priya did not expect was the timing. People book when they think of it, and they rarely think of it during salon hours. A gel refill booked at 11:40pm. A birthday manicure booked on a bus. Her page was open while she slept, quietly filling the week, and she woke to a diary that had grown overnight without her lifting a finger. > I used to lose the ones who messaged after closing. Now I wake up and they've already booked themselves in. It feels like having a receptionist who never sleeps and never asks for a raise. #### Turning a slow Tuesday into a party Tuesdays were her problem child. Quiet and a little dispiriting. So she tried something. She set up a group session, a two-hour Galentine's nail evening, eight spots, one price per person, a fixed date and time. She popped a little prosecco allowance in the description and shared the link around. It sold out in three days. Eight women paid up front online, so there was no chasing and no last-minute drop-outs eating her evening. The session card showed the studio address with directions built in, so nobody arrived confused or texting from the wrong end of the street. She ran it again the next month. Now her Tuesdays have a waitlist. Group sessions suit nails better than you would think. A few of the things Priya now runs on a fixed date and time: - A beginner's at-home care workshop, teaching people to make a manicure last - A seasonal press-on party where everyone leaves with a set for the weekend - A nail-art evening for teens, booked and paid for by parents in one go - A bridal-prep morning where the bride and her friends come as a group For the odd client who wants Priya to herself, nothing changed. A one-on-one full set is still just a normal appointment, booked the usual way. The group sessions sit alongside the everyday bookings, not in place of them. #### When she runs a session in the park Once a season Priya does a summer pop-up, a little outdoor nail-and-picnic thing in the Domain when the weather plays along. Outdoor sessions on Bookatu carry a live weather forecast right on the card, so people can see what they are booking into before they commit. It saves a hundred anxious what-if-it-rains messages. And when the forecast turns nasty, she does not have to text eight people one by one with the bad news. She cancels the session, and everyone is automatically credited and emailed. No refunds to fumble, no awkward apologies typed out at midnight. The rain is annoying, but at least it is not also admin. #### Letting good clients do the selling Here is the thing Priya knew all along but never acted on. Her best marketing was already sitting in her chairs. People compliment each other's nails constantly. A woman leaves the studio, someone at work asks who did them, and that is a new client Priya never had to pay for. So she started sending clients a referral link of their own. When a friend books through it, the friend gets a little something off their first appointment, and the client who sent them gets a reward too. Kate, the same Kate who once booked elsewhere out of impatience, has now sent four friends through her link. Priya reckons Kate has turned into her best salesperson, and Kate does not even know it. She just likes her nails and likes talking about them. It costs Priya almost nothing and it compounds. One happy client brings two. Those two mention it at brunch, and soon the studio fills without a single ad. The referral reward is small. The trust that comes attached to it is not. #### What actually changed A year on, Priya's phone is just a phone again. She checks it because she wants to, not because her income depends on how fast she replies. Her Tuesdays are booked and her outdoor pop-ups run without the weather panic. New faces arrive too, already recommended by someone they trust. And because Bookatu takes no commission, every dollar of it is hers. The group sessions, the late-night bookings, the friends of friends, the summer pop-ups in the park, all of it lands in full. If your own phone has started to feel like a second job, you do not have to overhaul everything at once. Put your booking link where your clients already are, then try a single group session on one quiet day. See who turns up. That is usually all it takes to feel the weekend come back to you. ### How a Small Restaurant Filled Its Quiet Nights With Online Reservations How a twenty-eight seat trattoria stopped losing tables to a ringing phone and filled its quiet midweek nights with fixed-time supper clubs people book and pay for online, with happy regulars bringing the crowd and no commission to pay. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/restaurant-online-reservations · markdown: https://bookatu.com/blog/restaurant-online-reservations.md > **The short version** > > - Taking reservations online means fewer missed calls during the dinner rush and a table plan you can actually trust. > - Your quieter nights are perfect for fixed-time events people book and pay for in advance, like a Tuesday pasta night with a set number of seats. > - When guests love a night, a referral link lets them bring friends and earns them a little thank-you from you. > - You keep every dollar. Bookatu charges no commission on the bookings that come through your page. #### The phone that never stopped ringing Rosa runs a twenty-eight seat trattoria on a side street in Kingsland. Small kitchen, one long communal table down the middle. She rewrites the chalkboard menu most mornings. For years her booking system was a spiral notebook by the counter and a phone that rang at exactly the wrong moments. Someone would call to book a table for six on Saturday right as she was plating four mains, and she would either let it ring or scribble a name so fast she could not read it back later. The worst part was not the busy nights. It was the quiet ones she never saw coming. A Wednesday would arrive half empty because the two tables she thought were booked had never actually confirmed, and a walk-in she turned away on Friday had wanted that exact slot. She was losing covers she never even knew about. #### Letting people book their own table The first thing Rosa changed was simple. She put a reservation link on her Instagram bio and at the bottom of the menu. Now when someone wants a table, they pick a night and a time that is genuinely open, then pop their name and number in. No call. No notebook. The table shows up on her plan the moment they hit confirm, and she gets a quiet notification instead of a ringing phone. What surprised her was when the reservations came in. Not during service. They landed at eleven at night when someone was lying in bed deciding where to eat that weekend, or on a Sunday afternoon when the restaurant was closed and she was at the market. The bookings kept arriving while she was living her life, which is the whole point of letting people do it themselves. She also stopped losing the details. Every reservation carries the party size and the time in one place, right alongside any note the guest left. When a regular writes ahead about a nut allergy or a birthday, it is there in the booking, not lost on a sticky note that fell behind the coffee machine. #### Turning the slow nights into something people book into Once the everyday reservations were sorted, Rosa looked at her quiet midweek nights differently. Instead of hoping a few tables would wander in, she started running fixed-time events people could book a seat at and pay for up front. Her first one was a Tuesday pasta night. One sitting, seven o'clock, sixteen seats, one price per person for four courses she chose that morning. She set it up as a group session on her booking page, and people reserved their spot and paid the moment they booked. By the Sunday before, fourteen of the sixteen seats were gone. She knew exactly how much dough to make and how much wine to bring in, because the night had sold itself before she lit the stove. A group session works well for a small restaurant because it gives a normally uncertain night a shape: - A set date and time, so everyone arrives together and the kitchen sends one beautiful service instead of a scattered trickle. - A seat limit, so the room is full but never oversold, and you cook for a number you can count on. - A price per person paid at the time of booking, so the night is covered before the first plate leaves the pass. - Its own little event page with the address and directions, so first-timers find the door without texting you for the cross street. She ran a courtyard supper club in summer too, out in the little back garden under the string lights. Because it was outdoors, the booking card showed a live weather forecast for that evening, so guests could see for themselves what the night looked like before they committed. When a storm rolled in one Friday and the courtyard was clearly a washout, Rosa cancelled that session with one tap. Everyone who had booked was refunded to their account and emailed straight away, so nobody was left standing in the rain wondering, and nobody had to chase her for their money back. #### When guests bring their own crowd The pasta nights did something Rosa did not plan for. People wanted to bring friends. So she started sending guests a referral link after a night they enjoyed. When a friend booked through that link, the person who sent it earned a small thank-you toward their next visit, a little off the bill or a glass on the house. It changed the feel of the room. A regular named Theo brought three different couples over two months, and each of them came back on their own afterward. Rosa was not paying for ads or boosting posts. Her happiest guests were quietly doing the inviting, and she was thanking them for it, which felt a lot more like her restaurant than any billboard ever would. #### What it actually changed Rosa still writes the menu by hand every morning, and the phone still rings sometimes. She likes it that way. What went away was the guessing. She walks in now knowing roughly how the night will land, because the reservations and the paid seats are sitting there on her plan waiting for her. None of this took a tech overhaul or a course. She set up her page one rainy afternoon between lunch and dinner. Then she put the link where her guests already look, and let them do the rest. And because Bookatu takes no commission on those bookings, the money her tables bring in stays with her kitchen, where it belongs. If your quiet nights have been keeping you up, maybe start the way Rosa did. Pick one slow evening and give it a set time and a fixed number of seats. Then see who books in. You might be surprised how a Tuesday fills up once you let people claim their place at the table. ### Fill every day of your school-holiday sports camp How Bex, who runs a school-holiday sports camp out of a New Lynn park, put every camp day online so it fills itself, forecast and rain-outs included. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/kids-holiday-sports-camp-booking · markdown: https://bookatu.com/blog/kids-holiday-sports-camp-booking.md Bex runs a holiday sports camp out of a park in New Lynn. Touch rugby, cricket, a bit of soccer, and a capture-the-flag game at the end of the day that the kids talk about for weeks. The camp itself she has down cold. It was the bookings that used to undo her. Every school holidays the same mess landed on her kitchen table: a spreadsheet, a stack of texts, two parents who'd paid twice, and one who swore she'd paid and hadn't. > **The short version** > > - Put each camp day online with a spots limit, so it fills and then quietly closes itself. > - Parents see the date, the park, the directions and the price on one card before they pay. > - Outdoor day? The forecast sits right on the booking, so nobody's guessing about the weather. > - Rain calls it off? Cancel the day and every parent is credited and emailed on the spot. #### A camp day is just a booking Here is the shift that made it click for Bex. Each day of camp is one thing parents book and pay for online, ahead of time. Monday the 7th is its own listing. Tuesday the 8th is another one. A parent picks the days that suit their week, pays for them right there, and they are in. No holding a spot on trust, no waiting on a reply. Every day carries the details that used to live only in Bex's head, all on the one card: - The date and start time, so there's no muddle about which morning is which. - The park it runs at, with its street address and a directions link. - The price per child, paid online at the moment they book. - How many spots are left, ticking down as families sign up. #### Let the spots do the door work Bex caps each day at twenty-four kids. That is what she can coach properly with the helpers she has. So each day online has a limit of twenty-four, and once it is full it closes itself. No more "is there still room?" texts at ten at night. No accidentally taking a twenty-sixth child and having to walk it back with an awkward phone call. The first July she ran it this way, the Wednesday sold out by Sunday night. She woke up to a full day and a couple of messages asking if she would open a second one. That is a good problem to have, and a long way from chasing people for numbers on the Friday before. #### The weather question, answered before they ask Camp is outdoors, so the weather question never really stops. It used to arrive as a slow drip of texts the night before. Will it still be on if it rains? What's the forecast looking like for Thursday? Bex would end up forwarding weather screenshots from the couch at nine o'clock. Now the forecast for each day sits right on the booking card. A parent looking at Thursday can see Thursday's outlook while they decide. It does not stop the rain, but it heads off half the questions. People book with their eyes open instead of hoping for the best. #### When the sky opens anyway Some mornings the rain simply wins. One Thursday last winter it came down sideways from dawn and the park was a swamp by seven. Bex called it off. In the old days that meant a whole morning of refunds and sorry-about-this messages, one parent at a time, while she should have been drying out her cones and her gear. Calling off a day is a single step now. Everyone booked onto it is credited automatically and emailed to say so. Parents can drop that credit straight onto another day that same week, or simply hold it for next time. Bex still sends a short note of her own on top, because that is who she is, but the money side is sorted before she has finished her coffee. #### For the kid who wants extra Every so often a kid catches the bug properly. Last summer it was a nine-year-old named Theo who wanted to work on his goal-kicking over and over, long after the others had wandered off to lunch. His mum asked whether Bex ever did one-on-one sessions. She does, and those work a little differently. A private lesson is not a fixed camp day with a crowd around it. It is a single appointment at a time that suits the two of them. Same booking page, so Theo's mum grabbed a Tuesday afternoon without a phone call. Camp days for the group, and quieter one-on-ones for the kids like Theo who want more. #### The parents end up doing your marketing The best advertising Bex gets is a parent at the school gate telling another parent their kid had the best week of the whole holidays. She leans right into that. Every family who books gets a link they can pass on to friends, and when a new family books through it, both sides get a little something back off their next run of days. The camp fills faster, and the parents who love it feel looked after for spreading the word. > The camp was never the hard part. I love the coaching. It was the Friday nights doing refunds by hand that nearly put me off running the whole thing again. #### Getting your first day up If your holidays are coming up and the thought of the sign-up scramble is already tightening your shoulders, start with one day. Put next Monday's camp online, set the cap at whatever you can coach well, add the park and the price, and send the link to the families who came last time. Watch that one day fill, then build the rest of the week out behind it. The kids will still remember the capture-the-flag game either way. This just gives you your Friday nights back. ### How a barber shop filled its chairs and stopped the no-shows A New Plymouth barber was losing four cuts every Saturday to no-shows. Here's how online appointments and a small deposit turned his best day of the week back into a full one. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/barber-shop-online-booking · markdown: https://bookatu.com/blog/barber-shop-online-booking.md > **The short version** > > - People can book an appointment at Copperline at eleven at night, with no text to Theo and no waiting for a reply in the morning. > - A small deposit taken when someone books turned a Saturday full of empty chairs into almost none. > - Fixed-time group sessions, like Theo's outdoor pop-up cuts, sell their spots in advance and credit everyone back automatically if the weather calls it off. > - Loyal clients get a referral link to pass around, and the shop says thank you with money off their next cut. #### Four empty chairs on a good Saturday Theo Marsh runs Copperline, a two-chair barber shop on a quiet street in New Plymouth. For the first couple of years he booked the way a lot of barbers do. People slid into his Instagram messages, and he scribbled the names into a paper diary by the mirror. Most weeks it held together well enough. Then there was a Saturday in March. He had a full sheet, back to back from nine, and he felt good walking in. By early afternoon four of those names had simply not shown up. One of them he'd chased by text and got nothing back. The part that stung was the ten o'clock. A walk-in had wandered past the window at quarter to. He saw Theo standing there and asked if he had time. Theo said no, sorry, I've got someone at ten. That someone never came. So he'd turned away real money to hold a chair for a ghost. He did the sums that night on the back of a receipt. Four missed cuts on his best day of the week, every week, adds up to a small holiday he wasn't taking. #### Letting people book themselves The first change was the easy one. Theo put his appointments online, so anyone could see his open times and grab one without going through him at all. A page with his services and prices, plus the open slots in his day. What surprised him wasn't the daytime bookings. It was the eleven-at-night ones. People scrolling in bed who remembered they were shaggy and booked a Thursday slot there and then. Those were customers who would never have bothered to message and wait for a reply. His diary started filling from hours he was asleep, and the steady drip of DMs asking "you free Saturday?" mostly dried up. #### The deposit that did the quiet work Online booking filled the chairs. It didn't stop people vanishing. For that, Theo turned on a small deposit. Ten dollars, taken when someone books, and it comes straight off the price of the cut when they sit down. Nobody pays a cent more. They just pay a little of it early. The effect was almost funny in how quick it was. A booking someone has put ten dollars behind is a booking they remember. If life gets in the way they message ahead and move it, because now there's something at stake. The no-shows didn't taper off politely over a few months. They mostly stopped. > I thought asking for a deposit would scare people off. It did the opposite. The ones who book now actually turn up, and I stopped holding chairs for nobody. Here's how Theo describes the difference the deposit made to his week: - He stopped turning away walk-ins to protect slots that were never really solid. - The Saturday sheet became a Saturday he could trust, not a Saturday he had to hope about. - When someone genuinely couldn't make it, they told him early, so he could offer that time to somebody else. - The awkward chasing texts, the "hey, you still coming?" ones, quietly disappeared from his day. #### Friday nights at the Coastal Market Once the everyday bookings were sorted, Theo tried something he'd wanted to do for ages. On summer Fridays he sets up a chair at the local coastal night market and runs a fixed-time cutting session out in the open air. It has a set date and start time, a cap of twelve spots, an address with directions so people can find his little corner among the food trucks, and one price per person that they pay when they book. Because it's outdoors, the booking card shows a live weather forecast for that evening, so a dad booking his kid a fresh fade can see whether Friday looks clear. And if the wind comes in off the sea and Theo has to call it off, he cancels the session and everyone who booked is credited back and emailed automatically. He doesn't spend his Friday afternoon working through a list of refunds by hand. The system does it, and the customers hear about it before they've left the house. Those market nights have become their own little thing. Half the people who come to them had never set foot in Copperline before. A good few now book their regular cuts with him too. #### The regulars who bring the regulars The last piece was almost an afterthought, and it's turned into some of his best new custom. Every regular has a referral link Theo can send them. They pass it to a mate. The mate books their first cut through it, and Theo says thank you with a bit off both of their next visits. It costs him a little, and it brings him people who already trust the person who sent them. A barber shop lives on word of mouth anyway. This just gives the word of mouth something to click. #### Start with one chair Theo didn't change everything at once. He put his appointments online first and lived with that for a fortnight. Then he switched on the deposit when he saw how much time he was still losing to no-shows. The market nights and the referral links came later, once the basics were humming. If your Saturday looks anything like his old one, pick the single thing that annoys you most this week. For a lot of barbers that's the empty chair someone reserved and never sat in. Turn on a small deposit for that and watch one weekend. See whether the ghosts stop coming. You can always add the rest when you're ready. ### How a Wednesday night run club counts itself now Reuben runs a Wednesday night club from the boat shed by the lake. Here is how putting each week's run on his page as a capped, bookable group session, with a live forecast on the card and payment taken up front, quietly handed the admin back to the runners. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/running-club-coached-runs-booking · markdown: https://bookatu.com/blog/running-club-coached-runs-booking.md > **The short version** > > - Set your weekly coached run as a fixed night and time with a cap on the places, and let people book and pay for a run online. > - Each run shows the date, the time, how many places are left, and a live weather forecast for that evening. > - The meeting point carries its own address and a directions link, so a first-timer can find you without a single text. > - If you call a run off in bad weather, everyone who booked is credited back automatically and emailed. Reuben has run the same Wednesday night club for four years. Two dozen runners meet at the old boat shed by the lake and split into a quicker bunch and a steadier one, then loop the waterfront while the sun drops behind the hills. He coaches from the front of one group and the back of the other, calling out form cues and bad jokes in roughly equal measure. It is the best part of his week. Working out who was actually coming used to be the worst. #### The old Wednesday Here is how a run got booked before. Someone would message him on Monday to ask if there was space this week. He would thumb back through a tangle of texts and group chats to tally who had already said yes. Somewhere in the teens he would lose count and take a guess. Regulars paid him ten dollars a run, mostly in cash, so his jacket pocket rattled with coins and he could never quite remember who was square and who owed him for a fortnight. Then every Wednesday around five, like clockwork, the messages started. Still on tonight? Looks a bit wild out there. He would squint at the sky and make the call, then reply to each person one at a time while trying to get his own gear on. It all held together, just about. It also swallowed his Monday evening and half his Wednesday, and none of that was coaching. #### One run on a set night, with a cap on the places Now the Wednesday run sits on his booking page as a group session. It has a night and a time, half past six, with a cap of twenty-four places. When eighteen people have booked, the page shows six places left. When the last one goes, it says full, and there is no way to wedge in a twenty-fifth. Reuben does not tally anything anymore. He opens the page and there is the list, already counted for him. Because it is a standing weekly thing, he set it to repeat. Next Wednesday's run is already there to book, and the one after that, so his regulars can lock in a few weeks at a time. A couple of them now book a whole month in one go, which means Reuben can watch his Wednesdays fill in before the current week is even done. He sets the price per run too. A normal week is ten dollars a head. On the last Wednesday of the month he does a longer river route with a coffee stop at the end, and he prices that one a little higher, so the page shows the right number against the right night. Everyone pays when they book a run, so the cash and the rattling pocket are gone. He turns up, and the money side is already handled. #### The meeting point, not his front door The club does not start at Reuben's place. It starts at the boat shed, which has its own address on the far side of the lake and a car park that is not obvious if you have never been. So every run carries that address and a directions link. A nervous first-timer who found the club through a friend can tap it and drive straight to the right spot, instead of messaging him at quarter past six to ask where everyone is. He was surprised how much that one small thing helped. The lost-in-the-car-park texts simply stopped. > The best change is a thing that no longer happens. Nobody messages to ask if it is on, because the page told them before they could reach for their phone. #### The little forecast that answers the wild-sky question Running is an outdoor business, and the weather has a vote. This is where a feature he assumed was decoration earned its keep. Every run on his page shows a live forecast for that evening, right there on the card, with a small animation. Clear skies when the week looks kind, cloud or rain when it does not. So when someone is deciding whether to book Wednesday, they can see Wednesday looks fine and book with a bit of confidence. The five o'clock still on? message more or less dried up, because the card had already answered it. It does something quieter too. A lot of the people who used to drop off were not really dropping off. They woke to a grey morning and decided the evening would surely be a washout, so they talked themselves back onto the sofa. With the forecast sitting on the card at the moment they book, saying clear and mild, they commit properly and they turn up. #### When it actually pours Some Wednesdays the sky wins. When the path is a river and the wind is coming in sideways, Reuben calls the run off from his phone in one tap. Everyone who booked is credited back automatically and sent an email to say so. He is not standing in his kitchen refunding twenty people one at a time, and nobody is left wondering whether they will see their ten dollars again. He adds a line to say see you next week, and that is the whole job done. #### The runner who wants a bit more Not everyone wants the group. Every so often a runner asks Reuben for a proper one-to-one, someone training for a first half marathon who wants their stride looked at, or a returning runner easing back after a niggle. Those are not group sessions. They book as a normal appointment, a single slot in his diary at a time that suits them both, at a one-to-one price. Same booking page, different shape. The club night fills its capped places, and the private sessions tuck into the quieter times around it. #### How the club actually grows A run club grows by someone bringing a mate. It always has. So Reuben sends his regulars a referral link they can pass to a friend, and when that friend signs up and books their first run, both of them get a small reward for it. It is the thing that was already happening, a runner talking the club up over a Saturday coffee, except now it counts for something on both sides. His Wednesday numbers have crept up without him printing a single flyer. If you run anything on a set evening, a club run, a track session, a weekend long run, a couch-to-5k, it can work like this. Pick the night, cap the places, put a price on a run, and let people book and pay themselves in. Then you get to do the part you actually laced up for, which is run at the front and shout the encouragement, with a group behind you who all knew exactly where to be. ### How to fill every bike in your spin studio without chasing texts A whiteboard and a phone full of maybes is no way to run a room of fourteen bikes. Here's how one Wellington studio put its class timetable online and filled the room before opening. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/spin-studio-indoor-cycling-booking · markdown: https://bookatu.com/blog/spin-studio-indoor-cycling-booking.md > **The short version** > > - Put your class timetable online so riders can grab a bike and pay in one go, day or night > - Every class has a set number of bikes, so it fills up and closes on its own instead of you refereeing a waitlist by text > - Private one-on-one sessions still book like a normal appointment, kept separate from the group ride > - Regulars can share a link that rewards them when they bring a friend, which is how spin studios actually grow Maya runs a small spin studio above a bakery on a side street in Wellington. Fourteen bikes, one very good sound system, and a whiteboard by the door that, for about two years, was how she ran her whole timetable. People texted her to book the 6am ride. Some turned up who hadn't texted at all. A few texted and never came. On a good Monday she had a full room and a playlist she was proud of. On a bad one she had four riders in a space built for fourteen and a phone full of maybes. The bikes were never the problem. The booking was. A fixed-capacity class is a strange little business puzzle. You have exactly this many spots, they only exist at exactly this time, and the moment the class starts an empty bike is gone for good. You can't sell it tomorrow like a bag of coffee beans. That was the money leaking out of Maya's week, quietly, in a way she couldn't quite point at. #### Why a spin class isn't like a normal booking Most booking tools imagine one person and one slot. You pick a time and you show up. That's fine for a haircut or a massage. A spin class works differently. It's a single time slot shared by a whole room, with everyone paying their own way in and watching the same number tick down toward full. So what your booking page really has to do is show a class the way a rider pictures it. Not just when it is and what it costs, but the one number that actually drives the decision: how many bikes are still free. When there are three spots left on the Thursday 6pm, the person staring at their phone on the bus home feels that little now-or-never nudge. That nudge is what fills your room. #### Getting the timetable onto the screen people already hold Maya put her week of classes onto a Bookatu page and sent the link to her regulars on a Sunday night. By Monday morning she'd taken eleven bookings for the week while she was asleep. Nobody had to text her. Nobody had to remember to bring cash. They saw the ride they wanted, tapped it, paid, and got a confirmation, all before she'd had her first coffee. Each class on the page carries what a rider needs to decide in about four seconds: - The day and start time, so there's no back-and-forth about when it actually is - The price for that one class, paid online at the moment they book - How many bikes are left, counting down as the room fills - The studio address and directions, for the friend coming along for the first time #### When you have to call a class off Indoor studios don't sweat the weather, but life still gets in the way. An instructor wakes up with a cold. The power goes out mid-afternoon. When that happens, Maya opens the class, cancels it, and that's the whole job. Every rider who booked gets their money back as a credit and an email explaining what's happened, all in one go. No list of names to work through by hand, no awkward refunds one at a time while people quietly wonder if they've been forgotten. > The first time I cancelled a class and watched it just handle everyone for me, I actually sat down. That used to be an hour of texting and apologising. #### The private sessions sit on their own track Not everything at Maya's studio is a group ride. Some people want a one-on-one to sort out their setup, or a nervous first-timer wants the room to themselves before they'll try a full class. Those book like a normal appointment. The rider picks a time that suits them both, and it lands on Maya's calendar without touching the group timetable at all. Two kinds of booking on one page, kept from tripping over each other. #### The quietest way a spin studio grows Here's the part Maya wishes she'd understood sooner. Spin studios don't really grow on ads. They grow on the friend who says come to the 6pm, it's brilliant. So every regular can be handed their own link to pass on, and when a friend books their first class through it, the studio says thank you in a way that's worth something, like a free ride or money off the next month. It turns the thing your best riders already do for nothing into something they get a small reward for. Maya's Tuesday crowd roughly doubled over a season on the back of it, with no marketing budget in sight. If you're running your timetable off a whiteboard and a phone full of texts, you already know which mornings hurt. Start with one week. Put your real classes up, send the link to the people who already love the place, and count how many bikes are booked before you've even unlocked the door. That's usually the moment it clicks. ### How a Piha surf school stopped dreading the Friday-night phone Ana teaches beginners to surf at Piha, where the wind decides everything. Here is how running lessons as bookable group sessions, each with a live forecast on the card, gave her back her Friday nights and her rain-day sanity. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/surf-school-lesson-booking · markdown: https://bookatu.com/blog/surf-school-lesson-booking.md Ana Ferreira has taught beginners to surf at Piha for eleven years. Ask her about the hard part and she will not mention the waves. She will mention her phone. Every Friday night it used to fill up with the same two questions. Is the lesson still on? And can my sister come too? By the time she had answered them all, half her evening was gone and she still had not looked at the forecast properly. > **The short version** > > - Put your beginner group lessons online as fixed times with a set number of spots, and let people book and pay their own way in. > - Each lesson card can show where to meet and a live weather forecast for that spot, so nobody turns up to a howling onshore wind. > - If the surf is unsafe, you cancel the lesson once and everyone is credited back and emailed straight away. > - Keep private one-on-one lessons as normal bookings, and hand your happy regulars a referral link they actually want to share. #### The weather runs the business, not the calendar A surf school lives and dies by the wind. Ana can plan a perfect Saturday, eight people signed up for the ten o'clock beginner lesson, and then wake to an onshore mess that turns the bay into washing-machine chop. On land, that is a phone problem. On the water with first-timers, it is a safety one. So her whole week bends around a forecast she cannot control, and for years her booking setup pretended the weather did not exist. That is the thing most booking tools get wrong for outdoor work. They treat a surf lesson like a haircut, a slot on a grid that either happens or does not. A lesson at the beach is really a small event. It has a time, a headcount, a meeting point in a car park, and a sky that might ruin all of it. #### Lessons that fill themselves up The change that gave Ana her Friday nights back was simple. She stopped treating each beginner lesson as a private appointment and started running it as a group session. One fixed time, eight spots at a set price per person. People find it, book a place and pay on the spot. The count ticks down as they go. When it hits zero, the lesson is full, and Ana never had to type a word. Now her Saturday ten o'clock is a page, not a text thread. Someone books three places for a hen weekend at eleven at night. The spots update. The two remaining places show as two remaining places. Nobody double-books, and nobody has to message her to ask whether there is room. Each session card carries everything a nervous first-timer wants to know before they commit: - The date and start time, and how many spots are left out of the total. - The beach and the exact meeting point, with directions so nobody is circling the car park. - The price per person, paid at the time of booking. - A live weather forecast for that spot, right there on the card, so the conditions are part of the decision. #### The rain call, made once Then there is the morning it is just not safe. Big clean swell for the experienced crew, far too much for eight beginners who have never duck-dived in their lives. Ana used to dread that call, because it meant a string of apologies and a pile of refunds to sort out by hand, plus the nagging worry she had forgotten someone. Now she cancels the lesson once. Everyone booked into it is credited back automatically and gets an email telling them what happened, all in the time it takes her to pour a coffee. The people who signed up are looked after before they have even noticed the wind. She can spend that saved half hour messaging them about the next dry window instead. > I used to lie awake on stormy Friday nights doing refund maths in my head. Now the rain call takes one tap and I go back to sleep. #### The private lesson still has its place Not everyone wants a group. Some people want a quiet hour with just Ana. That might be a kid who needs a gentler pace, or a returning surfer knocking the rust off after years away. Those stay as ordinary one-on-one bookings, a normal appointment on her calendar at a time that suits them both. The group sessions handle the crowd and the buzz. The private lessons look after the people who would rather not have an audience while they fall off a foamie. #### Let the stoke do your marketing The best advertising Ana ever had was a woman who caught her first green wave on a Sunday and would not stop talking about it. That kind of stoke spreads on its own, and it helps to give it somewhere to go. After a lesson, Ana sends people a referral link of their own. When a friend books through it, the friend gets a warm welcome and the person who sent them gets a little thank you toward their next session. It costs her almost nothing, and it turns one good morning into three. #### If you run lessons at the mercy of the sky You do not need a bigger team to stop drowning in Friday-night messages. You need each lesson to carry its own details and take its own bookings, weather included. Bookatu does not take a cut of what you earn, which matters when your season is short and the good-weather windows are shorter. If you teach anything outdoors, a surf lesson or a beginner clinic on the sand, try putting one session online this week and see how the next storm feels. Quieter, most likely. Start with Saturday. ### How a Tuesday night tennis clinic runs itself now Meet Will, who runs a beginners tennis clinic every Tuesday at his local club. Here is how running it as a fixed-time group session, with a live weather forecast on the card and payment taken online, quietly fixed the whole thing. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/tennis-clinic-group-sessions-book-and-pay-online · markdown: https://bookatu.com/blog/tennis-clinic-group-sessions-book-and-pay-online.md > **The short version** > > - Set a class for a fixed day and time, with a limit on spots, and let people book and pay online. > - Each session shows the date, the time, how many spots are left, and a live weather forecast for that day. > - The venue can be anywhere, with its own address and a directions link, so it does not have to be your own place. > - If you cancel a rained-off session, everyone who booked is credited back automatically and emailed. Will has coached beginners tennis for about six years. Every Tuesday at six he runs a clinic for adults at his local club, the kind of session where people who have not held a racquet since school come to give it a proper go. Six players, two courts, an hour of drills and a good laugh. It is the best night of his week. The booking side of it used to be the worst. #### The old Tuesday Here is how it worked before. Someone would text him on Sunday to ask if there was room. He would scroll back through the thread trying to count who had already said yes. Somewhere around the fourth name he would lose it and just guess. He kept a running list on a folded bit of paper in his kit bag, and half the players paid in cash, so he was forever carrying twenty-dollar notes and trying to remember who still owed him. Then, every single week without fail, two or three people would text at half past five: is it still on tonight? The sky looks a bit grey. He would look out the window, make a call, and message everyone back one at a time. If he had to cancel, the players who had already paid ahead needed sorting out later. It all worked, sort of. It just ate his Sunday evening and a decent chunk of his Tuesday, and none of it was the coaching he actually loved. #### One clinic, set for six, six spots Now the Tuesday clinic lives on his booking page as a group session. It has a date and a time, six o'clock, and a limit of six spots. When five people have booked, the page shows one spot left. When the sixth books, it shows full, and there is no way to squeeze in a seventh. Will does not count anything anymore. He opens the page and sees exactly who is coming. Because it is a standing Tuesday thing, he set it to repeat. Next Tuesday's clinic is already sitting there ready to book, and the one after that, so his regulars can grab a spot a few weeks ahead. A couple of his keenest players now book a month at a time, which means Will can watch his Tuesdays filling up before the week has even started. He sets the price per session too. A normal week is twenty dollars a head. When he brings in a second coach for a bigger group or a match-play night, he sets that session to twenty-five, and the page shows the right price for the right night. Everyone pays online when they book, so the cash and the folded list are gone for good. He turns up on Tuesday and the money is already sorted. #### The venue is the club, not his lounge The clinic does not run at Will's house. It runs at the club, which has its own address a couple of suburbs away. So the session carries the club's address and a directions link, and a first-timer who has never been there can tap it and drive straight to the right car park. Will was surprised how much that one small thing helped. People simply stopped texting him to ask where it was. > The best part is a thing that no longer happens. Nobody texts to ask if it is on, because the page has already told them. #### The little weather forecast that answers the grey-sky question Tennis is an outdoor sport, and Auckland weather has opinions. This is where a small feature turned out to matter more than Will expected. Each session card on his booking page shows a live weather forecast for that date and time, with a little animation. A bit of sun when the week looks clear, cloud or rain when it does not. So when someone is deciding whether to book Tuesday, they can see that Tuesday looks fine, and they book with confidence. The half-past-five is it still on text more or less stopped, because the page had already answered it. #### When it actually rains Auckland being Auckland, some Tuesdays are a write-off. When the courts are underwater, Will cancels the session from his phone in one go. Everyone who booked gets their money credited back automatically, along with an email letting them know. He is not sitting there refunding six people one by one, and nobody is left wondering whether they will get their twenty dollars back. He can add a quick note to say see you next week, then put the kettle on. If you run anything on a set night, a beginners clinic, a squad night, a weekly kick-around, a bootcamp in the park, it can work the same way. Set the day, set the time, set how many people fit, put a price on it, and let people book and pay themselves in. You just show up and coach, which was always the part you wanted to do anyway. ### Mini-session days that fill up before dinner Priya sells out a full Saturday of fifteen-minute autumn mini-sessions at the botanic gardens. Here is how laying the day out as bookable sessions, with one location and a live forecast on every slot, took the DM avalanche out of it entirely. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/photography-mini-session-days-book-online · markdown: https://bookatu.com/blog/photography-mini-session-days-book-online.md > **The short version** > > - Lay a whole day out as a row of fixed sessions, each its own short slot at its own time. > - Set how many bookings each slot holds, so once it is taken it drops off the page on its own. > - Every session sits at one venue with an address and a directions link, so nobody messages you asking where to go. > - People pick a slot and pay when they book, and a rained-off day can be cancelled with everyone credited back automatically. Every autumn, Priya photographs families under the big liquidambar trees at the botanic gardens, when the leaves go copper and the whole place looks like a postcard. She calls them her mini-sessions. Fifteen minutes each, one family at a time, enough for a handful of lovely frames and a Christmas-card photo. She runs a full Saturday of them, back to back, from mid-morning until the light goes soft. They are wildly popular. Booking them used to eat her alive. #### The Saturday the DMs took over She would post one photo on Instagram with a caption: autumn minis this Saturday, comment or DM to grab a time. Within an hour her inbox was chaos. Forty messages, all some version of what times have you got left. She would reply to one person and offer them eleven o'clock, and by the time they came back to confirm an hour later, she had already promised eleven to somebody else. She was keeping the running order in her notes app and getting it wrong. Payment was hit and miss, some on the day and some not at all, and a couple of people ghosted completely, so a slot she could have sold sat empty while a paying family missed out. None of it was the photography. It was admin dressed up as messaging, and it swallowed the whole week before the shoot. #### One day, a row of slots, booked and paid Now she builds the day once. She sets up a row of sessions, each a fixed fifteen-minute slot with its own time, ten o'clock, quarter past, half past, and on down the afternoon. She decides how many bookings each slot holds, which for her is one family, so the moment a slot is taken it drops off the page and the next family books the next opening. No two families ever land on the same time, because the page will not allow it. ![A hand holding a camera up against a bright sky](https://images.unsplash.com/photo-1554048612-b6a482bc67e5?auto=format&fit=crop&w=1200&q=70) *Lay the day out as a row of timed slots, and the whole Saturday can sell itself while you are somewhere else entirely.* Every slot sits at the same place, the gardens, so each session carries the garden's address and a directions link. A family who has never been can tap it and drive straight to the right gate, instead of messaging her the night before to ask exactly where. And they pay when they book, so by Saturday morning the whole day is sold and settled. Priya just turns up with her camera and a flask of coffee. She can price it however she likes. A standard fifteen minutes is one set price. If she adds a couple of longer golden-hour slots at the end of the day, she prices those higher, and the page shows the right number against each one. People see exactly what they are paying before they commit, so there is no awkward money chat at the shoot itself. > The first year she ran it this way, the whole day sold out in an afternoon while she was out walking the dog. She came home to a full calendar and not one DM to answer. #### Leaves are lovely, rain is not Outdoor sessions live and die by the weather, and everyone booking a mini knows it. So each session card shows a live forecast for that Saturday, with a little animation, bright sun or grey rain. When a family is deciding whether to book, they can see the day looks clear and book without the usual will it even be nice enough hesitation. It quietly does the reassuring for her. #### If the weather turns Sometimes autumn does autumn things and Saturday arrives grey and pouring. When that happens, Priya cancels the day from her phone, and every family who booked is credited back automatically and emailed to let them know. She is not up late refunding twelve people by hand. She can put up a fresh set of slots for the following weekend, and the families who missed out come straight back. If you run mini-sessions, or theme days, or seasonal shoots, or any short slot you sell over and over, this takes the messaging out of it completely. Lay the day out once, let people pick a time and pay, and keep your inbox for the fun stuff. Your Saturday sells itself while you get on with your week. ### A class timetable that fills its own spots Mara runs eight classes a week off a clipboard by the door, and it shows. Here is how putting every class on the timetable as a capped, bookable session let her members sort their own spots and filled her Saturday reformer by Thursday. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/class-timetable-group-sessions-book-online · markdown: https://bookatu.com/blog/class-timetable-group-sessions-book-online.md > **The short version** > > - Put every class on the timetable as its own session, pinned to a day and time, with a cap on spots. > - When a class is full, the page says full, so you never oversell a room or turn someone away at the door. > - The timetable repeats each week, and members book and pay for their own spot without messaging you. > - If a class is called off, everyone who booked is credited back automatically and emailed. Mara runs a small studio with eight regular classes a week. Vinyasa on Monday and Wednesday evenings, reformer Pilates on Saturday mornings, a gentle Friday class for her older members, a lunchtime stretch on Tuesdays. Twelve mats fit comfortably on the floor. For years she ran the whole timetable off a clipboard by the door and a lot of hoping. #### The clipboard, and the class with fourteen people in it The trouble with a paper list is that it lives in one place, on the wall of the studio. So people booked however suited them, a text one week and an Instagram message the next, or they simply turned up on the night and hoped. Mara tried to hold spots in her head. Every so often a class she thought had room turned out to be full, and someone who had driven across town on a wet Wednesday had to be turned away at the door, which felt awful. Other nights she squeezed fourteen mats into a room meant for twelve and nobody could stretch out. Payment was its own muddle of half-used class cards and cash in a tin, plus the odd I will get you next week that never quite came. #### Every class on the timetable, capped Now each class is a session on her booking page. Monday vinyasa at six, Saturday reformer at nine, each pinned to a day and time and each capped at twelve. When a class is full, the page says full, and that is the end of it. Nobody can book a thirteenth mat, so Mara never has to have the awkward doorway conversation again. The timetable repeats each week, so next Monday's class and the one after are already there to book. Each class also carries its price. Her drop-in reformer costs more than a mat class, and the page shows the right price against each one. Members pay when they book their spot, so the class cards and the cash tin are a thing of the past. She can glance at her phone before she leaves home and know exactly how many people are coming to the six o'clock. > A full class used to be a happy accident. Now it is just what a filled timetable looks like, and she can see it coming days ahead. #### Members book their own mat The quiet win is that her regulars now sort themselves out. They open the timetable, see Wednesday has three spots left, and grab one. No text to Mara, no waiting on a reply while she is mid-class. When a class fills up, the keen ones simply book further ahead, so her Saturday reformer is often full by Thursday. She spends her evenings teaching a room, not tapping out replies between poses. It changes the feel of the whole week, honestly. Mara used to spend the hour before each class half-distracted, wondering who would actually show and whether she needed to set out more mats or fewer. Now she knows before she arrives, so she lays out exactly the right number and starts on time. The class feels calm from the first breath, because the admin was all done days ago by the people coming. #### For the classes under the sky In summer Mara runs a Sunday morning class in the park, mats out on the grass. Those are the ones where the weather decides everything. Each session card shows a live forecast for that morning, with a little animation, so members booking the park class can see Sunday looks clear and book happily. It answers the thing they would otherwise text her, which is simply whether it is going ahead at all. #### If a class is called off If the park class gets rained out, or Mara comes down with something and has to cancel, she cancels the session and everyone who booked is credited back automatically and emailed. Nobody turns up to a locked door or a soggy field. Nobody has to chase her for a refund on a class that did not happen. It is handled, and she can actually rest. If you teach on a timetable, whether it is yoga, Pilates, spin, or a weekly bootcamp, your classes can work like this. Set each one up once, cap it at the number that fits, and let your members book and pay for their own spot. You get to do the part you trained for, which is teach a room full of people who all knew to come. ### Why there's a tiny weather forecast on your booking page There is a small animated weather forecast on the booking page for outdoor sessions, and it is not only there to look cute. It answers the question everyone asks before booking, and when a session is rained off, everyone gets credited back automatically. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/weather-forecast-on-your-booking-page · markdown: https://bookatu.com/blog/weather-forecast-on-your-booking-page.md > **The short version** > > - That little animated sun or raincloud on a session card is a live weather forecast for that exact session. > - It answers the question every outdoor class gets an hour before: is this still on? > - Seeing a clear forecast at booking time helps people commit, which quietly cuts the weather no-shows. > - If a session really is rained off, the owner cancels it and everyone is credited back automatically. Book a spot in an outdoor class on Bookatu and you might notice a small thing on the session card. A little sun, or a few animated raindrops, sitting next to the date. It is a live weather forecast for that exact session, and it is one of those features that sounds like decoration until you actually run outdoor classes. Then it turns out to be the whole game. #### It answers the question everyone was going to ask anyway Every coach and instructor who runs anything outside knows the message by heart. It lands an hour before the session, from someone already half into their gym gear: is this still on? The sky looks a bit iffy. On its own it is a perfectly fair question. Multiplied by six or eight people every single week, it becomes a part-time job you never applied for. The weather card answers it before anyone has to send it. Someone looking at Tuesday's clinic can see that Tuesday looks clear and just book, no message needed. It is a small shift with a real effect. The people who would have messaged now just glance and decide. You stop being the weather line for your own class, fielding forecasts between sessions when you are trying to actually run one. And the customer gets their answer instantly, at the exact moment they were wondering, rather than waiting on you to look out a window and reply. #### It quietly cuts the no-shows There is a sneakier benefit hiding in there. A lot of no-shows are not really no-shows. They are people who talked themselves out of it. They booked a park yoga class on Monday, woke on Sunday to a grey sky, decided it would surely be a washout, and stayed in bed. The class went ahead beautifully without them. When the forecast is right there on the card at the moment of booking, and it says clear and mild, people commit properly. They can see the morning is going to be lovely, so they show up expecting lovely. Confidence at booking turns into bums on mats later. > A forecast on the card is a small thing doing a big job. It turns 'I'm not sure it's worth leaving the house' into 'see you there.' #### And when it really does rain, you are covered Some days the forecast is honest and it is going to be miserable, and no cheerful animation is going to change that. That is fine too. If a session is genuinely rained off, the owner cancels it in a tap, and everyone who booked is credited back automatically and sent an email to say so. There is no refund admin to grind through and nobody left out of pocket for a class that never ran. The grace is built in. You cancel, everybody is made whole, and you all go again next week. #### Yes, we made the little cloud move We could have put a plain word on the card. Sunny. Cloudy. Instead there is a small animation: a sun that gives off a gentle glow, or raindrops that actually fall when rain is on the way. It is a tiny thing and it took more care than you would think, and we are glad we bothered. A booking page is often the first proper impression someone gets of your business, and a moment of charm on it does you a quiet favour. It says a real person set this up and they sweat the details, which is a lovely thing for a new customer to be thinking about you. The forecast also refreshes as the session gets closer, so what people see a week out only gets sharper the nearer the day comes. #### It shows up wherever the sky matters The card appears on the sessions where weather actually decides things. An outdoor tennis clinic, a beach bootcamp, a mini-session shoot in the gardens, a Sunday yoga class on the grass. If you run everything under a roof, you will not miss it. If you run things under the sky, it might become your favourite little detail. It is genuinely nice to look at, which we make no apology for, because software that runs your business does not have to be joyless. So no, the tiny animated sun is not only there for show, although it is a little bit for show, and we are quite okay with that. It answers the question your customers were about to ask, and when the weather does win in the end, it makes the cleanup painless. Set up an outdoor session and go and have a look at it. Then keep an eye on the sky, the way you always have, only with far less texting. ### Why your booking page is your colour, and your dashboard is ours When you set your brand colour in Bookatu, it paints your booking page, your emails and everything your clients touch. It does not paint the dashboard you work in. That is a deliberate choice, and it is the same one every tool you trust makes. Here is the thinking. The Bookatu team · 2026-07-03 · Grow your business · https://bookatu.com/en-nz/blog/your-brand-belongs-to-your-clients · markdown: https://bookatu.com/blog/your-brand-belongs-to-your-clients.md > **The short version** > > - Your brand colour leads everywhere your clients look: your booking page, your confirmations, your storefront. > - The admin dashboard you work in stays on one calm, consistent palette instead. > - That keeps the tool quick to read and quick to learn, so nothing gets in the way of running your day. > - Your brand is doing its job where it counts: winning the booking. Pick a colour for your business in Bookatu and you will see it right away where it matters. Your booking page wears it. Your confirmation emails wear it. The buttons a client taps to book, pay a deposit or buy a gift card all carry your colour, so the whole experience feels like you, not like a piece of software you happen to use. That is exactly how it should be. When someone books with you, they should feel like they are dealing with you. What your colour does not paint is the dashboard you sit in to run the business. That screen stays on one steady palette, the same for every business on Bookatu. Some owners ask why, and it is a fair question, so here is the honest answer. #### The tool should get out of the way Think about the software you rely on to run your own life: your banking app, your email, your calendar. None of them let you repaint the whole interface, and you would not want them to. A tool you use every day earns its keep by being fast to read and impossible to get lost in. Every button in the same place, every colour meaning the same thing, every time. That reliability is a feature. It is what lets you work without thinking about the working. A dashboard that changed its entire colour scheme per business would trade that reliability for decoration. Green means "go" and "done" in one place; if the whole screen were tinted green because that was the business colour, that meaning gets muddy. Consistency in the tool is not us being unbrandable. It is us keeping the tool quick. Diagram labels: Storefront · Admin · or · marketing · Visitor · Which surface? · sf-scope: tenant colour + own theme toggle · Platform palette: Bookatu indigo, light or dark · Clients see the brand · Owners see the product *Two surfaces, two jobs. Your clients see your brand; you see a steady, quick-to-read tool.* #### Your brand is working where it wins you money Here is the part that reframes it. Your brand colour is not decoration either. On your booking page it is doing real work: it makes a stranger who found you on Instagram trust that they are in the right place, that this is a real business, that booking is safe. That is where your brand earns its money, in the seconds before someone commits to an appointment. Spending it there, at full strength, beats spreading it thin across a back office only you ever see. So we made a clean split. Everything a client touches is yours, down to the colour of the confirm button. Everything you touch to run the day is a calm, consistent workspace that stays out of your way. You get a brand that sings where it counts and a tool that is quiet where it should be. > Your colour belongs on the page your clients see, not the screen only you do. If you have not set your brand colour yet, it takes a moment, and you will see it flow straight through to your booking page and your emails. That is the surface worth making beautiful. The dashboard will keep quietly doing its job while you do yours. ### How to put your services on sale without discounting everything You do not have to edit every price by hand to run a promotion. Put a whole category on sale in one place, let the discount come off automatically at checkout, and switch it back off when the week is over. The Bookatu team · 2026-07-01 · Grow your business · https://bookatu.com/en-nz/blog/put-your-services-on-sale · markdown: https://bookatu.com/blog/put-your-services-on-sale.md > **The short version** > > - Put a whole category on sale, like every facial at 20 percent off, from one place. You do not touch each service. > - The lower price shows on your booking page and comes off automatically when a client checks out. > - You can also charge more for a senior staff member and less for a junior, so clients pick the person and see the right price. > - Turn a sale off and prices go straight back to normal. There is nothing to undo by hand. A good promotion should be quick to set up and quick to end. The problem with most booking tools is that a sale means opening every service, editing the price, and then remembering to put it all back next week. By the third service you have already made a typo. So people avoid running offers at all, which is a shame, because a well-timed one fills a quiet week. #### Put a category on sale in one place Your services are already grouped into categories, things like Facials, Colour, or Manicures. A category sale lets you set one number against the whole group. Type 20 next to Facials and every facial you offer is 20 percent off. New facials you add later are included automatically, so you are not chasing a list. The client sees the sale price on your booking page, and the discount comes off when they pay, without a code to remember. ![A bright, modern salon studio](https://images.unsplash.com/photo-1633681926022-84c23e8cb2d6?auto=format&fit=crop&w=1200&q=70) *One number against a category is enough. Every service in it goes on sale, and new ones join it on their own.* #### Let clients book the right person at the right price Not every chair costs the same to run. A senior stylist with a waitlist is worth more than a junior building a book, and clients understand that. You can set a price level for each team member, so the same service quietly costs a little more with your senior and a little less with your junior. When a client picks who they want, they see that person's price before they book. It rewards your best people and gives price-sensitive clients an honest way in. #### When a sale actually earns its keep A discount is not free money, so point it where it does work you could not get otherwise. A few that tend to pay off: - Fill a slow day. Put one category on sale for the middle of the week and leave your busy Saturday at full price. - Launch something new. A short intro price on a new treatment gets the first bookings and the first reviews. - Move end-of-season stock or a service you want to retire, so the calendar clears without a fire sale on everything. - Reward the quiet months. A gentle sale in your off-season keeps regulars coming in when they might otherwise skip. #### Turning it off is the easy part Set the sale back to zero and every price in that category returns to normal on the next booking. You are not unwinding a batch of edits or hoping you remembered them all. That is the whole point of setting it in one place. Run the offer for exactly as long as you meant to, then end it, and get on with your week. ### How we ship features that touch money without changing anyone's price by accident A pricing bug is the kind you cannot take back once a card is charged. Here is the discipline we use to add discounts, staff pricing and sales to the booking flow without a single price moving until we mean it to. The Bookatu engineering team · 2026-07-01 · Engineering · https://bookatu.com/en-nz/blog/shipping-money-features-safely · markdown: https://bookatu.com/blog/shipping-money-features-safely.md > **The short version** > > - Anything that can move a price ships behind a flag that is off by default. The code is in production but does nothing until we turn it on. > - The final price is worked out again on the server at checkout. A number that arrived from the browser is never trusted. > - The discount maths lives in one small pure function with its own tests, so it can be reasoned about on its own. > - Before a pricing feature goes live, a set of adversarial checks tries to make it overcharge, undercharge, or go below zero. Most bugs cost you an apology. A pricing bug costs you a refund, a chargeback, and a client who no longer trusts the number on the screen. The stakes are lopsided, so the process around anything that touches money is deliberately slower than the rest of our work. This is the shape of it, using a recent feature as the example: a whole-category sale, where a salon can put every facial on sale at once. *Diagram: The price pipeline: base price, then staff price, then category sale, then the best coupon, then the amount charged* Diagram labels: REBUILT ON THE SERVER, EVERY BOOKING · Base price · Staff price · Category sale · Best coupon · Charged *Every booking's price is built in the same fixed order, and the whole sum is redone on the server.* #### Off by default, in production, doing nothing The first line of the feature is a flag. It reads an environment variable and defaults to off. That means we can merge and deploy the code long before it does anything, and every price stays byte-for-byte identical to the day before. There is no big-bang launch to be nervous about, because the launch is a separate, boring step we take once we are confident. ```ts export const FEATURE_LIVE = process.env.FEATURE_LIVE === "true"; // Read at the one place it matters. When the flag is off, the branch // is skipped entirely: no extra query, no price change, nothing. if (FEATURE_LIVE) { const pct = await activeCategorySalePercent(orgId, "service", service.category); if (pct > 0) fullPriceCents = applyCategorySaleCents(fullPriceCents, pct); } ``` *Diagram: The flag lifecycle: written behind a flag that is off by default, merged and deployed while still off, then after the audit passes the flag is flipped and the feature goes live* Diagram labels: 1 · Behind a flag · off by default · 2 · Merge & deploy · still off · 3 · Audit passes · 0 money bugs · 4 · Flip the flag · the go-live · Live *The launch is a separate, boring step. The code ships long before it does anything.* #### One function, one job The arithmetic of the discount lives in a single pure function. It takes cents and a percent, and it returns cents. It has no database, no request, and no clock, which means it is trivial to test every edge of it in isolation: a zero sale, a normal sale, a clamp at the top, a negative that should never happen. When the maths is one small function you can hold in your head, you stop guessing about it. ```ts export function applyCategorySaleCents( baseCents: number, salePercent: number | null | undefined, ): number { const base = cents(baseCents); const pct = Math.max(0, Math.min(100, Math.round(salePercent ?? 0))); if (pct === 0) return base; return cents((base * (100 - pct)) / 100); } ``` #### Recompute on the server, always The browser shows a price so the client knows what they will pay, but that number is only ever a display. When a booking comes in, the server loads the real service, resolves the staff price, applies any live category sale, and then works out the discount, all from data it fetched itself. If someone edited the request on the way in, it changes nothing, because the price the card is charged was never the price the browser sent. This is the single most important habit in money code: the trust boundary is the server, and the server does the sum. *Diagram: The browser only displays a price; the server independently loads the service, resolves the staff and sale price, applies the best coupon, and charges that amount* Diagram labels: BROWSER · Shows a price so the client · knows what they will pay. · A display only. Never trusted. · request · SERVER · SOURCE OF TRUTH · 1 · Load the real service · 2 · Resolve staff + sale price · 3 · Apply the best coupon · 4 · Charge exactly that *The number the browser shows is only a display. The server fetches its own data and does the sum again.* #### Try to break it before a customer does Passing tests tell you the cases you thought of work. They do not tell you about the case you missed. So before a pricing flag goes on, we run an adversarial pass whose only job is to find a way to make the money wrong. Separate checks each take a different angle: one hunts for any path that overcharges the client, one hunts for a path that loses the business money, one checks the feature is genuinely inert when the flag is off, and one goes after rounding and boundary drift. A sale stacked on a coupon on a deposit is exactly where a fractional cent hides, so that is where we look hardest. *Diagram: One new pricing feature is checked by four adversarial skeptics (does it overcharge, lose money, leak when the flag is off, or drift on rounding), and only a clean sweep is a go* Diagram labels: New pricing feature · Overcharges? · Loses money? · Leaks when off? · Rounding drift? · Clean sweep → GO *Four skeptics, each a different way to be wrong. Only a clean sweep is a GO.* None of this is clever. It is a flag, a small function, a server that does its own maths, and a habit of trying to break your own work before it ships. Put together, it is the difference between adding a feature that touches money and losing sleep over it. ### How much photo storage do you actually need? The honest answer is that it depends on what you shoot, not on a number on a pricing page. Here is a plain guide to what fills up a gallery, what your clients downloading never costs you, and how to size your plan without overpaying. The Bookatu team · 2026-06-30 · updated 2026-11-15 · Grow your business · https://bookatu.com/en-nz/blog/how-much-photo-storage-do-you-need · markdown: https://bookatu.com/blog/how-much-photo-storage-do-you-need.md > **The short version** > > - What fills a gallery is your full-resolution files, not the small previews clients browse. > - A portrait session is light. A wedding shot in RAW and delivered as JPEGs is heavy, often tens of gigabytes. > - Your clients downloading their photos never costs you extra, so you only pay for what you store, not for how often it is viewed. > - Plans include 5, 50, 250 and 1000 GB, and you can add 25 GB packs for a few dollars a month when a big job lands. > - Delivering and then archiving finished galleries keeps you on a smaller plan for longer. Storage is one of those numbers that looks scary on a pricing page and turns out to be simple once you know what it measures. It does not measure how many clients you have or how many galleries you send. It measures the size of the files you are keeping online right now. So the real question is not how big is the number, it is what am I actually storing. #### What actually takes up space There are two kinds of file in a client gallery, and they are wildly different sizes. The previews your clients scroll through are deliberately small, a watermarked version at screen resolution, so a whole gallery of them is light. The weight is in the originals: the full-resolution JPEGs you deliver, and the RAW files if you keep those online too. A single RAW frame can be 30 to 60 megabytes on its own. Multiply that by a full shoot and you see where the gigabytes go. ![A photographer's camera held up against a bright sky](https://images.unsplash.com/photo-1554048612-b6a482bc67e5?auto=format&fit=crop&w=1200&q=70) *The previews clients browse are tiny. The full-resolution files behind them are what fill a gallery.* #### A rough guide by shoot Every photographer's files are a little different, so treat these as ballpark figures rather than promises. They are meant to help you picture it, not to bill you. - A short portrait or family session, delivered as edited JPEGs: usually well under a gigabyte. - A longer session or a small event: a couple of gigabytes is common. - A wedding delivered as full-resolution JPEGs: often 10 to 30 GB. - The same wedding if you also keep the RAW files online: it can climb past 40 GB on its own. #### Downloads are free, which changes the maths A lot of older galleries charge you, or throttle you, based on how much your clients download. Ours does not. The storage runs on infrastructure with no egress fee, which is the technical way of saying that a client downloading their full gallery five times costs the same as never opening it. You pay for the space the files take up, full stop. That is why we can say unlimited downloads and mean it, and it is why you can size your plan around what you store rather than around how popular a gallery gets. #### What each plan includes Client galleries are included on every plan for photographers, and on Pro and Scale for everyone else. The storage that comes with each plan steps up as you grow: 5 GB on the entry plan, 50 GB on Studio, 250 GB on Pro, and a full terabyte on the top plan. When a single big job would push you over, you do not have to jump a whole tier. You can add a 25 GB pack for a few dollars a month, stack as many as you need, and drop them again later. #### Keeping it tidy The cap is about what is live, not about everything you have ever shot. A healthy rhythm is to deliver a gallery, give the client a generous window to download, and then archive or remove the finished one to your own backup. Your originals belong in your own long-term storage anyway. The online gallery is for delivering and selling, not for being your only copy. Work that way and a mid plan stretches a long way. So pick the plan that fits the jobs you have on at once, not the entire back catalogue of your career. You can always add a pack the week a wedding lands, and let it go the week after you deliver. ### Set the hours you actually work (and let clients book around them) Weekends only, evenings after a day job, three long days and four off. Your booking calendar should match your real life, not a default nine to five. Here is how to set opening hours per day, per person, with buffers and notice that protect your time. The Bookatu team · 2026-06-30 · Grow your business · https://bookatu.com/en-nz/blog/set-the-hours-you-actually-work · markdown: https://bookatu.com/blog/set-the-hours-you-actually-work.md > **The short version** > > - Set each day separately. Open Saturday and Sunday, close Monday to Friday, or any pattern you like. > - Each team member also has their own working days, so a weekend shooter and a weekday assistant can share one calendar. > - A buffer between bookings gives you time to pack down, travel, or just breathe. > - A minimum notice stops someone booking you for twenty minutes from now. > - Clients only ever see the times you are genuinely free, so there is nothing to decline later. Plenty of the people who run a business on Bookatu do not work a standard week. A photographer shoots weddings on weekends and edits midweek. A trainer takes early mornings and evenings around a day job. A weekend market stall, a side business, a studio open three long days and shut for four. The booking page should bend to that, not force you into office hours you do not keep. #### Set hours per day, not one blanket rule Opening hours are set a day at a time. Each day has its own switch and its own start and finish, so you are not stuck applying one rule to the whole week. Want Saturday and Sunday open from eight, and Monday through Friday closed entirely? Turn five days off and set two. The calendar immediately stops offering the days you do not work, and a client looking for a Tuesday simply will not see one. > If a time is not one you would happily say yes to, it should not be on the page. The fix is in your hours, not in declining later. #### Each person has their own days If you have a team, the business hours are the outer edge and each person narrows it from there. The studio might be open six days, while one photographer only works weekends and an assistant only covers weekdays. Set each person's working days and the calendar lines them up for you, so a client booking that photographer is offered weekend slots, and the assistant's weekdays stay separate. Nobody gets booked on a day they do not work. #### Give yourself room with buffers and notice Two small settings save a lot of stress. A buffer adds quiet time after each booking, for packing down, travelling to the next location, or resetting the room, and it means the next client cannot land right on top of the last one. A minimum notice sets how far ahead someone has to book, so you are not pinged for an appointment starting in fifteen minutes while you are still at the previous one. Set both to match how you actually run a day. The point of all of this is quiet. When your hours match your life, the booking page does the saying-no for you, gently and in advance, and every time it offers is a time you are genuinely glad to take. ### Add a Book Now button to your website or Instagram bio You already have a website and a bio link. Paste one line of code, or drop in your booking link, and turn the visitors you already get into booked appointments, with no plugin and no commission. The Bookatu team · 2026-06-29 · updated 2026-10-30 · Grow your business · https://bookatu.com/en-nz/blog/book-now-button-website-instagram-bio · markdown: https://bookatu.com/blog/book-now-button-website-instagram-bio.md > **The short version** > > - Paste one line of code to put a Book Now button on Squarespace, Wix, WordPress, Shopify or any site. > - No website? Use your booking link in your Instagram, TikTok or Facebook bio so the button is your link. > - Choose a button that opens your booking page in a new tab, a pop-up over your page, your menu inside the page, or a button that floats on every page. No plugin, no commission. > - It works inside social in-app browsers, where copy-paste links and pop-ups usually fail. Most service businesses do not have a traffic problem. They have a turning-visitors-into-bookings problem. People already find you, on your website, on your Instagram, on a Google listing, then leave to send a DM that you answer hours later, by which time the moment has passed. The fix is to let them book on the spot, wherever they already are. #### On your own website: one line of code Open Grow, then Website widget. Choose Button, Pop-up, Inline menu or Floating, set the label and colour, copy the snippet, and paste it into your site: an Embed or Code block in Squarespace, an Embed HTML element in Wix, a Custom HTML block in WordPress, or a Custom Liquid section in Shopify. Publish, and the widget appears on your page. ![Smartphones laid out on a pale blue background](https://images.unsplash.com/photo-1556656793-08538906a9f8?auto=format&fit=crop&w=1200&q=70) *Whichever site or phone your visitor is on, the button takes them straight to your booking page.* The Button is a real link, not a scripted pop-up window. That matters more than it sounds: pop-up windows are silently blocked inside the in-app browsers that Instagram, Facebook and TikTok use, so a lot of social traffic taps a booking pop-up window and nothing happens. A plain link is handled by the browser itself, so it opens every time, supports tap, long-press and open-in-new-tab, and is never blocked. #### No website? Your bio link is your button If your storefront is your Instagram, you do not need a site at all. Copy your booking link and put it in your profile bio (or in a link-in-bio tool), and add it to your TikTok, Facebook and Google Business Profile. A clear "Book now" call to action against that link does the same job as the button: it removes the DM step entirely. #### Why this beats DMs and third-party marketplaces - It is instant. A client books while they are looking at your work, not three hours later when you reply. - It is yours. The booking, the client's details and the deposit go to your account, not a marketplace that rents your own clients back to you. - It carries your no-show protection. The same deposits and reminders that protect your calendar apply to a booking made from your bio. - It costs nothing per booking. There is no per-cover or per-appointment commission skimmed off the top. One small thing to know: a site builder's draft or preview mode sometimes runs your page inside a locked-down frame that blocks any outbound link, including this one. That is the preview sandbox, not the button. Always check it on the published, live page, where it works as expected. You have already done the hard part of getting people to look. Give them a button, and let the ones who are ready book themselves in. To count those bookings in your own analytics, or to open the widget on a day or with a promo code, see our post Track website bookings in Google Analytics and Meta. ### Booking software for photographers: book, deliver and get paid in one place A plain guide to booking software for photographers: take deposits that stop no-shows, deliver private proofing galleries that sell the extra shots, and keep 100% of every booking with 0% commission. The Bookatu team · 2026-06-29 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-photographers · markdown: https://bookatu.com/blog/booking-software-for-photographers.md > **The short version** > > - Take a deposit when a shoot is booked, so a cancelled date does not cost you the day. > - Deliver a private proofing gallery: watermarked previews, the client hearts their favourites, full-resolution unlocks once they are settled. > - Charge for extra shots beyond an included set, right inside the gallery, with the money landing in your own account. > - 0% commission: the booking, the client and the payment are yours, not a platform's. Photography is two businesses stitched together. There is the booking side (filling dates, holding them, getting paid a deposit) and the delivery side (sending proofs, getting a selection back, selling the extras, handing over the finals). Most photographers run the first half in a calendar and DMs and the second half in email attachments and a separate gallery tool. Bookatu does both in one place, so a shoot flows from enquiry to delivered files without leaving the app. #### Stop losing the date: deposits at booking A photographer's worst loss is not a small fee, it is a held date that cancels the day before with nothing to show for it. Taking a deposit when the shoot is booked fixes the incentive: the client has skin in the game, and a no-show or late cancellation no longer costs you a whole day you could have sold. The deposit goes straight to your own bank through your connected account, and the balance can be collected on the day or on delivery. #### Deliver like a pro: private proofing galleries After the shoot, you upload your high-resolution files and Bookatu builds the client's view for you: a low-resolution preview with your watermark baked into the image, with the photo's hidden camera data stripped out. The client opens a private gallery, hearts the ones they love, and the full-resolution versions unlock once their selection is included or paid for. They never touch the finished files before the work is settled. ![A photographer holding a DSLR camera up against a bright sky](https://images.unsplash.com/photo-1554048612-b6a482bc67e5?auto=format&fit=crop&w=1200&q=70) *One place for the whole job: hold the date, deliver the proofs, sell the extras, hand over the finals.* #### Sell the extra shots without the awkward email Set how many photos are included in a package and a price per extra. When a client falls in love with more than their included set, the option to buy the extras is right there in the gallery, at the exact moment they are deciding. This is the quiet upsell that proofing tools are built around: a gentle included limit moves people to a decision, and the extra-photo button sits next to that decision. There is good evidence that fewer, clearer choices convert better than an overwhelming folder of 300 images, which is why an included-favourites count plus easy extras tends to beat "here is everything." #### Protect your work until it is paid for - Previews are low-resolution, so a screenshot is not a usable print. - The watermark is part of the picture, not an overlay a browser can strip off. - Full-resolution files only unlock for the photos that are included or paid. - Each gallery is private to that client, reached by a secure, expiring link. No protection makes image theft impossible, and it is honest to say so. But low-resolution, baked-in watermarks plus payment-gated downloads remove the easy, casual leak that costs photographers the most, while keeping the gallery open and easy to share. #### Keep 100%: 0% commission, your clients stay yours Marketplaces take a cut of every booking and sit between you and your client list. Bookatu charges you for the software, not a slice of your work: every booking, every gallery sale and every client record belongs to you, and payments land in your own bank account. You also get a branded booking page, automatic reminders, gift cards and packages, so the same tool that books the shoot also helps fill the quiet weeks. If you are juggling a calendar, a deposit request, a gallery link and an invoice for every single job, that is four tools doing what one can. Book the shoot, deliver the proofs, sell the extras and get paid, all in the same place. ### Introducing Pay as you go: no monthly fee, pay per team member A new way to pay for Bookatu, built for businesses that are just starting out or seasonal. No subscription and no commission. Pay US$8 per team member a month, and nothing in a month with no team. The Bookatu team · 2026-06-26 · updated 2026-11-15 · Grow your business · https://bookatu.com/en-nz/blog/introducing-pay-as-you-go · markdown: https://bookatu.com/blog/introducing-pay-as-you-go.md > **The short version** > > - No monthly plan and no contract: pay US$8 per team member, per month. > - A seat is an active team member. You pay for the team you have, so the bill never jumps with a busy month. > - There is no base fee, so a team of one pays just US$8 a month. > - A month with no team costs you nothing, and there is 0% commission on bookings. Our monthly plans are still there too: each is free for 60 days, then from US$9 a month. Not every business wants to start with a monthly subscription. If you are brand new, run a seasonal trade, or have quiet stretches, a fixed fee every month can feel like a risk before the bookings are coming in. So we built a simpler option: pay as you go. #### How it works There is no monthly plan to pick. You get everything you need to take bookings online, and at the end of each month you pay US$8 for each active team member, which we call a seat. Scale your team up or down and the bill follows. If you have no team in a given month, you pay nothing. There is nothing extra to plan for. One team member is US$8 a month, and the rate is the same for your first team member and your twentieth. A month with no team is not billed at all, and no invoice is sent for it. ![The pay-as-you-go estimator on the Bookatu pricing page, showing a cost of $32.00 a month for 4 team members](https://bookatu.com/help/payg-estimator.png) *The live estimator on the pricing page: drag the slider to the size of your team and see the monthly cost instantly.* #### What is included - Your own branded booking site - Deposits that stop no-shows - Automatic booking reminders - Payments straight into your own bank account, with our usual zero booking commission You are billed once at the end of each month, and only from the day you add a card, never for a day before. #### Pay as you go or a monthly plan Pay as you go follows the size of your team, with no commitment. If you would rather commit, our monthly plans are still there: each one is free for 60 days, then runs from US$9 to US$179 a month, and there is 0% commission on bookings either way. You can try the live estimator on the pricing page to see what pay as you go would cost for your team. If a no-commitment start is what has been holding you back, this is for you. Take a look on the pricing page and start taking bookings today. ### One Platform, Seven Trades: Who Bookatu Is For Bookatu is one booking and payments platform that reshapes itself for your trade, whether you run a salon, a gym, a restaurant or a photography studio. Here is why a tailored tool beats a blank calendar, with a day-in-the-life example for each. The Bookatu team · 2026-06-26 · Grow your business · https://bookatu.com/en-nz/blog/one-booking-platform-for-salons-trainers-restaurants-photographers · markdown: https://bookatu.com/blog/one-booking-platform-for-salons-trainers-restaurants-photographers.md > **The short version** > > - Bookatu is one booking and payments platform with a tailored setup for each trade: salons, spas, personal trainers, sports coaches, fitness and yoga studios, restaurants and photographers. > - Each industry gets its own wording and its own storefront, so the tool speaks your language from the first day. > - You keep the full value of every booking. There is no booking commission, and payments land in your own bank through Stripe Connect. > - A tool built for your trade beats a blank calendar, because the awkward parts of your week are already handled for you. #### Why a generic calendar runs out of road Most owners start with a generic calendar or a free booking link. It works for about a week. Then the gaps start to show. A hair salon needs a buffer between a colour and the next client. A photographer needs to hand over a gallery without giving away the finished files. A restaurant needs a floor plan, not a flat list. A coach needs to sell a block of ten sessions and watch them count down. A blank calendar treats all of these the same way, so you end up doing the rest by hand. That hand work adds up fast. Small businesses now juggle an average of 15 to 20 different software tools, and owners lose roughly 14 hours a week to admin like chasing payments and reconciling records, according to research summarised by Finli. The more tools you bolt together, the more places things quietly fall through. #### One platform, built for your trade Bookatu is built the other way around. It is one platform, but it knows what trade you are in. Sign up as a salon and the wording, the starter services and the storefront read like a salon. Sign up as a photographer and the same product reorganises itself around galleries and delivery. The trades it understands today: - Salons and spas - Personal trainers and sports coaches - Fitness and yoga studios - Restaurants - Photographers This is the difference between vertical and horizontal software. A horizontal tool tries to fit everyone and ends up fitting no one in particular. A vertical tool fits one trade closely. Industry analysts at Cledara point out that vertical tools tend to match the real workflow better and become harder to give up, precisely because they handle the specific jobs a generic tool leaves on your plate. #### What a tailored tool actually saves you The payoff is not abstract. Booking and reminders alone move real money. Online bookings carry roughly 49 percent lower no-show rates than phone bookings, according to Zenoti's beauty and wellness benchmark data. In restaurants, no-shows are estimated to cost the global industry around 16 billion dollars a year, which is why more venues now hold the table with a card, as Toast notes in its guide to cancellation fees. When the tool already knows your trade, these guards are switched on for you instead of being a project you never quite get to. > A blank calendar tells you when. A tool built for your trade helps with what happens next. #### A day in the life Salon or spa. A client books a balayage from your storefront on Sunday night. The slot includes the processing gap on its own. They get a reminder, so the chair does not sit empty. They pay into your own account, and you start Monday with the day already filling up. Personal trainer or coach. A client buys a pack of ten sessions. Each booking counts one down, so nobody has to argue about how many are left. If someone falls behind, your who-owes-me board shows it at a glance. You log a cash or bank payment, or send a gentle reminder, and the unpaid sessions stop slipping away. Restaurant. You lay out your room once in the visual floor-plan editor, with tables sized by how many they seat, plus chairs and decor so it looks like the real place. Guests reserve online and you seat them against the actual plan, not a guess. Friday night runs on a map of your floor instead of a notebook and a felt-tip pen. Photographer. You shoot a wedding and upload the high-resolution files. Bookatu makes a low-resolution preview at 1080px with the watermark baked in and the EXIF data stripped, so the couple can browse and pick favourites without the finished files leaking out. They get a set number of edits included and pay for any extras. The full-resolution files unlock only once that set is settled. A secure 30-day link handles the handover, and a delivery board tracks who has received what. As your galleries grow, you add storage in 25GB packs billed on your subscription. Studio. A yoga or fitness studio runs classes and one-to-ones from the same place, with the same reminders and the same payouts, all under its own branding. #### Your money, your bank One rule sits under all of this. Bookatu charges 0 percent booking commission. Payments go straight to your own bank through Stripe Connect, into your own account. That means you reconcile your own takings and your own taxes the normal way, with nothing skimmed off the top of each booking. #### Who it is for Bookatu is for the owner who is also the receptionist, the bookkeeper and the marketer. If your week has a shape that a plain calendar keeps fighting, the tailored version is most likely already built. A few extra touches travel across every trade: - A client portal that opens with a passwordless magic link, so customers never reset a password - Your own branding and colours, with a dark mode included - Storage you can grow as you go, so a busy photographer is never boxed in You do not have to be technical to make any of this work. You pick your trade, and the tool meets you there. #### Sources - Vertical vs Horizontal SaaS: The Similarities and Differences (Cledara): https://www.cledara.com/blog/vertical-vs-horizontal-saas - Salon, Spa & Medspa Benchmarks 2025 (Zenoti): https://www.zenoti.com/thecheckin/beauty-wellness-industry-statistics-2025 - Restaurant Reservation Cancellation Fees: The Complete Guide (Toast): https://pos.toasttab.com/blog/on-the-line/restaurant-reservation-cancellation-fees - Why Small Businesses Cobble Together Disconnected Tools (Finli): https://finli.com/learn/why-small-businesses-cobble-together-disconnected-tools/ - Stripe Connect product overview: https://stripe.com/connect ### Preview, pick, pay, download: private galleries that sell your photos for you A private online gallery lets clients browse a safe watermarked preview, choose their favourites, and pay for extras before they download. Here is how that one flow saves you hours and earns you more. The Bookatu team · 2026-06-25 · Grow your business · https://bookatu.com/en-nz/blog/photographer-private-galleries-preview-pick-pay-download · markdown: https://bookatu.com/blog/photographer-private-galleries-preview-pick-pay-download.md > **The short version** > > - A private gallery gives each client one safe link to view a watermarked preview of their shoot. > - Clients pick favourites themselves, so you stop chasing replies and re-sending files. > - They get an included free count, then pay for any extras before they download. > - Full-resolution photos only unlock once the included or paid set is settled. > - Money lands in your own bank through Stripe, with 0% booking commission from Bookatu. Taking the photos is the part you love. The part that eats your week is everything after. Culling, exporting proofs, emailing a big folder, waiting, answering "can I see the others again?", then exporting once more. Imagen's industry write-up found that post-production speed is the number one operational headache photographers name, ahead of everything else in the business. A private online gallery takes most of that back-and-forth off your plate. Here is what the client actually does, and what it does for your time and your income. #### The client journey: preview, pick, pay, download In the photographer setup on Bookatu, you upload your high-resolution files. The platform then builds the version your client sees for you. It makes a low-resolution preview, around 1080px on the long edge, with your watermark baked into the image and the photo's hidden camera data stripped out. The client never touches the full-quality files until the order is settled. - Preview: the client opens a secure link and browses the watermarked set on their phone or laptop. No app, no password. - Pick: they tap their favourites. They get an included free count you decide, and they can pay to add more. - Pay: card payment happens right inside the gallery, in the moment they are most excited. - Download: once the included or paid photos are settled, the full-resolution versions unlock for those images. You are not in the middle of any of that. You shoot, you upload, and the gallery does the asking, the counting, and the collecting. #### Fewer choices is not a limit. It is a nudge to buy. Giving someone a folder of 300 images feels generous. In practice it stalls them. This is the lesson of the famous jam study by Sheena Iyengar and Mark Lepper, summarised well over at digitalwellbeing.org. A shop table with 24 jams drew more lookers, but only 3% bought. A table with just 6 jams converted at 30%. People presented with fewer options were roughly ten times more likely to actually choose. An included favourites count works the same way. Pixieset's own proofing guide makes the point that gentle limits, like "choose your best 20", reduce decision fatigue and move clients to a decision faster. The clever part is what sits next to that limit. Once someone has picked their 20 and still loves number 21, the extra-photo option is right there. The structure that helps them decide is the same structure that sells the next image. > The easiest upsell is the one your client reaches for on their own, while they are still looking at the photo they fell in love with. #### Why the watermarked preview matters Showing low-resolution, watermarked previews is not about distrust. It is about keeping the value in the work you have not been paid for yet. Because the watermark is part of the picture and the file is small, a screenshot is not a usable photo. The full-resolution image only unlocks once that image is included or paid. So the gallery can be open and easy to share while your best files stay protected until the order is done. It also keeps things tidy on your side. Each client gets their own private gallery behind a secure link that expires after 30 days, so you are not leaving shoots sitting on the open web. A delivery board in your studio view shows you which galleries are out, which are picked, and which are paid, all in one place. #### The income lands in your bank, not ours When a client pays for extra photos, that money goes straight to your own bank account through Stripe Connect. It is your Stripe account, so the payout, the records, and the tax all sit with your business where they belong. Bookatu takes 0% booking commission on top. You keep the structure that makes selling easy without handing over a cut of each sale. That matters more as the work shifts online. Zenfolio's 2026 industry survey shows how much of the client relationship now happens through a screen, which makes a clean digital buying moment a real revenue lever rather than a nice extra. #### Set it up once, then mostly forget it The point of all this is fewer manual steps per shoot. You are not exporting proofs by hand, chasing selections by email, or re-sending downloads. A few things keep it running smoothly: - Branding: the gallery carries your studio name, colours, and a dark mode, so it feels like your business, not a generic tool. - Magic links: clients sign in with a tap, with no password to reset and no support ticket for you. - Storage: space is metered, and when a busy season fills it you can buy +25GB packs that simply add to your platform subscription. - One platform: the same Bookatu account handles your bookings, so a new client can book a session and end up in a gallery without you stitching tools together. None of this replaces your eye or your editing. It just removes the slow, repetitive layer between finishing a shoot and getting paid for it. The client does the picking. The gallery does the asking and the collecting. You get your evenings back, and the extra-photo sales you were too busy to chase start happening on their own. #### Sources - It's 2026, and photographers still spend too much time editing, Imagen: https://imagen-ai.com/post/photographers-spend-too-much-time-editing/ - 8 tips to help clients choose favourite photos faster with online proofing, Pixieset Blog: https://blog.pixieset.com/blog/favorite-photos-online-proofing/ - The Jam Study Strikes Back: When Less Choice Does Mean More Sales, digitalwellbeing.org: https://digitalwellbeing.org/the-jam-study-strikes-back-when-less-choice-does-mean-more-sales/ - 2026 State of the Photography Industry Survey Results, Zenfolio: https://zenfolio.com/blog/2026-photography-industry-survey-results/ ### Photo Proofing That Protects Your Work: Watermarks, Low-Res Previews, and Pay-First Downloads Proofing is where most photos quietly leak. Here is how watermarked low-res previews, baked-in marks, and payment-gated downloads keep your full-resolution work safe, plus the honest limits of stopping image theft. The Bookatu team · 2026-06-24 · Grow your business · https://bookatu.com/en-nz/blog/photo-proofing-protect-your-work-online · markdown: https://bookatu.com/blog/photo-proofing-protect-your-work-online.md > **The short version** > > - Show clients low-resolution, watermarked previews. Keep the full-resolution files back until they have paid. > - A watermark baked into the pixels survives downloads, screenshots, and crops. An overlay you can switch off in a browser does not. > - You own the copyright the moment you press the shutter. Paying for a session is not the same as buying the files. > - Strip hidden EXIF data, like GPS, from previews so a shared link does not leak a location. > - Bookatu does all of this automatically: upload high-res, clients see a 1080px watermarked preview, and full files unlock only after the agreed set is paid. Most photographers worry about someone stealing a finished, delivered image. The bigger gap sits earlier, at the proofing stage, when you send a gallery so a client can choose their favourites. That is the moment your photos sit on a screen, in a browser, ready to be saved. Good proofing closes that gap without making the client feel watched. #### Why proofing is where work leaks Proofing galleries are useful. They let clients pick photos, mark favourites, and order without a long email chain. But every preview you show is a file a browser has already loaded. Most professional galleries handle this with secure links, password protection, and watermarks. The principle is simple. Show enough for the client to choose well. Hold back enough that an unpaid file is not worth stealing. #### Low-res previews carry most of the weight The most reliable trick is also the oldest. Serve your previews at a low resolution. A small file looks crisp on a phone or laptop, but it is too small to print well. Photographers have leaned on this for years, because an image only a screen-width wide cannot become a large, sellable print. You are not hiding the photo. You are making the stolen copy useless. - A 1080px preview looks sharp on screen but holds up poorly in print. - The full-resolution file, the one worth money, never leaves your control before payment. - The client still gets a true sense of the final shot, so they can choose with confidence. #### Baked-in watermarks beat overlays A watermark can be added two ways. An overlay sits on top of the image as a separate layer in the web page. A baked-in watermark is drawn into the pixels of the file itself. The difference is everything. An overlay can often be stripped by anyone who opens browser developer tools or simply saves the underlying image. A baked-in mark travels with the file. Save it, screenshot it, or crop it, and the mark is still there. Placement matters too. Gallery providers like ShootProof advise putting the mark where it is hard to crop out, over a detailed part of the image rather than an empty sky, and at an opacity that protects the file without ruining the view. A mark across a face or a busy background is far harder to paint out than one floating in a clear corner. > An overlay protects the web page. A baked-in watermark protects the photo. Only one of those leaves with the file. #### The honest truth about image theft No system makes an image impossible to copy. Anything shown on a screen can be captured in some form. The goal is not a perfect wall. It is to make casual theft pointless and to keep the valuable file out of reach. One industry summary citing a Professional Photographers of America survey reported that 71% of photographers had experienced some form of image theft or misuse. That is why low-res previews and watermarks are standard practice rather than paranoia. There is a quieter risk too. Photos carry hidden metadata called EXIF, which can include the GPS coordinates of where a shot was taken. As Proton explains, that data can reveal a home address or a daily routine. Stripping it from previews protects your client as much as it protects your work, so a shared gallery link never gives away a location. #### Your copyright is the real protection Watermarks and small files reduce the temptation. Copyright is what gives you teeth when someone crosses the line. The U.S. Copyright Office states plainly that you own the copyright the moment you take the photo. No registration, watermark, or copyright notice is required for that ownership to exist. The Professional Photographers of America makes the same point. When a client pays for a session, they buy your time and skill, not the copyright. This is why licensing matters. When you deliver images, you are usually granting permission to use them in certain ways, not handing over ownership. ASMP, the American Society of Media Photographers, frames a license around how an image will be used, for how long, and in what media. Clear terms up front prevent most disputes, and they let you charge fairly when a client later wants wider use. #### How Bookatu fits in Bookatu builds these protections into its photographer galleries so you do not have to assemble them yourself. You upload your high-resolution files. The platform automatically generates a low-resolution preview at 1080px, bakes the watermark into the image, and strips the EXIF data. Your client only ever sees that protected preview. - Clients browse the private gallery, mark favourites, and get an included free count of photos. - They pay for any extra photos beyond that count. - Full-resolution files unlock only after the included and paid set is settled. - Galleries are shared through secure 30-day magic links, and a delivery board tracks what has gone out. Payments go straight to your own bank through Stripe Connect, so you reconcile your own taxes, and Bookatu takes 0% booking commission. Storage is metered, and you can buy +25GB packs that are billed on your subscription when a busy season fills your galleries. None of this replaces a good contract or your copyright. It just means the everyday work of protecting your images, the previews, the watermarks, and the locked downloads, happens by default while you get on with shooting. #### Sources - U.S. Copyright Office, What Photographers Should Know about Copyright: https://www.copyright.gov/engage/photographers/ - Professional Photographers of America, Copyright Law: Understanding Your Rights as a Photographer: https://www.ppa.com/articles/copyright-law-your-rights-as-a-photographer - ASMP, Licensing Guide: Retail Example: https://www.asmp.org/professional-development/pricing-guides/licensing-guide-retail-example/ - ShootProof, Protect Your Photos Against Theft: https://www.shootproof.com/blog/protect-your-photos-against-theft/ - Proton, EXIF data in shared photos may compromise your privacy: https://proton.me/blog/exif-data - The Contract Shop, How Do Professional Photographers Protect Their Images: https://thecontractshop.com/blogs/posts/how-do-professional-photographers-protect-their-images ### Event-driven by design: how one payment becomes loyalty, retention, and a receipt A booking platform lives or dies on consistency. Here is how a single Stripe payment fans out into loyalty points, retention, a receipt and a ledger entry, why every effect is gated on a real state change, and where we are taking the architecture next. The Bookatu engineering team · 2026-06-24 · Engineering · https://bookatu.com/en-nz/blog/event-driven-by-design-the-post-payment-ripple · markdown: https://bookatu.com/blog/event-driven-by-design-the-post-payment-ripple.md > **The short version** > > - One payment should ripple: loyalty, retention, a receipt and the ledger all follow from it. > - Every downstream effect is gated on a genuine state change, so a Stripe retry never double-fires. > - The webhook is the seam. Today it is a tidy in-process fan-out; the roadmap turns that seam into a durable event bus. When a client pays for a booking, a deposit, a package or a membership, that single event should move the whole system. Their loyalty balance should grow. They should count as active again, not lapsed. They should get a receipt. And the money should land in the books for reconciliation. Get one of those wrong and the product quietly loses trust: a member is charged but their credits never appear, or a Stripe retry double-counts a sale. For a while each of those was its own island. The webhook marked things paid and stopped there. So we made the payment an event, and let the rest of the system react to it. #### The pattern: fan out, but only on a real state change ![Diagram: a Stripe payment hits an idempotent webhook, which calls applyPaidRipple, fanning out to loyalty, retention, receipt and ledger.](https://bookatu.com/blog/eng-event-driven.jpg) *One payment, four effects. The webhook is the seam; the ripple is best-effort and never blocks the money path.* Stripe sends checkout.session.completed to one webhook. The handler does the money-critical write first (mark the deposit paid, flip the invoice to paid, grant the package credit), then calls a single shared function, applyPaidRipple, for the engagement side. The ripple is best-effort: every step is wrapped so a failure logs and is swallowed, because a flaky email provider must never stop us from recording a real payment. ```ts // In the webhook, after the money-critical write succeeds: if (fresh) { await applyPaidRipple({ orgId, customerId, amountCents, loyaltyReason: "Package purchase", receiptTo: email, receiptDedupeKey: `payment_receipt:package:${session.id}`, }); } // applyPaidRipple: loyalty -> lastVisitAt bump -> transactional receipt, // each in its own try/catch. The ledger write runs unconditionally below. ``` #### Idempotency is the whole game Stripe will deliver the same event more than once. That is a feature, not a bug, and it means every handler has to be safe to run twice. Two layers protect us. First, the event id is recorded in a processed-events table with a unique constraint, so a redelivery of the exact same event short-circuits. Second, and more importantly, each pathway gates its ripple on its own genuine state change: a boolean that is only true the first time the row actually flips. ```ts // markInvoicePaid flips 'open' -> 'paid' and returns true ONLY on that // real transition. A redelivery sees 'paid' already and returns false. const flipped = await markInvoicePaid(invoiceId, paymentIntentId, amountTotal); if (flipped) { await applyPaidRipple({ /* ...loyalty, retention, receipt */ }); } // So even if the event-id dedupe is bypassed, the ripple still fires once. ``` > The dedupe key is not a nice-to-have. It is the difference between a member being thanked once and being charged twice. #### Where this is heading Today the ripple is an in-process fan-out, which is the right amount of machinery for where we are: it is simple, transactional and easy to reason about. But the webhook is deliberately a seam, and the roadmap turns that seam into a durable event bus. The shape stays the same; the delivery gets stronger. - A queue in front of each effect (loyalty, retention, messaging), so a slow consumer never holds up the webhook and retries are automatic with backoff. - An outbox table written in the same transaction as the money, then relayed to the bus, so an effect is never lost between 'paid' and 'published'. - Splitting the heaviest consumers (notifications, retention scoring) into their own deployable services as load grows, while the core booking write stays a single, strongly-consistent unit. - A managed event/queue layer on our cloud, so scale is a config change rather than a migration. The lesson that holds across all of it: keep the money path strongly consistent and synchronous, and make everything that hangs off it event-driven, idempotent and best-effort. A payment is a fact. Everything good that follows from it is a reaction, and reactions should be safe to replay. ### Set up payments for your salon: it really does take two minutes Connecting payments sounds technical, but it isn't: it's a short, guided form from Stripe. Here is exactly what you will be asked, why, and how to get from "started" to "ready to take deposits" in one sitting. The Bookatu team · 2026-06-24 · Grow your business · https://bookatu.com/en-nz/blog/set-up-payments-for-your-salon · markdown: https://bookatu.com/blog/set-up-payments-for-your-salon.md > **The short version** > > - Connecting payments is a short, guided form from Stripe, our payments partner. No tech skills needed. > - You will need your bank account details and a photo ID. That is genuinely it. > - Most owners finish in about two minutes, and the money lands straight in their own account. If you have started setting up payments and then quietly closed the tab, you are in good company. It is the one step that sounds technical, so it is easy to put off for "when I have a proper sit down". The truth is less scary than it looks: there is no code, no integration, and nothing to install. It is a form, run by Stripe, that asks a few questions about your business so they can pay your takings into your bank. #### Why it is worth two minutes Until payments are connected, your booking page can take bookings but not money. That means no deposits, so a no-show costs you the whole slot, and no card payments, so clients pay you another way or not at all. The moment you connect, you can ask for a deposit to hold a booking, and deposits flow into your own account. Bookatu never holds them and never takes a cut of your bookings. #### What you will actually be asked When you tap "Connect payments", Stripe opens a short form. It is the same secure flow used by huge companies, just sized for a one-chair business. Have these handy and you will breeze through: - Your business basics: name, what you do, and your address. We pre-fill what we already know, so there is little to type. - A bank account: the account where you want your takings to land. This is the part people most often skip, and the one thing Stripe truly needs. - A photo ID: a driver licence or passport, to confirm you are you. Stripe checks it; we never see it. #### Why it asks for your ID Anyone who moves money has to confirm who they are. It is the law everywhere, and it is what keeps fraud out of the system. Stripe handles that check on your behalf so you do not have to think about it. Your ID and bank details go straight to Stripe over a secure connection; they are not stored by Bookatu and they are never visible to your clients. > The setup is not the hard part. The hard part is remembering to add your bank account before you wander off. #### The bit where most people stop, and how to finish If an account is "started but not finished", it is almost always for the same two reasons: a bank account has not been added yet, and Stripe's terms have not been accepted. Both take seconds. If you closed the tab partway, you do not lose your progress. Just open your dashboard and tap "Finish setting up payments", and Stripe drops you back exactly where you left off. #### How you will know it is done When the form is complete, your account flips to "ready to take payments", your booking page can ask for deposits, and your storefront goes live to clients. From then on Stripe pays your balance out to your bank on a regular schedule, usually every couple of business days, and you handle any refunds from your own Stripe dashboard. Two minutes once, and you are getting paid your way. ### Sell Session Packs and Stop Chasing Payments: A Calmer Money Setup for Trainers and Coaches Per-session billing makes your income lumpy and your week stressful. Here is how prepaid session packs and a simple "who owes me" board help you get paid up front, keep clients showing up, and stop chasing cash. The Bookatu team · 2026-06-23 · Recurring revenue · https://bookatu.com/en-nz/blog/sell-session-packs-stop-chasing-payments-trainers-coaches · markdown: https://bookatu.com/blog/sell-session-packs-stop-chasing-payments-trainers-coaches.md > **The short version** > > - Selling session packs (buy 10, they tick down) gets you paid up front and gives clients a reason to keep showing up. > - Fitness research links commitment and prepaid plans to better retention, and better retention is worth real money. > - Chasing cash and bank-transfer clients quietly eats hours every week. A simple board fixes it. > - Bookatu's trainer setup does both: packs that auto-decrement, plus a "who owes me" board to log cash or bank payments and send reminders. > - Your money lands in your own bank through Stripe Connect, with 0% booking commission from us. #### The pay-as-you-go trap If you bill one session at a time, your income jumps around. A client books, cancels, reschedules, then disappears for two weeks. You feel it in your bank balance and in your head. Coaches who sell big lump-sum packages run into a different version of the same problem. Clients buy a long block, then stretch it out over months because of holidays, illness, or work. The fitness coaches at The Business Movement note that monthly and committed plans keep clients accountable, and they report cancellations dropping from around 20% to about 5% when clients have skin in the game. Those are example figures from one coaching practice, not a promise, but the pattern is familiar to anyone who trains people for a living. Money you have not collected yet is the hardest money to earn. So the goal is simple. Get paid earlier, and give the client a clear reason to come back. #### Why prepaid packs help you keep clients When someone has already paid for ten sessions, skipping a session feels like wasting money they own. That small bit of pressure works in everyone's favour. The client trains more. You earn steadier income. Both of you stay motivated. The wider industry data points the same way. The Health & Fitness Association (formerly IHRSA) reports that members who commit to a longer agreement tend to stay longer than members on loose, month-to-month arrangements. Trainerize, which works with thousands of fitness pros, points out that clients who work with a trainer are far more likely to renew and stick around than those who go it alone. They also cite a well-known retention rule of thumb: a small lift in retention can lift profit by a surprisingly large margin. Again, treat those as general industry figures, not a guarantee for your business. The takeaway for a busy trainer is not complicated. Selling in packs, instead of one session at a time, nudges clients toward the kind of commitment that retention research keeps rewarding. > Paid-for sessions are the ones clients hate to waste. That is exactly the habit you want to build. #### How session packs work in Bookatu Bookatu has a setup made for personal trainers and sports coaches, so the wording and the storefront fit your work instead of a generic salon template. You can sell 1:1 sessions, and you can sell session packs. - Create a pack, like "10 sessions", and set your price. - The client buys it once and pays up front. - Every time they book and attend, the balance ticks down automatically. No spreadsheet, no mental maths. - Clients book and manage everything through a simple client portal. They sign in with a magic link sent to their email, so there are no passwords to forget. - Your storefront carries your own branding and colours, with a dark mode, so it looks like you and not like us. On the money side, Bookatu takes 0% booking commission. Payments run through Stripe Connect into your own bank account, under your own name. That means you reconcile your own income and handle your own taxes, the normal way, with nothing sitting in a middleman's account. #### The "who owes me" board for cash and bank clients Not everyone pays by card. Plenty of clients hand you cash at the door or promise a bank transfer "tonight". Then life happens and you forget who is square and who is behind. Chasing it feels awkward, so you let it slide, and the gap grows. This is a real cost, not a small one. Intuit QuickBooks, in its 2025 US Small Business Late Payments Report, found that more than half of small businesses are owed money on unpaid invoices, and that owners can lose around 14 hours a week to the admin of chasing late payments. Hours you would rather spend coaching, or resting. Bookatu gives you a missed-payment recovery board, a plain "who owes me" view. You log cash and bank payments as they come in, so the board always shows who is paid up and who still owes you. When someone falls behind, you can send a reminder from the same place, instead of writing an uncomfortable message from scratch. It turns an awkward chase into a quick, routine task. #### A calmer week, with steadier money Put the two pieces together and your week changes shape. Packs bring money in earlier and pull clients back to the gym. The board makes sure the cash and bank clients do not quietly slip through. You spend less time worrying about who paid, and more time doing the work you are good at. You do not need a finance degree or a new system to learn. Set up a pack, share your booking link, and log payments as they land. That is the whole thing. The research on retention and late payments has been telling small operators the same story for years. Get paid up front, keep people committed, and stop letting unpaid sessions pile up. #### Sources - Health & Fitness Association (IHRSA) Member Retention Report: https://hub.healthandfitness.org/member-retention-report - Trainerize: Gym Member Retention Strategies: https://www.trainerize.com/blog/gym-member-retention-strategies/ - Intuit QuickBooks: 2025 US Small Business Late Payments Report: https://quickbooks.intuit.com/r/small-business-data/small-business-late-payments-report-2025/ - The Business Movement: New Client Payment Plans That Will Upgrade Your Business: https://www.thebusinessmovement.com/fitness-business-blog/new-client-payment-plans-that-will-upgrade-your-business ### Booking Software for Hair Salons: A Plain Guide A plain guide to booking software for hair salons: your own branded booking page, synced stylist calendars, deposits that stop no-shows, and 0% commission. The Bookatu team · 2026-06-23 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-hair-salons · markdown: https://bookatu.com/blog/booking-software-for-hair-salons.md > **The short version** > > - Booking software for hair salons lets clients book the chair themselves, day or night, without ringing you mid blow-dry. > - Look for your own branded booking page, every stylist's calendar in one place, and 0% commission so the colour money stays yours. > - Deposits and card holds calm the no-shows. With Bookatu they land in your own bank, because you connect your own Stripe. > - Free for 60 days, no card needed, with all the core booking features. Plans start at $9 a month after that. Nobody goes shopping for booking software for the fun of it. You go looking because the phone keeps ringing while you've got foils in someone's hair, because there's a gap in the book nobody warned you about, or because a client no-showed on a two-hour balayage and that slot is gone for the day. Good booking software sorts out the boring, costly bits that sit between you and a full chair. This is a short, honest walk through what the right tool actually does for a hair business, what to look for, and a couple of traps worth dodging. No hype. Just the parts that matter when your day is spent at the basin and the chair. #### What it actually does for a hair salon At its plainest, a client opens a link, sees your real availability, picks their stylist and service, and books. While you're mid colour. While you're closed. While you're asleep. The booking drops straight into the right calendar and you never touched the phone. Hair has its own quirks, so a few things make or break the tool. Your services aren't all the same length, so it has to handle a 20-minute fringe trim and a four-hour full head without double-booking the chair. Clients usually want a specific stylist, and they should be able to ask for them. And colour has processing time in the middle, so a junior can be on hand and the day keeps moving while the timer runs. - Clients book the right service with the right stylist, and the correct time gets blocked out. - Every team member has their own calendar, with two-way Google Calendar sync so personal plans and appointments never clash. - You set your hours, breaks and days off once, and the booking page sticks to them. - Your salon gets its own branded booking page at its own link, so clients book you, not a marketplace stuffed with the salon down the road. #### No-shows and late cancels A no-show on a quick trim stings a little. A no-show on a colour correction can wipe out the most profitable two hours of your week. This is where the right tool starts paying for itself. Deposits and card holds are the quiet fix. Ask for a deposit on the bigger services, or hold a card on file, and the people who used to drift off tend to remember they've booked. Here's the part owners miss: with Bookatu you connect your own Stripe account, so every deposit goes into your bank, not ours. Bookatu never touches your booking money. We're the software, not a middleman sitting on your takings. > The chair only earns when someone's in it. A deposit is just a polite way of asking people to show up. Add reminders by text and email, plus a smart waitlist that offers a freed-up slot to the next client in line, and a lot of the gaps that used to cost you stop appearing. When one does open up, it gets filled instead of sitting empty until you lock the door. #### The fees question, before it costs you Slow down on this one. Plenty of booking platforms take a commission off your bookings. A few dollars off this cut and colour, a slice off that one. On a single appointment it looks like nothing. Across a busy year it's one of the biggest invisible costs a salon carries, and the busier you get, the more you hand over. That's a strange deal to sign up for. Bookatu takes 0% commission. The full price of every cut, colour and treatment stays with you. Instead of skimming bookings, the pricing goes on your active clients, meaning people you've actually seen in the last 90 days, never per stylist seat. Free for 60 days with no card, then plans start at $9 a month. A good month stays a good month. When you compare tools, look past the headline price and ask one thing: what happens to my money on every appointment? A tool that costs you more the better you do is quietly working against you. #### What to look for when you choose Most owners shopping for booking software for hair salons are weighing up two or three options. A short checklist keeps you honest, because the things that bite you later are rarely the ones in the sales pitch. - 0% booking commission, so growth feeds your bank, not the platform's. - Money paid into your own account through your own Stripe, not parked in a platform wallet. - Your own branded booking page and link, not a slot in a marketplace next to rival salons. - Per-stylist calendars with two-way Google Calendar sync, so the whole team stays clash-free. - Deposits and card holds to protect your colour slots, plus reminders and a waitlist as backup. - Predictable pricing. Bookatu charges by active clients, not per seat, so taking on a junior doesn't bump the bill. - Core features on every plan. Reviews, win-backs, loyalty points, gift cards, packages, memberships, referrals, promo codes and marketing newsletters come on every Bookatu plan. That last one is worth a second. Plenty of platforms keep the useful features one tier up, so the thing you actually need is always on the plan above yours. Every Bookatu plan includes the core features, and only a few optional add-ons cost extra. The plan price tracks how many clients you serve, not how many tools you switch on. #### It's your salon, and your client list Here's something easy to miss until you try to leave a platform: who owns the clients. On a marketplace, the people who book you can start to feel like the marketplace's customers, not yours. They get nudged toward other salons, and if you ever move on, that list can be hard to take with you. With Bookatu your clients are yours. No marketplace pulling them toward your competitors, no middleman between you and the people in your chair. You own the relationship, the list and the rebooking. The software's job is to make your day easier and your chair fuller, then stay out of the way. If you've been running the diary on a paper book, a string of texts and a held breath, the right booking software hands back the evenings you used to spend confirming tomorrow's clients. Set it up once, let it tick along in the background, and put your energy where it belongs: the hair. Get the tool right and the rest of the day gets a lot quieter. ### Take Online Reservations and Design Your Floor Plan Online: Fewer Phone Calls, Fewer No-Shows A visual floor plan plus online booking lets guests reserve a real table while you are busy, cuts the calls your host has to answer, and gives you the reminders that keep tables filled. Here is how it works and what the research says. The Bookatu team · 2026-06-22 · Grow your business · https://bookatu.com/en-nz/blog/restaurant-floor-plan-online-reservations-fewer-no-shows · markdown: https://bookatu.com/blog/restaurant-floor-plan-online-reservations-fewer-no-shows.md > **The short version** > > - Most diners now want to book online, so a phone-only door costs you reservations after hours and during the rush. > - Online booking takes work off your host. Guests see real openings and book themselves, which means fewer interrupting calls. > - A visual floor plan means each booking lands on a real table sized for the party, not a guess in a paper book. > - Automatic reminders and a card hold can lower no-shows. OpenTable reports card-hold guests are up to 16% less likely to skip. > - In Bookatu you build the floor plan and take reservations in one place, with 0% booking commission and payouts to your own bank. #### The phone is costing you tables Picture a Friday at 7pm. The room is full, the pass is calling, and the phone keeps ringing. Each call is a guest who wants a table, a time, or a change. Your host has to stop, find a pen, and read back a paper book while three people wait to be seated. Some callers give up. Some get booked into a table that does not fit them. A few never get through at all. That friction is now a real cost, because the way people book has changed. Toast's 2025 reservation data found that 65% of diners go straight to a restaurant's own website to book, and most people who reserve online do it from a phone while they are out and about. If your only front door is a ringing phone during service, you are turning away the exact bookings you want most. Phone bookings also break in quiet ways. A name heard wrong, a party of six written as four, two staff taking calls at once and double-seating the same table. Tableo, which builds reservation tools, points out that every phone step adds a chance for human error, and that online booking removes a large slice of that risk by letting guests enter their own details. #### Let guests book themselves, day or night Online reservations fix the timing problem first. A booking page is open at 11pm, on a Sunday, and in the middle of your dinner rush, when nobody can pick up. The guest sees which times are actually free and picks one. You wake up to a full book instead of a voicemail box. It also takes load off the people on the floor. Tableo's own guidance to restaurants is blunt about it. When guests can see availability and book without you, the number of calls drops and your team gets that time back for the room. The phone still rings for the things that need a human, like a large party or a special request, but the routine two-top for Thursday handles itself. > Every call your host does not have to answer is a guest at the door who gets seated faster. Fewer calls is not only about saving minutes. It is about fewer mistakes, a calmer host stand, and a guest who feels looked after the second they walk in instead of waiting while someone hunts through a paper diary. #### Why the floor plan matters A booking is only useful if it lands somewhere real. This is where a visual floor plan earns its keep. Instead of a list of times, you build a picture of your actual room. You place tables, size each one by how many seats it holds, add the chairs, and drop in the bits that shape the space, like a bar, a window, or a service station. When a party of two books, it goes to a two-top, not the six-seater you were saving for a big group. When a party of six books, you can see at a glance whether you have a table that fits, or whether you need to join two. You stop selling seats you do not have, and you stop wasting the ones you do. RestaurantsTables, which reviews floor-plan tools, makes the same point: a visual layout helps you match the right party to the right table and spot where tables sit empty or where the room gets jammed. A good floor plan gives you a few practical wins: - Right table, right party. Small groups stop eating into large-table capacity. - Fewer overbooks. You can only seat what the room can actually hold. - A clearer rush. The host sees the whole room as a picture, not a list. - Better turns. You can plan gaps between seatings on purpose instead of by luck. #### No-shows: the quiet leak Empty booked tables are the most frustrating loss in the business. You said no to a walk-in to hold that table, and nobody came. OpenTable's reporting on no-shows shows just how real this is, with skipped reservations running into double digits in many markets and a large share of diners admitting they have failed to show up at least once in the past year. On a busy night, even a couple of no-shows can be the difference between a good service and a flat one. Online booking helps here too, because it gives you the contact details to remind people. A confirmation when they book and a reminder the day before give the guest an easy chance to cancel and free the table, instead of just not turning up. For higher-risk bookings, a card hold raises the stakes a little. OpenTable found that guests who book with a credit card hold are up to 16% less likely to no-show and 15% less likely to cancel late than guests with no policy at all. People do not like leaving a deposit on the table, so they show up or they cancel in time. None of this needs to feel heavy. Most bookings need nothing more than a friendly reminder. A card hold is a tool you keep for the nights and the party sizes where a missed table really hurts. #### How Bookatu puts it together Bookatu gives restaurants the two pieces in one place. You design your room with a visual floor-plan editor, placing tables sized by seats, adding chairs and decor so the layout matches the real space. Guests book a table online through your own storefront, which you can brand with your colours and run in dark mode if that suits your look. The booking lands on a real table on your plan, so your host sees the night as a picture of the room. Guests do not need an account or a password. They confirm and manage bookings through a passwordless magic link, which keeps the step short and the drop-off low. And because Bookatu charges 0% booking commission, you are not handing over a slice of every cover. Payments run through Stripe Connect straight into your own bank account, under your own business, so you reconcile your own takings and your own taxes. The goal is simple. Take the routine bookings off the phone, put every reservation on a real table, and use reminders so the tables you booked actually fill. That is a quieter host stand, fewer empty covers, and a few more turns on the nights that count. #### Sources - Reduce restaurant phone calls. Push for online bookings! (Tableo): https://tableo.com/restaurant-tips/reduce-phone-calls/ - 2025 Reservation Data: 65% Of Diners Go Directly To A Restaurant's Website (Toast): https://pos.toasttab.com/blog/data/restaurant-wait-times-and-reservations-data - 3 Proven Payment Strategies to Help Reduce No-Shows and Cancellations (OpenTable): https://www.opentable.com/restaurant-solutions/resources/3-proven-payment-strategies-reduce-no-shows/ - Improve No-Show Numbers: What Restaurants Need to Know (OpenTable): https://www.opentable.com/restaurant-solutions/resources/no-show-diners-numbers/ - Restaurant Floor Plan Software: Design Your Layout for Profit (RestaurantsTables): https://restaurantstables.com/blog/restaurant-floor-plan-software.html ### Booking Software for Barbershops: Keep 100% of Every Cut A plain guide to booking software for barbershops: your own branded booking page, deposits that stop no-shows, payouts straight to your bank, and 0% commission. The Bookatu team · 2026-06-22 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-barbershops · markdown: https://bookatu.com/blog/booking-software-for-barbershops.md > **The short version** > > - Good barbershop booking software gives you a branded booking page, every barber's day in one calendar, and reminders that send themselves. > - Deposits and card holds protect the Saturday slots you can't afford to lose, and the money lands in your bank, not a platform's. > - Bookatu takes 0% commission. A busy week is just a good week, and you keep 100% of every booking. > - Your client list stays yours. No marketplace in the middle, and you pay by active clients, not by the chair. Most barbershop owners don't want software. They want a full chair, fewer gaps on a Saturday, and to stop playing phone tag halfway through a fade. The right booking system does that quietly in the background. The wrong one takes a slice of every cut, buries your clients in a marketplace, and charges you more every time you put another barber on. So before you sign up for anything, here's what actually matters for a shop. #### What booking software should do for a barbershop A barbershop runs differently from a one-room studio. You've got several chairs, walk-ins mixed with regulars, and one good Saturday that pays for a quiet Tuesday. Your software has to move with that, not fight it. At its core, it should let a client book the right barber for the right service in a few taps, any time of day, without ringing the shop. It should keep every barber's day in one calendar so nobody double-books the chair. And it should send the reminders, ask for the reviews, and nudge regulars to rebook without you thinking about it. - A booking page clients can use at 11pm, which is when a lot of appointments actually get made. - Per-barber services and availability, so a skin fade goes to the right chair and the right block of time. - Reminders by text and email that go out on their own before every appointment. - A smart waitlist that fills a cancelled Saturday slot from people who wanted it. - Reviews collected after a visit, so your Google profile keeps growing. #### Your own booking page, at your own link This is the part marketplaces quietly take from you. With Bookatu, your shop gets its own branded booking site at its own link, showing your name, your colours, your barbers and your real availability. That link goes in your Instagram bio, on your Google profile, on a QR code in the window, and in every DM reply your barbers send. Clients book you, not a directory full of every other shop in town. That matters more than it sounds. On a marketplace, the app owns the relationship, and it can show your regular three competitors on the way to your name. On your own page, the only shop they see is yours. Your team's calendars stay in sync too, with two-way Google Calendar sync, so a barber's personal diary and the shop's bookings never collide. #### Stopping the no-shows that hurt most Every barber knows the maths of an empty chair. A no-show on a slow afternoon stings. A no-show in a fully booked Saturday block is money you'll never get back, because someone else would have happily taken that slot. The fix isn't nagging people. It's two simple defences working together. First, reminders. A friendly text the day before catches the honest forgetters, and that's most of them. Second, for the slots that really cost you, a deposit or a card on file. When a client puts a small deposit down to book a Saturday cut, they tend to show, and the deposit comes off the bill. If they vanish without notice, your cancellation policy covers the gap instead of you eating it. > A reminder catches the forgetful. A deposit protects the slots you can't afford to lose. With Bookatu you connect your own Stripe account, so those deposits land in your bank, not in a platform wallet you have to wait to cash out. Bookatu never touches your booking money. It just runs the booking. #### Why 0% commission changes the maths Plenty of booking apps look cheap until you read how they actually make money. Some take a slice of every new client, some take a percentage of every booking, and some charge you per chair, so growing your team quietly grows your bill. For a busy shop, those little cuts add up to real money by the end of the year. Bookatu takes 0% commission. You keep 100% of every booking, whether it's a quick trim or a full cut-and-beard. You pay by active clients, meaning people you've actually seen in the last 90 days, never by the chair. Add a second barber, a third, an apprentice on Saturdays, and your software bill doesn't jump. It's free for the first 60 days with no card needed, then plans start at $9 a month. #### The features that turn a one-off into a regular Getting a new client through the door once is the hard part. Bringing them back is where a shop actually grows, and good software does that work for you. Every Bookatu plan includes the tools that bring clients back, and only a few optional add-ons cost extra. - Memberships and packages, so the client who comes in every two weeks pays up front and keeps coming back to you. - Loyalty points and referrals, because a happy regular with a mate who needs a cut is your cheapest marketing. - Gift cards, which turn into walk-in revenue around Christmas and Father's Day. - Win-backs that quietly message the regular who hasn't been in for a while. - Promo codes and a newsletter to fill a slow week, without discounting your whole book. None of this needs you to remember it. You set it up once, and it runs while you're heads-down on a fade. #### Choosing software you won't regret When you weigh up options, look past the homepage and ask three plain questions. Does the money come to my bank, or theirs? Do I own my client list, or do they? And does my bill grow when I grow? If a tool answers those the right way, the rest is detail. Bookatu was built for shops that want to stay independent: your own booking page, your own Stripe payouts, your own client list, and no cut taken from a single booking. You can have your page live and taking bookings the same day, try it free for 60 days, and watch how a fuller chair feels with the no-shows handled for you. The next busy Saturday is the one worth setting up for. ### Get paid into your own bank account: how 0% commission keeps the money yours Booking marketplaces can take a cut of every appointment and sit on your cash for days. Here is how 0% commission and Stripe Connect put the money in your own bank account, in your own name, and clean for tax time. The Bookatu team · 2026-06-21 · Recurring revenue · https://bookatu.com/en-nz/blog/paid-into-your-own-bank-account-0-commission-stripe-connect · markdown: https://bookatu.com/blog/paid-into-your-own-bank-account-0-commission-stripe-connect.md > **The short version** > > - Many booking marketplaces take a slice of each booking and hold the money for days before they pay you. > - Bookatu charges 0% booking commission. Your clients pay you, not a middleman. > - Payments land in your own bank account through Stripe Connect, so the cash is yours from the start. > - Because the account is in your name, your takings are already clean and easy to reconcile at tax time. > - A flat subscription means your costs do not climb just because you get busier. When you run a salon, a studio, a clinic or a small restaurant, you watch every pound and every dollar. So here is a question worth asking about whatever tool you use to take bookings: when a client pays, where does that money actually go first? With a lot of popular platforms, the honest answer is that it goes to them, not to you. #### The marketplace cut, in plain numbers A booking marketplace makes money by standing between you and your customer and taking a percentage. The headline rates are not small. In beauty, Fresha charges a 20% commission on the first appointment from any new client who finds you through its marketplace, with a minimum fee per client (see the Fresha Help Center). In food, the third-party delivery apps are steeper still. As Rezku's 2026 breakdown shows, DoorDash, Uber Eats and Grubhub commissions typically run from 15% up to 30% per order, and the real cost often lands higher once processing and promotion fees are added. Put that in everyday terms. If a platform skims 20% of a $5,000 month, that is $1,000 gone before you have paid your rent or your staff. The busier you get, the more you hand over. The fee grows exactly when you would rather keep the upside. #### 0% commission means the price is the price Bookatu works the other way around. There is no booking commission. When a client books a haircut, a training session, a table or a photo shoot, the full price is yours. The card processor still charges its standard fee, which every business that takes cards pays, but that is the payment network's cost, not a platform taking a cut of your work. Nobody at Bookatu is sitting in the middle of your sale. Bookatu is one platform with a tailored setup for each kind of business: salon, spa, personal trainer, sports coach, fitness or yoga studio, restaurant and photographer. The wording, the storefront and the tools fit your trade. The pricing model stays the same across all of them: zero commission on bookings. #### The money is yours, and clean for tax time This is the part that matters most for your accounts. Bookatu sends payments straight to your own bank account using Stripe Connect. You set up your own Stripe account, in your own business name, and payouts go to your bank from there. Stripe's documentation on payouts to connected accounts describes exactly this: available funds are paid out to the account holder's own bank, usually one to two business days after a charge settles. Because the money flows through your account and not a shared marketplace pool, your records are simple. Your sales are already in your name. There is no untangling of a platform's combined statement to work out what was really yours. Stripe's own guidance on tax reporting notes that the account holder is responsible for their own tax obligations, which is the point: your income is yours to report, cleanly, the way an independent business should. > If you cannot explain where your money is on any given day, you do not really control your cash flow. Owning the account is the whole game. #### No waiting for a platform to release your cash Holding funds is the other quiet cost of marketplaces. On Airbnb, for example, the platform holds the guest's payment and releases it to the host about 24 hours after check-in, and new hosts can face longer holds before their first payout (see Airbnb's own help article on payout timing). That model protects the marketplace and its buyers, but it means your money sits with someone else while you wait. With money going to your own Stripe account, payouts run on a standard rolling schedule to your bank, typically within a couple of business days. You are not waiting on a third party to decide it is time to let go of your earnings. #### What this looks like in your business - Salon and spa: clients book and pay through your own branded storefront, and the takings reconcile to your account, not a marketplace's. - Personal trainer and coach: sell session packs, for example buy ten and auto-decrement, and chase what you are owed with a simple who-owes-me board where you log cash or bank payments and send reminders. - Restaurant: take online reservations and lay out your room with a visual floor-plan editor, with tables sized by seats, without paying a per-cover fee to a booking app. - Photographer: deliver private, per-client galleries with watermarked previews and paid extra photos, and collect the payment into your own account. Clients reach their portal with a passwordless magic link, so booking and paying stays easy for them while the money stays yours. #### The benefit that compounds A commission is a tax on your success. Every extra booking costs you more. A flat subscription with 0% commission flips that. You grow, your fee stays put, and the extra revenue is yours to keep. Over a year of being fully booked, that gap is not a rounding error. It is the difference between funding your next hire and funding someone else's platform. The simplest test for any booking tool is this: when a customer pays, whose bank account does the money land in first? With Bookatu, the answer is always yours. #### Sources - Fresha Help Center: Marketplace new client fees (20% commission): https://www.fresha.com/help-center/knowledge-base/billing-and-fees/188-marketplace-new-client-fees - Rezku: Third-Party Delivery Fees in 2026 (DoorDash, Uber Eats, Grubhub): https://rezku.com/blog/third-party-delivery-fees-in-2026-what-doordash-uber-eats-grubhub-really-cost-restaurants/ - Airbnb Help Center: When you'll get your payout: https://www.airbnb.com/help/article/425 - Stripe Docs: Payouts to connected accounts: https://docs.stripe.com/connect/payouts-connected-accounts - Stripe Docs: US tax reporting for Connect platforms: https://docs.stripe.com/connect/tax-reporting ### How automated reminders cut no-shows (and win back your evenings) No-shows quietly drain your week. Here is how automated appointment reminders cut them down, what a good reminder actually says, and how to back it up with deposits and a few small habits. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Reduce no-shows · https://bookatu.com/en-nz/blog/automated-reminders-cut-no-shows · markdown: https://bookatu.com/blog/automated-reminders-cut-no-shows.md > **The short version** > > - Most no-shows aren't people ghosting you, they simply forgot. A well-timed nudge fixes that. > - A short SMS + email sequence catches the majority of missed bookings before they cost you the chair. > - Back reminders up with deposits and a waitlist so the gaps that do happen get filled fast. > - Set it up once. It runs quietly in the background while you actually do the work you love. Empty chairs are the most expensive thing in your diary. The good news: automated appointment reminders are the single cheapest fix, and you can have them running before your next coffee goes cold. #### Why clients no-show (and why it's rarely personal) It's tempting to take a no-show to heart. But when you actually ask, the reason is almost always the same: life got loud and the appointment slipped their mind. Someone booked three weeks ago, the day arrived, and nothing reminded them it was today. That's the part worth sitting with. If the problem is forgetting, then the fix isn't a stricter cancellation policy. It's a better memory. And memory is exactly the thing software is good at. > You don't have a no-show problem. You have a reminder gap, and that's a much easier thing to close. #### What a good reminder sequence actually looks like One reminder is fine. A small, well-spaced sequence is better, it gives clients a chance to reschedule early instead of vanishing on the day. The aim isn't to nag; it's to land a gentle nudge at the moment it's genuinely useful. A sequence that works for most salons looks like this: - Booking confirmation, instantly, so the details are saved while they're still thinking about it. - A reminder 48 hours out, early enough to move the appointment without leaving you a hole. - A final nudge the morning of, when the day's actually in front of them. - An easy reply or one-tap confirm, so changing plans is friction-free for them and visible to you. With Bookatu, both the SMS and email versions of this run automatically off the booking, you set the timing once and never touch it again. Clients who need to rebook do it themselves, which is the whole point. #### Reminders catch most people. Here's how to catch the rest. Even a great sequence won't reach everyone, phones die, plans change, some folks ignore everything. So you want a second layer that protects your time when a reminder doesn't land. A few things stack neatly on top of reminders: - Deposits, a small amount up front turns a maybe into a real commitment, especially for new clients and longer services. - No-show shield, if someone misses anyway, a fair fee is handled automatically, so you're not the one chasing money. - Waitlist auto-fill, when a slot opens late, waiting clients are offered it straight away and your gap quietly closes itself. > Reminders shrink the misses. Deposits, a no-show shield and a waitlist make sure the few that slip through don't cost you a thing. #### The quiet win: your evenings back Here's what doesn't show up on a spreadsheet. When your diary is full and reliable, you stop spending your nights texting reminders by hand, hunting for cover bookings, or staring at tomorrow wondering who'll actually turn up. That headspace is the real return. Reliable bookings also make everything downstream easier, memberships and packages give regulars a reason to commit ahead, and win-back messages gently pull lapsed clients back into the chair without you lifting a finger. And when someone messages at 9pm wanting to book? Bookatu's AI receptionist replies with your booking link, so they can pick a time while you're off the clock. #### Setting it up without becoming a full-time texter The mistake is treating reminders as a daily chore. Done right, it's a one-time setup that then looks after itself for every booking you take from here on. A sensible first pass: - Turn on confirmation, a 48-hour reminder, and a same-day nudge across SMS and email. - Add a deposit to the services that hurt most when they go empty. - Switch on the waitlist so cancellations get reoffered automatically. - Leave it for a fortnight, then check how many gaps you're seeing now versus before. Start there. Most owners are surprised how much of the problem disappears from that alone, and you can layer on the no-show shield, memberships and win-back once the basics are humming. Set the reminders up today, and let the system protect your diary while you get back to the part of the job you actually enjoy. ### Deposit and cancellation policies that protect your time A clear deposit and cancellation policy is the quiet rule that keeps your calendar honest. Here is how to write one, word it kindly, and let your booking system do the enforcing. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Reduce no-shows · https://bookatu.com/en-nz/blog/deposit-cancellation-policies-that-work · markdown: https://bookatu.com/blog/deposit-cancellation-policies-that-work.md > **The short version** > > - A deposit and cancellation policy protects the hours you can't sell twice. It's not about punishing clients. > - Deposits turn a casual "I'll probably come" into a real booking. Charge them where the risk is highest, not everywhere. > - A short, clearly worded cancellation window stops most last-minute drop-offs before they happen. > - Automate the deposit, the reminders and the policy text so the system enforces the rules, not you. Your salon deposit and cancellation policy has one job: make sure the time you block out actually gets used. Done well, it's almost invisible to your good clients and quietly weeds out the ones who never meant to show. #### Empty chairs cost more than the missed service When someone doesn't turn up, you don't just lose that appointment. You lose the slot you turned someone else away for, the product you prepped, and the rhythm of your whole day. The maths adds up faster than most owners realise: - A single missed 90-minute colour can wipe out a big chunk of a busy Saturday's profit. - The client you turned away for that slot may book elsewhere and never come back. - Late cancellations often leave gaps too short to refill on the day. > You can't sell the same Tuesday at 2pm twice. Once it's gone, it's gone. #### Take a deposit where the risk is highest You don't need a deposit on every booking. Save them for the appointments that hurt most to lose, so regulars booking a quick trim aren't asked to jump through hoops. - First-time clients who haven't built any history with you yet - Long or high-value services like balayage, extensions or keratin - Peak slots: Friday evenings, Saturday mornings, the lead-up to the holidays - Anyone who has no-showed before With Bookatu you can set deposits to apply automatically to those bookings, taken at the time of booking and counted toward the final bill. The client puts real money down, and you're covered if they vanish. #### Write a window people can actually respect A cancellation window should be long enough for you to refill the slot and short enough to feel fair. Twenty-four to 48 hours suits most salons. Anything longer starts to feel like you don't trust anyone. Keep the wording plain and human. Something like: "Need to change your appointment? No problem, just give us 24 hours' notice. Cancellations inside that window forfeit the deposit." > A policy nobody reads is a policy nobody follows. Then put it where clients actually see it: on the booking page, in the confirmation, and again in the reminder. A policy buried in your terms and conditions does nothing on a Sunday night when someone's deciding whether to bother. #### Let the system enforce it, not you The most uncomfortable part of any policy is being the one who has to enforce it. So don't be. Set the rules once and let your booking tools do the chasing, the holding and the reminding. Bookatu can quietly carry the whole thing for you: - Automated SMS and email reminders, so "I forgot" stops being a reason - Deposits held and the no-show shield applied automatically when someone breaches the policy - Easy self-service rescheduling, so a wobble becomes a new booking instead of an empty chair - Waitlist auto-fill that offers freed-up slots to clients who actually want them That last one matters. A cancellation only really costs you if the slot stays empty. Auto-fill turns a gap back into revenue while you carry on with your day. #### Handle the awkward bits gracefully Life happens, and a flat, robotic policy will cost you good clients. The point isn't to win every argument, it's to protect your time without becoming the salon people dread booking with. Build in a little discretion. A loyal regular with a sick child is not the same as a serial no-show, and treating them the same is how you lose the ones worth keeping. For the genuine no-shows, the no-show shield does the firm part for you, so you stay the good guy. For clients who simply drift away, Bookatu's win-back and retention nudges gently pull them back before they're gone for good. And memberships and packages quietly solve the problem at the root: clients who've prepaid for a course of treatments almost never ghost. If replying to booking messages is eating your evenings, Bookatu's AI receptionist can answer new clients' messages and send your booking link for you. Start small. Pick your two highest-risk booking types, add a deposit and a 24-hour window to those, and let automated reminders take the strain. You can always widen it later. The aim isn't a fortress of rules, it's a calm, full diary where the time you set aside actually gets used. ### Turn one-time clients into regulars with memberships A happy first-timer is still a coin flip to return. Salon memberships turn that coin flip into a routine, and give you predictable income while they do it. Here is how to build one clients actually want. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Recurring revenue · https://bookatu.com/en-nz/blog/one-time-clients-into-regulars-memberships · markdown: https://bookatu.com/blog/one-time-clients-into-regulars-memberships.md > **The short version** > > - A regular is worth a one-time client many times over, a membership locks in the repeat visit before they leave the chair. > - Price it around one go-to service a month, add a small perk, and most clients do the maths in your favour. > - Recurring monthly income smooths out the quiet weeks and funds the rest of the business. > - Let the tech do the chasing, auto-billing, reminders and win-back messages keep members turning up. Most salons spend their budget chasing new faces, then quietly lose half of them after a single visit. Salon memberships flip that around, they turn one great appointment into a monthly habit, and an unpredictable diary into income you can actually plan against. #### Why a happy client still disappears A first-timer can love their colour and still never rebook. Life gets busy, a friend recommends somewhere closer, or they simply forget you exist until their roots start showing. None of that means they were unhappy. It means the default for most clients is to drift. A membership replaces that drift with a standing reason to come back, on a schedule, without you having to remember to chase them. > You rarely lose regulars because they're unhappy. You lose them to a busy life and a full calendar. #### The maths behind a regular A one-time client is a single ticket. A regular is that ticket, every month, plus the add-ons and retail they buy once they trust you. The gap between the two is enormous, and it compounds quietly all year. - A $90 cut once is $90. - The same client on a monthly plan is $1,000+ a year, before retail and upgrades. - Members refer more, because a standing appointment becomes part of their routine, not a decision they make each time. That's the real point of recurring revenue: it makes every quiet Tuesday less frightening, and it turns your best clients into a base you can build on rather than a list you keep re-winning. #### What a salon membership actually looks like Forget gym-style lock-ins and small print. The versions that work in beauty are simple and generous, the kind a client can explain to a friend in one sentence. - A service club, one blow-dry, facial or tidy-up a month at a members-only rate. - A prepaid package, buy six sessions, get the seventh free, paid upfront or spread monthly. - A perks tier, priority booking, a standing slot, and a discount on the products they already buy. Pick one to start with. The clearer the promise, the faster people say yes, and the easier it is for you to run. #### Price it so the client does the sums for you The sweet spot sits at roughly the cost of one go-to service a month, with a small perk that tips the decision. The client should glance at it and feel slightly silly saying no. Bookatu handles the billing side so you're not stuck taking payments by hand. Set up memberships and packages once, take a deposit to secure that first booking, and let auto-billing run on the date you choose. > Price it like a no-brainer, then let the system collect quietly in the background. #### Let the booking system do the chasing A membership only pays off if members keep showing up, and that's exactly where most salons run out of hours. The fix is automation, not willpower or a sticky note by the counter. - Automated SMS and email reminders cut the no-shows that quietly kill recurring plans. - The no-show shield and deposits protect the slots members reserve. - Win-back and retention messages nudge a lapsing member before they think about cancelling. - Waitlist auto-fill drops a keen client into any gap a member leaves behind. Members don't have to message you to move a visit. The link in their confirmation email lets them move it themselves, within the rules you set, so nobody waits for a reply while you're mid-appointment. #### A simple plan to launch this month You don't need a campaign or a clever name. Start with the clients who already love you, they'll say yes fastest and tell their friends for free. - Offer it at the chair to your top 20 regulars first. - Keep it to one tier, confusion kills sign-ups. - Switch on reminders and auto-billing from day one so nothing slips. Memberships aren't about squeezing anyone. They give the people who already like you an easy way to stay, and they give you a diary you can count on. Pick one simple plan, offer it at the next appointment, and let Bookatu handle the billing and the chasing from there. ### Packages vs memberships: which grows your revenue? Both bring cash in upfront and pull clients back, but they grow your revenue in different ways. Here is how to read packages vs memberships and pick the one that lifts your takings. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Recurring revenue · https://bookatu.com/en-nz/blog/packages-vs-memberships-grow-revenue · markdown: https://bookatu.com/blog/packages-vs-memberships-grow-revenue.md > **The short version** > > - Packages sell a fixed number of sessions upfront, brilliant for a cash injection and locking in first-timers. > - Memberships charge a recurring fee, brilliant for predictable monthly income and everyday loyalty. > - Most thriving salons run both, matched to different kinds of client. > - Either way, the revenue only sticks if people keep rebooking, so automate the follow-up. When you're deciding how to grow steady income, the packages vs memberships question comes up fast. They sound similar, but they solve different problems, and picking the right one (or both) changes how much you earn and how predictable it feels. #### What's the actual difference? A package is a bundle of sessions paid for in one go, say six facials for the price of five. The client owns those sessions and books them whenever suits. A membership is an ongoing subscription: a set fee every month in exchange for a service, a discount, or a perk. The easiest way to feel the gap is to look at how the money behaves: - Packages = one bigger payment now, used up over time. - Memberships = smaller payments forever, until someone cancels. - Packages reward commitment to a treatment plan. - Memberships reward turning up regularly and being part of the club. > Packages give you a cash spike. Memberships give you a heartbeat. #### When packages win Packages shine for results-driven services where a client needs a course, not a one-off. Think a run of laser sessions, a six-week skin plan, or a block of personal-training appointments. The client is already thinking in multiples, so bundling feels natural. They're also your best tool for a quiet month. Sell a limited package deal and you pull future revenue into this week, useful when you need cash now rather than in ninety days. On Bookatu you can build a package, set how many sessions it includes, and let clients redeem them at booking without any mental maths from your front desk. The catch: packages can sit unused. A client buys ten, does three, and drifts. That's lost rebooking and an awkward refund conversation waiting to happen, which is exactly where good reminders earn their keep. #### When memberships win Memberships are the move when you want income you can forecast. A monthly fee, for a recurring blow-dry, a maintenance facial, or a members-only discount, turns one-off visitors into regulars who've already decided to come back. They suit habit-based services more than course-based ones. The value isn't a finish line; it's the routine. Members visit more often, spend more on add-ons while they're in the chair, and refer friends because they feel like insiders. - Predictable revenue you can plan staffing and stock around. - Higher lifetime value, members stay far longer than one-off clients. - Built-in loyalty, so you're not constantly chasing new bookings. - A natural home for perks: priority slots, members' pricing, a free monthly extra. Bookatu handles the recurring side for you, so the fee collects on schedule and the booking perks apply automatically, no spreadsheet, no remembering who's a member at checkout. #### The hybrid play most salons miss This isn't really an either/or. The strongest businesses use packages to win and prove value, then convert those happy clients onto a membership for the long haul. Picture it: a new client buys an intro package of three treatments. By session three they've seen results and trust you. That's the moment to offer a membership that keeps the routine going at a friendly rate. The package did the convincing; the membership does the retaining. > Sell the package to start the relationship. Sell the membership to keep it. #### Make the revenue actually stick Neither model pays off if clients quietly fall away. The real growth lever is keeping the chair full and the follow-through tight, and that's mostly automation, not willpower. A few things worth switching on: - Automated SMS and email reminders so package sessions get used and members rebook before they lapse. - Deposits and the no-show shield to protect the slots people have already paid for. - Win-back messages that nudge a member who's gone quiet before they cancel. - Waitlist auto-fill so a cancelled membership slot gets snapped up by someone else, not lost. - Each client's own account on your booking page, which shows how many sessions they have left, so they don't have to ask your team. These quietly defend the revenue you've already earned. A package with unused sessions and a member who forgot to rebook are the same problem, a gap in follow-up, and the same automations close both. #### So which should you choose? If you need cash and your services come in courses, start with packages. If you want predictable monthly income and your services are routine, start with memberships. If you want to grow properly, do both, and let your booking system run the reminders, deposits and rebookings so the money you sign up today is still there next quarter. ### How an AI receptionist answers new clients while you work You cannot answer every message while your hands are full. An AI receptionist for salons answers the common questions for you and sends your booking link, even after hours. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Grow your business · https://bookatu.com/en-nz/blog/ai-receptionist-books-while-you-work · markdown: https://bookatu.com/blog/ai-receptionist-books-while-you-work.md > **The short version** > > - An AI receptionist replies to new clients' messages at any hour and sends your booking link, so a question that comes in while you are busy can still turn into a booking. > - A message that arrives while you're mid-service can sit unanswered until you're free, and that's the gap this fills. > - Pair it with deposits, reminders and a no-show shield and you protect the revenue it brings in. > - It won't replace your front desk's warmth, it covers the hours and moments a human can't. An AI receptionist for salons is software that replies to your clients' messages for you. On Bookatu it answers a new client with your real services, prices and hours and sends your booking link. Anything tricky goes to a person. Think of it as a calm front-desk colleague who never goes on lunch. #### The booking you never knew you lost Here's the quiet problem: the calls and messages you miss are the ones that come in while you're already with a client. Your hands are in someone's hair or holding a wax strip, you physically can't answer. So the phone rings out. The caller doesn't leave a message. They tap the next salon on the list, and you never find out it happened. Every one of those is real money that walked straight past your chair. > A missed call isn't a missed call. It's a booking that went to the salon down the road. An AI receptionist closes that gap for messages. While you finish the service, it answers from your real services, prices and hours and sends your booking link, so the client can pick a free time straight away instead of moving on. #### What it actually does all day "AI receptionist" sounds futuristic, but the day-to-day job is wonderfully ordinary. It answers the repetitive front-desk questions that keep interrupting your shift. - Answers "are you open Sunday?" and "how much is a full set?" instantly, day or night - Sends your booking link, where the client picks a free time from your real calendar - Lists your services and prices when someone asks what you offer - Keeps the conversation in your inbox so nobody falls through the cracks - Hands the tricky or sensitive messages to a human instead of guessing The point isn't to sound like a robot reading a script. It's to take the predictable questions off your plate so you and your team can focus on the people actually in the room. #### It works best as part of a system A booking that ends in a no-show still loses you money. The booking is step one, keeping it is what matters. That's why the receptionist shines when it sits inside the rest of your tools rather than off on its own. On Bookatu, the receptionist sends your booking link, the client books, and the rest of the machine takes over. Automated SMS and email reminders nudge the client before they arrive. A deposit can be taken at the point of booking, so the slot has skin in the game. And the no-show shield gives you a clear, consent-based way to recover the loss when someone simply doesn't turn up. - Deposits make casual cancellations far less likely - Reminders cut the "oh, I completely forgot" no-shows - No-show shield protects you when a slot is wasted anyway - Waitlist auto-fill quietly offers any freed-up gap to the next client in line > Booking the appointment is easy. Keeping the chair full is the real skill, so let the system do both. #### It quietly grows your regulars, too A good receptionist doesn't just take orders, it brings people back. On Bookatu the receptionist sticks to replying, and the gentle follow-up work most of us never find time for runs on its own from your settings and client history. When a regular hasn't been in for a while, win-back and retention messages can reach out before they drift to someone else. If you sell memberships or packages, clients can buy them from your booking site, so a regular can pick the option that suits them instead of always defaulting to a single visit. Small nudges, repeated across your client list, can add up to a fuller book without you lifting a finger. #### What it won't do (and shouldn't) Let's be honest about the limits. An AI receptionist is brilliant at answering the same questions at any hour. It is not a replacement for the human warmth that makes someone choose your salon in the first place. It won't read the mood of a nervous first-timer the way your stylist does. It won't handle a delicate complaint with a real apology. The good news is it doesn't have to, set it up to pass those moments to a person, and you get the best of both. - Best at: after-hours questions, prices and hours, sending your booking link - Hand to a human: complaints, complex consultations, anything that needs judgement - Keep an eye on: your services, prices and hours, so its answers stay right #### How to start without the overwhelm You don't need to flip everything on at once. The smoothest way in is to let the AI cover the hours you genuinely can't, evenings, weekends, the middle of a busy treatment. Begin with after-hours message handling. Once you trust it, switch on reminders and deposits so the bookings that come in through your link actually stick. Then layer in win-back messages for lapsed clients. Each step pays for the next. Give it a fortnight and check your numbers: how many bookings came in outside opening hours, and how many no-shows you dodged. That's the receptionist earning its keep, sending clients to your booking page while your hands are full and your door is locked. Start small, watch the calendar fill, and add the next piece when you're ready. ### Get found on Google: local SEO for salons and studios A practical guide to local SEO for salons and studios, covering your Google Business Profile, reviews and online booking, so nearby clients find you and book before they call anyone else. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Grow your business · https://bookatu.com/en-nz/blog/local-seo-for-salons-get-found-on-google · markdown: https://bookatu.com/blog/local-seo-for-salons-get-found-on-google.md > **The short version** > > - Most new clients find you on Google Maps, not your website, so your Google Business Profile is your real homepage. > - Recent reviews, accurate hours and good photos lift your local ranking faster than almost anything else. > - Put booking one tap away from the search result, or you'll lose people who were ready to commit. > - A few small habits each week beat one big push, consistency is what Google rewards. Local SEO for salons isn't about gaming an algorithm. It's about being the obvious choice when someone two suburbs over types 'balayage near me' at 9pm, and can book you before they change their mind. #### Start with your Google Business Profile When people look for a salon, most never reach a website. They search, glance at the map, and pick from the three businesses Google shows at the top. That little box, the 'map pack', is where the bookings live. So your Google Business Profile is the single highest-leverage thing you own. Claim it, verify it, and fill in every field. Half-finished profiles get quietly skipped. - Your exact business name, address and phone number - Primary category (e.g. 'Hair salon') plus a few relevant secondary ones - Opening hours, including public holidays - A booking link that goes straight to your calendar - 15-20 real photos: your space, your team, your best work > Your Google Business Profile is the homepage you didn't know you had. #### Reviews are your ranking engine Nothing moves you up the local rankings like a steady stream of recent, genuine reviews. Google reads them as proof you're real, active and worth recommending. The trick is timing. Ask when a client is happiest, right after they've seen the finished result in the mirror, not three days later in an email they'll ignore. And reply to every review, good or awkward. A calm, kind response to a one-star says more to the next reader than the complaint itself. > The salon with 200 recent reviews beats the one with a prettier website nearly every time. #### Get the boring details exactly right Google trusts consistency. If your name, address and phone number differ across your website, Instagram and old directory listings, it gets confused, and confusion costs you rankings. Pick one exact format and use it everywhere: same spelling, same suite number, same phone. Then keep it honest as things change. - Match your details across Google, your site, Facebook and Instagram - List every service by its real name, those are the words people search - Keep hours current; wrong hours lead to a wasted trip and a bad review - Mention your suburb and nearby areas in your description, naturally #### Use the words your clients actually type People don't search 'premium hair artistry'. They search 'gel nails Ponsonby' or 'men's fade near me'. Local SEO for salons works when your profile and website speak their language, not the language on your price list. Give each main service its own simple page, and refer to your neighbourhood the way locals do. Natural beats stuffed every time, write for a human and Google tends to follow. #### Turn the click into a booking Getting found is only half the job. The other half is not losing the person the second they land on you. A client ready to book at 9pm won't wait for you to call back in the morning. So make booking immediate, then protect the calendar once it's full. This is where Bookatu does the quiet work behind the scenes: - A booking link straight from your Google profile, so 'found you' becomes 'booked you' in one tap - Automated SMS and email reminders that cut no-shows without you lifting a finger - Deposits and a no-show shield, so last-minute drop-offs stop costing you money - An AI receptionist that answers questions after hours and sends your booking link - Waitlist auto-fill that quietly books someone into every cancellation Memberships and packages keep your best clients coming back, and automated win-back messages nudge the ones who've drifted. That way the traffic you earned on Google doesn't leak away the moment a gap opens up. #### Small habits beat big pushes Local SEO rewards being alive. A profile that hasn't changed in a year looks dormant; one with fresh photos and recent reviews looks busy, and busy attracts more bookings. Fifteen minutes a week is plenty. - Post a photo or update once a week - Ask two or three happy clients for a review - Reply to new reviews within a day or two - Check your hours before every long weekend You don't need to master SEO. You need a complete Google profile, a habit of collecting reviews, and a booking link that turns a search into a confirmed appointment. Do those three things consistently and you'll be the salon your neighbourhood finds first. ### Win back lapsed clients automatically Lapsed clients are recurring revenue that paused, not sales you lost. Here is how to win them back automatically and turn a one-off return into a steady rhythm again. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Recurring revenue · https://bookatu.com/en-nz/blog/win-back-lapsed-clients-automatically · markdown: https://bookatu.com/blog/win-back-lapsed-clients-automatically.md > **The short version** > > - A lapsed client is far cheaper to win back than a brand-new one, they already know and trust you. > - Define "lapsed" by the rhythm of each service (a 6-week colour client is different from a twice-a-year facial). > - Set up one automated win-back message that fires on its own, then leave it running. > - Pair it with deposits, reminders and memberships so the clients you win back actually stick. Every salon has a quiet leak: regulars who slowly stop booking and never officially leave. The good news is you can win back lapsed clients without manually trawling your client list every month, the right reminder, sent at the right moment, does the chasing for you. #### Why lapsed clients are your easiest revenue Finding a new client is expensive. You're paying for ads, posting on socials, and competing on price. A lapsed client costs you almost nothing, they've sat in your chair, they like your work, and they already have a reason to come back. Most of them didn't leave because they were unhappy. Life got busy, they forgot to rebook, and the gap quietly stretched from six weeks to six months. A small nudge is often all it takes. > A lapsed regular isn't a lost client. They're a booking you haven't asked for yet. #### Decide what "lapsed" actually means for you Before you automate anything, get specific. "Lapsed" isn't one number, it depends on the natural rhythm of each service you offer. - Root colour or a tight fade: every 4-6 weeks, so flag at 8 weeks. - Cut and finish: every 6-8 weeks, flag around 12. - Facials, massage or brows: every 4-8 weeks, flag at 10-12. - Seasonal treatments or big colour changes: every few months, give these a longer leash. Set the trigger just past a client's normal cycle, not months later. The earlier you reach out, the warmer the relationship still is and the easier the rebook. #### Write a message that sounds like you The fastest way to get ignored is to sound like a marketing blast. Keep it short, personal and human, the kind of text you'd actually send a regular you'd missed. Lead with warmth, not a hard sell. "Hi Mia, it's been a while, we'd love to see you. Want me to hold your usual Thursday slot?" beats any 20%-off banner. A gentle offer can help the fence-sitters, but the personal touch is what reopens the door. - Use their first name and reference their usual service. - Give them a one-tap way to rebook, not a phone number to ring. - Keep it to two or three lines, this is a nudge, not a newsletter. - Add a small incentive only if you need it (a complimentary add-on works better than slashing your price). #### Let Bookatu do the chasing This is the part you should never do by hand. Bookatu's win-back and retention tools watch for clients who've drifted past their usual cycle and send your message automatically, by SMS or email, on the schedule you set. You write it once. From then on it runs in the background, quietly bringing people back while you're busy with the clients already in your chair. > Set it up on a quiet Tuesday afternoon, then let it earn for you every week after. #### Make the win-back actually stick Bringing someone back once is only half the job. The goal is to turn a one-off return into a regular rhythm again, so the same client never lapses twice. - Automated SMS and email reminders before every appointment, so "I forgot" stops being a reason they drift. - Deposits and the no-show shield to protect the slots your win-backs fill, so a returning client booking doesn't go to waste. - Memberships and packages to give your best clients a reason to commit to the next few visits up front. - Waitlist auto-fill, so when a returning client cancels, the gap is filled instead of going empty. - An AI receptionist that answers new messages after hours and sends your booking link, so a returning client can book straight away. Layered together, these mean a won-back client lands on a smoother experience than the one they left, reminders that respect their time, easy rebooking, and a membership that makes coming back the default. #### Start small, then leave it running You don't need a grand campaign. Pick your single biggest service, set a sensible lapsed window, write one warm message, and switch on the automation. Check back in a month to see who came back, then tune the timing and wording from there. The whole point is that it works without you. Spend an hour setting it up properly, and winning back lapsed clients becomes something that happens quietly in the background, week after week, with zero chasing on your part. ### The complete guide to online booking for solo beauty pros Working solo means you are the booker, the therapist and the accounts team at once. Here is how online booking for solo beauticians takes the admin off your plate, fills your week, and keeps clients coming back. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Grow your business · https://bookatu.com/en-nz/blog/online-booking-guide-solo-beauticians · markdown: https://bookatu.com/blog/online-booking-guide-solo-beauticians.md > **The short version** > > - Online booking for solo beauticians means clients book themselves, 24/7, without a single back-and-forth DM. > - Deposits and a no-show shield protect the income you can't afford to lose when it's just you. > - Automated SMS and email reminders cut no-shows without you lifting a finger. > - Pick a tool with 0% commission so every booking stays fully yours. If you run the whole show on your own, online booking for solo beauticians isn't a nice-to-have, it's the difference between chasing replies at 9pm and waking up to a full day already booked. Here's how to set it up so it actually saves you time. #### Why DMs and a paper diary stop working When you're a one-person business, every minute spent typing "hi lovely, I've got 2pm or 4pm Thursday?" is a minute you're not earning. And every message you don't reply to fast enough is a client who books someone else. A proper booking page does that conversation for you. Clients see your real availability, pick a slot, and pay or leave a deposit, while you're with a client, asleep, or off the clock. - No double-bookings, because your calendar updates the second someone books. - No "are you free Saturday?" at midnight, they just see what's open. - No mental load remembering who you still owe a reply to. > The best booking system is the one that lets clients book without ever needing you to answer. #### What to look for in a booking tool Plenty of tools can show a calendar. The ones worth your time protect your income and run quietly in the background. Solo means there's no front desk to catch the gaps, so the software has to. Before you commit, check it ticks these off: - 0% commission, you keep every dollar, not a cut per booking. - Automated SMS and email reminders so people actually show up. - Deposits at the time of booking to filter out the time-wasters. - A clean booking page that works on a phone, because that's where clients are. - Card-on-file and a no-show policy you can enforce without an awkward chat. If a platform charges you per booking on top of a monthly fee, the maths gets ugly fast as you grow. Flat pricing rewards you for being busy. #### Cut no-shows before they happen A no-show for a salon with ten chairs is annoying. A no-show for you is a hole in your day and your rent. This is where the right setup pays for itself. Bookatu sends reminders automatically, a friendly nudge by SMS and email so the appointment doesn't slip a client's mind. For the repeat offenders, deposits and the no-show shield mean a missed appointment isn't a total loss: you take a card at booking and charge a fair fee if they ghost you. > You shouldn't have to choose between protecting your income and being kind to your clients. Done right, you do both automatically. And when someone does cancel last-minute, waitlist auto-fill quietly offers the slot to the next person in line, so a gap fills itself instead of staring at you all afternoon. #### Turn one-off bookings into regulars Getting the booking is half the job. Getting them back is what builds a stable income when it's just you. The trick is making rebooking effortless and rewarding loyalty. A few features do the heavy lifting here: - Packages, sell a course of treatments up front so clients pre-commit and prepay. - Memberships, predictable monthly income and a reason for clients to keep coming back to you. - Win-back messages, automatically reach out to someone who hasn't booked in a while, before they drift off for good. These run on autopilot. You set them once, and they keep nudging the right clients at the right moment while you're busy doing the actual work. #### Let the admin run itself The dream for any solo pro is to spend your day on treatments, not on your phone. Automation gets you closer than hiring a receptionist ever could, and it doesn't take lunch breaks. Bookatu's AI receptionist can answer the common questions and send your booking link when you're mid-appointment with your hands full, so the client picks a time themselves. Reminders, deposits, waitlist offers and follow-ups all happen without you touching them. The point isn't to feel less personal. It's to free up the time you'd waste on admin so you can be more present with the client actually in your chair. #### Getting started this week You don't need to overhaul everything at once. Start small and let the system earn your trust before you lean on it fully. - List your services with honest durations and prices. - Set your real working hours and buffers between clients. - Switch on reminders and a small deposit for new clients. - Share your booking link in your Instagram bio and reply to enquiries with it. - Once it's flowing, add packages or memberships for your regulars. Set it up over a quiet evening, point your next few enquiries at the link, and let the bookings, and the reminders, deposits and follow-ups, take care of themselves. You'll feel the difference within a week, and so will your no-show rate. ### Reduce no-shows without scaring clients away You can reduce no-shows without making loyal clients feel mistrusted. The trick is to be clear rather than strict, and to put the gentle defences only in front of the bookings that actually carry risk. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Reduce no-shows · https://bookatu.com/en-nz/blog/reduce-no-shows-without-scaring-clients · markdown: https://bookatu.com/blog/reduce-no-shows-without-scaring-clients.md > **The short version** > > - Most no-shows aren't rude clients, they simply forgot. A well-timed reminder catches the majority of them. > - A small deposit signals commitment without making anyone feel mistrusted. > - Make rescheduling effortless. A client who can move their slot in two taps won't go quiet on you. > - Save the firm stuff, fees, card holds, for repeat offenders, not first-timers. You want to reduce no-shows, but you don't want to treat loyal clients like suspects. Good news: the two goals aren't at odds. The right mix of reminders, light-touch deposits and easy rescheduling does most of the work, quietly, in the background, without a single awkward conversation. #### Why clients actually skip Before you tighten the screws, it helps to know what you're up against. The vast majority of no-shows aren't malicious, they're human. People are busy, calendars are messy, and a 9am facial booked three weeks ago is easy to lose track of. When salons dig into the real reasons, the same handful keep coming up: - They genuinely forgot, or wrote down the wrong day. - Something came up and cancelling felt awkward, so they said nothing. - They weren't sure how to reach you outside opening hours. - They booked on impulse and the commitment faded. Notice what's missing from that list: "they don't respect my time." Once you treat no-shows as a friction problem instead of a character flaw, the fixes get a lot friendlier. #### Reminders do most of the heavy lifting If you only change one thing, make it this. Automated SMS and email reminders are the single most effective way to reduce no-shows, and they cost your clients nothing but a glance at their phone. A reminder that lands at the right moment turns a forgotten booking into a kept one. A rough cadence that works well: - A confirmation the moment they book, so the details are saved. - A friendly nudge 24 to 48 hours before, enough notice to rebook if life got in the way. - A short same-day reminder on the morning of the appointment. With Bookatu these go out on their own once you set the timing, so you're never manually texting fifteen people on a Sunday night. And if someone messages with a question after hours, the AI receptionist can answer it and send your booking link while you sleep. > A reminder isn't nagging. It's the difference between "I forgot" and "see you at three." #### Deposits: friendly, not frosty Deposits have a reputation for being cold, but that's usually down to how they're framed. Asked for the right way, a small upfront amount just gives the booking weight, people show up for things they've already put money toward. Keep it proportionate and explain it plainly. A line like "a small deposit secures your slot and comes straight off your bill" reassures far more than it deters. Bookatu lets you take deposits at the point of booking and apply them to the final total automatically, so there's no fiddly refund dance afterwards. A few ways to keep deposits feeling fair: - Reserve them for longer, higher-value or high-demand services rather than every quick trim. - Make the amount modest, enough to mean something, not enough to sting. - Always state that it's credited toward the service, never an extra charge. #### Make cancelling and rescheduling stupidly easy Here's the counter-intuitive bit: the easier you make it to cancel, the fewer no-shows you get. A client who can move their appointment in a couple of taps will do exactly that, instead of going silent because picking up the phone felt like a chore. Every reminder should carry a one-tap link to reschedule. And when someone does free up a slot, Bookatu's waitlist auto-fill can offer it to the next person waiting, so a cancellation becomes a filled chair rather than a gap in your day. > An empty slot you knew about beats a no-show you didn't, every time. #### Save the strong measures for repeat offenders Most clients will never need a firm hand. But there's always a small group who book, ghost, and book again, and that's where stronger tools earn their place. The trick is aiming them at the few, not the many. Bookatu's no-show shield lets you set fair, automatic consequences for people with a track record, a card on file, a no-show fee, or a deposit requirement, without changing a thing for the regulars who always turn up. New clients get the warm welcome; serial no-shows get a gentle bit of accountability. A sensible escalation looks like this: - First no-show: a friendly check-in, no penalty. - Second: a polite heads-up that future bookings may need a deposit. - Repeat pattern: deposit or card-on-file required to book. #### Win the relationship, not the argument The clients who show up reliably are usually the ones who feel invested in you. So the longer game for reducing no-shows is loyalty, not enforcement. People protect the appointments that feel like part of a routine. Memberships and prepaid packages do this naturally, when someone's already paid for six sessions, missing one feels like wasting their own money. And for the clients who drift off entirely, Bookatu's win-back tools can nudge them back with a timely message instead of letting them quietly disappear. Start small: switch on automated reminders this week, add a one-tap reschedule link, and test a modest deposit on your busiest services. Keep the firm measures in your back pocket for the rare repeat offender. You'll cut no-shows and keep the warmth your clients booked you for in the first place. ### 5 automations every small salon should turn on today Five practical salon automations you can switch on this week to cut no-shows, protect your diary, and turn one-off clients into regulars, without adding to your to-do list. The Bookatu team · 2026-06-21 · updated 2026-11-05 · Grow your business · https://bookatu.com/en-nz/blog/automations-every-small-salon-should-turn-on · markdown: https://bookatu.com/blog/automations-every-small-salon-should-turn-on.md > **The short version** > > - Reminders are the single fastest fix for no-shows, switch them on first. > - Deposits plus a no-show shield mean an empty chair still pays you something. > - Waitlist auto-fill quietly rebooks last-minute cancellations while you work. > - Win-back messages bring lapsed regulars back without you lifting a finger. Salon automation isn't about replacing the warm welcome that keeps people coming back, it's about handing the repetitive admin to software so you can stay on the floor. Here are five you can turn on today, roughly in the order they'll pay you back. #### 1. Turn on reminders first If you do only one thing, do this. Automated SMS and email reminders nudge clients a day or two before their appointment, and the drop in no-shows is usually immediate. You set the timing once and Bookatu sends them for you, no more copying numbers into your phone at 9pm. A good reminder does a few small jobs at once. - Confirms the time, date and which stylist they're booked with - Gives a one-tap link to reschedule instead of ghosting you - Goes out automatically, even on your day off That last point matters. The whole reason this is the first automation is that it keeps working when you're elbow-deep in a colour and can't be texting anyone. > A reminder is the cheapest staff member you'll ever hire, it never forgets, and it never sleeps in. #### 2. Make a no-show cost less than nothing Reminders cut no-shows; deposits handle the ones that slip through. Asking for a small deposit at booking filters out the people who were never really coming, and it makes the serious clients feel just as committed as you are. Bookatu's no-show shield goes a step further, if someone books, no-shows and vanishes, you're not left chasing them by hand. Take a card on file, set your policy in plain language, and let the system enforce it consistently for every client, not just the ones you feel brave enough to charge. > A deposit isn't distrust. It's a quiet handshake that says you'll both show up. #### 3. Fill the gaps while you keep working Cancellations happen. The expensive part isn't the cancellation, it's the empty chair nobody refilled. Waitlist auto-fill closes that gap for you. When a slot opens up, Bookatu offers it to people already waiting for that time, and the first to say yes books straight in. You don't have to scroll your texts, ring around, or even notice it happened until the new appointment lands in your day. It quietly turns one of the most frustrating moments in the diary into found income. #### 4. Win back the regulars who drifted Every salon has them, clients who came in like clockwork, then just... stopped. Usually nothing went wrong. Life got busy and rebooking fell off the list. Win-back automation watches for that gap and sends a gentle, friendly nudge at the right moment, so you're not relying on remembering who you haven't seen since autumn. A simple retention flow can lean on a few things. - A "we miss you" message after a client's usual gap has passed - A small incentive to rebook, if that suits your brand - A direct link so they can book in two taps, not ten Bringing back someone who already loves your work is far cheaper than winning a stranger, and far less effort when the message sends itself. #### 5. Let bookings happen while your hands are full You can't reply to messages mid-blow-dry, and a client who hears nothing back may book somewhere else. Bookatu's AI receptionist answers enquiries around the clock and sends your booking link, so a client browsing at 10pm doesn't drift to the salon down the road. Memberships and packages automate the other side of the counter: regular clients pay upfront or monthly, rebook on a rhythm, and your income gets steadier and easier to predict. Set the package once and the renewals, reminders and booking links take care of themselves. Together they cover the two things that eat a small salon's time, answering people and chasing repeat business, without adding a single task to your day. #### Where to start You don't need all five at once. Switch on reminders this week, add deposits and the no-show shield once you see the difference, then layer in waitlist auto-fill, win-back and the AI receptionist as you go. Each one quietly buys back time and protects revenue you're currently losing, and because it's Bookatu, there's no commission skimmed off the top while it does. ### Booking App for Nail Salons: A Practical Guide A practical guide to choosing a booking app for nail salons: deposits that stop no-shows, your own branded link, and keeping 100% of every booking with 0% commission. The Bookatu team · 2026-06-21 · Grow your business · https://bookatu.com/en-nz/blog/booking-app-for-nail-salons · markdown: https://bookatu.com/blog/booking-app-for-nail-salons.md > **The short version** > > - A booking app lets nail clients book a full set, a fill, BIAB or a gel soak-off on your own branded link, while your hands are busy at the table. > - Deposits and card holds quietly stop the no-shows and late cancels that wreck a fully booked Saturday. > - With Bookatu you keep 100% of every booking. There's no commission, and deposits land in your own bank through your own Stripe. > - Reminders, rebooking nudges, loyalty and win-backs run in the background, so your column stays full without you chasing anyone. You can't pause a gel cure to answer the phone. You can't text someone back with acetone on your fingers. So the messages stack up, the missed-call list grows, and the bookings you never saw wander off to the salon two doors down. A booking app for nail salons fixes one simple, expensive problem: you're too busy doing nails to take more bookings. This is a plain guide to what that looks like for a nail tech or a small nail bar. What to look for, what to ignore, and how to set it up so it earns its keep instead of becoming another tab you have to babysit. #### Why nail clients want to book online Think about how your clients actually live. They decide they want their nails done at 10pm on the sofa, phone in hand. If they can tap a link, see Saturday morning is free and lock it in, you've got the booking. If they have to remember to call you tomorrow during your busiest hours, half of them just won't. A good booking app meets them in that moment. They see your real availability, pick their service, and you wake up to a confirmed appointment. No phone tag, no DM that goes cold, no "sorry, I never got back to you". - They book at midnight, on a lunch break, or between meetings, whenever the urge hits - They can see how long a full set or an infill takes, so your day stops being a guess - Regulars rebook in two taps because their details are already saved - You stop losing the quiet clients who'd honestly rather not phone at all > Most nail bookings aren't lost to a competitor. They're lost to a missed call and a client who couldn't be bothered to try again. #### Build the booking around the way nails actually work Nails aren't one service. They're a menu with very different time slots. A polish change is twenty minutes. A full set of sculpted acrylics with art is two hours plus. If your booking app can't tell those apart, you'll either double-book yourself or leave dead gaps in the day. So set each service up with its real duration and price, including the soak-off or removal time you actually spend. Then the app books the right length of chair time on its own, and your day stops falling behind by 11am. - List your services properly: gel, BIAB, acrylic full set, infills, removals, nail art add-ons - Add removal or soak-off as its own timed step so it doesn't quietly eat the next client - Use add-ons for art, length or extra coats instead of one vague "manicure" slot - Block your breaks and admin time so nothing ever books over your lunch With Bookatu you also get your own branded booking site at your own link. It's not a listing in someone's marketplace next to fifty other nail bars. It's your page, your name, your work front and centre. You drop that link in your Instagram bio, on your shopfront, in every reply, and it does the booking for you. #### Deposits protect a fully booked day Here's the maths every nail tech feels in their gut. A two-hour acrylic slot that no-shows on a Saturday isn't a small annoyance. It's the best-paid block of your week gone, and it's far too late to fill. The longer your services run, the more a single no-show hurts. A deposit sorts out most of it. Once a client puts a little money down to hold the slot, the casual "eh, I'll skip it" bookings tend to fade away, because now there's something on the line. You can also keep a card on file and apply a fair charge when someone vanishes with no notice. The part that matters: with Bookatu you connect your own Stripe, so those deposits land in your bank, not ours. Bookatu never touches your booking money and takes no cut of it. The deposit is yours from the second it's paid, and it comes off the final bill at the table. > A deposit isn't you being difficult. It's a long acrylic slot that someone actually intends to turn up for. #### Let the boring follow-up run itself Taking the booking is step one. Keeping the chair full week after week is the real skill, and it's almost all repetitive nudging that you'll never find time to do by hand. This is where a booking app stops being a calendar and starts pulling its weight. Reminders are the obvious win. An automatic text and email before the appointment kills the "oh no, I completely forgot" no-show, which is a lot of them. The quieter wins add up too. Gel and BIAB grow out on a fairly steady schedule, so a gentle rebooking nudge around the three-week mark catches a client right when they're noticing the regrowth. - Reminders go out automatically before every appointment, no spreadsheet needed - Win-back messages reach a regular who's drifted past their usual fill - Loyalty points, packages and prepaid sets of infills pull people back on a rhythm - A smart waitlist offers any freed-up gap to the next client in line, so cancellations often refill themselves Every one of those is included on every Bookatu plan, and there's no per-seat charge, so a solo tech and a six-chair salon get the same core toolkit. Plans are priced by active clients, the people you've actually seen in the last 90 days, not by how many staff you have. #### What to actually look for when you choose one Booking apps blur together until one has burned you. A few things genuinely separate the keepers from the ones you'll be migrating off in six months. - Commission: 0% means you keep the whole booking. A "small" per-booking fee on every set quietly adds up to real money over a year - Your own payments: deposits should hit your own bank through your own Stripe, not sit in someone else's account on a payout delay - Your client list: you should own and be able to message your clients, not rent access to them in a marketplace - Calendar sync: two-way Google Calendar sync means your bookings and your actual life stop colliding - Real cost: per active client beats per seat or per feature, especially as you grow Bookatu was built around exactly those answers: 0% booking commission, your own Stripe and your own bank, your own branded site, two-way Google Calendar sync, and all the core features on every plan. It's free for 60 days with no card needed, then plans start at $9 a month, so you can fill two months of Saturdays before you decide anything. The right app more or less disappears into your day. It fills your column, holds your slots with deposits, reminds your clients and brings the lapsed ones back, while your hands stay where they belong: at the table, doing the work you're actually good at. ### Secure links, not passwords: a friendlier way to share photos and bookings with clients Passwords slow people down and links that live online forever are a quiet risk. Here is a plain-English look at passwordless magic links and links that expire, and why they are safer and friendlier for sharing client galleries and bookings. The Bookatu team · 2026-06-20 · Reduce no-shows · https://bookatu.com/en-nz/blog/secure-magic-links-share-photos-bookings-with-clients · markdown: https://bookatu.com/blog/secure-magic-links-share-photos-bookings-with-clients.md > **The short version** > > - A magic link signs your client in with one tap. There is no password to create, remember, or reset. > - Secure links expire. After a set window they stop working, so an old email cannot be reused forever. > - Public links feel easy but carry hidden risk. Anyone who gets the address can open them, and they often sit online with no end date. > - Most people reuse and forget passwords, which is exactly why a password wall costs you bookings and gallery views. > - In Bookatu, clients reach their portal and private photo galleries through passwordless magic links, and photo share links last 30 days. You finished the shoot. The gallery is ready. Now you just need the client to open it, pick their favourites, and say yes. The last thing you want is for that simple step to stall because someone cannot find a password. This is where the way you share matters more than most people think. #### Why passwords get in the way Passwords are a daily headache for the people you serve. Bitwarden's research found that a large share of people reuse the same password across many accounts, and many simply forget the ones they have. Worse for you as a business, Bitwarden reported that 55% of people have abandoned an account or made a brand new one just to dodge a password reset. Think about what that means for a client trying to view their photos. If the door has a lock they cannot open, some of them will walk away. There is hard money in that friction. A widely cited case study from the scheduling tool Calendly, summarised in Baytech Consulting's review of magic links, found that 67% of people who quit sign-up did so at the password step. After moving to passwordless sign-in, completed registrations rose from 43% to 71%. Those are not Bookatu numbers and your results will vary, but the pattern is clear. Every extra hurdle at the door loses you people. #### What a magic link actually is A magic link is a private, one-time web address sent to your client's email or phone. They tap it and they are in. No password to invent, no reset emails, no sticky note on the fridge. As Descope explains in its plain guide to magic links, the link itself is the proof of who they are, because it was sent to an inbox only they control. For your client the experience is one tap. Behind that tap, the system is doing the careful work so they do not have to. #### How a secure link keeps things safe A good secure link is not just a long web address. It follows a few rules that security teams have agreed on for years. The OWASP Forgot Password guidance, a respected open standard, sets out the same ideas that protect a magic link: - It is random. The link holds a long, randomly generated code that no one can guess. Picture a key cut so precisely that no copy fits the lock. - It expires. The link only works for a set window. OWASP advises that these links should rarely last more than a short period for sign-in, which is why an old email cannot be used to break in months later. - It can be used up. Once the job is done, the link can be retired so it is not a permanent back door. - It is tied to one person. The link is meant for the inbox it was sent to, not for forwarding around a group chat. > Time-limited, single-use links are not a gimmick. They are the same quiet safeguards that sit behind the password reset emails you already trust every day. #### Why public links are riskier than they look Plenty of people share client work with a plain public link from a cloud drive. It feels friendly and fast. The trouble is that a public link has no idea who is on the other end. Anyone who receives it, on purpose or by accident, can open it. Forwarded to a family thread, pasted into a chat, or left in an old email, that link often keeps working long after the project is done. For private portraits, newborn sessions, or anything a client expects to stay theirs, that is a real worry. A secure link with an expiry date closes that gap without making life harder. The client still gets a simple tap to open their gallery. The difference is that the door does not stay propped open forever. #### How this works in Bookatu Bookatu is built around this idea so you do not have to think about it. Your clients reach their portal through passwordless magic links. There is no account password for them to set up or lose, which keeps the path from their inbox to their booking short and clear. For photographers, the same thinking runs through private client galleries. You upload your full-resolution files. Bookatu automatically makes a low-resolution preview at 1080px with your watermark baked in and the photo's hidden location data stripped out, so what your client browses is a safe proof, not your finished art. They pick favourites, get an included free count, and pay for any extras. The full-resolution files unlock only once that set is settled. You share the gallery with a secure link that lasts 30 days, and a delivery board keeps every studio handover in one place. All of it carries your branding and theme, with a dark mode if that suits your look. The link feels like part of your studio, not a generic login screen. #### A friendlier handover, and fewer dropped balls When access is one tap, people actually take the next step. They open the gallery, confirm the booking, and reply. Fewer clients get stuck at a login wall and go quiet, which means fewer missed handovers and fewer half-finished sales sitting in your inbox. You spend less time playing tech support over a forgotten password and more time on the work you were hired for. Secure links are the rare upgrade that is both safer and kinder. Your client gets a smoother, more private experience. You get peace of mind that an old link will not float around the internet forever. That is a better way to hand over photos, and a better way to confirm any booking. #### Sources - OWASP Forgot Password Cheat Sheet (time-limited, single-use tokens): https://cheatsheetseries.owasp.org/cheatsheets/Forgot_Password_Cheat_Sheet.html - Bitwarden: A closer look at password statistics: https://bitwarden.com/blog/a-closer-look-at-password-statistics/ - Baytech Consulting: The Truth About Magic Links (UX, security, growth): https://www.baytechconsulting.com/blog/magic-links-ux-security-and-growth-impacts-for-saas-platforms-2025 - Descope: What are magic links and how do they work: https://www.descope.com/learn/post/magic-links ### Get found by new local clients: how Bookatu's Discover hubs work When someone searches for a service in your town, you want to be on the short list they find. Discover hubs are free pages that group real, bookable businesses by city and by service. The Bookatu team · 2026-06-20 · Grow your business · https://bookatu.com/en-nz/blog/get-found-by-local-clients-discover-hubs · markdown: https://bookatu.com/blog/get-found-by-local-clients-discover-hubs.md Picture someone new to the area who needs a haircut this week. They open their phone and search for a haircut in their town. In that moment they are not looking for your business by name, because they do not know it yet. They are looking for any good business nearby that they can book. The whole game is being on the short list that comes up. Most owners think the only way onto that list is to pay for an ad or rank first on Google. There is another route that costs nothing. Bookatu runs Discover hubs, shared public pages that gather real, bookable businesses by city and by service, so people searching locally can find you even when they have never heard your name. #### What the Discover hubs are A Discover hub is a public page on Bookatu that lists local businesses. There are two kinds. A city hub lives at a clean address like /discover/your-town and lists every Bookatu business in that town. A service hub goes one level deeper, at /discover/your-town/haircuts for example, and lists the businesses in that town that offer that particular service. Every business on a hub links straight to its own Bookatu booking page, where the client can see real availability and book in seconds. The hub is the introduction. Your booking page does the rest. Nobody on these pages is a rival you are bidding against, because there is no paid placement to bid for. #### Why we built them The hubs exist to help your storefront get found by people who do not know you yet. That is the hardest kind of client to reach, and it is exactly the kind a marketplace charges a new-client fee for. Bookatu does it differently. Being listed on a hub is free, there is no commission on the booking, and there is no paid slot that pushes you above or below anyone else. This sits alongside the work your own booking page already does to get found. We covered that in Getting found online: the local SEO and reviews flywheel, which is about reviews and the structured data on your own page. The Discover hubs are a different layer. They are the shared local pages that group everyone together, so a single search for a service in a town can surface a real, bookable business. #### How you get listed Getting on the right hub comes down to one thing: telling Bookatu where you are. You do that under Settings, Region & currency. - Set your City or town accurately. This is the field that groups you into the right city hub, so type the town clients would actually search for. - Set your Region if it helps, which is your wider area or state, like Auckland or Canterbury. - Complete your services, since that is what places you on the matching service hubs. - Keep your profile and reviews current, so you stand out once a searcher is looking at the list. That is the whole setup. Once your City is filled in and your services are listed, your storefront is grouped with the right local results automatically. There is nothing to apply for and no extra fee. #### An honest word on how the pages work We are deliberate about not creating thin or fake pages. A hub only appears when at least one real business is listed for that city or service. There are no empty doorway pages built to chase a search term, because that helps nobody and search engines see through it anyway. Every hub you land on is a page of genuine, bookable businesses. It is also worth being clear about what a listing is not. Being on a Discover hub means you are listed on Bookatu's own discovery network. It is not a paid advertisement, and it is not the same as connecting your own domain. It is also not a promise of a top spot on Google. It is one more free way for nearby clients to find a real business to book. #### How this fits the bigger picture The hubs work best as part of a complete approach to being found. A full, accurate profile and a steady stream of recent reviews help you stand out on the hub and on your own page alike. The same habits that win you new local clients also feed the wider find-a-business network where people search across towns and services. If you want the detail, the Local discovery hubs help article walks through the City and Region fields step by step, the Getting found online help article covers the structured data on your own page, and The Discovery network help article explains how the shared find-a-business network sends clients straight to you with no commission. #### A short checklist to get found - Set your City or town and Region under Settings, Region & currency. - List all your services so you appear on the right service hubs. - Complete your profile with real photos and accurate hours. - Collect reviews steadily after every visit. - Share your booking link everywhere, so direct and discovered clients both land in the right place. None of this is a one-off task, and none of it costs you a booking fee. Fill in where you are, keep your profile fresh, and let the hubs introduce you to the people in your town who are searching right now. You can start free and have your booking page and your listing live the same day. ### Go live in a day: the first-run setup checklist for new owners The hardest part of new software is the first hour. Bookatu shows a short, honest checklist the moment you sign in, so you go from sign-up to a live booking page the same day. The Bookatu team · 2026-06-20 · Grow your business · https://bookatu.com/en-nz/blog/go-live-in-a-day-first-run-checklist · markdown: https://bookatu.com/blog/go-live-in-a-day-first-run-checklist.md The hardest part of any new tool is not learning it. It is the first hour, when the screen is empty and you are not sure what to do first. Bookatu tries to take that worry away. The moment you sign in, your dashboard shows a short setup checklist, so you always know the next step and exactly how far you have to go. The whole point is to get you from sign-up to a live, bookable page the same day. Most owners can work through it in a single sitting. Here is what the checklist covers and why each step is there. #### The six steps to a live booking page The checklist is deliberately short. Six steps, in a sensible order, that take you from an empty account to a page clients can book on. - Review your services and prices, so clients see what you offer and what it costs. - Set your opening hours, so the calendar only shows times you actually work. - Add your team, so bookings land with the right person. - Add your logo, so your page looks like your business and not a blank template. - Connect Stripe to get paid, which switches on deposits and online payments. - Share your booking page, which is the finish line. #### Why the checklist is honest A progress bar is only useful if it tells the truth. Each step on the checklist ticks only when you have really done it, not just because you opened the page. So the bar filling up means something, and a finished checklist genuinely means you are ready to take bookings. There are no day-one false positives quietly telling you that you are set up when you are not. #### The one optional step Five of the six steps are about your page itself. The one optional step is connecting Stripe. You can go live and take bookings without it, but it is what turns on the parts that involve money. Connect Stripe and you can charge deposits, sell gift cards, packages and memberships, and take online payments, all into your own account. Our help article Connecting Stripe for payments walks through it, and it takes only a few minutes. If you are not ready to take payments on day one, leave Stripe for later. Your page still works for free bookings, and you can come back and connect it when you are ready to add deposits. #### Sharing your page is the finish line The last step is the one that actually brings clients in. Once your page is live, put your booking link everywhere people look for you: your Instagram bio, your Google profile, your email signature and a QR code at reception. Our help articles Your booking page and Getting found online cover where to put it for the best effect. If you want a deeper walk-through of each step as you go, the Your first-run setup checklist help article expands on all six. And if you are moving from another tool, our post Leaving Fresha or Booksy shows how to bring your clients across so your new page is busy from the start. #### You can be live today There is no long wait and no setup project that drags on for weeks. Work down the six steps, watch each one tick when it is truly done, and share your link. Most owners are taking bookings the same day they sign up. You can start free and follow the checklist from your very first sign-in. ### Booking Software for Personal Trainers: What Actually Works Pick booking software that fits how trainers really work: recurring slots, card holds against no-shows, packages and memberships in one place, and 100% of every booking in your bank. The Bookatu team · 2026-06-20 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-personal-trainers · markdown: https://bookatu.com/blog/booking-software-for-personal-trainers.md > **The short version** > > - You get your own branded booking page at your own link, so clients book a slot without a single back-and-forth text. > - Deposits and card holds quietly kill the no-shows that eat a one-person training business, and the money lands in your own bank. > - Packages, memberships and client homework all live in one place, so selling a ten-session block is a couple of taps. > - Bookatu takes 0% commission and charges by active clients, not per coach, so you only pay for what you actually use. Most personal trainers didn't get into this to spend their evenings answering "what times have you got free?" on WhatsApp. But that's where a lot of the admin goes. You finish a session, glance at your phone, and there are six messages: three about rescheduling, one from someone who isn't turning up tomorrow but hasn't said so yet. Booking software is meant to take that whole pile off your plate. The trouble is, a lot of it is built for big chains or beauty salons, and it bends awkwardly around how trainers and small studios really work. This guide walks through what booking software for personal trainers should actually do, what to ignore, and where the money quietly leaks out. Whether you train one to one, run small-group sessions, or look after a floor of coaches, the same handful of things decide whether the tool earns its keep. #### What a trainer actually needs from it Your day doesn't look like a hair salon's. Sessions repeat at the same time every week. The same client comes back two or three times a week for months. People buy blocks of sessions rather than single appointments, and a good chunk of your income is recurring, not one-off. Software that fits should make all of that easy instead of fighting it. - Your own booking page at your own link, with your name and colours, not a profile buried in someone else's marketplace. - Recurring slots, so a client can lock in Tuesday and Thursday at 6am without rebooking every week. - Small-group and class bookings with a cap on numbers, for bootcamps and studio sessions. - Card holds or deposits, because a missed 6am one to one is an hour you can't sell again. - Packages and memberships in the same place, so a ten-session block or a monthly plan is a couple of taps. - Two-way calendar sync, so your training diary and your own life never double-book. Bookatu gives every business its own branded booking site, plus calendars for you and your team with two-way Google Calendar sync. So a slot you block out for your own gym session shows as busy on your booking page, and a client's booking lands in your personal calendar straight away. #### Stop no-shows without being the bad guy A no-show hurts a trainer more than almost any other trade. You can't fill a 6am one to one at 5:55am. The hour is just gone. The honest fix isn't nagging people, it's a little skin in the game at the point of booking. When a client puts down a deposit or has a card held against the session, the soft cancellations dry up. People treat a booking they've paid towards very differently from a free one. The bit that matters most is where that money goes. With Bookatu you connect your own Stripe account, so a deposit or a no-show charge lands in your bank, not in some platform's wallet that pays you out whenever it feels like it. Bookatu never touches your booking money. You keep control of refunds too, so when someone genuinely can't make it, you can wave the charge from your own dashboard and keep the goodwill. > A missed 6am session isn't a gap in the diary. It's an hour of your income you can never sell again. #### Sell ahead, not session by session Single sessions are the hardest way to run a training business. Every week you start from zero, hoping people rebook. The trainers and small gyms who sleep well are the ones selling ahead: ten-session packages, monthly memberships, small-group blocks. It smooths your income and it commits the client, which is exactly what gets results. Good for both of you. This is where feature paywalls quietly cost you. Plenty of tools lock memberships, packages or loyalty behind a higher tier, so the things that actually grow your income are the ones you have to pay extra to reach. Every Bookatu plan includes all of these: packages, memberships, gift cards, loyalty points, referrals, promo codes, a smart waitlist, win-backs and marketing newsletters. Only a few optional add-ons cost extra. #### Keep clients on track between sessions The work that keeps a client paying often happens between sessions, not during them. The mobility homework, the food note, the check-in that says you remember them. Your software should help you do that without a separate app and a stack of spreadsheets. Bookatu includes client programs and homework built for trainers, so you can send a plan, track it, and keep someone moving when they're not in front of you. - Assign a client their between-session work straight from their profile. - Use reminders so a 6am session doesn't get slept through. - Send a win-back when a regular goes quiet, before they drift off for good. - Reward loyalty and referrals, since a happy client is your cheapest source of new ones. None of this is about being pushy. It's about staying useful in the gaps, which is what turns a six-week trial into a two-year client. #### What it should cost a small gym Pricing is where a lot of booking software stops making sense. Per-seat pricing punishes you for adding a coach. Commission on every booking quietly skims a slice off each session you sell, and that adds up fast when the same client trains a hundred times a year. For a trade built on repeat business, both models work against you. Bookatu charges 0% commission, so you keep 100% of every booking, and it prices by active clients (anyone you've seen in the last 90 days) rather than per coach. A solo trainer with a tight book pays little. A studio with several coaches but a shared client list isn't punished for the team. It's free for 60 days with no card needed, then plans start at $9 a month, and your client list stays yours. No marketplace renting your own regulars back to you. Strip it back and the job is simple. The right booking software should hand you back the evenings you currently spend on your phone, protect the hours you can't resell, and make selling ahead the easy default rather than the thing you keep meaning to set up. Get those three right and the tool quietly earns its keep, month after month. Once it's running with your own services and your own link, the admin stops being the loudest part of your week, and that's the whole point. ### Booking Software for Massage Therapists: Keep 100% A plain guide to booking software for massage therapists: what actually cuts no-shows, why deposits land in your own bank, and how 0% commission keeps every booking yours. The Bookatu team · 2026-06-19 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-massage-therapists · markdown: https://bookatu.com/blog/booking-software-for-massage-therapists.md > **The short version** > > - Clients book themselves at any hour, the reminders go out on their own, and your calendar stays straight. You stay in the treatment room instead of on the phone. > - Deposits and card holds are the best fix for last-minute cancellations. With Bookatu you connect your own Stripe, so that money lands in your bank, not ours. > - Bookatu charges 0% commission, so you keep 100% of every booking. You keep your client list too. It's yours, not a marketplace's. > - Free for 60 days, no card. Plans start at $9 a month after that, priced by active clients, not per seat. All the core features are on every plan. #### Booking software built for how massage therapists actually work Your hands are busy most of the day. When someone texts to book while you're mid-treatment, you either break your rhythm or you forget until that night, by which point they've gone elsewhere. The admin always seems to land at the worst moment. That's the real job here. Not a pile of features you'll never touch, just a way for clients to see your open slots and book themselves at 11pm without touching your phone. You finish a session, glance at the calendar, and the next hour is already filled. No back and forth, no double bookings, no "sorry, that time just went." With Bookatu you get your own branded booking site at your own link. Drop it in your Instagram bio, on your cards, in your email signature, and clients book straight from it. Your team's calendars stay in sync, with two-way Google Calendar sync, so a session you've blocked on your phone never gets double-booked online. #### No-shows cost you the most, so sort them first A no-show on a 60-minute remedial slot isn't a small thing. That hour can't be resold once it's gone, and it's often the gap between a good week and a flat one. Many therapists find a couple of empty slots a week is where most of their lost income quietly hides. The fix isn't nagging people. It's two simple things working together. Reminders that go out on their own so the appointment doesn't slip a client's mind, and a small deposit or card hold that makes the booking feel real. When someone has put a little down, they show up, and the few who genuinely can't make it tend to let you know in time so you can fill the gap. Here's the part that matters. You connect your own Stripe account, so any deposit lands in your bank, not ours. Bookatu never touches your booking revenue. The card hold protects your time, the money is yours from the start, and you set the policy that suits your practice. > The hour you lose to a no-show is the one hour you can never sell twice. #### What to actually check when you compare options It's easy to get dazzled by a long feature list. For a massage practice, a short list of things that genuinely save you time and money matters far more. Here's what's worth checking before you commit to anything. - Commission. Some platforms quietly take a cut of every booking. Over a year that's real money. Bookatu takes 0%, so you keep the full price of every massage. - Where the money lands. You want deposits paid into your own bank, not held by the platform. With Bookatu you connect your own Stripe, so it's your money from minute one. - Who owns the client list. Marketplaces keep your clients as theirs and rent them back to you. Your regulars are the heart of a massage practice. With Bookatu they belong to you. - Reminders and rebooking included. Automatic reminders, review requests, and gentle win-backs for clients you haven't seen in a while should come standard, not as a paid add-on. They do on every Bookatu plan. - Honest pricing. Per-seat pricing punishes you for growing. Look for pricing based on how many clients you actually see. #### Turn one-time bookings into a steady rhythm of regulars Most clients don't book the next session while they're still on the table, even when they mean to. Life gets in the way and the months drift. A good system keeps that rhythm going without you having to chase anyone by hand. Packages work well for massage. Sell a block of five sessions up front and the client has a reason to come back, while you're paid early for work you'll do over the coming weeks. Memberships suit the clients who come in monthly for maintenance, giving you a base of income you can count on. Bookatu includes packages, memberships, loyalty points, and gift cards on every plan, so you can offer whichever fits without paying extra for it. Then there's the quiet stuff that keeps a practice full. A reminder to a client you haven't seen in three months. A review request after a great session. A smart waitlist that fills a cancellation before you've even noticed it opened up. These run in the background so your calendar stays healthy while your attention stays on the person in front of you. #### Getting set up without losing a working day A lot of therapists put off switching because they dread a fiddly setup, and fair enough. You don't have a spare afternoon to wrestle with software. The good news is a clean booking site doesn't take long to stand up. Your services, your hours, your prices, your link. That's most of it. Bookatu is free for the first 60 days with no card needed, so you can build your site, take a few real bookings, and see whether it fits the way you work before you pay a cent. After that, plans start at $9 a month and you're charged by active clients, meaning people you've actually seen in the last 90 days, never per seat or per service. Quiet months cost you less. Whatever you land on, the test is simple. Does it give you back hours, keep your no-shows down, and let you keep the full value of your work? Sort those three and the admin fades into the background, where it belongs. Your job is the hour on the table. The right tools just make sure that hour is booked, paid for, and yours. ### Booking Software for Lash and Brow Artists: A Plain Guide A plain guide to booking software for lash and brow artists: real service lengths and patch tests, your own branded booking site, deposits that quiet no-shows, and 0% commission. The Bookatu team · 2026-06-18 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-lash-brow-artists · markdown: https://bookatu.com/blog/booking-software-for-lash-brow-artists.md > **The short version** > > - Lash and brow work runs on full sets, scheduled fills and back-to-back chairs. Good booking software protects that rhythm with real service lengths, buffers and patch-test windows. > - Your own branded booking site means clients pick the right service at the right length, with no back-and-forth. > - Deposits and card holds quiet the no-shows, and they land in your bank because you connect your own Stripe. Bookatu takes 0% of your bookings. > - All the core features are on every plan, and you pay by active clients, not per chair. Lash and brow work is precise, quiet and time-boxed. A full set of classic lashes is not a fifteen-minute trim, and a lamination needs its own slot and its own aftercare. So the booking software you pick has to understand your day, not just hand you a calendar. This is a plain guide to what matters for lash and brow artists, and where Bookatu fits. #### What lash and brow artists actually need from booking software Most generic booking tools were built for a barber doing a thirty-minute cut. Your services do not work like that. A new set of volume lashes might run two and a half hours, a fill runs an hour, and a brow lamination needs a patch test before the client sits in your chair. If the software cannot hold those rules, you patch the gaps by hand, and that is where double-bookings and awkward messages creep in. Here is what it has to handle for this trade: - Service lengths that match reality, so a full set blocks the right time and a fill is not squeezed into a quick slot. - Buffer time between clients to clean, prep and reset, without you remembering to add it every time. - Patch-test and aftercare prompts for tints, laminations and new clients, so nobody books a treatment they are not ready for. - Fills on a rhythm, so regulars rebook every two or three weeks instead of you chasing them. - A waitlist that fills last-minute gaps when a fill cancels, because an empty afternoon in this job is expensive. With Bookatu you set each service to its true length and add buffers once. After that, the booking page keeps your day from falling apart while you work. #### Your own booking site, your own brand Your work is visual, and clients chose you for your style. So your booking page should look like yours, not like a directory with ten competitors one tap away. Bookatu gives you your own branded booking site at its own link. Put it in your Instagram bio, on your card, in your story highlights, and clients book straight from there. On a marketplace app, the second a client opens your page they see other lash artists nearby. > Your booking link should grow your name, not someone else's marketplace. It syncs both ways with your Google Calendar too, so a personal appointment you add on your phone blocks that slot. No surprise Saturday booking when you are meant to be at a wedding. #### Deposits and card holds, paid into your bank A no-show on a two-hour full set is not a small loss. That is a slot you could have given to someone on your waitlist, and it is gone. Deposits and card holds are the honest fix: when a client books, they leave a deposit or save a card, and that quietly sorts out who is serious. Most people who miss are not being rude, they just forgot, and a deposit plus a reminder closes that gap. The part owners care about most: with Bookatu you connect your own Stripe account, so deposits land in your bank, not ours. Bookatu never touches your booking money and takes 0% commission. You keep every penny of every appointment, and the deposit on a new set is yours the moment it clears. You set the rules that suit your chair too: a deposit on new clients only, a card hold on full sets, a clear cancellation window. The software holds the line gently, so you are not the bad guy in the DMs. #### Keeping fill clients coming back The real money in lashes and brows is the fill cycle. A client who comes back every two or three weeks is worth far more than a string of one-off sets. The trick is making the rebook effortless and giving regulars a reason to stay. Every Bookatu plan includes the tools for that, with nothing locked behind a higher tier: - Reminders that nudge a client to book their next fill before their set thins out. - Loyalty points and referrals, so a happy client who sends a friend gets looked after. - Packages and memberships, like a block of fills or a monthly plan, that turn casual clients into committed ones. - Gift cards for the friend who wants to treat someone to their first set. - Win-back messages for the regular who quietly drifted off after a few months. - Reviews, so new clients can see your work spoken for before they book. You do not pay extra to switch these on. They are there from day one, and you pick the ones that suit how you work. A solo artist might lean on reminders and reviews. A small studio might add memberships and a waitlist. Same toolbox, your call. #### Pricing that fits a treatment-room business Per-seat pricing punishes you for growing, and commission punishes you for being busy. Neither fits a treatment-room business. Bookatu prices by active clients, meaning someone you have actually seen in the last ninety days. If a client has not been in for a while, you are not paying for them, and you are not charged per chair or per artist either. You start free for sixty days with no card, then plans start at $9 a month. With no booking commission, the more sets you do, the more you keep, and the client list is yours to export, message and keep. Choosing booking software is really choosing how your day feels. The right tool sets your service lengths properly, reminds clients so they show up, protects your time with deposits, and nudges fills to rebook, all while the money goes straight to you. Get those basics right and the calendar starts to look after itself, which frees you up for the work in front of you. ### Booking Software for Spas: A Practical Owner's Guide A plain-language guide to booking software for spas and wellness studios: 0% commission, deposits straight into your own bank, and all the core features on every plan. The Bookatu team · 2026-06-17 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-spas · markdown: https://bookatu.com/blog/booking-software-for-spas.md > **The short version** > > - Good booking software for a spa should run in the background while you stay in the treatment room, not pull you back to the desk. > - Look for your own branded booking site, deposits that go straight into your bank, and a diary that keeps therapists and rooms from clashing. > - Bookatu takes 0% of every booking, charges by active clients instead of per seat, and puts all the core features on every plan. > - It's free for 60 days with no card. Plans start at $9 a month after that. #### What a day spa really needs from booking software A spa diary is busier than most. You're juggling treatment rooms, packages, gift cards someone bought last Christmas, and a therapist who only works Thursdays. The software running all of that should be quiet. You set it up once, and it fills the day while your hands are on a client. The wrong tool does the opposite. It drags you out to the front desk to confirm a time, chase a deposit, or untangle a double-booking. So before you start comparing logos and price tags, get honest about what a wellness business actually needs. - Your own branded booking site on your own link, so clients book you, not a marketplace listing surrounded by your competitors. - Real room and therapist scheduling, so two facials don't land in the same room at the same time. - Deposits and card holds to protect the long, high-value slots that hurt most when they sit empty. - Reminders, reviews, and rebooking that run on their own, without you typing a single message. - Packages, memberships, and gift cards built in, because that's how spas earn between visits. #### Why 0% commission matters more for a spa Spa treatments carry a bigger average ticket than a quick trim. A 90-minute massage, a course of facials, a couples package. When a booking platform skims a slice off each of those, it quietly adds up, and you feel it most on exactly the bookings you worked hardest to win. Bookatu takes 0% booking commission. Every dollar a client pays for a treatment stays with you. We make our money from a flat subscription, not a cut of your work, so a busy month rewards you and not us. Over a year, that's real money that stays in your business. > If a booking tool earns more every time you do, it's quietly your business partner. You never agreed to that. #### Protect your longest, most valuable slots A no-show on a 20-minute slot stings. A no-show on a two-hour body treatment leaves a hole in your whole day, and you can't always fill it at short notice. This is where the right software earns its keep for a spa. With Bookatu you can ask for a deposit or place a card hold when a client books, which is the moment they're most committed. Because you connect your own Stripe account, that money lands in your bank, not ours. Bookatu never touches your booking revenue. On top of that, reminders go out before the appointment on their own, and a smart waitlist offers any gap that does open to someone who's ready to take it. #### The between-visits features spas live on Wellness clients don't always rebook on the spot. The real work is keeping them coming back and giving them easy ways to spend with you in between. Most tools lock these behind a premium tier. With Bookatu, all of these are on every plan, so you never pay more just to reach them. - Memberships and packages, so a course of treatments or a monthly facial becomes steady, predictable income. - Gift cards, the quiet earner that brings new faces in around birthdays and the holidays. - Loyalty points, referrals, and promo codes to reward regulars and turn them into people who bring a friend. - Win-backs that nudge a client you haven't seen in a while, without you having to remember. - Newsletters and client programs to stay in touch and keep your studio on their mind. None of it needs you at a screen. You switch it on once, and it works while you're in the room with someone. #### Pricing built for a seasonal, multi-therapist business Spas grow in waves. You take on a therapist for the busy season, add a room, then quieten down again. Software that charges per seat punishes exactly that. Every person you add costs more, whether they're booked solid or sitting idle. Bookatu charges by active clients, meaning someone you've actually seen in the last 90 days. Add as many therapists and rooms as you like at no extra cost. You only pay for the relationships that are genuinely live. It's free for the first 60 days with no card, then plans start at $9 a month. And the client list stays yours. No marketplace sitting between you and the people you serve, nobody renting you back your own customers. #### Choose well, then get back to the work The best booking software for your spa is the one you stop noticing. It confirms the bookings, takes the deposits into your own account, sends the reminders, fills the gaps, and keeps your regulars close, all while you do the work that made you open the doors. So when you weigh up your options, look past the feature lists and ask one simple thing: does this tool work for me, or do I end up working for it? Set it up once, point your clients at your own link, and let the quiet machinery handle the rest. ### Booking Software for Tattoo Studios: An Owner's Guide A plain-talk guide to booking software for tattoo studios: deposits that hold, a calendar per artist, the stuff around the appointment sorted, and 0% commission so the shop keeps every dollar. The Bookatu team · 2026-06-16 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-tattoo-studios · markdown: https://bookatu.com/blog/booking-software-for-tattoo-studios.md > **The short version** > > - Tattoo work isn't a 30-minute trim. Your booking software has to handle consults, deposits, long sessions and several artists, not one tidy service slot. > - Deposits and card holds are how you stop a no-show eating a whole afternoon. With Bookatu the deposit lands in your own bank, because you connect your own Stripe. > - Every artist gets their own calendar with two-way Google Calendar sync, so guest spots and days off never turn into a double-booking. > - Bookatu takes 0% booking commission and charges by active clients, not per artist. Free for 60 days, then plans from $9 a month. Tattooing doesn't book like a haircut. A piece can be a quick walk-in flash or a six-hour back session split over two sittings. There's a consult, a deposit, reference photos, aftercare, and often three or four artists keeping wildly different hours under one roof. Most general booking tools were never built for any of that, which is why so many shops still run on a paper book, a group chat, and a lot of hope. If you're shopping for booking software for tattoo studios, you already know the pain. Here's what actually matters when you pick one, in plain language, from the floor of the shop rather than a sales deck. #### Deposits that protect a whole afternoon A no-show at a nail bar costs you half an hour. A no-show on a half-day session costs you the afternoon, and you rarely fill it at short notice. That's why deposits aren't a nice extra for a studio. They're the whole thing. Someone who's put money down turns up, and on the rare day they don't, you're not left out of pocket. Good software takes the deposit when the client books, holds it against the appointment, and lets you set your own rules on cancelling and rescheduling. With Bookatu you connect your own Stripe account, so the deposit goes straight to your bank. It never sits in a platform wallet waiting to pay out, and Bookatu never touches your booking money. Prefer to keep the chair friendly? Use a card hold instead of an upfront charge and only bill if someone genuinely ghosts you. > A deposit isn't about distrust. It's the line between a confirmed session and a maybe, and your day is built on confirmed sessions. #### A calendar built for a shop, not one chair Most studios aren't one person. You've got residents, the odd guest spot, an apprentice, maybe a piercer. Everyone keeps their own hours and books their own lengths of work. The fastest route to a furious double-booking is one shared calendar nobody quite trusts. What you want instead is a calendar per artist, each one theirs to manage, with two-way Google Calendar sync so an artist's personal life and their studio diary stay in step. Block a guest week or mark off a convention, and the online booking page stops offering those slots on its own. Bookatu gives every team member their own synced calendar, so the front desk and the artists are looking at the same truth. - Per-artist availability, so a client books the right person, not just any open gap. - Two-way Google Calendar sync, so conventions, guest spots and time off block the diary straight away. - Service lengths that match real work, from a small flash piece to a multi-hour sitting. - A smart waitlist, so when a big session falls through you can offer the gap to someone who's ready to go. #### Your own booking page, on your own link A studio lives or dies on its look. Send clients to a generic marketplace listing parked next to ten other shops and you undo a lot of that work. You want your booking page to feel like an extension of the studio: your name, your style, your link, the one you drop in your Instagram bio and stick in the shop window. Bookatu gives each studio its own branded booking site at its own link. No marketplace skimming your clients, no middleman nudging them towards the shop down the road. The people who book are your clients, and your client list is yours. That counts for more in tattooing than almost any trade, because a loyal client is a decade of work, not a single appointment. #### The stuff around the appointment, sorted The booking is only half of it. A studio runs on reminders so nobody forgets a session they booked two months back, on follow-ups for aftercare and the next sitting on a big piece, and on the slow build of regulars who come back for sleeve after sleeve. Plenty of tools lock that behind a pricier tier. Bookatu puts all of that in every plan, so none of it is held back. - Automatic reminders before each session, so a booking made months ago still shows up. - Review requests after a piece heals, to build the reputation that keeps the chair full. - Win-back nudges for clients who haven't been in for a while. - Gift cards, packages and memberships, handy for clients saving towards a big multi-session piece. - Promo codes and referrals, for flash days, quiet weeks and the word of mouth that runs every good shop. None of it needs you to be a tech person. You set it up once and it ticks along quietly while you're in the chair doing the work you actually care about. #### Pricing that suits how a studio really earns Two things sting studios on most platforms: a commission on every booking, and a charge per artist seat. Both punish you for doing well. The more you book, the more they take. The bigger your team, the more you pay just to keep everyone on the calendar. Bookatu takes 0% booking commission, so you keep 100% of every booking. Pricing goes by active clients, meaning someone you've actually seen in the last 90 days, never per artist. A four-chair shop and a solo artist each pay for the clients they serve, not the number of stools on the floor. It's free for 60 days with no card needed, then plans start at $9 a month, so you can run it through a real week of bookings before you decide anything. Booking software for a tattoo studio doesn't need to be complicated, and it certainly shouldn't take a cut of your hours in the chair. The right setup quietly fills the diary, protects your time with deposits, keeps every artist's calendar honest, and leaves the money and the client list where they belong, with you. Get those basics right and the back office mostly looks after itself, which frees you up for the only thing that built the shop in the first place: the work. ### Booking Software for Skin Clinics and Estheticians How to pick booking software for skin clinics and estheticians that handles consults, deposits and treatment courses, keeps your client list yours, and takes 0% commission. The Bookatu team · 2026-06-15 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-skin-clinics · markdown: https://bookatu.com/blog/booking-software-for-skin-clinics.md > **The short version** > > - A peel isn't a quick trim. You need consults, deposits and proper gaps between treatments, so most generic booking apps fight your treatment room. > - Bookatu gives your clinic its own branded booking site, deposits that land in your own bank, and reminders that cut empty rooms. > - It takes 0% booking commission, so you keep 100% of every booking, and your client list stays yours, not a marketplace's. > - Free for 60 days, no card needed. After that, plans start at $9/month, priced by active clients, not per chair. Good booking software lets a client book a facial, peel or consult online, then quietly handles the deposit, the reminder and the rebook so you don't have to. The right one fits how skin work actually runs. The wrong one treats a chemical peel like a fifteen-minute fringe trim and leaves you patching the gaps by hand. If you've tried a generic salon app and felt like you were forcing your treatment room into someone else's box, this one's for you. Let's go through what to look for, in plain terms. #### Why a generic booking app fights your treatment room Skin work has rules a haircut doesn't. A peel needs a patch test and a healing window before the next session. A consult has to come before the treatment, not get booked as the treatment. Some services can't sit back to back, because you're cleaning down the room or letting product do its thing. Most cheap booking tools were built for quick, repeatable appointments. They'll happily let a client book a deep treatment with no consult, no buffer and no deposit, and you only find out when they're already on the table. The software you want lets you set those guardrails once, so the calendar protects you instead of working against you. > Your software shouldn't book a peel like it's a wash and blow-dry. The room is different, so the rules should be too. #### What actually changes your week Forget long feature lists for a second. Here's the short version of what genuinely makes a difference in a skin clinic. - Deposits or card holds at the point of booking, so a no-show doesn't cost you a whole treatment slot - Buffer and prep time built into each service, so the room is never double-booked or rushed - A required consult step before certain treatments, so first-timers don't skip straight to the strong stuff - Reminders by text and email, because a forgotten facial is an empty hour you can't get back - Client programs to log course progress and homework, so it lives in one place instead of on sticky notes - Your own branded booking site at your own link, so the clinic looks like yours Every one of those is in Bookatu, on every plan. There's no "upgrade to switch on reminders" trick. Reminders, reviews, loyalty points, gift cards, packages, memberships, referrals, promo codes, a smart waitlist and client programs all come in the box, whatever you pay. #### Deposits that protect a full treatment slot A no-show in a quick-service salon stings. In a skin clinic it really hurts, because you've blocked out 60 or 90 minutes, prepped the room and turned other clients away. An empty table at 2pm is gone for good. Asking for a deposit, or holding a card, gives the booking some weight. People who've put money down tend to turn up, and the casual "I'll just cancel last minute" bookings thin out. With Bookatu you connect your own Stripe account, so those deposits land straight in your bank. Bookatu never touches your booking money. It isn't a middleman taking a cut. It runs the booking and steps out of the way. #### Courses, memberships and the long game Skin results come from a series, not a single visit. A peel course, a run of microneedling, a maintenance facial every few weeks. Your booking software should help you sell and track that, not just take one appointment at a time. Packages let a client buy a course up front. Memberships turn your regulars into steady monthly income you can count on. Client programs give you a place to note where someone is in their plan and what to do at home between sessions. And when a regular drifts off, win-back messages can reach out before they book somewhere else. Many owners find that quietly bringing lapsed clients back beats chasing brand-new ones all day. Loyalty points, gift cards and referrals sit alongside all of that, so the people who love your work have an easy reason to come back and bring a friend. #### Keep your clients, and your money, yours This is the part owners often learn the hard way. On some platforms the bookings come through their marketplace, the clients start to feel like the platform's clients, and a slice of every booking goes to the house. The day you leave, your list can feel like it was never yours. Bookatu works the other way round. You get your own branded booking site at your own link, your team's calendars with two-way Google Calendar sync, and a client list that belongs to you. There's no marketplace selling your clients a competitor down the road. Commission is 0%, so you keep every dollar of every booking. - 0% booking commission, so you keep 100% of every booking - Priced by active clients seen in the last 90 days, never per seat or per room - Free for 60 days with no card, then plans from $9/month - Your own Stripe, your own bank, your own client list #### Getting started without losing a week to setup You don't have to rebuild everything on day one. Add your core treatments, set a deposit on the longer ones, switch on reminders, and drop your booking link in your Instagram bio. That alone covers most of what a busy clinic needs. From there you can require consults on the treatments that need them, build a peel or microneedling course as a package, and start logging notes in client programs so every client's progress sits in one tidy place. Each piece you turn on saves you a little more admin and protects a little more of your day. Skin clients stay loyal when the experience feels considered, from the first online booking to the follow-up after their last session. Software that respects how your treatment room really works lets you spend less time on the calendar and more time on the table, where your skill actually pays off. Set your guardrails once, and let the rooms fill themselves. ### Booking Software for Makeup Artists That Pays You Direct A plain guide to booking software for makeup artists: one branded link, deposits into your own bank, calendar sync for mobile days, and a client list that stays yours. The Bookatu team · 2026-06-14 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-makeup-artists · markdown: https://bookatu.com/blog/booking-software-for-makeup-artists.md > **The short version** > > - One branded link clients can book from, so the right service lands in the right slot without nine DMs back and forth. > - Deposits and card holds protect your kit, your travel and a Saturday you can't get back, and they land in your own bank because you connect your own Stripe. > - Two-way Google Calendar sync stops your studio days, bridals and trials from colliding. > - Bookatu takes 0% commission, the client list is yours, and it's free for 60 days with no card needed. Plans start at $9 a month after that. Your job is the face in the chair. The lashes, the skin, the moment someone catches themselves in the mirror and goes quiet. The job nobody warned you about is the DM thread that runs nine messages deep before a brush comes out of the kit. Good booking software for makeup artists takes that whole conversation off you, so your energy goes into the work that actually pays. Here's an honest look at what to look for, what to ignore, and how it fits the real way you work: studio days, on-location bridals, mobile gigs and the odd last-minute trial. #### One link that handles the booking chat Most MUA bookings still start in a DM. "Are you free the 14th?" "What's a bridal trial?" "Do you come to the venue?" You answer the same five questions ten times a week, usually with a brush in your other hand. A proper booking page sorts that. With Bookatu you get your own branded page at your own link. You list your services once, bridal, occasion glam, a trial, a group rate, each with a price, a length and any travel rules. Drop the link in your Instagram bio, your replies and your enquiry form. The client picks the service, sees your real availability and books the slot themselves. No phone tag, no "sorry, I'm actually booked then." Because it's your link and your brand, you're not sitting in a marketplace next to fifty other artists. Nobody gets shown someone cheaper underneath your name. #### Deposits, because your no-show costs more than most A no-show in a busy salon stings. A no-show for a makeup artist can be brutal. You might have turned down two other bookings for that date, bought product for the look and blocked out a Saturday you'll never get back. For an on-location bridal, you've often built a whole travel day around one client. This is where deposits and card holds earn their keep. When someone books, they leave a deposit or a card on file. It tells you they're serious before you give your day to them. The money goes straight into your own bank because you connect your own Stripe. Bookatu never sits in the middle of it. > A deposit isn't you being difficult. It's the line between a confirmed booking and a maybe, and on a wedding date that line is everything. A few habits keep deposits feeling normal rather than awkward: - Ask for more on bridal and big-event work, where your whole day is on the line, and less for a quick trial or single face. - Say the policy in plain words on the page: what the deposit covers and what happens if they move the date. - Let early reschedules off the hook so genuine clients feel safe booking, while late drop-offs still protect you. #### A calendar that keeps up with a mobile week Plenty of makeup artists don't work from one chair. You're at a studio some days, at a venue others, and wedging a trial in between. The quickest way to lose money and trust is to double-book yourself because your bookings live in one place and your life lives in another. Bookatu syncs both ways with Google Calendar. A new booking drops into your calendar on its own, and anything you block out there, a dentist appointment, your kid's match, a wedding you already said yes to, instantly closes that slot on your page. Clients only ever see times you can genuinely take, and you stop checking three apps to answer one question. #### Fill the gap when a date frees up Cancellations happen even with deposits. What matters is what happens next. A quiet Saturday with no plan is lost income. A quiet Saturday with a waitlist is a chance to fill the gap before lunch. Every Bookatu plan includes a smart waitlist, so when a date opens up the people who wanted it get nudged automatically. The same plan has reminders so fewer slots empty in the first place, and win-back messages for clients you haven't seen in a while. None of it is kept for a premium tier: reviews, loyalty points, gift cards, packages, memberships, referrals, promo codes and newsletters are on every plan too. Turn on what suits you and ignore the rest. #### The bit that matters most: it stays yours Some platforms quietly take a cut of every booking, or treat your clients as theirs. That's a slow tax on a business you built one face at a time, so it's worth reading the small print before you hand your client list to anyone. Bookatu takes 0% commission. You keep 100% of every booking, deposits land in your own account, and the client list is yours to export and keep. Pricing is by active clients, the people you've actually seen in the last 90 days, never per seat and never a slice of your takings. It's free for the first 60 days with no card needed, and plans start at $9 a month after that. A slow month costs you less, not more. Pick the tool that fits how you actually work: deposits that protect your day, a calendar that keeps up with a mobile week, a link that does the talking, and a client list that's still yours in five years. Set it up once, and the next bride who finds your page can book, pay her deposit and lock the date while you're still cleaning your brushes from the last one. ### Booking Software for Yoga and Pilates Studios: What Matters A plain guide to booking software for yoga and pilates studios: class passes, memberships, deposits that stop empty mats, your own branded link and 0% commission. The Bookatu team · 2026-06-13 · Grow your business · https://bookatu.com/en-nz/blog/booking-software-for-yoga-pilates-studios · markdown: https://bookatu.com/blog/booking-software-for-yoga-pilates-studios.md > **The short version** > > - Booking software for yoga and pilates studios lets students book and pay for classes on a page that looks like your studio, not a marketplace. > - Deposits and card holds keep mats from sitting empty, and because you connect your own Stripe, that money lands in your bank, not ours. > - Class passes, memberships, a smart waitlist and loyalty come in every plan, so growing your studio never means paying to switch on another feature. > - Bookatu takes 0% commission and bills by active students, not per teacher, so a busy month never costs you more for being busy. You didn't open a studio to spend your evenings answering "any space in the 6am?" on Instagram. The right booking software for yoga and pilates studios takes that job off your plate, so a page handles it while you teach, while you sleep, and while the reformers are mid-class. Here's what actually matters when you're choosing one. #### A studio needs more than a calendar A solo teacher can get by with a diary. A studio can't. You've got a class timetable, drop-ins, regulars on memberships, people halfway through a 10-class pass, and a waitlist for the Saturday flow that always fills. A plain calendar shows times. It doesn't hold any of that together. Good software keeps the whole thing in one place. A student books the 7pm vinyasa, the spot comes off your live count, their class pass ticks down by one, and if they cancel inside your window, the seat offers itself to the next person waiting. You didn't lift a finger. - Class capacity that updates the second someone books or cancels, so you never oversell a mat. - Memberships and class passes tracked for you, with no spreadsheet and no "how many have I got left?". - A smart waitlist that fills cancellations on its own, instead of you texting around. - Each teacher's calendar in one view, with two-way Google Calendar sync so their own diary stays right. #### Your studio's link, not a marketplace Some apps list your classes next to every other studio in town and take a cut for it. That's not booking software. That's a middleman renting you your own students. With Bookatu, you get your own branded booking site at your own link. It carries your name, it looks like your studio, and the students who book there are yours. That matters more than it sounds. When a student books through your page, you keep their details, their history and their permission to message them. No platform sits between you and the people who fill your classes, and nobody gets to advertise a cheaper studio over the top of your booking. Your client list stays your client list. > A booking link should build your studio's name, not someone else's app. #### Stop the empty mat without scaring anyone off An empty spot in a class of eight isn't one missing student. It's a mat that could have gone to someone on the waitlist, and a teacher you're paying to lead a half-full room. No-shows sting studios more than most trades, because your capacity is fixed and your costs aren't. The fix is gentle, not heavy-handed. A quick reminder by text and email catches the people who simply forgot, which is most of them. For the rest, a small deposit or a card hold at booking quietly sorts the committed from the casual. The detail that matters with Bookatu: you connect your own Stripe, so deposits and any no-show fees land in your bank account. Bookatu never touches your booking money. - Automatic reminders, so a forgotten 6am becomes a rare thing. - A small deposit or card hold to protect the spots that cost you most. - A clear cancellation window students agree to up front, so there's no awkward chat later. - Waitlist auto-fill, so the gaps that do happen close themselves. #### Passes, memberships and the maths of a full term Studios live and die by regulars. A drop-in is lovely. A student on a monthly membership or a 10-class pass is planned income you can actually build a timetable around. Your booking software should make that the easy, obvious path, not something you have to pay extra to reach. With Bookatu, every plan includes the full kit: memberships, packages and class passes, loyalty points, gift cards, referrals, promo codes and marketing newsletters. There's no "pro tier" wall between you and the tools that grow recurring revenue. You set them up once and they run quietly in the background, term after term. - Sell a 10-class pass up front, so students prepay and pre-commit to coming back. - Offer a monthly membership for unlimited mat classes, and earn income you can plan around. - Hand out gift cards and referral perks that bring new faces in without discounting your timetable. - Send the occasional newsletter about a new teacher, a workshop or a retreat, straight to the students who already love you. #### Pricing that doesn't punish a busy month Watch how a tool charges, because it shapes how you grow. Anything that takes a percentage of every booking gets more expensive exactly when you're doing well, which is backwards. Per-teacher pricing punishes you for bringing in a Saturday cover instructor. Bookatu charges 0% commission, so every class fee stays fully yours, and bills by active students, meaning someone you've seen in the last 90 days. Never per seat, never per teacher. A quiet January costs less than a packed September. You can run it free for 60 days with no card, and plans start at $9 a month after that. The idea is simple: when your studio has a great month, your software bill shouldn't be the thing that flinches. Booking software for yoga and pilates studios should feel like an extra pair of hands at the front desk: taking the bookings, sending the reminders, filling the waitlist and tracking the passes, so you and your teachers can stay where you belong, on the floor with your students. Set it up over one quiet evening, point your next few enquiries at the link, and watch the timetable start running itself. ### How to Take Deposits for Appointments: A Practical Guide A practical guide to taking deposits for appointments: flat vs percentage, how much to ask, who pays, card holds, and a refund rule clients won't resent. The Bookatu team · 2026-06-12 · Reduce no-shows · https://bookatu.com/en-nz/blog/how-to-take-deposits-for-appointments · markdown: https://bookatu.com/blog/how-to-take-deposits-for-appointments.md > **The short version** > > - A deposit isn't an extra charge. It's part of the bill, paid early, and it comes off what the client owes. Say that out loud and most people are fine with it. > - Pick three things: flat amount or percentage, how much, and who pays (everyone, or just new and risky bookings). > - You connect your own Stripe, so deposits land in your bank. Bookatu takes 0% and never touches the money. > - Write your cancellation window and refund rule once in plain words. Clients see it at booking, and the system handles the rest. Asking for money before someone has sat in the chair feels awkward the first time. It stops feeling awkward the moment you've watched a Saturday slot sit empty three weeks running. A deposit is the simplest, fairest way to turn a casual hold into a real commitment, and setting one up is mostly a few small decisions and one clear sentence. This is the practical version. Not why deposits work, but how to actually take them: what to charge, who to charge, and how to keep your good regulars happy while you do it. #### First, sort out the money plumbing To take a deposit you need a way to charge a card safely. In Bookatu that means connecting your own Stripe account, which takes a few minutes and a bit of business info. This matters more than it sounds. Because the Stripe account is yours, every deposit goes straight into your bank, not into some middleman's account that pays you out later. Bookatu takes 0% on bookings and never sees a card number or holds your revenue. So before you touch any settings, connect Stripe. Once that's done, your deposits, card holds and final payments all run on your own rails, and you can watch the money turn up where you'd expect. #### Flat amount or a percentage? This is your first real call, and there's no single right answer. It comes down to how much your prices vary. - A flat amount, say 20 dollars, is simple and predictable. It works well when most of your services cost roughly the same, like a barber or a single-treatment studio. Clients always know exactly what they're putting down. - A percentage, say 25 or 50 percent, scales with the booking. It's the better fit when you've got a 30 dollar trim and a 300 dollar colour correction in the same calendar. A flat 20 dollars barely covers the big slot, while half of it protects you properly. Not sure? Start with a modest flat amount. It's the easiest thing for clients to get their head around, and you can switch to a percentage later once you see which appointments you actually lose. #### How much should you ask for? Enough to make someone think twice about ghosting, not so much that booking feels like a risk. For most appointment-based businesses that's somewhere between 20 and 50 percent of the service, or a flat amount in the same range. The deposit comes off the final bill, so the client doesn't pay a cent more. They're just paying part of what they already owe a bit sooner, and that framing is the whole game. For your higher-value or longer bookings, the ones that hurt most when they vanish, lean towards the top end. A two-hour slot you can't refill is worth protecting harder than a quick fifteen-minute touch-up. Look at your own calendar and ask which appointments would genuinely wreck a day if they didn't show. Price the deposit to cover those. #### Decide who actually pays it This is the part owners chew over, and it's the part that decides whether deposits help you or quietly annoy your best people. The worry is always the same: will the loyal regular who hasn't missed in five years feel insulted by being asked for a card? You've got two honest options. Charge every online booking the same way, which is fair, consistent and easy to explain. Or be cleverer about it and only ask the bookings that carry real risk. Bookatu's smart waitlist and history aren't the only trick here: it can read each client's record, so a regular with a clean history books with no deposit, while a brand-new client or someone with past no-shows gets asked to pay one. > Protect the calendar without sending the wrong message to the people who keep you in business. Plenty of established businesses go the smart route. It puts a gate in front of the genuinely uncertain bookings and leaves a friction-free experience for everyone who's earned your trust. Newer salons often charge everyone at first, simply because they don't have the history to judge yet. Both are reasonable. You can change your mind in a minute. #### Card holds or charging upfront A deposit is money taken now and knocked off the bill. A card hold is different: you store the client's card at booking and only charge it if they no-show or cancel late. Nothing leaves their account if they turn up, which feels gentler and is often easier to sell to a nervous client. Both run through your Stripe connection, and both do the same job, giving the client something to lose. A rough rule: use a deposit when you want cash in hand and to filter out the truly non-committal. Use a card hold when your clientele is mostly reliable and you just want a backstop for the odd fade. Plenty of owners run holds for regulars and deposits for new faces, and you can set that up so the right people get the right ask. #### Write the rules once, in plain words A deposit on its own is only half a policy. The other half is a cancellation window, the notice you ask for before someone changes or cancels. Set it once in your settings and clients see it the moment they book and again in their confirmation. No surprises, which is exactly what keeps people from getting cross later. Keep the wording human and specific. Something like: "A 20 dollar deposit secures your spot and comes off your final bill. Cancel or rebook with at least 24 hours' notice and it's fully refunded. Inside 24 hours, the deposit covers the held time." That sentence does more for your no-show rate than any amount of chasing. And when someone does cancel late and forfeits a deposit, the slot reopens, so your waitlist can fill it while you get on with your day. #### Where to go from here Start small and watch what happens. Connect Stripe, pick a flat amount or a percentage, decide whether to charge everyone or just the risky bookings, and write one clear sentence about cancellations. Give it a month, keep an eye on your no-show rate, and nudge the amount up or down once you've seen real behaviour instead of guessing at it. Most owners find the first awkward week passes quickly and the calendar just starts holding together, with the money landing in their own account where it belongs. ### Leaving Fresha or Booksy: how to go independent without losing your clients Thinking of leaving a marketplace but worried about losing your regulars? You can switch and keep every client. Here is a calm, step-by-step plan to go independent. The Bookatu team · 2026-06-11 · Grow your business · https://bookatu.com/en-nz/blog/leaving-fresha-or-booksy-without-losing-clients · markdown: https://bookatu.com/blog/leaving-fresha-or-booksy-without-losing-clients.md Plenty of owners want to leave a marketplace but stay put anyway, held back by one fear. What if I lose my clients, my reviews and my calendar all at once? It is a fair worry, and it is exactly the fear the marketplace counts on. The good news is that switching is calmer than it looks, and you can keep every client. Here is the plan. #### Why owners stay longer than they should The thing keeping most people stuck is not the software. It is the sense that the platform holds the keys to their business, the client contacts, the booking history, the reviews. So leaving feels like starting from zero. It is not, but the feeling is real, and it is worth naming before we work through it. #### The truth: your clients came for you Your clients did not fall in love with an app. They came for your work, your chair, your manner. Move somewhere new and tell them where you are, and they follow. We make the wider case for this in Your clients are yours, but the short version is simple. The relationship is yours, and a marketplace cannot actually keep it from you. #### Step 1: Export your client list Start by getting your clients out of your old tool. Most booking apps let you export your clients as a CSV file, the kind any spreadsheet can open, with names, phone numbers and emails. That file is your business in your pocket, so save it somewhere safe. #### Step 2: Import them into Bookatu Next, bring that list into Bookatu all at once rather than typing anyone in. You upload the file, match up the columns, and your clients appear in your list, ready to message and recognise from day one. If the file is messy, send it to us and we will help bring your clients across (see Importing your clients). #### Step 3: Set up your booking page and services Now build your new home. Add your services with their prices and durations, set your opening hours, and add your team. Within an hour you have a branded booking page at your own link, showing your name, colours and real availability (see Your booking page, Setting up your services and Setting your opening hours). #### Step 4: Connect Stripe so you get paid directly Connect your own Stripe account so deposits go straight to you, with no platform wallet in between (see Connecting Stripe for payments). There is more on why this matters in Getting paid your way. This is also where your no-show defences switch on, since deposits need Stripe to charge a card. #### Step 5: Tell your clients, the part that actually keeps them This is the step that keeps your regulars, so do it warmly. Send a short, friendly message letting clients know you have moved and sharing your new booking link. Run both systems side by side for a few weeks if it helps, then put your new link everywhere clients look. - Put your booking link in your Instagram bio and stories (see Beam). - Add it to your Google profile and your email signature. - Send a one-off newsletter to your imported client list with the news (see Newsletters). - Print a QR code for reception and your window so walk-ins can book on the spot. #### Step 6: Rebuild reviews and momentum Reviews on a marketplace stay on the marketplace, but you can rebuild on your own Google profile quickly, and that is where new local clients find you anyway. Bookatu can ask for a review after every visit and point happy clients to Google (see Reviews and the Google flywheel). Our post Getting found online explains how reviews and a complete profile compound over time. #### You will not pay to grow Once you have moved, the maths changes for good. Bookatu takes 0% commission on your bookings, so a busy month is simply a good month, as we explain in Why we built a booking platform that takes 0% commission. And your data stays yours, so you are never locked in again (see Exporting your data). Going independent is far less scary than staying put feels once you have done it. You can start free, import your clients, and have your own booking page live the same day. Have a look at the pricing page to see what you would pay, with no cut taken from a single booking. ### Salon Cancellation Policy Examples You Can Copy Today Copy-and-paste salon cancellation policy examples for salons, spas, barbers, gyms and clinics. Swap in your own notice and deposit, then go live the same day. The Bookatu team · 2026-06-11 · Reduce no-shows · https://bookatu.com/en-nz/blog/cancellation-policy-examples · markdown: https://bookatu.com/blog/cancellation-policy-examples.md > **The short version** > > - A good policy is short, kind and clear. Say how much notice you need and what happens if someone misses it. > - Steal an example below, drop in your own times and amounts, and you're sorted in five minutes. > - Put the same line everywhere clients look: your booking page, the confirmation and the reminder. > - Let a small deposit and your booking system do the firm bit, so you never have to be the bad guy at the desk. Most owners know they need a cancellation policy. The thing that stalls everyone is the wording. You don't want to sound like a parking fine, but you also can't keep eating the cost of a no-show colour on a busy Saturday. So treat this as a swipe file: real, plain examples you can copy, tweak and put live today, whether you run a salon, a spa, a barbershop, a gym floor or a treatment room. Pick the one that fits your business, change the numbers, done. No legalese, no drama. #### What every good policy actually says Before the examples, here's the bones of it. Nearly every policy that works says four things, in words a tired client can read on their phone at 10pm: - How much notice you need to reschedule or cancel for free. 24 or 48 hours suits most businesses. - What happens inside that window, so you keep the deposit or charge a set fee. - What a no-show means, usually the full deposit and sometimes a share of the service price. - How easy it is to change a booking, so people move it instead of vanishing. That's the whole job. If your policy covers those four points, it's working. Everything below is just that skeleton dressed in different words for different rooms. #### Salon and barber examples (copy these) Salons and barbershops live and die by the chair. A missed long appointment is a hole you can rarely refill on the day. Keep the tone warm, because most no-shows are good people who forgot, not people trying to rip you off. A friendly, everyday version for a hair salon: > Plans change, we get it. Give us 24 hours' notice to reschedule and your deposit moves with you. Cancel inside 24 hours or don't show, and the deposit is kept to cover the slot. For high-value work like balayage, extensions or keratin, where the loss really stings, ask for a bit more notice and say why: > This appointment is booked just for you and takes a few hours of our day, so we ask for a deposit to hold it. Reschedule with 48 hours' notice and the deposit carries over. Inside 48 hours, or a no-show, and the deposit is kept. And a short one for a busy barbershop, where slots are quick and back to back: "Running late or can't make it? Give us a shout before your slot and we'll sort you out. No-shows lose the booking fee, simple as that." #### Spa, clinic and studio examples Spas, clinics and studios block longer rooms and often prep products or kit ahead of time. Your wording can lean a touch more formal without going cold. The trick is to explain the why in one line, so the rule reads as fair rather than fussy. A day spa or massage room: > Your room and your therapist are held just for you. We ask for 48 hours' notice to change or cancel. Late cancellations and no-shows are charged 50% of the treatment, as we rarely refill the time at short notice. A clinic or aesthetics practice, where time and consumables are committed in advance: "A deposit holds your consultation and comes off your treatment. Please give us 48 hours to reschedule. Miss the appointment without notice and the deposit is kept." For a fitness studio, gym or personal trainer, where a no-show often blocks a spot someone on the waitlist wanted: > Spaces are limited, so if you can't make your session please cancel at least 12 hours ahead and we'll pass it to someone else. Late cancels and no-shows use up the session from your pack. #### Put it where people actually read it A great policy buried in your terms and conditions does nothing on a Sunday night when someone's deciding whether to bother showing up. The words only work if clients meet them at the moments that matter. Use the same short line in three places: - On your booking page, right where they pick a time, so it sets the expectation before they commit. - In the confirmation, so it lands the moment the booking is real. - In the reminder a day or two out, so "I forgot the rule" never holds up. With Bookatu the policy sits on your own branded booking site and rides along in the confirmations and reminders, so you write it once and it shows up in all the right spots. #### Let the system enforce it, not you Here's the part most owners dread: being the person who holds someone to the rule. Standing at the desk asking a regular for a fee is nobody's idea of a good morning. So don't be that person. Let the tools carry the firm bit while you stay the friendly face. A policy with no deposit behind it is just a strongly worded suggestion. Pairing the wording with a small deposit or card hold is what turns "I'll probably come" into a real commitment. With Bookatu you connect your own Stripe, so any deposit lands in your bank, not ours. We never touch your booking money, and we take 0% commission on the booking. The system holds the deposit, applies your policy when someone breaches it, and can offer the freed-up slot to your waitlist on its own. > A cancellation only really costs you if the slot stays empty. Fill it from the waitlist and the gap quietly closes itself. Keep a bit of human discretion on top of all this. A loyal regular with a sick child is not the same as a serial no-show, and a quick "don't worry about it this time" buys more goodwill than any rule. Let the system handle the genuine offenders so you can be generous with the people worth keeping. #### Start with one or two booking types You don't need to police every appointment from day one. Pick your two highest-risk booking types, the long ones and the peak-time ones, add a deposit and a clear window to those, and paste in whichever example above sounds most like you. See how it feels for a few weeks, then widen it if you need to. The goal was never a fortress of rules. It's a calmer, fuller diary where the time you set aside actually gets used, and where good clients barely notice the policy is there. Get the wording right once, let your booking system do the chasing, and you can get back to the part of the job you actually enjoy. ### How to Set Up Online Booking: A Simple Guide for Owners A plain, practical guide to setting up online booking for a small service business: what to prep, how to list your services, and the settings that quietly protect your day. The Bookatu team · 2026-06-10 · Grow your business · https://bookatu.com/en-nz/blog/set-up-online-booking-in-an-afternoon · markdown: https://bookatu.com/blog/set-up-online-booking-in-an-afternoon.md > **The short version** > > - Setting up online booking takes an afternoon, not a fortnight. Write down your services, times and prices first and the rest falls into place. > - You get your own branded booking site at its own link, so clients book themselves in while your hands are busy. > - Switch on reminders, deposits and two-way Google Calendar sync from day one. They do the quiet work of protecting your diary. > - With Bookatu you connect your own Stripe and keep 100% of every booking. Deposits land in your bank, not ours, and we take 0% commission. If you still take bookings by phone, text and the odd DM, you know the cost already. The calls you miss while your hands are busy. The five messages it takes to land on a time. The double-booking you don't catch until two people show up for the same slot. Online booking takes that off your plate, and setting it up is far simpler than most owners expect. Here's how to do it properly, in an afternoon, so it's working for you by the time you lock up. #### Write down what you actually sell Before you touch any software, list what someone can genuinely book. Not the marketing version, the real thing. This is the step that makes everything after it quick, so give it ten minutes now. For each service, jot down three things: - The name a client would recognise (a cut and blow-dry, a 60-minute deep tissue, a first-session assessment). - How long it really takes, including your tidy-up and reset, not the wishful version. - The price, and whether you want a deposit to hold the slot. If a few services are nearly identical, group them. If one needs a chat before you can quote, mark it as a consultation. You're after a list that matches your real day, at the chair, in the treatment room, on the gym floor or in the studio. Get this right and the booking site practically builds itself. #### Set your hours, your team and your buffers Now tell the system when you actually work. Your opening hours, the days you're shut, the lunch you refuse to skip. If you've got a team, each person gets their own calendar and their own availability, so clients only ever see slots that are genuinely free. Buffers earn their keep here too. A short gap after certain services means you're not sprinting from one client to the next, and you've got a minute to reset the room. Set them once and you stop quietly running late by four in the afternoon. With Bookatu, those calendars sync both ways with Google Calendar. Block a dentist appointment in Google and that slot vanishes from your booking site. Take a booking online and it lands in Google. You stop running two diaries and hoping they agree. #### Switch on the settings that protect your time A booking link on its own is handy. A booking link with a few smart settings turned on is what actually changes your week. Do these from the start, not after a rough month forces your hand. - Reminders. An automatic text and email before each appointment catches the people who simply forgot, and that's most no-shows. - Deposits or a card hold. Asking for a small deposit makes people turn up, and it quietly filters out the ones who were never serious. - A cancellation window. Decide how much notice you need and let the system hold clients to it, so you're not the bad guy chasing them. - A waitlist. When someone cancels, the slot gets offered to people waiting, so a gap often fills itself instead of sitting empty. Here's the bit a lot of booking tools quietly skip past. With Bookatu you connect your own Stripe account, so deposits and payments land in your bank, not ours. We never sit between you and your money, and we take 0% commission, so what a client pays is yours to keep. Every plan includes all of these too, with no upsell to reach the settings. > A good booking page works like a good front-of-house. Polite, always on, and never once tempted to send your clients somewhere else. #### Make the page yours, then book yourself in Your booking site sits at its own branded link, so add the things that make it feel like you. Your logo, a couple of real photos, a short line about what you do. It doesn't need to be fancy. It needs to look like the place clients already trust, not a generic form on someone else's marketplace. And the clients you bring in stay yours, on your list, not anyone else's. Then do the step almost everyone skips. Book yourself in. Open the link on your phone the way a stranger would, pick a service, choose a time, pay the deposit. You'll catch the small stuff in two minutes, a service that's mislabelled, a gap in your hours, a price that reads oddly. Fix it now, before a real client meets it. #### Get the link in front of people A booking page nobody can find won't fill your diary. The good news is you do this once and then it runs itself. Put the link everywhere a client might look for you. - The 'Book' button on your Instagram and Facebook profiles. - Your Google Business Profile, so it shows up when locals search for you. - Your website, your link in bio, your email signature. - A short auto-reply to DMs and texts that points people straight to the link. From here, the booking happens without you. Someone finds you at ten at night, picks a time, leaves a deposit, gets their reminder, and turns up. You did the setup once and it keeps paying off every quiet evening after. That's really the point of getting online booking right. Not the tech, the time it hands back. Fewer interruptions while you're working, fewer empty chairs, fewer late-night messages to answer. With Bookatu you can try it free for 60 days, no card needed, and pricing is by active clients rather than per seat, so it scales with the work you're actually doing. Set it up carefully this week and the next few months get noticeably calmer, with your clients, your calendar and your money all staying exactly where they belong, which is with you. ### SMS vs Email Appointment Reminders: Cut No-Shows SMS or email for appointment reminders? Each does a different job. Here's how to use both at the right moment to cut no-shows, with timing and wording that work. The Bookatu team · 2026-06-09 · Reduce no-shows · https://bookatu.com/en-nz/blog/sms-vs-email-appointment-reminders · markdown: https://bookatu.com/blog/sms-vs-email-appointment-reminders.md > **The short version** > > - A text gets read fast and nearly always, so it's your day-before and morning-of nudge. Email has room and costs you nothing, so it's your booking confirmation and the friendly heads-up a few days out. > - You don't have to pick one. The owners who lose the fewest appointments use both, each for the job it's actually good at. > - Keep it short and human: who, what, when, where, and an easy way to reschedule. > - In Bookatu you set the sequence once and it runs in the background for every booking, on every plan, at 0% commission. Every appointment business runs on the same quiet bet: that the person who booked three weeks ago actually walks in today. A reminder is how you make that bet safer. The question I get asked most is which kind to send, SMS or email. The honest answer is that they do different jobs, and once you see the difference you stop choosing and start using both on purpose. #### What a text is good at A text lands on the one thing people never leave behind, and most of us open one within minutes of it buzzing. That makes SMS the right tool for the moments that matter most: the day before, and the morning of. If someone's going to forget, that's usually when, and a quick text reaches them while there's still time to confirm or move the slot. Texts are short by nature, and that's a feature. Nobody scrolls a text. They glance, they clock the time and place, and they get on with their day. The trade-off is cost. Texts aren't free to send, and the more of them you fire off, the more they add up. So spend them where they earn their keep, close to the appointment, not three days out for a haircut. #### What email is good at Email has room and costs you nothing to send, so it's the natural home for anything longer than a one-liner. Your booking confirmation belongs here: the full details, your address with a map link, what to bring, your cancellation window, the parking note for the studio or the prep before a treatment. It's also the gentle heads-up a few days out, the one that gives a client time to reschedule early instead of vanishing on the day. The catch with email is simple. People don't check it as fast, and a confirmation can sit unread under a stack of newsletters. That's why it's a poor last line of defence. Email is great for the calm, detailed message when there's plenty of runway, and weak for the urgent tap on the shoulder an hour before the chair, the gym floor or the treatment room sits empty. #### Don't pick one, give each a job Once you stop treating this as a contest, the setup almost designs itself. Use the cheap, detailed channel early and the fast, certain channel late. A sequence that works for nearly any appointment business looks like this: - At the moment of booking: an email confirmation with everything they need, plus a one-tap link to reschedule. - Two or three days before: a short email heads-up, your early warning so people can move the slot while it's still easy to fill. - The day before or the morning of: a brief text, the nudge that actually reaches the forgetful with time to spare. - After the visit (optional): a quick thank-you and a prompt to rebook, so the chair stays full next time too. Notice the shape. Email carries the detail when there's no rush. SMS carries the certainty when the clock is ticking. You're not sending more messages, you're sending the right kind at the right moment. #### Write reminders people don't resent The fastest way to make reminders feel like nagging is to send too many, or to leave them vague. Keep each one specific and human. Lead with the essentials, who they're seeing, what for, when and where, then make the next step obvious. The most useful thing you can add isn't a guilt trip, it's an easy way out: a link to reschedule. A client who can move their slot in two taps almost never becomes a silent no-show. > A reminder isn't a telling-off. It's a favour. You're handing busy people their own calendar back. Match the tone to your business. A barber can be cheeky, a clinic should be plain and reassuring, a trainer can be a touch motivating. The words are yours; the timing does the heavy lifting. And a reminder works best with something real behind it, like a deposit or card hold on the slots you can't afford to lose. Reminders catch the forgetful. A deposit catches the rest, and in Bookatu it goes straight into your own bank through your own Stripe. #### Setting it up without the faff None of this should mean copy-pasting texts at eleven at night. In Bookatu you set the reminder sequence up once and it runs itself for every booking, both SMS and email, on your own branded booking site. Email reminders are included on every plan; text reminders come with every plan from Studio up, and on Solo they are a small monthly add-on. Pricing goes by active clients, the people you've seen in the last 90 days, not by seat, so a busy week doesn't quietly cost you more. And because Bookatu takes 0% commission, none of this is funded by skimming your takings. You keep 100% of every booking, your client list stays yours, and the deposits you take to back up those reminders land in your own account, not ours. The reminder system just does its quiet job in the background while you do yours. The first 60 days are free, no card needed, so you can watch it work before you pay a cent. So stop framing it as SMS versus email. Think of it as a relay: email sets the pace early with the full picture, SMS brings it home when it counts. Get that handoff right and the empty-chair surprises that used to dot your week start to fade, without you chasing a single client by hand. ### How to Get More 5-Star Reviews for Your Salon or Clinic A practical guide to getting more 5-star reviews for your salon, spa, studio or clinic: when to ask, how to make it effortless, and how to keep unhappy clients off your public page. The Bookatu team · 2026-06-08 · Grow your business · https://bookatu.com/en-nz/blog/get-more-5-star-reviews · markdown: https://bookatu.com/blog/get-more-5-star-reviews.md > **The short version** > > - Most happy clients never leave a review. Not because they didn't love it, but because nobody asked while it was fresh. > - Ask every client, soon after the visit, with a link that takes two taps. Make it a habit, not something you remember on a good day. > - Hear the unhappy ones privately first, so problems come to you instead of landing on your public page. > - Reviews are on every Bookatu plan, and you can have the request go out automatically once an appointment is done, so it happens without you chasing it. You do good work. The cut lands, they leave the facial glowing, the client hits a new personal best, the treatment actually helps. Then they walk out happy and quietly forget you exist online. That gap between great work and a thin review count is the most fixable thing in your business, and it has almost nothing to do with how good you are at the job. Getting more 5-star reviews isn't about being more charming. It's about asking, at the right moment, in a way that takes two taps instead of twenty minutes. Here's how to build that into your week so the reviews stack up on their own. #### Reviews don't happen by accident, they happen by asking Here's the part owners learn the slow way: the clients who love you usually aren't the ones who post about you. Happy people are busy. They meant to leave a review, they really did, then dinner needed making and the moment passed. The clients most likely to write something without being asked are the annoyed ones, because being cross is a stronger push than being quietly pleased. So if you never ask, your page slowly fills with the loud few and stays silent on the happy many. The fix is dull but it works. Ask every single time, and make the ask effortless. The salons and clinics sitting on hundreds of recent five-star reviews usually aren't better than you. They're just better at asking. > Your best clients aren't holding back praise. They're waiting to be reminded, and handed a link short enough to use at a bus stop. #### Timing matters: ask while the glow is still warm A review request that turns up three weeks later gets ignored. One that arrives while they're still checking their hair in the car mirror, or still buzzing from a session that went well, gets answered. The window is short. Ask too early and they haven't even left. Ask too late and the feeling has gone. For most of us the sweet spot is a few hours after the appointment, or the next morning. Long enough to be home and settled, soon enough that it's still fresh. This is the kind of small, well-timed nudge that's easy to forget by hand and easy to get right with software. In Bookatu you can have the review request go out automatically once the appointment is marked done, so every client gets the same timing and you're not watching the clock. - Hair, beauty and barbers: a few hours after, while they still love the result. - Spa and massage: that evening or the next morning, once they've eased back into the calm. - Personal trainers: right after a milestone session or a personal best, while the motivation is high. - Clinics: once they've felt the benefit, not the moment they walk out sore or nervous. #### Make it a two-tap job, not a chore Every extra step between the client and the review costs you reviews. If they have to find your page, dig up their Google login, and work out what to write, most won't bother. Your job is to clear the friction, not to test how keen they are. Send a short, warm message with a link straight to your Google review page. No app to download, no form to hunt for. One line of thanks, one link, done. It helps to point them a little too. A nudge like "tell people what you came in for and how it turned out" gives a nervous reviewer the words, and those specific reviews are the ones future clients actually read. Personalise it where you can. "Thanks for coming in today, Sarah" beats a faceless blast every time, and it costs you nothing when your booking system already knows who Sarah is and what she booked. #### Hear the unhappy ones before they reach your public page Not every visit goes perfectly, and that's fine. What matters is where a disappointed client lands. If your only move is to fire the same public review link at everyone, you're handing the one person who left unhappy a megaphone aimed at every future client. There's a kinder, smarter way. Give people a private door first. Before you point anyone at Google, ask how the visit went. The ones who had a great time get a gentle push toward your public page, where their words help the next person find you. The ones who had a problem get a quiet way to tell you directly, so you can put it right, win them back, and protect your reputation while you're at it. A quick "how did we do today?" by text or email is enough to set this up. > A complaint you hear privately is a chance to fix things. The same complaint posted publicly is a warning to everyone else. #### Build the habit so it runs without you The owners who win at reviews don't run on willpower. They turn the ask into a routine that happens whether they remember or not. That means switching on an automatic review request after every appointment, so it fires for every client, every time, even on the days the place is heaving and you can't think straight. It also helps to get your team saying it out loud. A quick "if you loved it, we'd be so grateful for a review, we'll text you a link" from the stylist, trainer or therapist makes the message that follows feel expected and warm instead of out of the blue. The person plants the seed, the system delivers the link. And since reviews are on every Bookatu plan, turning this on doesn't cost you anything extra. - Switch on an automatic review request so every finished appointment triggers one. - Keep the message short, warm and personal, with a direct link. - Send happy clients to Google and route unhappy ones to a private reply first. - Add a human nudge at the chair, the bench or the treatment room. - Reply to every review you get, especially the awkward ones, because the next reader is watching how you handle it. None of this is a one-off push. It's a quiet routine that builds on itself. Ask every time, ask soon, make it effortless, and keep the unhappy ones offline and heard. Do that for a few months and your review count stops being something you fret about and starts being one of the strongest reasons new clients pick you over the place down the road, all of it ticking along in the background while you get on with the work you're actually good at. ### How to Price Your Services Without Guessing A plain, practical guide to pricing your services: work out your real costs, charge for the result, sanity-check local rates, and raise prices without losing good clients. The Bookatu team · 2026-06-07 · Grow your business · https://bookatu.com/en-nz/blog/how-to-price-your-services · markdown: https://bookatu.com/blog/how-to-price-your-services.md > **The short version** > > - Start from what a service actually costs you in time, product and overheads, then add the profit you want on top. Don't just copy the place down the road. > - People pay for the result, not the minutes. Getting good at your job should cost more, not less. > - Local rates are a sanity check, not a ceiling. Being the cheapest is rarely a plan. > - Raise prices in small, regular steps. Tell your regulars warmly, then let your booking page show the new rate quietly. Most owners set their first prices by peeking at what everyone else charges and knocking a bit off. It feels safe. It's also how you end up flat out, knackered, and somehow keeping almost nothing at the end of the month. Pricing isn't a dark art. It's a few honest sums and a bit of nerve, and once you've done it properly you stop second-guessing every quote. This is for the person actually doing the work, whether that's in the chair, the treatment room, on the gym floor or in the studio. Let's build a price from the ground up. #### Start with what the service really costs you Before you can price anything, you need to know what it costs to deliver. Not just the obvious bits like product and a room, but everything that has to be paid before you keep a single cent. Sit down once and work it out properly. It's less painful than you'd think, and you only do it now and again. - Your time, including setup, cleanup and the gap before the next client. - Materials and product used in the service. - A slice of your fixed costs: rent, power, insurance, software, water. - Card fees and any tax you set aside. - The profit you want left over once all of that is paid. That last line is the one people forget. Profit isn't what happens to be left at the end. It's a number you decide on and build into the price on purpose. If a service doesn't leave you the profit you set, the price is too low. Simple as that. #### Price the result, not the minutes Clients aren't really buying an hour of your time. They're buying the outcome: colour that finally suits them, a back that stops aching, a body that feels stronger, a photo they'll keep for years. Two people can offer the same service and charge very differently, because one delivers a better result and a calmer, more personal experience around it. So when you price, count the skill and the years behind the work, not just the clock. A treatment that takes you forty minutes because you're good at it shouldn't cost less than the same treatment done slowly by someone green. Speed you earned through skill is worth more, not less. > Price purely by the minute and you punish yourself for getting good at your job. #### Use local rates as a sanity check, not a rulebook It helps to know roughly what others nearby charge. Just use it as a reference point, not a ceiling you're scared to cross. There'll always be someone cheaper. Racing them to the bottom only means you both end up exhausted and broke. The question isn't whether you're the cheapest. It's whether your price matches the value and the experience a client actually gets. If you sit well above the local average, that's fine, as long as the experience backs it up: the welcome, the result, the little touches, the fact that everything just works. If you sit below average and you're rushed off your feet with no room to breathe, that's usually a sign your prices are too low, not that your diary is a triumph. #### Give people a way to spend more A single flat price gives a client one decision: yes or no. Offer a good, better and best option and the question quietly turns into which one, and a fair few people reach for the middle or the top. You're not pushing anyone. You're giving the client who wants more a clear way to have it. This is where Bookatu pulls its weight without adding to your admin. Packages, memberships, gift cards and loyalty points are in every plan, so you can bundle services, sell a course of treatments upfront, or offer a membership that smooths out your income. Building a higher-value option is just a setting, not an upsell on your bill. And because Bookatu charges by active clients rather than per seat, your pricing doesn't punish you for having a busy week. #### Charge with confidence and protect the booking A price only counts if the appointment actually happens. A no-show doesn't just cost you the slot, it quietly drags down what every booked hour really earns. Taking a deposit or holding a card at the time of booking makes the commitment real on both sides, and protects the price you worked out so carefully. With Bookatu you connect your own Stripe, so any deposit lands in your bank, not ours. Bookatu never touches your booking revenue and takes 0% commission, so the full price you set is the price you keep. That matters when you're doing this maths, because a platform skimming a cut of every booking is really a price cut you never agreed to. #### Raise prices in small steps, without the drama Most owners leave it far too long, then panic-jump prices in one go and brace for clients to walk. The calmer way is small, regular rises. A modest increase once a year, with a bit of notice, rarely loses you anyone who values your work. The ones who only ever came for the lowest price were never really your clients anyway. Let your booking page do the awkward part. When you update your prices in Bookatu, the new rate simply shows when clients book, so there's no uncomfortable moment at the counter. Tell your regulars warmly and ahead of time, thank them, and let the page handle the rest. Good clients know costs go up, and that you deserve to be paid properly. Pricing isn't something you solve once and never touch again. Your costs shift, your skill grows, and your diary keeps telling you things. Revisit your numbers every so often, keep building in the profit you actually want, and treat each rise as a normal part of running a healthy business. Get the foundation right and your prices stop being a worry, and start being one of the quiet, steady things that keep your doors open. ### How to Fill Quiet Weekday Appointment Slots Dead Tuesday mornings and that 2pm gap cost you money. Here's how to fill quiet weekday appointment slots without dropping your prices or chasing strangers. The Bookatu team · 2026-06-06 · Grow your business · https://bookatu.com/en-nz/blog/fill-quiet-weekday-slots · markdown: https://bookatu.com/blog/fill-quiet-weekday-slots.md > **The short version** > > - Quiet weekday slots are a scheduling problem before they're a marketing one. Find where the gaps actually fall, then move demand into them. > - You don't have to discount. Make off-peak times feel like the calmer, easier option instead of the cheap one. > - Your own clients are the quickest fill. A waitlist, a rebook at checkout and a nudge to your regulars beat hunting for strangers. > - Bookatu gives you the tools to do all of this from your own branded booking page, and it takes 0% commission, so every slot you fill is yours to keep. Every appointment business has them. The dead Tuesday morning, the 2pm lull on a Wednesday, the gap between your 11am and your 3pm that never quite closes. Weekends and evenings are packed, but the middle of the week has holes in it. Those holes aren't just annoying. They're hours you're paying rent and wages for with nothing coming in. The good news is that filling them rarely means cutting prices or working longer days. It usually means moving demand you already have into the hours that need it. #### First, find your real gaps Before you fix anything, look at your week honestly. Most owners think they know their quiet times, but the pattern is usually narrower than it feels. It isn't all of Tuesday. It's Tuesday before lunch. It isn't Wednesday. It's the early afternoon once the morning rush clears. Pull up your calendar for the last month or two and notice which slots sit empty again and again. This is easy to spot when your bookings live in one place. In Bookatu your team's calendars sit together, with two-way Google Calendar sync, so the empty hours stand out instead of hiding across three different diaries. Once you can name the exact gaps, you can point everything that follows straight at them instead of spraying offers across the whole week. #### Move demand, don't try to invent it Your quiet slots are quiet because of life, not because nobody wants you. Plenty of clients are stuck at work on a Tuesday morning. But plenty of others would happily come then if it suited them. The parent with a free school-run window. The shift worker. The retiree. The person who works from home and would rather skip your packed Saturday. So the simplest move is to gently steer the flexible people into your quiet hours, and save the busy times for the folks who can only do evenings and weekends. A few ways to do that: - When a flexible client asks for a popular Saturday slot, offer them a calmer weekday one first. Plenty will take it, and it's a nicer visit anyway. - Make your weekday availability obvious on your booking page, so people see those open hours before the crowded ones. - When someone rebooks, suggest a midweek time that matches when they last came in. Habits are easy to shift if you ask at the right moment. - Group your longer or quieter jobs into the slow hours, where you've got room to take your time. #### Let your waitlist do the work Your weekends are full and your weekdays are empty. A waitlist connects the two. When a client wants a busy time that's already gone, you add them to the list, and the moment something opens, they get the offer. People who were ready to book anyway are the easiest yes you'll ever get. Bookatu includes a smart waitlist on every plan, so you can turn a Saturday no into a Tuesday yes without picking up the phone. Over a few weeks it quietly mops up gaps you'd otherwise have stared at all day. > A quiet slot isn't a slow client coming. It's a flexible one you haven't asked yet. #### Fill it without dropping your price It's tempting to slap a discount on your dead hours, but that just trains people to wait for the cheap times and chips away at what your work is worth. You can make a weekday slot more appealing without touching the price. Add a bit of extra value or certainty instead. - Offer a small perk in the quiet hours that costs you next to nothing: a longer consultation, a complimentary add-on, an unhurried session. - Sell packages and memberships, then nudge members to book their regular visits midweek where there's room. - Use gift cards and referrals to bring in new faces, and point those first visits at your open weekday times. - Run the odd promo code for one specific quiet window if you want a nudge, framed as a thank-you for being flexible rather than a permanent price cut. All of these come with Bookatu on every plan, so you can mix and match what fits. The aim is to make your quiet hours feel like the relaxed, easy option, not the bargain bin. #### Bring your regulars back a little sooner The clients most likely to fill a quiet Tuesday are the ones who already love coming to you. A lot of them simply drift a few weeks past when they meant to rebook. A friendly reminder when they're due, pointed at a midweek time, often brings them in earlier than they'd have managed on their own, and that lands right in the hours you need. Bookatu can send reminders, win-backs and retention nudges for you, and because you own your client list with no marketplace in between, you're always talking to your own people. Bringing back someone who lapsed is far cheaper and warmer than finding a stranger, and they tend to be the flexible regulars who can do a weekday anyway. #### Make booking the quiet slot effortless Half the battle is just making the gap easy to grab. If booking means calling during your busy hours or waiting for a reply, the casual midweek client gives up. A booking page that's open day and night, on your own branded link, lets someone claim a quiet Wednesday at 9pm from their sofa. Put that link in your Instagram bio, your Google profile and your email signature, so the open hours are always one tap away. Add a deposit or a card hold behind those bookings and your quiet slots fill with people who actually turn up. You connect your own Stripe, so the deposit lands in your bank, not ours. Bookatu never takes a cut of your bookings, so every weekday slot you fill is yours, all of it. Filling quiet weekday slots is rarely one big trick. It's a handful of small habits: knowing your real gaps, steering the flexible people in, leaning on your waitlist and your regulars, and keeping the booking dead simple. Together they add up to a steadier, calmer week. Pick one quiet slot you'd love to fill, point a few of these ideas at it, and watch how fast the middle of your week stops feeling so empty. ### Paper Diary to Online Booking: The Calm Way to Switch Still running your salon on a paper diary? Here's the calm, stage-by-stage way to move to online booking without losing appointments, confusing regulars, or wiping out a weekend. The Bookatu team · 2026-06-05 · Grow your business · https://bookatu.com/en-nz/blog/paper-diary-to-online-booking · markdown: https://bookatu.com/blog/paper-diary-to-online-booking.md > **The short version** > > - Keep the habit you like about your diary. Just lose the gaps it leaves. > - Switch in stages: get a booking link live, move your regulars onto it, then let it fill the quiet hours. > - Clients book themselves at 11pm without ringing you, and reminders go out so fewer slots turn into no-shows. > - Bookatu is free for 60 days, no card needed, and there's 0% commission, so you keep every penny of every booking. Your paper diary has never crashed, never logged you out, and never charged you a fee. Fair play to it. It got you here. But it can't text a client the night before, it can't take a booking while you're mid-colour, and it can only be in one place at a time. If you've ever flipped back through it squinting at your own handwriting from a mad Saturday, you already know where this is going. Moving to online booking sounds like a big leap. It isn't, if you do it in the right order. This is the calm version. No lost appointments, no clients left confused, no weekend gone setting things up. Here's how to make the switch without the drama. #### What the diary is actually costing you The diary itself is fine. The trouble is everything that happens around it. Every booking is a call or a text you have to answer, usually while you've got someone in the chair. Every no-show is a gap you find out about when nobody walks in. And it lives on your counter, so the second you step away, your business can't take a booking. Think about the calls you miss while the dryers are going, or the message that lands at 9pm when someone finally has a minute to think about their hair. Those people wanted to book. The diary just wasn't awake to catch them. > A lot of the bookings you're missing aren't lost clients. They're people who tried to reach you when you had both hands full. #### Move in stages, not all at once The mistake owners make is trying to flip everything overnight, then panicking when it feels like a lot. You don't need to. Run the diary and online booking side by side for a couple of weeks, then let the paper one quietly retire. A sensible order looks like this: - Get your booking site live first. Bookatu gives you a branded page at your own link, with your services, your prices and your hours. This is the one job worth doing properly, and it takes an afternoon, not a week. - Block out what's already booked. Copy this week and next week's appointments across from the diary, so the calendar matches reality before anyone books online. - Connect your Google Calendar. The sync runs both ways, so anything in your personal calendar blocks the slot, and new bookings show up there too. No double-bookings. - Share the link, gently. Pop it in your Instagram bio, your Google profile and your replies. You don't need a big announcement. You just make booking easier and let people find it. - Let the diary fade. Once a fortnight goes by without you reaching for it, you'll know it's safe to close the cover. Notice what you didn't have to do. No migrating years of history, no learning a complicated system, no risky big launch. You added a front door that stays open at night, and kept doing the work the way you always have. #### Your regulars won't be left behind The worry most owners have is their loyal clients, the ones who've booked the same way for years. Will they be confused? In practice, no. Your regulars keep texting and calling if they like, and you keep popping them in. Nothing forces them online. The link is just there for the people who prefer it, which turns out to be most of them once they try it. And here's the quiet win. Those clients now sit in one tidy list that belongs to you. Not a marketplace, not a middleman, yours. When a Tuesday looks empty, you can message the right people and fill it. The paper diary could never do that, because the names were stuck on the page. #### The jobs paper never could do Once you're set up, the bits you used to do by hand start happening on their own. This is the part owners tell us they wish they'd had years ago. - Reminders go out before every appointment, so the no-shows that used to cost you a chair show up far less often as empty gaps. - Deposits and card holds protect your time. You connect your own Stripe, so deposits land in your bank, not ours. Bookatu never touches your booking money. - A smart waitlist fills the holes. When someone cancels, the slot gets offered to people waiting, instead of sitting empty. - Reviews, win-backs, loyalty points, gift cards, packages, memberships and newsletters are all included, on every plan, with nothing locked behind a higher price. You don't have to switch all of that on day one. Start with online booking and reminders. Add the rest when you fancy it. It'll be sitting there waiting, because every plan includes all of it. #### What it costs, and why it's an easy yes This is usually the question at the back of your mind, so let's be plain. Bookatu is free for 60 days with no card needed, which is long enough to see real bookings come through before you decide anything. After that, plans start at $9 a month, and you're priced on active clients, the ones you've actually seen in the last 90 days, never per seat or per stylist. The bit that matters most: there's 0% booking commission. You keep 100% of every booking. The diary was cheap because it was a notebook. Online booking that pays for itself the first time it saves you a no-show, and never skims a penny off your takings, is a different kind of cheap. #### Where this leaves you You're not throwing out what works. You're keeping the rhythm of your day and handing the admin to something that's awake at 11pm, never forgets a reminder, and keeps your clients in a list you own. Start small. Get your booking link live, copy this week's appointments across, share it with a few regulars. Give it a fortnight. By then the paper diary will feel like the thing holding you back, and closing the cover for the last time will feel less like a leap and more like a relief. ### Why 0% booking commission matters for your margins A per-booking commission looks small on one appointment. Across a full year of bookings it is one of the largest invisible costs a service business carries. The Bookatu team · 2026-06-04 · updated 2026-06-10 · Grow your business · https://bookatu.com/en-nz/blog/why-zero-percent-commission-matters · markdown: https://bookatu.com/blog/why-zero-percent-commission-matters.md Booking commission is easy to ignore because it never arrives as a single bill. It is taken a slice at a time, off the top of each appointment, so it never feels like a cost you control. That is exactly why it deserves a closer look. Small percentages, repeated across every booking you take, quietly become one of the largest expenses a service business carries. #### The maths of a per-booking cut Imagine a platform takes a commission on each booking it sends you, or even on every booking you take. On a single 80 dollar appointment, a cut of a few dollars feels trivial. Now multiply it by every booking, every week, all year. The number stops looking trivial very quickly. The figures here are only an example, but the shape of the problem is real. The busier you get, the more you pay, which is a strange thing to accept. Your software cost should not climb just because you had a good month. Growth should make you more profitable, not feed a larger commission bill. #### Margins are where the damage lands Service businesses often run on tighter margins than people assume. Rent, products, wages and equipment all take their share before you keep anything. A commission that comes straight off your revenue lands directly on the part you actually get to keep. A few percent of revenue can be a far larger percentage of your profit. That is the heart of the issue. Commission is not charged on your profit, it is charged on your turnover, and turnover is always bigger than profit. So the real bite is heavier than the headline rate suggests once you trace it through to the bottom line. #### What 0% commission means in Bookatu Bookatu charges no commission on your bookings. When a client books and pays, the service revenue is yours. The platform does not take a slice of each appointment, whether the booking came through your own link or through the Discovery network where local businesses are listed. There is no per-booking fee waiting in the background. Instead, the pricing is based on your number of active clients. That keeps the cost predictable and tied to the size of your business rather than to how hard you worked in a given week. You know what you are paying, it does not jump around with your takings, and a busy month stays a profitable month. - No cut taken from each booking, so the full service price stays with you. - Pricing based on active clients, so the cost is steady and easy to plan around. - A good month rewards you, rather than quietly costing you more in commission. #### What to do with the difference The money you keep by avoiding commission is not abstract. It is real margin you can put to work. You might lower a price to stay competitive, pay your team a little more, invest in better products, or simply hold on to it as breathing room. The point is that it stays your decision instead of being skimmed off before you ever see it. When you compare booking software, look past the monthly headline and ask what happens to your money on every single appointment. A tool that takes a commission grows more expensive exactly as you succeed. A tool that takes none lets your growth flow to your own bottom line, which is where it belongs. ### How to Automate Your Salon Front Desk (Without Sounding Like a Robot) Your salon front desk is a pile of small repeating jobs eating your day. Here's how to automate bookings, reminders, deposits and the waitlist so they run themselves. The Bookatu team · 2026-06-04 · Grow your business · https://bookatu.com/en-nz/blog/automate-your-front-desk · markdown: https://bookatu.com/blog/automate-your-front-desk.md > **The short version** > > - Your front desk isn't a person. It's a pile of small jobs that keep interrupting you: taking bookings, confirming them, reminding people, chasing deposits, filling gaps. > - Turn on online booking first so clients book themselves at 11pm. Then add reminders, deposits and a waitlist as you go. > - Done right, automation feels more personal, not less. You're calmer with the client in front of you instead of half-drafting a text in your head. > - Set it up once on Bookatu and the busywork runs in the background while you stay in the chair, the treatment room or on the gym floor. You don't really have a front desk. You have a phone in your apron pocket, a notebook by the kettle, and a memory that's already full. Between clients you're confirming tomorrow, replying to a DM, and trying to remember if the 4pm ever paid their deposit. That's the actual job of a front desk in a small studio, and right now you're doing all of it by hand, usually mid blow-dry. Here's the thing: almost none of it needs you. Automating your salon front desk isn't about replacing a person. It's handing a stack of small, repeating jobs to software so they happen on time, every time, without dragging you away from the work clients actually pay for. #### Write down what your front desk actually does Before you automate anything, look at the job honestly. A front desk isn't one task. It's a dozen tiny ones that each pull you out of what you're doing. Write them out and the pattern is obvious: most are predictable, and predictable is exactly what software is good at. - Taking bookings and answering "are you free Thursday?" - Sending a confirmation so the client knows it's locked in - Reminding people the day before so they actually turn up - Taking a deposit or holding a card for bigger appointments - Rebooking the regular before they walk out the door - Filling a last-minute gap when someone cancels - Keeping client notes, contact details and history in one place Now be honest about which of those need your judgement. Reading a colour formula, working on a sore shoulder, tweaking someone's programme: that's you. Sending the third reminder of the morning is not. The first move is just deciding which jobs you're allowed to put down. #### Start with the booking itself Everything else hangs off this one change. Give your studio its own booking site at its own link, and clients book themselves whenever it suits them, which is rarely during your open hours. A lot of online bookings come in the evening, long after you've gone home, when a missed call would've cost you the appointment. With Bookatu, your booking page shows your real availability, your services and your prices, and it writes straight into your team's calendars with two-way Google Calendar sync. A slot someone books online blocks out instantly, and a personal appointment you add to your own calendar closes that slot to clients. No double bookings, no "let me check and get back to you," no phone tag. > The best hour of your week is the one where a fully booked Saturday filled itself while you slept. #### Let confirmations and reminders run themselves Once a booking exists, the next jobs are confirming it and reminding the client. These are the easiest to hand over and the ones that buy back the most time. A confirmation goes out the moment someone books. A reminder lands the day before. You don't touch either one. This is also your strongest guard against no-shows. Most no-shows aren't people ghosting you. They simply forgot, and a well-timed nudge fixes that. Keep the wording warm and plain, like something you'd actually say, and give them an easy way to reschedule. A client who can move their slot in two taps is a client who doesn't vanish on the day and leave you staring at an empty chair. #### Add deposits and a waitlist to protect the gaps Reminders catch the forgetters. Deposits and a waitlist handle everyone else. For longer or higher-value appointments, ask for a deposit or hold a card when the client books. It quietly sorts the serious bookings from the maybes. And because you connect your own Stripe, that money lands in your bank, not ours. Bookatu takes 0% commission and never touches your booking revenue, so you keep 100% of every booking. Then let a smart waitlist do the chasing you'd never find time for. When a cancellation opens up, the people waiting get offered the slot automatically, and the gap often fills before you've even noticed it appeared. That's the whole point: the awkward, time-sensitive jobs get done in the moment, not three hours later when you finally glance at your phone. #### Keep it sounding like you, not a machine Worth naming the fear: that automation makes your studio feel cold. In practice the opposite usually happens. When the admin runs itself, you're calmer and more present with the person in the chair, instead of half-listening while you draft a reminder in your head. A few small habits keep it warm. Write your messages in your own voice. Use the client's first name. Keep the personal touches that are genuinely personal, like remembering someone's wedding is coming up, and let software carry the rote stuff, like "see you tomorrow at 2." And because you own your client list on Bookatu, with no marketplace sitting between you and the people you serve, every one of those touches builds your relationship, not a platform's. You don't have to automate the lot this week. Switch on online booking first, then reminders, then deposits and the waitlist once you've found your feet. Every plan includes all of these, so you never have to change plan to reach them. Each piece you turn on is one more job that stops interrupting your day, until the front desk is quietly running itself and you're back to doing the work you opened the doors for. ### Getting paid your way: money into your account, not a platform wallet Some platforms hold your money in their wallet and pay you on their schedule. With Bookatu, booking deposits go straight into your own Stripe account. Here is why that matters. The Bookatu team · 2026-05-28 · Grow your business · https://bookatu.com/en-nz/blog/getting-paid-into-your-own-account · markdown: https://bookatu.com/blog/getting-paid-into-your-own-account.md It is an easy question to forget to ask when you choose booking software. When a client pays, where does the money actually go first? The answer matters more than it sounds, because it decides whether you control your own cash flow or someone else does. #### The platform wallet problem Some platforms collect payments on your behalf and hold the balance in a wallet of their own. They then pay you out on their schedule and their terms. In the best case it is merely a delay. In the worst case a balance can be frozen while a question is sorted out, and your cash is stuck inside someone else's system at exactly the wrong moment. #### Your own Stripe, your own money Bookatu does it the other way round. When a client pays a booking deposit, the money goes into your own Stripe account. Stripe then pays it out to your bank on a regular schedule. Bookatu never holds your deposits and never takes a cut of your bookings (see Getting paid and payouts, and Connecting Stripe for payments). - Deposits land in your own account, with no middleman sitting on your cash. - You can see every payment and when it is due to reach your bank. - Stripe pays out on its regular schedule, often every couple of business days. - Refunds are done by you, from your own Stripe dashboard. #### Why direct payment protects your cash flow Cash flow is the heartbeat of a small business. When the money you earn goes straight into your own account and pays out on a predictable schedule, you can plan with confidence. There is no platform deciding when you get to use your own takings, and no surprise hold to throw off a payroll run. #### You stay in control of refunds and disputes Because deposits run through your own Stripe account, you handle their refunds directly. If you need to give money back, you do it from your Stripe dashboard, in full or in part, on your own judgement (see Refunds and cancellation charges). A clear cancellation policy still lets you keep a deposit when someone cancels at the last minute, so being in control does not mean being out of pocket. #### Setting it up once You connect Stripe once and add your bank account so payouts have somewhere to go. You can start on a test key while you practise, with no real money moving, then switch to a live key when you are ready to take real payments. If anything looks off, our guide Stripe is not working covers the common snags (see Connecting Stripe for payments). Getting paid directly is part of a bigger idea that runs through Bookatu, which we set out in Why we built a booking platform that takes 0% commission. Your money is yours. You can start free, connect your own Stripe, and see how the plans work on the pricing page. ### Gift cards: a quiet cash-flow engine for small studios Gift cards are money in the bank today for services you deliver later, and every one you sell can introduce a brand new client to your business. The Bookatu team · 2026-05-14 · updated 2026-10-30 · Recurring revenue · https://bookatu.com/en-nz/blog/gift-cards-cash-flow-engine · markdown: https://bookatu.com/blog/gift-cards-cash-flow-engine.md Gift cards rarely get the attention they deserve. They are not flashy, and they do not feel like a marketing campaign. But for a small studio, they are one of the most useful financial tools you have. They bring in cash today for work you do later, and they quietly hand you new clients in the process. #### Cash now, work later When someone buys a gift card, it is paid for straight away. The service is delivered at some point in the future, sometimes weeks or months later, and a portion is never redeemed at all. That timing is a gift to your cash flow. A card you sell at your counter is money in your hand today, and your Finance page says where online gift card sales are paid. Holidays, birthdays and special occasions create a natural rhythm of demand. People want to give an experience rather than another object, and a treatment or session is exactly that. A studio that makes gift cards easy to buy captures that demand instead of watching it go to a department store voucher. #### Every gift card is a new client Here is the part people miss. The person buying the gift card is often already your client. The person receiving it usually is not. That means each gift card you sell can introduce someone brand new to your business, and they arrive with a built-in reason to book and a positive recommendation from a friend. If that first visit goes well, you have not just sold a one-off service. You have potentially gained a regular. Few forms of marketing deliver a warm, prepaid new client quite as neatly as a gift card does. #### How gift cards work in Bookatu Clients buy a gift card on your booking site. The value lands in the recipient's account, in their wallet, and is used automatically at their next visit. There is no code to type and nothing for your front desk to track by hand. You can also issue a gift card by hand under Catalog, Gift cards, and tick Email it to them to send it to the recipient. It is handy for in-person sales or a goodwill gesture. Because the value sits in the wallet, redemption is effortless for everyone. The client books, the credit is applied, and any remaining balance stays ready for next time. That leftover balance is itself a reason to come back, which keeps the relationship going beyond the first visit. - Online purchases are paid through Stripe, so connect Stripe first to sell them on your site. - The recipient's wallet credit applies automatically at checkout, including covering a deposit if you charge one. - Manually issued gift cards are useful for walk-ins, partnerships or saying sorry when something went wrong. #### Make them easy to find and easy to give A gift card only helps if people can find it. Put the link where buyers already are. Add it to your booking site navigation, mention it in your newsletter ahead of the holiday season, and pin it on your social profiles. The easier it is to buy in the moment someone thinks of it, the more you will sell. Keep the offer simple. A clean set of values that people can buy in seconds beats a complicated menu of options. The goal is to remove every reason to hesitate, because most gift card purchases are made quickly and on impulse. For a short holiday offer, our post Run a gift card offer with a promo code shows how to take money off the price while the card keeps its value. #### A small engine that keeps running On their own, gift cards will not transform a business. But as a steady background income that smooths your cash flow and feeds you new clients, they quietly earn their keep. Set them up once, make them easy to buy, and let them run. For the effort involved, few features in your toolkit pay back as reliably. ### Fill your calendar without discounting: rebooking and waitlists Discounts fill chairs by training clients to wait for the next deal. There is a better way to fill a quiet week: rebook before they leave, and let a smart waitlist mop up the gaps. The Bookatu team · 2026-04-23 · Recurring revenue · https://bookatu.com/en-nz/blog/fill-your-calendar-without-discounting · markdown: https://bookatu.com/blog/fill-your-calendar-without-discounting.md When the diary looks thin, the easiest reflex is to run a discount. It works once, but it quietly costs you more than the margin you give away. There is a better way to fill a quiet week, and it starts with the clients already sitting in your chair. #### Why discounting is a trap A blanket discount does three unhelpful things. It cuts the margin on clients who would have happily paid full price. It trains your regulars to wait for the next deal before they book. And it tends to attract bargain hunters rather than the loyal clients your business is built on. The quiet week comes back, and now your prices are anchored lower. #### Rebook before the client leaves the chair The single highest-converting moment in your whole week is the minute after a great visit. The client is happy, relaxed and right in front of you. That is the moment to book the next appointment, before life gets in the way. A standing rhythm of rebooked visits does more for a full calendar than any discount, and it costs you nothing. #### Let a waitlist fill cancellations automatically Gaps will still appear when someone cancels. A smart waitlist turns those gaps back into bookings. When you are full, clients can join the list, and when a slot opens you see who is waiting, ranked by how much each client spends with you, so you can offer it to your best client first (see Smart waitlist). Pair it with a clear cancellation window so late cancels reopen the slot straight away (see Cancellations and your cancellation window). #### Bring the quiet weeks forward with retention Your existing clients are the fastest way to fill a slow stretch. Automatic win-backs nudge the ones who have gone quiet, and a quick newsletter to recent or lapsed clients can turn a thin week into a busy one without spending a cent on ads (see Retention and win-backs, and Newsletters). Our post Win back lapsed clients shows how to keep those messages friendly rather than pushy. #### Reward loyalty instead of cutting prices If you want to give clients a reason to come back more often, build it into loyalty rather than discounts. Loyalty points reward repeat visits, and packages and memberships put credit in a client's wallet that pulls them back to spend it (see Wallet credit and loyalty, Packages and Memberships). To work out which recurring option fits you, read Memberships vs packages. #### When an offer does make sense There is a place for a targeted offer. A promo code for a genuinely quiet Tuesday, or a standing senior or student rate, can fill specific slots without dropping your everyday prices, and a code lets you see which promotion actually brought people in (see Promo codes and discounts). The key word is targeted. Use an offer as a scalpel, not a sledgehammer. - Rebook the next visit before the client leaves the chair. - Let the waitlist fill cancellations with your highest value clients. - Run win-backs and the occasional newsletter to wake up quiet clients. - Reward loyalty with points, packages and memberships instead of price cuts. - Keep any discount narrow and targeted, never a blanket sale. Fill your calendar with loyalty rather than markdowns and you keep both your margin and your regulars. You can set up rebooking, waitlists and loyalty on a free trial, and the pricing page shows what each plan covers, with 0% commission on every booking. ### Win back lapsed clients with automatic reminders Clients rarely leave on purpose. They drift. A well-timed reminder, sent automatically, brings them back before they settle somewhere else. The Bookatu team · 2026-04-09 · updated 2026-05-20 · Reduce no-shows · https://bookatu.com/en-nz/blog/win-back-lapsed-clients-with-reminders · markdown: https://bookatu.com/blog/win-back-lapsed-clients-with-reminders.md Most clients who stop coming did not decide to leave. Life got busy, the appointment slipped down the list, and weeks turned into months. They still like you. They just forgot to rebook. The good news is that winning them back is usually far cheaper than finding someone new. The trick is timing and consistency. A friendly message at the right moment does the work, but only if it actually goes out every time. Doing this by hand is the part that always falls over, because nobody has time to comb through a client list each week. So the smart move is to let it run automatically. #### Reminders before the visit, and nudges after There are two jobs to cover, and they are easy to confuse. The first is the appointment reminder, sent ahead of a booking so it stays top of mind. The second is the win-back, sent to a client who has not been in for a while. Bookatu handles both. Appointment reminders are on by default for new bookings. Clients get a confirmation when they book and a reminder before the visit, using your business name and the details of their appointment. Since most no-shows are simply forgotten appointments, this is the cheapest way to fill more of your schedule, and it runs without you lifting a finger. #### Spotting clients before they fully drift away Win-backs are about the people who have gone quiet. Bookatu notices when a regular has not been in for a while and can send a friendly message to bring them back. You can also see who is due a nudge under Marketing, Retention, so nobody slips through unnoticed. The reason this matters is simple. A client who has been away for two months is still warm. A client who has been away for a year has probably found somewhere else. The earlier the nudge, the better the result, and an automatic system catches the right moment far more reliably than memory ever will. #### Keep the message human A win-back does not need a heavy discount or a hard sell. Often the best message is short and warm. Let the client know you noticed they have not been in, that you would love to see them again, and make it effortless to rebook. The booking link does the heavy lifting. - Lead with the relationship, not the offer. People respond to being remembered. - Make rebooking one tap. Every message should carry your booking link straight to a free slot. - Do not overdo the frequency. One thoughtful nudge beats a stream of pushy ones. - Only message clients who agreed to hear from you, and always include an easy way to opt out. #### Birthdays, thank-yous and the quiet touches Retention is not only about people who have gone quiet. Small, well-timed messages keep your best clients feeling looked after. Bookatu can send birthday notes and thank-you messages automatically, alongside win-backs. These touches cost almost nothing and they are exactly the kind of thing a busy owner means to do but never gets around to. #### Turn a quiet week around When the diary looks thin, your existing clients are the fastest way to fill it. They already trust you, they know where you are, and many of them are simply overdue. A newsletter to lapsed clients, or a round of automatic win-backs, can turn a slow stretch into a busy one without spending a cent on advertising. Set the automatic reminders and win-backs on once, keep the tone friendly, and let the system stay in touch for you. The clients who drifted away will start drifting back, and the appointments you used to lose to forgetfulness will quietly stay on the books. ### How to actually reduce no-shows: a practical playbook No-shows are not bad luck. They are a system problem with a system fix. Here is the full playbook: reminders, deposits, a fair cancellation window and a waitlist that fills the gaps. The Bookatu team · 2026-03-19 · Reduce no-shows · https://bookatu.com/en-nz/blog/how-to-reduce-no-shows · markdown: https://bookatu.com/blog/how-to-reduce-no-shows.md Every owner has had the morning where two clients simply do not turn up. It feels like bad luck, but it almost never is. No-shows are a system problem, and that is good news, because a system can be fixed. Stack a few simple defences together and an empty chair stops being a regular event. #### Start with reminders, because most no-shows are forgotten The biggest single cause of a no-show is a forgotten appointment. So the cheapest win is an automatic reminder. In Bookatu, clients get a confirmation when they book and a reminder before the visit, using your business name and the details of their booking. Reminders are on by default for new bookings, so this runs without you lifting a finger (see Automatic reminders). #### Add a deposit to turn a hold into a commitment Reminders fix forgetfulness. A deposit fixes the casual booking that was never really firm. When a client pays a little upfront, the appointment stops feeling disposable. The deposit is charged through Stripe when they book online and comes off their final bill, so they are not paying extra, just paying part of it sooner (see Deposits). We go deeper on this in How deposits stop no-shows. #### Protect your best clients with the No-show shield The worry with deposits is always the same. Will it annoy the loyal regulars who would never miss? The No-show shield solves this. It looks at each client's history and only asks for a deposit from new clients or anyone with past no-shows. Your best clients keep a friction-free booking, and you put a gate only in front of the bookings that actually carry risk (see No-show shield). #### Set a fair cancellation window A cancellation window is the notice you ask for before a client changes or cancels. Set it once, and clients see the policy when they book and again in their confirmation. If someone cancels inside the window, the deposit can be kept, and the slot reopens automatically. The point is to be clear up front so there are no surprises later (see Cancellations and your cancellation window). #### Fill the gap with a waitlist Even with every defence in place, the odd cancellation will happen. A waitlist makes sure it does not cost you. When you are fully booked, clients can join the list, and when a slot opens you can offer it to your highest value client first. A cancellation stops being lost money and becomes a chance to reward a good client (see Smart waitlist). There is more on this in Fill your calendar without discounting. #### Win back the ones who slipped away Some no-shows are really the start of a client drifting off. Automatic win-backs catch them. Bookatu notices when a regular has not been in for a while and can send a friendly nudge to bring them back before they settle somewhere else (see Retention and win-backs). Our post Win back lapsed clients covers how to keep the message warm. #### Put it together - Leave automatic reminders on, so forgotten appointments stop happening. - Turn on deposits, then switch on the No-show shield to protect your loyal regulars. - Set a clear cancellation window so the policy is fair and visible. - Let the waitlist fill any gaps with your best clients. - Run automatic win-backs so quiet clients drift back instead of away. Each piece is small. Together they change the feel of your whole week. You can set all of this up on a free trial and watch your no-show rate over the first month. See how the plans work on the pricing page, with no commission on your bookings. ### Memberships vs packages: which recurring revenue fits your business Both bring in cash upfront and pull clients back. But they suit different businesses. Here is how to tell which one fits the way you actually work. The Bookatu team · 2026-03-05 · updated 2026-04-28 · Recurring revenue · https://bookatu.com/en-nz/blog/memberships-vs-packages · markdown: https://bookatu.com/blog/memberships-vs-packages.md Predictable income is the thing every service business wants and few feel they have. One week is packed, the next is quiet, and cash flow lurches around with it. Memberships and packages are the two tools that smooth this out. They both bring money in sooner and give clients a reason to keep coming back. They are not the same thing, though, and choosing the wrong one for your business can leave money on the table. #### What a package is A package is a prepaid bundle. A client pays an amount upfront and gets a larger amount of credit to spend with you. For example, they pay 200 dollars and receive 250 dollars of credit. That credit sits in their wallet in Bookatu and is used automatically at their next visits until it runs out. Packages suit a course of treatment or a run of visits that has a natural end. Think a series of facials, a block of training sessions, or a set of treatments that work best done in sequence. The client commits to coming back several times, you get the cash upfront, and there is no ongoing charge to manage. #### What a membership is A membership is a recurring monthly plan. It charges the client every month and can give them monthly credit and perks. It keeps charging until the client cancels. This is the model behind gyms, regular blow-dry plans, and any service people use month after month. The appeal is steady, predictable income. Instead of hoping a client rebooks, you have an agreed monthly relationship. Clients start to feel like members rather than one-off visitors, and that sense of belonging tends to keep them loyal for longer. #### How to choose between them The honest answer is that it depends on how your clients actually use you. A few questions usually make it clear. - Do clients visit on a regular monthly rhythm, or in bursts with gaps in between? Regular rhythm leans towards memberships. Bursts lean towards packages. - Does your service have a natural course or end point? A set of treatments suits a package. An open-ended habit suits a membership. - Do you want ongoing monthly income, or a lump of cash now without managing recurring charges? Memberships give the former, packages the latter. - How comfortable are your clients with a subscription? Some happily sign up to monthly plans. Others prefer to pay for a bundle and be done. Plenty of businesses run both. You might sell a package for a course of treatment and a membership for the clients who come in like clockwork. There is no rule that says you have to pick one. #### Why upfront credit pulls clients back Both options share a quiet advantage. Once a client has credit sitting in their wallet, they are far more likely to come back and use it. The money is already spent, so visiting feels free, and unused credit is a gentle reason to book again. In Bookatu, this wallet credit is applied automatically when a client books or pays, and it can even cover a deposit so they need no card at the time. That automatic behaviour matters. The client never has to remember a code or do any maths. They book, the credit is used, and the experience just works. For you, that means the money you collected upfront keeps doing its job of bringing people through the door. #### Setting them up Both live under Sales in Bookatu. For a package, you set the price and the credit value the client receives, then they buy it from the Packages link on your booking site. For a membership, you set the monthly price, any monthly credit, and the perks, and clients join from the Memberships link. Memberships need Stripe connected, since they charge a card every month. Start with the model that matches how your best clients already behave. If they come in monthly, offer a membership and give them a reason to commit. If they come in courses, build a package that rewards buying the whole run. Either way, you trade an unpredictable diary for income you can actually plan around. ### Your clients are yours: why your salon should own its client relationships On a marketplace, your regulars are not really yours. They are the platform's, rented back to you through fees and ads. Here is why owning the relationship changes everything. The Bookatu team · 2026-02-26 · Grow your business · https://bookatu.com/en-nz/blog/your-clients-are-yours · markdown: https://bookatu.com/blog/your-clients-are-yours.md Think about the client who has come to you for years. They know your name, you know their coffee order, and they would not dream of going anywhere else. Now ask a simple question. If you booked them through a marketplace, who does that relationship actually belong to? The uncomfortable answer is that it may not be you. #### How marketplaces quietly take the relationship A marketplace sits in the middle. It often owns the contact details, the messages and the reviews. It can charge you a new-client fee even for someone who was already your regular, simply because they tapped through the app. And it can advertise a competitor to your own client at the exact moment they open the page to book with you. None of this is an accident. The marketplace business model is built on standing between you and the people you serve. The relationship is the product, and you are renting access to your own clients. #### What owning the relationship really means Owning the relationship is not complicated. It just means a few things stay with you rather than with a platform. - You hold your clients' contact details, so you can reach them directly. - Messages come to your own inbox, not a channel the platform controls (see Inbox and channels). - Reviews build your reputation, on your own Google profile (see Reviews and the Google flywheel). - Nobody advertises a competitor to your client while they are trying to book you. #### Why it is worth more than it looks A loyal client list is the single most valuable asset a service business has. It is what lets you fill a quiet week with one message, launch a new service to people who already trust you, and ride out a slow season. If that list lives inside someone else's app, the value sits with them, not with you. The day you want to leave is the day you find out how much you really owned. #### How Bookatu keeps your clients yours With Bookatu you get your own branded booking page at your own link (see Your booking page). Clients book with you, not with a marketplace. Their messages land in your inbox, their reviews go to your Google profile, and their details stay in your client list. We never sell your clients back to you, and we take no commission on a single booking. We do run a Discovery network, a shared page where people can find local businesses, but it works for you, not against you. It lists your business with no commission and sends the client straight to your booking page, rather than putting a rival in front of them (see The Discovery network). #### And if you ever want to leave Owning the relationship also means you are never trapped. Your data is yours, and you can export your client list whenever you like (see Exporting your data). If you are coming from a marketplace right now, our guide Leaving Fresha or Booksy walks through how to switch without losing a single regular. Your clients chose you, not a platform. It is worth building your business on software that remembers that. You can start free and keep your client relationships where they belong, and the pricing page shows exactly what you would pay, with no cut taken from your bookings. ### How deposits stop no-shows (and what an empty chair really costs) A no-show is not just a missed appointment. It is paid time you cannot get back. Here is how a small deposit changes client behaviour without scaring anyone off. The Bookatu team · 2026-02-12 · updated 2026-05-02 · Reduce no-shows · https://bookatu.com/en-nz/blog/how-deposits-stop-no-shows · markdown: https://bookatu.com/blog/how-deposits-stop-no-shows.md Every service business knows the feeling. A client books a Saturday slot, you turn other people away, and then nobody arrives. The chair sits empty, your stylist or therapist is paid for the hour, and the day is quietly less profitable than it should have been. Most no-shows are not malicious. People forget, plans change, and a free booking feels easy to drop. The fix is not to be harsh with clients. It is to add a small, fair piece of commitment at the point of booking. That is what a deposit does. #### What an empty slot actually costs you It helps to put a real figure on the problem, even a rough one. Take your average service price and the number of slots you lose in a typical week. As an example, if you lose three appointments a week at an average of 80 dollars each, that is 240 dollars a week that walked out the door. Over a year that adds up to a meaningful number, and none of it came with a warning. The hidden cost is bigger than the price of the service. A no-show also blocks the slot from someone who would have turned up, and it throws off the rhythm of your day. When you measure the loss honestly, a deposit stops feeling awkward and starts looking like basic protection for your time. #### How a deposit changes behaviour When a client pays something upfront, the appointment stops being disposable. They have skin in the game, however small. A deposit of 20 dollars, or a set percentage of the service, is usually enough to make people show up or give you proper notice if they truly cannot make it. In Bookatu, the deposit is charged through Stripe when a client books online, and it comes off their final bill. They are not paying extra. They are simply paying part of what they owe sooner. That framing matters, because it keeps the policy feeling fair rather than punishing. #### Setting deposits up without losing good clients The worry every owner has is the same. Will asking for a deposit put off the loyal regulars who would never miss an appointment? It is a fair concern, and Bookatu gives you two ways to handle it. - Charge every online booking a flat amount or a percentage. Simple and consistent, good if no-shows are a steady problem across the board. - Turn on the No-show shield instead. It looks at each client's history. Loyal regulars with a clean record book with no deposit, while new clients or anyone with past no-shows are asked to pay one. The No-show shield is the option most established businesses reach for. Your best clients keep a friction-free booking experience, and you only put a gate in front of the bookings that actually carry risk. You protect the calendar without sending the wrong message to the people who keep you in business. #### Pair deposits with a clear cancellation window Deposits work best alongside a cancellation window, which is the amount of notice you ask for before a client changes or cancels. Set that window in your settings, and clients see the policy when they book and again in their confirmation. If someone cancels inside the window, the deposit can be forfeited, and the slot reopens for your waitlist automatically. None of this needs to feel cold. The point is to be clear up front, so there are no surprises later. A client who knows the rules at the moment of booking is far less likely to be upset by them. #### Getting started To take deposits you need Stripe connected, since that is what securely charges the card. Bookatu never sees card numbers. Once Stripe is connected, you turn on deposits in settings, choose a flat amount or a percentage, and decide whether to charge everyone or only riskier bookings with the No-show shield. Start small. Even a modest deposit changes the feel of a booking from a casual hold to a real commitment. Watch your no-show rate over the first month, then adjust the amount if you need to. Most owners find they never go back. ### Getting found online: the local SEO and reviews flywheel When someone nearby searches for your service, you want to be the business they find. Here is how reviews, a complete profile and a fast booking page work together. The Bookatu team · 2026-01-22 · updated 2026-04-15 · Grow your business · https://bookatu.com/en-nz/blog/local-seo-and-reviews-flywheel · markdown: https://bookatu.com/blog/local-seo-and-reviews-flywheel.md When someone in your area searches for a haircut, a massage or a personal trainer, a short list of businesses appears. Being on that list is worth a great deal, because those searchers are ready to book right now. Getting there is not magic. It is the result of a few habits that reinforce each other over time, which is why people call it a flywheel. #### How the flywheel turns The idea is simple. Good service leads to happy clients. Happy clients leave reviews. Reviews help you get found by new people. New people become clients, and if you serve them well, they leave reviews too. Each turn makes the next one easier. The hard part is getting it started and keeping it moving. Most owners stall at the review step. They do great work but rarely ask for a review, so the flywheel never builds momentum. The fix is to make asking automatic, so it happens after every visit without you having to remember. #### Make reviews happen on their own Bookatu can send a review request after an appointment is completed. If the client is happy, you can point them to your Google page, where recent reviews are one of the biggest things that help you get found by new local clients. If the feedback is not positive, it stays private so you can put things right before it ever becomes public. This setup respects both sides. Clients who had a great time are nudged to share it where it counts, and clients who had a problem get a private channel to tell you. You collect more positive reviews and you hear about issues early, which protects your reputation in both directions. #### A complete profile does a lot of quiet work Search engines and AI assistants can only recommend you if they understand who you are. That means filling in the basics properly. Your business name, address, opening hours and full list of services all help search engines and assistants understand what you offer and when you are open. Every Bookatu booking page ships with the right titles, descriptions and structured data so this information is laid out in a way machines can read. You do not need to know how any of that works. You just need to fill your profile in completely and keep it accurate, and the page does the technical part for you. - Fill in your business name, address, hours and services completely. Gaps are missed opportunities. - Add real photos of your space and your work. They build trust and make you stand out. - Collect reviews steadily, since recent activity tends to matter more than a pile of old ones. - Share your booking link everywhere, on Instagram, in your email signature and on your Google profile. #### The booking page has to be fast and easy Getting found is only half the job. Once someone lands on your page, they need to be able to book in seconds, or they leave. A clean booking page that shows real availability and lets a client confirm a time quickly turns a visitor into an appointment. A slow or confusing one sends them straight back to the search results to try the next business. This is where the whole flywheel pays off. You get found, the client books without friction, you do great work, and they leave a review that helps the next person find you. The page being quick to use is what keeps the wheel from slipping at the most important moment. #### Ready for how people search next Search is changing. More people now ask an AI assistant to find or book a service for them, rather than scrolling a list of links. A complete, well-structured booking page gives those assistants the information they need to put you forward. The same habits that help you rank in search today, a full profile and steady reviews, also prepare you for the way people will search tomorrow. None of this is a one-off task. It is a routine. Keep your profile current, keep collecting reviews after every visit, and keep your booking link in front of people. Do that consistently and the flywheel keeps turning, bringing new clients to your door without a steady spend on advertising. ### Why we built a booking platform that takes 0% commission Most booking platforms get cheaper for them and more expensive for you the busier you get. We built Bookatu the other way round. Here is the thinking behind 0% commission. The Bookatu team · 2026-01-09 · Grow your business · https://bookatu.com/en-nz/blog/why-we-built-a-zero-commission-booking-platform · markdown: https://bookatu.com/blog/why-we-built-a-zero-commission-booking-platform.md When we started building Bookatu, we talked to a lot of salon, spa, studio and clinic owners. Different trades, different countries, but the same quiet complaint kept coming up. Their booking software took a cut of their own success. The harder they worked, the more it cost them. That did not sit right with us, so we built the opposite. #### The model we did not want to build The big marketplaces are clever. They are free to join, which feels generous, and then they earn from the relationship you bring them. New-client fees, a slice of each payment, and ads that put a rival in front of your own regulars at the very moment they go to book. The platform grows by sitting between you and your client. The deepest problem is the shape of it. When a platform earns a percentage of every booking, your software bill climbs in lockstep with your takings. A great month quietly costs you more. Growth turns into a tax. We wrote about the maths of this in Why 0% booking commission matters for your margins, and the numbers are worse than they first look. #### What 0% commission actually means Bookatu takes no commission on your bookings. When a client books and pays, the service revenue is yours, in full. It does not matter whether the booking came through your own link or through the Discovery network where local businesses are listed. There is no per-booking fee waiting in the background, ever. - No cut is taken from any booking, so the full service price stays with you. - Money from deposits and sales goes into your own account, not a platform wallet (see Getting paid and payouts). - A busy month rewards you, instead of quietly costing you more. #### So how do we keep the lights on We charge a simple subscription instead. It is based on how many active clients you have, not on how many staff you add. Every plan includes all the core booking features, and a few optional add-ons cost extra. That keeps the cost predictable and tied to the size of your business rather than to how hard you worked in a given week. You can see what each plan covers on the pricing page. This is a deliberate choice about incentives. Because we do not earn from your bookings, we have no reason to insert ourselves into your client relationships. The only way we succeed is if the software is good enough that you choose to stay. Our interests and yours point in the same direction. #### The promise underneath it Zero commission is really one part of a bigger idea. Your clients are yours, your money is yours, and your data is yours. We dig into the first of those in Your clients are yours, and into the second in Getting paid your way. If you ever decide to leave, you can export everything and walk out the door with your client list in hand (see Exporting your data). If a tool that backs your independence rather than taxing it sounds like the way it should have always been, you can start free and try the whole thing for yourself. Have a look at the pricing page to see how the plans work, with no commission on a single booking. ## Engineering Every post on the engineering blog in full, newest first: how the platform is built. ### One tool registry behind an MCP server, a REST API and an assistant Software can act on a Bookatu business three ways: an AI app over MCP, a developer's code over REST, and the owner's own assistant in the admin. Each used to keep its own list of tools, and their checks drifted apart. Here is how one registry entry per tool now feeds all three, and how we moved to it before changing any behaviour. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/one-tool-registry-behind-an-mcp-server-a-rest-api-and-an-assistant · markdown: https://bookatu.com/engineering/one-tool-registry-behind-an-mcp-server-a-rest-api-and-an-assistant.md > **The short version** > > - Each tool is one registry entry: its name, description, input schema, API scope, the permission its admin screen asks, whether it reads or writes, and the REST endpoint that does the same. > - Handlers are joined to entries when the module loads. A missing handler, or a handler with no entry, fails the build. > - One runner runs every call on every product in a fixed order, and marks every audit row with the product and the tool. > - Each product keeps its own transport and its own way of checking who is calling. > - A parity test fails when an entry is missing from a product, unless it sits on a named list with a reason. There are three ways for software to act on a Bookatu business. A connected AI app talks to our MCP server. A developer's code calls the v1 REST API. The owner can ask the assistant inside the admin. All three end up doing the same jobs, such as adding a product or moving a booking. They were built at different times, and each kept its own list of tools. The MCP route declared its tools inline. The REST API had its own route handlers. The assistant had its own dispatch table. Each list carried its own checks. Checks kept in three places drift. #### How the drift showed up The clearest case was the person behind an API key. On MCP, a key may never do more than the person who made it may do on that tool's own admin screen. If that person lost the permission, or left the team, the key's writes stopped. The REST route for the same action asked only whether the key held the scope. So an older key could keep doing on REST what MCP had already refused it. The second case was the own-column rule. Some team members may only see their own column of the calendar. MCP held their keys to it. The REST route for the same action did not, so the same key reached anyone's booking there. Neither bug came from a hard problem. Both came from one rule written twice and then changed once. #### One entry per tool The fix was to make the tool the unit, not the product. Each tool is now an entry in one registry, and the entry carries everything a product, a docs page or a test needs to know about it. Simplified, an entry looks like this: ```ts type Channel = "mcp" | "rest" | "assistant"; interface ToolSpec { name: string; title: string; // owner words, also the MCP title description: string; // written for the model inputSchema: JsonSchemaObject; scope: ApiScope; // what an API credential must hold permission: Permission | null; // what the tool's admin screen asks of a person access: "read" | "write"; destructive?: true; // changes or removes something already there openWorld?: true; // emails a client, calls out, or publishes rest?: { method: "GET" | "POST" | "PATCH" | "DELETE"; path: string }; column?: "bookingId"; // acts on one booking: held to the caller's column audit?: (args: Args, result: unknown) => AuditRow | null; } ``` Specs are plain data with no server imports. The developer docs, the OpenAPI file and the MCP annotations read them without loading a database driver. Handlers live in server files and are joined to the specs once: ```ts export function joinHandlers(specs: readonly ToolSpec[], handlers: Record): Tool[] { const tools = specs.map((spec) => { const handler = handlers[spec.name]; if (!handler) throw new Error(spec.name + " has no handler"); return { ...spec, handler }; }); const extra = Object.keys(handlers).filter((n) => !specs.some((s) => s.name === n)); if (extra.length) throw new Error("handlers with no entry: " + extra.join(", ")); return tools; } ``` This runs when the module loads. A typo fails the build and the tests. It is never found by a caller. #### One runner Every call, from any product, goes through one function. The order matters, and it is the same everywhere: ```ts export function runTool(tool: Tool, ctx: ToolContext, args: Args): Promise { return withToolMark({ channel: ctx.channel, tool: tool.name }, async () => { await assertInColumn(ctx, tool, args); // the own-column rule if (isDryRun(tool, args)) return dryRunPreview(ctx, tool, args); return withIdempotency(ctx, tool, args, async () => { const own = handlerArgs(tool, args); // the tool's own arguments only const result = await tool.handler(ctx, own); recordToolAudit(ctx, tool, own, result); return result; }); }); } ``` withToolMark puts a small value in AsyncLocalStorage for the length of the call. The audit logger reads it. So every row recorded during the call gets two extra changes: the product it came through and the tool that ran. That holds for rows the tool writes itself and for rows written deep inside a shared library it calls. The Audit log page reads them back, for example as made through a connected AI app, with the tool's name beside it. Some writes recorded no audit row at all before, such as a few catalog and content changes. Their entries now carry an audit function, and the runner records the row for them. Dry runs and idempotency keys are answered here too, once, so no handler has to implement them. Our posts Dry runs that never write and Idempotency keys that survive a cut-off request cover those two steps. #### What each product keeps The registry does not try to be a transport. Each product still owns what is truly different about it. - MCP keeps JSON-RPC, its credential checks for an API key or a connected app, the scope and read-only gates, and its rate limits. tools/list is built from the entries, with titles and annotations from the same fields. - REST keeps the v1 conventions: the key in a header, the error envelope, paging with limit and cursor. A new tool's route file is one line: export const POST = registryRoute("create_product"). - The assistant asks the signed-in person's permission on the business's own role grid before a write, and a person confirms on a card. What it may propose at all is its own list, kept in code. Our post The allowlist is the boundary explains why. - Each answers a refusal the way its callers expect: a tool error the model reads on MCP, an HTTP status and an error code on REST, a sentence in the chat. The context a handler receives has the same shape on every product. MCP and REST fill it from the credential and the person who made it. The assistant fills it from the signed-in person. The handler does not know which. #### Routes that already existed Many tools already had a REST endpoint with its own handler and its own exact answers. Integrations depend on those answers, down to the error messages some code matches on. Rewriting them through the new path would have changed them. So those routes keep their handlers, and are wrapped. The wrapper acts only on a call the route itself would let through. Anything the route refuses, it still refuses, word for word. ```ts export function registryGated(name: string, inner: RouteHandler): RouteHandler { const spec = toolSpec(name); return async (req, routeCtx) => { const key = await verifyApiKey(req); // Anything the route would refuse, it refuses itself, as before. if (!key || !(await keyHoldsScope(key, spec.scope))) return inner(req, routeCtx); const maker = await keyMaker(key); const refusal = await screenRefusal(spec, maker); // the same check MCP makes if (refusal) return apiFail(refusal.message, 403, refusal.data); return withToolMark({ channel: "rest", tool: name }, () => inner(req, routeCtx)); }; } ``` The real wrapper also applies the own-column rule, dry runs and idempotency keys. For the own-column rule it hands the route an id that cannot exist. A booking outside the caller's column then gets the route's own not found answer, in the route's own words, and nothing runs. #### A pure move first We did this in two steps. The first moved every tool into the registry and changed nothing. Before it, we wrote characterization tests that captured what each product answered, from every byte of tools/list to every refusal. The move had to pass them unchanged. Only then did later steps change behaviour, such as holding REST keys to their maker's permission. Each change was marked as deliberate in the tests it touched, with a note on why. That split is what made review possible. A diff that moves two thousand lines and changes behaviour is unreadable. A diff that moves two thousand lines and passes the old snapshots is boring, which is what you want. #### The parity test A registry is only shared if every product actually uses it. A test holds that: - Every entry is served by MCP, REST and the assistant, or sits on a named exception list with a reason. - Every MCP entry names its REST endpoint. The test finds the route file at that path, checks it exports that method, and checks the route asks the entry's own scope. - Every server action on an admin screen is covered by a tool, or by a guide entry that gives the steps and a link to the screen, or is on a list of things never done through an AI. - The number of gaps is pinned. It may go down. It cannot go up without someone editing the test. The last point does the work. A new admin feature fails the build until someone decides how AI and API callers reach it. #### How this differs from shared booking rules Our post One rule, every door is about a different layer. There, the rules of a booking, such as which services may share a visit, live in one function that the booking page, the staff form, REST, MCP and mobile all call. That keeps the answer the same wherever a booking is made. This post is about the layer above it: the gates a caller passes, and the record left behind. The booking rules keep a booking right. The registry keeps the gates in front of it the same. #### Trade-offs - An entry is bigger than a function signature. A new tool needs its scope, permission, REST path and audit row decided up front. That is the point, but the first tool in a new area is slower to add. - Specs and handlers live in separate files, so the MCP route never loads the assistant's code and the docs load neither. You trade one file per area for two. - Some differences are real and stay. The assistant confirms with a person on a card. MCP and REST have no card, so a caller there checks first with a dry run and retries safely with an idempotency key. - Wrapping the old routes keeps their answers stable, but REST has two code paths until those routes are retired. #### What we take from it - Make the tool the unit, and let each product be a thin adapter around it. - Fail at load, not at request time, for anything structural. - Move first and change second. Keep the snapshot tests that prove the move. - A parity test that only lets the gap shrink is worth more than a checklist. ### Idempotency keys that survive a cut-off request Our REST API and MCP server take an idempotency key on the writes they share, so a retry never creates the same thing twice. Then we found that the case the keys exist for was the one they handled worst: a request cut off halfway locked its key for a whole day. Here is the lease that fixed it, and the other rules that make a retry safe. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/idempotency-keys-that-survive-a-cut-off-request · markdown: https://bookatu.com/engineering/idempotency-keys-that-survive-a-cut-off-request.md > **The short version** > > - A write may carry a key the caller chooses. The same key with the same request within 24 hours gets the first call's answer back, and nothing runs again. > - The key is claimed with one insert on a unique index before the write runs, so two retries that race run the write once. > - A claim with no answer that is older than any request can run was cut off. The next retry takes it over with one conditional update. > - A write that was made is answered as made, even if storing its answer fails. A write that was refused frees its key. > - Every refusal carries a code and says what to do next, in a form an AI client reads. Writes to a booking API get retried. A client gives up at ten seconds while the server finishes at eleven. An AI agent decides its last call probably failed and sends it again. Without protection, either can make a second booking or a second product. The usual answer is an idempotency key, the pattern Stripe made familiar. The caller sends a unique key with the write. The server remembers the key and the answer. A retry with the same key gets the same answer, and nothing runs twice. Our REST API takes the key as the Idempotency-Key header. Our MCP server takes it as an idempotencyKey argument on every write. Both use the same stored rows. #### Claim first, then run The order is the whole design. The key is claimed before the write runs, with one insert that a unique index can refuse: ```ts const claimed = await db .insert(idempotencyKeys) .values({ orgId, credentialId, key, tool, requestHash, expiresAt: addHours(now, 24) }) .onConflictDoNothing() .returning({ id: idempotencyKeys.id }); if (claimed.length > 0) return { kind: "new", id: claimed[0].id }; ``` The unique index covers the business, the credential and the key. Two integrations can both use keys like order-1 and never collide. If the insert lands, this request owns the key and runs. If it does not, someone already holds it, and we read the row to find out what that means. The request hash is a SHA-256 of the tool's name and the tool's own arguments as canonical JSON, with the keys sorted, so the same request always hashes the same. The same key with a different hash is a mistake by the caller, and we say so instead of guessing: ```ts if (held.tool !== tool || held.requestHash !== hash) { throw refusal("IDEMPOTENCY_KEY_REUSED", "That key was used for a different request in the last 24 hours. Use a new key for a new change."); } if (held.status !== null) { // The first call finished: answer what it answered. return { kind: "replay", status: held.status, response: held.response }; } ``` A replay on REST carries an Idempotent-Replayed: true header, so the caller can tell it apart from a fresh write. A refusal on REST is a 409. On MCP it is a tool error with its code, which the model reads and acts on. A protocol error would only reach the client software, not the model. #### The case we got wrong A row with no answer yet means a request is still running. Our first version answered every retry in that state with IDEMPOTENCY_IN_PROGRESS: try again in a moment. That is right while the first request is alive. Now cut the first request off. A function hits its time limit, or a deploy replaces it mid-request. Either way the code that stores the answer, or frees the key, never runs. The row stays as it was, with no answer, until it expires. Ours expired after 24 hours. So the request most likely to be retried, the one that died halfway, was the one whose retries were refused for a full day. Each retry was told to try again in a moment, and every moment said the same. > A retry key that cannot tell a slow request from a dead one punishes the caller for the server's crash. #### A lease, not a lock The fix is a lease. A claim with no answer is trusted to be running only for as long as a request could possibly run. We set the lease a little longer than the longest time limit any of our functions has, so a live request is never taken over. Past that, the claim was abandoned. A retry that finds an abandoned claim takes it over. Two retries arriving together must not both win. One conditional update handles that: ```ts if (held.status === null) { const abandonedBefore = new Date(now.getTime() - LEASE_MS); if (held.createdAt <= abandonedBefore) { const taken = await db .update(idempotencyKeys) .set({ createdAt: now, expiresAt: addHours(now, 24) }) .where(and( eq(idempotencyKeys.id, held.id), isNull(idempotencyKeys.status), // still no answer lte(idempotencyKeys.createdAt, abandonedBefore), // still that old )) .returning({ id: idempotencyKeys.id }); if (taken.length > 0) return { kind: "new", id: taken[0].id }; } throw refusal("IDEMPOTENCY_IN_PROGRESS", "A request with this key is still running. Try again in a moment."); } ``` The where clause repeats the conditions we just read. When two updates race for the same row, Postgres makes the second wait for the first, then checks the where clause again against the row as the first left it. The first retry resets created_at and gets the row back. The second now sees a fresh created_at, matches nothing, and is told the request is in progress, which by then is true. Taking a claim over resets its clock, so the new attempt gets a full lease of its own. #### When storing the answer fails There is a quieter way to lose the answer. The write succeeds. Then the update that stores its answer fails, because the database hiccuped at that exact moment. What should the caller hear? Our first version returned the error and freed the key. That sounds reasonable and is the worst choice. The caller sees a failure, retries with the same key, finds it free, and makes the change a second time. Now the write is answered as made, because it was. The key is not freed. It stays claimed with no answer, so a quick retry is told the request is in progress: ```ts async function keepAnswer(id: string, status: number, response: unknown): Promise { try { await db.update(idempotencyKeys).set({ status, response }).where(eq(idempotencyKeys.id, id)); } catch (e) { // The change is done, so the caller still gets its answer. // The key stays claimed, and lapses after the lease. log.error("could not keep the answer of a change that was made", e); } } ``` Once the lease runs out, a retry can take the claim over and run again. So this case can still repeat a change, but only after a long gap, and only after two faults in a row. Freeing the key at once made a repeat the normal outcome. #### When the write is refused The opposite case is simple. If the write itself is refused, say the time was taken a second earlier, nothing changed. Keeping that refusal would stop a corrected retry from ever running under the same key. So a refusal deletes the claim, and the next try runs afresh. A dry run never claims a key at all. It changes nothing, so there is nothing to protect. #### Keeping it tidy A stored answer can hold personal data, such as the email address of a client the call just added. So keys are not kept past their 24 hours. A claim deletes its own expired row before it inserts, so an old key is free again at once. A daily job deletes every other expired row. #### Testing it The lease is easy to get almost right, so the tests set the clock instead of waiting. A claim with no answer that is a minute old must still be in progress. One older than the lease must be taken over, on MCP and on REST, run the write once, and answer the next retry as a replay. And when storing the answer fails, the call must still be answered as made, and a quick retry must not make the change again. Our post Idempotent webhooks: making sure the money only moves once covers the other direction: the same event reaching our server twice from a payment provider. That one is keyed on the provider's event id. This one is keyed on the caller's own key. #### What we take from it - Claim before you run, with an insert a unique index can refuse. - A claim with no answer needs an end. Make it a lease just longer than any request can live. - Take a claim over with one conditional update that repeats the conditions you read. - Answer a change that was made as made, and never free its key on the way out. - Free the key when the write is refused, so a fixed request can be retried. ### MCP structured output and tool annotations in a real booking server Our business MCP server lets a connected AI app read and change a business's bookings and catalog. We moved it onto the newer protocol features. Here is what tool annotations and output schemas changed in practice, and how clients written for the old protocol kept working unchanged. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/mcp-structured-output-and-tool-annotations-in-a-booking-server · markdown: https://bookatu.com/engineering/mcp-structured-output-and-tool-annotations-in-a-booking-server.md > **The short version** > > - Every tool has a title and states every hint, true or false: readOnlyHint, destructiveHint and openWorldHint. None is left to the protocol's default. > - Every read tool declares an outputSchema and returns structuredContent beside the JSON text it always returned. Writes declare none. > - A schema says only what is true of every answer, and leaves extra properties open, so adding a field later breaks no client. > - A tool's own refusal, such as a time that was just taken, comes back as an isError result with a code. Auth, scope and rate-limit refusals stay protocol errors. > - A client that sends no protocol version header keeps the text answers and the errors it always had. The business MCP server is how a connected AI app works with a Bookatu business. It can make a booking or add a product, within the scopes the business gave it. For a long time it spoke the 2024-11-05 version of the protocol, and every answer was one block of JSON text. The server now negotiates 2025-06-18, 2025-03-26 or 2024-11-05. A client that asks for one of those gets it. A client that asks for anything else gets the newest of the three. A few additions from those versions changed how clients use our tools. #### Annotations: say every hint out loud Annotations are hints a client uses to decide how careful to be. readOnlyHint says a tool changes nothing. destructiveHint says a write may change or remove something already there. openWorldHint says the tool reaches beyond the server's own data. The defaults are the part people miss. For a tool with no annotations, the protocol assumes the worst: not read-only, destructive and open-world. That is a sensible default for a tool nobody knows. It is a poor description of one you wrote. Unannotated, adding a yoga mat to a catalog looks as risky as cancelling a client's lesson, and a client that asks before every risky call asks before every call. So every tool sends every hint, read straight off its registry entry: ```ts function annotationsFor(spec: ToolSpec) { return { title: spec.title, readOnlyHint: spec.access === "read", destructiveHint: spec.destructive === true, openWorldHint: spec.openWorld === true, }; } ``` Destructive marks a write that changes or removes what is already there: cancel, decline, reschedule, update, unpublish, mark attendance. Making something new is not destructive. Open-world marks any tool that emails or texts a client, calls an outside URL, or publishes to the public web. Our first list of open-world tools was written by hand, and review found it missed some. Cancelling a visit emails the client. Publishing a blog post puts it on the public web. Neither was marked, and a client that trusted the hint would have let them run without asking. The hints now come from fields on each tool's entry, and a test reads the tools as tools/list serves them and checks each one against the rule. A tool whose description says the client is emailed must say openWorldHint: true. Hints are not enforcement. A client may ignore them, and the server still checks the scope and the permission on every call. They exist so a careful client can ask the person at the right moments, and not at every moment. #### Output schemas: promise only what is always true Since 2025-06-18 a tool can declare an outputSchema and return its answer as structuredContent that fits it. The appeal is clear: a client gets typed data instead of parsing text. The catch is in how clients use it. A client validates structuredContent against the schema, and if it does not fit, the client discards the answer. A schema that is a little too strict does not fail gently. It turns a working tool into a broken one, for one business, on the day one field happens to be empty. So our schemas follow a few rules: - List the top-level keys, and mark as required only those present in every answer. - Inside a list, describe only the fields of each row that are certain, and allow null wherever the stored value can be empty. A service may have no description. A booking may have nobody assigned yet. - Leave additionalProperties open. A field we add next month must not make every answer fail in a client that cached last month's schema. - Use plain JSON Schema only: type, properties, required, items, enum and description. No $schema line and no keyword from one draft, so any validator reads it. ```ts const str = { type: "string" }; const num = { type: "number" }; const strOrNull = { type: ["string", "null"] }; function obj(properties: Record, optional: string[] = []): JsonSchema { return { type: "object", properties, required: Object.keys(properties).filter((k) => !optional.includes(k)), }; } const listServices = obj({ services: { type: "array", items: obj({ id: str, name: str, description: strOrNull, durationMin: num, priceCents: num }), }, }); ``` Only reads declare a schema. A write's answer depends on what it did, and we would rather promise nothing than promise a shape we might break. Writes still return structuredContent, so a client can read it, but with no schema there is nothing to fail against. The answer goes out twice: once as the JSON text block every client already reads, and once as structuredContent. We build the second by parsing the first, so the two can never disagree. Dates, for example, are strings in both. ```ts export function toolResult(data: unknown, structured: boolean): ToolResult { const text = JSON.stringify(data); const result: ToolResult = { content: [{ type: "text", text }] }; if (structured && isPlainObject(data)) result.structuredContent = JSON.parse(text); return result; } ``` A test seeds a business with something in every corner, empty optional fields included, and calls every read tool. Each answer must fit its schema the way a client's validator reads it. #### Tool errors the model can read Before, every refusal was a JSON-RPC error. Most clients treat that as a failed call and do not show it to the model. So when a time was taken between the availability check and the booking, the model never learned why, and could not offer another time. Now a tool's own refusal comes back as a normal result with isError set. It carries an error object with a code, a message and any details the tool gave: ```ts // tools/call, for a time someone else booked a moment ago { content: [{ type: "text", text: '{"error":{"code":"BOOKING_REFUSED","message":"That time is no longer available"}}' }], structuredContent: { error: { code: "BOOKING_REFUSED", message: "That time is no longer available" } }, isError: true, } ``` The model reads it, checks availability again, and offers the person another time. Nothing was booked twice. Not every refusal belongs there. A missing scope, a bad credential or a rate limit is for the client software to act on, not the model. Those stay JSON-RPC errors with their HTTP status: 401, 403 or 429. An unknown tool, and arguments that do not parse, stay protocol errors too. ##### The error that fails its own schema One detail caught us. A tool with no output schema returns the error in structuredContent as well as in the text. A read tool with an output schema must not. Clients validate any structuredContent against the tool's schema, error or not. An error object does not look like a list of services, so the client would reject the error itself, and the model would see nothing. Those tools send the error in the text only. ```ts export function toolErrorResult(code: string, message: string, details = {}, hasOutputSchema = false): ToolResult { const error = { ...details, code, message }; const result: ToolResult = { content: [{ type: "text", text: JSON.stringify({ error }) }], isError: true }; if (!hasOutputSchema) result.structuredContent = { error }; return result; } ``` #### Not breaking anyone Scripts and integrations written against the old handshake expect a JSON-RPC error for a taken time, and some match on it. Changing that under them would break working code. The protocol gives a clean signal to tell them apart: from 2025-06-18, a client sends an MCP-Protocol-Version header on every request after initialize. ```ts export function wantsToolErrorResults(req: Request): boolean { const v = req.headers.get("mcp-protocol-version")?.trim(); return !!v && SUPPORTED_VERSIONS.includes(v) && v >= "2025-03-26"; } ``` A caller whose header names a 2025 version gets isError results. A caller with no header gets the JSON-RPC error it always had. Characterization tests pin both. tools/list changed the same careful way. The new fields are additions. Names, descriptions and input schemas stayed byte for byte the same, and tests that captured them before the change prove it. #### What we take from it - Send every annotation, true or false. The defaults describe a tool nobody knows, not yours. - Derive hints from the tool's definition, and test them against what its description says it does. - An output schema is a promise the client enforces by discarding your answer. Promise less. - Return a tool's own refusals as isError results with a code, and keep auth and transport failures as protocol errors. - Gate new behaviour on the protocol version header, so old callers see no change. ### Dry runs that never write: letting an AI check a change before making it An AI app working on a business's bookings should be able to ask what a change would do before it does it. Our MCP server and REST API take a dryRun flag on writes. It reads the real records and says who would be told, without changing anything. Here is how it works, and the two ways our first version told the AI something that was not true. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/dry-runs-that-never-write · markdown: https://bookatu.com/engineering/dry-runs-that-never-write.md > **The short version** > > - Send dryRun: true with a write, on MCP or REST, and the server answers what the call would do instead of doing it. > - The answer names the real record the write touches, read from this business and the caller's own column, and says who would be told. > - A dry run with a made-up id is refused in the same words the real call would use. > - Nothing is written or sent. No audit row is recorded and no idempotency key is claimed. > - The flag is honoured on every write, including writes that do not advertise it. Inside the admin, our assistant proposes a change and a person confirms it on a card. Our post Propose then confirm explains that pattern, and Undo for AI actions covers how each change records its own reverse. A connected AI app talking to our MCP server, or a script calling the REST API, has no card. It needs another way to look before it acts. That way is a dry run. A write sent with dryRun: true is worked out but not made. The server says what the call would do, and stops there. #### What a dry run answers With made-up details, and shortened a little, a dry run of cancelling a booking answers like this: ```json { "dryRun": true, "changed": false, "tool": "cancel_booking", "wouldDo": "Cancel a booking (appointmentId: ...)", "record": { "id": "...", "what": "Private lesson, 60 min", "who": "Sam Lee", "when": "Thursday 12 November at 10:00" }, "tells": "The client is not told: let them know yourself. A paid deposit is kept or refunded under the business's cancellation rules.", "next": "Call again without dryRun to make the change." } ``` changed: false is there so no caller can mistake the answer for a result. record says what the change would land on. tells says who finds out. next says how to go ahead. #### Read the real record A preview is only useful if it is true. The cheap version of a dry run echoes the arguments back: you asked to cancel booking X, so cancelling booking X is what would happen. That tells the caller nothing new, and it says yes to calls the real write would refuse. Ours reads the record the write names, from this business only. For a tool that acts on one booking or visit, it reads from the caller's own column only, the same filter the real call applies. If the record is not there, the dry run is refused, in the words the real call would use: ```ts // Each write that names one of these records, the argument, // and the words its real call uses for a missing one. const NAMED_RECORDS: Record> = { update_product: [["productId", "Product not found"]], update_service: [["serviceId", "Service not found"]], update_customer: [["customerId", "I could not find that client."]], }; async function namedRecord(ctx: ToolContext, tool: string, args: Args) { for (const [arg, missing] of NAMED_RECORDS[tool] ?? []) { const id = String(args[arg] ?? "").trim(); if (!id) continue; const row = await readers[arg](ctx.orgId, id); // this business only if (!row) throw refusal(missing); return describe(arg, id, row, ctx.canSeeClients); } return null; } ``` Our first version looked records up only for bookings, visits, classes, posts and forms. For a product, a service, a client or a webhook, a dry run with a made-up id came back with record: null and the line Call again without dryRun to make the change. The real call then failed with not found. An AI that trusted the dry run would tell the person all was well, then fail in front of them. Now every write that names one of those records is on a list, with the real call's own words for a missing one. A test fails when a new write declares such an argument and is on no list. The one write left off has a written reason: its real call does not refuse a missing record either. A client's name appears in the answer only for a caller allowed to see clients. Anyone else gets the record without the name. #### Say who is told Before an AI acts, the question a person most wants answered is who finds out. An email to a client about a cancelled lesson is a very different thing from a quiet change to a stock count. So every dry run says who is told, in plain words that match the tool's own published description: - Moving a booking: the client is told the new time. - Cancelling a booking as the business: the client is not told, so let them know yourself. A paid deposit is kept or refunded under the business's own rules. - Declining a booking request: the client is emailed, and a paid deposit is refunded. - Cancelling a place in a class: the client is emailed, and what they paid comes back to them as account credit. - Adding a webhook: events start going to an address outside the business. Writes that tell nobody say so: Nobody outside the business is told. Some lines depend on the business. A new visit at a business that approves online bookings is held as a request until someone says yes, so the dry run reads that setting before it answers. The quiet default was our second false answer. The dry run borrowed its lines from the in-app assistant's confirm cards. The assistant never proposes the writes that hand money back, so its cards had no line for them, and they fell through to the default. A dry run of declining a request said nobody would be told, while the real call emailed the client and refunded the deposit. A test now reads every write's description. If it says a client is emailed or told, or that money comes back, or that a deposit may be kept, the dry run must say so too. #### Change nothing, anywhere A dry run must have no side effect, not even a small one. It is answered early in the one runner every product shares, so it never reaches the handler: ```ts export function runTool(tool: Tool, ctx: ToolContext, args: Args) { return withToolMark(ctx, tool, async () => { await assertInColumn(ctx, tool, args); // Before the idempotency key, the handler and the audit row. if (isDryRun(tool, args)) return dryRunPreview(ctx, tool, args); return withIdempotency(ctx, tool, args, () => runHandler(ctx, tool, args)); }); } ``` No row is written. No email or text is sent. No audit row is recorded, because nothing happened. No idempotency key is claimed, so a later real call with the same key is not mistaken for a retry. tools/list advertises dryRun on the writes where a preview helps most. The server honours it on every write. In our first version the flag was read only where it was advertised. Sent to any other write, it was dropped, and the change went ahead. A caller who says change nothing means it, whether or not we expected the question. ```ts export function isDryRun(tool: ToolSpec, args: Args): boolean { // Honoured on every write, advertised or not. return args?.dryRun === true && tool.access === "write" && !("dryRun" in tool.inputSchema.properties); } ``` The last condition leaves room for a tool that has a dryRun argument of its own meaning. On REST a dry run is dryRun: true in the JSON body, or ?dryRun=true in the query string. Either way it passes the same scope and permission checks as the real call, so a dry run never describes a record the caller could not change. #### Refusals an AI can read A dry run is half of letting an AI act carefully. The other half is what happens when the real call says no. A refusal written only for a person leaves the AI guessing. Our refusals carry a code and, where there is one, a next step. On MCP, for a client on a 2025 protocol version, they come back as tool results with isError set, so the model sees them, not only the client software. A time that was taken a moment ago comes back as BOOKING_REFUSED with the reason. A reused idempotency key comes back as IDEMPOTENCY_KEY_REUSED with Use a new key for a new change. On the REST routes the registry serves, a call refused for a missing scope names the scope and points to how-do-i, which answers with the steps and a link to the screen where a person can do it. #### Trade-offs - A dry run is a real read, with the same checks as the real call. It is not free, and it should not be. - It is a snapshot. Between the dry run and the real call, the time can be taken or the client can cancel. The real call checks everything again. A dry run never holds anything. - Every new write needs its line saying who is told. Tests make a missing line a failing test, not a review comment. - Tool descriptions are now part of the contract. Tests read them, so changing a tool's wording can fail a test about its dry run. We think that is right. #### What we take from it - A dry run that echoes its arguments is worse than none. Read the real records. - Refuse in a dry run exactly where the real call would, in the same words. - Say who is told. It is the question people care about most. - Honour change nothing on every write, advertised or not. - Give every refusal a code and a next step the model can act on. ### EAN-13 and Code 128 in plain TypeScript, with a test that scans them back Businesses on Bookatu sell things next to their bookings. A studio sells mats, a salon sells the shampoo it uses. To print shelf labels we wrote EAN-13, UPC-A and Code 128 encoders by hand, with no dependency. Here is how each symbol is built and drawn as SVG, and the test that proves a printed label scans back to the right code. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/ean-13-and-code-128-in-plain-typescript-with-a-test-that-scans-them-back · markdown: https://bookatu.com/engineering/ean-13-and-code-128-in-plain-typescript-with-a-test-that-scans-them-back.md > **The short version** > > - An EAN-13 is 95 modules: three guards and twelve digits of seven modules each. The first digit has no bars of its own. It is carried by the pattern of the left half. > - A UPC-A is an EAN-13 that starts with 0, with the same bars. Scanners report it either way, so the point of sale looks a code up under both forms. > - Code 128 switches between set B for text and set C for pairs of digits, which halves the width of a long number. > - The SVG is measured in modules, quiet zones included, so one drawing prints on a small roll label or a full sheet. > - A test paints the SVG's own bars onto a bitmap and decodes it with ZXing, asking for the same formats the point of sale's camera scanner asks for. Bookatu has a point of sale and stock for the things a business sells next to its services. A yoga studio sells mats and blocks. A surf school sells wax. Most of these arrive with a barcode on the box. Some do not, and some shelves need a label anyway. So the Products page has Print labels, and a product with no code can get one with Make a barcode. We could have added a barcode library. We wrote the encoders instead. The two files are just over 200 lines together, they run the same in the browser and in Node, and writing them meant we know exactly what we print. #### EAN-13: twelve digits you see in the bars, one you do not An EAN-13 is drawn as 95 modules. A module is the narrowest bar or space. The symbol opens with a guard, 101. Then come six digits of seven modules each, a centre guard, 01010, six more digits, and a closing 101. That is only twelve digits of bars. The thirteenth, the first one printed, has no bars of its own. It is carried by which of two patterns, L or G, each of the six left digits uses. The right half always uses R. R is L with every module flipped, and G is R read backwards. ```ts const L = ["0001101", "0011001", "0010011", "0111101", "0100011", "0110001", "0101111", "0111011", "0110111", "0001011"]; const G = ["0100111", "0110011", "0011011", "0100001", "0011101", "0111001", "0000101", "0010001", "0001001", "0010111"]; const R = ["1110010", "1100110", "1101100", "1000010", "1011100", "1001110", "1010000", "1000100", "1001000", "1110100"]; // Which set each of the six left digits uses, by the first digit. const PARITY = ["LLLLLL", "LLGLGG", "LLGGLG", "LLGGGL", "LGLLGG", "LGGLLG", "LGGGLL", "LGLGLG", "LGLGGL", "LGGLGL"]; export function ean13Modules(code: string): string | null { if (!isValidEan13(code)) return null; const parity = PARITY[Number(code[0])]; let out = "101"; for (let i = 0; i < 6; i++) { const d = Number(code[1 + i]); out += parity[i] === "L" ? L[d] : G[d]; } out += "01010"; for (let i = 0; i < 6; i++) out += R[Number(code[7 + i])]; return out + "101"; } ``` The last digit is a check digit. Weights of 3 and 1 alternate from the right, starting with 3, and the check digit brings the sum up to the next multiple of ten: ```ts export function gs1CheckDigit(body: string): number { let sum = 0; for (let i = 0; i < body.length; i++) { const fromRight = body.length - 1 - i; sum += Number(body[i]) * (fromRight % 2 === 0 ? 3 : 1); } return (10 - (sum % 10)) % 10; } ``` Because it counts from the right, the same function works for the twelve digit body of an EAN-13 and the eleven digit body of a UPC-A. #### UPC-A is the same symbol A twelve digit UPC-A is drawn exactly as the EAN-13 of a 0 followed by it. With a first digit of 0 the parity pattern is all L, which is how UPC-A was laid out before EAN extended it. So our UPC-A encoder is one line: ean13Modules("0" + code). This has a practical side. The bars are identical, so a scanner has to choose what to report. Some decoders report an EAN-13 that starts with 0 as its twelve digit UPC-A. Many USB scanners send a UPC-A as thirteen digits. Neither is wrong. So the point of sale looks a scanned code up under both forms, the exact one first: ```ts export function scanMatchKeys(scanned: string): string[] { const code = scanned.trim(); if (!code) return []; if (isValidUpcA(code)) return [code, "0" + code]; if (code.startsWith("0") && isValidEan13(code)) return [code, code.slice(1)]; return [code]; } ``` #### Code 128 for everything else Not every product code is a retail number. A supplier may use its own code, such as MAT-PRO-6MM. Anything that is not a valid EAN-13 or UPC-A prints as Code 128, with the text exactly as stored. That includes thirteen digits with a wrong check digit, which we print as the text it is rather than guess at. Code 128 has three code sets. Set B carries printable ASCII, one character per symbol. Set C carries two digits per symbol, so a long number takes half the width. Set A carries control characters, which a code typed or scanned never contains, so we left it out and refuse any code that would need it. Choosing between B and C follows the usual rules from the standard, ISO/IEC 15417, annex E. Start in C when the text opens with four or more digits, or is exactly two digits. Otherwise start in B. From B, switch to C for a run of six or more digits, or four or more that end the text. An odd run spends its first digit in B before switching. From C, go back to B as soon as fewer than two digits are left in the run. Every symbol is eleven modules wide, and the stop is thirteen. The check symbol is the start value plus each symbol's value times its position, modulo 103: ```ts let sum = values[0]; // the start symbol for (let k = 1; k < values.length; k++) sum += values[k] * k; values.push(sum % 103, STOP); ``` Each value maps to six widths, bar first, from the Code 128 table. We did not trust our own copy of a 107 row table. A unit test holds it against the table inside ZXing, the open source decoder our point of sale's camera scanner falls back to. The EAN sets are checked against ZXing the same way, and against full module strings for two well-known example codes, worked out by hand from the GS1 tables. #### Drawing it The encoders return a string of 1s and 0s. The SVG layer turns each run of 1s into a rectangle, and adds what a scanner and a person need around the bars. - Quiet zones. A scanner finds the start of a symbol by the blank space before it. EAN-13 gets 11 modules on the left and 7 on the right. UPC-A gets 11 on each side, room for its outside digits. Code 128 gets 10. - Guard bars. On EAN-13 and UPC-A the guards reach a few modules lower than the rest, framing the digits. - Digits. The EAN-13's first digit sits in the left quiet zone, before any bar. UPC-A prints its first and last digits outside the bars, a little smaller. - Units. Everything is in modules in the viewBox. The label sheet decides how many millimetres a module is, so the same drawing fills a 25 mm roll label or a cell on an A4 sheet. Two small details matter more than they look. The bars are drawn with shape-rendering="crispEdges", so a printer driver does not blur one bar into the next. And the text under the bars is escaped, because a stored code is user input and an SVG is markup. A test feeds it a code full of angle brackets and quotes and checks no tag gets through. #### The test that scans it back Pattern tests prove the encoder matches our reading of the spec. They do not prove a label scans. For that we wanted the whole path: the SVG markup we actually ship, read by a real decoder. So the test ignores the encoder's internals. It parses the rectangles out of the SVG string, paints them onto a white bitmap at three pixels per module, and hands that to ZXing. It asks ZXing for exactly the formats the point of sale's camera scanner asks for, read from one shared list, so the test and the point of sale cannot drift apart. ```ts const PX = 3; const ROWS = 40; function decodeSvg(svg: string): { text: string; format: string } { const widthModules = Number(/viewBox="0 0 ([\d.]+)/.exec(svg)![1]); const group = /(.*?)<\/g>/.exec(svg)![1]; const bars = [...group.matchAll(/ ({ x: Number(m[1]), w: Number(m[2]) })); const width = Math.round(widthModules * PX); const row = new Uint8ClampedArray(width).fill(255); for (const b of bars) { for (let px = Math.round(b.x * PX); px < Math.round((b.x + b.w) * PX); px++) row[px] = 0; } const lum = new Uint8ClampedArray(width * ROWS); for (let y = 0; y < ROWS; y++) lum.set(row, y * width); const reader = new MultiFormatReader(); reader.setHints(new Map([[DecodeHintType.POSSIBLE_FORMATS, SCANNER_FORMATS]])); const bitmap = new BinaryBitmap(new HybridBinarizer(new RGBLuminanceSource(lum, width, ROWS))); const result = reader.decode(bitmap); return { text: result.getText(), format: BarcodeFormat[result.getBarcodeFormat()] }; } ``` Every case must come back as the stored code, character for character, in the expected format. The point of sale finds a product by an exact match on its code, so close is not good enough. ```ts expect(scan("5901234123457")).toEqual({ text: "5901234123457", format: "EAN_13" }); expect(scan("036000291452")).toEqual({ text: "036000291452", format: "UPC_A" }); for (const code of ["MAT-PRO-6MM", "123456", "12345", "AB12345678", "AB1234567", "X123456Y", "sku 42/b", "A"]) { expect(scan(code)).toEqual({ text: code, format: "CODE_128" }); } // Short bars, as on a small roll label. expect(scan("2000000000015", { barHeight: 12 }).text).toBe("2000000000015"); ``` The Code 128 cases are picked to hit each switching rule. There are digits only, in an even and an odd count. There are runs that end the text after letters, again even and odd. A six digit run in the middle switches to C and back, a short one stays in B, and a single letter is the smallest case. #### Codes for products that have none Make a barcode gives a product with no code an EAN-13 of the business's own. GS1 keeps the prefixes 20 to 29 for restricted circulation: numbers a shop uses inside its own walls, which no manufacturer is ever given. So one of ours can never collide with a real product's code. Ours all start with 20, then a ten digit running number, then the check digit: 2000000000015, 2000000000022 and on. We picked 20 because some point of sale systems read the other prefixes in the range as a code with a weight or a price inside it, and 20 is the one most often left plain. ```ts export function inStoreCode(n: number): string { const body = "20" + String(n).padStart(10, "0"); return body + gs1CheckDigit(body); } ``` The next number is one past the highest the business already has. Two people pressing the button at the same moment would work out the same number, so a unique index on the business and the barcode refuses the second insert. #### What we take from it - Barcode symbologies are small and well specified. Writing one is a modest job, and it takes a dependency off every page that prints. - Hold your tables against an independent copy, such as the one inside a decoder. - Test the thing you ship. Our scan test reads the SVG string, not the encoder's output. - Share the scanner's format list with the test, so the two cannot disagree. - When two encodings are one symbol, look a scan up under both. ### SMS segments in fourteen languages: GSM-7, UCS-2 and the maths A text message travels in segments, and one character can cut how much fits in each from 160 to 70. Bookatu writes its texts in fourteen languages, Czech and Japanese among them. Here is how we count segments the way the networks fill them, and how a text drops detail to fit the fewest segments it can. The Bookatu engineering team · 2026-11-11 · Engineering · https://bookatu.com/engineering/sms-segments-in-fourteen-languages-gsm-7-ucs-2-and-the-maths · markdown: https://bookatu.com/engineering/sms-segments-in-fourteen-languages-gsm-7-ucs-2-and-the-maths.md > **The short version** > > - GSM-7 fits 160 characters in one segment, and 153 in each part once a text is split. UCS-2 fits 70, and 67 per part. > - One character outside the GSM-7 alphabet sends the whole text as UCS-2. > - Nine GSM-7 characters, the euro sign among them, take two places. Most emoji take two UTF-16 code units. A network never cuts either across two parts, so dividing by the part size undercounts. > - Before a text goes out, typographic dashes, curly quotes and unusual spaces become plain ones. Letters are never touched. > - A text that runs long drops detail in a fixed order, and only to save a whole segment. A booking text has a small job. It says who it is from and what was booked for when, and sometimes it carries a link. It also has a budget. Networks carry and charge for texts in segments, so a reminder that spills into a second segment costs twice as much as one that fits. The words of our texts exist in fourteen languages, Czech and Japanese among them. The rules for what fits in a segment are the same in every one, and they are less obvious than they look. #### What a segment is SMS was built around 140 bytes. With the GSM-7 alphabet, seven bits a character, that is 160 characters. A longer text is split, and each part carries a small header so the phone can join the parts back up. The header takes room, so each part holds 153 characters. GSM-7 is a short alphabet. It has the Latin letters, digits, common punctuation and a handful of accented letters such as ä, ö, ü, ß, é, è, à, ñ, å, ø and æ. Any character outside it, a Czech ř, a Polish ł, any Japanese, a single emoji, sends the text as UCS-2 instead. That is 16 bits a character: 70 in one segment, 67 per part. The switch applies to the whole text. One ł in an otherwise plain message turns 160 characters a segment into 70. A 160 character reminder that fit in one segment now takes three. There is one more wrinkle. Nine characters reach GSM-7 only through an escape, from an extension table: € [ ] { } ^ ~ \ and |. Each takes two places. #### Counting it ```ts // GSM 03.38, the basic set, and the extension table (two septets each). const GSM7_BASIC = new Set([..."@£$¥èéùìòÇ\nØø\rÅåΔ_ΦΓΛΩΠΨΣΘΞÆæßÉ !\"#¤%&'()*+,-./0123456789:;<=>?¡ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÑܧ¿abcdefghijklmnopqrstuvwxyzäöñüà"]); const GSM7_EXTENDED = new Set([..."^{}\\[~]|€\f"]); export function smsSegments(body: string) { const widths: number[] = []; let gsm = true; for (const ch of body) { if (GSM7_BASIC.has(ch)) widths.push(1); else if (GSM7_EXTENDED.has(ch)) widths.push(2); else { gsm = false; break; } } if (gsm) { const septets = widths.reduce((a, w) => a + w, 0); return { encoding: "gsm7", units: septets, segments: septets <= 160 ? 1 : packed(widths, 153) }; } // UCS-2 counts UTF-16 code units: a character beyond them (most emoji) takes two. const units = body.length; return { encoding: "ucs2", units, segments: units <= 70 ? 1 : packed([...body].map((c) => c.length), 67) }; } ``` Two JavaScript details do the work here. for...of walks a string by code point, so an emoji is one step of the loop. body.length counts UTF-16 code units, so the same emoji counts as two. On the wire, texts written outside GSM-7 behave like UTF-16, so a character outside the basic plane takes two units of the 70. #### The off-by-one at the edge Our first version divided: septets over 153, rounded up. It is the obvious formula, and it is wrong at the edges. A network fills parts one character at a time, and it never cuts a character in two. If a part has one place left and the next character is a euro sign, which needs two, the euro sign starts the next part. The spare place goes unused. Take 152 letters, a euro sign, then 152 more letters. That is 306 septets, which divides into two parts. On the network, the first part takes 152 letters and has one place left. The euro sign does not fit, so it starts part two. Part two fills to 153 with the euro sign and 151 letters, and the last letter goes into a third part. Three parts, not two. UCS-2 has the same edge with emoji. 66 characters, an emoji, then 66 more is 134 units: two parts by division, three on the network. So the count now fills parts the way the network does: ```ts function packed(widths: number[], perPart: number): number { let parts = 1; let used = 0; for (const w of widths) { if (used + w > perPart) { parts += 1; used = 0; } used += w; } return parts; } ``` A text of one segment was always counted right, so this only changes split texts. It matters most when a text has to fit a set number of segments, which is where we found it. #### Keeping texts in GSM-7 Many characters that push a text into UCS-2 are not language at all. They are typography that slipped in on the way. - French and Swedish write a negative UTC offset with the true minus sign, not a hyphen, so a time zone label can carry it. - Some versions of ICU, the library behind date formatting, put a narrow no-break space inside a formatted time. - Phone keyboards turn quotes into curly quotes, and two hyphens into a dash, inside business and service names. - An ellipsis can arrive as one character instead of three dots. Every text passes through one function before it is sent, which swaps these for plain ones: ```ts export function smsSafe(body: string): string { return body .replace(/[\u2010-\u2015\u2212]/g, "-") // dashes and the minus sign .replace(/[\u00A0\u2000-\u200A\u202F\u205F]/g, " ") // unusual spaces .replace(/[\u2018\u2019\u201A\u201B\u2032]/g, "'") // single quotes and the prime .replace(/[\u201C-\u201F\u2033\u00AB\u00BB]/g, '"') // double quotes and guillemets .replace(/\u2026/g, "..."); // the ellipsis } ``` Letters are left alone. A Czech č or a Polish ł is the language, not typography. Those texts are UCS-2 whatever we do, and the rest of this post is about living with that. #### Choosing words that fit Translation has a say too. Where a language has a GSM-7 word and another outside it for the same meaning, our texts use the GSM-7 one. In Portuguese, reserva rather than marcação. In French, stopper rather than arrêter. The meaning holds, and the text stays at 160 a segment. Other languages have no such choice. Czech and Polish use letters outside GSM-7 in nearly every sentence. Japanese is outside it entirely. For those, 70 characters is the budget, and a long business name can use half of it. #### Trimming to the fewest segments Some of our texts carry a link, so the client can open their booking from the message. A link cannot be shortened by translation, and in UCS-2 it takes a large share of 70 characters. For texts sent from a sender nobody can reply to, the link is the client's only way to act on the message. For those we went further: the text is fitted, not only written to fit. Each such text has three versions, tried in order. The full version has the business, the service and the long date. The next drops the service. The last also shortens the date, to something like Wed 4 Nov. The first version with the fewest segments wins: ```ts export function fitText(input: TextInput): FittedText { const { words, business, service, when, whenShort, url } = input; const versions = [ { step: "full", body: fill(words.full, { business, service, when, url }) }, { step: "no_service", body: fill(words.short, { business, when, url }) }, { step: "short_date", body: fill(words.short, { business, when: whenShort, url }) }, ]; let best: FittedText | null = null; for (const v of versions) { const body = smsSafe(v.body); const length = smsSegments(body); if (!best || length.segments < best.segments) best = { body, step: v.step, ...length }; } return best!; } ``` The comparison is strict on purpose. A shorter version wins only by saving a whole segment, never a few characters, because characters inside a segment cost nothing. If the full text fits one segment, the client gets the full text. The business name, the date and the link are never dropped. A text without the date is useless, and one without the link leaves the client no way to reach the booking from it. When even the shortest version is long, say a long business name in Japanese, the shortest version is the one used, in more segments. #### Testing every language The tests fill each language's words the way the sender does. They use a deliberately long business name, a service with the person doing it, and a date in a month and on a weekday whose names are long in most languages. Then they run smsSafe and count segments. Each text must stay within a fixed number of segments, with one budget for GSM-7 and a larger one where a language needs UCS-2. A translation that grows past its budget fails the tests, in the language it grew in. The counter has its own tests at the edges: 160 and 161 characters, 306 and 307, a euro sign as the 160th place, and the 152, euro, 152 case that started this. #### What we take from it - Count segments by filling parts, not by dividing. A two-place character never splits. - Clean up typography before sending. Never change letters. - In translation, pick GSM-7 words where the language allows it. - When trimming, drop detail in a fixed order, and only to save a whole segment. - Test every language with the longest realistic inputs, not the example in the catalog. ### A booking MCP server where the person always confirms A client's own AI assistant can find a time at a business on Bookatu and hold it, but only the client can turn the hold into a booking. Why we built it that way, and what we left out on purpose. The Bookatu engineering team · 2026-11-06 · updated 2026-11-07 · Engineering · https://bookatu.com/engineering/a-booking-mcp-server-where-the-person-always-confirms · markdown: https://bookatu.com/engineering/a-booking-mcp-server-where-the-person-always-confirms.md > **The short version** > > - An assistant can get the person or the time wrong, so only the person can turn a held time into a booking. > - Before that yes, there is no booking and no client record, only a held time that lets go by itself, and the business's booking page can still book it. > - The person confirms with the code from the email or on the page the email links to, where "This wasn't me" turns it down instead. > - Anything that needs a deposit, a card, terms or a form is booked on the business's own booking page. > - It is off until someone at the business who can change its settings switches it on, and one check decides every way in, again at the moment the person confirms. > - Bookatu's messages for the person come from fixed templates in 14 languages, and a business's words come back in their own labelled fields. > - One switch decides whether any page or document names the server, and tests checked that none did before it was on. > - We left out taking money through the assistant, health and medical care, services that need more than a time, and any booking without the person's yes. At a business that has switched it on, a client's own AI assistant can use Bookatu's public booking server to look up the business from its booking link and hold one of its free times for the person it is helping. MCP is an open protocol that lets AI assistants use other software's tools, and this server speaks it. What the assistant cannot do is book. A held time becomes a booking only when the person confirms it from their email. This post is about why we drew the line there, and about the rules that follow from it. #### Why should an AI assistant not book on its own? An assistant acts on behalf of a person, and it works from what it was told. It can pick the wrong day or the wrong service. It can also be handed an email address that belongs to someone else, and nothing about an address typed into a chat shows whose it is. A booking the person never agreed to costs the business as well. It takes a time another client could have booked, for someone who may not come, and it sends a confirmation to an inbox that never asked for one. So in this design only the person can make the booking. #### Why does the assistant hold a time instead of booking it? Before the person says yes, there is no booking and no client record. There is only a held time, which lets go by itself if nobody confirms it. Bookatu keeps a held time away from other assistants, so a time held for one person is not offered to anyone else's assistant. It does not take the time away from the business. The business's booking page, its booking widget and its team can still book a held time. We wanted it that way round. A held time is a request that may never be confirmed, so it should never stop a client who is ready to book on the business's own page. If the time is booked on the business's side first, nothing is booked when the person confirms. Bookatu gives the assistant other free times that day to offer when there are any, and the page the email links to gives the person the business's booking page instead. The same happens if the price has changed by then: nothing is booked at the old price, and the times Bookatu offers start with the same time at the new price when it is still free. #### How does a client show that the email address is theirs? Bookatu emails the address the assistant gave, when that address can take email from Bookatu, and writes as itself. The email says plainly that the request came from an AI assistant, and that ignoring the email books nothing. It carries a code and a link. The person confirms in one of two ways: they read the code to their assistant, or they open the link and confirm on the page it opens. Every answer to a held time also carries the business's booking page link, so if no email comes, the assistant can give the person that link instead. Opening the link books nothing by itself. Mail scanners and link previews open links too, so only an action on the page can confirm. The code has a rule of its own. The email tells the person to read it only to an assistant they are using themselves, and Bookatu tells the assistant to ask for it only when the person in the chat is booking for themselves. Someone booked by another person confirms from their own inbox. The page also has a "This wasn't me" button, and the email carries a link straight to it. Pressing it on the page means nothing can be booked from that hold, and for a while Bookatu sends that address no more of these emails. The same page can undo that with "Allow assistants again". *Diagram: Flow chart: an assistant looks up a business from its booking link, checks free times and holds one. Bookatu emails the person, and only the person's confirm makes the booking, or the request at a business that accepts bookings by hand. A service that needs more than a time leads to the business's own booking page.* Diagram labels: A client's own AI assistant · Looks up the business · from its booking link · Checks free times · on the business's clock and the person's · Holds one time · it lets go by itself if nobody confirms · Bookatu emails the person · a code and a link · The person confirms · the code to the assistant, or on the page · A booking, or a request · as the business usually takes them · The business's own · booking page · needs more than a time *Only the person's yes turns a held time into a booking.* #### Why does money stay on the booking page? Some services need more than a time: a deposit, a card held for the no-show policy, booking terms, a required form or booking question, two or more team members, more than one kind of room or equipment at once, a trip, a class or workshop, or an extra. Those are booked on the business's own booking page. Bookatu tells the assistant so and gives it the booking page link to pass on. The page already handles each of those with the person in front of it, and none of them belongs in a chat. The verification email carries one plain line: "Bookatu never asks you to pay inside a chat." The instructions the server gives every assistant carry the same rule: "Bookatu never takes payment in a chat." Both sentences live in one catalog, in all 14 languages, and every message takes them from there, so none can word the rule its own way. Because the rule has no exceptions, a person can rely on it. If a chat asks them for money for a booking, the request did not come from Bookatu. #### Who decides whether assistants can book a business? The business does. It is off until someone at the business who can change its settings switches it on, and a business that offers health services cannot switch it on at all. A business on its free trial with no bookings yet can. The business can switch it off again, or keep single services out, at any time. One check decides whether a business can be booked, whether the call comes in over MCP or over the plain web API we offer agents that do not speak MCP. When a business the public can book on Bookatu does not pass that check, the server gives the same answer whatever the reason, with the business's booking page link, and only the business's own settings page says what stopped it. A service that assistants cannot book gets an answer with the booking page link too. Each refusal carries a code for the assistant and a plain sentence for the person in their language. The check runs again when the person confirms. A held time is never booked after the business has switched it off, or after its service has been kept out. #### How does an assistant tell Bookatu's words from a business's words? An assistant reads Bookatu's messages next to text that a business wrote, and a business can write anything into a service description. So the two never share a field. Every sentence the server writes for the person, refusals included, comes from a fixed template in each of 14 languages, and a business's words never go inside one of those sentences. Names and descriptions written by the business come back in their own labelled fields, marked as the business's own words, with the language they were written in. The server also tells every assistant to read text a business wrote as data and never as instructions. Bookatu gives the assistant each free time on the business's clock, and on the person's clock too when they are somewhere else, written out ready to read. It tells the assistant not to convert times itself. #### How did we keep the booking server dark until launch? One switch decides whether any public page or document names the server. Until it was on, every page and document that names it stayed dark, this post included. The server itself answered from the start, and until a business could be booked, a booking call for it got a plain refusal. The code was written test first. While the switch is off, tests check that no page or document an assistant or a directory might read names the server, and that the blog and the FAQ are exactly what they were before. We also broke those tests on purpose, to see them fail, before trusting them. #### What did we leave out of the booking server on purpose? - Taking money through the assistant. - Health and medical care. - Services that need more than a time. - Any booking without the person's yes. Health and medical care is left out for the whole business. If any of a business's services is health or medical care, assistants cannot book that business at all, and before switching it on, the business states that none of its services are. #### Where to start The server is described for developers at https://bookatu.com/en-nz/developers#mcp-book, and the plain web API for agents that do not speak MCP is documented on https://bookatu.com/en-nz/developers. The server is at https://bookatu.com/api/mcp/book and calls itself Bookatu Booking. It needs no account and no key. ### Widget events, written as if they were published Our booking widget now tells the website it sits on what happens inside it, so owners can count bookings in their own analytics. That website is someone else's, and so is every tag on it. Here is the event contract we wrote on that assumption, and three bugs review found before it shipped. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/widget-events-written-as-if-published · markdown: https://bookatu.com/engineering/widget-events-written-as-if-published.md > **The short version** > > - Release 13 gave the booking widget nine events, from ready to closed, that the page it sits on can listen for. That page runs someone else's analytics, so every field is treated as published. > - One module defines the fields. The frame builds every message with it, the loader on the host page checks every message by the same rules, and one test runs both. > - A booking is named by a reference that opens nothing, never the appointment id, and it is announced once, even when the done screen reloads. A business can put Bookatu on its own website with one script, /embed.js. In the inline and pop-up modes the booking happens in an iframe from our origin. For a business running ads, each booking is a conversion, so the widget now tells the page with postMessage. Every script on that page can read what we send. So we started from one rule: whatever an event carries, assume it ends up in a report someone else can read. #### A fixed list of fields, checked on both sides lib/embed-events.ts is the contract. Every event has a version, a name, the business's slug and a dedupe id. It may add the service, the start time, the time zone, the price, the currency and a few more. There is no name, email, phone, note, appointment id or manage key, and no way to add one. embedEvent() rebuilds every event from the allowed fields alone, and drops a field that fails its check. The test hands it everything a careless caller might: ```ts const ev = mod!.embedEvent({ ...BOOKED, dedupeId: undefined, start: new Date("2026-11-03T21:30:00.000Z"), // None of these may ever get through. ...({ name: "Rae Client", email: "rae@example.com", phone: "+64 21 555 0142", notes: "allergic", appointmentId: "apt_123", manageKey: "mk_secret" } as object), }); expect(ev).toEqual(BOOKED); ``` On the host page, public/embed.js is plain ES5 with no build step, because it lands in old site builders, so it carries its own copy of the checks. tests/unit/embed-events-contract.test.ts loads the real embed.js into a pretend website, posts the same good and bad messages to both copies, and fails if they ever disagree. #### A booking reference that opens nothing An analytics tool wants a transaction id to count a booking once, and the appointment id is the wrong one. Since release 12 a new booking is changed only with a signed manage key, but a booking made before that has no key, and its id alone can cancel or move it. So ref is an HMAC of the business and the appointment, under a signing key of its own purpose: ```ts export function embedBookingRef(orgId: string, appointmentId: string): string { return `bk_${signToken("embed-ref", `${orgId}:${appointmentId}`).slice(0, 24)}`; } ``` It is the same for the same booking, cannot be turned back into the id, and opens nothing. Our post Magic links done right: why a login token is not a share link covers how we sign and scope tokens. #### One booking, one conversion A booking's dedupe id is fixed by its reference, so a reloaded done screen announces the same id. The frame skips a booking it has sent where its storage allows. The loader also keeps the last 50 booking ids it announced in the tab's sessionStorage, so each booking fires once: ```js function remember(key) { seen[key] = true; try { var list = JSON.parse(window.sessionStorage.getItem(SEEN_KEY) || "[]"); if (!(list instanceof Array)) list = []; list.push(key); window.sessionStorage.setItem(SEEN_KEY, JSON.stringify(list.slice(-50))); } catch (e) {} } ``` A test reloads the host page on the same tab's storage: the booking counts once, and nothing stored looks like an email or an appointment id. #### Who may receive a postMessage With no allowed domains, the default, the frame posts to *. It cannot know which site it is on, and nothing in an event is personal. A business can list its own sites under Grow, Website widget, Only allow your own websites. Then the frame posts only to the framing page's origin, and only if it is on the list: ```ts const list = opts.embedDomains ?? []; if (list.length === 0) return ["*"]; if (opts.ancestorOrigin && embedOriginAllowed(list, opts.ancestorOrigin)) { return [new URL(opts.ancestorOrigin).origin]; } // ... return []; ``` The loader ignores any message not from the origin it was loaded from. #### We never load a tag Each event reaches the page as a window event, bookatu:, and, if the page has a dataLayer, a push named bookatu_. With data-track="gtag meta" on the snippet, the loader also calls the site's Google tag and Meta pixel, but only if the site has already loaded them. If a consent banner has kept a tag from loading, we do not load it either. Values travel in minor units, and the loader converts them with the currency's own digits, so 4500 is 45 in NZD and 4500 in JPY: ```js function major(value, currency) { var digits = 2; try { digits = new Intl.NumberFormat("en", { style: "currency", currency: currency }).resolvedOptions().maximumFractionDigits; } catch (e) {} return value / Math.pow(10, digits); } ``` #### Strict fields, cleaned inputs - An error carries one of ten fixed codes. Anything else becomes generic, because free text could carry what the visitor typed. - Times are RFC 3339 in UTC. Zones must be IANA names: an analytics tool shown EST would be an hour wrong all summer. - The host page's utm_ values are cleaned, and one that looks like an email address or a phone number is dropped. A gclid or fbclid never leaves the page, only a marker that it was an ad click. - Old listeners keep working: bookatu:booked and bookatu_booking_complete still fire. /embed.v1.js is a pinned copy for sites that check an integrity hash. #### What review found ##### The details never arrived The done screen sends the v1 event and, for older copies of embed.js, the old { slug, at } message. It drew the old one first. The loader fired bookatu:booked from that with a slug and a time only, and the details we document never reached it. The frame now marks its old message with contract: 1, and the loader leaves it to the v1 event, in either order: ```js if (d.type === "bookatu:embed:booked") { // From a v1 frame (contract: 1): the same booking's v1 event, sent with // it, announces it, with its details, whichever of the two arrives first. if (d.contract === 1) return; ``` tests/unit/embed-booked-alias.test.ts draws the done screen's two real senders against the real loader in both orders, plus a frame from before v1. The pinned copy had not been released yet, so it took the fix too, with a new integrity hash. ##### A funnel step went missing With data-date, the menu opens a service already on that day. The step counted as service_selected only when its address named no day, so the host's funnel went from ready straight to time_selected. The page now hands the frame an opening event, sent only when the visitor came from outside this service's steps. tests/unit/embed-deep-date-opening.test.ts covers each case. ##### Two forms, one score When nothing is free and the business has its waitlist on, the frame shows a waitlist form. It minted its reCAPTCHA token as waitlist, the storefront form's action, so a flood against one would drag down the other's score. Our test that rejects two forms with one action name caught it. The frame now mints its own: ```ts // Its own reCAPTCHA action (the frame's form mints embed_waitlist), never the storefront's. const outcome = await joinWaitlistFromForm(org.slug, formData, { serviceIds: [serviceId], recaptchaAction: "embed_waitlist" }); ``` #### What we take from it - Anything that crosses into someone else's page is published. Fix the fields once and rebuild every message from them. - An id that works as a key never goes into analytics. Hand out a reference that opens nothing. ### A nonce per request, and a cache that lived twice In release 12 every page moved from a host allow-list to a nonce with strict-dynamic, and it shipped enforced because a test proves every page gets the nonce. In release 13 the widget's pages began naming the only sites allowed to frame them, for a business that sets a list. Review found that saving the list took up to a minute to apply, because the proxy had its own copy of the cache. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/a-nonce-per-request-and-a-cache-that-lived-twice · markdown: https://bookatu.com/engineering/a-nonce-per-request-and-a-cache-that-lived-twice.md > **The short version** > > - Release 12 replaced our script host allow-list with a fresh nonce per request and 'strict-dynamic'. A script runs only if it carries the nonce, or was added by one that did. > - It shipped enforced, because a test proves every page gets the nonce. > - In release 13 a business that lists its own sites gets frame-ancestors naming those sites, and their subdomains, on every widget page, inside the one policy. > - Review found that a saved list took up to a minute to apply, because the separately bundled proxy had its own copy of the cache. The cache now lives on globalThis. In our post A private channel nobody else can join, an enforced allow-list quietly broke a websocket. Here the script allow-list goes, and the widget learns to tell the browser who may frame it. #### Why a host allow-list is weak The policy we enforced before release 12 allowed 'unsafe-inline' and 'unsafe-eval', so injected script could run. Nor did it stop data leaving. img-src allowed any https: image, connect-src allowed our blob provider's whole domain, which takes an upload token for any blob store, and the analytics hosts accept hits for any property. A stricter report-only draft dropped 'unsafe-inline' but kept a host list, which Google's CSP Evaluator flags: Google hosts serve JSONP and script gadgets that get past host lists. #### A fresh nonce on every request The new script-src is one line: ```ts `script-src 'nonce-${o.nonce}' 'strict-dynamic' https: 'unsafe-inline'${o.dev ? " 'unsafe-eval'" : ""}`, ``` A browser that knows nonces ignores 'unsafe-inline' here, and one that knows 'strict-dynamic' ignores https:. They only keep older browsers working. 'unsafe-eval' appears in development only, for React's tooling. proxy.ts makes 16 random bytes per request and builds the policy once. It goes on the response, and on the request the page renders from, where Next reads the nonce and stamps every script it writes. Whatever the caller sent under those header names is deleted first, so nobody picks their own nonce: ```ts const frameAncestors = await embedFrameAncestors(req.nextUrl.pathname); const csp = pageCsp({ pathname: req.nextUrl.pathname, frameAncestors }); const withCsp = (h: Headers): Headers => { h.delete("content-security-policy"); h.delete("content-security-policy-report-only"); h.delete(NONCE_HEADER); for (const [k, v] of Object.entries(csp.request)) h.set(k, v); return h; }; ``` Our own two inline tags, the platform's GA tag and a business's own GA tag, read the nonce from x-nonce. next/script adds an afterInteractive script from the browser, where it no longer knows the nonce, so we pass it in. Stripe.js, reCAPTCHA and gtag.js are loaded by our own code, so 'strict-dynamic' lets them through with no host list. The cost: every page renders per request, because the root layout reads headers(). #### How we dared to enforce it A nonce policy that misses one page breaks that page. tests/unit/csp-strict.test.ts proves, among other things: - Every page route in app/ passes through the proxy, checked with Next's own matcher code. - Every branch of the proxy, redirects and rewrites included, sets the policy and hands the render the same one, and Next's own parser reads the nonce back. - Nothing opts a page into static rendering. - Every inline script we write carries a nonce. - Paths the proxy skips, /api and files with a dot, get exactly one static policy. Two policies on one response would intersect. ```ts it("every page route in app/ passes through the proxy", () => { const pages = APP.filter((f) => /(^|\/)page\.tsx$/.test(f)); expect(pages.length).toBeGreaterThan(100); const missed = pages.map(sampleUrl).filter((u) => !matcher.test(u)); expect(missed).toEqual([]); }); ``` There is a kill switch. With a redeploy and no code change, it enforces the old policy while the strict one keeps reporting. Reports go to /api/csp-report by report-uri and report-to. The route logs the directive, the blocked origin and the page path. It never logs a script sample or a query string, because a blocked URL is where injected script would put what it stole. #### A report-only next step, and its noise The enforced policy still allows any https: image, for a business's own photos, though connect-src now allows only the blob upload path. Beside it rides a report-only policy with img-src narrowed to the hosts we know, so its reports say what narrowing would break. Our browser check before release found it left out two hosts our own pages use: the one serving our marketing photos, and Google's avatar host for an owner signed in with Google. One view of the home page sent 11 reports and one of the blog sent 26, each a function run and a rate-limit write. Both hosts are now on the list, and tests/unit/r12-csp-own-images.test.ts checks every policy a page carries allows them. #### frame-ancestors for the booking widget The widget is made to be framed. Under Grow, Website widget, a business can list its own sites, and before release 13 that list was checked against the Referer. A Referer gate only sees the request in front of it. Every step inside the frame sends our own origin as its Referer, which the gate has to let through, so it said nothing about who was framing a later step. frame-ancestors asks the browser instead, on every response. With a list, each /embed/ page names the business's sites and their subdomains, plus 'self' for the admin's own preview. It goes inside the one policy, never a second header. A browser enforces every policy it is sent, so two policies intersect: ```ts function frameAncestors(o: { embed?: boolean; frameAncestors?: readonly string[] | null }): string { if (!o.embed) return "frame-ancestors 'none'"; const list = (o.frameAncestors ?? []).filter((a) => ANCESTOR.test(a)); if (!o.frameAncestors || o.frameAncestors.length === 0) return "frame-ancestors *"; // A list was given: never widen it to *, even if nothing in it survived. return `frame-ancestors ${list.length ? list.join(" ") : "'self'"}`; } ``` Every widget step is a page, so the proxy keeps each slug's list for a minute, for up to 1000 slugs. The response stays per request, with its fresh nonce, and one that names a business's sites is sent private, no-store. #### The cache that lived twice Saving the list calls invalidateEmbedAncestors for that slug, so the next widget page sends the new list. In the browser check, the old frame-ancestors came back for about 40 seconds after a save. proxy.ts is bundled apart from the app's pages and actions. Each bundle had its own copy of lib/embed-ancestors.ts, and each copy its own Map. The save cleared the action's copy, and the proxy's copy kept its answer until the minute ran out. The fix moves the cache from the module to the process: ```ts type AncestorCache = Map; const CACHE_KEY = Symbol.for("bookatu.embedFrameAncestors"); const cache: AncestorCache = ((globalThis as Record)[CACHE_KEY] ??= new Map()); ``` Symbol.for returns the same symbol in every copy, so every copy in one server process shares one Map. Other server instances still catch up within the minute, and the admin page says so. The test imports two fresh copies of the module, as the proxy and the action have: ```ts const proxySide = await freshCopy(); const actionSide = await freshCopy(); expect(actionSide).not.toBe(proxySide); await setDomains(["one.example.com"]); expect(await proxySide!.embedFrameAncestors(`/embed/${biz.slug}`)).toContain("https://one.example.com"); await setDomains(["two.example.com"]); actionSide!.invalidateEmbedAncestors(biz.slug); // what saveEmbedDomainsAction does const now = await proxySide!.embedFrameAncestors(`/embed/${biz.slug}/book`); expect(now).toContain("https://two.example.com"); ``` A second case pins the other side: without a save, a copy keeps its answer for the minute, which is the bound on database reads. #### What we take from it - A nonce policy is only as good as the proof that every page gets the nonce. Write the proof as a test, then enforce. - One policy per response. A second header never widens the first: the browser enforces both. - A module-level cache is one cache per bundle. If two bundles must agree, keep the state where both can see it. ### The card step was a page, not a rule A business can ask for a card to hold a booking. Until release 13 the only thing that asked was the card step on the booking page, so the widget, the API and waitlist claims booked straight past it. Here is how the rule moved to where bookings are written, what counts as proof a card was saved, and what review found when booking terms and questions came after it. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/the-card-step-was-a-page-not-a-rule · markdown: https://bookatu.com/engineering/the-card-step-was-a-page-not-a-rule.md > **The short version** > > - The setting Require a card to hold the booking was asked only by the booking page's card step, in the browser. Every other door booked without a card. > - The rule now runs where bookings are written: createBooking, createVisit and the Quick swap claim. > - Proof is a card saved in this booking's own card step and confirmed by Stripe, or a usable card on file on a booking shown to be the cardholder's. If Stripe cannot be asked, the answer is no. > - The card step sits behind a platform switch that is off by default in the code, and a business has to turn the setting on. Without both, nothing changes. > - Booking terms and booking questions came next, and review found gaps in both before release. Our post One rule, every door explains why every visit ends in one function. This rule has a harder edge: its proof lives outside our database. Stripe has to have saved a card. #### A rule that lived in a page The cancellation policy has a setting, Require a card to hold the booking. With it on and a fee above zero, the booking page puts a card step before the review, and will not move on until the card is saved. That check lived in components/booking-flow.tsx: ```tsx // The flag-gated consent step: a card must be saved before continuing. Only // reachable when consentActive, so this never affects the flag-off flow. if (consentActive && s === consentStep) return consentVaulted; ``` createBooking never asked. So every other door booked a card-required service with no card: the website widget, POST /book and /visits/book on the keyless API, create_booking from a business's own agent, Magic Fill and Quick swap claims, and anyone posting straight to the page's own server action. A rule in a page is a suggestion to everything else. #### The question, asked like the page asks it lib/card-requirement.ts asks it in one place: ```ts export function cardRequiredFor(settings: unknown, priceCents: number, currency: string): boolean { if (!NOSHOW_CONSENT_CAPTURE_ENABLED) return false; return buildConsentDisclosure(settings, priceCents, currency).applies; } ``` The platform switch comes first, off by default. Then the disclosure applies only when the business has turned the setting on and its worst-case fee is above zero, exactly when the page shows its card step. createBooking asks it for every client booking, never the team's own. #### What counts as a saved card Since release 12 the card step returns a signed card receipt: this business, this client, this service, this SetupIntent. The catch is timing: it is handed over when the card form starts, before anyone types a number. On its own it proves only that the step was opened. ```ts export async function cardStepSaved(orgId: string, customerId: string, setupIntentId: string): Promise { if (await stepPaymentMethodOf(orgId, customerId, setupIntentId)) return true; try { const org = await getOrgById(orgId); if (!org?.stripeAccountId) return false; const stripe = await forConnectedAccount(org.stripeAccountId); const si = await stripe.setupIntents.retrieve(setupIntentId); return si?.status === "succeeded"; } catch (e) { log.warn("card_requirement.setup_intent_unreadable", { orgId, error: e instanceof Error ? e.message : String(e) }); return false; } } ``` So the receipt has to match the booking, its consent proof has to exist, and the card has to be saved: the webhook recorded its payment method, or Stripe says the SetupIntent succeeded. Stripe unreachable is not saved. A test pins it: a card step whose SetupIntent Stripe reports as requires_payment_method books nothing. The other way to hold is a card already on file. It counts only on a booking shown to be the cardholder's, for example signed in as them or claimed through their own link. The consent on file must also cover the policy in force. Change the policy, and an old consent no longer holds a new booking. #### Doors that cannot show a card form - The widget hands the service to the full booking page in a new tab, with the hand-off reason card_required, as it does for a deposit. - The keyless API answers 409 CARD_REQUIRED_USE_BOOKING_PAGE with a bookingPageUrl. - Magic Fill and Quick swap claims need a usable card on file. - Later visits of an online series are held by the card that held the first one. An online booking with neither a receipt nor a portal session is refused before a client record is looked up or made: ```ts const cardRequired = !isStaffBooked && cardRequiredFor(settings, service.priceCents, settings.currency); if ( cardRequired && source === "online" && !keyless && !input.seriesRepeatOf && !input.bookerProof?.cardReceipt && !input.bookerProof?.sessionCustomerId ) { return { ok: false, code: CARD_REQUIRED_CODE, error: CARD_REQUIRED_MESSAGE }; } ``` tests/integration/r13-card-required.test.ts walks the doors on real PGlite and the real booking code, faking only Stripe, mail and the request; a companion file covers Quick swap. Its characterization cases pin what must not change: the team books by phone with no card, a free service needs none, and a business without the setting books as before. #### Booking terms took a different road Booking terms came in the same release. A business sets plain text in Settings, Booking terms, and with none set nothing changes. Its version is the SHA-256 of the text, and a booking keeps the version and the time it was accepted. The public API asks for acceptTerms: true, or answers 422 TERMS_NOT_ACCEPTED with the terms to show. Acceptance is a tick a person makes, and it is checked at each door that shows the box, not in createBooking. That choice had a cost. Review found that Magic Fill and Quick swap claims booked a client with no terms at all. Both claim pages now show the terms with a required, unticked box, and a claim without the tick, or on terms changed since, changes nothing. tests/integration/r13-claim-terms.test.ts pins both, with characterization cases for a business with no terms. #### Booking questions, and what review found Booking questions in release 14 take the card's road: createBooking and createVisit check every answer, whoever books, and hold every client booking to its required questions. The keyless doors also check early, and answer 422 with the ids of any required question left blank. Review found two problems there. The early check ran before the service check, for any service id of the business. A phone-only or private service with a required question answered 422 ANSWERS_REQUIRED, naming a question found nowhere else, where an unknown id answers 409 Service unavailable. The difference told the caller the hidden service exists. The early check now asks only the questions of services a client may book online, plus the business-wide ones: ```ts .where( and( eq(services.orgId, orgId), inArray(services.id, ids), eq(services.active, true), eq(services.bookableOnline, true), eq(services.isPrivate, false), ), ); ``` The second was a NUL. A text answer ending in U+0000 passed checkAnswers, then Postgres refused it in jsonb inside the booking's transaction. POST /book answered 500, booked nothing, and logged the failed query with every answer on it. readOne now strips C0 and C1 controls, except a tab and a line break, and lone surrogate halves from a text answer before it reads anything else: ```ts const UNSEEN = /[\ud800-\udbff][\udc00-\udfff]|[\u0000-\u0008\u000b\u000c\u000e-\u001f\u007f-\u009f\ud800-\udfff]/g; const dropUnseen = (s: string): string => s.replace(UNSEEN, (m) => (m.length === 2 ? m : "")); ``` A whole surrogate pair, an emoji, matches first and is kept. There is no lookbehind, because this module also runs in the booking page's browser. Both fixes came with tests that failed on the code before them. #### What we take from it - A check in a page protects that page. Put the rule where the write happens. A page can still ask first, to show the right step. - Know when your proof is issued. A receipt handed back as a step starts proves the step started. - When the proof lives at a payment provider, fail closed if you cannot ask. - An error a caller can tell apart from not found is an answer. Refuse hidden things the way you refuse missing ones. ### Weekly blocks that keep to the wall clock Blocked time can now repeat every week, for a person, everyone or a room. We store one rule instead of a row per day, and work out only the days a reader asks about, on the business's own clock. Here is how that holds across daylight saving and a change of time zone, and five review findings, one of which made a 14-day read work out 314 zone days instead of 14. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/weekly-blocks-that-keep-to-the-wall-clock · markdown: https://bookatu.com/engineering/weekly-blocks-that-keep-to-the-wall-clock.md > **The short version** > > - Blocked time can now repeat every week, or every few weeks, for a person, for everyone or for a room, for up to two years. > - A weekly block is one row holding a rule. Nothing is written out per day. > - Readers work out only the days inside the window they ask about, on the series' own clock, so daylight saving never moves a block on the wall. > - Review found five problems before release 14 shipped. Each has a test that failed on the old code. A team meeting every Monday. A room cleaned every Friday. Until release 14, each had to be blocked one day at a time. The Blocked times form now has a Repeats weekly box: pick the weekdays, how often, and the last day. #### One rule, not a row per day Our post Recurring appointments and the 'admin force-book' rule shows a standing series booking each visit as a real booking. That suits appointments, which each have a client and a price. Blocked time only says these hours are not for booking. Two years of a weekday block would be over five hundred rows, and every edit would touch each one. So it is one rule: ```ts /** A weekly rule, as stored. */ export interface WeeklyRule { /** 0 = Sunday to 6 = Saturday, sorted, no repeats. */ weekdays: number[]; /** Wall-clock minutes since midnight; endMin 1440 is midnight at the end of the day. */ startMin: number; endMin: number; /** "YYYY-MM-DD", inclusive, on the rule's zone's calendar. */ fromDate: string; untilDate: string; /** 1 = every week, 2 = every other week, ... counted from fromDate's week. */ everyWeeks: number; } ``` A time_block_series row holds the rule, every 1 to 12 weeks, and the zone it was made in. A time_block_exceptions row removes one day, for This one. This and following moves the last date back. #### Only the days you ask about The engine asks about the days it offers. The calendar asks about a week. occurrencesBetween walks that window's days and no others: ```ts let first = dateKey(from, tz); let last = dateKey(new Date(to.getTime() - 1), tz); if (first < rule.fromDate) first = rule.fromDate; if (last > rule.untilDate) last = rule.untilDate; const out: Occurrence[] = []; for (let key = first, i = 0; key <= last && i < 800; key = addDaysToKey(key, 1), i++) { if (skip.has(key) || !ruleOccursOn(rule, key)) continue; const span = occurrenceSpan(key, rule.startMin, rule.endMin, tz, days); if (!span || span.endAt <= from || span.startAt >= to) continue; out.push({ date: key, ...span }); } ``` An occurrence ends by midnight, so it never leaves its day, and the work is the window's length, not the series'. A test asks about one day 500 days into a two-year daily series. It counts the zone days worked out and allows five at most, all within two days of the one asked about. #### On the business's own clock A rule says 09:00 to 10:00, not two instants. Each day becomes instants through zoneDay, the per-day clock the engine already uses for opening hours: ```ts export function occurrenceSpan( key: string, startMin: number, endMin: number, tz: string, days?: ZoneDays, ): { startAt: Date; endAt: Date } | null { const day = zoneDayOf(key, tz, days); const s = day.firstAtOrAfter(startMin); const e = day.firstAtOrAfter(endMin); if (e <= s) return null; return { startAt: day.instantAt(s), endAt: day.instantAt(e) }; } ``` In the test, a Monday block from 09:00 to 10:00 in Auckland holds 09:00 to 10:00 either side of 4 April 2027, when the clocks go back. The instant underneath moves from 20:00 to 21:00 UTC. A wall time the clocks skip does not exist, so a block starts at the first time after the gap. On 26 September 2027, when Auckland jumps from 02:00 to 03:00, a Sunday block from 02:00 to 03:30 holds 03:00 to 03:30. A block wholly inside the gap does not happen that day. A wall time shown twice is read the first time it shows, as opening hours are. #### The null that used to mean everyone Rooms came in the same release, through a new resource_id column. Before it, a null staffId meant everyone, and a room's block has a null staffId too. Read the old way, a room out of service would close the business. So every reader had to learn two things at once: a room's block is nobody's, and a weekly day holds what a one-off block would. That is the booking engine, the day check, the booking editor's clash warnings, a standing series' clash check, report capacity, MCP closures and calendar feeds. Tests walk each one through both. Our mobile API lists a room's blocks only when the client asks with include=resources, because a client built before rooms would read a null staffId as the business closed. #### What review found ##### Clock work that grew with every series Each series worked out the zone day for each of its dates on its own. A 14-day availability read with 30 weekday series asked for 314 zone days instead of 14, so every booking page and calendar feed slowed with each series a business added. A read now shares one cache, keyed by zone and date. A zone day is pure, so sharing it changes no answer: ```ts function zoneDayOf(key: string, tz: string, days?: ZoneDays): ZoneDay { if (!days) return zoneDay(key, tz); const k = `${tz} ${key}`; let day = days.get(k); if (!day) { day = zoneDay(key, tz); days.set(k, day); } return day; } ``` lib/dates also keeps one date-parts formatter per zone now. The test counts calls to zoneDay: at most 16 for 300 spans over 14 days, and at most 30 for the whole availability read. A characterization case checks the spans are unchanged. The calendar feed had also expanded weekly blocks for its last week out to 187 days. It now stops at seven. ##### A new time zone left the blocks behind A series keeps the zone it was made in. When an owner corrected the business's zone, opening hours moved to the new clock and weekly blocks did not. A 12:00 to 13:00 lunch made under Auckland held 10:00 to 11:00 Sydney time, while the list still said 12:00 PM to 1:00 PM. Saving a new zone now moves every series kept on the old business zone. A series on any other zone stays put, and the list names its zone. ##### A series with no days left This and following on a series' first day removes it. But the first day was worked out without the days already taken out one at a time. So This one on the first day, then This and following on the next, left a series with no days in the list. removeBlockedTime now checks seriesHasDayLeft, which walks the whole series, two years at most: ```ts if (scope === "following") { const until = addDaysToKey(occ!.date, -1); const untilDate = until < series.untilDate ? until : series.untilDate; if (!seriesHasDayLeft({ ...ruleOf(series), untilDate }, skipped)) return removeWhole(); // ... } if (!seriesHasDayLeft(ruleOf(series), new Set([...skipped, occ!.date]))) return removeWhole(); ``` ##### Two holes in our mobile API GET /time-blocks found each weekly day's series in the same list the Blocked times card uses, which stops at 60, and dropped days whose series was not in it. A client could show a person free while the engine held them. Those series are now read by id, and the test makes 61. And DELETE with a series id and scope=one or scope=following removed the whole series. A series id names no day, so the route now answers 422 and the library refuses it too: ```ts if (!occ && isSeriesId(id) && scope && scope !== "series") return false; ``` #### Trade-offs - Every read works out its days again. That is cheap per day now, and there are no per-day rows to keep in step. - Two years is the limit, which bounds the full walk in seriesHasDayLeft. - A rollback has a cost. Release 13 reads a room's block as everyone and never reads a series, so our deploy notes say to delete room blocks first and to warn owners that weekly blocks will vanish. - A one-off block is a moment, so it stays put when the zone changes. ### One pricing function, and the inputs that disagreed Public holiday and busy-time surcharges are priced by one pure function, shared by every door that charges them. Review still found doors that showed one price and charged another, because each handed that function different inputs: another branch, another start, another person. Here is the function, the refusal that caught some of it, and the door it could not protect. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/one-pricing-function-and-the-inputs-that-disagreed · markdown: https://bookatu.com/engineering/one-pricing-function-and-the-inputs-that-disagreed.md > **The short version** > > - Surcharges add a percent or an amount on chosen dates, public holidays or busy weekly times. With no rule set up, nothing changes. > - One pure function, priceSlot, prices them for every door that charges one, from the booking page to the API. > - Review still found doors that told one price and charged another. Most handed the function a different branch, start or person from the one they showed. > - An online booking that would now cost more than it was shown is refused, not charged. The API has no such guard. > - Each mismatch below was found in review before release 14 shipped, and each has a test that failed first. An owner sets a surcharge up in Settings > Surcharges: a name the client sees, a percent or an amount, and the dates, weekly times or national public holidays of New Zealand or Australia it covers. Our post One rule, every door showed every visit ending in one function. Surcharges taught us that one function is not enough. #### Eight rules, written down The top of lib/surcharges.ts writes the money rules out. In short: - The wall clock at the start decides. 18:00 to 21:00 takes 18:00 and 20:45, not 21:00. - Overlapping rules never add up. The highest surcharge wins, and a tie goes to the oldest rule. - A percent is of the price before any discount code, rounded half up, in whole units where a currency has no cents. - A fixed amount is added once per booking or visit. - Nothing is added to a booking priced at zero. - Changing a rule never reprices a booking. - With no active rule, priceSlot returns the base price and no lines. - A holiday rule names the holiday: "Public holiday surcharge (Christmas Day)". Our post Money math in integer cents, and the discount that vanished covers the rounding. Here is the heart of the function: ```ts for (const rule of input.rules) { const covered = input.lines.map( (l, i) => clocks[i] !== null && ruleInScope(rule, l.serviceId, input.locationId) && ruleCoversMoment(rule, clocks[i]!) && l.baseCents > 0, ); if (!covered.some(Boolean)) continue; let perLine: number[]; if (rule.amountType === "percent") { perLine = input.lines.map((l, i) => (covered[i] ? percentOf(l.baseCents, Math.min(MAX_SURCHARGE_PERCENT, rule.amount), input.currency) : 0)); } else { const first = covered.indexOf(true); const amount = fixedAmount(Math.min(MAX_FIXED_SURCHARGE, rule.amount), input.currency); perLine = input.lines.map((_, i) => (i === first ? amount : 0)); } const cents = perLine.reduce((a, b) => a + b, 0); if (cents <= 0) continue; // Strictly more wins, so on a tie the rule met first (made first) stays. if (!best || cents > best.cents) best = { rule, perLine, cents, first: perLine.findIndex((c) => c > 0) }; } ``` Its inputs are the rules, the lines (a service, a price and a start each), a zone, a branch and a currency. The function is pure, so it is only as right as those. Most bugs below were one input coming from somewhere other than what the client saw. #### The refusal that caught some of it Telling a surcharge before the client commits is a product rule. The booking page and the widget send back the surcharge they showed, and createBooking compares: ```ts if ( source === "online" && typeof input.shownSurchargeCents === "number" && Number.isFinite(input.shownSurchargeCents) && surcharge.cents > Math.max(0, Math.round(input.shownSurchargeCents)) ) return { ok: false, code: "surcharge_changed", error: "The price for this time has changed since it was shown. Please check the time again.", }; ``` It was meant for a rule added while a page sat open. It also turned a disagreement into a refusal, not a bigger bill. That is the better failure, but a client refused on every try still cannot book. And the API sends no such figure, so there a disagreement was charged. #### Another branch An online booking was priced at the branch of the person it landed on. A door that names no branch shows its times with no branch's own rule. That is the API, an agent, and every door while the MULTI_LOCATION_ENABLED flag is off, its default. So once a person was kept to a branch with its own rule, the API charged it without saying so, and the booking page refused every try. Now a client's booking is priced at the branch its door named: ```ts locationId: isStaffBooked ? assignedLocation : (input.locationId ?? null), ``` A client's repeats had the same mistake, priced at the branch the engine filed the first visit at. bookRepeats now keeps the door's own branch, which may be none. The New booking form had it the other way round. With Any available, the quote priced at no branch, while createBooking prices the team's booking at the branch of whoever the engine picks. A surcharge was saved with none shown and no waiver offered. The quote now asks the engine the same question: ```ts const pricedFor = staffId ?? (named ? null : await staffBookingAssignee(org.id, { serviceId, startAt, addOnIds, partySize })); const locationId = await staffBookingBranch(org.id, named, pricedFor); ``` That lookup first landed inline in app/, and our tenant guard, a test that fails on new inline org-scoped queries there, went red. It lives in lib/surcharges-db.ts now. #### Another start createVisit prices each service of a visit at its own start. The booking page marked a visit's times by the visit's start only. In the test, a colour starts at 16:00 and a cut at 17:00, on a Friday with 10% from 17:00 to 21:00. The page showed nothing, createVisit surcharged the cut, and the guard refused every try. A rule kept to the cut was also shown as a percent of the whole visit. Each start now says which services each rule covers, from visitRulesAt, and the page works the figure out on those. The visit's emails had the same blind spot: they told the first service's figures as the Total. They now tell the whole visit. #### Another person Prices per team member sit behind STAFF_PRICING_LIVE, a flag also off by default. With it on, the API's visit times priced a start at the person they placed it with, while POST /visits/book books anyone at each service's "from" price. In the test, Sam's colour is $150, Anna's is $120, and the cut is $80. The times said $253.00 and the booking was $220.00. The times now price the person asked for. Our mobile API surcharged team bookings but answered with no money, so a receptionist could quote the plain price. The answer now carries the total and the surcharge. Waiving one now takes the money permission there and on the web form. #### Another label, after a move A booking kept its surcharge through every move, and its label names the holiday. So a Christmas Day booking moved to 23 December still said "Public holiday surcharge (Christmas Day)" in the reminder, the API and at the point of sale. A move now prices it again at the new start and keeps the smaller: ```ts const cents = Math.max(0, Math.min(l.surchargeCents, priced.perLine[k] ?? 0)); const label = cents > 0 ? priced.total.label : null; ``` Off a holiday, it goes. Between holidays, the new one is named and the amount is no more. Onto a holiday, nothing is added. #### Two small things The holiday is added to a rule's name in one pass, so a $ or {holiday} in the name is not read as a pattern there. A unit test pins it. A business with no rule pays one query on an indexed column, and a characterization suite checks its booking page, API, MCP tool, point of sale, email and widget are unchanged. #### What we take from it - One function is necessary, not enough. Each input has to come from what that door showed. - Write the money rules down, and fold each fix back into them. - A refusal beats an overcharge. Where a door cannot say what it showed, as with our API, the inputs have to be right. - Test the door. Most of these tests ask a real route or action what it shows, book through it, and compare. ### Test mode inside production, without one real email Release 15 adds sandbox businesses: test businesses that sit in the production database beside real ones. They must never email a real person or charge a real card, and no live business may ever be deleted as one. Here is how two marks, a few CHECKs and triggers hold that line, how the expiry sweep is kept away from live businesses, and three design critic findings that changed the plan. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/test-mode-inside-production-without-one-real-email · markdown: https://bookatu.com/engineering/test-mode-inside-production-without-one-real-email.md > **The short version** > > - A sandbox is a business row in the production database with two marks, set when the row is made. A trigger stops either one changing. > - CHECKs and triggers keep a sandbox off a real Stripe account and off Bookatu billing, test keys on sandboxes, and outbox rows off live businesses. > - Code that could send or charge treats either mark as a sandbox. Code that deletes needs both. > - The expiry sweep deletes through one statement that names both marks. > - Three of a design critic's findings changed the plan: simulate ids, custom domains, and hidden businesses that answered differently from missing ones. > - Making sandboxes sits behind SANDBOX_CREATION_ENABLED, which is off by default in the code. Release 15 adds test mode for developers. A sandbox issues only bk_test_ keys, keeps every message it would send in an outbox, and simulates every payment. We built it inside production, the way Stripe's test mode works, so a sandbox runs exactly the code a live business runs. That only holds if nothing can mistake one kind of business for the other, so the first lines went in the database, where no code path can step round them. #### Two marks, set once Migration 0186 adds two booleans to organizations: sandbox and created_as_sandbox. Both default to false, so every existing business is live. The second looks redundant. It is there so that wiping a business needs two facts, not one. ```sql -- The flag and the marker agree on every row. alter table bookatu.organizations add constraint organizations_sandbox_marker check (sandbox = created_as_sandbox); -- A business is made live or as a sandbox, and stays that way. create or replace function bookatu.organizations_sandbox_immutable() returns trigger language plpgsql as $$ begin if new.sandbox is distinct from old.sandbox or new.created_as_sandbox is distinct from old.created_as_sandbox then raise exception 'a business is made live or as a sandbox and stays that way (organizations.sandbox cannot change)'; end if; return new; end $$; ``` So a live business can never become a sandbox, and so can never be wiped or expired as one. A sandbox can never be promoted into a live business full of test data. tests/integration/migration-0186.test.ts tries each flip on PGlite and expects each refused. Migration 0186 adds the other hard lines too: - A sandbox's payments account id, when set, starts acct_sandbox_, and no live business may hold one of that shape. - A sandbox has no Bookatu billing customer or subscription. - A bk_test_ key is exactly a key with livemode false, and only a sandbox may hold one. Connected apps follow the same rule. - Only a sandbox may have rows in the outbox or the simulated payments table, so a live business's message can never be swallowed there. #### Either mark to send, both to delete ```ts export function isSandboxOrg(org: SandboxMarks | null | undefined): boolean { return !!org && (org.sandbox === true || org.createdAsSandbox === true); } export function isDeletableSandbox(org: SandboxMarks | null | undefined): boolean { return !!org && org.sandbox === true && org.createdAsSandbox === true; } ``` Anything that could reach a real person or card treats either mark as a sandbox, as isSandboxOrg does, so it leans towards test. Anything that deletes asks isDeletableSandbox. The database keeps the marks equal, so the answers only differ on a row that should not exist, and on that row both fail safe: it sends nothing, and it is not deleted. #### An expiry sweep with one way to delete A sandbox unused for 30 days is deleted. Its maker is emailed from day 23, and while the maker can still be reached, a deletion needs that warning to have stood a week, so a missed run becomes a warning first, never a surprise. Every removal goes through one statement, whether it comes from the sweep, the developer, the platform console or a reset: ```ts export async function deleteSandboxRow(ex: SeedExecutor, orgId: string): Promise { const gone = await ex .delete(organizations) .where(and(eq(organizations.id, orgId), eq(organizations.sandbox, true), eq(organizations.createdAsSandbox, true))) .returning({ id: organizations.id }); return gone.length > 0; } ``` The sweep also selects only rows with both marks and checks each before it acts. Hand deleteSandboxRow a live business's id and it matches nothing. The lifecycle tests try a live business whose owner has made a sandbox, and a live one renamed to look like a sandbox. Then they run the sweep a year ahead against a live business made 400 days ago, and check it was neither warned nor deleted. #### Three findings that changed the design Before the build started, a design critic was given the plan and one brief: find every way a sandbox could send, charge, appear in public or hurt a live business, and check each choke point for a way round it. Here are three of its findings that changed the shape of the work. ##### Simulate ids that named any booking POST /api/v1/{slug}/sandbox/simulate/{event} makes things happen to a sandbox booking: a deposit paid, a no-show, reminders coming due. The plan checked that the URL's business was a sandbox, then took the booking id from the body. Some functions it would call, the deposit checkout among them, load a booking by id alone and find the business and its payments account from it. A test key with a live business's booking id could have reached a real booking and a real payments account. Now every event reads the booking by both ids first: ```ts /** A booking of THIS business only (another business's id is not found). */ async function sandboxAppointment(orgId: string, appointmentId: string): Promise { const row = ( await db .select() .from(appointments) .where(and(eq(appointments.id, appointmentId), eq(appointments.orgId, orgId))) .limit(1) )[0]; return row ?? null; } ``` tests/integration/r15-simulate-api.test.ts sends a live booking's id to a sandbox's simulate URL for all six events. Each answers 404 APPOINTMENT_NOT_FOUND. No Stripe client is built, nothing reaches Resend or Twilio, and the live booking is unchanged. ##### A CHECK on a deprecated column 0186 forbids a custom domain on a sandbox with a CHECK on organizations.custom_domain. The critic pointed out that this column is deprecated. Domains live in the custom_domains table, and that is what the host resolver reads. The CHECK would have passed its tests and stopped nothing. So the guard lives in code: addCustomDomain refuses a sandbox before any Vercel call, customDomainEntitled is false for one, and the resolver joins only live businesses. custom_domains has no trigger, so the test writes a sandbox's active domain straight into the table, as a bug might, and checks the resolver serves it to nobody while a live business's domain still resolves. ##### Hidden businesses that answered differently Every v1 API answer about a business now says livemode. The plan looked the URL's business up by slug for that, drafts and suspended businesses included. So a draft's slug would answer 404 with livemode: true, and a slug that does not exist 404 with none. Anyone could have probed for unpublished businesses by name. The envelope every API route goes through now notes a business only when the public may see it: ```ts if (org && publiclyVisible(org)) noteOrg({ id: org.id, slug: org.slug, sandbox: isSandboxOrg(org) }); else if (org) hidden = org; /** getPublicOrgBySlug's tests: may the public see this business at all? */ function publiclyVisible(org: Organization): boolean { return !org.internal && !!org.published && org.status !== "suspended" && org.status !== "cancelled"; } ``` A hidden business tells its livemode only to a caller whose own credential was verified. tests/integration/r15-core-envelope.test.ts calls a draft's slug and a missing one with no key, a stray bk_test_ bearer and Bookatu-Livemode: false, and expects the same status, bytes and header names each time. Sandbox slugs are sbx- and eight random characters, a prefix no live signup may take. #### Off until it is switched on Making sandboxes sits behind SANDBOX_CREATION_ENABLED, off by default in the code. That came from the critic too: a release rolled back to one with no send gate must not find sandboxes waiting. scripts/sandbox-quarantine.mjs counts them, then, only when asked, deletes rows with both marks. #### What we take from it - Draw the line you must never cross in the database, and test the database refusing. - Make a deletion need two facts, and a send need only one. - Check every id a caller hands you against the business in the URL. - Check a guard against the table the code really reads. - A hidden thing has to answer exactly like a missing one. ### One gate for every send and every charge A sandbox runs the same booking code as a live business, so every email, text and Stripe call had to be caught somewhere. We funnelled messages through one send gate and money through one Stripe gateway, then wrote static tests that fail when a new path appears. Here is how each choke point works, and the way round them that review still found. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/one-gate-for-every-send-and-every-charge · markdown: https://bookatu.com/engineering/one-gate-for-every-send-and-every-charge.md > **The short version** > > - Every transport that can carry a business's message to a real person asks one module, lib/send-gate.ts, before it sends. A sandbox's message goes to its outbox instead. > - The gate has three answers: live, sandbox and missing. Missing is a failed send, never a live one. > - Every Stripe client is built in lib/stripe.ts, which answers a sandbox's made-up account with a simulator. Every fall-back to Bookatu's own account is fenced. > - Static tests list every transport and every call to the platform account, and fail when one is added without a gate. > - Review still found a refund that slipped past the fence when its sandbox was deleted mid-flight. The fence now refuses the simulator's own ids, whoever they belong to. Test mode only works if a sandbox runs the real code. A sandbox booking must build the real confirmation from the real template, so a developer sees what their client would. But it must never arrive. Money is the same: the real deposit flow runs, and no card is charged. We could have put an if at every call site, but there are dozens, and the next one written would forget. So we looked for the narrowest points everything already passes through. #### One gate for messages Every transport that can put a business's message in front of a person, an email through Resend or a text or WhatsApp through Twilio, now asks the send gate first, with the business the message is from: ```ts export async function captureIfSandbox(msg: OutgoingMessage): Promise { const mode = await sendModeOf(msg.orgId); if (mode === "missing") throw new SendGateRefused(msg.orgId); if (mode === "live") return { captured: false }; const id = await recordOutboxMessage({ orgId: msg.orgId, channel: msg.channel, kind: msg.kind, // ...the recipient, subject, bodies and the booking it was about }); return { captured: true, id }; } ``` A live business gets captured: false, and the caller sends exactly as before. A sandbox's message is written to its outbox, which the developer reads in the admin or through GET /api/v1/{slug}/sandbox/outbox. Each sandbox keeps its newest 500. ##### Missing is not live The third answer came from our design critic. A send job can hold a business id while that sandbox is reset or expired. The first lookup answered a missing business as not a sandbox, which reads as live, and some senders fall back to the platform's own Twilio account when a business has none. Together, a deleted sandbox's text could have gone out for real. Now a missing business throws SendGateRefused, a failed send, and a database error throws too, so the caller's own failure path runs. Texts needed one more step: the provider used to read Twilio credentials and then send. It now decides first: ```ts export async function getSmsProvider(orgId: string): Promise { if (await sendsToOutbox(orgId)) return new OutboxSmsProvider(orgId); const creds = await twilioCreds(orgId); if (creds) return new TwilioSmsProvider(creds, orgId); return null; } ``` Underneath, a trigger from migration 0186 refuses an outbox row for a live business. So even a wrong answer from the gate could only fail loudly. It could never swallow a real client's reminder. ##### A test that finds new transports A gate is only as good as its coverage. tests/unit/r15-send-gate-guard.test.ts scans lib/ and app/ for every way code can reach a real inbox or phone: the Resend and Twilio endpoints, Meta's Graph API and the push services. Each file it finds must ask the gate before the send, inside the function that sends, or sit on an allowlist with a written reason. There are four, such as account mail to a Bookatu login and the expiry warning to a sandbox's own maker. A new transport anywhere fails the test until someone decides which it is. #### One gateway for money Stripe was easier, because it was already funnelled. Every Stripe client is built in lib/stripe.ts, so the API version is pinned in one place. A sandbox's account is always its made-up acct_sandbox_ id, and the gateway answers that before it imports the SDK: ```ts // TEST MODE (release 15): a sandbox's made-up account (acct_sandbox_...) is // answered by the payment simulator (lib/sandbox-stripe.ts). No real client // is built for it and STRIPE_SECRET_KEY is never read for it. if (isSandboxStripeAccount(accountId)) return createSandboxStripe(accountId); const { default: Stripe } = await import("stripe"); ``` So the deposit, card on file, gift card, shop, refund and no-show fee paths run unchanged against a simulated account. The simulator implements only what the code calls, and anything else throws, so a method we forgot fails closed instead of quietly reaching Stripe. Its ids are the usual prefix, then _test_sbx_ and 28 random letters and digits. It answers only for a business with both sandbox marks whose made-up account is exactly its own, and only ids it made for that business. Its errors use their own codes, never Stripe's resource_missing, so no caller's fall-back for a missing payment intent fires. Simulated events run through the real webhook handler with a fixed id per object and type, so a double click is deduplicated like a redelivery. A signed event from Stripe that concerns a sandbox is answered 200 and dropped. ##### Fencing the fall-backs The other way out is Bookatu's own Stripe account, which some payment paths fall back to when a business has no connected account. Each now calls a fence first: ```ts if (!org?.stripeAccountId) refusePlatformStripeFor(org, "a deposit refund", apt.stripePaymentIntentId); const stripe = org?.stripeAccountId ? await forConnectedAccount(org.stripeAccountId) : await getPlatformStripe(); await stripe.refunds.create({ payment_intent: apt.stripePaymentIntentId }); ``` tests/unit/r15-platform-stripe-fences.test.ts lists every call to getPlatformStripe, file by file, with the reason each is safe. It fails when a call is added, moved or loses its fence, and when a Stripe client is built anywhere but lib/stripe.ts. #### What review still found A final review read every path again and found a refund that got past the fence. A sandbox booking with a paid test deposit is cancelled through the MCP server while the developer, or the daily sweep, deletes the sandbox. The booking was loaded before the delete. When refundDeposit asks for the business there is none, and paymentsSimulated(null) is false. getPlatformStripe was meant as a last line, but it read only the business named in the URL, and the MCP server has none. So refunds.create would have gone to Stripe with Bookatu's live secret and a simulator id. Two changes close it. The fence now refuses the simulator's own ids whatever the business: ```ts export function refusePlatformStripeFor(org: PaymentsOrg | null | undefined, what: string, objectId?: string | null): void { if (paymentsSimulated(org) || isSandboxObjectId(objectId)) { throw new SandboxStripeUnsupported(`${what} on Bookatu's own Stripe account for a test business`); } } ``` And the last line also refuses during any API call made with a test credential: ```ts export async function getPlatformStripe(): Promise { const ctx = apiContext(); if (ctx?.org?.sandbox || ctx?.credential?.livemode === false) { throw new SandboxStripeUnsupported("Bookatu's own Stripe account during an API call to a test business"); } ``` tests/integration/r15-final-stripe-fence.test.ts swaps the Stripe SDK for a recorder. Its four refusal tests failed on the code before the fix, and a characterization case checks that a live business with no account of its own still refunds a real id on the platform account. Review found one more send the gate cannot cover, because it is no business's message. The button that sends a new email confirmation link mailed a Bookatu login on every press, and anyone can make a developer login for any address. The limit now lives in lib/welcome-email.ts, inside the send all three buttons go through, so they share it. #### What we take from it - Gate at the narrowest point everything already passes through, not at each caller. - Give not found its own answer. Folded into the default, a deleted thing gets the live path. - A gate needs a test that finds new ways round it, not only one that checks the old ones. - Make test ids look like nothing real, then refuse them at every door. ### API versions named by date, and limits on every answer Release 15 gives the Bookatu API dated versions and rate-limit headers. Every key is pinned to a version, a call with no key and no header gets the oldest version still served, and a deprecated version will say so on every answer. Here is the order a version is chosen in, the headers, and why a call the route refuses is now taken back off the key's count. The Bookatu engineering team · 2026-10-30 · Engineering · https://bookatu.com/engineering/api-versions-named-by-date-and-limits-on-every-answer · markdown: https://bookatu.com/engineering/api-versions-named-by-date-and-limits-on-every-answer.md > **The short version** > > - Versions are named for the day they are released. The first is 2026-10-30, and today it is the only one. > - A call is answered in the Bookatu-Version it asks for, else the version its key or connected app is pinned to, else the oldest version still supported. > - Every key and app made before versions existed is pinned to 2026-10-30. A new one is pinned to the version current when it is made. > - A deprecated version's answers will carry Deprecation, Sunset and a Link to the changelog. No version is deprecated yet. > - Every answer carries the RateLimit headers, and every 429 carries Retry-After. > - A call the route refuses before its own limiter is taken back off the key's count. An API other people build on has to change without breaking them. Release 15 adds two things to its answers to make that possible: the version each was answered in, and the limits the call is held to. #### Named for the day A version is a date, YYYY-MM-DD, the day it is released. A date sorts, needs no explanation, and tells you how old your integration is. The first, 2026-10-30, is the REST API, the MCP server and webhooks as they stood the day versions arrived. A version id must be a real calendar date, so 2026-13-01 is refused like any unknown version. The registry is a plain list in lib/api-versions.ts, and a test holds it to the published policy: one current version, oldest first, each named for its release day, supported at least 12 months after the next one ships, with its sunset announced at least 6 months ahead. #### Which version a call gets ```ts export function resolveApiVersion(input: { header: string | null | undefined; credential: string | null | undefined }): ResolvedApiVersion { const asked: string = (input.header ?? "").trim(); if (asked) { if (isApiVersionId(asked) && isSupportedApiVersion(asked)) return { ok: true, version: asked, source: "header" }; // ...400 UNSUPPORTED_API_VERSION, naming the supported versions } if (isSupportedApiVersion(input.credential)) return { ok: true, version: input.credential, source: "credential" }; return { ok: true, version: oldestSupportedVersion(), source: "default" }; } ``` The header wins, so a developer can try a newer version on one call before moving. Without it, the credential's pin decides. The pin is written when a key is made or a connected app approved, and survives a key rotation and a token refresh. Migration 0186 gave the column a default of 2026-10-30, so every existing key is pinned to the version that describes what it was already getting. A header naming anything else is refused before the handler runs: 400 UNSUPPORTED_API_VERSION, with the supported versions. Every answer says the version it was answered in, in Bookatu-Version. ##### Why the oldest, not the newest A call with no header and no key is one to the keyless doors, such as services, times and booking. There is nothing to pin. If it got the newest version, every one of those front ends would change under its owner the day a breaking version shipped. So it gets the oldest version still served, the behaviour it was most likely written against, and moves only when that version is switched off. A key pinned to a version since switched off is answered in the oldest one still supported, not refused. Refusing it would turn a sunset into an outage. #### Deprecation, built before it is needed A version on its way out will say so on every answer: Deprecation, an @ and a Unix time (RFC 9745); Sunset, an HTTP date (RFC 8594); and a Link to its changelog entry. ```ts export function deprecationHeaders(versionId: string): Record { const v = findApiVersion(versionId); if (!v || v.status !== "deprecated" || !v.deprecatedAt) return {}; const out: Record = { Deprecation: `@${Math.floor(dayMs(v.deprecatedAt) / 1000)}`, Link: `<${changelogUrl(v.id)}>; rel="deprecation"; type="text/html"`, }; if (v.sunsetAt) out.Sunset = new Date(dayMs(v.sunsetAt)).toUTCString(); return out; } ``` Today the registry holds one version and it is current, so no answer carries these yet. We built them anyway, because the first deprecation is the worst moment to find a bug in the plumbing. Tests swap in a registry with a deprecated version, check the exact strings, and check through the real envelope that a Link a route already sends is kept. #### Limits on every answer The limiter is older than release 15: a fixed window in Postgres, one atomic upsert per window, so it holds across serverless instances. What is new is that every answer says where the caller stands, across every window the call was counted against. apiFinalize, the hook that runs last on every call, takes every window the call was counted against. It reports the one closest to its limit in RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, and all of them in RateLimit-Policy, shortest first: 30;w=60, 2000;w=86400 for a key on the Solo plan. A 429 always carries Retry-After. The names are the IETF draft fields the limiter already sent, so no client reading them breaks. The limiter enforces by default. Each key now has its own windows at its plan's numbers, beside its business's windows for all keys together. A Bookatu platform admin can put a live key on the raised tier, four times its plan's numbers, at its own business only. A test key gets the sandbox ceilings, lower than the cheapest plan, whatever its tier. #### Giving a refusal back To hold each key to its own windows, the platform now counts the key before the route runs. Before release 15, a route checked the key's scope and business first and reached its limiter only after, so a call refused for a missing scope cost nothing. Counted up front, it did. Review found the case: an integration making 15 mis-scoped calls a minute beside 20 good ones sat under its Solo plan's 30. Its 31st call of the minute would have been a 429, in a release whose changelog says a standard key sees no change. The hook now gives such a call back: ```ts async function uncountRefused(state: PlatformCallState, res: Response, windows: RateLimitObservation[]): Promise { // Only ever set when the preflight counted the key. const keyId = state.countedKeyId; if (!keyId || state.limiterReached || res.status < 400 || res.status === 429) return windows; await uncountApiWindows([`rl:k:${keyId}:min`, `rl:k:${keyId}:day`]); return windows.map((w) => w.policy === RATE_POLICY.keyMinute || w.policy === RATE_POLICY.keyDay ? { ...w, remaining: w.remaining + 1, breached: w.remaining + 1 < 0 } : w, ); } ``` The route's own limiter sets limiterReached the moment it runs. So a refusal before it is given back, a refusal after it still counts, as it always did, and a 429 is never given back. uncountApiWindows only touches a window that has not reset, and never goes below zero. tests/integration/r15-final-rate-limits.test.ts makes 15 refused calls, then 20 good ones in the same minute, with a Solo key. All 20 answer, and the key's minute window reads 20. #### Three smaller things review found - MCP answers sent before the server's own limiter, such as a parse error, carried no RateLimit headers. They now report the key's windows, read and not counted. - A raised key at its own business that the public cannot see was held to the standard ceiling. Its own business is now the URL's business, seen or not. - A 429 from a counter with no policy name, such as sandboxes made per person, reported another window's headers. Those counters have names now. #### What we take from it - Pin every credential the day it is made, and give what cannot be pinned the oldest behaviour still served. - Build the deprecation headers before the first deprecation, and test them with a registry you make up. - When you move a counter earlier, give back what the old order never charged. - A changelog line that says nothing changes is a claim. Write the test that holds you to it. ### A hidden menu item is not a gate Almost every button in the Bookatu admin runs a server action, and each business decides on its own role grid who may do what. We audited every action against that grid. Of 40 candidate gaps, 34 held up and 6 were by design. Here is what the real ones had in common, the public side where the question is ownership, and how the fixes were tested on the old code first. The Bookatu engineering team · 2026-10-29 · Engineering · https://bookatu.com/engineering/a-hidden-menu-item-is-not-a-gate · markdown: https://bookatu.com/engineering/a-hidden-menu-item-is-not-a-gate.md > **The short version** > > - Each Bookatu business has a role grid that says what owners, admins, staff and trainees may do. The owner can change it: trust a staff member with Manage the business, or take it away from an admin. > - We audited every server action against that grid. Five read-only auditors each took one area, and an adversarial judge tried to refute every finding. 40 candidates came back, 34 held up and 6 were by design. > - The real gaps had three shapes: an action whose only guard was a menu that hid it, an action that did not repeat its page's gate, and an action that checked the role's name instead of the permission on this business's grid. > - On the public side the question is ownership. A client's actions reach only their own bookings, a card on file is replaced only by the client it belongs to, and "stop every link" now also ends a portal sign-in already in someone's browser. > - The fixes were written test-first: 446 characterization tests that pass on the old code, 266 new tests that fail on it, and the full suite of 14,563 tests green after the merge. > - We found all of these in our own audit and fixed them before anyone reported misuse. We have no evidence of misuse. Behind almost every button in the Bookatu admin is a server action: a function that runs on our server when the button is pressed. Who may press it is decided per business, by a grid of permissions. Owner, admin, staff and trainee start from defaults, and the owner can change every row but their own. A front desk might be given Edit the calendar. The grid was already checked in many places. What we had not done was ask the question the other way round, for every action we have: if this function runs, what made sure the person running it may? #### The menu is not the gate The admin menu decides what each person sees. Staff see only the items marked safe for them, and trainees see none: ```ts export function isNavItemVisible(item: { staff?: boolean }, role: Role | null | undefined): boolean { if (role === "trainee") return false; if (role === "staff") return item.staff === true; return true; } ``` That is a good rule for a menu, whose job is to keep the screen tidy for someone who does not set the business up. It is not a rule for anything else. Packages, memberships, promo codes, the floor plan, forms, programs, the gallery and the blog all sit behind items staff never see, and on several of them the actions only checked that the caller belonged to the business. Delete was usually gated. Create, edit and publish often were not. > A menu decides what you see. Only the action decides what you can do. A server action is an endpoint. The page that draws its button is one way to reach it, not the only one. So a hidden menu item says nothing about who can run the action behind it. #### A page gate is not an action gate The next layer is the page. Most setup pages call requireAdmin, which checks the Manage permission on this business's grid and sends anyone else back to the dashboard: ```ts export async function requireAdmin(slug: string): Promise { const access = await requireOrgAccess(slug); if (!(await hasPermission(access.role, PERMISSION.Manage, access.org.id))) redirect(`/${slug}/admin`); return access; } ``` The Settings page has used it for a long time. Its actions did not all follow. Several asked something narrower and older, whether the caller was an owner or an admin by name: ```ts const access = await requireOrgAccess(slug, ["owner", "admin"]); ``` Some pages disagreed the other way: the menu item was for Manage only, but the page and its actions let any member in. Only the action decides what gets written, so a page's gate is now a promise its actions keep. If a page is for Manage, every action it renders checks Manage itself, and the packages, memberships, promo codes, blog, announcements and reviews pages now use requireAdmin too. #### The role's name is not the permission Checking the name looks safe, because on the default grid owners and admins are exactly the people with Manage. It stops being safe the day an owner changes the grid, and it goes wrong in both directions. An owner can untick Manage the business for Admin. The admin can then no longer open Settings, as the owner asked, but the saves behind it still asked for the name, and an admin is still called admin. The other way round, an owner can trust a staff member with Manage: requireAdmin let them onto the page, and the name check behind it refused everything they saved. The Settings actions now ask what the page asks: ```ts /** * Who may save the Settings page: the page is requireAdmin, so what it saves is * the business's setup, the Manage permission on this business's own grid. Not * the role NAME: an owner can take Manage from Admin (the admin is then turned * away from the page, so they must be from its saves too) or trust a staff * member with it. * ... */ async function settingsEditor(slug: string): Promise { const access = await mayEditSettings(slug); if (!access) redirect(`/${slug}/admin`); return access; } /** The same check for the saves that answer their form: null = refused, nothing written. */ async function mayEditSettings(slug: string): Promise { const access = await requireOrgAccess(slug); return (await hasPermission(access.role, PERMISSION.Manage, access.org.id)) ? access : null; } ``` The business's id in that call matters as much as the permission. Without it, hasPermission answers from the platform's default grid, which is wrong for exactly the businesses that changed theirs. The same fix covered the team, services, products and stock, classes, forms, programs, reviews, newsletters and privacy. Invoices now follow the Finance page they live on, Manage plus See analytics & earnings, and adding a gallery storage pack changes the bill, so it needs Manage billing. The admin assistant needed the same rule one level down. It stays for owners and admins, on purpose, but an admin the owner had made read-only could still ask it to book someone in, confirm, and the booking was made. Each tool now names what it needs, in a Record over every tool, so a new one cannot be added without deciding: ```ts export const TOOL_PERMISSION: Record = { create_product: PERMISSION.Manage, update_service: PERMISSION.Manage, // ... sell_product: null, create_booking: PERMISSION.EditCalendar, reschedule_booking: PERMISSION.EditCalendar, // ... create_customer: null, create_form: PERMISSION.Manage, undo_create_form: PERMISSION.Manage, // ... }; ``` The check runs at every entry point: confirming one change, running a plan, undo and redo. A plan the role can only partly carry out runs none of it, because running the allowed steps and refusing halfway leaves the business in a state nobody asked for. The model is also told this month's revenue only when the person asking may see it. #### Reads leak too Not every gap was a write. Without See everyone's calendar, which staff lack by default, the calendar draws only your own column, but the jump-to-date helper beside it returned every column's bookings with the client's name and service. It now keeps the whole grid, so you can still see when people are busy, and labels any booking you are not on as "Busy", without reading that client's name. #### Refusing quietly, or telling the person Every refusal chooses between saying nothing and saying why. Our rule: if the app never offers the button to this person, the refusal can be quiet. The action does nothing, or sends them to the dashboard as requireAdmin always has, because nobody pressed a button to get there. If the app does offer the button, the person gets a sentence in the words of the grid: ```ts const SETTINGS_REFUSED = "Your role can't change the business's settings. Ask the owner."; export function toolRefusalMessage(permission: Permission): string { return permission === PERMISSION.EditCalendar ? "Your role can't change the calendar. Ask the owner." : "Your role can't change the business's services, products, stock, forms or announcements. Ask the owner."; } ``` Where the better answer was to stop offering the button, we stopped offering it. Deleting a client's photo needs Delete records, and the button is now hidden from anyone without it. Mark fulfilled follows Fulfil orders the same way. Our browser journeys found the same mistake from the other side: a Remove button the server refused and the page ignored. It is in our post on browser tests, and fixed in this release too. #### The public side is about ownership On the booking site and in the client portal, the question is whose record this is. The auditor for that area followed every client-facing action to the row it changes, and asked whether the session or signed link proves the client owns it, at the business in the address. Most actions already got this right. A client cancelling a class place from their account sends the place's id, and the id only chooses among their own: ```ts /** * A signed-in client cancels one of their own class places from their account * page. Whose place it can be is the session's to say: the enrolment id arrives * from the browser, and cancelMyPlace only ever reaches this client's own place * at this business, by the business's own rules. */ export async function cancelMyClassPlaceAction(slug: string, enrolmentId: string): Promise { const org = await requireOrg(slug); const session = await getCustomerSession(); if (!session || session.orgId !== org.id) redirect(`/${slug}/account`); const res = await cancelMyPlace({ org, customerId: session.customerId, enrolmentId: String(enrolmentId ?? ""), via: "account", }); // ... } ``` That is only as good as the session behind it, which is where both public gaps were. ##### Stop every link means every link A studio can press "stop every link" when a gallery link has gone to the wrong person. It adds one to the client's session epoch, and every link carries the epoch it was issued with, so all of them stop at once. They did stop. But the 30-day portal cookie a link sets never looked at the epoch again, so a browser that had already opened one stayed signed in as the client. The cookie now carries the epoch too, and every read of the session checks it: ```ts export async function getCustomerSession(): Promise { const store = await cookies(); const parsed = decode(store.get(COOKIE)?.value ?? store.get(LEGACY_COOKIE)?.value); if (!parsed) return null; // ... const { customerSessionEpoch } = await import("@/lib/customer-links"); const current = await customerSessionEpoch(parsed.orgId, parsed.customerId); if (current === null || current !== (parsed.epoch ?? 0)) return null; return parsed; } ``` Cookies set before the change read as epoch 0, the starting value. A client whose links were never stopped is still at 0, so the release itself signs nobody out. A client whose links were stopped is not, and their old cookie stops working, which is what the button always promised. Magic links and Google sign-in both stamp the epoch now. ##### A card on file is changed by its owner The booking form can save a card for no-show protection. It finds the client from the contact details typed into it, and finding is not proof: the person at the keyboard might not be that client. Two changes close it. A client who already has a card or a consent on file has to be signed in to their own portal to change it: ```ts if (onFile?.stripePaymentMethodId || onFile?.cardMandateAcceptedAt) { const session = await getCustomerSession(); if (!session || session.orgId !== org.id || session.customerId !== customerId) { return { ok: false, reason: "sign_in_required" }; } } ``` That answer comes before any call to the payment provider or any write, and the booking step shows it as a sign-in prompt. And the card and the consent are now written to the client only when the payment provider confirms the card was saved, so a form someone abandons changes nothing. #### How the audit ran The audit had four steps, each with one job. 1. **Audit, read-only, by area.** Five auditors, one area each: configuration, the catalog, operations, marketing and the rest of the admin, and the public site. They could read the code and change nothing. For every exported action they followed the gate to the end, through helpers and library code, found the page and menu item that offer it, and wrote down who can call it today and who should. 40 candidates came back. 2. **Verify, adversarially.** One judge, whose job was to refute each candidate in the code: a check further down the chain, an action nothing can reach, or behaviour meant for staff because a page they use offers it. The judge was told to be careful about taking abilities away. 34 survived. 3. **Fix, test-first, in two batches.** Two fixers in separate worktrees: 25 findings about the business's setup, and 9 about operations, the assistant and the public side. Tests first, then code. 4. **Merge and run everything.** Both batches merged with no conflicts, then the full suite ran on a freshly migrated scratch database, and a full build. The six rejections were worth as much as the 34. Someone without Edit the calendar may schedule class sessions that do not clash, on purpose; only Schedule anyway, over a clash, needs it. Opening hours changed from the calendar follow Edit the calendar, as their own comment says. A photographer's delivery controls sit on the client page staff already use. A form's share link returns nothing clients cannot already see. Price tiers are not a record type Delete records covers. And opening the assistant to staff would have widened it. Each would have taken away something a business may rely on. #### Tests on the old code first The fixes followed our rule for any change to code that already works. Characterization tests pin who must keep working: the owner, an admin on the default grid, and a staff member the owner trusted with the permission, and that staff and trainees who were refused stay refused. They have to pass on the old code. New-behaviour tests check that a refused caller writes nothing, sends nothing and gets nothing back. They have to fail on it. Each case says how to set up a fresh target, how to call the action and what to look at. The same look decides both directions: ```ts /** A staff member the owner trusted with `perms` on top of the default grid. */ export function staffGranted(...perms: Permission[]): Caller { return { label: `a staff member granted ${perms.join(" + ")}`, login: "staff", grid: { role: "staff", grant: perms } }; } /** An admin from whom the owner took `perms` away. */ export function adminWithout(...perms: Permission[]): Caller { return { label: `an admin without ${perms.join(" + ")}`, login: "admin", grid: { role: "admin", revoke: perms } }; } /** The caller is refused: nothing `look` sees changes, and nothing leaks back. */ export async function expectNoWrite(c: GateCase, who: Caller): Promise { const s = await c.seed(); const before = await c.look(s); const out = await settle(c.run(s)); await drain(); const after = await c.look(s); expect(after, `${c.name} by ${who.label}`).toEqual(before); c.refused?.(out, s); return out; } ``` Nothing about access is faked: each call carries a real session cookie, against real membership and grid rows. The admin without Manage and the staff member granted it are the two callers a name check gets wrong, and every gate is tested with both. A script runs the new test files on a worktree of the base commit. The first batch had 12 characterization files with 388 tests, all green on the base, and 12 new-behaviour files with 223 tests, every one red with an assertion failure: the write happened, or the redirect did not. The second batch added 58 characterization and 43 new-behaviour tests, with the same result. Fourteen existing tests had to change because a fix contradicts them, each marked CHANGED DELIBERATELY with the reason. Four of them had pinned that a staff member could still save a service as it was. After the merge the full suite passed: 1,129 files and 14,563 tests. #### What we left alone on purpose - Staff with Manage still cannot make API keys. A characterization test pins that decision, and a fix does not overturn one in passing. The gap the audit found was the other direction, an admin without Manage, and that is closed. - The assistant stays for owners and admins. Each tool inside it now follows the grid. - The retention page stays open to staff, because their dashboard links to it. Its send buttons were the gap, and they need Manage. - Removing a gallery storage pack still needs only Manage, because it never adds to the bill. We found all of this in our own audit and fixed it before anyone reported misuse. We have no evidence of misuse. #### What we take from it - Gate the action, not the menu. A menu is for tidiness. Anything that writes or reads something private asks for itself. - If a page has a gate, every action it renders repeats it. The page makes the promise and the actions keep it. - Ask for the permission on this business's grid, never the role's name, and always pass the business. A check that is right on the default grid is wrong for exactly the owners who used the grid. - Refuse quietly only where the app never offered the button. Where it did, say why, or stop offering it. - Give your auditors a skeptic. Six of forty findings would have taken away something a business relies on. ### Browser tests that read like the journey Our newest browser tests are written as the journey a person takes, in Given, When and Then steps that use their words. Quick swap needs two waiting clients reaching for one time, so every journey takes a seeded set of its own and can run again. Here is how they wait for hydration, ignore React's hidden streaming copy, pass three times in a row with no retries, and the four app bugs they found. The Bookatu engineering team · 2026-10-29 · Engineering · https://bookatu.com/engineering/browser-tests-that-read-like-the-journey · markdown: https://bookatu.com/engineering/browser-tests-that-read-like-the-journey.md > **The short version** > > - Six Playwright specs with 38 journeys cover our newest features: Quick swap, the Security page, Remove and sign out, passkeys, the blog's own-AI panel and several services in one visit. > - Each journey is a run of test.step calls named Given, When and Then, in the words of the person on the page. A failure names the step where that person would have got stuck. > - Seeds write each scenario into a local in-process Postgres as a pool of independent sets. A journey claims a set nobody has used, with an atomic mkdir, so one seed survives repeats. > - Two helpers do most of the waiting. One waits until React has hydrated the button about to be tapped. The other reads only visible text, because React keeps a hidden copy of content while a page streams in. > - Every spec passed three times in a row with retries off, and so did the merged run of all six on one server: 0 failed, 0 flaky. > - The run found four app bugs: a claim tapped before the scripts load, a Remove button that did nothing, Continue racing tap-to-advance, and a phone number matching the wrong client. All four are fixed in this release. Most of our tests run in vitest against a real Postgres, in process. They are fast, and they are where the rules are pinned. They cannot tell us what a person sees: whether the button is there, whether a tap does anything, whether the words are the ones the code meant. For our newest features we added browser journeys that do, written to read like the journey they cover. #### Quick swap, as the people in it live it Quick swap is a good test of the idea, because it is a story with several people in it. A client inside the late-cancel window asks to swap out instead of paying the fee. Two clients on the waitlist get a one-tap link to that time. The first to take it is booked in, and the asking client is released with no fee. The second is told the time has gone. The engine underneath has its own integration tests, including two claims racing inside one Promise.all. The browser journey covers the same moment the way the two waiting clients live it: each in a browser of their own, both with the offer open, one tapping a moment before the other. ```ts test("NEGATIVE: a second waiting client is too late once the first has taken the time", async ({ page, visitor }) => { const set = takeSet("on"); const bPage = await visitor(); const cPage = await visitor(); await test.step(`Given ${set.a.firstName} asked to swap out, and ${set.b.firstName} and ${set.c.firstName} both have the offer open`, async () => { expectBeforeCutoff(); await openMyBooking(page, set.a.bookingPath, set.a.firstName); await askToSwapOut(page); await openOffer(bPage, set.b.claimPath); await expectSpotOffered(bPage, set.b.firstName); await openOffer(cPage, set.c.claimPath); await expectSpotOffered(cPage, set.c.firstName); }); await test.step(`When ${set.b.firstName} takes the spot first`, async () => { await bPage.getByRole("button", { name: "Take this spot" }).click(); await expect(bPage.getByRole("heading", { name: "You're booked in" })).toBeVisible(); // ... }); await test.step(`And ${set.c.firstName} then taps Take this spot on the page they still had open`, async () => { await cPage.getByRole("button", { name: "Take this spot" }).click(); }); await test.step(`Then ${set.c.firstName} is told the spot is taken, that they are still on the waitlist, and is not booked`, async () => { await expectSpotGone(cPage); await expect(cPage.getByRole("heading", { name: "You're booked in" })).toHaveCount(0); }); // ... }); ``` visitor is a small fixture that opens another browser context, as a second person on another phone would have. The business is one more, signed in to the admin. Locators mostly use roles and the English copy, so a renamed button is noticed. #### Given, When and Then are just steps There is no Gherkin file and no step registry. A step is a test.step with a sentence for its name, and the helpers inside it are named for what people do: openMyBooking, askToSwapOut, openOffer, expectSpotGone. Playwright records each step in its report and trace, so a failure is pinned to the sentence it happened in. The takeover journey, with the seeded names filled in, starts like this: ```text Given Aroha asked to swap out of their late Gel Manicure, and Bianca Lowe is on the waitlist for it And the time is emailed to Bianca and Chloe, the two clients waiting for it, and to nobody else When Bianca opens the offer link from their email Then they see the spot up for grabs: what, when, and until when When they take the spot Then they are booked in, with a reference And Aroha's booking page says the time was taken and they are released with no fee, deposit refunded ``` A journey also says what must not happen. Those are marked NEGATIVE in the title: the second claimer, a tampered link, a link opened on another business's site, an offer after the asking client withdrew, and a business with Quick swap off, where a late cancel is the plain cancel it always was. #### Each journey takes its own seeded set A journey changes the data it runs on. Once Bianca has the time, nobody can take it again. So scripts/seed-bdd-quick-swap.ts makes a pool: 45 independent sets at one business, each with a team member of its own, client A booked with them about six hours out with a paid deposit, and clients B and C on the waitlist for that service, person and day. With a person each, one set's offer reaches only its own B and C. A journey claims a set nobody has used yet by making a directory. mkdir is atomic, so two workers can never take the same set, and the directories live under the seed's id, so a new seed starts with every set free: ```ts function takeSet(kind: "on" | "off" | "credit"): { n: number } { const s = scenario!; const dir = path.join(BDD_DIR, "quick-swap.taken", s.seedId); fs.mkdirSync(dir, { recursive: true }); const sets: Array<{ n: number }> = s[kind].sets; for (const set of sets) { try { fs.mkdirSync(path.join(dir, `${kind}-${set.n}`)); return set; } catch (e) { if ((e as NodeJS.ErrnoException).code !== "EEXIST") throw e; } } throw new Error(`every seeded "${kind}" Quick swap booking is used: rerun tools/bdd-serve.sh to reseed`); } ``` Running out is loud, and so is a stale seed. The bookings start about six hours after seeding and offers close two hours before the start, so each journey begins by checking there are at least fifteen minutes before offers close. If there are not, the Given step fails and says to reseed. It does not skip, because a skipped journey looks too much like a passing one. The seeds only ever write to the local rig. Each exits if a real database variable is set or the PGlite directory is not, and imports the database code only after that check. The specs run only when E2E_URL is plain http on this machine. The first version compared a string prefix, which a reviewer noticed would accept http://localhost.example.com, so the URL is parsed now: ```ts /** Only ever the local rig: a plain http URL whose host is this machine (no tricks like localhost.example.com or user@host). */ const LOCAL_RIG = (() => { try { const u = new URL(process.env.E2E_URL ?? ""); return u.protocol === "http:" && ["localhost", "127.0.0.1"].includes(u.hostname) && !u.username && !u.password; } catch { return false; } })(); ``` #### A seed must not do the app's job The seed signs B's and C's links with the app's own token helper, exactly what the offer signs when A asks. That made the journeys easy to write, and a reviewer found the cost: the takeover journey would pass even if the offer reached nobody, because the links the journey opened never came from the offer. With no email key, the local dev server logs every email it would send, one line each. So the journey now reads that log: ```ts await expect.poll(() => emailsTo("quick_swap_offer", s.orgId, set.b.email), { timeout: 30_000 }).toBe(1); expect(emailsTo("quick_swap_offer", s.orgId, set.c.email)).toBe(1); expect(emailsTo("quick_swap_offer", s.orgId, set.a.email), "never to the client who asked").toBe(0); expect(emailLines("quick_swap_offer", s.orgId).length - offersBefore, "offer emails sent for this ask").toBe(2); ``` It also checks the business's activity log says the time was offered to two waiting clients. The same review found other promises that were only checked as copy. "Released with no fee" was checked through a sentence the page prints for every swapped booking, so the journey now reads the deposit status and the money line in the activity log too. Expected texts are not typed into the spec either. The seed computes dates, times and amounts with the app's own formatters and writes them into the scenario file, so a journey that reads a booking from Europe/London expects exactly what the app prints there. #### Waiting for hydration before tapping Server rendering means the page arrives before it works. A button drawn by the server is visible and enabled, and a tap on it does nothing until React has hydrated it, or, for a form with a server action, posts the plain form instead. Playwright's auto-waiting checks that an element is visible, stable and enabled. It cannot know whether React is listening yet. Where a page has its own sign of being live, the journey waits for that. The manage-booking page adds an "On your clock:" line for a reader in another time zone only once it runs in the browser, so the Quick swap journeys run in Europe/London and wait for that line before any tap. The claim page has no such sign, so a helper asks React directly: ```ts /** A page's buttons answer a tap only once React has hydrated it. */ async function whenLive(target: Locator): Promise { await expect .poll(() => target.evaluate((el) => Object.keys(el).some((k) => k.startsWith("__reactProps$"))), { timeout: 30_000 }) .toBe(true); } ``` That key is a React internal, fine in a test helper and nowhere else, and if React renames it the helper times out loudly. It earned its place. A reviewer noticed the passing journeys tapped Take this spot without it, which is exactly how a person on a slow phone meets the first bug below. #### React's hidden streaming copy While a page streams in, React briefly keeps content it is about to show in a hidden container, a div with an id like S:0, then swaps it into place. For a moment the same sentence is in the DOM twice. Playwright locators are strict: a getByText that matches two elements fails rather than guess, and our first runs hit that on exactly the pages that stream. Every text check now goes through one helper that counts only what a person can see: ```ts /** * Text a person can see. While a page streams in, React briefly keeps a hidden * copy of what it is about to show; that copy is nobody's to read. */ function shown(page: Page, text: string | RegExp, opts: { exact?: boolean } = {}) { return page.getByText(text, opts).filter({ visible: true }); } ``` The tempting fix is .first(), which makes the clash go away by picking one of the two. Nothing says it picks the one on screen. Filtering on visibility says what we mean. #### Three times, with no retries Our smoke tests against the live site allow two retries, because a long run over the internet has hiccups that are not bugs. These journeys run on a local rig, where a retry would only hide a race. So every spec had to pass three times in a row with retries off: ```bash E2E_URL=http://localhost:3600 E2E_ADMIN_SLUG=test-business \ npx playwright test --project=bdd --workers=1 --retries=0 --repeat-each=3 tests/e2e/bdd/quick-swap.spec.ts ``` --repeat-each=3 is where the pools earn their keep: three runs of a journey take three sets. Three builders wrote the specs, each on a server of their own, and two reviewers read them against the features' promises. After the review fixes, all six specs ran together on one server seeded by all four scripts. The 35 journeys that could pass did, three times each, in 10.5 minutes, with 0 failures and 0 flaky runs. The other three recorded app bugs. We also broke the code on purpose. Removing the preventDefault from the blog panel's Enter handler made the Enter journey fail, and switching off the never-with refusal in the visit engine made the combination journey fail. A green run is only worth something if the journey can go red. Time is the one thing a journey cannot always fake. page.clock holds the browser's timers, and one bug below needed exactly that. Auto sign-out could not use it, because its warning asks the server how long is left, and the server counts in real time. So that seed pre-signs the session's last-activity stamp every five seconds over three hours, and the journey picks the one from 13 minutes 55 seconds ago. #### What the run found Three journeys could not pass, because the app was wrong. Each was written to assert the correct behaviour and marked test.fixme, which keeps the suite green and keeps the bug as the test that has to pass once it is fixed. The fourth bug turned up in the test data. All four are fixed in this release, and the three journeys are ordinary journeys again. ##### A claim tapped before the scripts load The claim button is a progressively enhanced form, so without JavaScript it still posts and the server action still runs. A waiting client on a slow phone who tapped before the scripts arrived was booked in, and the asking client released. But the page sent back was built from the link's state, which now read as taken, so it told the person who had just won the time that it was gone and that they were still on the waitlist. The journey drops the page's script chunks until the tap: ```ts // B is on a patchy connection: the page arrives, but its scripts do not // (until after the tap), so the button works as a plain form. const bPage = await visitor(); let tapped = false; await bPage.context().route(/\/_next\/static\/chunks\//, (route) => (tapped ? route.continue() : route.abort())); // ... tapped = true; await bPage.getByRole("button", { name: "Take this spot" }).click(); ``` The fix recognises the client whose link took the time and shows them that they are booked in, with their reference, both straight after the plain post and when they open the link again. Everyone else still sees that the spot has gone. ##### A Remove button that did nothing On the team page, an admin saw a plain Remove on an owner's row. The server refused, correctly, because only an owner can remove an owner. But the action returned nothing and the button ignored the outcome, so the click did nothing and said nothing. The new Remove and sign out button beside it already followed the right rule. Now the plain Remove follows it too, and a refusal from the server is shown to the person instead of swallowed. ##### Continue racing tap-to-advance On the booking page, tapping a service moves the page on by itself 260 ms later. Continue moved on at once and did not cancel the move already waiting. Tap a service, then Continue within that beat, as Playwright and people both do, and the page moved on twice: past Date & time to Your details, with no time chosen. Add another service was never shown, and Confirm booking at the end did nothing. The journey holds the browser's timers so the pending move is still waiting when Continue is tapped: ```ts await page.clock.install(); await page.goto(`/${s.on.slug}/book`); // ... // Hold the page's timers still, so the tap-to-advance is pending when Continue is tapped. await page.clock.pauseAt(Date.now() + 1_000); // ... tap the service ... await page.getByRole("button", { name: "Continue", exact: true }).click(); await expect(step(page, "Date & time")).toHaveAttribute("aria-current", "step"); // The page's own beat (260 ms) passes. await page.clock.runFor(1_000); await expect(step(page, "Date & time")).toHaveAttribute("aria-current", "step"); ``` Now any explicit move cancels a pending one, and Confirm booking with no time chosen no longer fails silently. ##### A phone number that matched the wrong client This one came from the test data. An early version of the visit journeys reused a phone number across new clients, and a confirmation email went to a different test client from the one who booked. Online bookings were matched by email, then by phone, so a new person with a new email who typed a phone number already on file was booked under the earlier client's record, and the earlier client got the email. The specs now give every client a fresh number, and the app no longer uses a phone match when the booker gave an email and the record found by phone has a different one. That booking gets a client of its own, which the business can merge if it was the same person. #### What we take from it - Write the journey in the person's words. A failing step should read like the place they got stuck. - Give every run its own data. A pool of seeded sets and an atomic claim make repeats cheap and retries unnecessary. - Do not let the seed do the app's job. If the seed makes the link, check that the app sent it. - Wait for what the person waits for. Visible is not the same as live, and the DOM can hold a copy nobody sees. - Turn retries off on a local rig, and break the code on purpose. A journey that cannot go red proves nothing. ### A private channel nobody else can join The who's-online bar in our admin had not connected for three months, and nothing on screen said so. Allowing the socket in our CSP would have taken five minutes and switched back on a channel anyone could read and spoof. Here is what we built instead: a short-lived token, a private channel, and two row-level security rules, plus two lessons from putting them into production. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/a-private-channel-nobody-else-can-join · markdown: https://bookatu.com/engineering/a-private-channel-nobody-else-can-join.md > **The short version** > > - The who's-online bar in our admin had not connected since 28 July. That day we started enforcing our Content-Security-Policy, and its connect-src did not list the Realtime websocket. A blocked socket shows the user nothing at all. > - Adding that origin to the policy would have taken five minutes, and it would have switched a public channel back on. Anyone holding the public key and an org id could have read it and added fake people to it. > - What we shipped instead: a fifteen-minute token that the server signs only for a signed-in member, a private channel, and two row-level security policies on realtime.messages that match the channel topic to the org_id claim inside that token. > - Two lessons from production. The migration first tried to ALTER a table our migration user does not own, and failed safely inside one transaction. Then a hand-written probe was refused, because the realtime client only turns presence on when the channel has a presence listener. Our admin has a small avatar stack in the header showing who else from the business has the admin open, the way a shared document shows other editors. It runs on Supabase Realtime presence. Everyone in a business joins one channel, tracks themselves, and draws whoever else is there. When realtime is not available the bar degrades to just you, with the words "Only you here" beside it. That degradation is the whole reason this story took three months to notice. A business with one person in the admin sees "Only you here" whether the feature works or not. A business with three people sees it too, if the socket never opens. The failure looked exactly like a quiet afternoon. #### How the bar went dark On 28 July we moved our CSP from report-only to enforced. It had sat in report-only for months, and before that change it had no report-uri either, so it blocked nothing and collected nothing. Enforcing it was the right call. connect-src limits where injected script can send data, which is most of what an XSS is for. We went through the allowlist carefully: Stripe, reCAPTCHA, analytics beacons. This is the connect-src that shipped that day: ```ts "connect-src 'self' https://*.stripe.com https://api.stripe.com https://www.google.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com", ``` There is no Realtime origin in it. The presence client opens a websocket to the project's Realtime host, the enforced policy refused it, and the bar stayed at its starting state. The bar's code wraps everything in a try/catch on purpose, because presence is a nice-to-have and must never crash the admin. That was deliberate, and it meant nothing on screen ever looked wrong. We were not entirely blind. A stricter report-only policy shipped alongside the enforced one, and it had the same connect-src gap plus a report-uri, so the browser reported the violation. The enforced policy blocked the same request. Nobody was reading those reports with the who's-online bar in mind. #### The five-minute fix we did not ship Once we found it, the obvious fix was one more origin in connect-src. Before adding it, we read what the bar was actually joining: ```tsx channel = supa.channel(topic, { config: { presence: { key: me.id } } }); channel.on("presence", { event: "sync" }, () => { const state = channel!.presenceState(); // ... }); channel.subscribe((status) => { if (status === "SUBSCRIBED" && channel) void channel.track(me); }); ``` That is a public channel on the topic presence:org:, opened with the anon key. The anon key is public by design. It ships in every browser bundle, because the browser client needs it. So anyone who had it and knew an org id could subscribe and see who was online, with names and avatars. They could also call track() and appear in someone else's admin as a person who does not exist. So the CSP gap that broke the feature had also, by accident, been the only thing keeping that channel shut. Allowing the socket on its own would have fixed the bug by reopening the hole. > Before you remove the thing that is blocking a feature, find out what else it has been blocking. #### A socket is not access We still needed the socket, so the CSP change came first and stayed narrow. connect-src gains exactly one origin, built at build time from the same public Supabase URL the browser client uses. It is never a wildcard: wss://*.supabase.co would let injected script talk to any Supabase project anywhere, which is the very thing connect-src exists to prevent. Anything that does not parse as a plain https URL with an ordinary host adds nothing, and the policy stays byte for byte what it was. ```ts function realtimeOrigin(): string | null { const raw = process.env.NEXT_PUBLIC_SUPABASE_URL; if (!raw || !raw.trim()) return null; let url: URL; try { url = new URL(raw.trim()); } catch { return null; } if (url.protocol !== "https:" || url.username || url.password) return null; // An ordinary DNS name, optionally with a port. Rules out "*" and anything // else that could mean more than this one host inside a CSP source list. if (!/^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)+(:\d{1,5})?$/i.test(url.host)) return null; return `wss://${url.host}`; } ``` There is no https:// entry for the same host. The realtime client always hands its transport a WebSocket and never turns on the long-poll fallback, and presence does not use the REST broadcast endpoint. The embeddable booking widget has its own policies and does not get the origin either, because it never opens a socket. Opening a socket is now allowed. Joining our channel is a separate question. #### A token the server signs only for members Supabase Realtime has private channels. A client may join one only when row-level security on the realtime.messages table allows it, and that check runs as the role in the client's token, with that token's claims. That means the token's claims are the access control, so we decided to mint our own token rather than lean on the anon key. ```ts const iat = Math.floor((input.now ?? Date.now()) / 1000); const exp = iat + REALTIME_TOKEN_TTL_SECONDS; // 15 * 60 const header = { alg: "HS256", typ: "JWT" }; const claims = { role: "authenticated", aud: "authenticated", sub: input.userId, org_id: input.orgId, iat, exp, }; const signingInput = `${b64url(header)}.${b64url(claims)}`; const signature = crypto.createHmac("sha256", secret).update(signingInput).digest("base64url"); ``` role is the role Realtime runs the check as. That role has no grants on our application schema, so the token reaches no data at all. All it can do is satisfy the two rules described below. org_id names exactly one business. exp is fifteen minutes, so a copied token stops being useful soon after. It is signed with HS256 on node:crypto, the same way the codebase already signs its other tokens. If the signing secret is not configured we mint nothing, and the bar shows just you, the same as when realtime is off. The minting function deliberately checks nothing except its inputs. The decision about who gets a token lives in one route, POST /api/realtime/token. That route does not copy the admin's access rules. It calls the same guard the admin layout calls, so the token goes to exactly the people the layout would draw the bar for: ```ts const user = await getCurrentUser(); if (!user) return refuse(401); const orgId = await readOrgId(req); if (!orgId) return refuse(400); const org = await getOrgById(orgId); if (!org) return refuse(404); let access: Awaited>; try { access = await requireOrgAccess(org.slug); } catch (e) { const status = guardStatus(e); if (status === null) throw e; return refuse(status); } if (access.org.status === "suspended" && !access.isPlatformOwner) return refuse(403); if (access.org.id !== org.id || access.user.id !== user.id) return refuse(403); const grant = mintRealtimeToken({ userId: access.user.id, orgId: access.org.id }); if (!grant) return refuse(503); ``` A few details mattered here. The session check runs before the body is even read, so a caller with no session learns nothing about whether their request was well formed. The guard was written for pages, so it says no by redirecting or calling notFound(). guardStatus turns those into bare status codes and rethrows anything else as a real fault. The org id in the body is only ever a question. The token names the business the guard actually let the caller into, never one the client asserted. Every response, refusals included, is sent with Cache-Control: no-store. #### The rules are the access control Migration 0160 adds two policies to realtime.messages. One is for SELECT, which lets a client receive presence. One is for INSERT, which lets it track itself. Both use the same condition: ```sql create policy bookatu_presence_read on realtime.messages for select to authenticated using ( realtime.messages.extension = 'presence' and realtime.topic() = 'presence:org:' || (auth.jwt() ->> 'org_id') ); ``` realtime.topic() and auth.jwt() are Supabase's own functions: the topic of the channel being checked, and the claims of the token. So a token for one business matches that business's presence topic and nothing else. It cannot see another business's topic, and it cannot use broadcast even on its own. A token with no org_id claim, such as an ordinary Supabase-auth session, matches nothing, because 'presence:org:' || NULL is NULL. The anon key gets no rule at all. Each of those statements is a test. The realtime schema only exists on Supabase, and locally and in every test our database is PGlite. So the migration test builds a small Supabase-shaped stand-in: a realtime.messages table with row-level security on, plus the two functions defined as Supabase defines them. It then checks receive and track as each kind of caller: our own topic, another business's topic, broadcast on our own topic, a token with no org_id, and anon. On PGlite itself the real migration is a guarded no-op, because every PGlite suite replays every migration. #### Joining, and staying joined In the browser, the bar fetches a token, gives it to Realtime, and only then joins, with private: true: ```tsx await supa.realtime.setAuth(grant.token); // ... const ch = supa.channel(topic, { config: { private: true, presence: { key: me.id } } }); channel = ch; ch.on("presence", { event: "sync" }, () => { // rebuild the avatar list from ch.presenceState() }); ch.subscribe((status) => { if (status === "SUBSCRIBED" && !gone) void ch.track(me); }); scheduleRenewal(grant.expiresAt); ``` A fifteen-minute token means renewing it, and renewal turned out to be most of the client code. The bar asks for a new token three minutes before the current one ends, with the wait clamped between thirty seconds and twelve minutes so a skewed clock still renews in time. It hands the new token to the joined channel with setAuth, which needs no rejoin. If a renewal fails, it retries every thirty seconds while the old token lasts. If none arrives in time, the bar leaves on its own instead of waiting to be dropped, and shows only what it knows: you. The bar also separates two kinds of no. A definite no, such as not signed in, not a member, or realtime not set up (the route's 503), is not retried on a timer. A no that may pass, such as being offline or a server fault, is retried on a backoff that starts at thirty seconds and doubles up to five minutes. It also retries at once when the browser comes back online or the page is shown again. A laptop that wakes from sleep before its Wi-Fi does should not need a reload to see its colleagues. #### Lesson one: the table was not ours The first version of the migration also switched row-level security on for realtime.messages, as a belt to go with the braces. On the production apply it failed with "must be owner of table messages". On Supabase, our migration user does not own that table. It failed safely. The file runs as a single transaction, so the error took the whole file down and nothing was applied. There was no half-migrated state with policies on a table whose row-level security we were unsure of. The fix was to stop trying to change a table that belongs to someone else, and to check it instead: ```sql if not (select relrowsecurity from pg_class where oid = 'realtime.messages'::regclass) then raise exception 'row-level security is off on realtime.messages; switch it on in Supabase first. Nothing was changed.'; end if; ``` Supabase keeps row-level security on for that table, so in practice this check always passes. It is there so that our policies can never be the only thing standing in for it. The test suite now pins both behaviours: the file never alters realtime.messages, and it raises without adding any rule when row-level security is off. One more operational detail. CREATE POLICY takes an ACCESS EXCLUSIVE lock on a table that Realtime itself reads, so the file sets lock_timeout to five seconds. If the table is busy, the migration fails, changing nothing, and the apply script tries it up to six times in all, retrying only on the lock-not-available error code. Any other error stops it immediately. After applying, the script reads pg_policies back and fails unless both rules are present, permissive, for authenticated only, and checking the extension, the topic and the org_id claim. #### Lesson two: a probe needs a presence listener With the rules live, we wanted to see a real join succeed and a wrong one fail. A quick hand-written probe minted a token, joined the private topic, and waited for SUBSCRIBED. It was refused. For a few minutes it looked as if the rules were wrong. They were right. The probe was wrong, and the reason is in the realtime client's subscribe(): ```js const presence_enabled = (!!this.bindings[REALTIME_LISTEN_TYPES.PRESENCE] && this.bindings[REALTIME_LISTEN_TYPES.PRESENCE].length > 0) || ((_c = this.params.config.presence) === null || _c === void 0 ? void 0 : _c.enabled) === true; // ... presence: Object.assign(Object.assign({}, presence), { enabled: presence_enabled }), ``` Passing a presence key in the channel config does not turn presence on. The client turns it on only when the channel has at least one presence listener registered, or when the config sets enabled: true explicitly. Our probe registered no listener, so its join asked for a channel with presence off. Our rules only ever admit presence, so nothing matched and the server correctly said no. The bar itself always registers its sync listener before it calls subscribe(), which is why it joined and the probe did not. The lesson: probe with the client exactly as the product uses it. We already had a test that does. It drives the real supabase-js and realtime-js client with only the WebSocket swapped for a recorder, and it pins what Realtime actually receives: the socket URL, private: true, the minted token rather than the anon key, and a renewal sent to the joined channel with no second join. The hand-written probe skipped all that, and misled us within minutes. #### What we take from it - A graceful fallback that looks like the normal state will hide a failure for as long as you let it. If a feature can quietly degrade, something other than a person's eyes has to notice when it does. - When a security control breaks a feature, read the feature before you widen the control. Here the control had been covering for a design that should never have shipped public. - Put the access decision in one place and reuse it. The token route calls the admin layout's own guard, so the two cannot drift apart. - Migrations that touch someone else's schema should check, not change. Run them as one transaction, so a failure leaves nothing behind. - Test through the real client. Some of what a realtime join asks the server for is decided by the library before a byte is sent. ### One rule, every door A client can now book a colour and a cut as one visit, and a braiding salon can say that a 4 braids and a 6 braids are never booked together. Bookatu takes bookings through five different doors. This is how those rules live in one place that every door has to pass through, and how we taught an engine built around a grid to find starts that are not on it. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/one-rule-every-door · markdown: https://bookatu.com/engineering/one-rule-every-door.md > **The short version** > > - Whether a set of services can be one visit is decided by two pure functions: visitProblem in lib/visits-shared.ts and comboProblem in lib/service-combos.ts. Neither touches the database. > - Every door that books a visit ends in one server function, createVisit in lib/visits.ts, which asks both questions before anything is written. The booking page, the staff New booking form, the v1 API and the MCP server all call it. > - Because the rules are pure and client-safe, the booking wizard and the staff form use the same functions to decide what to show. The UI may hide a choice. Only the seam refuses one. > - Times for a visit come from the same availability engine every single booking uses, asked once per service. The only thing relaxed is the grid, through an exactStarts parameter, because a 45-minute colour puts the cut at a quarter to. > - When a reviewer found a bug in how a moved visit was checked, the fix went into the one helper that lays a visit out, and every door that moves a visit was corrected by it. Release 5 brought two features that sound small and are not. A visit is two to four different services for one client, one straight after another, possibly with different people: a colour with Sam, then a cut with Anna. Combination rules let a business say which services go together, per service: "only with these", "never with these", and, for an extra, whether it adds its own minutes to the booking. The example we kept coming back to was a braiding salon whose 4 braids and 6 braids are mutually exclusive. A client books one or the other. The rules themselves are a page of code. The hard part was that a booking does not arrive at Bookatu through one door. #### Five ways in - The booking page, where a client picks services in a wizard and books online (app/[org]/(site)/book/actions.ts). - The staff New booking form, where the team books a visit for a client on the phone or at the desk (app/[org]/admin/appointments/actions.ts). - The v1 REST API: POST /visits/book for a client booking online, POST /visits for the business's own key, and GET /visits/availability for times. - The MCP server, whose create_visit and get_visit_availability tools are what an AI assistant calls on a client's behalf. - The owner's phone app, which books through its own route under app/api/mobile. Each of those has its own request shape, its own validation and its own way of saying no. The tempting design is to check the rules where the request comes in, because that is where the request is understood best. We have been down that road before, and one of our v1 routes carries a comment about it that predates visits entirely: > Re-implementing the rules here is how the app and the web would slowly come to disagree about money. Five copies of a combination rule would agree on the day they were written. The sixth door, or the first change to what a visit may contain, is where they stop agreeing, and nothing would notice, because each door's tests would be testing its own copy. #### The rule, with no database The first half of the seam is a function that takes the services in order, the facts about each one, and whether a client or the team is asking. It returns the first reason these cannot be one visit, or null. ```ts export function visitProblem( serviceIds: string[], facts: Map | Record, opts: { online: boolean }, ): VisitProblem | null { if (serviceIds.length < MIN_VISIT_SERVICES) return "too_few"; if (serviceIds.length > MAX_VISIT_SERVICES) return "too_many"; if (new Set(serviceIds).size !== serviceIds.length) return "repeated"; const get = (id: string) => (facts instanceof Map ? facts.get(id) : facts[id]); for (const id of serviceIds) { const f = get(id); if (!f || !f.active) return "unavailable"; if (f.isAddOn) return "add_on"; if (f.isGroup) return "class"; if (f.videoMeeting) return "video"; if ((f.staffRequired ?? 1) > 1) return "team"; if (opts.online && !f.bookableOnline) return "unavailable"; } return null; } ``` The online flag is the only difference between a client and the team. A client books only what the business offers online. The team can book anything the business offers, including a service it keeps off the booking page. The cap of four is in the same file with its reason written down: four covers the real combinations, and the availability search asks once per service, so it has to stay cheap enough for the booking page. The second half is the business's own rules. They are loaded from a service_links table, but the decision is again a pure function. Two services clash if either one says "never with" the other, or if either has an "only with" list the other is not on. ```ts /** Whether either of the two says "never with" the other. */ export function neverTogether(rules: ComboRules | null | undefined, a: string, b: string): boolean { if (!rules || a === b) return false; return Boolean(rules[a]?.never?.includes(b) || rules[b]?.never?.includes(a)); } /** Whether two services can be in one visit, and if not, why. */ export function servicesClash(rules: ComboRules | null | undefined, a: string, b: string): ComboClash | null { if (!rules) return null; if (neverTogether(rules, a, b)) return "excluded"; const onlyA = rules[a]?.only; const onlyB = rules[b]?.only; if ((onlyA && !onlyA.includes(b)) || (onlyB && !onlyB.includes(a))) return "not_allowed"; return null; } ``` comboProblem walks every pair of services, then every extra against the service it was added to, then every extra against everything else in the booking, and returns the first clash with the two ids it is about. A business that has set no rules gets null before any of that runs, which is how every business that never opens the rules editor books exactly as it did before. #### Where the doors meet The second half of the seam is createVisit. It is the only function that writes a visit, and it asks its questions in a fixed order before it opens a transaction: is this business offering visits to clients at all, is it a restaurant (a party is seated for one reservation, so there is no visit to make), can these services be one visit, and do the business's rules let them go together. ```ts // Clients only once the business has turned it on; the team always. if (!staffBooked && !visitOffer(settings)) { return refuse("not_offered", "This business books one service at a time online."); } // A restaurant seats a party for one reservation; there is no visit to make. if (org && vertical(org.industry).value === "restaurant") { return refuse("cant_combine", "Those services can't be booked together in one visit."); } const ids = input.lines.map((l) => l.serviceId); const { rows: serviceRows, facts } = await serviceFacts(orgId, ids); if (visitProblem(ids, facts, { online: !staffBooked })) { return refuse("cant_combine", "Those services can't be booked together in one visit."); } // ...extras read for each line... const clash = await checkCombination( orgId, input.lines.map((l, k) => ({ serviceId: l.serviceId, extraIds: extrasByLine[k].map((x) => x.id) })), /* names already read */, ); if (clash) return refuse("cant_combine", clash.error, { combo: clash.named }); ``` Only after that does it ask the availability engine whether the whole visit fits, and only after that does it create a client, price the lines, share one discount across them and write anything. A refusal at any of these checks leaves no trace: the tests for it check that no appointment and no client row was created. Who is asking is the BookingSource argument. The booking page passes "online". The staff form passes whichever channel the team picked, a phone booking or a walk-in. The API has one function for each path, and the source each one passes is the difference that matters: ```ts // lib/api-visits.ts, bookClientVisit (POST /visits/book, create_visit) const result = await createVisit( { orgId: org.id, lines: await linesForClient(org.id, first, rest, input.staffId || null, input.addOnIds), /* ... */ }, "online", ); // lib/api-visits.ts, bookTeamVisit (POST /visits, the business's own key) const result = await createVisit( { orgId: org.id, lines, /* ... */ }, "admin", ); ``` The MCP server does not get a function of its own at all. Each visit tool is a thin wrapper over the operation its REST route calls, so the two surfaces cannot answer differently: ```ts export async function createVisitMcp(orgId: string, args: unknown, opts: { appBase: string }) { return unwrap(await bookClientVisit(await orgOrThrow(orgId), args, { channel: "mcp", appBase: opts.appBase })); } ``` The refusal comes back from createVisit carrying the pair by name, and each door only decides how to say it. The booking page says it in the business's language from the translation catalog. The staff form adds a pointer to where the rule can be changed, under Services. The API returns the engine's own English sentence with a 409 and the code cant_combine, and the MCP server returns the same words as a tool error with the code in its data. The sentence is built in one place too, so the integration tests for different doors assert the same words: "4 braids and 6 braids can't be booked together." ##### The phone app has the least to check To be straight about the fifth door: the owner's phone app does not book visits. Its booking route takes one service, with no extras, and hands it to createBooking in lib/appointments.ts, the same function behind every single booking on the web and through POST /book. There is no pair to compare, so there is nothing for a combination rule to say. What matters is where it stands. createBooking is the single-booking seam, and it already refuses an extra the service does not take, with the same checkCombination call and the same named reason. The phone app sits behind it rather than beside it. #### Asking for times is a second question Booking is not the only moment a door needs the rules. Before a client picks a time, the page asks which times the visit fits. If that answer ignored the rules, the wizard could offer a slot for a 4 braids and a 6 braids, the client would pick it, and only then would createVisit refuse. So the times doors ask the same functions before they search. This is the booking page's: ```ts if (visitProblem(ids, facts, { online: true })) return []; // Services the business's rules keep apart are no visit either (S3-K4). if (await checkCombination(org.id, ids.map((serviceId) => ({ serviceId })))) return []; ``` The comment above that function states the goal plainly: a stale page can never be offered a time it cannot book. The API's visitTimes makes the same two calls and turns a problem into a 409, and the staff form's times ask checkCombination before searching. This is the one place the doors repeat themselves: three call sites asking the same shared questions. We accepted it because what they repeat is a call, not a rule, and because createVisit asks again regardless. A mistake at a times door can show or hide a time. It cannot write a booking. #### Back to back on an engine built for a grid The availability engine in lib/availability.ts offers starts on the business's grid. With a 30 minute interval and a 9:00 opening, a client sees 9:00, 9:30, 10:00, and a booking for 9:15 is refused. We have a characterization test pinning exactly that, written before visits existed, and it still passes. A visit breaks the assumption immediately. A 45 minute colour at 9:00 means the cut starts at 9:45, which is not on the grid, and refusing it would make most visits unbookable. We did not write a second engine for visits. Everything the engine knows about a single booking still has to hold for each service of a visit: the person's hours and break, their other bookings with the buffer, the room the service needs, the notice period and the horizon. So lib/visits-availability.ts asks the existing engine once per service. The first service is asked on the grid over the whole range. Each later one is asked at exactly the instants the visit would put it at. ```ts const first = await ask(0, { ...range, ...(firstExact ? { exactStarts: firstExact } : {}) }); const later: Array> = []; for (let k = 1; k < lines.length; k++) { const starts = first.flatMap((d) => d.slots.map((s) => plus(toDate(s.startAt).getTime(), offsets[k]))); const found = new Map(); if (starts.length > 0) { const days = await ask(k, { fromKey: range.fromKey, toKey: addDaysToKey(range.toKey, 1), exactStarts: starts }); for (const d of days) for (const s of d.slots) if (s.staffIds.length > 0) found.set(toDate(s.startAt).getTime(), s); } later.push(found); } ``` Inside the engine, exactStarts changes two things and nothing else. The candidate starts are the instants handed in instead of the grid, and the window check stops requiring a start to sit on the grid. Opening, closing and the break still apply. ```ts const onGrid = p.exactStartMins == null; const fitsWindow = (w: WorkWindow | null | undefined, start: number, end: number): boolean => !!w && start >= w.openMin && end <= w.closeMin && (!onGrid || (start - w.openMin) % interval === 0) && !(w.brk && start < w.brk.endMin && w.brk.startMin < end); // ... if (!onGrid) { for (const m of p.exactStartMins!) tryStarts.add(m); } else { if (businessWindow) addGrid(businessWindow); // ... } ``` Only the visit search sets exactStarts, so every other caller gets the grid it always had. The cost is one engine pass per service for the whole range, at most four, rather than one per candidate start. The day after the range is included for the later services, so a visit that runs past midnight is still found. At booking time the same reasoning applies once more. createVisit calls resolveVisitSequence, which checks each service at its time through resolveBookingSlot, the function a single booking is checked with. The first service of a client's visit must be on the grid like any client booking. The later ones, and every service the team books, are checked at their exact start. #### The UI uses the same functions lib/service-combos.ts is pure and client-safe, as is lib/visits-shared.ts, so the booking wizard and the staff form import the rules directly. The wizard only lists a service as something to add when it goes with every service already in the visit, and when the client changes the first service, it lets go of any added service that no longer fits: ```tsx // And each one only while it goes with the services before it (S3-K4): a // saved 6 braids is let go of when the first service is now a 4 braids. const visitKey = (serviceId ? keepCompatible(comboRules, [serviceId, ...visitAdded]).slice(1) : visitAdded).join(","); ``` The staff form runs comboProblem over what is on the form and shows the same sentence as a warning before anyone presses Book. This is where the seam pays off for the people using it, because the reason a choice is missing on screen is the same reason the server would give. But the line we hold is that the UI may hide and only the seam may refuse. Nothing on the client is trusted to keep a rule. It only saves somebody a round trip. #### What one seam bought us The first payoff is the tests. The combination rules have integration tests through the doors on a real in-process Postgres: createVisit directly, the booking page's actions, the staff form's actions, the v1 visit routes, and the v1 and MCP booking tools for extras. They do not each test a copy. They test that each door reaches the one implementation and reports what it says. ```ts it("refuses two services that are never together, whichever of them the rule was set on", async () => { const s = await braids("cmbvisit"); await rule(s, s.sixId, s.fourId, "excludes"); const res = await createVisit( { orgId: s.orgId, lines: [{ serviceId: s.fourId }, { serviceId: s.sixId }], startAt: at(dayKey(8), 540), ...who("bria.visit@example.com") }, "phone", ); expect(res).toMatchObject({ ok: false, code: "cant_combine", error: "4 braids and 6 braids can't be booked together.", combo: { kind: "services", first: "4 braids", second: "6 braids" }, }); expect(await rows(s.orgId)).toHaveLength(0); expect(await clients(s.orgId)).toHaveLength(0); }); ``` The second payoff arrived in the release review. A reviewer found that moving a whole visit checked its services back to back, even when the team had already dragged one service later on its own. The person doing the later service was checked at a time it would never be saved at, and could be double-booked at the time it was. The search and the check both worked out each service's start in one helper in lib/visits-availability.ts. The fix let that helper take the gaps the visit is booked with, and fall back to back to back only when none are given; lib/visits.ts now passes the booked gaps from its two move functions. ```ts function startsFor(durations: number[], offsets?: number[]): number[] { return offsets?.length === durations.length ? offsets : visitOffsets(durations); } ``` Every way of moving a whole visit goes through those two functions, moveVisit and visitMoveTimes: the client's manage link, the v1 reschedule routes and the MCP reschedule tool. One fix corrected all of them, and the test for it exercises both the client's path and the team's. In a design where each door kept its own idea of when a visit's services start, the same fix would have been a search for every copy, and the copy nobody found would have been the next bug report. None of this is novel. A rule that matters lives in one function, and every way in has to pass through it. What made it hold here was being strict about which side of the line each thing sits on. The doors parse, authenticate and translate. They do not decide. ### Pin today, fail first Most of what we ship changes code that already works for businesses taking bookings every day. Before a feature touches that code, we write down what it does today as tests that must pass on the old commit, then tests for the new behaviour that must fail on it. A small script checks both against a copy of the base. Review findings get the same treatment: no fix until a test reproduces the finding. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/pin-today-fail-first · markdown: https://bookatu.com/engineering/pin-today-fail-first.md > **The short version** > > - Before a feature touches existing code, we write characterization tests that pin what that code does today. They have to pass on the base commit, untouched. > - Then we write tests for the new behaviour. They have to fail on the base commit, and why they fail matters as much as the fact that they do. > - A short script copies the test files into a git worktree of the base commit and runs them there, one file at a time, so both claims are checked rather than remembered. > - When a feature has to change something a characterization test pinned, the test is edited in place and marked CHANGED DELIBERATELY, with what it used to say and why. There are 101 of those markers across 49 test files. > - Review findings are hypotheses. Each one is reproduced by a failing test before anybody fixes it. In our first release review, 10 of 19 findings were refuted before any fix was written. Release 5 let a client book several services as one visit, a colour and then a cut, possibly with different people. It also let a business say which services go together. Both features run straight through the booking engine, the booking page, the staff New booking form, the public API and the MCP server: code that every business on Bookatu relies on, most of which has nothing to do with visits and never will. The risk in a feature like that is rarely the new code. It is the old code doing something slightly different afterwards, in a place nobody was looking. So every feature starts the same way, with two sets of tests written before the code, each with a different job. #### Two kinds of test The first kind says what the code does today. We call these characterization tests, after Michael Feathers, and they live in files named *-characterization.test.ts. There are over a hundred of them. Each opens with a header comment saying what it pins, and against which feature. This is the one written before visits existed: ```ts /** * CHARACTERIZATION (S3-K5, rows 19 and 24): what one booking, and two separate * bookings of the same client on the same day, do TODAY, before a client can * book several services in one visit. * * The visit is off by default and every single-service path must stay exactly * as it is, so these are pinned on the commit before it: * * - the engine offers a service only on the business's grid, and a client * booking a time off it is refused; * - a booking on the booking page is one appointment: one confirmation for the * client, one "New booking" email for the business; * ... */ ``` The second kind says what the feature will do. Their headers start with NEW instead, and they describe the behaviour that does not exist yet. The two kinds are kept in separate files on purpose, because they are checked in opposite directions. #### Pinning today A characterization test is not a claim that today's behaviour is right. It is a claim that today's behaviour is what it is, so that any change to it is a decision and not an accident. That is why the rule is that it must pass on the base commit with no help. If it does not pass there, it is describing what somebody believes the code does, which is a different and much less useful thing. The visit work had one obvious danger. A colour of 45 minutes followed by a cut means the cut starts at a quarter to the hour, and our availability engine had only ever offered starts on the business's grid. Visits would need that relaxed. A single booking must not notice. So the first thing pinned was the grid itself: ```ts it("lists starts every slot interval from opening, and refuses a client's time off the grid", async () => { const biz = await business("vchgrid", { slotIntervalMin: 30 }); const day = dayKey(6); const [d] = await getAvailability({ orgId: biz.orgId, serviceId: biz.serviceId, durationMin: 30, fromKey: day, toKey: day }); expect(d.open).toBe(true); expect(d.slots.slice(0, 3).map((s) => s.startMin)).toEqual([540, 570, 600]); expect(d.slots.every((s) => (s.startMin - 540) % 30 === 0)).toBe(true); const off = await resolveBookingSlot({ orgId: biz.orgId, serviceId: biz.serviceId, durationMin: 30, startAt: at(day, 555), staffId: biz.samId }); expect(off.ok).toBe(false); const on = await resolveBookingSlot({ orgId: biz.orgId, serviceId: biz.serviceId, durationMin: 30, startAt: at(day, 570), staffId: biz.samId }); expect(on).toMatchObject({ ok: true, staffId: biz.samId }); }); ``` The combination rules got the same treatment, and one of their characterization tests is a good example of pinning scope rather than behaviour. Once a business can say that a 4 braids and a 6 braids are never booked together, the easy mistake is for that rule to leak beyond a single visit. So before the rules existed, we pinned that one client can book both, as two separate bookings on the same day, each with the same extra. That test still passes today. The rule applies inside a booking and nowhere else, and the test is the reason we know. ```ts it("is offered with every service: both braids take the same extra, and one client books both", async () => { const s = await braids("cxboth"); const day = dayKey(9); const four = await createBooking( { orgId: s.orgId, serviceId: s.fourId, startAt: at(day, 540), ...client("bria.both@example.com"), addOnIds: [s.beadsId] }, "online", ); const six = await createBooking( { orgId: s.orgId, serviceId: s.sixId, startAt: at(day, 720), ...client("bria.both@example.com"), addOnIds: [s.beadsId] }, "online", ); expect(four.ok && six.ok).toBe(true); expect(four.appointment!.customerId).toBe(six.appointment!.customerId); // ... }); ``` #### Failing first, for the right reason The new tests go in the other direction. Each must fail on the base commit, because a test of new behaviour that already passes is testing something that was already true. This is the visit's counterpart to the grid test above: with a 45 minute first service on a 30 minute grid, the visit starts on the grid and the second service starts at 9:45. ```ts it("starts the next service off the grid when the one before is not a whole number of slots", async () => { const s = await salon("vavoffgrid", { slotIntervalMin: 30 }, { durationMin: 45 }); const d = await startsOn(s, [{ serviceId: s.colourId }, { serviceId: s.cutId }]); expect(minutes(d).every((m) => (m - 540) % 30 === 0)).toBe(true); expect(planAt(d, 540)![1].startAt).toEqual(at(DAY, 585)); }); ``` Both of these tests pass now, side by side, and that is the point. The single booking still lives on the grid. The visit's later service does not. They could only both pass because the engine was given a parameter that only the visit's search sets, and the characterization test is what would have gone red if that parameter had leaked. Failing on the base is necessary and not sufficient. A test can be red for reasons that have nothing to do with the behaviour it describes, and a red you have not read is no better than a green you have not read. We wrote about the green version of this problem in Green for the wrong reason. The red version is the same mistake from the other side. - An assertion that fails with today's value is the right reason. It means the test reaches the code it is about and the code says something else today. - A missing module is a weak reason. The visit tests above import lib/visits-availability.ts, which did not exist on the base, so that file goes red before a single assertion runs. That proves the file is new. It says nothing about whether its assertions would catch a wrong answer, which is what breaking the code on purpose afterwards is for. - A fixture that cannot be set up is the wrong reason. A test whose setup writes to a table the base does not have fails in its setup, and would fail the same way if the feature were never written. #### The red check Saying a test passes or fails on the base is easy. Checking it means having the base commit somewhere you can run it, with the new test files in it and nothing else from the feature. We do that with a short shell script in our own tooling, outside the app. Its first lines say what it is for: characterization tests must pass there, and new-behaviour tests must fail there. The technique is simple. The script makes a detached git worktree of the base commit, once, and links the working tree's node_modules into it so nothing is installed twice. Each run resets that worktree, copies in any new helper files under tests/ that are not tests themselves (a new fixture the new tests need), then copies in one test file at a time, runs vitest on just that file, records the result, and puts the worktree back the way it was before the next one. The heart of it: ```bash git -C $TREE worktree add --detach $WT $BASE_REF ln -s $TREE/node_modules $WT/node_modules # ... for f in "$@"; do mkdir -p "$WT/$(dirname $f)"; cp "$TREE/$f" "$WT/$f" name=$(echo $f | tr '/' '_') (cd $WT && npx vitest run "$f" --maxWorkers=2 > "$OUT/$name.txt" 2>&1); rc=$? # ... if [ $rc -ne 0 ]; then echo "RED $f |$counts | $why"; else echo "GREEN $f |$counts"; fi git -C $WT checkout -q -- "$f" 2>/dev/null || rm -f "$WT/$f" done ``` A few details earn their place. - The output is one line per file, RED or GREEN, with the test counts. Every characterization file should say GREEN and every new file should say RED. Anything else has to be explained before the work goes on. - Beside each RED goes the first error line from that file's output, picked by matching patterns like AssertionError, TypeError and Cannot find module. That is the line that tells you whether the red is the right red, and putting it on the summary line means it gets read. - The full output of each file is kept, so a surprising line can be followed up without running anything again. - Each base worktree is named for the base commit and a label. Several builders can run red checks against the same base at once without overwriting each other's copies. - It runs the test files from the working tree against the base's code, so the comparison is exactly the tests that will be committed, against exactly the code they will be committed on top of. #### When today has to change Sometimes the feature is supposed to change something a characterization test pinned. That is fine, and it happens often, because a characterization test pins today's behaviour whether or not today's behaviour is right. What is not fine is for the test to change quietly. The convention is to edit the assertion in place, keep the test in its characterization file, and leave a comment that starts CHANGED DELIBERATELY, naming the work that changed it, what it used to pin, and why the new value is the right one. Some of those comments are a record of a bug we found by pinning it. The money screens were characterized before we built deposit reconciliation. When later work on what money was actually collected came through, one of the pinned figures turned out to be counting money that was still owed: ```ts // CHANGED DELIBERATELY (T5-E3, requirement 18): "Collected in person" was // the booked price less deposits ($150 - $25 = $125), which counted the $75 // still owed on the $100 visit as collected. It is now what was recorded // on those visits in person: the $50 cash. expect(text).toMatch(/Collected in person \$50\.00 cash, card terminal, bank & other, as recorded/); ``` Another came from consent law. A characterization test had pinned that recording a client's marketing consent minted a fresh unsubscribe token. That was today's behaviour, and the test held it exactly. It was also wrong, because a fresh token kills the unsubscribe link in every email already sent: ```ts // CHANGED DELIBERATELY (CASL, row 14): this pinned a FRESH token // (not.toBe("u_old")), which killed the unsubscribe link in every email // already sent. The law wants that link to keep working (60 days at least). expect(yes.unsubscribeToken).toBe("u_old"); ``` The marker makes these searchable, and it makes them reviewable. A reviewer looking at a diff that edits a characterization file can see at once whether the change is deliberate and explained, or whether a test was edited until it went green. At the time of writing there are 101 of them across 49 files, and each one is a decision somebody can still read. #### Review findings are hypotheses Every release goes through a review once it is built: several reviewers each taking an area of the code, plus a few lenses that cut across all of it, such as security, migrations and the seams between features. The rule for what comes back is the same as for a feature. No finding is fixed until a test reproduces it, and the test must fail on the code as it stands. That rule throws a surprising amount away. In our first release review, 19 findings came back, and skeptics, whose job is to try to disprove each one, refuted 10 of them. Only the 9 that survived were fixed, each with a test that failed before the fix. Later reviews confirmed 20 of 27 findings and 15 of 24. A finding that cannot be turned into a failing test is either not a bug or not understood yet, and in neither case is a fix the next step. One of the findings the release 5 review confirmed is a good example of the shape. The team can drag one service of a visit to a new time on its own, so a visit's services are not always back to back. Moving the whole visit kept each service's own gap from the first, which is right. But the check before the move laid the services out back to back, so the person doing the later service was checked at a time it would never be saved at, and could be double-booked at the time it was. ```ts it("is refused when a later service's person is taken at the time it would be saved at", async () => { const s = await salon("vgapclient"); const day = dayKey(10); const [first, second] = await gappedVisit(s, day, "lee.gap1@example.com"); // Anna has somebody at 16:15. Moved to start at 12:00, the cut (4 hours // after the start) would be saved at 16:00-16:30, on top of them (a start // of its own, so the one-booking-per-person-and-start index cannot catch it). await insertBooking(tdb, s, { startAt: at(day, 975), staffId: s.annaId }); const [d] = await getRescheduleAvailabilityAction(s.slug, first.id, day, day); expect(d.slots.map((x) => x.startMin)).not.toContain(720); expect(await rescheduleBookingAction(s.slug, first.id, at(day, 720).toISOString())).toMatchObject({ ok: false }); expect((await reread(first.id)).startAt).toEqual(at(day, 600)); expect((await reread(second.id)).startAt).toEqual(at(day, 840)); expect(await annaOverlaps(s, at(day, 960), at(day, 990))).toHaveLength(1); }); ``` The colour is 90 minutes from 10:00 and the cut has been dragged to 14:00. Moved to 12:00, the old check asked whether the cut's person was free at 13:30, right after the colour, and she was. The move would then have saved the cut at 16:00, on top of somebody else. Against the unfixed code the first assertion fails, because 12:00 is offered, and that is the right red: an assertion about the behaviour, with today's value in it. The fix was to stop assuming: ```ts /** * Each service's start, in minutes from the visit's first: the gaps it is * booked with, which are not back to back once the team has moved or resized * one service on its own. A whole-visit move keeps them, so it is checked at them. */ function bookedGaps(live: Appointment[]): number[] { const base = live[0].startAt.getTime(); return live.map((r) => Math.round((r.startAt.getTime() - base) / 60_000)); } ``` Next to that test is a second refusal, for the team's own move, and a third test that a fix-first habit would probably not have produced: the visit still moves, with every service keeping its own gap, to a time each person is free at. A fix that refused every move of a gapped visit would have passed both refusals. #### What it costs It is slower. Writing tests for behaviour you are not changing feels like overhead on the day, and the characterization files are large: they set up whole businesses on an in-process Postgres and render real pages. The red check is one more run of every new and pinned file against the base. The release 5 review commit ended with the full suite at 13,194 tests passing on a freshly migrated scratch database, and it is not a small suite to keep honest. It also does not prove the tests are good. A red on the base says a test can tell the base from the feature. It does not say the test would notice the feature being subtly wrong, which is why we still break code on purpose after a fix to watch the right test fail. What it buys is a specific kind of confidence. When the visit work landed, the single-service paths it ran through had been written down beforehand, by tests that had already passed on the code before it, and they still passed after. That is the closest thing we have to a promise that the businesses who never turn visits on will not notice that visits exist. For a feature that touches the booking engine, that promise is most of the job. ### GST plus QST: tax lines that add up to the cent One tax rate per business was enough until Canada. Quebec charges GST and QST, British Columbia charges GST and PST, and some services carry only one of them. Here is how our tax engine works each tax out on its own, rounds so the cents always add up, freezes the result on the sale, and hands the same figures to the tax report, the CSV exports and QuickBooks. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/gst-plus-qst-tax-lines-that-add-up · markdown: https://bookatu.com/engineering/gst-plus-qst-tax-lines-that-add-up.md > **The short version** > > - A business has up to four tax lines (GST and QST in Quebec, GST and PST in British Columbia, one HST in Ontario), and each service or product says which of them apply: every line, none, or a named few. > - Each tax is worked out on its own, on each line, and rounded to the cent with half a cent going up. Never once on the combined rate. Ten cents in Quebec carries one cent of GST and one cent of QST, where 14.975% in one go would say one cent in all. > - Everything is whole cents and whole thousandths of a percent, worked in BigInt. Our earlier arithmetic ran in floating point and got the QST on $20.00 wrong by a cent. > - When prices include tax, the net is whatever is left after the taxes, so net plus taxes is always exactly the price. > - A sale freezes its tax when it is charged, tax by tax on its lines whenever there is more than one tax or a line not taxed at every one, and an invoice freezes each tax on its row. The tax report, the CSV exports and the daily QuickBooks journal entry all read tax by tax, so the GST figure and the QST figure each stand on their own. Bookatu started with one tax rate per business, which is all most of the world needs. A salon in New Zealand charges GST at 15%, and one number with one label covers it. Canada does not fit in one number. Quebec charges GST at 5% and QST at 9.975%, British Columbia charges GST and a 7% PST, Ontario folds both into a 13% HST, and some services are taxed at only part of that. #### Tax lines and treatments A business's tax position is a list of lines, called rates in the code, with at most four of them. Each line has a stable id, a label, a rate, the business's registration number for that tax, and a compound flag. A service or product carries a treatment that says which lines apply to it. ```ts /** One tax the business charges. */ export interface TaxRate { /** Stable id, named by a service or product taxed at only some lines. Kept * when the line is renamed. */ id: string; /** What the receipt, invoice and report call it: "GST", "QST", "HST". */ label: string; /** As a fraction (0.09975), to three decimals of a percent. */ rate: number; /** The business's registration number for this tax ("123456789 RT0001"). */ number: string; /** Charged on the amount plus the taxes listed above it. Never the first. */ compound: boolean; } /** How a service or product is taxed: null every line, [] none, ids only those. */ export type TaxTreatment = string[] | null; ``` Null means standard, which is what every service and product that existed before treatments reads as. An empty list means exempt. A list of ids means only those lines, which is how a haircut in British Columbia carries GST and not PST. The Tax page offers presets for each province and territory, filled in as charged in 2026, but a preset is only a starting point the business edits and saves. Its accountant confirms the rates, and it adds its own registration numbers. One rule in the treatment code is there purely to stop a settings change from quietly removing tax. If a service is set to "GST only" and the business later deletes its GST line, the list now names nothing that exists. We could read that as exempt. We read it as standard instead, because a tax silently dropped is far worse than one the owner has to correct. ```ts export function appliedRates(regime: TaxRegime, treatment: TaxTreatment | undefined): TaxRate[] { if (treatment == null) return regime.rates; if (treatment.length === 0) return []; const picked = regime.rates.filter((r) => treatment.includes(r.id)); return picked.length > 0 ? picked : regime.rates; } ``` Every existing business had at most one saved rate when this landed, and their figures could not move by a cent. A business that never saved a list of lines reads as one line with exactly its old rate, label and number. A unit test then runs the new engine against splitTax, the single-rate function every existing figure came from, at every three-decimal rate from 0% to 99%, on a spread of amounts from nothing to $12,345.67, with prices both including and excluding tax, and fails on the first cent of difference. #### Round each tax by itself The interesting decision was where to round. The tempting approach is to add the rates up (5% plus 9.975% is 14.975%), work out one tax figure, and then split it between GST and QST for display. That is wrong for Canada. GST and QST are two taxes, each reported on its own, and each one's figure has to be its own rate applied to the sale. Rounding once on the combined rate and splitting afterwards produces numbers that neither rate, applied honestly, would give. So the engine works each tax out separately, on each line, and rounds each one to the cent, half a cent up. The test file pins the case that made the point for us. ```ts it("$100.00 before tax: GST $5.00, QST $9.98 (9.975 rounds up), $114.98", () => { expect(one(10_000, qc)).toEqual({ netCents: 10_000, taxCents: 1_498, grossCents: 11_498, taxes: [ { rateId: "gst", label: "GST", rateMilli: 5_000, taxCents: 500 }, { rateId: "qst", label: "QST", rateMilli: 9_975, taxCents: 998 }, ], }); }); it("each tax is rounded by itself, not once on 14.975%: 10 cents carries 1 + 1 cents, not 1", () => { expect(taxesOf(10, qc)).toEqual([["gst", 1], ["qst", 1]]); expect(splitTax(10, 0.14975, false).taxCents).toBe(1); }); ``` Ten cents at 5% is half a cent, which rounds up to one. Ten cents at 9.975% is just under a cent, which also rounds to one. Ten cents at 14.975% is about one and a half cents, which rounds to one. Two correct taxes add up to two cents, and the combined shortcut says one. On a single sale nobody notices. Across a quarter of small add-ons it is a discrepancy an accountant has to explain. #### Whole numbers all the way down Our earlier tax arithmetic ran in floating point, and it had a bug that made us stop trusting floats for money. The rate 9.975%, worked out as 9.975 divided by 100, is held as 0.09974999999999999. Multiply $20.00 by that and you get 199.49999999999997 cents, which rounds to 199. The real QST on $20.00 is exactly 199.5 cents, which rounds to 200. The same thing happened at 7.25% and at 4.712%. Now every rate is turned into a whole number of thousandths of a percent before any arithmetic happens (9.975% becomes 9975, out of 100,000), amounts are whole cents, and the division with rounding is exact. ```ts /** A stored fractional rate (0.09975) as whole thousandths of a percent (9975). * The same number lib/tax.ts taxRateMilli gives. */ export function rateMilli(rate: number): number { if (!Number.isFinite(rate) || rate <= 0) return 0; return Math.round(rate * UNIT); } /** n ÷ d rounded half up, exactly, for whole numbers n ≥ 0 and d > 0. */ function divRoundHalfUp(n: bigint, d: bigint): bigint { return (2n * n + d) / (2n * d); } ``` The rounding function is the classic trick: doubling the numerator and adding the denominator before integer division gives half-up rounding with no fractions anywhere. It only works for non-negative numbers, so a refund is worked on its size and then given its sign back. Half a cent rounds away from zero in both directions, and a refund carries back exactly the tax its sale carried. #### Inside the price, the net takes the remainder Prices that include tax are the default for a new business, as is common for salons. Taking two taxes out of an inclusive price is where cents usually go missing. Each tax is the price times its rate divided by one plus every rate that applies. Round GST and QST separately and then also round the net separately, and the three numbers can disagree with the price by a cent. We do not round the net at all. The taxes are rounded, and the net is the price minus the taxes. ```ts function taxAmount(amountCents: number, rates: TaxRate[], inclusive: boolean): TaxedLine { const active = rates.filter((r) => rateMilli(r.rate) > 0); if (active.length === 0 || !Number.isFinite(amountCents)) { return { netCents: amountCents, taxCents: 0, grossCents: amountCents, taxes: [] }; } const size = BigInt(Math.round(Math.abs(amountCents))); const each: bigint[] = []; if (inclusive) { const { t, d } = factors(active); const whole = t.reduce((a, b) => a + b, d); for (const f of t) each.push(divRoundHalfUp(size * f, whole)); } else { let above = 0n; for (const r of active) { const base = r.compound ? size + above : size; const tax = divRoundHalfUp(base * BigInt(rateMilli(r.rate)), UNIT_N); each.push(tax); above += tax; } } const signed = (n: bigint) => (amountCents < 0 ? -Number(n) : Number(n)); const taxCents = signed(each.reduce((a, b) => a + b, 0n)); const taxes = active.map((r, i) => ({ rateId: r.id, label: r.label, rateMilli: rateMilli(r.rate), taxCents: signed(each[i]) })); if (inclusive) return { netCents: amountCents - taxCents, taxCents, grossCents: amountCents, taxes }; return { netCents: amountCents, taxCents, grossCents: amountCents + taxCents, taxes }; } ``` A test walks every inclusive price from zero to $200.00, cent by cent, in Quebec, and checks that net plus each tax is the price. Before tax the same holds the other way round: the gross is the amount plus the rounded taxes, so nothing is left over to reconcile. The compound flag exists for history rather than for today. Quebec charged QST on the price plus GST until 2013, and none of the current presets compound. The factors helper puts every rate over one common denominator, a power of 100,000, so a compound rate's share of an inclusive price is still a whole number and still exact. The first line can never compound, because there is nothing above it to compound on. #### How a sale stores its tax The engine returns each line taxed, the totals, and a per-tax total that is the sum of that tax across the lines. Totals are never rounded again, so the GST on a receipt is always the sum of the GST on its lines. At the point of sale, one function reads the business's position once and decides what is recorded. One tax inside the price with every line taxed at it is recorded the way the point of sale always did, on the sale's total. More than one tax, or any line that is exempt or partly taxed, freezes each line's taxes onto the receipt's own copy of the line. Prices that exclude tax with "Add tax at checkout" switched on freeze the taxes the same way, plus a flag that says they were added on top. If no tax was charged, nothing is recorded, and a receipt never shows a tax line nobody paid. ```ts export function saleTaxRows(lines: PosSaleLine[]): Array<{ rateId: string; label: string; rateMilli: number; taxCents: number }> { const rows = new Map(); for (const l of lines) { for (const t of l.taxes ?? []) { const row = rows.get(t.rateId) ?? { rateId: t.rateId, label: t.label, rateMilli: t.rateMilli, taxCents: 0 }; row.taxCents += t.taxCents; rows.set(t.rateId, row); } } return [...rows.values()].filter((r) => r.taxCents !== 0); } ``` The sale row itself still carries one tax figure, one label and one rate, because plenty of older screens read exactly those. With several lines, the figure is their sum, the label is the lines' names joined ("GST + QST"), and the rate is the combined rate. The point of sale's receipt reads the frozen line taxes instead, through the function above, and prints one row per tax. The client's visit receipt does the same and prints each tax's registration number, which a test pins for a Quebec business. Invoices freeze their tax on the row when they are raised, since the tax on an invoice is what was quoted and agreed. A business with one tax line keeps the old columns. With more than one, each tax goes into a tax_lines jsonb column. ```ts /** One tax on an invoice, frozen when it was raised (drizzle/0109). */ export interface InvoiceTaxLine { /** The tax line's id in the business's settings ("gst"). */ id: string; label: string; /** The rate, in thousandths of a percent (9975 = 9.975%). */ rateMilli: number; /** The registration number it was raised under. */ number: string; taxCents: number; } ``` When tax is added at checkout and the client pays through Stripe Checkout, each tax becomes a line item of its own, so the payment page and Stripe's receipt show GST and QST separately. The total tax goes into the session's metadata for the webhook to read back. #### Reading it back: the report and the exports The tax report covers everything a business sold in a period: visits completed, invoices paid, products sold at the point of sale, class places, and deposits kept on no-shows and late cancellations. A kept deposit is treated as a sale with the tax inside it, because Canada deems a forfeited deposit to include tax. This is one place where we got it wrong first. The report used to count appointments alone, so a salon that invoiced a company and sold shampoo filed a return missing both. That was not a display bug. The export goes to an accountant. Invoices raised with one combined tax before a business split its tax into lines needed a home. Each frozen tax is filed under one of today's lines by id, then by name, then under the only line if there is one, and otherwise under a separate "Other tax" column, rather than being guessed into GST or QST. ```ts const currentLine = (id: string | null, label: string | null): string => { if (id && totals.has(id)) return id; const byName = regime.rates.find((r) => r.label === (label ?? "")); if (byName) return byName.id; return regime.rates.length === 1 ? regime.rates[0].id : OTHER_TAX; }; ``` The exports split by tax only when there is more than one tax line. A single-rate business still gets exactly the columns it always had (Date, Reference, Description, Net, Tax, Gross), so nobody's import mapping breaks. A Quebec business gets a column per tax, headed "GST 5%" and "QST 9.975%", between Net and the total Tax. The Xero file names each line's tax type ("GST + QST on Income", or "Tax Exempt") and includes each line's tax amount, so Xero takes our figure instead of working out its own. The QuickBooks CSV marks each line taxable or not and gives a column per tax. #### QuickBooks: one journal entry a day, tax by tax For businesses that connect QuickBooks Online, we post each day of each location as one journal entry. The day's sales come from the same function as the Tax page, so the day's tax in QuickBooks is the day's tax in Bookatu. QuickBooks Canada handles sales tax through tax codes, and a code is a set of rates. So we map by the combination a line was taxed at rather than by individual tax. The combination key is the line ids in the business's own order. ```ts export function comboKey(rateIds: readonly string[], regime: TaxRegime): string { const known = regime.rates.filter((r) => rateIds.includes(r.id)).map((r) => r.id); const unknown = [...new Set(rateIds.filter((id) => !regime.rates.some((r) => r.id === id)))].sort(); const ids = [...known, ...unknown]; return ids.length ? ids.join("+") : EXEMPT_KEY; } ``` A Quebec business maps "gst+qst", plus "gst" if it has GST-only services, plus "exempt". Once a code is chosen, each of our lines is matched to the rate inside that code with the same percentage, and if two rates share a percentage, to the one whose name contains our label. If the code has no matching rate, the day is refused with a sentence the owner can act on, not posted with the tax in the wrong place. Suggested mappings are left empty when nothing fits. A company whose HST code still says 15% gets no suggestion for Nova Scotia's 14%. The entry is whole cents throughout and only becomes dollars in the payload. Each line's tax rides on the line, on the same side, so debits equal credits by construction, and a clearing line absorbs money and sales that fall on different days. #### What we would tell ourselves at the start - Decide where rounding happens before writing any arithmetic. Per tax, per line, half up, with the net taking the remainder, was the only rule we found that every downstream consumer could agree with. - Do not do money in floating point, even when the rate is "just a percentage". Converting to integer units at the boundary costs one function and removes a whole class of one-cent bugs. - Freeze what was quoted. An invoice's tax was agreed when it was raised, and working it out again at today's rate would change what a past quarter owed. - Keep the old shape for the businesses that do not need the new one. Single-rate exports have the same columns they had before, and a test proves the figures did not move. ### An append-only tip ledger A tip at checkout can belong to three people, and the split is sometimes wrong. We record each share as a row the database will not let anyone edit, split tips with largest-remainder arithmetic so the cents always add up, and change a split by writing an adjustment that moves money and sums to zero. Here is how it works, and how commission, payroll and QuickBooks read it. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/an-append-only-tip-ledger · markdown: https://bookatu.com/engineering/an-append-only-tip-ledger.md > **The short version** > > - A tip is stored beside the sale's total, never inside it, so the total, the tax and every report that reads them are exactly what they would be without it. > - A tip is split by the business's rule (by share of the services, equally, or by share of the whole sale) or by amounts entered at the point of sale. The split is exact integer arithmetic with largest-remainder rounding, so the shares always add up to the tip. > - Each share is one row in tip_allocations. A database trigger refuses every update and delete, except the one a foreign key makes when a person or login is deleted. > - Changing a split never edits a row. It writes an adjustment: new rows that share an id, move money between people, add up to zero, carry a reason, and are dated when they are made. > - Commission reads tips as their own lines worth no commission, payroll gives them their own column, and QuickBooks credits them to the account the business picks for tips owed to the team. Before tips were part of Bookatu, a client who wanted to tip their stylist did it in cash or on the card terminal, and nothing in the books said a tip had been taken, how much, or who it went to. A business split its tips from memory, and nobody could check the split afterwards. When we added tips at checkout, the money part was the easy bit. The harder part was the record: who got what, under which rule, who changed it later and why, and whether last month's payroll still adds up after someone fixes a mistake today. This post walks through the design we ended up with. #### Where the tip lives The first decision was that a tip is not part of the sale. It sits in its own column on the sale row, next to the total. ```ts /** The tip taken with the sale (drizzle/0106), beside `totalCents` and * never inside it: the client paid total + tip. Not taxed. Who got it is * in tip_allocations. 0 when there was none. */ tipCents: integer("tip_cents").notNull().default(0), ``` Putting the tip inside the total would have been one less column, and it would have changed the meaning of a number that the receipt, the booking's payment on the ledger, the tax report and the commission engine all read. Keeping it beside the total means none of them needed to learn anything. One integration test checks out two identical bookings, one with a $7.65 tip and one without, at a business that adds 13% HST at checkout. The two sale rows are identical apart from tip_cents, tax included. Tips are off until the business switches on "Accept tips at checkout", because a tip changes what a client pays. The prompt offers preset percentages, 10%, 15% and 20% by default, stored in hundredths of a percent, at most four of them and none above 50%. A preset is a percentage of the booking's price after its discount and before any tax added at the point of sale, rounded to the cent with half a cent going up. A tip above $10,000 is refused. As the code puts it, past that it is a slip of the finger. #### Splitting a tip to the cent A sale can involve several people. One person did the colour, another did the blow-dry, and a third sold the client a bottle of shampoo. The business chooses how a tip is split when nobody types the amounts in: - service_share, the default: by each person's share of the services, so a booking one person did sends them the whole tip; - equal: equally between everyone on the sale; - line_share: by each person's share of the whole sale, products included. Each rule turns the sale's lines into a weight per person. Under service_share, product lines are skipped. If every weight comes out at zero, for example on a sale of free lines, everyone on it gets an equal weight instead. The weights then go through one function. ```ts export function splitTip(tipCents: number, weights: Array<{ staffId: string; weight: number }>): TipShare[] { const tip = Math.round(tipCents); const total = weights.reduce((s, w) => s + Math.max(0, Math.round(w.weight)), 0); if (tip <= 0 || total <= 0) return []; const T = BigInt(total); const parts = weights.map((w, i) => { const exact = BigInt(tip) * BigInt(Math.max(0, Math.round(w.weight))); return { i, staffId: w.staffId, weight: w.weight, cents: Number(exact / T), rem: exact % T }; }); let left = tip - parts.reduce((s, p) => s + p.cents, 0); const byLoss = [...parts].sort((a, b) => (a.rem !== b.rem ? (a.rem > b.rem ? -1 : 1) : b.weight - a.weight || a.i - b.i)); for (const p of byLoss) { if (left <= 0) break; p.cents += 1; left -= 1; } return parts.filter((p) => p.cents > 0).map((p) => ({ staffId: p.staffId, amountCents: p.cents })); } ``` This is the largest remainder method. Each share is worked out exactly, as whole cents times whole weights, and rounded down. Fewer cents are left over than there are people, and they go one at a time to the shares that lost the most in rounding. Ties go to the larger share, and then to whoever comes first on the sale. A $7.65 tip split equally between two people is $3.83 and $3.82. A $10.00 tip by share of the sale, where the exact shares are $6.7105 and $3.2895, rounds down to $6.71 and $3.28, and the spare cent goes to the second share because it lost more. A seeded property test runs two thousand random splits of up to five people and checks two things on each one: the shares add up to the tip exactly, and no share is a cent or more away from its exact value. Amounts typed at the point of sale for one sale skip the rule entirely. They must be whole cents, nobody gets a negative amount, every person must be on the business's team, and the amounts must add up to the tip exactly. Anything else is refused rather than rounded into shape. #### Taken with the sale, or not at all The checkout reads and checks the posted tip before it writes anything. Amounts typed at the point of sale are checked inside the checkout's transaction, against the team and the people on the booking. A rule-based split can only be worked out once the sale's lines are known, so it happens inside the transaction too. If the rule finds nobody to give the tip to, such as a booking with no staff member on it, the checkout throws and the whole sale rolls back. The point of sale then asks who the tip is for. ```ts if (tip > 0 && !shares) { shares = allocateTip(tip, tipRule, [ ...draft.lines.flatMap((l) => lineShares(l).map((s) => ({ kind: l.kind, staffId: s.staffId, totalCents: s.totalCents }))), ...sold.soldLines.map((l) => ({ kind: "product" as const, staffId: seller?.id ?? null, totalCents: l.totalCents })), ]); if (shares.length === 0) throw new TipRefused(); } // ... // Who got the tip, with the sale: the record (lib/tip-allocations.ts). if (tip > 0 && shares) { await writeTipAllocations(tx, { orgId: org.id, saleId: sale.id, shares, rule: entered ? "manual" : tipRule, by: input.createdBy ?? null }); } ``` Writing the allocation rows in the same transaction as the sale means there is never a sale with a tip on it and no record of who got the tip. #### A table that refuses to be edited tip_allocations has one row per person per tip. Each row stores the person and their name at the time, the amount, the rule, the login that took it and that login's name at the time, and a timestamp. Names are copied in on purpose. If someone is renamed or removed later, the record still says who it was. The value rules live in the migration, because the raw SQL is the authority on the table's shape. ```sql -- A tip given is a positive amount; an adjustment moves money either way, -- and a row of nothing says nothing. constraint tip_allocations_amount check (amount_cents <> 0 and (rule = 'adjustment' or amount_cents > 0)), -- An adjustment's rows share its id and say why; a split at checkout has neither. constraint tip_allocations_adjustment check ( ((rule = 'adjustment') = (adjustment_id is not null)) and (rule <> 'adjustment' or length(btrim(coalesce(reason, ''))) > 0) ) ``` Append-only is enforced by a trigger, not by convention. The obvious trigger, one that raises an exception on any update or delete, would have broken two things we needed to keep working. A row's staff_id and allocated_by are foreign keys with ON DELETE SET NULL, and Postgres carries out that action as an UPDATE on this table. A row's sale and business are foreign keys with ON DELETE CASCADE, which is a DELETE. A blanket refusal would have stopped anyone from deleting a staff member or a login who had ever received or taken a tip, and blocked a business's data from ever being removed. The answer was pg_trigger_depth(). A foreign key's own action runs inside the system's referential trigger, so our trigger fires at depth 2 or more. A statement sent to the table directly fires at depth 1. ```sql create or replace function bookatu.tip_allocations_append_only() returns trigger language plpgsql as $$ begin if tg_op = 'DELETE' then if pg_trigger_depth() < 2 then raise exception 'tip allocations are a record: they are never deleted (record an adjustment instead)'; end if; return old; end if; -- ON DELETE SET NULL letting go of a deleted person or login; nothing else. if pg_trigger_depth() >= 2 and (new.staff_id is null or new.staff_id is not distinct from old.staff_id) and (new.allocated_by is null or new.allocated_by is not distinct from old.allocated_by) and (new.id, new.org_id, new.sale_id, new.staff_name, new.amount_cents, new.rule, new.adjustment_id, new.reason, new.allocated_by_name, new.created_at) is not distinct from (old.id, old.org_id, old.sale_id, old.staff_name, old.amount_cents, old.rule, old.adjustment_id, old.reason, old.allocated_by_name, old.created_at) then return new; end if; raise exception 'tip allocations are a record: they are never changed (record an adjustment instead)'; end $$; ``` Even at depth 2, the only update allowed is one that clears a link and leaves every other column exactly as it was. The link goes and the name stays. An integration test takes a real tip at checkout and then tries three raw statements against the table: changing the amount, moving the row to another person, and deleting it. All three come back with the database's own refusal, and the original row is still there. #### Adjustments are new rows Tip splits do get changed. The point of sale said one person did the blow-dry and it was actually someone else. The owner opens the sale's tip page, types the amounts it should have been, gives a reason, and saves. The code that handles this works out the difference and writes only that. ```ts const next = new Map(check.shares.map((s) => [s.staffId, s.amountCents])); const moves: TipShare[] = []; for (const staffId of new Set([...held.keys(), ...next.keys()])) { const delta = (next.get(staffId) ?? 0) - (held.get(staffId) ?? 0); if (delta !== 0) moves.push({ staffId, amountCents: delta }); } if (moves.length === 0) return { ok: false as const, error: "unchanged" as const }; const adjustmentId = `tadj_${nanoid(16)}`; await writeTipAllocations(tx, { orgId: org.id, saleId: sale.id, shares: moves, rule: "adjustment", by: input.by, adjustmentId, reason }); ``` Here held is each person's current share, the sum of all their rows so far. The new amounts must be money, must go only to people who are or have been on the business's team (a correction can be for someone who has since left), and must add up to the tip. A reason is required, and something has to actually change. The sale row is locked with SELECT ... FOR UPDATE while this runs, so two people adjusting the same tip at once are queued instead of both applying their change to the same starting split. The test for it is the best description of the result. In the test, Sam got the whole $7.65 at checkout. An admin then moves $2.65 to Anna with the reason "Anna did the blow-dry". The table ends up with three rows: Sam's original 765 cents under service_share, untouched, then Anna plus 265 and Sam minus 265, both marked adjustment, sharing one adjustment id, with the reason and the admin's login on them. The sale's tip_cents is still 765. Only who has it changed. Every row is dated when it was written, and a person's tips for a period are the sum of their rows dated in that period. So an adjustment counts in the period when it was made, not the period of the original sale. If last month's payroll has already gone out, its figures stay as they were, and the correction appears in this month as a plus for one person and a minus for the other. Staff earnings already handles refunds this way, and we wanted the two to behave the same. #### How commission and payroll read it The commission engine builds a list of earning lines from visits, sale lines, refunds and voids. Tips join that list as lines of their own, with a sales figure of zero, a commission of zero, and the amount in a separate tip field. The totals function handles them before anything else. ```ts function addLine(t: EarningsTotals, l: EarningLine): void { if (l.source === "tip") { t.tipsCents += l.tipCents; return; } ``` A tip line carries no sales and a commission fixed at zero, and the totals function returns before it reaches the commission sums, so no commission rule, tiered or flat, can pay commission on a tip. A test checks that a stylist's 40% commission on a $51.00 visit is the same whatever the client tipped. An adjustment row comes through as a line labelled "Tip adjusted", negative for the person who gave money up, so a period that contains only an adjustment still shows who gained and who lost. The payroll export works out each employee's total as commission plus goal bonus plus tips, minus any booth rent owed. Tips get their own column in the generic CSV, their own Tips column in the Wagepoint file, and their own earnings code (the business's own, typed into the download form) in the ADP paydata file. A payroll provider can then treat tips differently from commission. Sales tax never touches a tip, because the tip is outside the total that tax is worked on. When a day is posted to QuickBooks, the tips taken at the point of sale are part of the money taken and are credited to a "Tips for the team" account with no tax code. The account picker describes it as a liability, because the business owes that money to its staff. > A tip is never taxed, never commissioned, and never part of the sale's total. #### The audit trail The table is itself most of the audit trail: who got each share, under which rule, who recorded it, and when. A sale's tip page shows the split made at checkout and then each adjustment, oldest first, with its reason and who made it. A CSV download gives every row in a date range with its date, time, receipt, booking, person, amount, rule, whether it was a checkout or an adjustment, reason, who recorded it, and how the sale was paid. On top of that, the business's activity log gets two events. Taking a tip records "Tip taken" with the amount and the split made at checkout. An adjustment records "Tip split changed" with each person's plus or minus, read back from that adjustment's own rows. The free-text reason stays on the tip record and is deliberately not copied into the activity log, because a reason can say anything, about anyone. Changing a split requires an owner or admin role with both the Manage and the revenue permission, under the business's own role settings. #### What we would do again - Keep new money beside existing totals, not inside them. Every reader of the old number stayed correct without being touched. - Make the database enforce append-only, and remember that foreign key actions are writes too. pg_trigger_depth() let us refuse application writes while still allowing SET NULL and CASCADE. - Model a correction as rows that add up to zero. The tip stays what was taken, the history stays readable, and nothing already paid gets restated. ### Handing over a slot that is still booked Quick swap lets a client who would pay a late-cancel fee hand their time to someone on the waitlist instead. The time is never free, not even for a moment. Here is the one transaction that releases one booking and writes the other, how two claimers racing give one winner, and how a cancellation and a claim at the same moment give one outcome. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/handing-over-a-slot-that-is-still-booked · markdown: https://bookatu.com/engineering/handing-over-a-slot-that-is-still-booked.md > **The short version** > > - Quick swap lets a client inside the late-cancel window ask to swap out instead of cancelling. Bookatu offers that exact time to matching waitlist clients through a signed one-tap link, while the asking client still holds it. > - A claim is one transaction. Under the same advisory locks every booking takes, it reads the booking again FOR UPDATE, releases it as "swapped", writes the claimer's booking for the same times, people and rooms, marks the ask claimed and fulfils the waitlist entry. The time is never free to anybody else. > - Two claimers racing give one winner. The loser's transaction finds the ask already gone. Behind that sits the unique index that allows one live booking per person and start time, and a violation of it reads as "gone" too. > - Each link carries a fingerprint of the booking as it was offered. If the booking moved, changed hands or lost a service since, the claim fails politely and writes nothing. > - cancelAppointment closes an open ask before any money moves, and refuses to write over a row a claim has released. A cancellation and a claim at the same moment give one outcome, never both. > - The hourly cron closes expired asks with a conditional update, so only the run that moved an ask tells anybody about it. A late cancellation costs both sides. The business keeps the deposit or queues a late-cancel fee, and the client pays for a time they cannot use. Very often someone on the waitlist would have taken that exact time. Quick swap connects the two: the client asks to swap out, the time is offered to the waitlist, and if somebody takes it the client is released with no fee and their deposit back (or kept as credit, by the business's setting). If nobody takes it by the business's cutoff, the client is still booked and is told so. Most of the work was not the offer or the emails. It was making sure the time changes hands without ever being free in between. #### Why not cancel first and offer second We already had a path for freed time. When a booking is cancelled, cancelAppointment offers the freed slot to the best matching waitlist clients. The tempting build was to reuse it: cancel the booking without a fee, then let that path offer it. That gets the order wrong. Between the cancel and anyone claiming, the time is free. Anyone booking online can take it, which is fine for the business but means the client was let off a fee in exchange for nothing. Worse, if nobody claims, the client has already lost the booking they were willing to keep. So the rule we wrote at the top of lib/quick-swap.ts is that the old booking stops holding the time only inside the transaction that makes the new one hold it. > The asking client keeps the time until the moment somebody else has it, and not one statement earlier. The state lives on the booking itself: a handful of nullable swap_* columns added by migration 0170, all NULL for a business that never switches Quick swap on. For a visit of several services the ask is kept on the first service, which speaks for the visit. Asking is a conditional update, so two taps make one ask: ```ts const asked = await db .update(appointments) .set({ swapStatus: "requested", swapRequestedAt: now, swapStartAt: lead.startAt, swapCutoffAt: e.cutoffAt, // ... }) .where( and( eq(appointments.orgId, orgId), eq(appointments.id, lead.id), eq(appointments.status, "confirmed"), eq(appointments.startAt, lead.startAt), isNull(appointments.checkedInAt), // Not while an ask on the booking as it is stands (a second tap). sql`(${appointments.swapStatus} is null or ${appointments.swapStatus} <> 'requested' or ${appointments.swapStartAt} is distinct from ${appointments.startAt})`, ), ) .returning({ id: appointments.id }); ``` swap_start_at records the start the ask was made for. That one column lets every later step tell an ask that still stands from an ask on a booking that has since moved. #### One transaction claimSwap does its cheap checks first, outside any transaction: the link verifies, the waiting client's entry is still open, the booking still looks as offered, the business still allows it. None of that writes anything. Then it opens one transaction and starts by taking the same locks every booking takes, in the same order: ```ts // The same locks every booking takes on its resources and people, in the // same order (resources, then people), so a booking being made for any // of them at this moment waits for this one, then sees it. // ... await lockResources(tx, orgId, [...booking.lines.map((l) => l.resourceId), ...otherRows.map((o) => o.resourceId)]); await lockPeople( tx, orgId, [...booking.lines.map((l) => l.staffId), ...crewRows.map((c) => c.staffId)].filter((x): x is string => Boolean(x)), ); // The booking again, held: it must still be exactly what was offered. const [first] = await tx .select() .from(appointments) .where(and(eq(appointments.orgId, orgId), eq(appointments.id, booking.lead.id))) .for("update"); if (!first) throw new SwapGoneError(); // ... if (!stillAsOffered(fresh, r.ctx.token, now)) throw new SwapGoneError(); ``` Both lock helpers are transaction-scoped Postgres advisory locks, one per resource and one per person, taken in sorted order so two transactions can never wait on each other in a circle. The booking flow takes the same keys, which is what makes "at this moment" safe: an online booking for the same stylist at the same time waits for the claim, then sees the claimer's booking. Holding the locks, the claim reads the booking again with FOR UPDATE and checks it once more. Everything read before the transaction was only a hint. Then come the writes: ```ts // Release the asking client's booking, every service of it, as swapped. // Only while each one is still confirmed: anything else is a change. const freed = await tx .update(appointments) .set({ status: "cancelled", cancelledAt: now, cancelReason: "swapped", updatedAt: now }) .where(and(eq(appointments.orgId, orgId), inArray(appointments.id, fresh.lines.map((l) => l.id)), eq(appointments.status, "confirmed"))) .returning(); if (freed.length !== fresh.lines.length) throw new SwapGoneError(); // The claimer's booking, in the same times, with the same people and rooms. const inserted = await tx .insert(appointments) .values( fresh.lines.map((l, k) => ({ orgId, customerId, staffId: l.staffId, resourceId: l.resourceId, // ... startAt: l.startAt, endAt: l.endAt, // ... })), ) .returning(); // ... // The ask is claimed, by this booking. await tx .update(appointments) .set({ swapStatus: "claimed", swapClosedAt: now, swapClaimedAppointmentId: byStart[0].id }) .where(and(eq(appointments.orgId, orgId), eq(appointments.id, fresh.lead.id))); ``` The release only matches rows that are still confirmed, and the count has to equal the number of services. If one of them changed under us, SwapGoneError rolls the whole thing back. The extra rooms and people a service holds are copied onto the new rows inside the same transaction, and the waiting client's entry is marked fulfilled with a conditional update that also throws if it matched nothing. Everything that talks to the outside world happens after the commit: the deposit refund or credit, removing the old booking from the team's Google Calendar, webhooks, the audit rows and the emails. Each one is wrapped so that a failure is logged and never undoes the swap. A refund Stripe could not make is recorded as needing handling rather than quietly marked done. #### Two claimers, one winner Up to five waiting clients get a link for the same time, so two of them tapping within the same second is a case we had to plan for. Both pass the checks outside the transaction, because at that point nothing has changed. Inside, the second one waits on the first one's locks. When it gets them, it reads the booking FOR UPDATE and finds it cancelled with its ask claimed. The ask no longer stands: ```ts function askStands(lead: Appointment): boolean { return ( lead.swapStatus === "requested" && lead.status === "confirmed" && lead.checkedInAt == null && lead.swapStartAt != null && lead.swapStartAt.getTime() === lead.startAt.getTime() && lead.swapCutoffAt != null ); } ``` If some path ever got past that check, the schema has one more answer. Appointments carry a partial unique index that allows one live booking per staff member and start time, and the same for a resource: ```ts // One live appointment per staff member + start time (anti double-booking). uniqueIndex("apt_staff_slot_uniq") .on(t.staffId, t.startAt) .where(sql`status in ('pending','confirmed') and staff_id is not null`), ``` The claim treats a violation of it exactly like a lost race: ```ts } catch (e) { if (e instanceof SwapGoneError || isUniqueViolation(e)) return { status: "gone" }; log.error("quick_swap.claim_failed", e, { orgId, appointmentId: booking.lead.id }); return { status: "gone" }; } ``` An unexpected error also answers "gone", after logging it. We chose that on purpose. The transaction has rolled back, so nothing was written, and a waiting client who tapped a link does not need a stack trace. The integration test races two real claims with Promise.all against the test database: ```ts const results = await Promise.all([claimSwap(s.b.orgId, tokenFor(a.id)), claimSwap(s.b.orgId, tokenFor(c.id))]); expect(results.map((r) => r.status).sort()).toEqual(["gone", "swapped"]); expect(await liveAt(s.b.orgId, TOMORROW_9)).toHaveLength(1); const statuses = [(await entryRow(tdb, a.id)).status, (await entryRow(tdb, c.id)).status].sort(); expect(statuses).toEqual(["fulfilled", "offered"]); ``` The loser stays on the waitlist as "offered", so the next opening can still reach them. A sibling test races a claim against an ordinary online booking for the same stylist and start, and checks that the claim wins, the online booking is refused, and exactly one live booking exists afterwards. #### A claim that fails politely A link is offered for a booking as it was at that moment. If the team moves it an hour later, the link must not claim the new time. So every link carries a fingerprint of the booking's services: ```ts export function swapFingerprint(lines: FingerprintLine[]): string { const ordered = [...lines].sort((a, b) => a.startAt.getTime() - b.startAt.getTime() || a.id.localeCompare(b.id)); const text = ordered .map((l) => [l.id, l.startAt.toISOString(), l.endAt.toISOString(), l.staffId ?? "", l.resourceId ?? ""].join("|")) .join(";"); return crypto.createHash("sha256").update(text).digest("base64url").slice(0, 22); } ``` stillAsOffered compares it, together with the start and the ask, both before the transaction and again on the locked rows inside it. A test suite pins five ways the booking can change after the offer: moved to another time, given to someone else, cancelled by the client the normal way, checked in, and the ask withdrawn. In each one the claim answers "gone", the original booking is untouched, the waiting client's entry is still open, no new booking exists and no release email went out. The link's page is a GET that only reads. Claiming is a separate POST. Mail scanners and chat apps that fetch links to draw a preview can open the page as often as they like and never take the time. #### When a cancellation and a claim cross This was the case that needed the most care. The asking client can still cancel the normal way at any time, fee and all. cancelAppointment reads the booking, decides what happens to the deposit and the fee, and then writes. If a claim commits between that read and that write, a cancel that knew nothing about swaps would forfeit a deposit the swap had just refunded, count a late cancellation against the client, queue a fee, and write over the row that now records the swap. So cancelAppointment's one Quick swap step comes before any of that. It only runs for a booking with an open ask: ```ts if (apt.swapStatus === "requested") { const closed = await db .update(appointments) .set({ swapStatus: "expired", swapClosedAt: new Date() }) .where( and( eq(appointments.orgId, orgId), eq(appointments.id, appointmentId), eq(appointments.swapStatus, "requested"), ), ) .returning({ id: appointments.id }); if (closed.length) { // ... } else { const released = await bookingReleasedSince(orgId, appointmentId); if (released) return released; } } ``` Whichever update moves the ask off "requested" first decides the outcome. If the cancel closes it, a claim arriving later finds the ask gone and the cancellation is exactly today's, fee and all. If the claim got there first, the cancel finds nothing to close, sees the booking already released, and returns the answer a repeat cancel gets, doing nothing more. One more case was left. A visit's later services carry no ask of their own, so the step above never runs for them. The final cancel write therefore carries a narrow guard: ```ts .where( and( eq(appointments.id, appointmentId), // Never over a booking a Quick swap claim released after it was read // above (a later service of a visit carries no ask of its own to // close): that time is the claimer's now, and the swap settled it. // Narrowed to that on purpose: every other write lands as it always has. sql`not (${appointments.status} = 'cancelled' and ${appointments.cancelReason} is not distinct from 'swapped')`, ), ) ``` Testing a race between a read and a write needs a seam. The test file wraps loadOrgSettings so that the next call first runs a hook, and cancelAppointment calls it after reading the booking and before writing anything. The hook runs a full claim there. The tests then check that the claim stood, that nothing was forfeited, queued or counted, that the deposit was settled once (a card deposit kept as credit is not also refunded to the card), and that the claimer holds the time. #### The hourly sweep An ask with no taker lapses at its cutoff. The hourly reminders cron calls expireSwaps, which reads the open asks (a partial index on swap_cutoff_at covers exactly those rows) and moves each one with a conditional update: ```ts const [moved] = await db .update(appointments) .set({ swapStatus: "expired", swapClosedAt: now }) .where( and( eq(appointments.orgId, apt.orgId), eq(appointments.id, apt.id), eq(appointments.swapStatus, "requested"), ...(stands ? [lte(appointments.swapCutoffAt, now)] : []), ), ) .returning({ id: appointments.id }); if (!moved) continue; ``` Only the run that moved an ask sends anything, so two overlapping runs, or a retry, never tell a client twice that they are still booked. The test runs the sweep a minute before the cutoff (nothing happens), five minutes after (one ask expires, one email), and then again (nothing). An ask whose booking changed meanwhile is closed too, quietly, because telling someone "you are still booked" when they may not be is worse than saying nothing. The sweep has its own try/catch in the cron, and a test checks that a swap failure never costs the reminders that run before it. The same hourly pass also offers asks that are still open to waiting clients who joined the list since. The waitlist already records each opening it offered to each client, so nobody hears about the same time twice. #### The link itself The link is an HMAC-signed token with its own signing purpose, separate from the Magic Fill claim link it was modelled on. A Magic Fill link books a free time. A swap link takes over a time somebody still holds. The two must never stand in for each other, and a test checks that a Magic Fill link is refused here. The payload names the business, the booking, the waiting client's entry, the start and the fingerprint, and it expires at the ask's cutoff. The claim checks that the business in the link is the business of the page. Single use is enforced where it matters, inside the claim. The ask can leave "requested" once, and the waiting client's entry can be fulfilled once. A second tap on the same link is told the time has gone. #### What we take from it - When something has to change hands, do the release and the take in one transaction. A gap between them, however short, is a window someone else can use. - Take the same locks as the rest of the system, in the same order. Locking was the easy part. Agreeing with every other writer on what to lock was the work. - Treat everything read before the transaction as a hint and check it again on locked rows. The fingerprint made "is this still what we offered?" one comparison. - When two operations can race, pick one column whose change decides the winner. Here it is swap_status leaving "requested", and both the claim and the cancel have to move it. - Build a seam to test the race between a read and a write. Without one, the most dangerous case in the feature would only ever have been tested by luck. ### Passkeys without telling anyone who has an account Business logins can now sign in with a passkey. The WebAuthn library does the cryptography, and most of our work went into everything around it: where the relying party comes from, challenges that live on the server and are used once, a sign-in prompt that never asks who you are, sign counters, and a fresh check before a session can add a passkey of its own. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/passkeys-without-telling-anyone-who-has-an-account · markdown: https://bookatu.com/engineering/passkeys-without-telling-anyone-who-has-an-account.md > **The short version** > > - Passkey sign-in for business logins uses SimpleWebAuthn. The library verifies the signatures. We own the relying party, the challenges, the counters and every rule about who may add or remove a passkey. > - The relying party comes from the configured public URL, never from the request's Host header. Its origin, its rpID and user verification are checked by our own code after the library has checked them. > - Every challenge is stored on the server for five minutes and deleted in the same statement that checks it. A sign-in challenge is bound to the hash of a random value in the asking browser's httpOnly cookie. > - The sign-in prompt asks for any passkey for this site, with an empty allow list, so it never takes an email address. A refused answer reads the same whether the passkey is known or not. > - A sign counter that stands still or goes backwards is refused, and the update that records a new counter only lands on the counter it was checked against. > - Adding a passkey needs a fresh password or two-step code (or, with neither, a sign-in in the last ten minutes), and the last passkey cannot be removed when it is a login's only way in. A passkey is a key pair an authenticator makes for one site: Face ID or Touch ID, Windows Hello, an Android phone, a password manager or a security key. The private half never leaves the device. We keep the public half and check each sign-in's signature against it. Because we require user verification every time, a passkey sign-in is something you have and something you are or know in one step, and a business that requires two-step login accepts it. We used SimpleWebAuthn rather than writing CBOR and COSE parsing ourselves. That still left plenty for us to decide, and most of what can go wrong with passkeys lives in those decisions rather than in the cryptography. #### The relying party is configuration WebAuthn ties every credential to a relying party id, a host name, and checks each answer against an expected origin. The easy way to get both is to read them off the incoming request. That would let whoever controls the Host header choose them, so we never do. lib/passkeys.ts reads the configured public URL: ```ts export function relyingParty(): RelyingParty | null { return relyingPartyFor(process.env.NEXT_PUBLIC_APP_URL, process.env.NODE_ENV); } ``` relyingPartyFor is pure and refuses anything a browser would never make a passkey on. An IP address is never a valid relying party id, and WebAuthn needs https, or plain http on localhost: ```ts const host = url.hostname.toLowerCase(); if (!host || /^[\d.]+$/.test(host) || host.includes(":") || host.startsWith("[")) return null; const localhost = host === "localhost" || host.endsWith(".localhost"); if (url.protocol !== "https:" && !(url.protocol === "http:" && localhost)) return null; return { rpID: host, origin: url.origin.toLowerCase() }; ``` null means passkeys are off on that address, and every door says so plainly. The integration test sends requests that claim to come from another host and checks that the options still name the configured one. #### Checked twice, on purpose We pass expectedOrigin, expectedRPID and requireUserVerification: true to the library. Then, after it says yes, we check the same three things again on what it returns: ```ts const info = verified?.verified ? verified.registrationInfo : null; if ( !info || info.userVerified !== true || info.origin !== rp.origin || (info.rpID !== undefined && info.rpID !== rp.rpID) || !info.credential?.id || !(info.credential.publicKey instanceof Uint8Array) ) { return { ok: false, error: NOT_ADDED }; } ``` This is not distrust of the library. It means a default changing in a future major version, or a call site that forgets one option, cannot quietly loosen the rule. The sign-in path does the same and also checks that the credential id the library verified is the one we looked up. The tests replace the library with a mock that says "verified" while reporting a wrong origin, a wrong rpID or no user verification, and expect a refusal for each. #### One-time challenges on the server A WebAuthn answer signs a random challenge the server issued. If the server does not remember which challenges it issued, or lets one be used twice, a captured answer can be replayed. Migration 0171 adds a webauthn_challenges table with a constraint that every row is bound to something: ```sql constraint webauthn_challenges_bound check ( (purpose = 'register' and user_id is not null) or (purpose = 'sign_in' and attempt_hash is not null) ) ``` A challenge for adding a passkey names the signed-in login. A sign-in challenge cannot name a login, because nobody is known yet, so it names the browser. Using a challenge is a single DELETE ... RETURNING, so checking it and spending it are one statement: ```ts const rows = await db .delete(webauthnChallenges) .where( and( eq(webauthnChallenges.challenge, challenge), eq(webauthnChallenges.purpose, purpose), "userId" in bound ? eq(webauthnChallenges.userId, bound.userId) : eq(webauthnChallenges.attemptHash, bound.attemptHash), gt(webauthnChallenges.expiresAt, new Date(nowMs())), ), ) .returning({ id: webauthnChallenges.id }); return rows.length === 1; ``` Two answers racing with the same challenge cannot both get a row back. The purpose is part of the match, so a challenge issued for adding a passkey can never finish a sign-in. Expired rows are cleared each time a new challenge is stored, so the table only ever holds the last few minutes. #### Binding a sign-in to the browser that asked For a sign-in, the browser that asks for a challenge gets an httpOnly cookie holding 32 random bytes. The server never stores that value, only a hash of it: ```ts export function attemptHashOf(token: string): string { return crypto.createHash("sha256").update(`bookatu:passkey-attempt:v1:${token}`).digest("hex"); } ``` The cookie lives as long as a challenge does, five minutes. A challenge copied out of one browser and answered from another finds no matching row, because the other browser's cookie hashes to something else, or it has no cookie at all. The test covers both, plus the opposite case that matters for usability: autofill and the button can each open a prompt in the same browser, and both still work. The challenge endpoint is a route handler, POST /api/passkey/options, and not a server action. Setting a cookie inside a server action makes Next.js re-render the page. The sign-in page asks for a challenge as soon as it opens, so as an action it reloaded the page under every visitor while they typed. A test now pins that the challenge comes from the route. The same lesson came up again in auto sign-out, in the same release. #### A prompt that never asks who you are A sign-in form that takes an email address and then says "this address has no passkey" tells anyone who asks which addresses have accounts. So the passkey prompt takes no address at all: ```ts const options = await generateAuthenticationOptions({ rpID: rp.rpID, userVerification: "required", timeout: PASSKEY_PROMPT_TIMEOUT_MS, }); await storeChallenge(options.challenge, "sign_in", { attemptHash }); ``` With no allowCredentials list, the browser offers whichever passkeys it holds for this site. That needs discoverable credentials, so registration asks for residentKey: "preferred", and it sets the user handle to our own user id, never the email. When an answer carries a user handle, it has to name the login that holds the passkey, or the sign-in is refused. The other half of not telling is the refusal. An unknown credential and a bad signature return the same reason to the browser. The difference only shows in our own audit trail: a failure on a known passkey is recorded on that login, like a wrong password, and an unknown one leaves nothing anywhere. Tries are limited per IP, with the same counter the password form uses, and per passkey, under a hash of its credential id. #### Counters against copied authenticators An authenticator can report a sign counter that goes up at each use. If it stands still or goes backwards, the key may have been cloned. Most synced passkeys always report zero, so zero and zero has to be allowed: ```ts export function counterAccepted(stored: number, next: number): boolean { if (!Number.isInteger(next) || next < 0 || !Number.isInteger(stored) || stored < 0) return false; if (stored === 0 && next === 0) return true; return next > stored; } ``` Checking is not enough on its own if two sign-ins with the same counter arrive together. The update that records the new counter carries the old one in its WHERE clause, so only one of them lands: ```ts const updated = await db .update(userPasskeys) .set({ counter: info.newCounter, lastUsedAt: new Date(nowMs()), backedUp: Boolean(info.credentialBackedUp) }) .where(and(eq(userPasskeys.id, passkey.id), eq(userPasskeys.counter, passkey.counter))) .returning({ id: userPasskeys.id }); if (!updated.length) return { ok: false, reason: "failed", userId: user.id, why: "counter" }; ``` A counter refusal is written to the login's audit trail with its own wording, which says the passkey may have been copied, so the owner of the login can see it. #### A stolen session cannot add a passkey If someone gets hold of a signed-in session, a passkey is the most useful thing they could add: it outlives the session and works without the password. So adding one asks for a fresh proof first. That is the password, or a two-step code (spent like any code), when the login has either. A login with neither, one that signs in with Google only, needs a sign-in from the last ten minutes: ```ts export function passkeyProofKind(login: { hasPassword: boolean; twoStepOn: boolean }): PasskeyProofKind { if (login.hasPassword && login.twoStepOn) return "password_or_code"; if (login.hasPassword) return "password"; if (login.twoStepOn) return "code"; return "recent_sign_in"; } ``` The proof is checked before any challenge is made, and its tries are limited per login, so a session cannot guess its way to the password through this form either. Adding a passkey also needs Manage at the business. Renaming and removing your own passkeys stays open to every member, because someone who later loses Manage must still be able to remove the passkey of a device they lost. #### Never the last way in Removing a passkey must never leave a login with no way to sign in. The rule is small: ```ts export function mayRemovePasskey(login: { hasPassword: boolean; hasGoogle: boolean; othersLeft: number }): boolean { return login.hasPassword || login.hasGoogle || login.othersLeft > 0; } ``` The race is the interesting part. For a login with no password and no Google sign-in, two tabs removing its last two passkeys at the same moment would each see one other passkey left, and both would go. removePasskey runs in a transaction that first locks the login's row with FOR UPDATE, then counts, then deletes, so the second removal counts after the first has committed. #### Where a passkey shows up later A passkey sign-in records which passkey it used in the session. When a business requires two-step login, the guard accepts that session only while the passkey is still on the login, so removing a passkey also stops it counting as a second step. The phone app is unchanged. Its token never names a passkey, and the tests check that it is refused at a two-step business just as before. #### What we take from it - Take the relying party from configuration. Anything read from the request is chosen by whoever sent the request. - Check the security properties you depend on in your own code, even when you also pass them to the library. It costs a few lines and protects you from a changed default. - Make spending a challenge and checking it the same statement. DELETE ... RETURNING gives you single use for free. - If the prompt never asks who you are, it cannot tell anyone who has an account. Make every refusal read the same. - Ask for proof before adding a long-lived credential, and lock the row before removing the last one. ### An idle timer you cannot reset by deleting a cookie A business can now sign its team out after 15 minutes to 2 hours without activity. Our sessions are stateless, so the server has no record of when anyone last did anything. Here is how a signed, per-business activity cookie answers that question without being something you can delete for a fresh window, and the two review findings that changed how it ships. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/an-idle-timer-you-cannot-reset-by-deleting-a-cookie · markdown: https://bookatu.com/engineering/an-idle-timer-you-cannot-reset-by-deleting-a-cookie.md > **The short version** > > - Auto sign-out is a per-business rule: 15, 30, 60 or 120 minutes, or off. Every admin page and action checks it in requireOrgAccess, the guard they already call. > - Sessions are stateless signed tokens, so activity is carried in a second signed cookie, one per business, bound to the login, the business and the sign-in (the session's iat). > - With no valid cookie, the clock starts at the later of the sign-in and the moment the rule was set. Deleting the cookie gives you the strictest answer, not a fresh window. > - Only the browser's own report of a click, key, scroll or touch writes the cookie. Polling, refreshes and prefetches read it and never move it. > - Review finding one: the report was first a server action, and setting a cookie inside a server action made Next.js re-render the whole page every minute. It is now a route handler, and two tests pin that. > - Review finding two: approving an OAuth app hands it owner-level access, so the consent action now holds to the idle rule too. Front desks share computers. Someone signs in to the admin at nine, gets pulled away to a client, and the screen stays open on the finance page for the rest of the day. The fix people expect is the one their bank uses: if nobody has touched it for a while, sign it out. On most stacks this is a column on the session row, updated on each request. Our sessions have no row. A session is a signed token in a cookie, checked by signature and a per-login revocation epoch. That is cheap and simple, and it means the server has no idea when anyone last did anything. #### A second signed cookie We did not want to add a session table and a write on every request for a rule most businesses leave off. Instead, while a business has the rule on, the browser reports activity at most once a minute, and the server stamps the time into a signed cookie that belongs to that business: ```ts export function idleActivityCookieName(orgId: string): string { return `bk_idle_${crypto.createHash("sha256").update(`bookatu:idle:${orgId}`).digest("base64url").slice(0, 16)}`; } function key(master: string): Buffer { return Buffer.from(crypto.hkdfSync("sha256", master, Buffer.alloc(0), "bookatu:idle-activity:v1", 32)); } ``` One cookie per business, so one business's rule never reads or writes another's. A person on two teams can be signed out of one and still working in the other. The name is a hash, so the business id is not spelled out on every request. The HMAC key is derived from the master secret with its own HKDF label, so a session token can never pass as an activity cookie or the other way round. A unit test signs an activity payload with the session cookie's key and checks that it is refused. The cookie carries five short fields: the login, the business, the sign-in it belongs to (the session token's iat), the last activity time, and a flag set once the person's own timer has signed them out. #### Whose cookie is it A valid signature is not enough. The cookie has to be this login's, at this business, from this sign-in: ```ts function belongs(a: IdleActivity | null, userId: string, orgId: string, sessionIat: number): a is IdleActivity { return !!a && a.u === userId && a.o === orgId && a.s === sessionIat; } ``` Binding it to the sign-in matters in both directions. Signing in again is a new session with a new iat, so an old stamp stops counting against you. And a stamp from yesterday's session, kept in a browser that someone copied cookies out of, cannot keep today's session alive. #### Deleting the cookie never buys time This is the decision in the title. The natural reading of "no cookie" is "just started", which fits the first page after sign-in. It would also let anyone reset the timer by clearing one cookie, which is exactly what an unattended browser does not need. The verdict runs from the stamp when there is a valid one, and otherwise from the later of the sign-in and the moment the rule was last set: ```ts export function idleVerdict(args: { setting: IdleSignOutSetting; userId: string; orgId: string; sessionIat: number; activity: IdleActivity | null; now: number; }): IdleVerdict { const { setting, userId, orgId, sessionIat, activity, now } = args; const mine = belongs(activity, userId, orgId, sessionIat) ? activity : null; if (mine?.x) return { idle: true, lastActiveAt: Math.min(mine.t, now), remainingMs: 0 }; const from = Math.min(now, Math.max(mine ? mine.t : sessionIat, setting.since)); const deadline = from + setting.minutes * 60_000; return { idle: now > deadline, lastActiveAt: from, remainingMs: Math.max(0, deadline - now) }; } ``` With no cookie, the clock starts at the sign-in. A session signed in three hours ago, under a rule that was already on, is three hours idle without its cookie. Deleting the cookie can only make your answer stricter. setting.since is the other half. When an owner turns the rule on, or changes the window, the time is saved with it. Nobody's idle time counts from before that, so turning the rule on never signs out a colleague who was working a minute ago, the owner included. The outer Math.min(now, ...) means a time from the future, in a hand-edited setting or a stamp, can never push the deadline out. The integration test for the title is short: ```ts it("deleting the activity cookie does not buy a fresh window", async () => { await turnOn(A, 15); signIn(a.users.staff); clock = T0 + 10 * MIN; await touchIdleActivityAction(A, 0); clock = T0 + 26 * MIN; h.jar.delete(idleActivityCookieName(a.orgId)); expect((await inA()).to).toBe(idleSignedOutPath(A)); }); ``` #### What counts as activity requireOrgAccess only reads the cookie. It is written in exactly two places: the activity report, and the timer's own sign-out, which sets the flag. Our admin polls for some things, refreshes others, and Next.js prefetches links. None of those move the stamp, so a dashboard left open with a live clock on it still goes idle. The browser side listens for pointerdown, keydown, wheel, touchstart, mousemove and scroll, and reports at most once a minute, trailing, so the stamp is never more than a minute behind the last real input. The server does not take the browser's word for when that was. The report says how long ago the activity happened, and the server clamps it: ```ts const back = Number.isFinite(args.idleMs) ? Math.min(IDLE_PING_EVERY_MS, Math.max(0, args.idleMs)) : 0; const mine = belongs(existing, userId, orgId, sessionIat) ? existing : null; const t = Math.max(now - back, mine ? Math.min(mine.t, now) : 0); return { u: userId, o: orgId, s: sessionIat, t }; ``` A browser can claim activity at most a minute back and never in the future, and the stamp never moves backwards. The report itself goes through requireOrgAccess without skipping the idle check. A browser that is already idle past the window is refused before it can write anything, so a late report cannot bring a session back. A minute before the end, the browser first asks the server how long is really left, since another tab may have kept the session alive, and asking does not count as activity. Then it shows a warning with a countdown. A stray mouse move does not dismiss the warning. Stay signed in does. #### The guard The check sits in requireOrgAccess, after the membership check and before the role, email and two-step gates: ```ts if (!opts.skipIdleGate && (await idleSignOutState(org, user))?.idle) { redirect(idleSignedOutPath(org.slug)); } ``` idleSignOutState reads the org row the guard already holds and two cookies, so a business with the rule off pays no query at all. Only the timer's own two actions pass skipIdleGate: asking how long is left, and the sign-out itself, because both have to be able to answer "no time left". Platform support staff are not held to one business's rule, and the phone app's bearer path returns before this check and is left as it was. #### Review finding one: every report reloaded the page The first version reported activity through a server action, like the timer's other two calls. It worked, and its tests passed. The review found what it was doing to the page around it. That came from how Next.js treats cookies set inside a server action. Setting one makes the response report the action as revalidating. The client then empties its prefetch cache and re-renders the whole current page: the admin layout, the calendar, finance and all their queries. The report sets a cookie up to once a minute while someone works, so the admin was quietly reloading itself under them every minute. The fix was to move the one call that writes the cookie to a route handler, POST /api/idle-activity. A route handler sets the cookie with no effect on the page. It keeps the same guard. A refusal comes back as a 401 with the redirect target, which the browser opens, the same as the action's redirect did. It only accepts a JSON body, so a form on another site cannot post to it. The comment at the top of the route explains why it is not an action, so nobody tidies it back into one: ```ts * A route handler, not a server action, on purpose: any cookie set inside a * server action makes Next report the action as revalidating, and the client * then empties its prefetch cache and re-renders the whole current page (the * admin layout and the calendar, finance and so on, with all their queries). ``` Two tests pin it. The integration test checks that the actions module no longer exports a report action at all, and that the route answers with no-store and writes the cookie. The component test drives the timer through two minutes of activity and checks the reports went through the plain request: ```ts expect(client.reportIdleActivity).toHaveBeenCalledTimes(2); expect(Object.keys(actions).sort()).toEqual(["idleSignOutAction", "idleStatusAction"]); expect(actions.idleStatusAction).not.toHaveBeenCalled(); expect(actions.idleSignOutAction).not.toHaveBeenCalled(); ``` The same trap caught the passkey sign-in page in the same release, where asking for a challenge sets a cookie and the page asks for one as soon as it opens. That fix was the same: a route handler. #### Review finding two: the OAuth consent page Bookatu lets owners and admins connect outside apps through OAuth. The consent action is not under /admin and did not call requireOrgAccess. It checked the session, two-step login and that the user was an owner or admin of the chosen business. A browser signed out of a business for inactivity could still open the consent page and hand an app owner-level access to that business. The fix holds the consent action to the same rule as every admin action: ```ts const org = orgId ? await getOrgById(orgId) : null; if (org && (await idleSignOutState(org, user))?.idle) redirect(idleSignedOutPath(org.slug)); ``` The tests cover a browser idle past the window, a browser whose own timer signed it out two minutes in, and the two cases that must keep working: the same owner while active, and the same owner at another business that has the rule off. The idle browser gets no authorization code. The active owner, and the same owner at the other business, each get one. > A rule that guards the admin has to guard every door that grants what the admin grants. #### What we take from it - When the server keeps no state, decide what a missing cookie means before anything else. Here it means the strictest answer, so deleting it gains nothing. - Bind a client-held stamp to everything it is about: the login, the business and the sign-in. A valid signature is not ownership. - Only an explicit report should count as activity. Anything the app does on its own, such as polling, refreshing or prefetching, must not keep a session alive. - In Next.js, a cookie set inside a server action re-renders the page. A call that sets a cookie often belongs in a route handler. - List every door that grants the same access, not just the ones under the same path. OAuth consent was one we nearly missed. ### Parsing what someone else's AI wrote The blog editor can now hand a business owner a prompt for ChatGPT, Claude, Gemini or any other AI, and read back whatever it replies. We do not control that model or its output. Here is how we ask for JSON, read it tolerantly, strip HTML until nothing changes, stay fast on hostile input, and the two review findings that changed the panel. The Bookatu engineering team · 2026-10-28 · Engineering · https://bookatu.com/engineering/parsing-what-someone-elses-ai-wrote · markdown: https://bookatu.com/engineering/parsing-what-someone-elses-ai-wrote.md > **The short version** > > - "Use your own AI" builds a prompt that is itself a JSON document, asking for a JSON object with six known keys. The owner pastes it into any AI and pastes the reply back. It all runs in the browser and uses no AI credits. > - parseBlogAnswer reads raw JSON, JSON inside a code fence, or JSON with chatter around it, and unwraps one level of {"post": {...}}. A title and a body are required. Everything else may be missing. > - HTML is stripped in passes until a pass changes nothing, because one pass over <img ...> leaves an behind. An unclosed / is correct for closed comments. The trouble is an unclosed one. A post about writing HTML might contain ""); const head = last === -1 ? "" : s.slice(0, last + 3).replace(//g, ""); return (head + s.slice(last === -1 ? 0 : last + 3)).replace(/
``` ```css /* Components read tokens, never raw colours. A button three levels deep inherits --brand from the scope above it. */ .sf-scope { --surface: #ffffff; --text: #111827; } .sf-scope .button-primary { background: var(--brand); color: #fff; } .sf-scope .chip { background: var(--brand-soft); color: var(--text); } ``` Because custom properties inherit, there is no per-tenant CSS to write or ship. The component stylesheet is fixed. Only the values on the scope change, and they change at request time, not at build time. #### Dark mode as a second plane Dark mode is not a new set of components. It is the same tokens with different values. We call it a "plane" because the component layer stays still while the value layer underneath swaps. A data attribute on the scope picks the plane. ```css /* Light is the default plane, declared on the scope. */ .sf-scope { --surface: #ffffff; --text: #111827; } /* The dark plane is the same token names, new values. No component rule changes. Only the variables move. */ .sf-scope[data-sf-theme="dark"] { --surface: #0b0b0f; --text: #f4f4f5; } ``` We also respect the visitor's system setting. MDN describes prefers-color-scheme as the media feature that detects whether a user "has requested a light or dark color theme." We use the media query as the default and let an explicit choice on the attribute override it. One detail worth stating: set that attribute synchronously in a tiny head script before the first paint, or the page flashes the wrong plane for a frame while your client script catches up. #### The specificity gotcha Here is the bug. A tenant's brand usually comes with a soft tint, a near-white version of their colour used for hover backgrounds and chips. In light mode it reads fine. In dark mode that near-white tint glows against the dark surface. We wrote a dark-plane rule to recompute the tint. It did nothing. The chips stayed pale. The reason is specificity. The tenant's tint was injected inline, on the style attribute. MDN puts inline styles at a specificity weight of 1-0-0-0, which beats any selector. Our dark rule was a selector, .sf-scope[data-sf-theme="dark"], so it ranked lower. The inline near-white value won every time, in both planes. Custom properties are not special here; they follow the same cascade as normal properties, so an inline custom-property declaration outranks a stylesheet one. > The value would not budge no matter how specific we made the selector. That is the tell: it was not a cascade problem, it was an inline declaration we could not outrank with another normal rule. MDN is blunt about the only escape: "The only way to override inline styles is by using !important." So the dark-plane override gets one !important, and the tint finally recomputes for the dark surface. ```css /* The inline --brand-soft wins over a plain selector, so it leaks into dark mode. !important lets this normal rule beat the inline declaration, and only on the dark plane. */ .sf-scope[data-sf-theme="dark"] { --brand-soft: color-mix(in srgb, var(--brand) 28%, #0b0b0f) !important; } ``` We do not reach for !important often. MDN warns that it "interacts directly with specificity and the cascade" and that overuse makes stylesheets hard to follow. But this is the exact case the keyword exists for: a normal stylesheet declaration that must beat an inline one. It is one property, scoped to one plane, with a comment explaining why. #### Keeping the planes apart Bookatu actually runs two theme systems. The marketing site and the owner's dashboard use a global theme on the document root. The public storefront uses its own scope, because a tenant's brand colour and the visitor's chosen storefront mode must not bleed into the app chrome. We scope them separately: the app theme on one attribute at the root, the storefront theme on .sf-scope with its own attribute. A visitor choosing a dark storefront does not flip the salon owner's dashboard. Two planes, two scopes, no leaks. The payoff is that a salon, a photographer, and a restaurant share one component tree, one stylesheet, and one dark mode. The only thing that changes per tenant is a handful of variable values, set on a single element. And when you hit a value that will not move, check whether it was injected inline before you blame the cascade. #### Sources - Using CSS custom properties (variables) - MDN Web Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_cascading_variables/Using_CSS_custom_properties - Specificity - CSS - MDN Web Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity - !important - CSS - MDN Web Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/important - prefers-color-scheme - CSS - MDN Web Docs: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme ### One codebase, thousands of branded sites: our multi-tenant model How Bookatu serves every tenant's branded storefront and back office from one Next.js app: a slug in the path, a flag-gated host proxy, and org_id on every query. The Bookatu engineering team · 2026-06-22 · Architecture · https://bookatu.com/engineering/multi-tenant-architecture · markdown: https://bookatu.com/engineering/multi-tenant-architecture.md Bookatu is a booking platform that takes 0% commission. A hair studio in Wellington, a physio clinic, a photographer running private galleries: each one gets a public storefront where clients book, plus a back office where the business runs. Each wants it to look like their site, in their colours, eventually on their own domain. We run all of them from a single Next.js app and a single Postgres database. That is the tension worth writing about. One deploy has to feel like thousands of separate sites, and a query for one tenant's customers must never return another tenant's. This post walks through how we actually do it: a slug in the URL, a thin host proxy for custom domains, and org scoping written into every read and write. No service mesh, no per-tenant deploy, no database per customer. > **The gist** > > - The URL slug is the tenant key. app/[org]/... carries it, and one cached helper turns it into an organisation row. > - Branding is data, not a build. Colours come out of the DB row and become CSS variables at the layout level. > - Custom domains are a flag-gated proxy that rewrites an inbound host to /{slug}. The rest of the app never knows. > - Isolation is org_id on every domain table, plus the discipline of putting it in every WHERE clause. #### The slug is the tenant Routing starts with one dynamic segment. The whole tenant surface lives under app/[org], where [org] is the slug. Under it sit two route groups: (site), the public storefront (booking page, account, gift cards, waitlist), and admin, the back office. Same segment, two very different audiences, no duplicated tenant plumbing. Turning that slug into a real organisation is the job of one small tenant module. The core lookup is wrapped in React's cache() so a page and its layout, which both need the org on the same request, only hit the database once. ```ts export const getOrgBySlug = cache( async (slug: string): Promise => { if (!slug) return null; const rows = await db .select() .from(organizations) .where(eq(organizations.slug, slug.toLowerCase())) .limit(1); return rows[0] ?? null; }, ); ``` Around that sit a few rules that matter in production. requireOrg returns the org or renders a 404, but first it checks a small alias map: when a tenant renames its public URL, the old slug redirects to the new one so existing links and printed QR codes keep working. There is also a public variant of the lookup that only ever exposes published storefronts, so the public API and AI agents never see anything that is not a live business. #### Branding is a row, not a build A common trap with white-label products is treating each tenant's look as a build artefact or a theme bundle. We treat it as data. The organisations row carries the branding: a primary colour, a logo URL, a hero image, a tagline. The org layout reads the row and turns the colour into CSS custom properties on a wrapper that contains both the storefront and the admin shell. ```tsx const { org: slug } = await params; const org = await requireOrg(slug); // primaryColor from the DB becomes CSS variables for this subtree return
{children}
; ``` brandStyle does a little colour maths with color-mix in oklab to derive a hover shade, a soft tint, and a focus ring from the one stored colour, so a tenant picks a single value and the whole UI stays coherent. Because it is just CSS variables on a div, there is no per-tenant CSS to ship and no theme cache to invalidate. A colour change is one column update that takes effect on the next render. Components reference var(--color-primary) and never know which tenant they are rendering for. #### Custom domains: one proxy, zero new routes Most tenants live at bookatu.com/{slug}. Some want their own domain pointing at their storefront, like a studio on ariahair.example.com. The constraint we set ourselves: this should add exactly one routing change and nothing else. The app/[org] tree should not learn a single new thing about domains. That one change is proxy.ts (Next 16 renamed middleware.ts to proxy.ts). It resolves the inbound Host header to the owning org and does an internal rewrite to that org's storefront path. The storefront tree serves the request exactly as it would for a /{slug} URL, because as far as it is concerned, that is the URL. ```ts // Flag OFF -> pure pass-through. No Host read, no DB, zero routing change. if (!customDomainsEnabled) return NextResponse.next(); // Platform / preview / local hosts skip the DB in the common case. const host = (req.headers.get("host") || "").split(":")[0].toLowerCase(); if (!host || isPlatformHost(host)) return NextResponse.next(); // Only an 'active' custom domain resolves to a slug; unknown hosts fall through. const slug = await getOrgByCustomDomain(host); if (!slug) return NextResponse.next(); const path = req.nextUrl.pathname === "/" ? "" : req.nextUrl.pathname; const url = req.nextUrl.clone(); url.pathname = `/${slug}${path}`; return NextResponse.rewrite(url); ``` This code runs on every matched request, so the ordering is deliberate. The feature is flag-gated, and when the flag is off the first line returns before the host is even read, a byte-for-byte pass-through. When it is on, platform, preview and local hosts (bookatu.com, *.vercel.app, localhost) fast-path out with no database cost, so normal traffic never pays for the lookup. Only a genuinely unknown host reaches the resolver. The resolver is the part that keeps this cheap and safe. It is backed by a module-level TTL cache that stores misses as well as hits. React's cache() only dedupes within one request, but the proxy runs per request, so a cross-request cache is what actually stops a database hit on every visit. Caching the negative result matters just as much: a flood of requests with random Host headers can't turn into a flood of lookups. The resolver also never throws. Any database error resolves to null, and the proxy falls through to a normal response, so a wobble in the domains table can't take the storefront down. One more rule lives here: custom domains serve the public storefront only. An /admin request arriving on a custom domain is redirected to the equivalent path on the platform host rather than rewritten, so the back office has exactly one home. #### Mapping a host to an org, and one org to many domains Behind the proxy is a custom_domains table rather than a column on the org. A small business legitimately wants an apex plus a couple of aliases (the .co.nz, the .com, a redirect host), so one org owns up to five domains, all pointing at the same storefront. The resolver joins the table to organisations purely to fetch the slug, and only matches rows whose status is active, so a domain still pending DNS or settling its certificate is never served. ```ts const rows = await db .select({ slug: organizations.slug }) .from(customDomains) .innerJoin(organizations, eq(organizations.id, customDomains.orgId)) .where(and( sql`lower(${customDomains.domain}) = ${key}`, eq(customDomains.status, "active"), )) .limit(1); ``` A global unique index on lower(domain) is the real guard against two accounts claiming the same host. The per-org cap of five is enforced twice: a cheap pre-check, then a re-count under a per-org advisory lock inside the insert transaction, so two concurrent adds can't both slip past the limit. The lock is keyed to the org, so it never blocks other tenants. Attaching the domain on the hosting side and writing the row are kept in step, and if a concurrent add fills the last slot, we detach the orphan rather than leave it dangling. None of this leaks into the app; it all sits behind the same resolver the proxy already calls. #### Isolation: org_id everywhere, every query Branding and routing are the visible half. The half that has to be right is data isolation, and ours is deliberately boring. Every domain table carries the tenant's id, and every query that touches tenant data filters by it. There is no clever ORM magic that auto-injects the scope; the scope is written out, on purpose, so it is visible in review. ```ts // list: scope the whole result set to this org .where(eq(customers.orgId, org.id)) // single row: id AND org, so you can't read another tenant's row by guessing an id .where(and(eq(customers.id, id), eq(customers.orgId, org.id))) ``` That second pattern catches the sharp edge. A bare eq(customers.id, id) would happily return any tenant's row if someone guessed or enumerated an id. Pairing the id with org.id means a lookup that doesn't belong to the current tenant returns nothing. The admin side gets org from requireOrgAccess, which checks the signed-in user's membership of that org before any data is read, so the org.id you scope to has already been authorised against the user. > The safest scope is the one you can see in the diff. We chose explicit org_id filters over invisible magic precisely because someone has to be able to spot a missing one in review. #### What this buys us, and where it bites The payoff is real. One deploy ships every tenant at once. A new storefront is a row, not a provisioning job. Branding is a column update. A tenant's own Stripe account, their bank, their funds (we never touch them, which is what 0% commission means in practice) hangs off the same org row. Pricing by active clients over the last ninety days, rather than per seat, is just another query against the same scoped data, with all the core booking features available on every plan. The cost is discipline. A single shared database means a missing org_id is a real bug class, not a theoretical one, which is why the scope is explicit and why row lookups pair id with org. A shared deploy means one bad migration touches everyone, so schema changes are additive and idempotent. And a per-request proxy is high blast radius, which is why it is flag-gated, fast-paths the common case, caches negatives, and never throws. What's next is mostly hardening the seams. The custom-domain proxy is built and flag-gated rather than fully on. Longer term, the explicit-scope discipline is the thing we would most like to make harder to get wrong without making it invisible. A lint rule that flags a tenant-table query with no org filter would keep the safety we get from seeing it in the diff, while removing the chance of forgetting it. The model itself, slug in the path, branding in a row, org_id in every clause, has held up well as the surface has grown. ### A +25GB storage pack is just a quantity line: billing add-ons as Stripe subscription items How Bookatu turns a photographer's "+25GB storage pack" into a quantity line on the org's existing platform subscription, finds or creates a versioned price, prorates the change, and keeps the in-app storage cap from drifting away from what Stripe actually bills. The Bookatu engineering team · 2026-06-21 · Engineering · https://bookatu.com/engineering/billing-add-ons-as-stripe-subscription-items · markdown: https://bookatu.com/engineering/billing-add-ons-as-stripe-subscription-items.md > **The short version** > > - A photographer's storefront has private per-client galleries, and storage is metered. Buying a +25GB pack does not start a new subscription. It adds a quantity to a line on the org's existing platform subscription. > - We keep one versioned Stripe price per pack and find it by a stable lookup_key, creating it only the first time. > - Buying, changing, or dropping packs maps to create, update, or delete on a single subscription item, with proration so the org pays only for the days it holds the extra space. > - Stripe is the source of truth for what was billed. A nightly reconciliation job pulls the item quantity back into our in-app cap so the two never drift. > - Idempotency keys and webhook-driven cap updates stop double-charges and stale limits. #### Why an add-on is just a line item Bookatu is one booking platform with per-industry verticals. The photographer vertical leans on private per-client galleries. The photographer uploads high-res files, and we auto-generate a low-res, EXIF-stripped, watermark-baked preview at 1080px. That preview pipeline plus the originals adds up, so gallery storage is metered and sellable in +25GB packs. Each org already pays us a platform subscription. The cleanest model for an add-on is not a second subscription and not a one-off charge. It is an extra line on the subscription the org already has. Stripe calls that line a subscription item. A storage pack becomes a subscription item whose quantity is the number of packs. Buy three packs, quantity is 3. The Stripe quantities guide describes exactly this licensed, per-unit billing where the line cost is unit price times quantity. #### Find or create a versioned price We do not create a fresh Stripe Price on every purchase. We keep one Price per pack version and look it up by a stable lookup_key. Versioning the key (v1, v2, and so on) means a price change for new buyers never silently re-prices existing orgs. Stripe's transfer_lookup_key moves the key onto the new price when we cut a version, so the lookup stays a one-liner. Amounts below are illustrative, not a published Bookatu price. ```typescript // One Price per pack version, found by a stable lookup_key. async function findOrCreatePackPrice(version: string): Promise { const lookupKey = `storage_pack_25gb_${version}`; const existing = await stripe.prices.list({ lookup_keys: [lookupKey], active: true, limit: 1, }); if (existing.data[0]) return existing.data[0]; // First buyer on this version creates the Price once. return stripe.prices.create({ lookup_key: lookupKey, currency: "usd", unit_amount: 500, // example: per 25GB pack, per month recurring: { interval: "month" }, product: packProductId, // the pack's Stripe product transfer_lookup_key: true, // claim the key from any prior price }); } ``` #### Create, update, or delete the item Setting the pack count is one function with three branches. If the org wants packs and has no item yet, create the item. If it has one, update the quantity. If it drops to zero, delete the item. We pass proration_behavior so Stripe bills the difference for the remaining days, and an idempotency key so a retried request never charges twice. ```typescript async function setPackQuantity(orgId: string, packs: number) { const sub = await getPlatformSubscription(orgId); const price = await findOrCreatePackPrice(currentPackVersion); const item = sub.items.data.find( (i) => i.price.lookup_key?.startsWith("storage_pack_25gb_"), ); // Same desired state, same key. Retries collapse to one charge. const opts = { idempotencyKey: `packs:${orgId}:${sub.id}:${packs}` }; const proration = { proration_behavior: "create_prorations" as const }; if (packs === 0) { if (item) await stripe.subscriptionItems.del(item.id, proration); return; } if (!item) { await stripe.subscriptionItems.create( { subscription: sub.id, price: price.id, quantity: packs, ...proration }, opts, ); return; } await stripe.subscriptionItems.update( item.id, { quantity: packs, ...proration }, opts, ); } ``` One sharp edge from Stripe's change-price guide: if you update a subscription with a new price but do not name the item, Stripe adds a second item instead of replacing the first, leaving both active. We always target the item by id, so a version bump replaces in place rather than stacking a duplicate line. #### Proration: what the org actually pays Storage is bought mid-cycle. Proration is what makes that fair. Stripe's prorations guide explains it with a clean example: change a plan halfway through the period and you get a credit for unused time on the old amount plus a charge for the remaining time on the new amount. For our add-on the same math runs at the item level. Add a pack with fifteen days left in the month and the org is billed for roughly half a pack now, then the full pack on the next invoice. > Negative prorations are not automatically refunded and positive prorations are not immediately billed. That default is a feature: a photographer who tries a pack for a busy weekend gets a credit on the next invoice, not a flurry of tiny charges and refunds. If you do need to collect immediately, Stripe supports proration_behavior set to always_invoice, which finalizes an invoice on the spot. We keep the default create_prorations because storage packs are small and recurring, and folding the delta into the next invoice is calmer for the tenant. #### Keeping the cap and the quantity from drifting Two numbers describe the same fact. Stripe holds the billed quantity. Our app holds the storage cap that the upload pipeline enforces. If those disagree, either the photographer is paying for space they cannot use, or they are using space they are not paying for. Both are bugs. Stripe is the source of truth for money, so the cap follows the quantity, never the other way around. We close the gap from two directions: - Webhooks, live. On customer.subscription.updated we recompute the cap from the item quantity. As the Hookdeck webhook guide recommends, the handler verifies the signature, dedupes on the event id, and stays small so a slow database write never times out Stripe's delivery. - Reconciliation, nightly. A scheduled job re-reads each subscription and rewrites the cap from what Stripe billed. Stripe's own reconciliation writeup frames this as the safety net: even if a webhook is lost or the handler was down, the batch pass catches the drift. ```typescript // Nightly: Stripe's billed quantity wins, the in-app cap follows. async function reconcileStorageCap(orgId: string) { const sub = await getPlatformSubscription(orgId); const item = sub.items.data.find( (i) => i.price.lookup_key?.startsWith("storage_pack_25gb_"), ); const billedPacks = item?.quantity ?? 0; const capGb = (await includedGbForPlan(orgId)) + billedPacks * 25; const org = await db.org.get(orgId); if (org.storageCapGb !== capGb) { await db.org.update(orgId, { storageCapGb: capGb }); log.warn("storage cap drift corrected", { orgId, was: org.storageCapGb, now: capGb, billedPacks, }); } } ``` #### What we learned - Model the add-on as a quantity, not a product catalog. One item, one number to move up and down. - Version the price by lookup_key so a future price change cannot re-price orgs that already bought. - Always target the subscription item by id when replacing a price, or Stripe leaves two live lines on the bill. - Pick one source of truth for the billed amount, make the in-app limit derive from it, and run reconciliation so a dropped webhook is an inconvenience rather than a refund ticket. #### Sources - Stripe Docs: Change the price of existing subscriptions: https://docs.stripe.com/billing/subscriptions/change-price - Stripe Docs: Prorations: https://docs.stripe.com/billing/subscriptions/prorations - Stripe Docs: Set product or subscription quantities: https://docs.stripe.com/billing/subscriptions/quantities - Stripe Dev Blog: Real-time vs batch reconciliation: https://stripe.dev/blog/database-reconciliation-growing-businesses-part-3 - Hookdeck: Guide to Stripe Webhooks, features and best practices: https://hookdeck.com/webhooks/platforms/guide-to-stripe-webhooks-features-and-best-practices ### Localizing into 13 languages without /[locale] routes How Bookatu ships its UI in 14 languages with no /[locale] URL segment: a pure deep-merge catalog, a visitor-locale resolver over header, cookie and geo, and SEO bolted on later behind a flag. The Bookatu engineering team · 2026-06-21 · Internationalization · https://bookatu.com/engineering/i18n-without-locale-routes · markdown: https://bookatu.com/engineering/i18n-without-locale-routes.md Most Next.js i18n guides start by carving a `[locale]` segment into the route tree. You end up with `/en/pricing`, `/de/pricing`, a `generateStaticParams`, and every link in the app suddenly needs to know the current locale to build a correct href. That works when the whole product is one big localized site. Bookatu isn't shaped that way. We have two very different kinds of surface. There's our own marketing, signup and app chrome, where the language should follow the visitor. And there's each tenant's public storefront, which is the tenant's business, in the tenant's chosen language and money format, no matter who's looking at it. A single URL-driven locale would conflate the two: a German visitor browsing a New Zealand salon's booking page shouldn't flip that salon into German. So we kept locale out of the URL and made it a data concern instead. > **The gist** > > - Two locale planes: the org's locale formats a storefront, the visitor's locale translates our own surfaces. Neither lives in a route segment. > - The resolver is a pure, dependency-free function: exact locale, then language prefix, then English, with per-key fallback inside each group. > - A partial translation is always safe. A missing key, or a whole missing section, silently shows English. > - Per-language URLs for SEO came later, as a flag-gated proxy rewrite, not a rewrite of the route tree. #### One catalog, deep-merged onto English The English catalog is the source of truth. It's a plain object grouped by surface (`storefront`, `booking`, `auth`, `signup`, and so on), and its type comes straight from the value: ```ts export const en = { storefront: { bookNow: "Book now", backToHome: "Back to home" }, auth: { signIn: "Sign in", signingIn: "Signing in…" }, // … }; // NOT `as const`: values are typed as `string`, so a translated // catalog can hold its own text while keeping the exact key shape. export type Messages = typeof en; export type DeepPartial = { [K in keyof T]?: T[K] extends object ? DeepPartial : T[K] }; export type LocaleCatalog = DeepPartial; ``` That comment about `as const` matters more than it looks. With `as const`, `bookNow` would have the literal type `"Book now"`, and a German catalog assigning `"Jetzt buchen"` would fail to type-check. Leaving it off makes every value a `string`, so a translation keeps the exact key structure while carrying different text. The `DeepPartial` on top lets a translator override only what they've done so far. Resolution itself is tiny and pure, which is the point. It runs unchanged in server and client components, with no provider and no async: ```ts export function getMessages(locale?: string | null): Messages { if (!locale) return en; const lc = locale.toLowerCase(); const override = LOCALES[lc] ?? LOCALES[lc.split("-")[0]]; return override ? merge(en, override) : en; } ``` So `getMessages("fr-CA")` looks for an exact `fr-ca` catalog, falls back to the `fr` language catalog, and finally to English. The `merge` is a shallow merge at the group level: for each translated group it spreads the override over the English group of the same name (`{ ...en[group], ...override[group] }`). Because the catalog is one level of nesting deep, that's enough. If French translated `auth` but not `booking`, the whole `booking` group comes through from English. If it translated `auth.signIn` but not `auth.signingIn`, that single missing key falls back too. > A missing key, or an entire missing section, silently renders English. A half-finished translation never breaks a page, and adding a new English string never breaks an existing catalog's build. #### The visitor plane: resolving a language without a URL If the locale isn't in the URL, something has to decide it per request. For our own surfaces that's `getVisitorLocale`, a server-only function that reads request state in a strict priority order: - An internal locale request header, when present. The proxy sets this on a per-language URL, and it's the strongest, most explicit signal. - A pinned locale cookie, set when the visitor uses the language toggle or has visited a localized URL before. An explicit choice beats detection. - Geo: Vercel's `x-vercel-ip-country` header, mapped to a default business language for that country. - The `Accept-Language` header's first entry. - English. ```ts export async function getVisitorLocale(): Promise { const h = await headers(); const fromPath = h.get(localeHeaderName); // set by the proxy on /de/... URLs if (fromPath) return normalizeLocale(fromPath); const pinned = (await cookies()).get(localeCookieName)?.value; if (pinned) return normalizeLocale(pinned); const geo = localeForCountry(h.get("x-vercel-ip-country")); if (geo !== "en") return geo; const accept = h.get("accept-language"); if (accept) { const first = normalizeLocale(accept.split(",")[0]); if (first !== "en") return first; } return "en"; } ``` The country mapping is deliberately conservative. We only map countries Stripe supports, and multilingual countries pick the most common business language (Switzerland and Austria go to German, Belgium and Luxembourg to French) on the understanding that the visitor can always switch. Anything unmapped, including the US, UK, Ireland, Australia and New Zealand, stays English. `normalizeLocale` strips any region or casing (`fr-CA`, `FR_fr`) down to a supported two-letter code, or English if we don't have it. A server component resolves this once and hands `{ locale, messages }` to a thin client `LocaleProvider`. Client components then read strings with `useMessages()`. The provider defaults to English so a component used outside a provider still renders, and on a localized route it nudges `document.documentElement.lang` to match, so screen readers and JS-rendering crawlers see the real language. #### Why cookie-and-geo localization is invisible to Google The cookie-plus-geo approach is great for humans and useless for Googlebot. The crawler arrives with no cookie, crawls predominantly from the US, and sends a generic `Accept-Language`. Every one of our detection signals resolves it to English. So however many languages we render for real visitors, Google only ever indexes the English version. There's nothing for it to discover for the other thirteen. The fix is the one thing we'd avoided: distinct URLs per language. But we added them as a narrow, reversible layer rather than re-architecting routing. English stays unprefixed, so every existing URL is byte-for-byte unchanged. The thirteen other languages get a `/` prefix, and only on marketing roots we explicitly allow-list (the home page, `pricing`, `discover`, `blog`, `help`, `faq`, plus `developers` and `compare`). Tenant storefronts, `/admin`, `/api` and auth are never prefixed, so an org whose slug happens to be two letters is never shadowed. #### A flag-gated proxy rewrite, not a route segment The whole feature lives in the proxy (Next 16's renamed `middleware.ts`) and is gated by a build-time flag. When the flag is off, the block is skipped entirely and routing is unchanged. When it's on, a localized request is rewritten back to its canonical English path, with the locale handed downstream as a header: ```ts if (localeUrlsEnabled) { const { locale, path } = splitLocalePath(req.nextUrl.pathname); if (locale !== "en" && path !== req.nextUrl.pathname) { const requestHeaders = new Headers(req.headers); requestHeaders.set(localeHeaderName, locale); // feeds getVisitorLocale const url = req.nextUrl.clone(); url.pathname = path; // /de/pricing -> /pricing const res = NextResponse.rewrite(url, { request: { headers: requestHeaders } }); res.cookies.set(localeCookieName, locale, { path: "/", maxAge: 31536000, sameSite: "lax" }); return res; } } ``` So `/de/pricing` is served by the existing `/pricing` page. No `[locale]` directory, no duplicated routes, no `generateStaticParams`. The page tree never learns about locales; it just reads the resolved messages as before. The proxy also pins the cookie, so once a visitor lands on a German URL, their in-language navigation to unprefixed internal links stays German via the cookie branch of the resolver. The careful bit is `splitLocalePath`. It only treats a leading segment as a locale when the following segment is one of the allow-listed marketing roots. `/de/pricing` parses as German pricing; `/de/some-org` is left untouched, because `some-org` isn't a marketing root, so a tenant storefront can never be mis-parsed as a localized page. To make the languages actually indexable, the sitemap emits `hreflang` alternates for exactly those localized paths, each variant self-canonical, plus an `x-default` pointing at English. The toggle closes the loop on the client: when per-language URLs are on and you're on a localizable page, picking a language navigates to the prefixed URL, so the URL is shareable and crawlable; everywhere else it just pins the cookie and refreshes. #### What this bought us, and what we'd watch The payoff is that localization stayed a data problem. Adding a language is dropping in one small per-language catalog file and registering it; nothing at the call sites changes, and untranslated keys are safe by construction. The visitor plane and the org plane never fight, because the same `getMessages` serves both from different inputs. And the SEO layer that finally put locale into the URL did so without touching the route tree, behind a flag we can switch off in one line. The honest trade-offs: the group-level merge assumes a one-level-deep catalog, so if we ever nest a third level we'd need a real recursive merge or we'd silently drop English siblings. Geo-defaulting a language is a guess, and the cookie is the only thing that makes it stick, so a visitor who clears cookies gets re-detected each time. And keeping the translated catalogs honest against a moving English baseline is a process problem more than a code one; the type system guarantees they compile, not that they're complete or well translated. For now, English-as-floor is the safety net we want while the catalogs fill in. ### Keeping a client photo gallery private: row scoping, a private bucket, and a route that 404s on any mismatch How Bookatu keeps each photographer's client galleries private in a multi-tenant app: org plus customer row scoping in Postgres with Drizzle, a private blob store, and a serving route that checks ownership and returns 404 for anything you do not own. The Bookatu engineering team · 2026-06-20 · Engineering · https://bookatu.com/engineering/private-photo-galleries-multi-tenant-row-scoping-ownership-404 · markdown: https://bookatu.com/engineering/private-photo-galleries-multi-tenant-row-scoping-ownership-404.md > **The short version** > > - A private client gallery is a textbook target for broken access control. The fix is boring on purpose. > - Every row is scoped by two keys: the tenant (org) and the customer. Queries filter on both, always. > - The image bytes live in a private bucket. Nothing is served by a public URL. > - One serving route checks ownership and returns 404 for anything you do not own. It never confirms that an id exists. > - OWASP puts this under A01 Broken Access Control. We treat it as the first thing to test, not the last. Bookatu is one booking platform with per-industry verticals: salon, spa, personal trainer, sports coach, fitness studio, restaurant, and photographer. The photographer vertical ships private per-client photo galleries. The photographer uploads high-res files. We auto-generate a low-res (1080px) preview with a baked-in watermark and stripped EXIF, and the client sees only that preview until the included and paid set is settled. Clients reach their gallery through a long-lived passwordless magic link. That feature is a wedding shoot, a newborn session, a set of headshots. It is exactly the kind of data that must never leak to another client or another studio. This post is the access-control spine behind it. None of it is clever. That is the point. #### The vulnerability we are designing against OWASP describes an Insecure Direct Object Reference (IDOR) as exposing an internal reference, like a database id, without checking that the caller is allowed to use it. It sits under A01 Broken Access Control, the top category in the OWASP Top 10. The failure mode is simple: a gallery loads at /g/1041, someone tries /g/1042, and the server hands back a photo that belongs to a different client. The server trusted the client to ask for the right id. The OWASP IDOR prevention guidance is direct about the fix. Scope every data-access query to the current user, and do not rely on the reference alone. Their example reads SELECT ... WHERE id = :id AND user_id = :current_user. We follow that shape, with two scoping keys instead of one. #### Two keys on every row Multi-tenant rows carry a tenant key so one studio can never read another studio's data. AWS makes the same point for pooled Postgres: isolation belongs in the data layer, enforced on every table that holds tenant data, not sprinkled across handlers. A gallery adds a second key for the client, so one client of a studio cannot read another client of the same studio. Here is the shape, with names simplified for illustration, and the only query pattern we allow. ```ts // schema (names generic for illustration) export const photos = pgTable('photos', { id: uuid('id').primaryKey().defaultRandom(), tenantId: uuid('tenant_id').notNull(), // the studio (tenant) clientId: uuid('client_id').notNull(), // the client objectKey: text('object_key').notNull(), // private bucket path unlocked: boolean('unlocked').notNull().default(false), }, (t) => ({ // tenant key leads the index so scoped reads stay fast scopeIdx: index('photos_tenant_client_idx').on(t.tenantId, t.clientId), })); // every read is scoped by BOTH keys, never by id alone async function loadPhoto(db: DB, scope: Scope, photoId: string) { const [row] = await db.select().from(photos).where(and( eq(photos.id, photoId), eq(photos.tenantId, scope.tenantId), eq(photos.clientId, scope.clientId), )).limit(1); return row ?? null; // null means "not yours", treated the same as "absent" } ``` The scope object is never read from the request body or the path. It comes from the verified magic-link session for the client, or from the authenticated studio account. The id in the URL only narrows the result inside an already-scoped set. AWS notes that a leading tenant column on the index keeps these scoped reads cheap, so the safe query is also the fast query. #### The bytes live in a private bucket No photo is served by a public object URL. The bucket is private, and the object key never appears in client-facing HTML. When a client is entitled to a file, the app mints a short-lived presigned URL at request time. Cloudflare's R2 docs frame presigned URLs the right way: they grant time-limited access to a specific object to someone who would not otherwise have credentials. Short expiry means a copied link dies quickly, and a leaked watermarked preview is still only a watermarked preview. Entitlement is the gate. Clients get a presigned URL for the 1080px watermarked preview. The full-resolution key is only signed once the included free count plus any paid extras are settled. The unlock decision is a database read scoped by the same two keys, so storage never makes an authorization decision on its own. #### One route, ownership-checked, 404 on any mismatch All image access funnels through a single serving route. It resolves the session, scopes the read, and refuses to distinguish 'this id is not yours' from 'this id does not exist'. Both return 404. The CGI engineering guidance calls this resource hiding: a 403 confirms the resource is real, which lets an attacker map your data by scanning ids. A uniform 404 reveals nothing. ```ts // The private photo endpoint. The original is never a public asset. export async function GET(req: Request, { params }: Ctx) { const scope = await resolveScope(req); // magic-link or studio session if (!scope) return new Response(null, { status: 401 }); const photo = await loadPhoto(db, scope, params.id); // not found AND not-yours both land here. Same body, same status. if (!photo) return new Response(null, { status: 404 }); const wantsFull = new URL(req.url).searchParams.get('res') === 'full'; const key = wantsFull && photo.unlocked ? fullKey(photo) : previewKey(photo); if (!key) return new Response(null, { status: 404 }); // full not settled yet const url = await signGet(key); // short-lived presigned URL return Response.redirect(url, 302); } ``` Two details matter. First, a missing row and an unauthorized row take the identical branch, so timing and response shape stay constant. Second, the full-resolution path checks photo.unlocked before signing, so settlement is enforced on the server, not in the client UI. The id in the URL is a non-sequential UUID, which OWASP recommends as defense in depth. It is not the control. The scoped query is. #### Access-control sketch - Identify: verify the magic-link or studio session. No session, return 401. - Scope: build {tenantId, clientId} from the session only, never from the request. - Authorize: read the row filtered by id AND tenant AND client. No row, return 404. - Entitle: for full resolution, require unlocked = true, else 404. - Serve: mint a short-lived presigned URL for the private bucket and redirect. > Ensure that database queries and data access layers are scoped to the current user's permissions, for example SELECT * FROM orders WHERE user_id = :current_user AND id = :order_id. (OWASP IDOR prevention guidance.) #### What we test Cross-tenant isolation is a silent failure. A broken scope does not throw. It just returns the wrong rows. So we test it like AWS suggests for RLS: automated tests that act as client B and try every route with client A's ids, then assert 404 every time, with an identical body. We assert the full-resolution key is never signed while a gallery is unsettled, and that the private object key never appears in any response payload. Those tests run on every change to the gallery code. The lesson is that privacy here is not a feature you bolt on. It is the default query shape, the default bucket setting, and the default error code. Two keys on every row, a private bucket, and a route that gives nothing away. Boring, repeatable, and the thing a client's wedding photos actually depend on. #### Sources - OWASP Insecure Direct Object Reference Prevention Cheat Sheet: https://cheatsheetseries.owasp.org/cheatsheets/Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet.html - OWASP: Insecure Direct Object Reference (IDOR): https://owasp.org/www-community/attacks/insecure_direct_object_reference - AWS: Multi-tenant data isolation with PostgreSQL Row Level Security: https://aws.amazon.com/blogs/database/multi-tenant-data-isolation-with-postgresql-row-level-security/ - Cloudflare R2: Presigned URLs: https://developers.cloudflare.com/r2/api/s3/presigned-urls/ - When Should You Return 404 Instead of 403 (CGI Insights): https://www.insights.cgi.com/blog/when-should-you-return-404-instead-of-403-http-status-code ### Building a touch-friendly booking calendar from scratch Why we built Bookatu's drag-to-reschedule calendar on raw pointer events instead of a library, and how the touch model, swim lanes and optimistic updates actually work. The Bookatu engineering team · 2026-06-20 · Frontend · https://bookatu.com/engineering/building-the-booking-calendar · markdown: https://bookatu.com/engineering/building-the-booking-calendar.md Most calendar UIs assume a mouse on a wide screen. Ours can't. A salon owner runs the day from a phone behind the counter, between clients, with one thumb. The same screen has to show several staff side by side, let you drag a booking to a new time, draw a block to hold an hour off, and stay correct in the salon's own timezone. We tried to make a generic drag-and-drop library do all of that on touch, kept fighting it, and ended up writing the calendar ourselves on raw pointer events. This post walks through the real decisions in the calendar component and the availability engine behind it: why custom over a library, the touch gesture model, how swim lanes and drops resolve, and how optimistic updates stay fast without lying to the user. > **The gist** > > - Time is absolute-positioned pixels on a 24-hour grid (1.1px per minute), and drags snap to 15-minute slots. > - Everything runs on Pointer Events, so one code path covers mouse and touch. > - Drops resolve the target lane with elementFromPoint over data-colid columns, which sidesteps HTML5 drag-and-drop entirely. > - Drawing a new block on the empty grid is armed by a 250ms long-press so a normal swipe still scrolls; dragging an existing card opts out of scrolling with touch-action: none instead. > - Every action is optimistic with a captured original to revert to, and the server re-checks availability before it commits. #### Why not a calendar library Libraries are good at the common case. The problem is that our case is mostly edges, and the edges are where a library makes you fight its model. We needed multiple staff as columns on one day (swim lanes), drag-to-reschedule that also reassigns staff, draw-on-empty-grid to create a time block, drag handles in the time gutter to adjust opening hours, and all of it working under a thumb on a phone. The mobile story is where off-the-shelf touch handling tends to break: you get either a drag that hijacks page scrolling, or a scroll that won't let you drag. The layout itself is simple enough that owning it is cheaper than bending a library to it. A day is just minutes mapped to pixels. We fix a scale and position every appointment, block and gridline absolutely: ```ts const PX_PER_MIN = 1.1; const SLOT_MINS = 15; // drag snap interval const GRID_START_MIN = 0; const GRID_END_MIN = 24 * 60; // render the full day, grey the closed hours function snapToSlot(min: number): number { return Math.round(min / SLOT_MINS) * SLOT_MINS; } // An appointment's box: const top = (a.startMin - dayStartMin) * PX_PER_MIN; const height = Math.max(a.durationMin * PX_PER_MIN, 28); // floor so tiny ones stay tappable ``` Once geometry is that direct, the work isn't drawing the grid. It's the gestures, and a library doesn't help with the gestures we actually need. #### One pointer model for mouse and touch The whole calendar runs on Pointer Events. Not separate mouse and touch handlers, and not HTML5 draggable. A drag is a small state machine started in onPointerDown: record the start point, then in pointermove decide whether the gesture is a real drag or just a tap. We use a 6px slop before we treat a move as a drag, so a slightly shaky tap doesn't get read as a reschedule. ```ts onPointerDown={(e) => { if (!isDraggable || (e.pointerType === "mouse" && e.button !== 0)) return; const node = e.currentTarget as HTMLElement; const sx = e.clientX, sy = e.clientY; let moved = false; const move = (ev: PointerEvent) => { if (!moved && Math.hypot(ev.clientX - sx, ev.clientY - sy) > 6) { moved = true; node.style.pointerEvents = "none"; // so elementFromPoint sees the columns, not the card onDragStart(a.id); } if (moved) { ev.preventDefault(); const t = targetFromPoint(ev.clientX, ev.clientY); if (t) onDropTargetChange(t); } }; const up = (ev: PointerEvent) => { /* remove listeners */ node.style.pointerEvents = ""; if (!moved) { onSelect(a.id); return; } // no drag, a tap selects const t = targetFromPoint(ev.clientX, ev.clientY); if (t) onDrop(a.id, t.dateKey, t.startMin, t.colId); }; window.addEventListener("pointermove", move, { passive: false }); window.addEventListener("pointerup", up); window.addEventListener("pointercancel", up); }} ``` The card itself carries touch-action: none, so on a phone the drag starts at the 6px slop instead of being eaten by the scroller. The line that matters most on touch is the one generic solutions miss: when a drag starts, we set the dragged card's pointerEvents to none. That lets document.elementFromPoint report the column under the finger instead of the card you're holding. We don't track which lane you're over by maths, we ask the DOM. Each column carries a data-colid, so targetFromPoint walks up from the point to the nearest column and converts the y position back into a snapped minute. That one trick makes cross-lane drops behave the same on a trackpad and a thumb. ```ts function targetFromPoint(clientX: number, clientY: number) { const el = (document.elementFromPoint(clientX, clientY) as HTMLElement | null) ?.closest("[data-colid]") as HTMLElement | null; if (!el) return null; const raw = el.dataset.colid ?? ""; const rect = el.getBoundingClientRect(); const min = snapToSlot(Math.max(dayStartMin, dayStartMin + (clientY - rect.top) / PX_PER_MIN)); return { dateKey: date, startMin: min, colId: raw === "" ? null : raw }; } ``` #### Drag versus scroll: the hardest touch problem The genuinely hard part on a phone is drawing a new time block on the empty grid. A vertical finger drag there is ambiguous: it could mean scroll the day, or draw a block from 2pm to 3pm. You can't know which until the user commits, and if you guess wrong the page either jumps or freezes. (An existing card has no such ambiguity, since its own touch-action: none already claims the gesture, which is why only the empty grid needs the trick below.) We resolve it the way Google Calendar does. On touch, the draw isn't armed immediately. A normal swipe scrolls. A press-and-hold of 250ms arms the draw, and only then do we claim the gesture: set touch-action to none on the column and scroller, clear any text selection the long-press kicked off, and capture the pointer. If the finger moves past the tap slop before the hold fires, we treat it as a scroll and stand down. A mouse arms instantly, because a mouse has no scroll-versus-drag ambiguity. ```ts let armed = !isTouch; // mouse arms now; touch waits for the hold const arm = () => { armed = true; colEl.style.touchAction = "none"; // claim the gesture from the scroller if (scroller) scroller.style.touchAction = "none"; window.getSelection?.()?.removeAllRanges?.(); document.body.style.userSelect = "none"; colEl.setPointerCapture(pointerId); }; const armTimer = isTouch ? window.setTimeout(arm, DRAW_LONG_PRESS_MS) : 0; ``` Once armed, a block can grow past the visible screen. An edge auto-scroll runs on requestAnimationFrame: when the finger nears the top or bottom of the scroller, it scrolls the grid and keeps extending the selection. Because the grid slides under a stationary finger, we re-read the column's bounding rect on every frame rather than caching it once, or the mapped time drifts as you scroll. A capture-phase scroll listener recomputes the selection end even when no pointermove fires, so the box keeps tracking the grid during momentum scroll. On touch, a quick tap with no drag opens a default one-hour block-or-book chooser. These are the small behaviours a library can't know you want. #### Swim lanes that collapse on a phone On desktop, each staff member gets a column, plus an Unassigned lane that only appears when there's an unassigned booking. Side by side those lanes are fine on a wide screen and unusable on a phone, so on mobile we render one full-width lane at a time with a chip switcher above it. The desktop columns are hidden with a responsive class rather than unmounted, so the same component tree drives both. An org-wide block, one with staffId null, would naively render a duplicate copy in every column. Instead we draw it once as a single band spanning all lanes, clearly labelled as blocking everyone. It stays draggable vertically to change its time and stays org-wide however far sideways you drag it. Small thing, but a per-column copy read as a bug to every user who saw it. #### Optimistic updates that don't lie Every mutation (reschedule, status change, block move, hours edit) updates local state first and reverts on failure. The pattern is always the same: capture the original row, apply the change locally, call the server action, and on a non-ok result put the original back and show a toast. The user sees an instant move; if the server disagrees, it snaps back with a reason. ```ts const orig = appts.find((a) => a.id === apptId); setAppts((prev) => prev.map((a) => a.id === apptId ? { ...a, startMin: snapped, startAtISO: newStartIso, dateKey, staffId } : a, )); const res = await rescheduleAppointmentAction(slug, apptId, newStartIso, newStaffId); if (!res.ok) { setAppts((prev) => prev.map((a) => (a.id === apptId ? orig! : a))); // revert showToast(res.error ?? "Could not reschedule. Try again.", false); } ``` The detail that earns the optimism is timezone handling. A drop gives us a date and a snapped minute in the salon's local time, and we convert that to the correct UTC instant before sending it. An earlier version assumed UTC midnight, so 2pm in New Zealand became 2pm UTC, which is 2am local, and the slot then read as unavailable on the server. Booking times are exactly where naive date maths bites, so the calendar never trusts the browser's clock. It always converts through the org's timezone. Optimism is only safe because the server is the real authority. The client lets you drop almost anywhere, but the server's resolveBookingSlot recomputes that day's availability from scratch and confirms the exact slot still exists before it commits. The engine buckets appointments and blocks by local day in one pass, builds busy intervals per staff member with a configurable buffer, and splits a service that has processing time into two hands-on intervals, so the staffer stays bookable during, say, colour developing. The UI can be loose because the engine behind it is strict. ```ts // Server re-check at booking time (simplified) const day = (await getAvailability({ /* org, service, duration, from/to = key */ }))[0]; if (!day || !day.open) return { ok: false, reason: "Salon closed" }; const slot = day.slots.find((s) => s.startMin === startMin); if (!slot) return { ok: false, reason: "Time no longer available" }; return { ok: true, staffId: params.staffId ?? slot.staffIds[0] }; ``` #### Accessibility wasn't free, and it isn't done Drag interfaces are hostile to keyboards by default, so the gestures aren't the only way in. The opening-hours edges are real drag handles, but they're also role=slider with aria-valuenow and arrow-key support, so you can adjust open and close times without a pointer at all. Appointment cards are focusable, with Enter and Space to open the detail panel, and the panel lets you reassign staff without dragging, which doubles as the easy path on a small screen. Toasts announce through an aria-live region. > The geometry was a day. The gestures were a month. That ratio is the whole argument for and against building your own calendar. Would we do it again? For this product, yes. The cost of a custom calendar is concentrated in the touch state machines: the arm-on-hold logic, the auto-scroll, the elementFromPoint drop resolution. You don't escape that cost with a library so much as relocate it into fighting the library's assumptions. What's left is honest: keyboard reordering of appointments themselves, better screen-reader narration during a drag, and a week view that's as comfortable to drag on as the day view. None of it changes the core bet, which is that when the interaction is the product, owning the interaction is worth it. ### Stopping fake signups without punishing real owners How Bookatu keeps junk businesses off a public booking platform with layered checks that stay out of a real salon owner's way. The Bookatu engineering team · 2026-06-19 · Reliability · https://bookatu.com/engineering/stopping-fake-signups · markdown: https://bookatu.com/engineering/stopping-fake-signups.md Bookatu is a booking platform with a public side. Every business that signs up gets a storefront and a slug, and those pages can surface in discovery. That public surface is exactly what spammers want: a free, indexable page with outbound links. So the signup form is a target, and the cost of getting it wrong cuts both ways. The hard part is the asymmetry. A blocked spammer just moves on. A blocked real owner, usually someone trying to set up before their next client, often never comes back. So the goal was never to build a wall. It was to add friction that bots hit and humans don't, and to make sure that when the defences misfire, they misfire in the customer's favour. > **The short version** > > - Cheap, layered checks instead of one heavy wall: a disposable-domain blocklist, a sanity check on the email's domain, score-based bot detection, and an email-verification gate. > - Every check is tuned so that a mistake lands in the customer's favour. > - The real enforcement is non-blocking: a fresh org lands hidden and stays hidden until the owner verifies their email and connects Stripe. > - New defences never punish the people already here. The gate was rolled out so that existing tenants are never locked out by it. #### Layer 1: cheap rejection at the form The cheapest check is the email domain itself. A lot of throwaway signups use temporary-inbox providers, and the catch is that a disposable inbox can still receive a verification link, so it would quietly defeat the verification gate further down. We block those domains up front. Rather than hand-maintain a blocklist that goes stale, we build the set from a community-maintained list of throwaway domains and add a few typo-squats of our own on top (the gmial.com and hotmial.com class of thing). The whole thing is a pure function with no database and no network, so it slots straight into the zod schema as a refinement and is trivial to unit test. ```ts export const DISPOSABLE_EMAIL_DOMAINS: ReadonlySet = new Set( [...disposableList, ...CURATED_EXTRA] .map((d) => d.trim().toLowerCase()) .filter((d) => d.includes(".") && !d.includes("@")), ); // in the signup schema: email: z.string().trim().email().refine( (e) => !isDisposableEmailDomain(e), "Please use a permanent email, not a temporary/disposable one", ), ``` This catches the laziest bots and gives instant inline feedback. It blocks on a fixed, curated list rather than a guess, which is what makes a hard stop acceptable here. #### Layer 2: a DNS check that refuses to be confident The next obvious move is to confirm the email's domain can actually receive mail. This is where it would be easy to over-engineer and start blocking real people, so we made the check conservative to the point of timidity. It only rejects a domain that plainly does not exist, the classic typo. A real domain that happens to be set up in an unusual way still gets through, because mail can still reach it. The point of this layer isn't to be the enforcement. It's to give immediate, friendly feedback on an obviously dead domain (you fat-fingered gmail.con) without ever risking a false block on a real but oddly configured one. The actual enforcement is layer 4. #### Layer 3: bot scoring that only acts when it is sure Disposable lists and DNS checks don't stop a determined script using a real Gmail address. For that we run score-based bot detection on our public forms. The browser mints a token, and the server asks for a risk score before deciding what to do with the submission. One choice keeps this from hurting real users. We only act on a score when it clearly points to a bot, so a real person is not turned away on a guess. Where the pass line sits is a judgment call we keep revisiting, and the scoring decision itself (including replay protection, so a token minted for one form can't be spent on another) is split into its own pure function so it's unit-tested without touching the network. The reasoning is simple. This is bot friction, and it should never be the reason a real customer cannot book. > Bot friction should slow down scripts. It should never stop a real customer from booking. #### Layer 4: the part that actually does the work The first three layers are friction. None of them stop a patient attacker, and that's fine, because the real defence is structural and non-blocking: a fresh signup can't harm us, because it isn't public yet. A brand-new org is inserted with published set to false, a quiet coming-soon state. The owner can set everything up and preview their page, but it only goes live once they've verified their email and connected a Stripe account. Bookatu takes 0% booking commission and tenants use their own Stripe, so funds go straight to their bank, not ours, and connecting Stripe is also a strong real-business signal. Pages auto-publish the moment Connect succeeds, so most owners never even see the toggle. On top of that, a new unverified org doesn't get dashboard access until the owner confirms their email; the guard redirects them to a verify page rather than locking the account. The confirmation link carries a signed, expiring token, so it's unguessable, tamper-evident and time-boxed. It gates publishing, not login, so a stale link can never lock anyone out. It just means not verified yet. The gate is also deliberately non-destructive. It was rolled out so that the people already running their business on us never get caught by it. That's the whole don't-punish-real-owners principle in one rule: we're not about to lock out a long-standing owner to catch spammers who signed up later. #### Why pure functions everywhere One pattern runs through all of this: the decision logic is pulled out into pure functions with no database and no network. The disposable-domain check, the captcha scoring decision, the publish eligibility, and the access gate are all plain functions that take their inputs and return a boolean. That's deliberate. Anti-fraud logic is exactly the code where a subtle off-by-one becomes we accidentally locked out every existing owner. Keeping the rules pure means each one is unit-tested in isolation against the cases that matter, and most of all against the cases where the right answer is to wave someone through. The side effects (the lookups, the scoring call, the redirect) live in thin wrappers around a tested core. #### What's next This setup is honest about its limits. A layered approach that leans towards letting people in lets some junk through by definition. We trade a few slipped signups for never blocking a real one. The bet is that the structural layer (hidden until verified and connected) carries the weight, so the noisier checks can stay lenient. The next things worth doing are watching the block logs to keep tuning where the scoring line sits, and adding rate-based signals so we can react to a burst of signups from one source without raising friction for everyone else. The principle won't change: friction for bots, an open door for the owner who just wants to take bookings. ### Recurring appointments and the 'admin force-book' rule How Bookatu books a standing recurring series through the same pipeline as one-off bookings, why admin scheduling force-books while customer booking stays strict, and the one collision the database still refuses. The Bookatu engineering team · 2026-06-18 · Architecture · https://bookatu.com/engineering/recurring-appointments-force-book · markdown: https://bookatu.com/engineering/recurring-appointments-force-book.md Standing recurring appointments sound trivial. The owner finishes a booking, the client says "same time every four weeks", and you stamp out the next six visits. The hard part is not the arithmetic. It is deciding who gets to override availability and who does not, and then making sure the one rule you never bend is enforced by something more reliable than a code path. We had a real bug here. An early version ran a strict availability pre-check on every occurrence before booking it. On a salon that hadn't finished setting up its working hours, every repeat got skipped as "out of hours". The owner had deliberately picked those times, and the system threw them all away. That bug forced us to be precise about a distinction we'd been hand-waving: availability is a gate for customers, but it's only guidance for an admin. > **The gist** > > - A recurring series books each visit through the same createBooking pipeline as everything else, tagged with source "admin". > - Customer bookings are strict: an unavailable slot is rejected. Admin bookings force-book, so working hours and days off are guidance, not a gate. > - The one thing nobody can override is a real double-book, caught by a partial unique index on (staff, start time) in Postgres. > - Force-booking lives in the application; the collision rule lives in the database. Different problems, different layers. #### One pipeline, a source argument There's exactly one function that creates a booking, and a recurring series is just a loop that calls it N times. We resisted writing a parallel bulk-insert path. A series occurrence is a real appointment. It needs the same customer matching, the same duration handling, the same row shape, the same side effects. Forking that logic would mean two places to keep in sync and two places to get subtly wrong. The whole behaviour difference is carried by one argument. createBooking takes a source, and that single value decides whether availability is a gate or a hint. ```ts export async function createBooking( input: CreateBookingInput, source: BookingSource = "online", // the strict, customer-facing default ): Promise ``` The recurring module passes "admin" for every occurrence, because an owner locking in a standing series is doing the same deliberate scheduling as someone dragging an appointment onto the calendar. The default is "online", the strict path the public booking page uses. The default matters: the safe, locked-down behaviour is what you get if you forget to think about it. #### Why customer booking stays strict Before writing anything, createBooking resolves the slot against the org's real availability: working hours, the staff member's roster, room or chair resources, existing appointments. For an online or magic-fill booking, a failed resolve ends the request. ```ts const slot = await resolveBookingSlot({ orgId, serviceId, durationMin, staffId, startAt, }); // Customer-facing claims must land on a still-open slot. if (!slot.ok && isCustomerFacing(source)) return { ok: false, error: slot.reason ?? "That time is no longer available" }; ``` This is non-negotiable for self-serve. A customer on the public site has no business placing themselves outside open hours, on a day the salon is closed, or on top of someone else's appointment. The strict reject is the only correct answer, and "that time is no longer available" is exactly what they should see. Magic Fill, a one-tap claim of a freed slot, is held to the same standard on purpose. If two people race for the same recovered slot, the loser gets a clean rejection rather than a silent double-book. #### Why admin scheduling force-books An admin is not a customer. When an owner sets up "every four weeks at 2pm", they're asserting a fact about their own calendar. They might be booking before they've finished entering their hours. They might run a regular Sunday slot for a loyal client even though Sunday isn't a published opening. Treating availability as a hard gate here means the system overrides the person who runs the business, which is backwards. So for the admin source, a failed slot resolve is not fatal. The booking proceeds. The recurring loop spells this out in a comment, and it's the heart of the whole thing: > Each occurrence force-books like the anchor appointment: availability (working hours, a day off) is guidance, not a gate, for an admin who is deliberately scheduling these times. Only a genuine same-(staff, instant) double-book is rejected by createBooking's unique slot index and reported as skipped. The same asymmetry shows up in rescheduleAppointment, which defaults to "online" and only relaxes for "admin". When an admin drags a booking on the 24-hour calendar grid, it can land outside open hours. A customer-initiated reschedule still has to find a real, open slot. ```ts // Admins (calendar drag) may place an appointment outside open hours; // customer-facing reschedules (the default) stay strict. if (!slot.ok && isCustomerFacing(source)) return { ok: false, error: slot.reason }; ``` There's a detail worth noting when the slot doesn't resolve. The resolver also assigns things like a free room or chair. When an admin force-books past a failed resolve, there's no resolver output to trust, so we keep the staff member the admin chose and drop the auto-assigned resource rather than invent one. Forcing the time does not mean fabricating the rest of the row. #### The one line nobody crosses: the unique index Force-booking opens an obvious hole. If admins can ignore availability, what stops two appointments for the same staff member at the same instant? The answer is not a check in the booking function. Checks lose races. The answer is a partial unique index in Postgres on (staff, start time), scoped to live (pending or confirmed) rows with a staff member set. This matters because the availability check and the insert are not atomic. Two bookings can both pass resolveBookingSlot, then both try to write the same slot. The database is the only place that can settle that, because it's the single point where both writes serialise. When the second insert violates the index, the driver throws, and we translate it into a friendly retry instead of a 500. ```ts try { // insert appointment + add-ons + wallet debit, in one transaction appointment = await db.transaction(async (tx) => { /* ... */ }); } catch (e) { // The partial unique index (staff + start time) rejected a colliding // booking that slipped through the availability check via a race. if (isUniqueViolation(e)) return { ok: false, error: "Sorry, that time was just taken. Please choose another." }; throw e; } ``` The recurring loop relies on exactly this. It does not pre-check each occurrence for clashes. It tries to book, and if createBooking comes back with an error (a real collision tripping the index), it records that occurrence as skipped with a reason and moves on. The owner sees "booked five, skipped one", can look at the overlap, and fix it. Force-booking and collision-rejection aren't in tension. They're two different rules living in two different layers, which is why both can be true at once. - Force-book versus strict is a business rule, so it lives in application code, keyed off source. - No real double-book is an invariant, so it lives in the schema as a constraint. - isUniqueViolation walks the error's cause chain because Drizzle wraps the driver error; trusting the top-level message would miss the 23505. - The same transaction protects the wallet debit and add-on inserts, since they share the booking transaction and roll back together. #### The few things we still won't force Force-booking is not a blank cheque. The recurring path still refuses to create a back-dated appointment: an occurrence that lands in the past is skipped, not booked. We also org-scope the staff member before persisting the series. A foreign-org staff id would create an "active" series whose every occurrence silently skips forever, because that staffer is never in this org's qualified set. That's a permanently stuck series that can never book, so we reject it up front with "staff member not found" rather than let it rot. There's also a deliberate billing decision baked in. Admin bookings skip deposits, so each occurrence is created confirmed with no payment. A recurring series never auto-charges and never touches Stripe. That fits how Bookatu works generally: 0% booking commission, tenants run their own Stripe, money lands in their bank, not ours. Materialising six future visits should not quietly create six payment intents. #### What's next Right now a series materialises its occurrences up front, in one batch. The schema already hints at where this goes. Each series row stores a nextDate marking where the visit after the current batch would fall, which is the hook for a future cron that extends a standing series instead of booking a fixed run. When we build that, the force-book rule and the unique index won't change. They already draw the line in the right place: be generous to the person running the business, and let the database be the one thing that never bends. ### Custom domains for every tenant with Vercel for Platforms How Bookatu lets each tenant point their own domain at their storefront: a flag-gated routing proxy, the Vercel Domains API behind a wrapper that never throws, and a TTL cache that keeps the common request free. The Bookatu engineering team · 2026-06-17 · updated 2026-11-15 · Infrastructure · https://bookatu.com/engineering/custom-domains-vercel-platforms · markdown: https://bookatu.com/engineering/custom-domains-vercel-platforms.md Bookatu is a multi-tenant booking platform. Every tenant gets a storefront at a slug like bookatu.com/aria-hair. That works, but a real business wants its own name on the door: ariahair.example.com, not someone else's domain with their slug bolted on the end. Pixieset does this for photographers, Shopify does it for shops, and our tenants kept asking for it. The catch is that the storefront is one Next.js app serving thousands of tenants. A per-tenant domain can't mean a per-tenant deploy. The other constraint was blast radius. The routing change runs on every matched request across the whole app. Get it wrong and we don't break custom domains, we break booking for everyone. So the feature had to be inert until we deliberately turned it on, and it had to cost nothing on the 99.9% of traffic that isn't a custom domain. This post walks through how that's wired in the code: a flag-gated proxy, the Vercel Domains API behind a wrapper that never throws, and a resolver cache that keeps the common case free. > **The gist** > > - One Next.js app serves every tenant. A proxy rewrites an inbound custom host onto that tenant's existing /{slug} storefront path. No per-tenant routes, no per-tenant deploys. > - The whole thing sits behind a feature flag. When off (the default), the first line of the proxy returns a pass-through before it even reads the Host header. > - The Vercel Domains API wrapper never throws and degrades to a not_configured status when the token is absent, so dev, CI and tests stay green. > - A cross-request TTL cache (positive and negative) means a custom-domain request hits the DB at most once a minute, and random Host headers can't amplify into DB load. #### The routing trick: rewrite, don't re-route The whole feature rests on one idea. The storefront already lives at app/[org]/(site)/**, served at /{slug}/.... A custom domain needs no new pages. It needs the inbound Host header turned into a slug, and the request rewritten onto the existing path. Next 16 renamed middleware.ts to proxy.ts, and that's where this happens. A rewrite, not a redirect, means the URL bar still shows the tenant's domain, and rewrites don't re-run the proxy, so there's no loop to guard against. ```ts // Flag OFF -> pass-through. No Host read, no DB, zero routing change. if (!customDomainsEnabled) return NextResponse.next(); // Platform / preview / local hosts -> fast-path, no DB cost. const host = (req.headers.get("host") || "").split(":")[0].toLowerCase(); if (!host || isPlatformHost(host)) return NextResponse.next(); // Resolve the custom host to an org slug. Only 'active' domains resolve. const slug = await getOrgByCustomDomain(host); if (!slug) return NextResponse.next(); // (admin guard + double-prefix guard omitted here; see prose) // Internal rewrite onto the existing storefront tree. const path = pathname === "/" ? "" : pathname; const url = req.nextUrl.clone(); url.pathname = `/${slug}${path}`; return NextResponse.rewrite(url); ``` The ordering matters. The flag check is the first statement, so when the feature is off the proxy reads nothing and queries nothing. The matcher excludes /api, Next internals and any path with a dot (static assets), and even on matched paths the in-body flag check makes it a no-op. Two guards sit between the resolve and the rewrite. Custom domains serve the public storefront only, so an /admin request arriving on a custom host is redirected to the platform origin rather than rewritten, and the admin panel never gets served under a tenant's domain. A second guard skips the rewrite when the path is already prefixed with the slug, so there's no chance of double-prefixing. #### Why a flag, and why default off The flag is defined once and imported everywhere it matters: the proxy, the admin section, and the connect actions. That single idiom is deliberate. When it's off, the proxy is a pass-through, the settings section is hidden, and the server actions refuse early. Until the feature is deliberately enabled it is fully inert. There's no half-on state where the UI shows up but routing doesn't work, or routing runs but nothing can be connected. Shipping a high-blast-radius feature dark, then enabling it as a separate, deliberate step, means the risky code lands and gets reviewed in isolation, well before it starts handling live traffic. And if enabling it causes trouble, stepping back is just as contained. #### Talking to Vercel without letting it break a request Attaching a domain to the project, checking its status, verifying ownership, and detaching it all go through Vercel's Domains API. We call it with a raw fetch: no SDK, no new dependency. The wrapper reads a deploy token scoped to the project from the environment. If that config is absent, the helper returns null and every exported call short-circuits to a not_configured status instead of attempting a request. That's what keeps dev, CI and tests green without a Vercel token, and it means a missing token can never break a live request. Every call also wraps its fetch in try/catch and returns a typed result object on failure. None of them throw. The status machine that decides whether a domain is servable is a pure function, unit-tested in isolation, and it combines two distinct Vercel concepts that are easy to conflate: - verified is project-domain ownership: has the TXT challenge been satisfied? This is the apex or www the tenant proves they control. - misconfigured is DNS and certificate: are the A/CNAME records pointing at us and is the cert issued? - A domain is only active (and therefore served) once both are good. Anything else is pending, verifying or error, and the proxy never serves it. ```ts export function customDomainStatusFor(input: { verified: boolean; misconfigured: boolean; }): CustomDomainStatus { if (!input.verified) return "pending"; if (input.misconfigured) return "verifying"; return "active"; } ``` One detail worth flagging for anyone copying this: don't hard-code the DNS records you tell the tenant to add. Vercel returns the recommended A and CNAME values from its config endpoint, and the shape varies (a bare string, a string array, or an array of objects). We pull the first usable value out of whatever comes back and show that, with no IP or CNAME fallback baked in. Hard-coded DNS targets rot the moment the platform changes them. #### Keeping the common case free The resolver is the one piece on the hot path. isPlatformHost is a cheap string check that fast-paths bookatu.com, *.bookatu.com, *.vercel.app, localhost, 127.* and an empty host straight to next() with no DB cost. Only a genuinely unknown host reaches getOrgByCustomDomain, which looks the host up in the custom_domains table and returns the owning org's slug, but only when that domain's status is active. React's cache() only dedupes within a single request, which is useless here because the proxy runs per request. So the resolver keeps a module-level TTL cache with a 60-second lifetime that stores misses as well as hits. The negative caching is the part that earns its keep. Without it, someone could spray random Host headers and turn each one into a DB query. With it, an unknown host is looked up once and then served from cache as a miss until the TTL expires. The lookup also never throws: any DB error resolves to null, and the proxy falls through to a normal response. ```ts const RESOLVER_TTL_MS = 60_000; const resolverCache = new Map(); export async function getOrgByCustomDomain(host: string): Promise { const key = (host || "").trim().toLowerCase(); if (!key) return null; const hit = resolverCache.get(key); if (hit && hit.expires > Date.now()) return hit.slug; // hit OR cached miss // ... DB lookup joining custom_domains -> organizations, status = 'active' } ``` When a tenant connects or removes a domain, the admin action invalidates that host in the cache, so a just-changed domain starts (or stops) being served without waiting out the TTL. #### One tenant, many domains The first cut stored a single custom_domain column on the organizations row. That column is now deprecated. Real businesses legitimately want a few hosts pointing at the same storefront: a .co.nz, a .com, and maybe a redirect alias. So domains moved to their own custom_domains table, with one org owning many rows, all resolving to the same storefront. There's a cap of five per org, generous for a small business without inviting abuse of the global domain namespace or unbounded attach calls to Vercel. Two guards protect that table. A global, case-insensitive unique index on lower(domain) means a domain belongs to exactly one org across the whole platform, which is the real cross-org collision guard. The per-org cap is enforced under a per-org transaction advisory lock, so two concurrent adds can't both slip past it (the unique index only stops identical domains, not two distinct ones that would both push an org over the limit). If a concurrent add fills the last slot after we've already attached on Vercel, we detach to avoid an orphan attachment and report the cap. The lock is keyed to the org, so it never blocks other tenants. Entitlement stays per-org and lives in one pure function. A custom domain is included on Pro and Scale, and is not part of Solo or Studio. The connect action re-checks entitlement and owner/admin access server-side, so the client is never trusted. Pricing here is the same as everywhere on the platform: it's about your plan and your active clients over the last 90 days, not per-seat and not a cut of bookings. Bookatu takes 0% booking commission, and deposits flow to the tenant's own Stripe account, not ours. #### What's next The honest status: the code is in, validated, and still behind its flag. There's a deprecated single column plus its index waiting on a cleanup migration once nothing reads them. If I were starting again I'd build the multi-domain table first instead of the single column. The one-to-one model felt simpler at design time and turned into a migration I now have to schedule. The pattern travels well beyond booking. If you run one app for many tenants on Vercel, the same three pieces (a flag-gated rewrite proxy, a Vercel API wrapper that never throws, and a TTL-cached host resolver) get you custom domains without per-tenant infrastructure. The discipline that made it safe wasn't clever code. It was defaulting the flag off and making sure the unhappy path, a missing token or a flaky DB, always resolves to a normal response instead of an error. ### Pricing by active clients: computing who actually counts How Bookatu bills by active clients instead of seats: a 90-day window, a deliberately plain in-memory de-dupe across two activity sources, and a clean split between lifecycle and counting. The Bookatu engineering team · 2026-06-16 · Architecture · https://bookatu.com/engineering/pricing-by-active-clients · markdown: https://bookatu.com/engineering/pricing-by-active-clients.md Most booking software charges per seat. You add a stylist, a trainer, a second front-desk login, and the bill goes up. It's easy to meter and easy to reason about, but it punishes exactly the wrong thing: hiring. A small studio that takes on a part-time helper shouldn't pay more for the privilege. Bookatu charges by active clients instead. Staff, services and calendars are unlimited on every plan, and we take 0% booking commission. The only number that moves your bill is how many real people you served recently. That framing is friendlier, but it pushes a hard question onto the engineering side: who, precisely, counts? A name in a CRM isn't a customer you're serving. A client who cancelled isn't either. Someone who both books a haircut and logs a workout is one person, not two. This post is about turning that fuzzy intent into a number we can defend on an invoice. > **The gist** > > - Bill by active clients (booked or trained in the last 90 days), never per seat. > - An active client is a distinct customer id, de-duped across two activity sources in memory. > - Cancelled appointments are excluded; quiet clients on your list never count. > - Lifecycle (trial/grace/paused) is computed without the count, so hot paths stay DB-free. #### Defining "active" in one sentence, then in code The product definition lives as a string next to the pricing logic, because the marketing page, the FAQ and the billing math all have to agree on it: ```ts export const ACTIVE_CLIENT_EXPLAINER = "An active client is someone who booked or trained with you in the last 90 days. Quiet clients on your list never count, so you only pay for the people you are actually serving."; ``` Two knobs back it. The window is a single 90-day constant, kept separate from the 60-day free trial so either can change without the other. "Booked or trained" maps to two concrete activity sources: a non-cancelled appointment, or a workout logged against a client program. That second source matters because Bookatu isn't only salons. Trainers and clinics drive value through programs, not just the calendar. #### Counting distinct people, not rows The naive version is a COUNT over appointments in the window. That's wrong twice over. It counts a regular who came in five times as five, and it ignores anyone whose only recent activity was a workout log. The value metric is people, so the unit has to be a distinct customer id pulled from both sources and merged. ```ts const since = new Date(now.getTime() - WINDOW_DAYS * 86_400_000); const [booked, trained] = await Promise.all([ db.select({ customerId: appointments.customerId }) .from(appointments) .where(and( eq(appointments.orgId, orgId), ne(appointments.status, "cancelled"), // a cancelled visit is not a served client gte(appointments.startAt, since), )), db.select({ customerId: clientPrograms.customerId }) .from(programLogs) .innerJoin(clientPrograms, eq(programLogs.clientProgramId, clientPrograms.id)) .where(and(eq(programLogs.orgId, orgId), gte(programLogs.createdAt, since))), ]); const active = new Set(); for (const r of booked) active.add(r.customerId); for (const r of trained) active.add(r.customerId); return active.size; ``` The Set does the real work. Someone who both booked and trained appears in both result arrays and collapses to one id, so they're never billed twice. The ne(status, "cancelled") filter is the other decision that carries weight: a cancellation isn't a service you delivered, so it shouldn't push a tenant towards a bigger plan. #### Why the de-dupe is in memory, on purpose You could ask the database to do all of this with COUNT(DISTINCT ...) over a UNION of the two sources, and it would be a perfectly good query. We didn't, and the reason is the kind of boring you want from infrastructure: tests run against pglite, production runs against postgres-js. Pushing the de-dupe into SQL means trusting two different engines to agree on DISTINCT semantics across a UNION. Pulling the ids out and folding them into a JavaScript Set makes the merge identical everywhere. The driver only has to return rows. The counting logic has exactly one implementation. There's a second version of the function for the billing cron, countActiveClientsByOrg, which drops the per-org filter, fetches every tenant's activity in two queries, and buckets ids into a Map>. Same idea, batched. Orgs with no activity in the window never appear in the map, which the callers read as zero. No row per idle tenant, no special-casing. #### Keeping the count off the hot path Here's the part that's easy to get wrong. The billing lifecycle (are you in trial, in grace, or paused?) feels like it should depend on your client count. It doesn't, and conflating the two would put a COUNT query on every page load. The pure decision function takes the count as just one input: ```ts export function evaluateAccess(input: { trialEndsAt: Date | null; subscriptionActive: boolean; activeClients: number; now: Date; }): AccessState { /* ... */ } ``` The phase, the paused flag and the day counters fall out of the trial date and subscription status alone. The active-client count only decides the requiredTier, the plan we suggest. So the gate that runs on every admin page and every public booking page uses a lite path that passes activeClients: 0 and never touches the database for a count. Only the billing page, which actually renders "X active clients," pays for the real query through getOrgAccess. One screen needs the number and does the work; the rest of the app doesn't. Mapping a count to a price is then trivial and testable in isolation. tierForClients walks the tiers cheapest-first and returns the first one whose cap fits, or the uncapped top tier: ```ts // solo <= 20, studio <= 75, pro <= 250, scale = unlimited export function tierForClients(activeClients: number): Tier { return TIERS.find((t) => t.maxClients == null || activeClients <= t.maxClients) ?? TIERS[TIERS.length - 1]; } ``` #### What the count is allowed to do, and what it isn't A pricing-by-usage system invites an obvious failure mode: silently upgrading someone the moment they cross a threshold. We don't. The daily cron computes everyone's count, snapshots where each tenant sits in the lifecycle, and, behind a feature flag, can email an owner a consent-based "set up billing" nudge. It never charges a card and never moves a plan on its own. The flag is checked twice on that path, so with it off no email goes out and no dedupe row is reserved. Crossing into a bigger tier is something a human agrees to, not something Set.size triggers at 2am. It matters that the money side stays just as restrained: tenants connect their own Stripe account, so payments land in their bank, not ours, and we never reach for a card we weren't given. > You only pay more as you serve more clients. Quiet clients on your list never count. It's worth being honest about the gap, too. The count function isn't covered by its own unit test yet. The tiers, the tier selection and the access state machine all are, but the two-source merge currently rests on the de-dupe being simple enough to read. That's a fair trade for now, because the logic is one Set and two filters, but it's the first thing I'd lock down before changing what counts as activity. #### What's next The shape holds up well. Adding a third activity source (say, a paid deposit with no appointment yet) is one more select and a few more active.add calls, with the Set absorbing any overlap for free. The more interesting work is at the edges of the window. A tenant watching a client age out of the 90 days and drop their count by one wants to know why, so surfacing a per-client "last counted" date is worth more than any clever query. The number on the invoice is only trustworthy if a salon owner can reconstruct it by hand, and that, more than the SQL, is the real design constraint. ### Testing a booking engine with pglite and 1600+ tests How Bookatu tests its booking engine against a real in-memory Postgres: actual migrations, partial unique indexes that catch double-bookings, and 1600+ tests that run anywhere. The Bookatu engineering team · 2026-06-15 · Reliability · https://bookatu.com/engineering/testing-a-booking-engine · markdown: https://bookatu.com/engineering/testing-a-booking-engine.md A booking engine is mostly a database problem wearing a calendar costume. Two clients must never hold the same slot with the same stylist. A standing weekly series must land on the right instants without re-booking the anchor. One salon must never see another salon's customers. Almost every one of those rules is enforced by Postgres itself: a partial unique index, an org-scoped WHERE clause, a constraint. So the question for our test suite was simple. How do you test code whose correctness lives in the database, without mocking the database away and testing nothing? Our answer is to run a real Postgres for every test. Not a shared dev database, not a Docker container the CI runner waits on, and not a hand-rolled fake. We run pglite, which is Postgres compiled to WebAssembly, in-memory, in the same Node process as the test. We point Drizzle at it, replay our actual migration SQL, and let the same query code that runs in production run against it. There are now more than 1600 tests built this way, and about 80 integration files spin up their own database. > **The gist** > > - Tests run against pglite (real Postgres in WASM), in-memory, in the test process. No Docker, no shared DB. > - Each suite replays the real numbered migration SQL files, so the schema under test is the schema we ship. > - A partial unique index does the double-booking enforcement, and the tests prove it does, not a mock. > - Most bugs come back as a test first, with the real-world report written into the comment above it. #### Why a real Postgres instead of mocks The interesting bugs in a booking system are not in the TypeScript. They are at the boundary. Does the partial unique index actually reject the second booking when the status is 'confirmed'? Does an org-scoped query genuinely return nothing for the wrong tenant, or does it quietly leak? You cannot answer either of those by mocking the database client, because the behaviour you care about is the database's behaviour. A mock just returns whatever you told it to, so it tests your assumptions rather than the system. pglite gets us the real thing cheaply. It is the Postgres query planner and executor, partial indexes and all, running in WASM with no network and no daemon. A fresh database costs almost nothing, so we can afford one per file, and a fresh org per test where a suite wants full isolation. The trade-off is honest. pglite is single-connection and not byte-for-byte identical to a managed Postgres for every extension. But for schema, constraints, indexes, and standard SQL, which is where our correctness lives, it is the same engine. #### Replaying the real migrations The setup is deliberately dumb, and that is the point. We do not maintain a separate test schema. Every suite reads the same numbered migration files we apply in production, in order, and executes them against a fresh pglite instance. If a migration is wrong, the tests run against the wrong schema and fail, which is exactly what we want. ```ts beforeAll(async () => { const client = new PGlite(); const dir = path.resolve(process.cwd(), MIGRATIONS_DIR); const files = fs.readdirSync(dir).filter((f) => f.endsWith(".sql")).sort(); for (const f of files) { await client.exec(fs.readFileSync(path.join(dir, f), "utf8")); } tdb = drizzle(client, { schema }); }); ``` That sorted readdir is load-bearing. Migrations are numbered (0000, 0001, and so on), so a lexical sort replays them in the order they were authored. The result is a database whose schema is, by construction, the schema we ship. When we added galleries or per-service video meetings, the new migration just appeared in the folder and every suite picked it up for free. #### Pointing the app's db at the test database Our application code imports a shared db instance from one module. We do not want the tests to reach the database through a different code path, because then we would be testing a different program. So instead of refactoring every function to accept an injected client, we redirect that shared module at the in-memory instance. Vitest needs the mock hoisted above the imports, so we use a tiny holder. ```ts const h = vi.hoisted(() => { let d: unknown = null; return { get: () => d, set: (x) => { d = x; } }; }); vi.mock("@/db", () => ({ get db() { return h.get(); } })); // the shared db module // later, in beforeAll: h.set(tdb); ``` The getter matters. The mock exposes db as a property that reads from the holder at access time, so the module can be imported before the database exists and still resolve to the live instance once beforeAll has run. From there, createBooking, getAvailability and the rest run unmodified. The only thing that changed is which Postgres they talk to. #### Testing the rules that live in SQL The double-booking guard is a good example of why this approach earns its keep. There is no application-level lock and no read-then-write check that hopes to win a race. The rule is a partial unique index: ```sql -- conceptual: names simplified for illustration CREATE UNIQUE INDEX "one_booking_per_staff_slot" ON "appointments" ("staff_id", "start_at") WHERE status IN ('pending','confirmed') AND staff_id IS NOT NULL; ``` Because the WHERE clause only covers live bookings, a cancelled appointment frees the slot automatically, and two clients can never both hold the same (staff, instant). The tests do not assert that we 'called the check'. They book a slot, try to book it again, and assert the second is rejected, with the real index doing the rejecting. A sibling index does the same for a shared room or resource. If someone weakened either WHERE clause in a migration, the conflict tests would go red immediately. Multi-tenant isolation gets the same treatment. We seed two orgs, then prove that loading a customer by her real id but scoped to the other org returns nothing. It is a three-line test, but it is a real query against a real database, which is the only version of that test worth having. ```ts const leaked = await db .select() .from(schema.customers) .where(and(eq(schema.customers.id, alice.id), eq(schema.customers.orgId, orgB.id))); expect(leaked).toHaveLength(0); ``` #### Bugs come back as a test, with the story attached Most of these tests started life as a bug report. We write the failing case first, fix it, and leave the real-world story in a comment so the next person knows why the test exists. The reschedule suite is a clear one. An admin dragging a booking onto another stylist's lane got 'Time no longer available'. The cause was that the admin action called the reschedule function without a source, so it took the strict customer-facing path and rejected any slot the engine deemed busy or out of hours. A deliberate admin move should force-book. Only a genuine same-(staff, instant) double-book may block it. > The bug: dragging a booking to another staff member's lane came back 'Time no longer available'. The fix: pass 'admin' so the move force-books like the calendar drag, blocking only a genuine same-(staff, instant) double-book. The test then pins both halves at once. The admin action force-moves a booking to 06:00, before the 9am default open, and succeeds, while the same move on the default 'online' source still fails. That second assertion is the important one. It is easy to fix a bug by loosening a rule everywhere. Pinning the strict path in the same test stops the fix from quietly handing the admin bypass to the public. The recurring-series tests follow the same shape. A standing weekly series must force-book each occurrence like its anchor, even out of hours on a not-yet-configured org, yet still skip an occurrence whose exact slot is already taken and report it in skippedCount. Both behaviours sit in one file, each with the scenario that motivated it written above the assertions. #### Keeping behaviour stable while refactoring Not every test asserts a single rule. The availability engine is dense (multi-staff, org-wide blocks, back-to-back bookings, cross-midnight windows, processing-time gaps, resource pools, non-UTC timezones), and we wanted to refactor it without changing what it returns. So there is a characterization test. It runs getAvailability across a representative sweep of those scenarios and snapshots the output, with the clock and the date window pinned so the result is deterministic. The snapshot is the behaviour contract. The refactor has to keep it byte-identical or explain why it changed. This is a different use of the same setup. The unit-rule tests say 'this specific thing must be true'. The characterization test says 'whatever this currently does, keep doing it until you decide otherwise'. Both run against the real schema, so both stay honest as the database evolves. #### What it costs, and what is next The honest downsides. pglite is single-connection, so it cannot reproduce a true OS-level parallel write race. We do fire two bookings at the same slot with Promise.all and assert exactly one wins, but pglite serialises those calls, so what the test really proves is that the unique index rejects the duplicate, not that two parallel transactions race cleanly. For our shape that is the right thing to lean on: make the race structurally impossible at the index rather than hammer for it. It is still a real limitation worth naming. There is also a small per-file cost to standing up a database and replaying every migration, which grows as the migration list grows. So far it sits comfortably inside our 30-second per-test timeout, and the payoff is worth it: no Docker, no shared state, and it runs identically on a laptop and in CI. The next step is squeezing the setup cost. Replaying all migrations per file is simple and correct, but as the schema grows we will likely cache a migrated database snapshot and clone it per suite. The principle will not change. Tests run against the same Postgres and the same migrations we ship, because the bugs that matter in a booking engine are the ones only the database can catch. ### Per-language URLs for SEO via a proxy rewrite Cookie-based localisation is invisible to Googlebot, so it only ever indexed our English pages. Here's how we made 14 languages crawlable with a flag-gated proxy rewrite and zero new routes. The Bookatu engineering team · 2026-06-14 · Internationalization · https://bookatu.com/engineering/per-language-urls-for-seo · markdown: https://bookatu.com/engineering/per-language-urls-for-seo.md Bookatu's marketing pages already spoke 14 languages. A visitor from Berlin saw German, a visitor from Lisbon saw Portuguese. We picked the language from a cookie the visitor set with a toggle, or fell back to their country from a geo header. That worked well for humans and did nothing for search. The trouble is that Googlebot is not a normal visitor. It carries no cookie, and it crawls from the US, so our geo detection hands it English every single time. Every localised page we rendered collapsed into the same English URL in the index. We were translating content nobody could find. The fix is well understood in theory (give each language its own URL), but the interesting part was doing it without forking our route tree, without breaking a single existing English URL, and behind a flag we could turn off instantly if it misbehaved. > **The gist** > > - Cookie and geo localisation is invisible to crawlers, so only English ever got indexed. > - Non-English languages get a / URL prefix; English stays unprefixed, so no existing URL changes. > - A proxy rewrite maps /de/pricing back to the canonical /pricing page and passes the locale via a request header, not a new route. > - The whole thing is gated on a build-time flag, so 'off' is byte-for-byte the old behaviour. #### English unprefixed, the rest prefixed The first decision was the URL shape. The common pattern is /[locale] for everyone, including /en. We rejected that because it would 301 every English URL we already have, throw away the ranking those URLs have built up, and force a redirect on our highest-traffic pages. English is the default and the fallback everywhere else in the system, so it keeps its bare URLs. The other 13 languages each get a / prefix. ```ts export function localizedPath(canonicalPath: string, locale: SupportedLocale): string { if (locale === "en") return canonicalPath || "/"; const p = canonicalPath === "/" ? "" : canonicalPath; return `/${locale}${p}`; } // localizedPath("/pricing", "en") -> "/pricing" // localizedPath("/pricing", "de") -> "/de/pricing" // localizedPath("/", "de") -> "/de" ``` The language list is the source of truth. Prefixes are derived from it by filtering out English, so adding a fifteenth language is a one-line change to the names map and the URL scheme follows for free. #### Only some paths are eligible Bookatu is multi-tenant. Tenant storefronts live at /[org], so /de could just as easily be an org whose slug happens to be 'de'. Admin lives at /admin, the API at /api. None of those should ever be read as a language prefix. So the split is deliberately narrow: a leading segment counts as a locale only when the next segment is a known marketing root. ```ts const LOCALIZED_ROOTS = new Set([ "", "pricing", "discover", "blog", "help", "faq", "developers", "compare", ]); export function splitLocalePath(pathname: string) { const parts = pathname.split("/"); // ["", "de", "pricing"] const first = parts[1] ?? ""; if (isLocalePrefix(first) && LOCALIZED_ROOTS.has(parts[2] ?? "")) { const rest = "/" + parts.slice(2).join("/"); return { locale: first, path: rest === "/" ? "/" : rest.replace(/\/+$/, "") }; } return { locale: "en", path: pathname }; // untouched } ``` So /de/pricing splits to { locale: 'de', path: '/pricing' }, and /de/some-org splits to { locale: 'en', path: '/de/some-org' } and passes through unchanged. The empty string is in the set so /de (the localised home page) resolves to /. An org slug that collides with a two-letter language code is never shadowed, because the segment after it won't be a marketing root. #### The rewrite lives in the proxy Next 16 renamed middleware.ts to proxy.ts, and it always runs on the Node.js runtime. Our proxy already handled custom domains, so the locale routing slots in as the very first block. When a request comes in for a prefixed marketing path, we rewrite the URL back to its canonical form and hand the locale to the page through a request header. A rewrite, not a redirect, so the prefixed URL stays in the address bar and in the index. Rewrites don't re-invoke the proxy, so there's no loop to guard against. ```ts if (localeUrlsEnabled) { const { locale, path } = splitLocalePath(req.nextUrl.pathname); if (locale !== "en" && path !== req.nextUrl.pathname) { const requestHeaders = new Headers(req.headers); requestHeaders.set(localeHeaderName, locale); const url = req.nextUrl.clone(); url.pathname = path; const res = NextResponse.rewrite(url, { request: { headers: requestHeaders } }); res.cookies.set(localeCookieName, locale, { path: "/", maxAge: 60 * 60 * 24 * 365, sameSite: "lax" }); return res; } } ``` Two things happen besides the rewrite. We set an internal locale request header so the page knows which language to render, and we pin the locale cookie. The cookie matters for what comes next. Once you've landed on a German page, the in-page nav links point at unprefixed canonical paths (the nav doesn't rewrite every href), so without the cookie your next click would silently drop you back to English. Pinning it keeps in-language navigation in language. On the server side, the header wins over everything. The resolver checks the URL-derived header first, then the cookie, then geo, then Accept-Language, then English. The header is the strongest signal precisely because it's the one a crawler can act on without state. ```ts const fromPath = h.get(localeHeaderName); if (fromPath) return normalizeLocale(fromPath); // URL beats cookie beats geo const pinned = (await cookies()).get(localeCookieName)?.value; if (pinned) return normalizeLocale(pinned); // ...geo, then Accept-Language, then "en" ``` #### Telling search engines which page is which Distinct URLs are only half of it. Without hreflang, Google sees a dozen near-identical pages and may pick the wrong one for the wrong region, or treat them as duplicates. So each localised page emits a self-referencing canonical plus the full set of language alternates, including x-default pointing at English. ```ts export function localeAlternates(base: string, canonicalPath: string, currentLocale = "en") { const languages = { "x-default": `${base}${localizedPath(canonicalPath, "en")}` }; for (const code of Object.keys(LOCALE_NAMES)) languages[code] = `${base}${localizedPath(canonicalPath, code)}`; return { canonical: `${base}${localizedPath(canonicalPath, currentLocale)}`, languages }; } ``` A page feeds its own resolved locale in as currentLocale, so /de/pricing canonicals to itself and not to the English page. The pricing page wires this straight into Next's metadata as alternates: { canonical, languages }. The sitemap does the same, but with one honest restriction: it declares hreflang alternates only for paths whose bodies are actually translated today (home, FAQ, pricing). Advertising a /de/blog that still renders English would be lying to the crawler, and Google drops hreflang clusters where the return tags don't line up. #### Flag-gated, so 'off' is exactly the old behaviour Everything above hangs off one build-time flag, wired so the proxy and the client toggle agree at build time. When it's off, the proxy block is skipped entirely (the routing is byte-for-byte what it was), the sitemap emits no alternates, and the language toggle falls back to its old job of just setting the cookie and refreshing. When it's on, the toggle navigates to the prefixed URL instead, so the address bar reflects the language and the page is shareable. > The flag isn't a feature toggle so much as a blast-radius control. The proxy runs on every matched request, so 'instantly revertible' was a hard requirement, not a nicety. We leaned on this gate because the proxy sits in the hot path. The matcher already excludes /api, Next internals, and anything with a dot in it, and the locale block only acts on a non-English prefix followed by a known root. But a routing bug here would hit every page, so being able to flip back to a pure pass-through with one env var was worth more than any elegance. #### What's next The plumbing is done and live behind the flag: URLs, rewrites, canonicals, hreflang, sitemap, and a toggle that navigates. The honest gap is content. Right now only the home page, pricing, and FAQ have fully translated bodies, which is why the sitemap only advertises alternates for those three. The next round of work is unglamorous: translate the remaining marketing bodies and add each path to the localised set as it lands, so the hreflang clusters grow to match what we actually serve. The architecture was the interesting part. Filling it in is just typing.