What does Inbox Follow-up do?

It reads pasted threads, keeps a running ledger of who is waiting on what, and ranks follow-up by dollars at risk rather than by date.

What does Inbox Follow-up need?

Threads pasted in by the account owner, their own voice notes for replies, and their review rules.

When does Inbox Follow-up stop?

It stops when it cannot name the sender, tell who wrote last, or find an ask, or when a draft needs a price or date nobody supplied.

Kit 06 · Commitment tracking

Inbox Follow-up

Surface every open commitment, ranked by what is actually at risk, and prepare replies without surrendering send authority.

Authority rule
A person decides whether a thread requires action, whether the draft is accurate, and whether anything is sent.

Field sheet

Find the promise before it becomes a problem.

Inbox Follow-up reads pasted threads, refuses the ones too thin to stand behind, and keeps a running ledger of who is waiting on what, ranked by dollars at risk rather than by date. It prepares the queue and the drafts; it does not impersonate the sender and it never sends.

Worked exampleIllustrative workflow

Current dragA month of threads sits unanswered and nobody knows which one is expensive.

Control addedRecord the promise, the amount at stake, the direction of the money, and the source thread.

System preparesRank what to chase by what is at risk, and draft a reply or an honest status update.

Human releaseThe account owner reviews, edits, and sends from the normal inbox.

Processing boundary

Local by default. External by decision.

The operating record remains useful without a connected service. External assistance is limited to approved context and explicit tasks.

Runs locally

Commitment ledger with amounts
Follow-up clocks per thread kind
Ranked chase list
Draft queue
Review status

May run externally

Summarizing approved threads
Drafting a reply from supplied context
Grouping similar follow-ups

Never automatic: sending messages, making promises, inventing a number, or closing a thread while money on it is still unpaid.

Ownership and hand-off

The workflow remains useful when the tool changes.

Client keeps the sourceThe inbox remains the system of record.
Decisions remain visibleDrafts are visibly separate from sent mail.
Review stays attributableCommitments retain source threads, dates, and amounts, and private detail stays out of the file.
Tools remain replaceableThe sender controls every release.

Human review checklist

Before the work moves.

Is the source thread attached?
Is the commitment quoted accurately, one row per ask?
Does the draft avoid new promises and invented numbers?
Is money still outstanding on anything marked closed?
Did the named sender review and send it?

Discuss this workflow Read the intake walkthrough Back to all kits