# What can be automated in marketing and what should stay with people Canonical page: https://aryehalgorithms.com/resources/what-can-be-automated-in-marketing · Updated 2026-09-15 Marketing automation is the use of software and defined workflows to execute marketing processes (lead routing, enrichment, nurturing, monitoring, reporting) continuously, without a person handling each step by hand. The work that qualifies is repeatable: the same trigger, the same steps and a rule that can be written down before it runs. Work that reaches a customer in unapproved words, or changes a rule other workflows depend on, should run only with a person approving it. Positioning, offers and the borderline cases stay with people, and a well-built system is designed to hand them over cleanly. ## How to tell whether a marketing task can be automated Three questions settle most cases. Does the task start from something a system can see, such as a form submission, a changed field, a date or a failed check? Does it end in a defined state, such as a record with an owner, a message sent or a row added to a report? And can the rule that connects the start to the end be written in a sentence your team would agree with before it runs? If all three answers are yes, a workflow can carry the task. If the third is “it depends”, the task belongs to one of the other two groups. The test matters because automation does not make a task easier; it makes it consistent: the same rule applied to every record, every day, whether or not anyone is at a desk. Where the rule cannot be written down, what you would be automating is a guess dressed up as a process. A guess made once by a person is a mistake. A guess made by a workflow is the same mistake repeated until someone notices. Sorted this way, marketing work falls into three groups: what can run on its own, what should run only with a person approving, and what stays with a person from start to finish. The sections below take each in turn, then show how the three fit together on one lead. ## What can run as a workflow on its own Routing and enrichment come first. A new lead is a visible trigger, an owner on the record is a defined end state, and the rule between them (which fields decide the score, which field decides the owner) fits in a sentence. Enrichment has the same shape: a record with gaps is the trigger, a record that meets your field standard is the end state, and the agreed source for each field is the rule. Neither needs judgment once the rule exists, and each has an obvious failure mode (no matching rule, conflicting data) that goes to a queue rather than being guessed at. Nurturing and reminders are the next group. Nurturing qualifies only when the words were approved before the sequence was built; the workflow decides timing and order, never content. Write down which events end the sequence, because a sequence with no exit is how an automated message reaches someone who has already bought. Reminders are the safest kind of automation, because they prompt a person rather than act on a customer: a task when a lead has waited past the agreed window, a note ahead of a renewal date, a nudge when an internal step is overdue. Monitoring, reporting and list refresh round out the group. A scheduled check can confirm that the connections between your website, forms, CRM and email platform still work, and pause what depends on one that has failed. Reporting can be automated up to the point of interpretation: data collected on schedule, counted the same way as last week, and a summary drafted for a person to read. Lists and segments qualify when each has a written definition (these tags, this consent status, this stage); membership then follows the definition rather than the last export someone ran. - Lead routing: applying the rule your team already uses to decide who gets a lead, on arrival. - Enrichment: completing, formatting and matching new records against what the CRM already holds. - Nurturing: scheduled messages from approved content, with an exit on reply or status change. - Monitoring: scheduled checks on forms, tracking and integrations, with a pause when one fails. - Reporting: collection and counting on a fixed definition, with the summary drafted for review. - List refresh: rebuilding each list from its written definition whenever the data changes. - Reminders: prompts to a named person when a lead, task or date has passed its window. ## What should run only with a person approving Two kinds of work sit in the middle group: anything that reaches a customer or prospect in words a person has not seen, and any change to a rule that other workflows depend on. Automation can prepare both. It can draft the message and it can propose the rule change. It should not release either. The test is not whether software wrote the words or found the pattern; it is whether a person looked before anything left the building or changed underneath it. Messages first. A nurture sequence built from approved copy is automation, because the words were reviewed once and are sent the same way every time. A reply drafted to one person from the specific question they asked is a draft until someone reads it. The same applies to a follow-up that changes an offer, a response to a complaint, and anything sent to an existing customer account rather than a prospect. A wrong message costs a relationship, which no workflow can restore. Rule changes second. A routing rule that sends leads to a new territory, a scoring threshold, a consent rule, the criteria for merging two records: each applies to every record that follows, so a wrong rule is a wrong decision repeated quietly at scale. Automation should surface the evidence; a person decides. Ask three things of every proposed change: can it be stated in a sentence, who on your side signs it, and how would you put the old rule back if the new one misroutes for a week. The mechanism that makes this group work is a queue with an owner. Whatever a workflow cannot place, and whatever it would have to write from scratch, lands where a named person looks on business days. A queue nobody owns is not supervision; it is a backlog with a delay attached. ## What stays with people Positioning stays with people: who you sell to, what you say about yourself and why a buyer should choose you. Not because software cannot produce a sentence on the subject, but because the decision belongs to the business and shapes every downstream rule. Offers stay with people for the same reason: price, terms, what is included, when to make an exception. Judgment on borderline cases stays with people because the data has run out: the lead that scores just under the line, the account that fits on paper and not in the conversation, the duplicate record that might be two companies after all. Run these through the three questions and the third one fails every time. There is no rule a team would agree to in advance, because the answer depends on context that is not in the record. Put a threshold on them and the judgment does not disappear; it is frozen at whatever number was chosen that day, and nobody revisits it. The larger cost is that the people who could have explained the decision stop being asked. What automation can do for this group is prepare the decision. A borderline lead should arrive with its score explained and a short brief attached. An uncertain merge should arrive with both records side by side and the fields that conflict marked. A proposed change to the offer should arrive with the evidence that prompted it. The person deciding then spends their time deciding, not reconstructing what happened. ## How the three groups fit together on one lead A form is submitted late on a Thursday. The submission is written to the CRM, the record is completed and matched against existing companies, the lead is scored and, because it clears the threshold, assigned to an owner with a timestamp. All of that is the first group, and none of it waited for Friday morning. On Friday afternoon the owner is reminded because the agreed window has passed without a note. That is still the first group: a prompt to a person, not a message to the customer. The owner calls, learns that the timing is wrong, and moves the lead to a nurture path. The next message is scheduled from approved content, which is the first group again. Three weeks later the contact replies with a question about terms. The reply moves the lead out of the path and back to the owner, and a draft answer is prepared from the question. The draft is the second group: it waits for the owner to read it, change it or discard it before anything is sent. At the end of the month, a look at where leads ended up shows that leads from one region keep being passed on. A change to the routing rule is proposed as a sentence, signed by your team and kept alongside the one it replaces. That is the second group. Whether to keep selling in that region at all is a positioning question, and it goes to whoever runs the business. That is the third group, and no workflow should be in the room for it. ## How to sort your own marketing work Take one ordinary week and list the marketing tasks that were done. For each, write the trigger, the steps and the end state in one line. Then mark the ones where the rule between trigger and end state can be written in a sentence your team would sign. Those are candidates for the first group. Where the sentence needs an exception clause, note the exception; it is probably a queue that needs an owner. Next, ask two questions of each candidate. Does it send words to a customer or prospect that nobody has read? Does it change a rule that other tasks rely on? A yes to either moves it to the second group, where automation prepares and a person releases. Finally, look at what is left. If the task depends on context that is in no record, it is the third group, and the useful question is how to get the decision to the right person with the evidence attached. Start with the first-group task that stalls most often when your team is busy, and fix the foundation it depends on before building the workflow, since a workflow reads whatever the record holds and applies the rule to it, wrong or not. If you want a structured version of this exercise, the Marketing Automation Assessment on this site turns this sort into a short questionnaire with a readout on the page, and the marketing operations function page describes what keeping the rules running looks like week to week. ## Questions ### Can emails to customers be automated? Scheduled messages built from content a person approved can be, with an exit the moment the contact replies or changes status. A reply to a specific person about their specific question should be drafted by automation and read by a person before it is sent. The dividing line is whether the words were seen before they went out, not whether software produced them. ### Does automating marketing mean the team has less to do? It changes the shape of the week rather than the size of the team. Time spent copying, chasing and rebuilding goes to the workflows. The time freed goes to the work that was being squeezed: deciding what the rules should be, reading what the exceptions say about the business, and the conversations with customers that no sequence can have. Plan where that time goes before the first workflow runs, or it is absorbed without anyone noticing. ### What happens to the tasks a workflow cannot place? Give them a named owner and a fixed time on each business day, and keep a one-line note of why each could not be placed. Read those notes monthly: a reason that repeats is a missing rule, and a reason that never repeats is a judgment call that belongs with a person. The queue should shrink over time; a queue that grows is a sign the rules were written too narrowly. ## Related - [Marketing Automation as Aryeh Algorithms runs it](https://aryehalgorithms.com/solutions/marketing-automation) - [How the marketing operations function keeps the rules running](https://aryehalgorithms.com/ai-marketing-department/marketing-operations) - [Take the Marketing Automation Assessment](https://aryehalgorithms.com/tools/marketing-automation-assessment)