Low-Noise Inbox Triage: A Draft-Only Loop for Executive Slack Overflow
A reusable pattern for checking a noisy channel on a schedule, drafting replies, and routing them to human review without ever auto-sending.
The problem
A lower-priority Slack workspace was getting checked too often for what it produced. Checking less meant missing things. Auto-replying meant sending the wrong things. The fix was separating steps that had been silently fused together: reading, drafting, reviewing, and sending.
What got built
A scheduled collector reads new mentions and DMs in a bounded window. A drafting step produces candidate replies in the account owner’s voice. A poster step routes those drafts into a private review surface, grouped by topic thread so repeat messages about the same issue land in one place instead of scattering.
Nothing in this pipeline can send to the source channel. Sending is a separate, human-only action. Sensitive or commitment-shaped content gets flagged approval-required rather than answered automatically.
The reusable frame
- Decide the noise budget first. Batch cadence beats real-time pings, and silence is the expected output on a clean run.
- Separate read, draft, review, and send into distinct steps. Never let one step silently do the job of two.
- Route to topic threads, not one giant digest.
- Treat commitments and sensitive items as approval-required by default.
- Verify with dry-runs and receipts before trusting the schedule.
Proof it runs
- Collector and poster built as separate, independently testable scripts
- Collector smoke-tested against a live read
- Poster dry-run tested against a synthetic payload before going live
- Output validated as well-formed JSON before being trusted downstream
- Scheduled job installed and confirmed via a direct readback of the installed schedule, not just “it should be running”
Why this generalizes
None of this is Slack-specific. The pattern: bounded read window, drafting step with a voice constraint, human review gate, explicit approval path for anything sensitive, and a verification pass before you trust the schedule. Same shape works for email triage, support ticket intake, or any channel where an accidental auto-send is expensive and a delayed draft is not.