Design human oversight and permissions
Define what the system may suggest, read, change or send. Separate preparing an action from executing it. Operations with financial, legal or third-party impact may need explicit approval. Oversight needs time, information and authority to intervene.
Apply least privilege: give each integration only the access it needs. Plan for exceptions, failures and a way to stop the system. An approval button that is hard to understand or triggered automatically is not meaningful human control.
A tool can prepare a draft reply to a customer. Sending it requires review by a person who can see the original message, sources and proposed changes.
Build control into the process, not just into a warning sentence.
Try it yourself
Create a pilot brief: problem, current process, authorised data, owner, metric, test cases, budget and stopping condition. Include a non-AI alternative and a plan for returning to the previous process.