AI only with a person in the loop
A draft can be fast. A message that leaves the building still needs a name on it.
Where rates and answers live
AI only with a person in the loop
-
01
An AI pilot at Aarvix Services is one job: a support reply that cites the help centre, an intake summary, a first pass on a document. The pilot includes the review step. If the draft can be sent to a customer, someone on your side sends it.
-
02
An agent engagement is larger and still has that rule. We will not sell a queue that answers itself with no owner. Model spend is not hidden inside the hour. The hour block is the build of the loop. If a provider bill is separate, we say so in the scope.
-
03
The decision at the end of a pilot is continue, narrow, or stop. Stopping is a successful outcome when the job was the wrong one.
Worked detail
Review is a step in the workflow, not a policy paragraph.
- 01
- A useful pilot has a source the draft must cite, a person who is allowed to send, and a place the draft waits. If any of those three is missing, the build is pretending. The waiting is the product. Speed without the wait is the thing we will not ship.
- 02
- An agent engagement is the same rule at a larger queue. Intake, triage, document handling. The queue is defined. The person remains. We will not sell “the inbox answers itself”.
- 03
- The contact form is not sent to a model. If a later job uses a provider, the scope names it, and the hour is still the build of the loop rather than a blank cheque for model spend.