Human control matters wherever an incorrect action could have a serious consequence, a customer needs judgement or a commitment exceeds agreed limits. Automation can help organise those cases without becoming the final decision-maker.
Define the boundary before launch
List decisions involving safety, complaints, unusual pricing, sensitive information and contractual commitments. Decide which actions a system may perform, which it may prepare for review and which it must immediately escalate. The boundary depends on the service and should be checked by the person responsible for that area.
For a clinic enquiry workflow, collecting administrative details is different from giving clinical advice. For a quotation workflow, acknowledging receipt is different from promising a price or completion date.
Make escalation usable
Give the receiving person the request, relevant context, reason for escalation and the customer's contact preference. Specify when they must respond and who provides cover. A vague instruction to “contact a human” is weak if nobody owns the queue.
Test unclear language, conflicting requests and unavailable staff. Confirm that the system does not invent an answer to keep the conversation moving. Track failed or delayed escalations as a pilot outcome.
Human control also includes stopping the workflow, correcting records and reverting to a manual process. Review permissions regularly. A well-designed automated business preserves clear responsibility; it does not leave the team guessing whether a machine has already made a consequential promise.
Existing guides: Clinic enquiry routing · Reception model · Pilot design.