Three automations work in almost any business regardless of sector: capturing an enquiry, sending a reminder, and a report that sends itself. What each does and needs.
Key takeaways
- Capturing inbound enquiries has the fastest payback, because a lost lead costs more than an hour.
- Reminders save twice: fewer no-shows and fewer chasing calls.
- A report that sends itself removes the request for updates, not only the report preparation.
- All three need one data source, so they are viable even in a business with no systems.
- What decides the outcome is not the tool but who owns it when one stops working.
Three automations recur in almost every business regardless of sector: what happens to an incoming enquiry, who reminds the customer, and who prepares the report. All three are short to build, all three measure themselves, and all three solve something the owner is already doing by hand - which is what makes them the sensible starting point.
One: capturing an inbound enquiry
The flow: an enquiry arrives from a form, from WhatsApp or by phone - and is recorded automatically in one place, with source, time and status. A first reply goes to the customer, and a task is created for whoever should call back.
What this solves is not time but loss: enquiries falling between two channels, a customer who wrote on WhatsApp on Saturday and got a reply on Tuesday, and no way to know how many enquiries there were at all. The method for recording source without relying on analytics is in lead source tracking without analytics.
What it needs: an identified form or channel, one place to record, and one reply sentence. That is all.
Two: an automatic reminder
An appointment reminder, a payment reminder, or a reminder for a missing document. The same mechanics in all three: an event with a date, a message sent ahead of it, and a record that it went.
| Reminder type | When it sends | What it prevents |
|---|---|---|
| Appointment | 24 hours before | A no-show and a confirmation call |
| Payment | Before and after the due date | The first collection call |
| Missing document | 3 days after the request | A process stalling quietly |
| Renewal | Two weeks before | A subscription lapsing unnoticed |
Choosing between SMS, WhatsApp and email depends on the audience and the message type, and the operational comparison is in SMS vs WhatsApp vs email for reminders. More important than the channel is that the reminder stops when the event is cancelled - a reminder for a meeting that is not happening costs more than sending nothing.
Three: a report that sends itself
Not a new report - the same report somebody prepares by hand every week, sent automatically on a fixed day and time. A handful of lines, to whoever needs to read them.
What this removes is not only preparing the report but the request for it: when an update arrives by itself every Sunday morning, the "what is the status of X" questions decline without anyone deciding so. The full logic, including what belongs in such a report and who maintains it, is in scheduled reports instead of asking.
What all three share
- One data source - no system integration required.
- A simple rule that fits in a sentence.
- A visible result within two weeks.
- Easy measurement - how many enquiries, how many no-shows, how many update requests.
- Non-destructive failure - if they break, you revert to manual for a day.
That last point is what makes them suitable as firsts. An automation whose failure stops the business is not where to start without experience, and what happens when something breaks is covered in automation runbooks and alerting.
What each one returns, in numbers
| The automation | Measured before | Measured after |
|---|---|---|
| Enquiry capture | How many enquiries were recorded this month | How many recorded, and time to first reply |
| Reminder | How many no-shows or late payments | The same number, a month later |
| Scheduled report | Preparation time, and update requests | Zero preparation, and how many requests remain |
The left column is the one most businesses do not hold, which is why they struggle to justify the next automation. One number recorded before starting - even a rough estimate - turns the conversation about the second automation from a feelings conversation into a data conversation.
Worth noting that in the first row the number usually rises after rollout rather than falls. That is not a failure but the opposite: enquiries that were previously never recorded start being counted, and the gap between the numbers is exactly the information that was being lost.
In what order should they be built?
By what hurts most, with one rule: the first should be the one whose number you already know. If you know how many no-shows there were this month, the reminder is the right start - because in a month you will know whether it worked.
If no number is known, enquiry capture comes first, because it is the one that starts counting. After a month of recorded enquiries there is a basis for the next decision, and that is usually worth more than the hours it saved itself.
What each one needs to actually work
| The automation | What must exist | What breaks it |
|---|---|---|
| Enquiry capture | An identified channel and one place to record | A new channel opened and never connected |
| Reminder | An event with a date in a system | A cancellation that never reaches the automation |
| Scheduled report | A stable data source | A renamed column or sheet |
The second row is what generates complaints. A reminder sent for a cancelled meeting does more damage than sending nothing, so the cancellation has to travel through the same place the meeting was booked - not a phone call nobody recorded.
The third row is the quietest: a report that stops being populated keeps arriving empty or partial, and recipients learn not to look at it. So it is worth having the report include the number of records it read - one line that reveals immediately that something broke.
What not to do in the first three
Do not chain them together. Three independent automations that each work alone is a stable state; a chain where the second depends on the first doubles the failure points exactly when there is no experience yet in finding them.
Do not add conditions. The first version should handle the normal case only, and exceptions continue by hand. A condition added in the first week is nearly always based on a guess, and it is the one that will break.
And do not automate a process that is still changing. If you changed how enquiries are handled twice in the last three months, stabilise first and automate after.
Sources
Frequently asked questions
Which of the three pays back fastest?
Enquiry capture, almost always. One lead that was not lost returns more than any hours saved, and in businesses where enquiries are scattered across channels the loss is larger than it appears until you start counting.
Do you need a dedicated automation tool?
Not necessarily. In many businesses these three are built from tools already in place - a form, a sheet, and a messaging system. A dedicated tool starts paying off when several processes exist and need shared monitoring.
What happens when a customer replies to a reminder?
Somebody has to see it. A reminder sent from an address nobody reads is a built-in fault, so the channel has to be one where replies land somewhere that gets checked - and that is a central factor in choosing the channel.
How much maintenance does this need?
Not much, but not zero. A change in a template, a form or a third-party tool can break any of them, so they need an owner - covered in [who maintains the automation](/blog/automation-ownership-and-monitoring).
Keep reading
Related service
Dashboards
One screen with the few numbers that actually change a decision.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.