The Series· No. 60 · Act XV — The Engine, Deeper

By DocuSeller · Published

Waiting On People
DocuSeller · No. 60

The machine that asks a stranger

The packet is finished except for one page, and the only person who has it doesn't work for you.

So the line writes to them itself.

An external party stands beyond a fence with the missing page while the company’s workflow remains inside The missing page is outsideWorkflowYour teamExternal party
Not on the payroll, not in the building, holding the only page that matters.

Every stop in this engine so far has waited on somebody with a badge. A reviewer. An approver. Someone two desks away.

This one waits on a roofer.

Mid-order, the line can raise a link, send it out of the building, and go to sleep.

Two steps do it, and you drag them on like any other.

The first builds the link. Whatever you wired into it goes inside: a form to fill in, a letter to read and sign, files to look through, an upload slot carrying your own instructions and a cap on how many. Wire a second form in next month and the link grows a second page. There is no fixed menu — it reads what it is plugged into.

A workflow builds and sends a link, pauses for an outside person, and resumes at the next step with the reply data The order keeps its place while waitingBuild linkSend it outWaitPausedResumeNext stepOutsideReplyThe reply becomes data for the next step
One order, paused in public, still holding its place in the queue.
Two illustrative emails contrast a complete clickable example URL with plain text that requires selecting and copying Make the whole address a linkClickablehttps://example.com/r/7Plain texthttps://example.com/r/7Open directly, without copying
One of these gets clicked. The other gets selected, copied, and abandoned.

The link that goes in the email is a real, whole, clickable address. On purpose. A link that arrives as flat grey text somebody has to select and copy isn't a link. It's homework.

You get the usual guardrails: a date it closes, a cap on how many answers it will take, one answer per device. Past any of those it doesn't quietly keep working. It says it's over.

The second step is the waiting, and there is less to it than you'd think. The order parks. Nothing polls. Nothing retries. Nothing fires a reminder at three in the morning.

Nobody chases anybody. The answer is the alarm clock.
A handless alarm clock resumes a waiting run when an external reply arrives, without polling or timed reminders The reply is the alarm clockResumeNo polling or timed remindersContinue when the reply arrives
No hands on the face. It only knows one time, and that time is when they answer.

The moment their reply lands, the run picks up at the exact next step, with what they said already in the tray every later step reaches into.

And if the order is refunded, that link is deleted along with everything else the run produced.

That is the difference worth noticing. It was never a form parked on your website forever. It existed because one order needed one answer out of one person, and when the order goes, it goes.

The honest bit: it still doesn't nag. Somebody has to notice the roofer has gone quiet.

But that somebody is looking at one order that says plainly what it is waiting for, instead of four people each assuming one of the others sent the email.

Next: the four people on one document, and how each sees only their own blanks.

#Automation · #PropTech · #CommunityManagement