What a $500 a Month Automation Care Plan Actually Includes

By Roxli Cahayag · 2026-09-16

Why a working automation still needs looking after

Your lead automation is not a fridge. It sits on top of things that move. GoHighLevel ships changes. A calendar link can be changed or removed. A form field gets renamed. Your email sending domain gets new rules. Some failures produce an obvious alert. Others need a check against the expected output. The workflow keeps running, the log keeps saying success, and the leads stop arriving. The worst failure in automation is not an error message. It is a success log for a message that never landed. Care is the habit of checking for that before it costs you a booked call.

The install and the care plan are two separate things

The install is $1,500. It is scoped, one time, and it ends at a defined finish line. A lead comes in, gets sorted, and either books a call or reaches a person with the context attached. When it is done you own it. The care plan is $500 a month and it is optional. You can run the system yourself. Care is for when you would rather not be the person watching it.

What the $500 a month covers

Five things. Nothing hidden behind the word support.

- Weekday checks. Someone looks at the system every working day. Not a green light on a dashboard. A look at what came in and what went out.

- Scoped fault fixes. Up to one repair hour per month for the installed workflow. Initial response by the next business day. If a repair needs more time or a new scope, I explain it and quote it before doing extra work.

- Weekly exception digest. One short message listing every lead the system did not handle on its own, and the reason for each.

- Monthly health report. Volume, how leads routed, response times, and anything drifting in the wrong direction.

- Up to one hour of improvement per month. A small change you ask for. A new tag, reworded email, one extra routing rule. It does not roll over.

What it does not cover

A new system, a new channel, or a rebuild is separate scoped work. If a change needs more than the hour, I quote it first. Outages at a third party get reported to you, not fixed by me. Your GoHighLevel subscription, phone numbers and email sending costs stay yours. Writing your marketing copy is not in here either. Any care plan that will not name its limits is a retainer with no scope.

What the weekly digest checks, using a demonstration test plan

This is a demonstration acceptance test plan, not a measured client result or a claim that these tests passed. It defines twelve test leads, seven expected automatic outcomes and five expected handoffs. These are examples of the checks:

- A lead whose email address had two @ signs in it. The expected behavior is to flag the invalid address before sending and hand the record to a person.

- A repeat submission twenty minutes after the first. The second run should stop, with a duplicate log entry and no second sequence.

- An existing client asking an account question. The expected behavior is to raise an owner task instead of pitching the program again.

- A notes field containing instructions aimed at the system, telling it to mark the lead top priority and to tell nobody. The expected behavior is to ignore those instructions and escalate according to the approved rules.

- No automatic rejection messages. This test checks that a person reviews an uncertain qualification decision.

That list is exactly what a weekly exception digest is. It is the exceptions the workflow should hand to a person.

The numbers I report, and the ones I will not

The test plan sets targets, including a first-response target and zero wrong contacts. Those are acceptance criteria, not measured performance. A real monthly report would separate observed lead volume, routing outcomes, response-time measurements and unresolved exceptions. If tracking is unavailable, the report says unknown. It never substitutes a test target for a measured result or converts response time into an unsupported hours-saved claim.

Checklist: how to judge any care offer

Ask these before you pay anyone, including me. Get the answers in writing.

1. What exactly counts as a fault you fix at no extra cost?

2. How fast do you respond when it breaks, and during which hours?

3. Do I get a written list of every lead the system did not handle?

4. What is on your daily check list? Ask to see it.

5. Do you report wrong contacts made, or only successes?

6. Can the system ever tell a lead they do not qualify? Ask which decisions require human review.

7. What happens when the same person submits twice?

8. What happens when a lead's email is undeliverable? Ask how obvious format errors are caught and how delivery failures are handled; a valid-looking address can still bounce.

9. Do I keep the build if I cancel?

10. What is the notice period, and does the improvement hour roll over?

Worked hypothetical example (not a real client)

Made up numbers, to show the shape of a month. A business coach with a website form gets about forty enquiries a month. Month one: forty in, twenty six routed themselves, fourteen land in the weekly digest. One fault appears. A booking link was removed. The Tuesday check catches it and it is fixed the same day. The improvement hour goes on adding a referred by field to the routing. Month two: the coach notices six of the fourteen exceptions share one reason, enquiries from ecommerce shops that are out of scope. She asks for a rule to log those and stay silent. That takes about forty minutes, so it fits inside the hour. Cost that month is $500. Compare that cost with the operational risk and actual contribution margin of the business. A booked call is not a sale, and no recovered revenue is assumed.

How to decide in two questions

Do enquiries arrive when you are not looking? Would you notice inside a day if they stopped arriving? If monitoring is a meaningful burden and failures have a material cost, discuss whether care is worth it for your volume. If you already handle every enquiry the moment it lands and you get a handful a month, take the install on its own. Add care later when volume grows or when you stop wanting to be the alarm system.

Book a discovery call

See the demonstration builds