The five automations, and what each one touches

You could automate a thousand things. Five of them are worth learning first, because each one maps to a moment where a business that already did the expensive work loses the result of it. For each, learn the mechanism, the build shape, and the failure mode. The failure mode is the part that separates you from someone who watched a tutorial.

1. Missed-call text-back

Mechanism: 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 in the act of choosing, and the next result on the map is one tap away. A text that arrives inside a minute turns an abandoned call into a thread that survives the next hour.

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's own mobile every time they ring their own shop.

2. Appointment reminders and confirmations

Mechanism: a booked slot that nobody shows up for is worse than an empty one, because it was held and staffed and could have been sold. A reminder that lets someone confirm or reschedule with one tap 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, and reminders that keep firing for a cancelled job.

3. Review requests

Mechanism: a review is easiest to write while the job is still in your head. Asking is a manual step at the exact moment everyone is packing up, so it does not happen. Moving the ask to a trigger is the whole automation.

Build: the job is marked complete, wait a sensible gap, send one link. Breaks: policy, mostly. Read Google's own prohibited-content and review policies before you build this. Filtering who you ask based on how happy they seem, and offering anything in exchange for a review, are the two places people get a business's profile in trouble. Do not design a flow that only asks the happy ones.

4. Lead routing

Mechanism: 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, with an escalation if nobody has touched it after a set number of minutes.

Build: form or ad lead comes in, 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.

5. Inbox and quote triage

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

Build: mail arrives, the model classifies and extracts, a rule decides what happens, a draft is written, a human sends. Breaks: a wrong classification is silent. Nobody notices the quote that got filed as spam. Keep a human in the send path and keep a log of everything the model decided, so a mistake is findable.

Which one to start with

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. You want your first build to be the kind where the owner can check the before and after themselves, without you handing them a number they have to trust you on.

• 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?
• Is the automation allowed to send anything to a customer, or does it only ever notify staff? The second kind is far easier to go live with.