Infinite Game OS

Definition

Email Triage helps a service-business solopreneur process an inbox in a fixed, predictable window. Every message routes to one of seven named buckets (New Job Inquiry, Active Job: Client, Scheduling, Invoices and Payments, Vendor and Supplier, Admin and Compliance, Noise). Draft replies generate automatically for repeating scenarios. Action items surface from every non-Noise thread so buried asks do not fall through. The skill is a starting point: the operator's bucket names, reply tone and follow-up timing make it theirs.

Seven buckets and the 4 D's

Every message lands in exactly one bucket based on sender, subject line, keywords and thread context. The seven default buckets fit a general service-business operator and are fully renameable. A tree trimmer might rename Vendor and Supplier to Equipment and Crews; a property manager might split New Job Inquiry into New Residential and Property Manager. The routing rules per bucket (sender domains, subject keywords, from-address patterns) are the operator's first customization. Budget 15 to 30 minutes with a real inbox batch before first use.

The 4 D's apply at the bucket level: Do (needs action today), Defer (needs action, not today), Delete (no action needed). The Noise bucket auto-archives on first occurrence with an unsubscribe on repeat senders. Action items extract from every non-Noise thread as a numbered checklist with deadlines or trigger conditions named. Draft replies generate for New Job Inquiry, Invoices and Payments and Active Job: Client threads that match a repeating scenario. The operator reviews and sends; the skill never auto-sends.

Handoff payload and pairing

Each triage session closes with a structured handoff payload: categorized message list, action-item checklist, draft replies awaiting send, follow-up triggers queued with timing. The payload feeds directly into Daily Admin Orchestrator or into the operator's direct workflow. New inquiries flag for Quote Builder. Payment events flag for Invoice and Payment Tracker.

Three follow-up trigger windows anchor the defaults: new inquiry unanswered at 24 hours, estimate sent with no response at 48 hours (hands off to Quote Builder), invoice unpaid at 7 days. These are calibration anchors, not rules. A competitive-market plumber might set inquiry follow-up to 2 hours; a coaching practice might set it to 72 hours. Adjust after one week of live reps when the actual business rhythm has surfaced.

Use Cases

Monday morning catch-up for a tree trimmer

Joel finishes his coffee before the first job site. Eighteen weekend emails run through triage in eleven minutes. Four new inquiries get draft replies ready for his review. Eight noise emails auto-archive. Two past-due invoice follow-ups draft with the client's first name already pulled. He leaves the driveway knowing exactly what needs action today.

End-of-day pass for a handyman with active jobs

A handyman with three jobs running simultaneously gets a dozen client messages through the week. End-of-day triage prioritizes Active Job: Client threads first, flags any unanswered client message past 4 hours as urgent and surfaces tomorrow's schedule confirms as a batch. The inbox stops being a second task manager.

Property manager email volume for a landscaping solopreneur

A landscaping solopreneur manages twelve commercial accounts through a single property management company. Those emails often contain three asks buried in one thread. Email Triage extracts each ask as a separate numbered action item. Nothing gets missed even in the longest threads.

Freelance designer recovering from a project-crunch backlog

A freelance brand designer surfaces from a two-week intensive with 40 emails in the inbox. A single triage pass buckets every message, drafts replies for the six estimate requests and the three payment follow-ups and identifies the two threads that need her judgment before a reply goes out.

First-time automation setup for a plumbing solopreneur

A plumber using n8n or Make.com feeds incoming Gmail messages through a classification prompt that pre-sorts the inbox before he opens it. Triage time drops from 45 minutes to under 10. The automation layer runs the categorization; the skill's bucket structure and action-item extraction define what the automation produces.

FAQ

How do I customize the seven buckets for my business?

Rename the bucket labels directly in your copy of the skill. Set routing rules for each bucket: the sender domains, subject-line keywords or from-address patterns that trigger that bucket. A 15-to-30-minute pass with a real week of email as input is the fastest calibration. Change what does not fit. Add a bucket if a category is missing. The defaults are a starting point, not a prescription.

Does this skill auto-send draft replies?

No. The skill generates draft replies for repeating scenarios and surfaces them for the operator's review. The operator sends. Auto-send creates liability and breaks client trust when a draft goes out without a human read. The discipline is that the draft exists at all, not that it sends itself.

How does it work without an automation layer?

Fully. The automation layer (n8n, Make.com, Gmail filters) multiplies the time savings by pre-sorting messages before the operator opens the inbox. Without it, triage runs Steps 2 through 4 message by message in a manual session. The skill works either way. Automation is a multiplier, not a requirement.

What is the right triage rhythm?

Two fixed windows per day: morning and end of workday. On-demand triage throughout the day turns the inbox into a real-time interrupt loop and creates context-switching drag. Real-time interrupts are appropriate only for Active Job: Client threads during an active job. Fixed windows are the discipline.

How does Email Triage connect to the other toolkit skills?

Email Triage is the first step in every Daily Admin Orchestrator run. Its handoff payload routes new inquiries to Quote Builder, payment events to Invoice and Payment Tracker and relationship touchpoints to Customer Follow-Up. Running triage standalone is valid; running it as the first step of the Orchestrator is how the whole toolkit connects.