Automation Isn’t a Strategy

A working send isn’t a strategy. Pete shows what belongs before the triggers: purpose, stop rules, reply ownership — and how a Hot Sheet rooted in the properties you’ve photographed gives outreach a real reason to exist.

Picture this. An agent books another shoot with you this morning. This afternoon, your automated email tells them you haven't heard from them in a while. The copy is fine. The link works. And it still makes your business look like it isn't paying attention.

That isn't a software problem. It's a decision nobody made: what the email is for, and what should stop it.

Decide what the email is for before you build it

Triggers, delays, and tags come last. Start with what you want for the client. Do you want a new agent to feel comfortable booking again? Do you want honest feedback on the shoot? Do you want them to hear about another service that fits their listings? Each goal needs a different message. Skip the decision, and one sequence ends up asking for all three, no matter what the agent is going through.

Write one sentence for every automated email: what should be true for the client after they read it. For a first-delivery check-in, that might be "the agent can use the photos, or tells us what's in the way." Sending the email is what you did. That sentence is what you're actually after.

The best reasons to reach out come from your own work: a property you just photographed, a delivery that just landed, a question the agent asked. That's what a Hot Sheet built from your own shoots gives you — a real reason to get in touch, not a calendar reminder. Before you add anything new, check the relationship before the next follow-up.

Decide what stops it

Most automation mistakes come from emails that should have stopped:

• The agent books again, so the "come back" reminder gets skipped.

• The agent replies with a delivery problem, so the upsell and the review request wait until it's fixed.

• You or someone on your team takes over the conversation, so the sequence steps aside.

• The agent asks you to stop, so you stop.

Write these down in plain sentences before anyone builds anything. "Only ask for a review after delivery is complete and the agent hasn't raised a problem." If you can't say it plainly, the automation won't handle it reliably either.

When something pauses, someone should know why. Otherwise a client can sit in limbo with nobody checking on them.

Know who answers the replies

Every email that invites a reply needs a person who owns the answer. If an agent writes back with a question about their order, it should land with someone who will answer it, not get buried while the next email goes out on schedule.

Don't trust the green check mark

A scheduled email isn't a sent email. A sent email isn't a read one. An open doesn't mean the relationship got better. For every client, you should be able to answer three plain questions: Did it go out? Did they reply? Who's handling it?

If an email fails, someone should find out. Don't assume the agent heard from you.

Try it on one client this week

Pick one automated sequence that goes out after delivery, and one agent who just went through it. Read the emails in order, along with everything that happened in between: replies, new bookings, questions, problems. Then read it the way the agent would, between showings.

Where does it stop making sense? That's your fix. Fix that one spot, check it against the same client, and move on. You don't need to rebuild everything at once.

Then pick one client whose next message keeps landing back on your to-do list. Look at that relationship across connection, retention, expansion, advocacy, and reactivation. Choose the biggest gap, one useful next step, who's doing it, and a follow-through date — and decide what would make that outreach stop.

Want this to run inside your business? Watch the PixlCRM demo.

Great work starts the relationship. What happens next helps build loyalty.