Define the boundary
Give every automation a limited job, a clear source of information, and explicit permissions. Drafting a reply and sending it are different actions. Deciding which actions need approval is part of the product design.
Make uncertainty visible
Missing information, conflicting records, and unexpected responses should trigger an understandable handoff. Show the reviewer the original request, the available evidence, and the proposed next step.
Test the awkward cases
Use duplicate submissions, unavailable services, ambiguous requests, and expired permissions as test cases. Keep an action log, add safe retries, and make it possible to stop the workflow without losing its history.