The approval gate
Ash never commits on your behalf.
It answers routine questions, gathers information, and records conversations. Anything that could commit you stops and waits for approval.
Control stays with you.
An assistant can save time without taking control of decisions that affect your reputation or obligations.
Ash handles routine questions, gathers information, and records conversations. When a decision could bind your business, it stops and asks you.
What waits for you.
Any proposed action that could bind your business becomes a decision, with the relevant conversation attached. The action does not run until you approve it.
- Prices and quotes
- Ash will not name a number you have not set.
- Terms and commitments
- Anything promising what you will do waits for you.
- Outbound that binds you
- Drafted, held, and sent only after explicit approval.
- Anything unclear
- Flagged for you rather than answered on the spot.
Booking is the deliberate exception.
There is one deliberate exception: Ash can book appointments without asking you to approve each one.
A slot is offered only when it falls within hours you marked as bookable and is free on your live calendar. Ash checks again at confirmation. It follows availability rules you set instead of making a judgment about your time.
Planned work is approved once, then checked before every send.
A follow-up plan or a nurture sequence is reviewed in full before you switch it on — you see what will go out and when.
Before each send, Ash checks whether the person has opted out or replied, whether the message falls within quiet hours, and whether Ash's automated messages have already reached that person too often. Any one of those conditions stops the message.
The approval gate is part of the system.
Ash does not rely on a prompt that merely tells the model to be careful.
Actions that require approval are stored on the server and run only after an explicit confirmation. The model can suggest an action, but it cannot bypass the gate.