Email autopilot

Each day an email operator triages your inbox into needs-you, routine, and noise, drafts replies for routine threads in your voice, nudges threads that never got an answer, and compiles a digest of what actually needs you — you approve every send.

Saves you ~15.2 h / week

Join the waitlist

What it installs

Agents 2

  • Email Operator

    Works the user's inbox through the browser: triage, voice-matched drafts, polite nudges, and a daily needs-you digest — every send behind approval.

  • Email autopilot Quality Reviewer

    Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Teams 1

  • Email autopilot quality team

    The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.

Workflows 1

  • Triage, draft, nudge, digest

    Triage new mail into needs-you, routine, and noise, draft voice-matched replies and nudges, compile the daily digest, and hand every send to approval.

Documents 1

  • Triage rules

    The living contract for what needs you, what is routine, what is noise, how you sound, and how silence is chased — updated as you correct the agent's calls.

Goals 1

  • Inbox worked daily, nothing important missed

    Keep the inbox triaged every working day with the user's attention spent only where it is actually needed.

Skills 4

  • inbox-triage

    Scan the inbox by time window rather than read state and sort every thread into three tiers — needs-you as a numbered list, routine to review and draft, noise reported as counts only — never archiving or deleting anything without confirmation. Adapted from ericporres/email-triage-plugin/email-triage.

  • reply-drafting-in-voice

    Draft replies that read as the user wrote them — learned from their sent mail and the voice section of the triage rules — answering only from the thread and known facts, with every unknown marked instead of invented.

  • thread-nudging

    Find threads still waiting on a reply from the other side, and draft polite escalating nudges on the configured cadence — each adding a reason to reply or an easy out, with hard stop conditions.

  • needs-you-digest

    Read the inbox in cost tiers — shortlist by search, exclude noise, batch-read snippets, open full threads only for active conversations — track the waiting-on-them bucket that feeds the chaser, and compile a digest that states its scope and confidence instead of overclaiming. Adapted from coderabbitai/codex-plugin/gmail-inbox-triage.

Schedules 1

  • Daily inbox run

    Works the inbox and compiles the needs-you digest each working day. ## Professional quality control Objective: complete the recurring Email autopilot operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Reconcile each status, owner, date, dependency, exception, and next action to the operating record. Confirm that proposed changes remain within authority. Internal communication must be decision-dense and plain, without generic AI phrasing, management filler, vague ownership, or a polished summary that omits blockers. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Folders 1

  • Email autopilot

Requirements

What this playbook expects to do its job. Task Machine does not verify these — you decide whether your setup is ready.

  • Browser access to your email — The agent works your Gmail or Outlook inbox through its web interface in your browser — reading threads, preparing drafts, and labeling — and pauses for your approval before anything is sent. Until you connect it, it works from forwarded threads and the triage-rules document.

Setup guide

How to Automate Email Triage

A practical guide to daily inbox triage with needs-you lists, voice-matched drafts, polite nudges, digests, and approvals.

Read the setup guide

Don't see your workflow? Describe it.

A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.

* What keeps taking time you don't have? *

Takes a minute · no account needed

Install Email autopilot and run it with approvals.

Join the waitlist and we will send early access when the first private beta spots open.

Private beta. We invite teams in batches and never share your email.