Build the Voice File Before You Schedule the Task

We recently published module 2 of a client training portal. The module covers two things: connecting Claude to Outlook and then putting Claude on a schedule. The output is a weekday inbox triage that groups mail by urgency and writes real draft replies before the client sits down.

Simple concept. The interesting part was what had to happen before the schedule.

The Problem with Generic Triage

Scheduled tasks in Claude work the same as any other Project. You give it instructions, it runs them on a timer. Hook it to Outlook, point it at the inbox, tell it to triage by urgency and write drafts. Claude will do it.

But the drafts will sound like Claude, not like the person who's supposed to send them.

That's a problem that compounds. If the client has to rewrite every draft from scratch, the scheduled task saves them nothing. If they edit lightly and send something that sounds generic, their growers notice. Agricultural supply is a relationship business. "Professional and warm" reads different from "how we've been talking for eight years."

The fix is a voice file.

What the Voice File Prompt Does

The prompt we built asks the client to paste in five or six real emails they've written recently, then produces a single markdown document that describes how they write. Not how they should write. How they actually write.

The instruction to Claude is specific: do not rewrite them, do not grade them, do not suggest improvements. Just study and describe.

Six sections come out: how they open, how they sound, words they use, how they handle hard conversations, how they close, and a short rules block written directly as instructions for the scheduled task.

That last section is the piece that plugs into the triage prompt. The scheduled task references the voice file. Now the drafts have the right opener, the right sign-off, the right level of directness.

One rule goes in every voice file by default: never state a price, availability, product rate, or delivery date that isn't in the source material. Put a [CONFIRM: ...] placeholder instead. That guardrail is especially important in ag supply, where price and availability can shift week to week.

Why This Comes First

You can set up the connector and the schedule in twenty minutes. The voice file takes longer because it requires real emails, and most clients have to go find them.

But skipping the voice file means the schedule ships incomplete. The triage logic works, the urgency grouping works, and the drafts are technically coherent. They just don't sound right.

We teach this in sequence in the training: here's how to connect Outlook, here's the triage prompt, but before you turn on the schedule, do this voice file exercise. Once it's done, you upload it to the Project and the scheduled task references it on every run.

The schedule is easy. Getting the voice right is the actual work.

The Pattern Generalizes

This comes up any time you're scheduling a Claude task that produces client-facing or stakeholder-facing output. The automation setup takes an afternoon. Building the artifact, the voice file or the style guide or the tone calibration document, that's the real deliverable.

We're building more modules for this client around exactly that principle: do the calibration work once, reference it everywhere.