Kit 05 · Commitment tracking
Inbox Follow-up
Surface commitments and prepare contextual replies without surrendering send authority.
Field sheet
Find the promise before it becomes a problem.
Inbox Follow-up identifies threads that contain unanswered questions, promised actions, or waiting parties. It prepares a review queue and suggested replies; it does not impersonate the sender.
Worked exampleIllustrative workflow
Current dragA customer is waiting for an update promised three days ago.
Control addedIdentify the promise, deadline, latest context, and source thread.
System preparesDraft a concise reply with the promised information 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
- Thread index
- Commitment register
- Draft queue
- Review status
- Sent-reference log
May run externally
- Summarizing approved threads
- Drafting a reply from supplied context
- Grouping similar follow-ups
Never automatic: sending messages, making promises, or inventing customer context.
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 links.
- Tools remain replaceableThe sender controls every release.
Human review checklist
Before the work moves.
- Is the source thread attached?
- Is the commitment quoted accurately?
- Does the draft avoid new promises?
- Are sensitive details handled appropriately?
- Did the named sender review and send it?