The morning sweep: what has gone quiet

Every workflow so far has reacted to something — a lead arriving, a stage changing, a form coming back. This one reacts to nothing happening, which is harder, because nothing happening does not raise an event.

It runs at 09:30, 6 days a week, and asks one question: what has gone quiet? An enquiry nobody has touched is the most expensive thing in a pipeline. It costs nothing to keep, it flatters every report it appears in, and it is dead.

This is the part worth stealing. The query does not ask when the record was last updated — it asks when somebody last wrote a note on it, falling back to when the enquiry was created if nobody ever has: COALESCE(max(note.created_at), deal.created_at).

An enquiry can be updated by a machine and still be abandoned by a human. A vector sync, a score being written, a stage tidy-up — all of those move updated_at and none of them is contact. The note is the human's fingerprint, and it is the only honest measure of attention. Same rule as Working the old list, and the year after the sale, where it decides who counts as an old lead.

Everything so far has done one thing to one record. This does one thing to fifty, through a Loop — and the loop is the first node in this course with two different outputs that mean different things:

So the escalation is not raised fifty times. It is raised once, after every individual task has been created, from a second query that asks a different question of the whole pipeline at once.

Both the query and the loop cap out at 50. If a business has two hundred quiet enquiries on a Monday, a hundred and fifty of them are not chased that day.

What makes that acceptable is the ORDER BY above it: the biggest cases first. A cap with an order is a policy — chase the fifty that matter most, every day, until the backlog clears. The same cap without an order would be a bug that looks like a feature, quietly ignoring a different arbitrary hundred and fifty each morning.

The second query counts the enquiries silent for 21 days and adds up what they are worth. Then a condition asks whether that count is above zero, and only the true arm is connected to anything.

Nothing is missing. If nothing is that badly stuck, the correct behaviour is to do nothing — no task, no mail, no “all clear” notification for somebody to start ignoring. You met this shape in Conditions and branches: an unwired arm is sometimes a guard, and reading which is which is a skill.

Open the two writes and read them as an advisor would. The daily one refuses the obvious message; the escalation refuses the comfortable conclusion:

That is sales management, written into a workflow. The automation's contribution is the list of names; the value is in what the person is told to do with it. When a client asks what makes these workflows different from a reminder, this is the answer, and it is readable in a text box.

Do not activate this one. You were told why in Draft and active: which workflows are actually running, and now you can see it: switching this on raises up to 50 tasks at 09:30 tomorrow. Find out how many before you decide.