Does this work with the channels we already use?

The pattern needs channels you authorize it to read and an authorized way to read the record. The audit confirms which of yours can carry it and what is in scope.

What happens when a thread should be let go?

A person closes it and the reason is recorded against the thread, so the end is a decision rather than a silence. The workflow closes nothing on its own.

Threads do not get dropped on purpose

Today

One goes quiet while everybody assumes somebody else has it

Threads do not get dropped on purpose.
One goes quiet while everybody assumes somebody else has it.
An owner leaves and the context goes with them, so the next person starts from whatever survived in the record.
The conversation that needed one more message never gets it, and you find out when the buyer has already moved on.

With agents

The record is kept and a person is handed the moment it needs one

An open thread has an owner.
Going quiet becomes a visible state.
Picking a thread back up costs less.

How an agent runs it

An open thread is either a record somewhere or a memory in somebody's head, and memory is the half that fails here. The workflow keeps the record and hands a person the moment it needs one.

Maintains

Keeps a ledger of the open threads across the channels you authorize, so an open thread is a record rather than a memory.

Names

Puts an owner and a next action on each thread, so the question of whose it is has an answer.

Surfaces

Flags the thread that has gone quiet past the interval you set, and the thread whose owner has changed or left.

Assembles

Reassembles the context a person needs to pick the thread back up, from the thread and the record rather than from memory.

Prepares

Drafts the message that would restart the thread, for the owner to send, change or discard.

Human gate

Nothing is sent and nothing is scheduled to send. The send, the decision to let a thread go, and the ownership are a person's, and the ledger can be kept by hand at any point because the threads and the records are yours.

Records

Keeps what was closed and why, so a thread that ends is a decision rather than a silence.

Results

What changes when the thread is a record

An open thread has an owner

The ledger carries an owner and a next action on each one, so the question stops being answered by assumption.

Going quiet is a visible state

The interval you set is checked against the thread rather than remembered by somebody.

Picking it back up costs less

The context is reassembled from the thread and the record, with a draft attached.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from an open thread to a draft a person sends. The boundary is the send. The send, the close and the ownership stay a person's. It extends toward The sales ops coordinator as an AI Employee as a possible next step rather than a promised state. How It Works shows how the gates and the authorizations are built.

Tier 1 / Prove

How It Works

Questions, answered

No. It prepares the draft and a person sends. Nothing is scheduled to send and the gate is closed by default. The threads and the records stay in your systems, so the ledger can be kept by hand at any point without the agent.

AI Opportunity Audit

See which threads are still open on your side

Bring the deals that have gone quiet on you and see which threads are still open on your side.

Book an audit