Dispatch September 15, 2026

Let the Machine Draft, You Keep the Send Button

You're at the counter between customers, phone in hand, typing out a reply you've already sent a hundred times. Same question about your hours, same 'yes, we can fit you in Thursday,' same directions to the shop. It isn't hard. It's just you, again, doing the part a trained parrot could handle.

Meanwhile the messages that actually need you sit in line behind the parrot work. The refund a customer's upset about, the apology for the job that ran long, the quote you want to word just right. By the time you reach them you're tired and rushing, which is exactly when the wrong tone slips out.

There's a split that fixes this, and it's older than any software. Let the machine write the first draft of the routine stuff. Keep your hand on the send button for anything with money, an apology, or bad news in it. Machines do the relay. You do the judgement.

The line to draw: who owns the send button

Here's the rule worth sticking to your monitor: a person sends anything that carries money, an apology, or bad news. Everything else is fair game for a draft.

Think about why that line sits where it does. A booking confirmation is a fact. You're either open Thursday at ten or you're not, and there's no tone to get wrong. A message telling a loyal customer their part is delayed two weeks isn't a fact, it's a relationship, and it needs a human who can read the room.

The machine is genuinely good at the first kind. It can turn 'confirm the Miller appointment' into a warm, correct, on-brand message faster than you can find your reading glasses. It's genuinely risky at the second kind, because it has no idea the Millers are the family whose kitchen flooded last month and who don't need one more thing going sideways.

Anything in this circle stays in your hands:

  • Money: refunds, price changes, a bill that came in over the quote, anything touching a deposit.
  • Apologies: you ran late, the part was wrong, the crew tracked mud down the hall.
  • Bad news: a delay, a cancellation on your end, a no you have to deliver.

Everything outside that circle, the confirmations, the directions, the 'we got your message and we'll call you back this afternoon,' can start life as a draft and save you the typing.

Where a drafting robot buys back real hours

Savings show up wherever you send the same shape of message over and over.

  • Appointment confirmations and reminders.
  • 'Yes, we cover your area' and 'sorry, we're booked till the 12th.'
  • First replies to a web form or a missed call, the 'we got you, here's what happens next.'
  • Directions, parking notes, 'text me when you're five minutes out.'
  • Routine follow-ups: 'your invoice is attached,' 'here's the link to book.'

Figure the math yourself. If you tap out forty of these a week and each eats two or three minutes of thinking and typing, you're spending a couple of hours a week being a parrot. A draft that's ninety percent right turns those minutes into a ten-second glance and a tap.

None of these carry money, an apology, or bad news, so a quick read is all the oversight they need. Some you'll trust enough to let go out on their own after a while. Most you'll want to eyeball first, and that's fine, eyeballing is fast.

Where it costs you hours instead

Now the honest part, because this is where owners get burned.

A draft isn't free. Somebody has to read it, decide if it's right, and fix it if it isn't. For a routine confirmation that's a great trade. For a delicate message it can be a terrible one, because editing a draft that's aimed slightly wrong is often slower than writing the right thing from scratch.

Machines write fluent, confident, and a little generic. On an apology, generic reads as insincere, and insincere makes an upset customer angrier. You end up rewriting every line, and now it's taken longer than if you'd just picked up the phone.

It also doesn't know what it doesn't know. Ask it to answer a refund question and it'll cheerfully invent a policy, quote a number, or promise a timeline you never agreed to. If that goes out under your name, you own it. That's the whole reason the send button stays in a human hand for anything with money in it.

So a drafting robot loses you time when:

  • The message needs facts only you have, like this customer's history or the real reason for the delay.
  • Tone is the entire job, like an apology or a tricky no.
  • Getting it wrong is expensive: a wrong number, a promise you can't keep.

Set up the approval step so it takes seconds

This split only works if approving a draft is faster than writing one. If your review step means logging into a dashboard and hunting for the message, you'll quietly stop doing it by Wednesday.

  • Bring drafts to where you already are. Your texts, your email, your phone. Not one more app to check.
  • Make approve one tap, and let you edit in place. Change a word without leaving the message.
  • Sort by stakes. Let plain confirmations go out on their own; route anything touching money, an apology, or bad news into a 'needs you' pile.
  • Keep a short leash at first. Review everything for a week or two, watch what it gets wrong, then loosen where you've earned the trust.

Aim for a two-minute pass over the morning's drafts with your coffee, not a task that pings you all day.

Keeping it sounding like you, not a template

One more thing decides whether this sticks: the drafts have to sound like you, or you'll rewrite them and lose the savings you came for.

Feed it your real words. Paste in ten or fifteen messages you've actually sent, the good ones, and tell it to match them. Short if you're short. A little dry if you're dry. If you sign off 'thanks, Dave,' it should too.

Watch for the tells. Robots love 'we apologize for any inconvenience' and 'please don't hesitate to reach out.' Nobody you'd hire talks like that. Cut those lines and the draft stops smelling like a form letter.

Be honest about the ceiling, too. Even a well-trained draft is a starting point for the routine stuff, not a stand-in for your judgement on the messages that matter. The machine handles the relay. The reading-the-room part is still yours, and it always will be.

Worth doing this week

Five steps, none of them long:

  1. Draw the circle. On a sticky note: money, apology, bad news means I send it myself. Under that, list your three most-repeated routine messages as fair game for drafting.
  2. Pick the highest-volume one, probably confirmations or first replies, and set up a draft for that message only. Leave the rest alone for now.
  3. Feed it ten real messages you've sent so the drafts come out in your voice.
  4. Review every draft for one week and jot down what it got wrong.
  5. After the week, decide which drafts can send on their own, which still need your glance, and which message types should never be drafted at all.

That's the kind of setup we build at TellRobots: the machine drafts, you keep the send button. You can also start it yourself this week with the tools you already pay for, and honestly, that's a fine place to begin.

More dispatches →