Your sent folder already has your AI agent's answers

You've been answering emails for years. Lead times, what a quote does and doesn't cover, what happens when someone cancels with two days' notice. All of it is already written down, in your words and your tone, sitting in your sent folder. Getting an AI agent started isn't blocked by a lack of information — it's blocked by the fact that the information is spread across four thousand threads and tangled up with things you'd never want repeated. Here's a practical way to pull it out in an afternoon, without rereading your whole mailbox.

The best answer you'll ever write, you already wrote

Sit someone down to draft what their agent should say and you get flat, brochure-ish prose. That's not a failure of effort. Writing in the abstract is nothing like answering one specific person who is about to lose their patience.

Your archive doesn't have that problem. On some Tuesday in March, when a customer asked whether a repair was covered under warranty and you took the trouble to do it properly, you produced an answer that explained the reasoning, got ahead of the next question and closed with a clear next step. That is precisely what you want the agent to be able to say.

There's a second gift buried in there: frequency. You don't have to guess which questions come up most — you can see it in how many times you've typed the same thing. If you've explained how the deposit works fourteen times, you know where to start.

Four searches that surface most of the material

The trap is reading your email chronologically. That's three days of work and you'll abandon it halfway. Go in with searches instead:

1. Your own explaining tics. Everyone has four or five. Search your sent mail for just to confirm, in principle, the price includes, the lead time, what we normally do is. In Gmail, in:sent "the price includes" works; in Outlook, search inside Sent Items. Those phrases mark the exact spot where you were explaining something.
2. The long ones. Anything you wrote over ten lines is almost always an explanation rather than a "great, thanks". Sort by size, or filter for messages with an attachment — that's where the annotated quotes and instructions live.
3. The customer's words, not yours. Warranty, refund, invoice, deposit, cancel, urgent, coverage. Find them in the thread and keep your reply.
4. Your team. Ask each person to forward you the three replies they're proudest of. It's the best half hour of the whole project, and you find out how everyone answers when you're not looking.

Cap it at fifteen or twenty threads. You're not building an archive, you're gathering raw material. If twenty good answers don't cover most of what comes in, the material isn't the problem — your business answers everything from scratch, and there's a section on that below.

You'll find three versions of the same answer

This is the part nobody expects, and it's where most of the value is. Put four replies on the same subject side by side and the contradictions jump out.

Take lead time. You say "about a week". Your colleague says "seven to ten days". The person in the warehouse says "depends on the supplier, I'll let you know". All three are reasonable. All three have gone out to customers. And the gap between them is exactly what turns into a complaint later.

This is the point to stop and decide, because an agent can't hold all three. For every cluster of contradictory replies you need two things: which one is right and who gets to say so. It's usually a ten-minute conversation you've been avoiding for two years, because until now everyone managed with their own version.

Building the knowledge base isn't a copy-and-paste job. It's the moment your business writes down what its answer actually is.

If that's the only thing you get out of the exercise, it was worth doing even if no agent ever goes live.

What must not cross over from the archive

Your sent folder is a record of private conversations, not a reference library. Strip four kinds of thing before any of it reaches the agent:

• Other people's data. Names, phone numbers, case references, anything tied to one customer's situation. You want the reply for the reasoning it explains, not for the case. Rewrite it in general terms and drop the rest — you're reusing emails containing personal data for a new purpose, and the less you carry over, the less you have to account for.
• Exceptions and favours. The 15% you knocked off for a long-standing client, the delivery you didn't charge for, the Saturday slot you opened up. Put that in the knowledge base and the agent will offer it to everyone, cheerfully.
• Anything with a shelf life. Prices, seasonal lead times, names of people who've left, terms from a supplier you've since dropped. A stale figure in an old email is harmless. The same figure in the knowledge base gets repeated a hundred times.
• Emails written on a bad day. Tense negotiations and defensive replies. The tone worked in that moment and reads terribly when it's repeated cold.

Quick test: if you wouldn't mind that answer turning up in a screenshot with your company's name on it, it can go in.

Turning a thread into something the agent can use

A pasted email works badly. It carries greetings, context from that particular case, and three paragraphs that don't apply. Give it a shape instead. This one does the job, in plain text, with all of them in a single document:

Question: is this repair covered by the warranty?
Answer: [3-5 sentences, your tone, ending in a next step]
Source: warranty terms v3 (document) / written by hand
Do NOT say: don't promise a repair date, don't rule on misuse
Review: January 2027

Two details carry most of the weight. Source separates what has a live origin — your price list, your calendar, your invoicing software — from what you typed by hand and will quietly freeze in time. And do NOT say is usually handed to you by the thread itself: if you deliberately avoided committing to a date in that email, there's a boundary the agent needs to respect.

Keep it in one place, in editable text. If it ends up as a PDF in a shared drive, nobody updates it, and six months from now the agent is quoting last year's prices.

When the sent folder is the wrong place to start

It isn't always the right door, and that's worth saying plainly:

• When your volume lives on WhatsApp. For a lot of small businesses, email is now a minority of customer contact. Run the same exercise, but where the work actually arrives.
• When every job is different. In genuinely bespoke project work, your emails are pure negotiation and there's nothing reusable in them. Start with what you answer on the phone, which is usually far more repetitive than it feels.
• When the answer depends on live data. Stock, free slots, order status. Copying an eight-month-old reply freezes a number that moves daily — that needs connecting to the source, or escalating to a person.
• When the judgement is professional and regulated. In clinical, legal or tax work, that reply was right for that case. It's useful as an internal reference, not as an automatic answer to anyone who asks something similar.

Start with the five you've typed most

Don't try to empty the archive. Take the five questions you've answered most often, rescue the best version of each, clean it up and write it as a card. That's enough to run the agent with real customers and watch what it escalates — which is the best possible list of the next five cards you need to write.

If you'd rather that material worked directly on your inbox — sorting what comes in, drafting the reply with the right answer already in it, and leaving the final call to you — that's the job of the email manager. You approve what goes out; it makes sure the same version goes out every time.