When a slot opens, Palm offers it to the people waiting for that day and service, a few at a time, first to reply wins. Then it writes down who was asked and why.
The moment a slot opens, Palm offers it to the people waiting for that day and service.
Offers go to the front of the line, not a blast to everyone. First to reply wins; the rest are told.
Rides the same delivery as reminders, so it honours your sending switch and your voice.
Who was asked, in what order, who said yes. In the activity log.
Clients join from the booking page; you add them from the calendar or by asking.
Maria cancels Thursday 3:00. Palm looks at who wanted Thursday afternoons with Marco, texts the first, waits, texts the next.
"A 3:00 with Marco just opened Thursday. Want it?"
First yes books it; the slot is gone for everyone else, and they're told so.
If Kim moves from next Tuesday to Thursday, next Tuesday is open again. Palm asks whether to offer it.
Priorities. Today the list is in order of who asked first. "Members first" is the next thing to build, and it's a sentence, not a setting.
Members, then regulars, then everyone else. On the build list.
Someone waiting for exactly a 90-minute deep tissue before someone waiting for anything. On the build list.
A handful, in order. Never everyone.
Yes, from the booking page when their time isn't available.
The slot stays open on the booking page like any other, and the log says who was asked.
Not yet. It's on the build list; say it and it's logged.
Finally, a scheduler that runs your calendar the way you would.
Start free for 30 days