Skip to content

How Do I Check That My Business Automations Are Still Working?

After an automation goes live, watch six things: whether messages are delivered, whether people reply or book, whether it leads to sales, how many people opt out, what errors and duplicates show up, and when you’ll audit it next. Check alerts daily, look at the numbers monthly, and do a full review of each automation at least twice a year.

Automations break quietly. A tool updates, a form field changes, or a phone number gets flagged, and messages stop or go wrong with no warning. Without monitoring, you find out from an angry customer or months of missing leads.

What it means: tracking which messages were delivered and which failed.

How to do it: check your email and text tools for delivered, bounced, and failed counts. Watch for sudden drops. For email, a high bounce rate often means an old list. For texts, a spike in failures can mean carrier filtering, so contact your provider.

Common mistake: assuming “sent” means “delivered.”

What it means: tracking replies, bookings, inquiries, and complaints.

How to do it: count replies and bookings for each sequence. Read a sample of replies each month. A complaint about an automated message goes into your complaint log (see 17.8 Complaint Handling).

Common mistake: tracking clicks but never reading what people actually wrote back.

What it means: connecting automation activity to sales and revenue.

How to do it: tag leads and jobs with the sequence that touched them (see 15.8 Lead-Source Tracking). Each month, add up booked jobs and revenue from each one. Compare with what it costs to run.

Common mistake: keeping a sequence because it “feels” helpful when it has produced no jobs in six months.

What it means: tracking unsubscribes and stop requests.

How to do it: watch the opt-out rate for each sequence and each message. A jump after one message usually means it was too frequent, off-topic, or sent to the wrong group. Confirm opt-outs reached every tool (see 12.6 Communication Consent Records).

Common mistake: treating opt-outs only as a number and never checking that they were honored everywhere.

What it means: reviewing failed actions, duplicates, and wrong routing.

How to do it: check error logs and failure alerts weekly (see 18.9 Internal Notifications). Look for people who got a message twice, messages sent to the wrong owner, and steps that failed. Fix the cause, retest, and note it in your change log (see 18.10 Testing Automation).

Common mistake: fixing the one customer who complained but not the setting that caused it.

What it means: putting regular automation audits on the calendar.

How to do it: review every automation at least twice a year, and after any tool change. For each, confirm it’s still needed, the owner is current, the wording is accurate, consent rules are met, and tests still pass. Retire the ones that no longer earn their keep.

Common mistake: an automation still promising a price you stopped offering a year ago.

An automation or analytics specialist can build a simple monthly report from your tools. Questions to ask:

  • Can I see delivery, replies, bookings, and opt-outs for each sequence in one place?
  • How do I connect messages to booked jobs and revenue?
  • What error alerts should I turn on in each tool?

[Bill: add a short note. For example, what SiteSmarty checks each month on client automations, or an automation that quietly broke and what it cost.]

  • [Date I did this:]
  • [What I actually did, step by step: the SiteSmarty monthly automation report and audit schedule]
  • [What it cost and how long it took:]
  • [What surprised me or what I’d do differently:]
  • [Screenshot or photo to add, with private info blurred: the monthly automation report]
  • [Result so far:]

How do I know my automated messages are delivered? Check delivered, bounced, and failed counts in each tool, and watch for sudden drops.

How do I tell if an automation brings in sales? Tag leads and jobs with the sequence that touched them, then add up booked jobs and revenue each month.

What does a rise in opt-outs mean? Usually that a message was too frequent, off-topic, or sent to the wrong group. Look at which message caused it.

How often should I audit automations? At least twice a year, and after any tool change.

Outline lineQuestionPass looks likeFail looks likeEvidence to collect
18.11.1 DeliveryAre delivery and failure counts checked?Monthly delivery review“Sent” treated as deliveredDelivery report
18.11.2 ResponseAre replies, bookings, and complaints tracked?Counts and sampled repliesClicks onlyResponse report
18.11.3 ConversionIs each automation tied to sales and revenue?Revenue per sequenceNo link to salesConversion report
18.11.4 Opt-outsAre opt-out rates watched and honored everywhere?Rates tracked, opt-outs syncedIgnored spikesOpt-out report
18.11.5 ErrorsAre errors and duplicates reviewed and fixed at the cause?Weekly review and change logRepeat errorsError log
18.11.6 Review dateIs there a scheduled audit for each automation?Twice-yearly audits on calendarNo auditsAudit calendar and notes

Where this fits

Do this first: 18.10 Testing Automation

Do this next: 20.1 Pre-Spend Checklist

Related pages: 15.8 Lead-Source Tracking, 18.5 Follow-Up Sequences, 18.9 Internal Notifications, 21.2 Marketing Metrics, 21.5 Dashboards, 14.6.6 Review Monitoring

Sources

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.

Get free updates

I'll send you a short email when new guide pages and videos go up.

No sales pitches. Unsubscribe any time.