The Brain / Capabilities / Silence detection

SENSE

It notices when nothing has happened
for too long.

A thread quiet for nine days, an approval nobody chased: no system records these, so the Brain works them out from the last thing that did happen.

Book a demo See it running first

What it looks like on a Tuesday

Three quiet things, one raised

07:40

An approval passes eleven days silent

The last event is the request itself, and eleven days is not a threshold, it is simply how long it has been.

07:41

Two other quiet records are dropped

An undated backlog task and a thread about a decision closed elsewhere, neither worth a morning.

07:43

One item, chase already written

The approval blocks two dated tasks and a Thursday review, so it is raised once with a drafted reply for a person to send.

How it works

Three mechanisms

01

Absence is derived from the last event

Every record carries a last-touched time, quiet is the gap between that and now, and there is no reminder to forget.

02

A gap is only a candidate

A quiet record is raised only when the silence has a consequence, judged against your written policy.

03

Raised once, not daily

Each item is raised once and updated in place, inside a cap of 40 interruptions an hour company-wide and 5 per person.

What it is not

Three honest limits

It cannot see silence in an unconnected system.

It does not know a thread was settled over lunch.

Not a productivity monitor; records, not humans.

A client that has gone quiet, expanded: why the Brain raised it, with two mail-thread reasons, and what it did not check.
A quiet thread, raised with its reasons and its limits. Real screen.

Book a Diagnostic Sprint

Bring the thread that went quiet and see it on the list.

Book a Diagnostic Sprint