Why this is the right automation
It stays small, local, and deterministic. It reduces support demand without turning Vraimony into a support desk or high-touch agency.
Because Vraimony is being run by one operator, the better answer is not a human-heavy service layer. It is a deterministic local copilot that guides the user to the right next move: intake score, deadline posture, missing evidence request, receiver cover, or delta follow-up.
It stays small, local, and deterministic. It reduces support demand without turning Vraimony into a support desk or high-touch agency.
Later, this can evolve into a rules-based side panel inside One Case: source checks, named gap requests, receiver-mode preview, and red/yellow deadline posture.