Ash never commits on your behalf.

Every product in this category advertises how much it will do without you. That is a reasonable pitch if the worst case is a badly worded email. It is an unreasonable one if your reputation is the actual product you sell — and for anyone whose clients chose them personally, it is.

So Ash is built the other way round. It is generous with the things that cost nothing to get wrong and strict with the things that cannot be taken back. What it does freely is answer, gather and record. What it does not do, ever, is commit you to something.

Anything that binds you stops and becomes a decision. A price you have not quoted, a term you have not agreed, a promise about what you will do or when — these arrive in the owner app as something to approve or decline, with the conversation that produced it attached. Nothing is written and nothing is sent until you say so.

There is one thing Ash completes on its own, and it is worth saying out loud rather than hiding in a footnote: it books appointments without asking you first.

The reason it is safe is the constraint around it. A slot is offered only if it is inside the hours you have declared bookable and free on your live calendar, and that is re-checked at the instant of confirmation. Ash is not exercising judgement about your time; it is reading rules you set and a calendar you control. Making you approve each booking would only mean the client waits — which defeats the point of answering quickly at all.

The distinction matters more than it sounds. Plenty of systems achieve this by instructing the model to be careful, which works until the day it does not, and you find out from a client.

Ash does not rely on the assistant choosing well. Actions that write or send are stored on the server and executed only when an explicit confirmation arrives. An assistant that decided to be bold would produce a card awaiting your approval — not a sent email. The gate is in the plumbing, where a bad day cannot argue with it.