Home/Running the studio/Activity log & "why?"
Every decision, with the rule behind it

Every automatic action, with the rule that caused it.

Palm filled Maria's cancelled 3:00. Who did it ask, in what order, who said yes, and which rule decided the order. Ask "why is 2:00 hidden?" and get a real answer.

Activity log &
What it does

Activity log & "why?", in detail.

What Palm did

Filled a slot, texted a reminder, refused a booking, and the rule that caused it.

What it asked first

Everything you approved, with what you approved.

Why?

"Why is 2:00 hidden?" "It would be Ashley's third deep tissue in a row."

Versioned rules

Every rule change kept; roll back any of them.

The asks log

Everything you asked for that Palm couldn't do yet. That's the roadmap.

Explanations from the rule, not after the fact

The answer to "why" is generated from the rule that actually ran, not invented by a model afterwards. A policy you can't trace is one you stop trusting and work around.

Refusals

Which rule said no, in its own words.

Fills

Who was offered a slot, in what order.

Policies

"Because Deep Tissue says so."

"A policy you can't trace is one you stop trusting and work around."
Palm design note
Questions

About activity log & "why?"

Can I undo something Palm did on its own?

Bookings it made can be cancelled like any other; rule changes roll back; messages, once sent, are sent.

Can staff see the log?

Their own actions, by role.

How long is it kept?

As long as your account.

More in running the studio

Say it once. It books that way.

Finally, a scheduler that runs your calendar the way you would.

Start free for 30 days