Dev.to AI 🤖 Ai 👁 0 📖 5 min read

Which Message Would You Never Let Send Itself?

Yesterday's article named five updates a small business forgets to send — each one a sentence in WhatsApp. This morning's post asked the question underneath them: the hard part was never writing the messages. It is decid

Yesterday's article named five updates a small business forgets to send — each one a sentence in WhatsApp. This morning's post asked the question underneath them: the hard part was never writing the messages. It is deciding which ones go out. Because some messages, sent wrong, cost more than silence ever did. A quote with the wrong number in it. An apology that reads like a shrug. An "it's ready" sent before the work is done. Every owner has sent one of these — or caught one at the last second, finger hovering over send, and thought: not this one. Not like this. The catch is the whole job.

This article was drafted with AI assistance. It is written in plain English for people who run businesses, not for people who build software, and it makes no claim about any particular product. It works through five messages I would never let send themselves, using the tools people already use, so you can check my working and tell me where I got it wrong.

The test is a short one. A message can go out on its own when getting it wrong is cheap — a nudge, a reminder, a "we got it". A message waits for a human when getting it wrong costs a customer, money, or trust. That is the whole test, and it fits on one line. Here are five messages that fail it, in the order I would check them.

1. The price — the quote with the wrong number

A customer asks what it costs. You work it out, you type it into WhatsApp, you press send before you have read it back. One wrong digit and the quote is a promise you cannot keep — or a price so high the customer never replies, and you never find out why.

The check takes ten seconds: read the number out loud, compare it with the job, and check who it is going to. A quote is a promise with a number on it, and a number typed in a hurry is the easiest promise in business to get wrong. This is the message I would check first, every time, because the cost of getting it wrong is written into the message itself.

2. The apology — "sorry" that reads like a shrug

Something went wrong. The delivery was late, the order was wrong, the appointment slipped. The customer is upset, and upset customers read every word twice. A drafted apology that sounds copied — "we apologise for any inconvenience" — tells them nobody actually looked at what happened to them.

The check is a question you ask yourself before you send it: would I say this to their face, standing in their shop, with them looking at me? If the answer is no, rewrite it. An apology is the one message where the tone is the message. Get the tone wrong and you have not apologised — you have confirmed that you do not care, in writing, with your name on it.

3. The "it's ready" — sent before the work is done

The job is nearly finished. The message says it is ready. The customer sets off, arrives, and finds it is not ready — a part is missing, a step is unfinished, someone forgot to check. Now you have two problems: the unfinished job, and a customer who was told a thing that was not true.

The check is the simplest of the five: has someone actually looked at the finished work? The message is only true if the work is. "It's ready" is a claim about the real world, not about the diary, and no system should make a claim about the real world without a human who has seen it. This one waits until eyes have been on the job.

4. The money chase — "your payment is overdue"

Chasing money is the message most likely to go to the wrong person, with the wrong amount, on the wrong day. The customer who paid yesterday gets a reminder today. The amount is last month's, not this month's. The reminder goes to the person who never handles payments, and the person who does never sees it. Each version ends the same way: a good customer who feels accused, and an owner who only finds out when the customer calls, angry.

The check has three parts, and all three are human: is this the right person, is this the right amount, is today the right day? A reminder that passes all three is a normal part of business. A reminder that fails any one of them is a relationship ending in a sentence. Money messages are where politeness and accuracy have to arrive together, and that is a human judgment, not a scheduled one.

5. The bad news — the delay, or the price going up

The job will be late. The price has to rise. Somebody has to tell the customer, and the telling matters as much as the news. A delay announced on a Friday evening reads differently from the same delay announced on a Tuesday morning with a new date attached. A price rise with no reason reads differently from the same rise with one honest sentence about why.

The check is the hardest of the five, because it has no right answer, only a better one: would I want to receive this message, in these words, today? If you would not, the message is not ready — and no amount of drafting makes it ready without you. Bad news is the message where the owner's judgment is the whole product. It cannot be handed over, because the judgment is the thing the customer is actually paying for: someone who cares enough to tell them properly.

The short version

Five messages wait for a human: the quote with the wrong number, the apology that reads like a shrug, the "it's ready" sent before the work is done, the money chase to the wrong person, and the bad news told badly. Each one lives in a tool people already use — WhatsApp, Gmail, a phone call, a paper note — and each one fails the same short test: getting it wrong costs a customer, money, or trust. Let a workforce draft them as the work happens, and keep the sending in your hands: you check the number, the tone, the timing, and the truth of it, and the message only leaves when you say so.

So — which message would you never let send itself? Which of these five is yours, and is there a sixth I missed? Tell me in the comments. I would rather be corrected than agreed with.

Ready-made AI agents for small businesses, built in public.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.