Mail that sorts and chases itself

Mail is where most people's automation starts, and where most of it goes wrong, because the inbox is the one place where a mistake is visible to somebody else. This lesson keeps the risky part in your hands and hands over the rest — which turns out to be most of it.

Sorting first, sending later. The safest automation in mail moves things around without saying anything: label an enquiry, file a receipt, push an attachment into the right folder, add a line to a tracking sheet. Nothing leaves your name, nothing is irreversible, and you get a week of watching the filters behave before anything is sent on your behalf. Do this for a fortnight before you let a flow write to a human.

The follow-up chase is the highest-value flow in this lesson, and the one to build most carefully. The shape: when a quote is sent and no reply has arrived in five working days, raise a task for you — not a message for them. The machine watches the clock; you write the nudge. That split is deliberate. The watching is what humans are bad at and the writing is what they are good at, and a chase that sounds automated is worse than no chase at all.

When you do let a flow send, three rules make it safe. Send to yourself first for a week, with the real recipient in the body, so you can see exactly what would have gone out. Never send on a trigger you do not control — a flow that replies to any incoming mail can be provoked by anyone who learns it exists. And put a human-visible delay in: fifteen minutes between the trigger and the send is invisible to the recipient and gives you time to stop it when you notice it is wrong.

What not to automate here, stated plainly. Anything with a price in it. Anything with an apology in it. Anything to someone you have never written to before. The common thread is that these are the messages where tone carries the meaning, and tone is the first thing a template flattens. Automating the record of them is fine; automating the message is not. The test that settles most cases: imagine the recipient learning a flow sent it. For a delivery notice filed to a log, they would not care. For a reply to a first enquiry, they would feel handled rather than answered — and that feeling arrives exactly where you were trying to begin a relationship.

One habit that pays for itself: let the flow write the draft, not the send. Most mail tools can create a draft that sits in your outbox waiting. You get the assembly done — the right recipient, the reference number, the attachment already pulled in — and the sentence that matters stays yours. This is the pattern the rest of the course generalises: hand over the assembly, keep the judgement.