DEV Community

Cover image for What Part of Your Diary Would You Hand Over First?
Elarigent
Elarigent

Posted on AI-assisted

What Part of Your Diary Would You Hand Over First?

A customer tried to book on Tuesday. By Thursday they had gone elsewhere — not because you said no, but because nobody said yes in time. The booking page was buried, the reply came late, and the diary kept its secret: there was a free slot on Thursday at 4pm, and nobody told the customer. That is the diary's job, and most small businesses still do it by hand, in the gaps between the real work.

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 part of your diary would you hand over first? — and it works through the diary job by job, using the tools people already use, so you can check my working and tell me where I got it wrong.

The diary holds five jobs, not one

The first mistake is treating the diary as one job. It is five jobs that happen to live on the same page.

1. The booking request. A customer asks for a time. It arrives as a message at 9:14am — "Thursday at 4pm, if you have it?" — or a call while you are with someone else, or a note on the booking page you check twice a day. The job is to catch it before the customer asks someone else.

2. The confirmation. Telling them they are in, with the facts: the date, the time, the address, what to bring, what it costs to change. A confirmation with the facts in it is a promise the customer can plan around. A confirmation without them is a reason to call back and ask.

3. The reminder. The day before, a short message: tomorrow, 4pm, see you then. This is the job that stops the empty slot — the hour you kept free, the room you set up, the customer who forgot. It is also the job that gets skipped first, because it feels like nagging. It is not nagging. It is the difference between a full day and a hole in it.

4. The change. The customer moves it. Thursday 4pm becomes Friday 10am, and now Thursday 4pm is free again — but only if someone notices, and only if someone tells the next person waiting. A diary that does not handle changes is a diary that quietly loses bookings twice: once when the customer moves, once when the freed slot sits empty.

5. The follow-up. The booking that never got made, and the customer who never showed. Someone asked, nobody answered, and nobody knows. Or someone booked, did not come, and nobody asked why. This is the job with no deadline on it, so it never gets done — and it is the job that would tell you the most about where the diary leaks.

Five jobs. Five different kinds of waiting. The request waits minutes. The confirmation waits hours. The reminder waits a day. The change waits until someone notices. The follow-up waits forever, because nobody is waiting for it at all.

What people use today

Most small businesses run the diary on tools that each do one part of it. A paper diary by the phone: nothing to charge, nothing to learn, and it cannot remind anyone of anything. Google Calendar: the times are visible to everyone on the team, and it sends a reminder — but it cannot answer the customer who asked. Calendly or a booking page: the customer picks a slot themselves, which is the best version of the request — but it cannot handle the customer who wants something the page does not offer, and it cannot chase the one who never confirmed. WhatsApp or text messages: where the customer actually is, and where the whole conversation lives — but a message thread is not a diary, and a booking buried under forty other messages is a booking lost.

None of these is the wrong tool. Each one does its part well. The gap is between them: the request arrives in one place, the diary lives in another, the reminder is a third job done by memory, and the follow-up is a fourth job that nobody owns. The owner is the glue — and the owner is the one person in the business who is already busy.

What a workforce does with the diary

This is the kind of work an AI workforce is for — not the clever part, the ordinary part. The diary is watched while you do the real work: a booking request is read and matched against the free slots, a confirmation is drafted with the facts in it — date, time, address, what to bring — and a reminder is drafted for the day before. The change is handled the same way: the old slot is freed, the next person waiting is told. Nothing is confirmed 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 kept the diary. It is that the diary stopped being five jobs held together by one busy person, and became five small jobs with an order. You still decide what counts as a booking. You still approve every word that leaves. The difference is that the catching, the drafting, and the reminding are done before you sit down, so the minutes you have are spent deciding — not digging through messages.

Which part goes first

The booking request goes first, because a person is deciding right now. A customer who asks at 9:14am and hears nothing by lunch is a customer who is already asking someone else. The confirmation goes next, because a customer who does not know they are booked cannot plan around it. The reminder follows — it is the easiest of the five to get right, because it is the same message every time, with the facts changed. The change and the follow-up come after, because they need a judgement call: which slot to offer, 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 diary is not one job — it is five: the request, the confirmation, the reminder, the change, and the follow-up. Each one waits differently, and the request costs the most to leave waiting, because a person is deciding right now. The tools most businesses use each do one part well; the gap is between them, and the owner is the glue. Let a workforce watch the diary, draft the confirmations and reminders, and keep the sending in your hands: you pick the order, you approve every word, and the booking that never got made stops happening.

So — what did I get wrong about your diary? Which part would you hand over first, and which part 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)