Inbox Triage Until SLA Green
Inspired by Supafax — connect inbox and calendar, auto-label threads, draft replies in your voice, and schedule meetings until response SLAs stay green.
Inspired by Supafax
by Trooper
/loop 30m Start the "Inbox Triage Until SLA Green" loop. Inspired by Supafax (https://supafax.com). Goal: inbox threads labeled, drafts ready for approval, and calendar holds proposed within SLA targets Max iterations: 20 Between iterations run: Report unread priority threads, drafts pending approval, overdue SLAs, and scheduling conflicts Exit when: zero priority threads without draft or explicit escalation, SLAs green, and calendar conflicts resolved or delegated ## Before you start - Connect Gmail (required) — Inbox read, label, and draft replies - Connect Slack (optional) — Escalate urgent threads to team - Attach Loop runner (required) — Self-pace iterations and run checks between passes. - Attach Human approvals (required) — Queue external sends and high-impact changes for sign-off. - Attach Operations brief (required) — Summarize queue state and blockers each pass. - Google Calendar (read via plugin) — Meeting scheduling context - Outlook (read via browser) — Alternate inbox source ## Steps 1. Connect streams: Sync inbox and calendar; learn reply patterns and priority contacts. [tools: Gmail, Google Calendar] 2. Label and prioritize: Auto-label threads; rank by SLA, sender importance, and urgency. [tools: Gmail] 3. Draft replies: Generate reply drafts in user voice; queue for approval before send. [tools: Gmail] 4. Propose meetings: Suggest calendar holds and scheduling options for approval. [tools: Google Calendar] 5. Report SLA state: Surface overdue threads, conflicts, and threads needing human judgment. [tools: Slack] Command: node scripts/inbox-sla-report.js Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass. Guardrails: - Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply - Preserve full audit trail linking source data to every automated action - Escalate compliance, safety, or regulatory-sensitive items immediately
Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.
1. Connect streams
Sync inbox and calendar; learn reply patterns and priority contacts.
Tools: Gmail, Google Calendar
2. Label and prioritize
Auto-label threads; rank by SLA, sender importance, and urgency.
Tools: Gmail
3. Draft replies
Generate reply drafts in user voice; queue for approval before send.
Tools: Gmail
4. Propose meetings
Suggest calendar holds and scheduling options for approval.
Tools: Google Calendar
5. Report SLA state
Surface overdue threads, conflicts, and threads needing human judgment.
Tools: Slack
node scripts/inbox-sla-report.jsGuardrails
Rules the agent must follow so it cannot cheat the exit condition.
- Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
- Preserve full audit trail linking source data to every automated action
- Escalate compliance, safety, or regulatory-sensitive items immediately
More Operations loops
Inbox Triage with Approval
On an interval, classify incoming mail, draft safe replies for routine threads, and escalate anything that needs a human decision.
Morning Operator Brief
Daily interval loop that reads your calendar, open tickets, and inbox priorities, then delivers a concise operator brief with ranked actions.
Customer Onboarding Watch
Interval loop that watches new signups, runs the onboarding checklist against each account, and nudges or escalates stuck users.
