The five automations, and what each one touches

You could automate a thousand things. Five are worth learning first, because each maps to a moment where a business that already did the expensive work loses the result of it.

Learn each one's mechanism, build shape and failure mode. The failure mode is what separates you from someone who watched a tutorial.

An unanswered call leaves the business nothing: no name, no number they will use, no idea what it was about. The caller is holding a phone, already choosing, and the next result on the map is one tap away.

• Build: the phone provider emits a missed-call event, you send one SMS, replies land where the owner already looks.
• Breaks: reply loops with the caller's own auto-responder, texting a landline, texting at 3am, texting a spam caller, texting the owner every time they ring their own shop.

A booked slot nobody shows up for is worse than an empty one, because it was held and staffed and could have been sold. A one-tap confirm or reschedule either keeps the booking or frees the slot early enough to refill it.

• Build: read the booking tool, schedule a message a day ahead and another a couple of hours ahead, write the response back into the calendar.
• Breaks: time zones, a reschedule that does not cancel the old reminder, double-sends when the automation runs twice, reminders that keep firing for a cancelled job.

A review is easiest to write while the job is still in someone's head, and asking is a manual step at the exact moment everyone is packing up. Build: the job is marked complete, wait a sensible gap, send one link.

A website form goes to one inbox, and inboxes belong to people who are sometimes on a ladder. Routing sends each lead to a named person by type and time of day, and escalates if nobody has touched it after a set number of minutes.

• Build: the lead arrives, you classify it, send it to a person, start a timer, escalate on silence, log the whole thing.
• Breaks: routing to a group address, which means everyone assumes someone else has it. Always route to one human, with a named fallback.

The owner reads everything because sorting requires knowing the business. This is where a model genuinely earns its keep: it classifies inbound mail, pulls out the address, job type and dates, and drafts a reply to approve in one tap.

• Build: mail arrives, the model classifies and extracts, a rule decides, a draft is written, a human sends.
• Breaks: a wrong classification is silent. Nobody notices the quote filed as spam. Keep a human in the send path and log every decision the model made.

Start with the one whose absence the business can already see. Missed calls sit in a phone log; anyone can count them. Forgotten follow-ups leave no trace at all, so nothing you fix will be visible. Your first build should be one where the owner can check before and after themselves, without a number they have to take on trust.

• Does money arrive after an inbound call, form or message, rather than over a counter?
• Is there a tool in the loop you can connect to, or does the whole thing live in one person's head?
• Can the owner see the failure for themselves, in a log they already have?
• Does it send anything to a customer, or does it only notify staff? The second kind is far easier to go live with.