The volunteer coordinator’s kitchen table held a single lamp and a stack of half-folded bulletins. At 9:17 p.m. on Thursday she opened the scheduling agent’s latest file. Three names filled the 8 a.m. Sunday slot. None carried a confirmation checkmark. She stared for four seconds, then picked up her phone and began texting the backup list one by one.
The agent had run exactly as built. It pulled availability, applied the preference rules, and produced a clean list. What it lacked was an agent escalation path: any instruction for the moment when no one on that list had actually said yes. She moved to the next manual step because nothing in the workflow told the system to stop and ask a human first.
Teresa Torres describes continuous discovery as ongoing contact with the real moments when users encounter a product. In agent loops the same principle applies, except the critical moments are handoffs rather than clicks. The loop stays trustworthy only when it contains explicit rules for what happens when the automated step ends and a person must act.
Define the agent escalation path before the first run
Most teams start by describing the output they want: a filled schedule, a set of reminder texts, a list of curriculum pages. Torres pushes teams to name the job the user is actually doing at that moment instead. For the volunteer coordinator the job is not “receive a list.” It is “know within two minutes whether the list is safe to act on or whether she must start calling people.”
Writing that job description forces the escalation step into view. The agent must now include a rule that checks confirmation status before it closes the loop. Without the rule the coordinator still does the work, only later and under more pressure.
One children’s ministry platform I watched last year added a single line to its scheduling agent: if fewer than two confirmed names exist four hours before the shift, pause and surface the list to the coordinator with a red banner. The change took one afternoon. The number of Sunday morning emergency texts dropped by half within three weeks.
Why the agent escalation path has to survive the print step
Ministry workflows still contain physical moments. Someone prints the roster, someone tapes it to the door, someone hands a stack of name tags to a greeter. Torres would call these the observable moments of use. An agent that stops checking once the digital file is generated misses every one of them.
The useful escalation rule therefore triggers after the print action, not before. In practice this means the agent waits for a simple signal— a photo of the printed list, a checkbox marked “posted,” a short voice note from the volunteer on site. Only then does it consider the handoff complete.
Without that post-print check the coordinator receives a clean digital file on Thursday night and still walks into Sunday unsure whether the paper version ever reached the right door. The agent has done its job on paper; the actual job remains unfinished.
Measure the handoff, not the generation count
Reliability teams formalize this in the idea of an on-call escalation policy: someone is always named as the next human in the loop.
Teams often track how many schedules the agent produces each week. That number rises quickly and looks like progress. Torres would ask instead how many of those schedules reached a confirmed human action without further intervention.
Track the percentage of shifts that move from “agent output” to “volunteer confirmed on site” without the coordinator reopening her phone after 9 p.m. When that percentage stalls, the escalation path is still missing or mis-timed.
One team I worked with replaced its weekly generation metric with a simple handoff score. Every Monday they counted how many of the prior week’s agent outputs required zero follow-up texts. The number started at 41 percent. After they added the post-print confirmation rule it reached 78 percent in six weeks. The generation count stayed roughly flat; the usable schedules increased.
Your Turn: Apply This Today
- Pick one agent loop already running in your ministry tools and write the exact sentence that tells it when to stop and surface a human instead.
- Add a single confirmation field that must be marked after the physical print or door-post step before the loop can close.
- Replace the “schedules generated” number on your dashboard with a handoff completion rate for the past seven days.
- Schedule a ten-minute review each Monday where you look only at the shifts that still needed manual rescue and note the exact missing escalation rule.
- Write the escalation rule in plain language a volunteer coordinator could read out loud, then paste it into the agent prompt or workflow description.
- Test the new rule on next week’s schedule and record whether the coordinator sent any after-9 p.m. texts for that shift.
Two earlier posts on this blog explored the same pattern from different angles. “The Niche Tool That Still Needs a Human Print Step” showed how digital outputs still require a physical checkpoint, and “The Goal Loop I Set That Ignored Sunday Validation” described what happens when the measurement stops at generation instead of handoff.
I consult with product leaders building agentic workflows for ministry teams on continuous discovery loops, escalation rule design, and handoff metrics. Let’s talk.