Practical software guides
Separate a suggested response from permission to act. The application should enforce the approval rule even if an AI draft or urgent message asks to bypass it.
| Action | Allowed automation | Human gate |
|---|---|---|
| Acknowledge enquiry | Draft from approved template | Review before send in this specimen |
| Change booking | Prepare proposed change only | Verify customer authority and availability |
| Refund | No release credential | Approved amount and original payment matched |
| Unknown policy | Flag missing source | Responsible reviewer and backup |
| Queued action after revocation | Stop | Confirm credential denied and queue cancelled |
Define response windows and an unavailable-reviewer path in the real policy; a universal deadline is not appropriate. Unknown amount, currency, customer or provider state should stop a financial action.
Evaluate stale booking data, duplicate requests, unauthorised recipients and instructions embedded in documents. Log the approved action and result without secret values or unnecessary customer data. The travel-quote example supplies a bounded drafting case; the permission budget covers broader limits.