DEV Community

Cover image for The Check Before the Reply: What You'd Never Skip Before Answering a Customer
Elarigent
Elarigent

Posted on AI-assisted

The Check Before the Reply: What You'd Never Skip Before Answering a Customer

You promised delivery by Friday — then found the shelf empty. The customer heard "Friday" and planned around it. You heard "Friday" leave your mouth and only afterwards went to check whether it was true. The reply went out before anyone checked the stock, and now the choice is between a late delivery and an awkward phone call. Nobody meant to break a promise. The promise was made before the facts were known.

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 is about the question this morning's post asked — what check would you never skip before answering a customer? — and about why the answer is usually a small habit, not a big system.

The reply went out before the check

Most broken promises in a small business do not start with a lie. They start with a fast reply. A customer asks, "Can you deliver by Friday?" and the honest answer is, "I think so — let me check." But the inbox is full, the phone is ringing, and "Yes, Friday" is quicker to type than a check. So the reply goes out, the customer plans around it, and the check happens afterwards — on the shelf, in the diary, in the supplier's inbox — where it finds the truth too late.

The cost is not the late delivery. It is the second message: the one that says "actually, Monday". That message costs more trust than a slow first reply ever would. A customer can wait a day for an answer. They cannot un-hear a promise.

The checks that matter

Before any promise goes out, four things are worth knowing. First, do we have it — the stock, the part, the room, the slot. Second, can we do it by when we said — the diary, the supplier, the person who actually does the work. Third, is the price right — the number you quoted, not the number you remember. Fourth, who is responsible — a name, not "someone will handle it".

None of these checks is hard. Each one takes a minute, sometimes less. The shelf is either full or it is not. The diary either has Friday free or it does not. The hard part is doing the check before the reply, not after it — because once the reply is sent, the check stops being a question and starts being damage control.

What a workforce does with the check

This is the kind of work an AI workforce is for — not the clever part, the ordinary part. The enquiry comes in, and the work starts while you are doing something else: the facts are pulled together in one place — what is on the shelf, what the diary says, what the price is — and the reply is drafted with those facts in it. If the stock is not there, the draft says so honestly, and suggests the date that is true. Nothing goes out before you have seen it. You check the facts, you fix a line if it needs fixing, you say yes — and the customer hears a promise you can keep.

The relief is not that a machine wrote the words. It is that the promise stopped depending on a memory of the shelf. The check happened first, the reply came second, and the only thing left was the one-minute decision that only you can make.

Make the check a habit

A habit beats a reminder. Before any reply that makes a promise, ask the four questions out loud: do we have it, can we do it by then, is the price right, who is responsible? If the draft in front of you cannot answer one of them, do not send it — send the question instead. "Let me check the stock and come back to you by 3pm" is a better reply than a Friday that never arrives.

And keep the checks where you can see them: one list of what is promised, one list of what is actually available. A promise you can see against the facts is a promise you can keep. A promise made from memory is a promise made in the dark.

The short version

A broken promise usually starts as a fast reply sent before the facts were checked. Four checks matter before any promise goes out: do we have it, can we do it by then, is the price right, and who is responsible? Let the AI workforce pull the facts together and draft the reply, and keep the sending in your hands: you check the facts and say yes, and the customer hears a promise you can keep. A slow, checked reply beats a fast, broken one — every time.

So — what check would you never skip before answering a customer?

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

Top comments (0)