Set the maintenance spend cap in Agent settings to define the maximum repair spend Aptoria may stage through the dispatch workflow. Add daily or monthly ceilings and restrict proposals to preferred vendors for tighter control. Set the cap to zero when you want every dispatch to wait for approval.
Daily and monthly ceilings
Vendors and the safety window
The maintenance spend cap is the dollar line between a repair the agent can stage through the vendor, acknowledgement, and safety-window workflow and one it has to bring to you. Under the cap, Aptoria prepares the vetted-vendor route and records the checks; over the cap, the work order routes to your approval queue and waits for your decision.
You set this on the Agent settings screen. Setting the cap to 0 means every dispatch needs your approval — a sensible starting point while you are still calibrating how much you want moved by configured rules.
Daily and monthly ceilings
Beyond the per-repair cap, you can add daily and monthly ceilings on maintenance spend, so a run of individually-small repairs cannot add up past what you are comfortable with in a given period. Leave a ceiling blank for no limit of that kind.
These ceilings count work still inside its safety window too, so a burst of proposed dispatches in quick succession cannot slip past the limit before it is spent. When a ceiling is reached, further dispatch proposals route to you until the period resets.
Vendors and the safety window
You can also restrict eligible dispatch proposals to your preferred vendors, so the agent only routes people you have already vetted. Anyone outside that list becomes a proposal you approve rather than an automatic assignment.
Every eligible dispatch path gets a short soft-commit window — a cancellable delay before it commits — and the emergency stop pauses all autonomy at once and voids anything sitting in its window. Adjust the cap any time; changes apply to new work, and your existing approvals are unaffected.