A person in the loop
If it can reach a customer, a patient, or a parent, a person sends it.
Speed without a wait is a different product, and we do not sell it.
The loop is the product.
Review means a named step where a person can change, reject, or send. It is not a policy sentence in a footer. For a support draft, the draft cites the help centre and waits in the tool the agent already uses. For a document read, a low-confidence page waits in a queue and is not filed as if it were certain. For an order line that does not match, a person is notified and the line does not silently drop or silently pass.
The person is on your side when the message is yours. We can build the wait. We do not become the sender of your customer email. An internal summary can have a lighter review than a public reply. The scope says which one you bought.
Model spend is not a secret inside the hour. The hour is the build of the loop: the source, the draft, the cite, the wait, the failure cases. If a provider will bill you separately, the scope says that before you confirm.
The end of a pilot is a decision. Continue, narrow, or stop. Stop is a result. An agent build is a later block for a queue the pilot showed was real. You are allowed to keep the pilot and decline the rest.
Review, in practice
Can the model send if confidence is high?
No. Confidence is not a person. High-confidence drafts still wait when the scope says a person sends.
What about an internal note nobody outside will see?
The scope can make that review lighter. It still names who is responsible if the note is wrong.
Does the contact form use a model?
No. The form is stored and emailed. It is not summarised by a model on the way in.