Key takeaways
- Every good automation is a sentence: when this happens, if this is true, then do that.
- Start with the tasks you already do the same way every time, like confirming a booking or thanking someone for paying.
- Use a condition to keep a rule narrow, so it only fires for the right customers and services.
- Turn rules on one at a time, test them against real past activity, and read the first few messages yourself.
Most of the admin in a service business is the same small task, done again and again. A new lead comes in, so you send the same "got it" text. Someone books, so you send the same prep notes. A customer pays, so you mark them paid up and say thanks. None of it is hard. It just eats the evening.
An automation is a rule that does one of those tasks for you. You write it once as a plain sentence: when something happens, if a condition is true, then take an action. Below are ten rules worth setting up, grouped by where they sit in the life of a customer. Pick two or three that match what you already do by hand, and start there.
How a when, if, then rule works
- When (the trigger): the event that starts the rule. A new lead is created, an appointment is booked, an invoice is paid.
- If (the condition, optional): a filter that narrows it. Only when the service is "Intro call". Only when the lead came from your website.
- Then (the action): what happens. Send an email or a text, add a tag, update a field on the customer, or send the details to another tool you use.
A good test for any rule: could you explain it to a new hire in one sentence? If the sentence needs three "unless" clauses, it's probably two rules, or a job that still needs a person.
New leads: answer fast, sort them right
1. Tell every new lead what happens next
When a lead is created, if it came in through your website form, then send a short email or text: you got their request, when you'll reach out, and how to reach you sooner. Why it helps: people who fill out a form at 9 p.m. wonder if it went anywhere. A quick reply shows a real business is on the other end, and it buys you until morning.
2. Tag leads by what they asked for
When a lead is created, if the service they picked is, say, "Mosquito treatment", then add a matching tag. Why it helps: at the end of the week you can pull up every mosquito lead in one view and call them back in a batch, instead of scrolling a mixed list.
3. Send new leads to the tool you already use
When a lead is created, then send it by webhook to a spreadsheet, an accounting tool, or another system your team still checks. Why it helps: nobody retypes names and numbers into a second place, and the two lists stay in sync.
Bookings: get people ready before the visit
4. Send an intake survey for a first meeting
When an appointment is booked, if the service is "Intro call" or "Consultation", then email a short survey. Why it helps: you walk into the first meeting already knowing the basics, so the time goes to the customer instead of to filling out a form together.
5. Send prep notes to first-time customers
When an appointment is booked, if the customer has the tag "New", then send what to expect: arrival window, parking, keep pets inside, unlock the side gate. Why it helps: fewer locked gates, fewer surprise dogs, and fewer "what do I need to do?" calls the night before.
After the job: close the loop
6. Send care instructions after the visit
When a job is done, if the service is one with aftercare (fertilizer, a color treatment, a new filter), then send the instructions in writing. Don't mow for two days. Wash with a sulfate-free shampoo. Check the filter next month. Why it helps: customers forget what the tech said at the door, and a bad result from skipped aftercare still gets blamed on you.
7. Mark a lead as a customer once they've been served
When a first job is done, then remove the "New" tag and add "Customer". Why it helps: the prep-notes rule above stops firing for them, and your newsletters and follow-ups can tell the two groups apart.
Billing: thank people and keep score
8. Thank customers when they pay
When an invoice is paid, then send a short thank-you. Mention the next visit if one is booked. Why it helps: it's a small touch that most businesses skip, and it gives the customer an easy reply thread if they have a question.
9. Record the last payment on the customer
When an invoice is paid, then update a "Last paid" date field on the customer. Why it helps: when you plan a win-back email or a price change, you can filter for people who haven't paid in six months without opening a single invoice.
Records: keep your list clean without trying
10. Flag records that are missing something
When a lead is created, if there's no phone number, then add the tag "Needs phone". Swap in whatever you can't work without: an address for a route business, an email for a coach who sends session notes. Why it helps: you fix gaps before the visit, not when the tech is standing at the wrong house.
Rules like this one never message a customer. They only label and fill in your own records, which makes them a safe first automation to try.
Turning automations on without surprises
Start with one
Pick the task you do most often by hand. Write it as a when, if, then sentence before you build anything.
Test it against real activity
Run the rule against recent leads, bookings, or payments and check who it would have matched. Too many? Tighten the condition.
Read the message as the customer
Send it to yourself first. Check the name, the tone, and any links.
Switch it on and watch the first few
Look at the first handful of runs. Then leave it alone and move to the next rule.
In Meep, any rule that sends a message to customers starts paused. You review it and switch it on yourself, so nothing goes out by surprise. That's true even when an AI assistant drafts the rule for you.
FAQs
Will automations make my business feel robotic? +
Not if you write them the way you talk. Use your name, your shop's name, and the same plain words you'd use in a text. Keep the personal stuff, like a hard conversation or a custom quote, for yourself.
What if a rule sends the wrong message to a customer? +
Keep conditions narrow, test against past activity before you switch a rule on, and send the message to yourself first. In Meep, rules that message customers start paused, so you review them before anything goes out.
How many automations should I have? +
Fewer than you think. Three to five good rules cover most of the repeat work for a small team. Add one only when you notice yourself doing the same task by hand again and again.
Can I send leads to another app I already use? +
Yes. A webhook action sends the details to another system, like a spreadsheet or your own records. On Meep Core you can also connect through Zapier or the REST API.
General information for small business owners, not legal, tax, or financial advice. Last updated October 12, 2026.
