Five AI Automation Examples, Written as Specs Instead of Promises

AI automation examples that actually run in a small business come down to five workflows: a missed call texted back, an inquiry qualified and booked, a quote chased on a schedule, a no-show rebooked, and a review requested at a fixed milestone. Each one is a trigger, a condition, an action, and a handoff.

Each of the five below is written as that specification rather than as a benefit, because the two middle lines decide whether it works. A demo shows the trigger and the action; the condition and the handoff are where a system embarrasses you in front of a customer.

The four lines every workflow needs

Every workflow worth building writes down four lines: the trigger that fires it, the condition that must be true before it runs, the action it takes, and the handoff point where a person takes over. A fifth line, the number it is supposed to move, decides whether it stays switched on.

The failures are all condition failures: a text to a landline at 2am, a reminder for a job somebody already cancelled by phone, a bot arguing with an angry customer.

Missed call texted back in seconds

A missed-call text-back fires when a call to the business number ends unanswered, checks that the number is a mobile and not already in an open thread, sends one text offering a booking link or a callback, and hands the conversation to a person as soon as the reply is anything but a time.

ServiceTitan's platform data across more than 3,000 US and Canadian trade businesses, published October 2022 from June 2022 numbers, put a typical shop's call booking rate at 42%, with shops under five technicians at 24%; the same report says mornings booked best and rates fell after 6 p.m. One platform's customers, not a census, and still the clearest published number on it.

ServiceTitan principal industry advisor Angie Snow, in that report: "You see contractors pouring in money for training their technicians," and then, "But what kind of training are they putting into their CSRs?" An automation is not CSR training. It covers the hours when nobody answers at all.

The condition here is legal as much as technical. The Federal Communications Commission's consumer guide, last reviewed February 2026, says FCC rules ban autodialed texts to a mobile phone without prior consent, that commercial texts require written consent, and that consent for informational texts may be oral. Answering the person who just called you is not a marketing blast, and that distinction is what the condition encodes. General explanation of published rules, not legal advice.

After-hours inquiry qualified and booked

An intake workflow fires on a form submission or a chat message, checks the job type and the address against what the business actually sells and where it travels, asks two or three qualifying questions, offers real open slots from the calendar, and books one. Anything outside those answers goes to a person with the transcript attached.

The condition line is what makes this one safe to leave running overnight. Without it the system books outside the service area, promises something nobody offers, or fills a slot the van cannot reach. With it, the worst case is a message saying somebody will confirm in the morning.

Two constraints belong in the spec. The customer is told what they are talking to. And outbound voice is a separate decision from inbound answering: the FCC's consumer guide states that AI-generated voice calls are illegal unless the consumer has agreed to receive them or the caller is exempt, so a voice agent that calls people back needs a consent record.

Quote followed up on day two and day five

Quote follow-up fires when a quote is marked sent, checks that the job has not already been won, lost or superseded, and sends a short message on day two and day five that names the specific job rather than saying "following up". A reply of any kind ends the sequence and goes to a human.

Nobody notices the quote that was never chased, which is why this one gets skipped. The number it moves is the quote-to-job rate, measurable within a month because the denominator already sits in your system. Two messages is the whole sequence; a third turns a follow-up into a nuisance.

No-show rebooked before the slot goes cold

A no-show workflow fires when an appointment passes without a check-in, confirms from the schedule that nobody marked the customer as arrived, sends one message offering the two nearest open slots, and releases the original slot to the waitlist. The second miss goes to a person, not to another automation.

The condition matters most here, because the schedule is edited by humans all day. A workflow that reads "appointment time passed" without reading "and nobody marked them arrived" will text customers sitting in your waiting room. Pair it with a reminder the day before: the cheapest no-show to fix is the one that has not happened.

Review requested at one fixed milestone

A review request fires at one fixed milestone, the same milestone for every customer: job closed, invoice paid, vehicle collected. The condition is that the milestone happened, never that the customer seemed happy. The action is one ask with a direct link, and a second reminder at most. Replies go to a person.

Uniformity is the rule, not squeamishness. The Federal Trade Commission's Rule on the Use of Consumer Reviews and Testimonials, at 16 CFR 465.4, makes it a violation to provide compensation or incentives "in exchange for, or conditioned expressly or by implication on, the writing or creation of consumer reviews expressing a particular sentiment". The same rule carves out generalized solicitations to purchasers, so asking everyone is not the problem. The spec: same ask, same milestone, every customer, no incentive, no sentiment gate.

The payoff is documented by the platform itself. Google's Business Profile help documentation, as of September 2026, lists relevance, distance and prominence as the main local ranking factors and says: "More reviews and positive ratings can help your business's local ranking." Google does not weight those factors, and the same page states no ranking can be bought.

What to write down before you build any of them

Before any of the five gets built, five answers go in writing: what fires it, what must be true, what it sends, who it escalates to, and what number it moves. Add two more for anything that messages a customer: what consent was captured, and what happens when somebody replies stop.

1. 1Write the trigger as an event your systems already emit, and the condition as a check that can fail. "Call ends unanswered" is a trigger; "when we miss a call" is a wish.
2. 2Write the action as the exact message, once, in plain words, and the handoff as a person and a channel with the history attached. An escalation into an inbox nobody owns is not an escalation.
3. 3Write the consent basis and the opt-out path. The FCC's rules treat a reply of stop, quit, end, revoke, opt out, cancel or unsubscribe as a reasonable revocation on its face, and require one made by any reasonable method to be honored within ten business days.
4. 4Write the number it moves and where you read it. A workflow nobody measures is one nobody turns off when it breaks.

What this looks like when it runs

Running, the five stop being projects and become one operation: the phone covered after hours, intake booked into a real calendar, quotes chased on a schedule, missed appointments offered the next two slots, reviews asked for at one milestone, and a single screen showing what each produced last month.

Mirastart builds and runs those systems for Charlotte businesses: the online booking and repair-status software Quick Auto NC runs its bays on is ours, and so is the live-availability booking on this site. The accounts and the phone number stay in your name, the logs are yours to open, and ongoing engagements start at $3,000 a month because the process work and the consent plumbing sit inside that number.