What support do you get after an automation build?
Every Autoesta build includes six months of maintenance at no extra charge: if something we built breaks, we fix it. That covers the workflows, pipelines, integrations and AI agents we delivered. After six months, monthly support starts at $200, with extra hours available when you want changes or new features.
Those terms are the same ones on our about page. The maintenance period exists because automations rarely break on day one. They break weeks later, when a vendor changes something, a new staff member edits a workflow, or a situation comes up that nobody tested. Six months is long enough for most of those to surface while we are still responsible for the fix.
What does the included maintenance cover?
It covers fixing what we built when it stops working as agreed. It does not cover changes to third-party platforms we did not build on, or new features you ask for later; those are scoped separately. The line is simple: broken is ours to fix, new is a new piece of work.
Is it covered by included maintenance?
| Situation | Covered by included maintenance? |
|---|---|
| A workflow we built stops sending reminders | Yes |
| An integration we built fails after a vendor update | Yes, for the integration we delivered |
| An AI agent we built gives a wrong answer about your services | Yes, we correct its instructions and knowledge |
| You want a new workflow or a new location added | No, scoped as new work or support hours |
| A tool we did not build on changes how it works | No, scoped separately |
Why do automations need maintenance at all?
Because the tools they run on keep changing. Vendors retire features, change limits and add rules, and every change can quietly break a step. In September 2026 alone, Zapier switched off its Functions feature, HighLevel stopped SMS on Mexican local numbers, and the FCC was preparing new opt-out rules for calls and texts.
September 2026: changes that can break automations
- Zapier Functions stopped running on September 1, 2026, breaking any Zap that used them.
- GoHighLevel's September updates changed snapshots, dashboards and Mexico SMS.
- The FCC's opt-out changes affect how reminders and marketing texts must handle "stop".
- Google's sender rules mean an email setup that worked last year can land in spam today; see why GoHighLevel emails go to spam.
None of these is dramatic on its own. Together they are why a system with no one watching it slowly stops doing its job.
Which parts of a system are most exposed to breaking?
The parts that depend on someone else's rules break most often: connections between tools, which break when a vendor changes an API or retires a feature; email and texting, which depend on sender rules and registration; and AI agents, whose answers go out of date when your prices, hours or services change. The workflows inside one tool are usually the most stable part.
| Part | What changes under it | What to watch |
|---|---|---|
| Integrations between tools | Vendor APIs, retired features, plan limits | Error notifications, missing records |
| Mailbox provider sender rules | Spam complaints, inbox placement | |
| Texting | Carrier registration and opt-out rules | Failed messages, opt-out rate |
| AI agents | Your own prices, hours and services | Wrong answers in transcripts |
| Workflows inside one tool | Staff edits, new triggers | Duplicate or missing messages |
The Care Star Healthcare case study shows a set of recurring automations that has to keep running week after week, which is exactly what maintenance protects.
What does monthly support include after six months?
Monthly support, from $200 a month at the time of writing, keeps someone responsible for the system: monitoring, fixes, small changes and keeping up with platform updates. Extra hours are available in any month for larger changes, such as a new campaign, a new location or a new AI agent.
Whether you need it depends on how much your business changes. A stable business with a small build may run for months without help. A growing one that adds services, staff or locations usually needs changes every month, and support is cheaper than fixing a year of drift in one go, which is what a GoHighLevel account cleanup often is.
How do you keep an automation system healthy yourself?
Check it on a schedule. Once a month, read the workflow history for a few recent contacts, send yourself a test lead, look at error notifications and opt-out rates, and read the last few AI conversations. Fifteen minutes a month catches most problems before customers notice.
A 15-minute monthly check
- Test lead: submit your own form and call your own number after hours.
- Workflow history: check three recent contacts went through the expected steps.
- Errors: read any failed-action notifications in the CRM and your automation tool.
- Messaging: watch opt-out and email complaint rates for sudden jumps.
- AI: read a sample of AI conversations for wrong or outdated answers.
For duplicate messages, a problem customers notice quickly, see why a workflow sends a message twice.
Questions about support after launch
When do the six months of maintenance start?
At launch, when the system goes live for your team and customers.
Do we have to buy monthly support after six months?
No. It is optional. Many clients keep it; some call us for extra hours only when they need a change.
What if something breaks after the maintenance period ends?
We can fix it as support hours, or you can have your own team or another provider fix it. The accounts are yours, so you are never locked in; see who owns what you build.
Can you support a system another agency built?
Yes, usually after a free audit, so we know what we are taking responsibility for.
Sources and further reading
- Autoesta, what happens after we build it, terms at the time of writing (September 2026).
- Zapier, Functions deprecation notice.
- HighLevel, product changelog.
- Google, email sender guidelines.
