A few years back I heard a story about a company that automated their birthday outreach to clients. Pull the birthday field, send a friendly note. Lots of companies do it. They wanted every client to feel remembered.
The problem started about six months in. A long-time client called the founder directly. She said, "I lost my husband three weeks ago. Your birthday email arrived this morning. Did anyone there even know?"
He did not know what to say. He apologized. They turned the automation off. The damage was done. That client never felt the same about the brand.
That story has stayed with me. Not because automation is bad. I run a lot of automation in my agency. We have AI agents stitched between every part of our pipeline now. The story stays with me because it draws the most important line in the AI conversation, and most leaders are not drawing it carefully enough.
There is a line between a task and a relationship. You can automate one all day. Touch the other and you will pay for years.
Where the line falls
A task is something you do. A relationship is something you have with somebody. They are different categories of work and they live by different rules.
A task can be repeatable. The same input gets the same output. The point of doing it well is efficiency. Examples in my agency. Generating a project recap email from meeting notes. Pulling weekly campaign performance into a standardized format. Drafting the first version of a proposal section. Updating a HubSpot record. Scheduling a sequence of follow-up reminders. All tasks. AI just made them an order of magnitude faster.
A relationship is not repeatable. It is contextual, cumulative, shaped by every previous interaction. The point of doing it well is presence. The phone call when a client just lost a major deal. The hard conversation when a project missed its deadline because of something on your end. The annual catch-up dinner with the customer who has been with you since the start. The ten minutes you spend with a team member who is having a rough week.
Touch the second category with automation and you do not save time. You spend trust.
What makes the line tricky
A lot of work that looks like a relationship is actually a task. And a lot of work that looks like a task is actually a relationship. The labels deceive you.
The birthday email looks like a relationship gesture. It is actually a task that pretends to be one. The recipient cannot tell the difference until the moment the pretense becomes obvious, and that moment is unforgivable.
The status update email looks like a task. Most weeks it is. But on the project where things are not going well, that email is no longer a task. It is the most important relationship moment of the week. Sending the same automated update on that week is the kind of mistake you do not realize you have made until the client moves their account.
The principle I have settled on is this. Automate the work whose value is in the doing. Do not automate the work whose value is in the noticing.
A weekly recap email has value in the doing. The client wants the information.
A note checking in on a client whose business has been quietly struggling for two months has value in the noticing. The whole point is that you noticed. The moment they suspect a workflow noticed instead of you, the gesture is dead.
Where I automate and where I do not
I want to give you the actual lines I draw, because examples beat principles.
I automate aggressively in these places. Drafting first versions of internal recaps. Pulling reports from project tools. Cleaning meeting transcripts into structured notes. Categorizing inbound leads. Standard onboarding sequences up to about week two. Compiling end-of-quarter performance summaries. None of these touch a relationship.
I will not automate these. The first call when a client has bad news. The personal congratulations when a client wins something significant. The introduction email when I am connecting two people who matter to me. The Friday note to a team member who carried something hard. The check-in with a long-time client when I have a hunch something is off. The apology when we missed something.
That second list is not long. It is also the list that, if I get it right, makes the rest of the agency work for the next twenty years. I refuse to hand it to a workflow. Not because the workflow could not draft something passable. It could. The point is that the doing is the gesture. If I delegate the doing, the gesture is gone.
action
1. Walk the last five touches to your top ten clients. Label each one task or relationship. 2. For every relationship moment, confirm a human was in the loop when it mattered. 3. Turn off any "personal" automation that the recipient would feel betrayed by if they noticed. 4. Write the list of moments you will never delegate to a workflow. Post it where your team sees it. 5. Pick the one relationship moment you were tempted to automate this week. Do it yourself.
dont Automate the first call after bad news, the personal congratulations, the apology, the check-in when something feels off. Work whose value is in the noticing. :::
What is the one relationship moment this week that you are tempted to delegate to a workflow, and what would change if you did it yourself?
