How Do I Know My Automation Stopped Before It Costs Me Clients?
Invoices not sent, enquiries reaching nobody, reminders not going out: three questions, a weekly report and one alert that tell you an automation has stopped.
- Automation
- Monitoring
- Business Owners
- HARDEN
In short
- An automation that stops rarely sends an error, so the first sign is usually a client asking where their invoice, answer or reminder is.
- An owner can notice a stop without technical knowledge: compare two numbers, ask one person one question, or look at one screen that is already there.
- In our own case a morning automation stopped halfway three days in a row, about a third of the checks we pay for were lost, and I found out on day 3, by chance.
- Ask whoever maintains your automations where the record of each run is, who is alerted when a run does not happen, and what healthy means for each one.
Invoices that stop going out. Website enquiries that land in a mailbox nobody reads. Booking reminders that quietly stop, so clients forget and the chair stays empty.
None of these announces itself. You find out when a client phones to ask where their invoice is, or when the money does not arrive. By then it has cost you clients, cash and a little reputation.
This article is for owners who rely on automations and do not want to read technical logs. Here is how to notice a stop yourself, what to demand from the person who maintains them, and what you can do this week.
A stopped automation looks exactly like a quiet day
Picture a bakery where the oven did not start this morning. Nobody hears an error. There is simply no bread, and the shop looks calm until the first customer asks.
Automations behave the same way. When one is broken loudly, you hear about it. When it just stops, nothing rings, and the day looks like any other.
The cause is often ordinary. The program your automation runs on has a limit on how long one job may run, and when the job reaches it, it simply stops. Alerts, meanwhile, are usually set to ring on an error, not on a stop.
Three ways to notice it yourself
You do not need technical knowledge. You need one number that should exist every day, and the habit of looking at it.
Imagine three businesses:
| Business | What should happen | The two numbers to compare |
|---|---|---|
| An accounting firm | Invoices go out on the 1st | Invoices created, invoices sent |
| A clinic | Reminders go out the evening before | Appointments tomorrow, reminders sent |
| An online shop | Website enquiries reach someone | Enquiries on the site's own statistics, enquiries received |
If the two numbers differ, something stopped. If you cannot find the second number anywhere, that is the finding.
There are two more ways, both cheap. Ask the person who maintains the automation one question: "How many went out yesterday?" A good answer comes within minutes and with a number. Or open one screen you already have, such as the sent folder, and check that today's items are in it.
What it looked like when it happened to us
The damage was small: lost checks, not lost clients. The pattern is the one that hurts a real business. The job stopped, it said nothing, and the person who found out was whoever happened to look.
For an accounting firm, the same stop would be a week of unsent invoices. For a clinic, a week of empty slots.
Three questions to ask whoever maintains your automations
Your freelancer, agency or IT person should answer these without hesitation. A good answer is specific. A bad answer is a reassurance.
| Question | A good answer sounds like | A bad answer sounds like |
|---|---|---|
| 1. Where is the record of every run? | "One line per run: start time, end time, how many items. I can show you yesterday's." | "It would show up if something went wrong." |
| 2. Who is told when a run does not happen? | "Anna, by message on her phone, within an hour." | "It would be in the error list." |
| 3. What does healthy mean for each automation? | "By 9:00, at least as many reminders as bookings for tomorrow." | "It is working fine." |
The second question matters most. Telling you about an error is the easy part. Telling you about something that did not happen needs a person or a check that looks at the clock and says: this should be done by now.
This is not complicated. Ready-made services do exactly this: they stay quiet while everything arrives on time and message you the moment something is late (Healthchecks.io, for example).
The weekly report you should receive
Once a week, without asking, you should get a short message with counts. Not a technical log. For example:
- Invoices created and invoices sent, side by side.
- Enquiries received this week, and how many were answered.
- Reminders sent against bookings made.
- Any day when an automation did not run, or ran late.
If a count is missing from your report, either nobody measures it or nobody wants to show it. Both are worth knowing.
A checklist for this week
- List the automations that touch money or clients: invoices, enquiries, bookings, reminders, offers.
- For each one, write the number that should appear every day.
- Send the three questions above to whoever maintains them, and ask for written answers.
- Ask for the weekly report with counts, to arrive on the same day each week.
- Ask for the alert to go to one named person, then ask them to stop one automation on purpose, with you watching, to see that it arrives.
- Book five minutes every week to look at the report.
How we help
We start with analysis: which processes you run, where a stop would hurt most, and what "healthy" means for each. Then we automate the whole process, not only one step, and we build the checks into it.
We do this with the HARDEN method (the method in full). Its phases include Break, where we try to break an automation before launch, and Monitor, where the records, rules and alerts live. The Bulgarian pages of the AI Ready Standard describe our approach to process automation (in Bulgarian). The checks that watch our own work are described in the systems we built to deliver reliable automations, and the same worry applies to a website form that may not reach you.
Your next step is item 1 of the checklist: take ten minutes today and write down the automations that touch your clients. If you want a second pair of eyes, look at our process automation service.
Questions and answers
Can an automation stop without telling anyone?
Yes. Alerts are usually set up for errors, and a job that is cut short or never starts is not always an error. Silence on your side proves nothing, so a person or a check has to notice that something that should have happened did not.
How can I check my automations without technical knowledge?
Compare two numbers that should match, such as invoices created and invoices sent, or ask the person who maintains them how many went out yesterday. You can also open one screen you already have, like the sent folder or a booking list.
What does a healthy automation mean?
It is one or two rules for that automation that you can read in a sentence, for example that by 9:00 it has handled at least a set number of items. A weekly report should show whether each rule held.
Who should receive the alert when an automation stops?
A named person, through a channel they actually see during the day, such as a message on their phone. An alert to a shared mailbox nobody reads is the same as no alert.