AI Email Triage Employee: What Does It Do, and How Do You Install One This Week?

What is an AI email triage employee?

An AI email triage employee is an AI hired into one written job: sorting and drafting for an inbox. It reads what arrived overnight, sorts each thread into one of 4 buckets, drafts the obvious replies, and routes money, complaints and decisions to a person. It is the INSTALL book's first hire, before the eight jobs, because you can judge it by the next morning.

Picture opening your laptop tomorrow to the 3 buying questions that came in overnight already sitting as drafts in your voice, the one refund request flagged at the top with the thread summarised, and the other 113 threads filed before the coffee has finished, which is what the job looks like on day two, and how many of the 4 buckets could you fill in for your own inbox right now?

How much email lands on a working day, and why have AI tools not fixed it?

The average person at work receives 117 emails a day and is interrupted every 2 minutes, according to Microsoft WorkLab, 17 June 2025. In PwC's 29th Global CEO Survey, 19 January 2026, 56% of 4,454 chief executives reported no significant financial benefit from AI so far.

You already pay for the tools, don't you, and a tool waits for you to open it while an employee arrives with its job written, so how many of your last 7 mornings began with a buying question buried under a supplier invoice?

What does the written job description look like?

The job description is ten lines long and fits on one page.

"Never does" is the line that lets you sleep, so what reply would you never want sent without reading it first?

How does it sort the inbox?

It sorts every thread into one of 4 buckets and takes one action per bucket. Buying questions get a held draft, support problems get a held draft or a handoff, admin and supplier threads are routed, and noise is filed.

Start with buying questions and noise, since drafts of buying questions return the most hours and the most revenue while noise is the lowest stakes archive there is, and at your own hourly rate, what is the first hour of tomorrow worth to you already sorted?

What does it read, and what does it produce?

It reads four inputs and produces four outputs every run.

• Reads: the mail since the last run, the sender's history with you, the full thread, and the Business Brain.
• Produces: a label on each thread, held drafts in your voice, a summary on each handoff, and one log.

A customer who has bought twice gets a different first line from a stranger asking the same question, and you know what a good reply sounds like in your own voice, right?

What may it decide alone?

It decides four things alone: the bucket, archiving noise, drafting a reply, and drafting an acknowledgement for a known question. It sends 0 messages on its own in week one.

Those are the job description's rules: no send in week one, and send rights only after 2 clean Fridays, by your choice, so the employee earns each permission the way a new hire would.

When does it stop and hand a thread to a person?

It stops on six signals: anything new, a price question, a refund, a complaint, a decision, and any thread it scores below 70% confidence. The thread reaches the person you named with a summary on top.

Twenty broken messages out of 57 is what an unread system looks like from inside, and an employee that guesses costs more than it saves, so at a 70% line, how many of your own threads from last week would you have wanted held?

What context document does it read?

It reads the Business Brain starter, a 12 section document on what you sell, who buys it, your voice, your policies and the exceptions you always make. Email triage leans hardest on the voice and policies sections.

The starter takes half an hour and the full Business Brain extends it to every function, which is why yours writes about your refund window and your shipping countries instead of beautifully about nothing.

Which seam does it own, and who owns it today?

It owns seam 03 of The Thirteen Seams, capture to contact, for everything that arrives by email. The rate it protects is the share of first replies that open with something the sender wrote. Nobody owns that seam today: replying sits between two people's lists and on neither.

The inbox does not leak because you are slow, it leaks because a revenue seam has no name beside it, and the same gap shows up at the capture to contact seam on every form you run.

Who in your company owns the moment between a message arriving and a reply starting?

What does it not do?

It does not send in week one, quote a price, promise a date, close a sale, or make a call. Those stay with you.

Carrying a new lead from a form to a booked call is the job of the AI lead contact employee.

What does the Friday log show?

The Friday log shows counts per bucket, drafts approved against drafts edited, threads handed off, and one change for the week ahead. You read it for 30 minutes each Friday for the first 2 weeks.

The employee keeps no memory beyond what you write down, so the one change you make each Friday, to the Brain or to the job description, is how it improves, and if that read takes 30 minutes, what are you spending on the same inbox now?

How do you install one this week?

You install an AI email triage employee in five steps, in half an hour plus one evening, for $20 to $150 a month in AI account and connector costs.

1. Find the seam: pick the one inbox where buying questions arrive.
2. Write the job: copy the ten line job description above.
3. Give it the Business Brain: half an hour, voice and policies first.
4. Set the boundaries: read access, drafts only, a person for money and complaints.
5. Read the log on Friday and make one change.

The full nine step install walkthrough for the first hire sits in Appendix B of the INSTALL book, priced at $7, planned for one evening with the AI account you already have.