Marketing Automation Examples: Twelve Flows, Each With a Trigger, a Rule, a Stop Condition and a Failure Mode

These marketing automation examples are twelve flows a small or mid-size team can build in a CRM or workflow tool. Each gets four lines: what starts it, what it does, what ends it and how it usually goes wrong. Stop conditions and failure modes are the parts most lists skip, and they decide whether a flow helps customers or annoys them.

Lists of automation ideas tend to read like menus: send a welcome email, send a reminder, send a thank-you. That tells you almost nothing about whether to build one. What matters is the edge. What happens when the lead replies by phone while the sequence is still queued? What happens when a second tool also emails the same person? We have written about the exit side of nurture in depth in our post on nurture enrollment and exit rules, and this post does not repeat it. It stays on operational flows that sit around the sale: responding, routing, following up, asking for reviews, and raising an alarm when something stops.

HubSpot's workflow documentation is a useful reference for the mechanics, and we use it for the examples that depend on tool behavior. It describes enrollment triggers, re-enrollment settings and unenrollment settings as separate steps of building a workflow. That separation is the point of this post. A flow is not finished when it starts; it is finished when it knows how to stop.

The first six are about speed and follow-through on a lead or an estimate. They share a weakness: each one depends on a human picking up where the automation leaves off.

Flow 1 rests on one of the few well-documented findings in this area. Oldroyd, McElheran and Elkington argued in Harvard Business Review in 2011 that most companies are not responding to online sales leads nearly fast enough. The article is fifteen years old and one co-author led a vendor of lead-response software. Read it as a reason to measure your own response time, not as a promise. The automation's job is narrow: it acknowledges the lead instantly and makes sure a human is on the hook. It does not replace the reply that qualifies the lead.

Flow 2 carries the heaviest compliance weight. The FCC's consumer guidance says its rules require consent before an autodialed or prerecorded call or text to a wireless number, and that commercial texts need written consent while informational texts may rest on oral consent. Whether a missed-call text is informational or promotional depends on its wording, so keep it to a reply to someone who just called you, and have counsel confirm your consent practice. The compliance notes in this guide are general information, not legal advice. Carriers add a second layer. Twilio's documentation explains that anyone sending SMS over a 10-digit long code from an application to US numbers must register for A2P 10DLC, and that unregistered traffic faces more filtering and extra carrier fees. As a conservative practice of our own, keep outbound texts inside an 8 a.m. to 9 p.m. window in the recipient's local time, the window federal rules set for solicitation calls to residential lines.

Flow 4 shows why stop conditions beat clever timing. HubSpot's sequences tool can unenroll a contact when they reply or book a meeting, which is the setting that prevents the follow-up that arrives after a customer has already said yes. It does nothing for the case where the customer said yes by phone and nobody logged it. For that case the only fix is a rule that the estimate stage gets updated the same day, and a weekly report of estimates older than ten days with no logged activity.

Flow 6 depends on a default that surprises people. HubSpot documents that, by default, records enroll in a workflow only the first time they meet its enrollment triggers, and re-enrollment has to be turned on deliberately. Leave it off and a second dormant period will never trigger the flow. Turn it on everywhere and the same contact can receive the same reactivation twice in a month. Decide per flow, and write the decision in the flow's description.

The second six are about trust, handoff and monitoring. They tend to be quieter than the first six, and they are where automation most often fails without anyone noticing.

Flow 7 sits closest to a rule that tools will not enforce for you. Google's Business Profile guidance lets you ask customers to leave a review through a link or QR code. It also lists what merchants may not do, including discouraging negative reviews or selectively soliciting positive ones. The FTC's 2024 rule on fake reviews and testimonials separately prohibits using certain threats or intimidation to suppress a negative review. So send the link to everyone who completed a job, and route unhappy customers to a person without removing the link. A rule that sends the link only to customers who scored you highly is selective solicitation, however sensible it looks on the flow chart.

Flow 8 is where the CRM's reporting gets quietly corrupted. If the automation sets the lifecycle stage and a rep also edits it by hand, you will see stages flip and conversion reports shift in ways that look like performance. Pick one owner for each stage transition, and write it down. Our posts on lifecycle stage definitions and CRM field change control go deeper on who should own what. Flow 9 is small, but it is the one that most affects what the customer feels in week one. Attach a record of what was promised to the onboarding tasks, which is the subject of our post on transferring contract promises to implementation.

Flow 10 is the cheapest flow on the list and the one with the highest return per hour of effort, in our judgment, because a broken form fails silently. A lead-flow alert tells you before the quarter does. Its failure mode is alert fatigue, so start with a threshold you would be embarrassed to miss, such as a source silent for a full business day, and tighten it only if you can keep up with the noise. Our marketing automation observability post covers the logging side of this.

Flow 12 is the one with a clock attached. The FTC's CAN-SPAM guide says you must honor an opt-out request within 10 business days, that the law covers all commercial email with no exception for business-to-business messages, and that each separate violating email can carry penalties of up to $53,088. The tool you use will handle one list. The risk is the second system: an old list in a spreadsheet, an agency's platform, a sales rep's personal sequence. Our suppression propagation post covers how to make one list authoritative.

The twelve flows differ, but the discipline around them does not. Write these rules once and apply them to every flow you build, so that the twelfth is no riskier than the first.

Test with records built to break it, not records that behave. Create a contact who unsubscribed last week and see whether the flow skips them. Create a duplicate of an existing lead and see whether it enrolls twice. Create a record with a blank territory and see where it routes. Create a contact in another time zone and read the reminder. Reply to the first message and check whether the second one still goes out. Each of these has a known failure in the tables above.

Then run the flow live on a small slice before opening it to everyone, for example a single service line or a single office, and watch the log for a week. Compare what the flow did with what you intended, record by record. If that sounds slow, compare it with finding out from an angry customer. Skip the slice and the customers who hit the failure modes become the test.

Build the one that answers the problem you can already see. The table maps a visible symptom to the flow that addresses it. If more than one row fits, pick the one where a lost customer costs the most.