Schedule-based automation fires whether or not reality cooperates: the Monday email goes out even to the customer whose job was cancelled Friday. Event-based automation reacts to what actually happened, which is why it feels attentive instead of mechanical. The best trigger catalogs include absence events too, no rebooking ninety days after completion is one of the most profitable triggers a service business can wire.
Specific enough to mean one thing: job marked complete, not vague activity. Sourced from operational truth, the booking system and payment records, not from a parallel tool guessing. And paired with conditions that respect context: skip the review ask if a complaint is open, stop the win-back the moment a booking lands. Triggers without conditions become the automation people apologize for.
Rented tools expose the triggers their vendor imagined. When the booking, client records, and payments live in one owned system, any event in the business can become a trigger, crew assigned, invoice overdue by three days, fifth job completed, VIP threshold crossed. That richness is where automation stops being email scheduling and starts being the operating system of the business.
Booking confirmed, job completed, and the silence trigger at the natural rebooking interval. Those three carry confirmation, reviews, and win-back, the highest-return automations that exist.
Yes, completions can start follow-ups that themselves trigger on replies. Chain deliberately and document it; automation spaghetti is real.
Idempotency, one event fires once even if reported twice, plus suppression conditions and a log humans can read. Boring engineering is what makes automation trustworthy.
Everything in this glossary, we build and operate for real businesses. Thirty minutes maps it to yours.