Notes / Workers
An AI worker should know when not to act
Useful AI workers do not act on everything. Learn when AI workflows should pause, ask for approval, escalate, or route work to a person with context.
By Rich Hill III. Published Jul 8, 2026. 7 min read.
AI agents are getting better at doing work across tools. They can read messages, summarize records, draft replies, update fields, route tasks, compare information, and trigger the next step in a workflow.
That is useful.
It is also where a lot of AI workflow projects start to get risky.
The important question is not only: What can this AI do?
The better question is: When should it stop?
A useful AI worker should not act on everything it sees. It should know its boundaries. It should know when context is missing. It should know when a decision needs approval. It should know when to route work to a person instead of guessing.
That is the difference between uncontrolled automation and a managed AI worker.
AI workflows need boundaries, not just speed
Key takeaways
- A useful AI worker should know when to pause, ask, or escalate instead of guessing.
- More autonomy creates more need for clear ownership, approval rules, and monitoring.
- Human oversight should be placed where risk changes, not applied blindly to every step.
- Escalation is not failure when it protects the business and gives a person context to decide.
- The best AI workflows define what the worker can handle, draft, ask, and escalate.
Frequently asked questions
What should an AI worker not do?
An AI worker should not guess when context is missing, silently resolve conflicting records, make sensitive commitments without approval, or expand beyond its defined workflow. It should ask for missing information or escalate unclear/high-risk moments to a person with context attached.
When should an AI agent require human approval?
Human approval should be required before sensitive actions such as sending external commitments, changing important records, approving refunds, making policy exceptions, handling account access, or acting when confidence is low.
What is the difference between human-in-the-loop and human-on-the-loop?
Human-in-the-loop means a person must approve before the AI continues. Human-on-the-loop means the AI can complete routine work while a person monitors summaries, exceptions, logs, or risk signals. Many workflows need a mix of both.
How do you automate business workflows without losing control?
Start by mapping the workflow. Define the inputs, tools, handoffs, routine steps, approval moments, escalation rules, monitoring process, and owner. Then decide what the AI worker can handle, draft, ask, and escalate.
Are AI workers the same as chatbots?
No. A chatbot usually answers messages. An AI worker is built around a workflow: triggers, tools, records, decisions, approval rules, escalation paths, and next steps.
Explore Workers