DEV Community

Cover image for A Polite Reply Is Not Work Done: Five Jobs a Chatbot Leaves Undone
Elarigent
Elarigent

Posted on AI-assisted

A Polite Reply Is Not Work Done: Five Jobs a Chatbot Leaves Undone

A customer got a polite apology from the chatbot — and nothing else. The refund never moved, the booking never changed. The reply was fast, friendly, and correct in every word. It was also the end of the job, as far as the chatbot was concerned. The customer was still waiting, and the business did not know it, because a reply had been sent and the thread looked finished.

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 — when did a polite reply leave the real job undone? — and it works through five jobs a chatbot leaves undone, using the tools people already use, so you can check my working and tell me where I got it wrong.

The difference is one word: done

A chatbot's job ends when it has answered. An agent's job ends when the work is done — or when a human has said no. That sounds like a small difference. In a normal day it is the whole difference, because most of the work a small business does after a customer writes in is not answering. It is moving money, moving dates, moving orders, and chasing the people who went quiet.

Here are five jobs, numbered, each one with the tools people already use. Each one starts with a polite reply. Each one ends with the job still waiting.

1. The refund that never moved

A customer writes on WhatsApp: the order arrived damaged, can I have my money back? The chatbot apologises, explains the returns policy, and offers a form. The customer fills in the form. Nothing else happens. The refund is a job in the bank account or in Stripe — someone has to look at the order, check the amount, and press the button. The chatbot cannot press it, and nobody told a person that a form had been filled in.

The tools are ordinary: WhatsApp for the message, Gmail for the form, Stripe or the bank for the money, a spreadsheet for the record. Each one does its part. The gap is between them — the message arrived in one place, the money lives in another, and nobody owns the step in between.

2. The booking that never changed

A customer books for Thursday at 4pm, then writes to move it to Friday at 10am. The chatbot says "Of course, I have noted your request" — and nothing is noted anywhere that matters. Thursday 4pm stays booked in Google Calendar, Friday 10am stays free, and the slot that could have gone to the next person waiting sits empty twice over: once when the customer does not come on Thursday, once when nobody offers the freed time to anyone else.

The booking page, Calendly, does its part well — the customer picks a slot themselves. But a booking page cannot handle the customer who wants something the page does not offer, and it cannot hear a change that arrives as a message. The change lives in the message thread. The diary lives in the calendar. The owner is the only bridge between them, and the owner is busy.

3. The invoice nobody chased

An invoice is fourteen days overdue. The chatbot can write a beautiful reminder — "We hope you are well, a gentle reminder that invoice 1042 is now due" — and it can write it in seconds. But a reminder that is written and never sent chases nobody. The invoice sits in the spreadsheet, the customer's email sits in Gmail, and the polite draft sits in a chat window that closed when the owner got distracted.

This is the job with no deadline on it, so it never gets done. It is also the job that would tell the owner the most: which customers pay late every time, which ones pay when asked once, and which ones have quietly stopped paying at all. A reply is not a chase. A chase ends with money in the account or a decision to stop supplying — and a chatbot does neither.

4. The follow-up that never happened

A customer asked a question on Tuesday, got a polite answer, and never bought anything. Or a customer booked, did not show up, and nobody asked why. The follow-up is the job that has no owner and no deadline, so it waits forever — and it is the job that would tell the business the most about where it leaks.

The tools make it worse, not better. WhatsApp keeps the whole conversation in one thread, which is where the customer actually is — but a message thread is not a list, and a question buried under forty other messages is a question lost. The chatbot answered the question. Nobody answered the silence that followed it.

5. The wrong order that stayed wrong

The wrong item arrived. The customer writes in, the chatbot apologises, explains how returns work, and the customer is told someone will be in touch. Nobody is in touch, because "someone will be in touch" is not a job assigned to anyone. The replacement is never arranged, the courier is never booked, the wrong item sits in the customer's hallway, and the customer tells the next person they know that this business does not fix its mistakes.

The fix is four small jobs — check the order, arrange the replacement, book the collection, tell the customer when it is coming — and each one is a step in a different tool. The chatbot did the first step, the polite one, and the other four waited for a person who never got the message.

What a workforce does with the reply

This is the kind of work an AI workforce is for — not the clever part, the ordinary part. The reply is written, and then the work behind it is done too: the refund is drafted with the amount checked against the order, the booking change is drafted against the free slots, the reminder is drafted with the invoice number and the amount in it, the follow-up is drafted for the customer who went quiet, the replacement is drafted with the courier booked. And nothing is sent before you have seen it. You read the draft, you fix a line if it needs fixing, you say yes — and the customer hears from you the same day, not the next week.

The relief is not that a machine answered faster. It is that the answer stopped being the end of the job. You still decide what counts as a refund, what counts as a change, and what counts as a chase. You still approve every word that leaves. The difference is that the moving, the checking, and the chasing are done before you sit down, so the minutes you have are spent deciding — not digging through messages to find out what was never done.

Which job goes first

The refund goes first, because money is moving and a person is deciding right now. A customer who asked for their money back and heard nothing by the end of the day is a customer who is already telling someone else. The booking change goes next, because a freed slot has a value that drops to nothing the moment the hour passes. The invoice chase follows — it is the easiest of the five to get right, because it is the same message every time, with the facts changed. The replacement and the follow-up come after, because they need a judgement call: which item to send, what to say to the person who never showed.

That order is my answer. It is also a guess, and it is the part I most want corrected.

The short version

A polite reply is not work done. A chatbot's job ends when it has answered; the five jobs behind the answer — the refund, the booking change, the invoice chase, the follow-up, the replacement — still wait for a person. The tools most businesses use each do one part well; the gap is between them, and the owner is the glue. Let a workforce do the work behind the reply, draft it all, and keep the sending in your hands: you pick the order, you approve every word, and the polite apology stops being the last thing the customer ever hears.

So — when did a polite reply leave the real job undone in your business? Which of these five would you hand over first, and which would you never hand over? Tell me in the comments. I would rather be corrected than agreed with.

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

Top comments (0)