48 hours or 24. A fee, a credit, or nothing. Card on file so a late cancellation costs what you said it would, without an awkward Venmo request.
48 hours, 24, or none. Changes inside it are locked or fee'd, your choice.
Charge a percentage, keep it as credit, or let it go. A closed list, so a typo can't become the other one.
"Studio massages take a $50 deposit. Mobile pays in full."
A client override beats a service policy beats the studio default, field by field.
"Why is this one asking for a card?" "Because Deep Tissue says so."
Deposits, card-on-file, approval and cancellation handling existed in most software, but only studio-wide. Owners wanted to mix them: the deposit from the service, the card requirement from the studio. Palm resolves field by field, most specific wins, null means inherit.
The default everything inherits from.
Couples take a deposit; a consult doesn't.
A long-standing regular skips the deposit; someone with two no-shows prepays in full.

Money is where getting it wrong is discovered by a client at the till rather than seen and undone on a screen. So the policy fields are typed and closed, and Palm reads back every one before it's saved.
Every resolved value carries where it came from.
Nothing changes for anyone until you write an override.
Yes. Deposits, card-on-file, approval, and the cancel window are all per service if you want them to be.
Whatever you chose: a fee, credit kept for next time, or nothing. Stated in the reminder so it's not a surprise.
Yes, per client.
Yes. Same policy table.
Finally, a scheduler that runs your calendar the way you would.
Start free for 30 days