Appearance
Repeat appointments and a waitlist for a salon in Laravel
A regular comes every four weeks, Thursdays at ten, always to Mira. At the end of each visit the desk books the next one, and only the next one: the fifth is forgotten, the Thursday fills up, and the regular goes elsewhere. Meanwhile Saturday is full a week ahead. A client who wanted it gives up; on Friday night someone cancels, and the hour stays empty because nobody knew who wanted it.
Fresha, Booksy and Vagaro all have an answer for both: repeat appointments and a waitlist. kitloom/bookings has them now, on a Laravel site with the salon's own data, and an AI agent can do both for the desk.
Ask the agent
With kitloom/ai connected, an agent whose user manages the bookings books the series and works the list:
- "Book Nora's cut every four weeks until the end of March." (
bookings_— it shows the dates first, a taken one at the nearest free time that day, and books only when you say so)repeat - "Nora is moving away. Cancel the rest of her visits and thank her." (
bookings_— the visit and every later one, one email)series_ end - "Who is waiting for Saturday?" and "Put Ruth on the list for a blow-dry any morning next week; her number is 204 555 0199." (
bookings_— list, add, end)waitlist
Repeat appointments
On the calendar, a visit's panel has Repeat. It asks for a rhythm — every one to twelve weeks — and either how many visits after this one, or the date of the last. Before anything is booked it lists every date it would book:
- a date that is free, at the same time with the same staff member;
- a date whose time is taken, at the nearest free time that day, and the line says so (Mon 11 Jan, 09:00 — 10:00 is taken);
- a day with nothing free at all, named under the list.
Untick the week the client is away and press Book these visits. They are ordinary bookings: the calendar, the reminders, the till and the client's account treat them as any visit. Ten o'clock stays ten o'clock when the clocks change. The client gets one email with every date, its link to change or cancel it, and one calendar file with all of them; the staff member gets one too. Nobody gets an email per visit.
A visit of a series is marked ↻ on the calendar, and its panel says where it stands: 2 of 6, every 4 weeks. When the regular stops coming, Cancel asks which visits: this one, or this visit and all after it — told in one email.
A waitlist
Switch it on in Bookings → Settings → Waitlist, with how many days ahead a wish may reach. The booking page then says Tell me if a time frees up under the free times, and a client leaves a wish: the services, a stylist or anyone, the days, and the part of the day — morning, afternoon, evening or any time.
When a booking is cancelled, declined, let go unpaid or moved, the freed time goes at once to everyone whose wish it fits: an email, a text where the salon texts, a push in the salon's app. The message opens a page with the time, and one tap books it. The first to book has it; nothing is held, so the gap fills as fast as someone wants it, and a client is told again only after an hour, so a busy day does not flood a phone. A booking that covers the wish ends it.
The desk sees it all. Bookings → Waitlist lists the wishes, who, what, with whom, the days and where each stands; Add to the waitlist puts a client who called on it (a phone is enough), Book puts a wish on a free time of its days, Take off the list ends one. On the calendar, a day with wishes says so — 2 waiting for this day — and the badge opens the list on that day. Clients see their open wishes on their account page and may leave them.
Moving from another booking system
A salon with years of clients in Fresha, Booksy, Square or Vagaro brings them along: their export, CSV or Excel, goes into Bookings → Clients → Import / Export. The columns are matched by the names these systems use (Mobile phone, Client notes, Accepts marketing, Birthday), a client the salon has already only gets what their card lacks, and the same file brought in twice doubles nobody. The guide says where each system keeps its export.
For a Laravel developer
Both are tables of the module's own, booking_ and booking_ with booking_, on Eloquent models the application can swap through the Model. A series is planned by Series and written by Series, which books each visit through the same Booking as any booking, under its lock; its visits announce themselves with Booking, so whoever tells people — an email, a push, the owner's notice — hears Series once instead, and whoever keeps records — a Google Calendar, a Zoom meeting, a webhook — does as for any booking. A freed time is heard by Waitlist\ from the bookings' own events and offered from the queue after the commit; the offer is Events\, so a module of your own can send it another way. It comes with both admins, Filament and Nova, and the REST routes bookings/ for a theme or an app.
Watch it
Try it
Both come with kitloom/bookings, for either admin:
bash
composer require kitloom/bookings kitloom/bookings-filament
php artisan migrateOn a Nova site, the second package is kitloom/. Open a sandbox in one click, with no sign-up: Filament or Nova. Every detail — the limits, the texts, the agent's tools, the routes — is in the Bookings guide.