The AI that proposes. You decide how far it goes.
Ven reads every new message, works out what the customer needs and gathers the details required to move the job forward. You decide how much it may do on its own, service by service, and every workspace starts with changes switched off.
Four modes, and you start at the safest
Observe changes nothing and only records. Assist proposes for review. Qualify lets Ven collect the answers itself. Book stays off until you turn it on.
You can see why Ven proposed it
Every value carries the message it came from and how sure Ven was, so an operator accepts or rejects field by field instead of trusting all of it.
01
Ven reads the message against your templates
It matches the service, extracts what the customer already said, and marks what is still missing for that particular service.
02
It proposes a structured change
Typed values with a confidence score, plus the next approved question — not a paragraph of prose for somebody to interpret.
03
Your rules decide whether it applies
Your template, your policy and the operator's permissions are checked first. What passes is saved; what does not is logged with the reason.
The decision it proposed
Structured, typed and stored — whether or not it was ever applied.
The message behind it
Each value points back to the message it was read from.
The verdict and the reason
Applied, or refused with the policy that refused it.
That distinction is what makes AI safe to run on operational work. A clumsy sentence is embarrassing; a wrong booking costs a van and a morning. Ven never writes the appointment itself. It proposes, and the application checks state, permissions, policy and version before anything applies.
Allowed one service at a time
A service becomes bookable in its own form — never for the whole workspace at once.
Refusals are recorded too
An action the policy layer blocked is logged with its reason, beside the ones that succeeded.
Stale writes cannot land
Changes apply against the version the operator reviewed; anything older is rejected rather than merged.
Handoff with everything attached
When judgement is the better path, the request, its history and Ven's reasoning move to a teammate together.
Start with Ven changing nothing
Every workspace begins in Observe: Ven writes down the decision it would have made, and your team reads it before anything is switched on.