The fifteen-minute Monday review that keeps automation alive

Nobody switches off an automation on purpose. It fades. You put your prices up and never touch the agent's handbook. You add a service in September and the agent is still quoting the May catalogue. Someone on reception starts answering messages herself because "it's quicker", and three months later the agent is handling half of what it handled before. Nobody decided any of that. There simply wasn't a moment in the week when anyone looked. This piece is about that moment: fifteen minutes on a Monday, with a script, two people and exactly one change a week.

What rots isn't the agent, it's the handbook

A well-built agent doesn't get worse over time. The business underneath it changes, and the agent stays exactly where you left it. That happens in three ways, and all three are quiet.

The handbook ages. Prices, opening hours, local bank holidays, who handles what. These are small changes nobody files under "system update", so nobody tells anyone. The agent keeps confidently repeating something that stopped being true six weeks ago.

Exceptions quietly become the rule. At first there's one odd case a month that a human sorts out. Then it's three a week. Nobody notices the pattern is now routine, so nobody adds it to the rules, and that task drifts back to being manual without a single decision being made.

The owner stops looking. This is the most common and the most expensive. Early on you read every conversation, then one in ten, then none. The day something goes wrong you hear about it from a customer, and there are three weeks between the two events.

None of these is a technology problem. All three are fixed by a recurring slot in the calendar.

Four numbers and one sentence

Fifteen minutes doesn't buy you a report. It buys four numbers and a direct quote. If pulling them takes more than two minutes, that's your first thing to fix — you can't manage what you can't see.

1. Volume. How many conversations the agent handled this week. It only means anything next to last week's figure. A thirty percent drop with no obvious cause (a holiday, a seasonal dip) usually means something broke at the front door, not inside the agent.
2. How many a human touched. The number that actually tells you whether hours are being saved. If it climbs week after week, the handbook has fallen behind.
3. How long the human took when it was their turn. An escalation answered in ten minutes is a working system. One answered the next morning is a lost customer with extra steps.
4. How many ended where you wanted. Appointment booked, quote sent, document received, order resolved. Without this, the other three measure activity, not outcome.

Then the sentence: the ugliest complaint of the week, copied exactly as the customer typed it. Don't summarise it, don't soften it. "This is my third message and I still don't know anything" tells you more than any percentage, and it's the only part of the meeting anyone still remembers on Thursday.

The script, minute by minute

The structure matters more than it looks, because without it the fifteen minutes vanish into the first anecdote anyone brings up.

Minutes 0 to 3 — the numbers, read out, uninterpreted. All four plus the quote. Nobody explains yet, nobody defends anything. You just say them.

Minutes 3 to 8 — three random conversations, read in full. Genuinely random: the most recent one, one from midweek, one from the weekend. Read them end to end, not skimmed. This is where you find what no metric shows: the agent greeting people twice, being stiffly formal with someone writing in one-line shorthand, asking for account details before it knows whether the customer wants anything.

Minutes 8 to 12 — what changed in the business. The literal question is: "what does the team know this week that the agent doesn't?" A promotion, a supplier running late, someone away for a fortnight, a product out of stock. This prevents most failures and it's the step people skip first.

Minutes 12 to 15 — one change, with a name and a date. One thing gets decided, one person owns it, one deadline. Written in a single line. Done.

The one-change rule

One change a week. It sounds unambitious and it's the opposite: it's fifty changes a year to a system that, if you rewire three things at a time, will never tell you what helped and what hurt.

Change the welcome message, adjust the escalation rules and add three new answers on the same Monday, and if human interventions spike on Tuesday you have no idea which of the three did it. With one change, next week's number answers the question for you.

If there's no change worth making this week, don't invent one. A review that ends in "leave it as it is" is a result, not a failure.

The obvious exception: if something is sending customers incorrect information, that gets fixed today, doesn't wait for Monday, and doesn't count as the change of the week.

Who's in the room, and who isn't

Two people. Whoever catches the flak when the agent gets it wrong — usually whoever runs the inbox or the front desk — and whoever can approve a change without asking anyone. If that's the same person, better still: fifteen minutes alone with the script works just as well.

Who isn't in the room: the whole team. A seven-person meeting to review a chatbot is precisely the kind of meeting that makes people hate meetings, and it gets cancelled within two months. Standing up, no screen share, no long minutes — one line with the decision and the owner's name.

When you can skip this

• Under about twenty conversations a week. At that volume there's no weekly signal to read. Do it monthly, same script.
• In your dead season. If January or August is when your business goes quiet, reviewing automation every Monday is theatre. Restart it when the volume comes back.
• When the setup was wrong from the start. This ritual keeps a working thing working; it won't rescue an agent that never fitted. If three Mondays in a row reach the same conclusion, you don't have a maintenance problem — you have a process to rethink.
• When a month has passed with no changes and no complaints. Congratulations: move to fortnightly. The point isn't the meeting, it's that nothing rots.

What you actually get

No individual week looks important. The difference shows up at six months, between the business that spent fifteen minutes every Monday and the one that set up an agent in March and walked away. The first has a system still doing its job, and knows why. The second has a half-working thing that answers so-so and nobody quite trusts any more.

If setting this up reveals you can't even pull the four numbers, start there. Our operations agent exists for exactly that kind of internal work — keeping things measured and flagging when something drifts out of normal — which is half of this meeting already done before you sit down.