The Dry Run: Test a New Robot on Yourself Before It Touches a Customer

The worst version of a new automation isn't the one that doesn't work. It's the one that works perfectly, fast, and sends the wrong thing to everybody at once.

You've probably seen it land in your own inbox from some other business. "Hi {first_name}, thanks for your visit on ." A reminder that fires at 3 AM. A follow-up that goes out to a customer who canceled last week, so now they're annoyed and you look like you weren't paying attention. The machine did exactly what it was told. Nobody checked what it was told to do first.

Here's the good news. You don't have to choose between flipping the switch for every customer and never trying anything new. There's a middle step the pros use and most owners skip: you run the robot on yourself first. Point it at your own phone and your own inbox, let it do its thing for a week, and read every single message it sends before a real customer ever sees one. We call it the dry run, and it's the cheapest insurance you'll ever buy.

Why the first live send is the dangerous one

A person makes one mistake at a time. You fat-finger one address, you forget one callback. Bad, but small. A robot doesn't work that way. It does the same thing to your whole list in the time it takes to pour a coffee, so a small error isn't small anymore. It's two hundred small errors with your name on them.

That's the real trade with automation. The speed that saves you hours is the same speed that spreads a mistake. Machines do the relay, fast and tireless. People do the judgement about whether the relay is any good. Skip the judgement part and you've just automated your embarrassment.

The dry run puts the judgement back where it belongs: in front of the first send, not after it. You're not testing whether the robot can send a text. Of course it can. You're testing whether the text it sends is one you'd actually be proud to get.

What a dry run actually looks like

It's simpler than it sounds. You set up the new automation exactly the way you'd run it for real, then you make yourself the only customer. Your cell number, your personal email, maybe a spare address if you've got one. For about a week, you live inside the thing like a customer would.

Say you're setting up appointment reminders. You book a few fake jobs for yourself across the week at different times. Then you wait and watch what shows up on your phone, when it shows up, and how it reads at a glance between tasks.

Does it arrive at a sane hour? A reminder that pings at 6:12 AM or 11 PM tells you the timing rule is wrong before a customer tells you with a one-star review.
Do the blanks fill in? Every name, date, time, and address should read like a human typed it. If you see a stray bracket, a double space, or a time with no date, the robot's pulling from the wrong spot.
Does it sound like you? Read it out loud. If it's stiff, or too chummy, or signs off with a company name you don't use out loud, fix the wording now while the only person offended is you.
Can you reply to it? Hit reply like a confused customer would. See where your answer lands. A reminder nobody can respond to just moves the phone tag somewhere you're not looking.

Keep a running note on your phone of every awkward thing you catch. You'll be surprised how fast the list fills up, and how small each fix is once you can see it.

The things a dry run catches that nothing else will

Reading the setup screen tells you what the robot is supposed to do. Getting the message on your own phone tells you what it actually does, and those are different animals more often than you'd think.

Tone is the big one. A line that looks fine in the settings box can read cold or pushy when it buzzes in your pocket during dinner. You only feel that by feeling it as the customer does.

Timing is the next. Robots think in rules like "24 hours before." Real life thinks in "that means Sunday night, when nobody wants a work text." Living through a week of sends surfaces the weekend and after-hours problems a glance never would.

Then there are the empty spaces. The reminder for a customer with no last name on file. The follow-up for a job that has no price yet. These edge cases hide until a real record hits them, so seed a messy fake record on purpose and watch what the robot does with the gaps.

Trust it in widening circles, not all at once

Once the dry run is clean, you still don't have to go straight to everyone. Widen the circle one ring at a time, and keep your eyes on it as you go.

Just you, for a week. Fix the wording, the timing, the blanks.
You plus a couple of friendlies. Your spouse, your most forgiving regular, a crew member. People who'll tell you "that read weird" without taking their business elsewhere.
A small slice of real customers, maybe the next ten bookings. Small enough that if something's off, it's ten apologies, not two hundred.
The full list, once a slice has gone out clean and quiet with no surprises.

At every ring, leave yourself copied on what goes out for a little while. A blind copy to your own inbox for the first week of real sends means you see what your customers see, in real time, and can pull the plug in a minute if something looks off.

Be honest about what the robot still can't judge

A dry run makes a robot safe to send. It doesn't make it smart. The machine will happily send a cheerful review request to the one customer you just had a blowup with, because it doesn't know about the blowup. It'll remind someone about a job you already know is getting rained out, because the forecast isn't its department.

So the dry run isn't the end of your attention. It's the thing that earns the robot a longer leash. You still want a way to hold or skip a message for the customer who's a special case, and you still want to glance at what's going out, at least until the thing has proven itself over a few weeks. That's not a failure of the automation. That's the division of labor working the way it should: the robot runs the relay, you keep the judgement.

When we build these for folks, the dry run is the part we never skip, even when the owner's itching to go live. An afternoon of testing on yourself beats a week of apology texts. Ask us how we know.

Worth doing this week

Pick one automation you've been meaning to turn on, or one that's already live and makes you a little nervous, and give it a proper dry run.

Make yourself the customer. Put your own cell and personal email into a test record and book two or three fake jobs across different days and times.
Read every message out loud as it arrives. Keep a note of anything stiff, mistimed, or missing, and fix the wording before anyone else sees it.
Feed it a messy record on purpose, one with a blank name or no price, and watch how it handles the gap.
Blind-copy yourself on the first week of real sends so you see exactly what your customers see.
Start with ten, not two hundred. Let a small slice go out clean before you hand the robot the whole list.