← All plays
Inbound & Follow-up

Inbound Email Triage Reply

Every message in the watched inbox is classified, gated, and either answered once with a reviewed reply inside caps and quiet hours, or handed to a human with the reason, so nothing sits unread and nothing gets an automatic answer it should not have.

Every message in the watched inbox is classified, gated, and either answered once with a reviewed reply inside caps and quiet hours, or handed to a human with the reason, so nothing sits unread and nothing gets an automatic answer it should not have.

The scoreboard

Every message in the watched inbox is classified, gated, and either answered once with a reviewed reply inside caps and quiet hours, or handed to a human with the reason, so nothing sits unread and nothing gets an automatic answer it should not have.

What’s in the play

  • A complete 5-member Team
  • The version-pinned Play, Player configurations, typed handoffs, schemas, and fixtures
  • Project-local adapters for Claude Code, Codex, Cursor, Hermes, and OpenClaw
  • Offline verification and Player-aware run receipts

Tools it connects to

mailbox.readmailbox.sendoperator-handoff.sendfs.write

Team and proof

  • 5 Players are included. Names and assignments unlock after purchase.
  • Offline synthetic fixture included
  • Player-aware routing and run receipts
  • Byte-for-byte reproducible package with a published SHA-256

Safe sample output

A validated inbound email triage reply artifact written inside your project.