Which actions wait for a human, and what happens when the human is slow?
Two questions, and vendors answer the first gladly. Ask them together, because the first is a list and the second is a rule, and only the rule says what your company is exposed to on a Friday evening. You are the human in the second half: boarding something, or looking at a message you fully intend to read properly later.
The pause, and what fills it
An approval step is a place in the work where nothing may pass until a named person answers. What matters is what the design does with the space that opens while it waits.
Three things fill that space in the reference design. The wait has no expiry, so a person who has not answered has not decided. The state of the work at the pause is written down, so what proceeds afterwards is what you were shown rather than a fresh attempt at the task. And when your answer arrives, the run records the decision and stops, leaving a person to restart it, a setting on the Register, the standing page of every setting in ArkOne’s reference design for an executive agent.
The third thing is a rule about your words rather than your speed. An answer the design is not sure it understood is asked again rather than interpreted. A single word of assent is a decision; a thought about what would happen if the client committed to two years is a question wearing the clothes of one.
One weekend, two rules for silence
Suppose the renewal invented for this work reaches a point where a new commercial term must go to the client, and your company puts an approval step in front of it. The message arrives on Friday at six. You see it, mean to answer, and do not.
| Through the weekend | The wait has no expiry | The wait expires |
|---|---|---|
| Friday evening | Paused, state saved | Paused, a timer running |
| Saturday and Sunday | Nothing happens | The timer runs out |
| What the design concludes | Nothing; no answer has been given | Whatever the expiry was set to conclude |
| What the client receives | Nothing | The offer, or nothing, depending on that setting |
| Monday, when you read it | The request, exactly as drafted | A message about something already settled |
| What you can still change | Everything | What has not yet left the building |
Exhibit 1. Illustrative. One approval left unanswered over a weekend, under a pause that waits and a pause that expires.
The third row carries the argument. On the right, a conclusion was reached over a weekend by nobody. Whether the expiry proceeds or abandons hardly matters: either way your not answering became an answer, and the conversion happened in a setting rather than a decision.
The fifth row is where you find out. What separates the columns on Monday is not damage, necessarily, but whose decision Friday’s offer was. A term that went out on a timer is a term nobody at your company chose, and Monday is a better moment to learn that than the client call.
What a good pause volunteers
A good answer has two halves and volunteers both. The list of actions that pause, held somewhere your company can edit. Then the sentence that no timer turns an unanswered message into consent, followed by what happens instead when a pause has waited a long time: an escalation to a second person, a reminder, an item on somebody’s morning brief. Waiting forever and waiting invisibly are different, and a good design chases you.
An ordinary answer describes the notification rather than the rule. It sends you an approval request and you approve it, which walks the easy path and answers neither question you asked. A second is that the timeout is configurable, which concedes that silence means something and hands you the decision without naming the default. Ask what it is set to today.
Then the follow-up that gets past the demonstration. What did it do the last time somebody replied with something unclear, and may you see that conversation? A design with a rule shows a question asked back. A design without one shows an interpretation, written with the same confidence as everything else, and the gap between those two transcripts is a client holding terms nobody approved.
An approval you can give from an airport gate is worth having. An approval that happens because you were at an airport gate is a different product, sold in the same meeting, described in the same words. The question of what happens after you answer is the other half of this one.
component: answer-card
Asked plainly
Which actions should an AI agent wait for a human to approve?
The ones that cannot be taken back once they happen: money leaving, a filing submitted, a commercial term offered to a client, anything written to a system of record other people rely on. The list belongs to the buying company rather than the vendor, so the question to ask is where that list is kept and who may change it, not which actions the vendor happens to have chosen.
What happens if nobody answers an AI agent's request for approval?
It depends entirely on a rule somebody wrote. One design pauses with no expiry, saves the state of the work where it stopped, and holds there until a person answers, so a slow approval means a delayed action. Another expires the pause after a set period and proceeds, or abandons the work, which means silence has been read as a decision without anyone deciding.
Can an AI agent treat a vague reply as approval?
Some do. A reply such as a single word, or a conditional thought about terms, has to be turned into a yes or a no somewhere, and that step is either a rule or a guess. A design that measures how confident it is that it understood, and asks again below a threshold, costs one extra message. A design that guesses acts on terms nobody approved.