Support

What Happens If the Automation Breaks? Support, Maintenance, and Who Is Responsible

By Clinton Fisher · 16 Nov 2026 · ← Back to the blog

Every automated system breaks eventually. A connection drops, a tool changes how it works, a phone number is replaced, a login expires. That is not a flaw in automation. It is how all software behaves. What matters is what happens next: who notices, who fixes it, and how long your leads go unanswered while it is down. This is the question to ask before you start, not after.

What Actually Breaks

Most failures are small and predictable. A connection between your CRM and your messaging tool stops working. A third-party service changes its rules. A password or access token expires. A form is edited and stops sending data. Very few failures are dramatic. Most are quiet, which is exactly what makes them costly: nothing visibly crashes, leads simply stop arriving.

Who Notices First

The worst answer is the agency owner, three weeks later, because the pipeline looks thin. A well-run system has some form of monitoring, so a failure triggers an alert rather than a puzzled review of the numbers. Ask any partner how problems are detected, and how quickly someone is told.

Who Is Responsible for the Fix

Responsibility should be written down. Is the partner responsible for fixing issues within a certain timeframe? Does the agency handle small changes in-house? Who owns the accounts and logins that everything runs on? Vague answers here lead to arguments at exactly the wrong moment.

Maintenance Is Not Optional

Systems that are never reviewed drift out of date. Tools update, teams change, processes evolve. A regular check, even a short one, keeps the setup aligned with how the agency really works. Ask whether ongoing maintenance is included, billed separately, or left to you.

Documentation and Ownership

If the person who built the system disappears, could someone else take over? Clear documentation of how things are connected, plus agency ownership of the accounts involved, protects you from being locked into one person. This is one of the most important questions in any automation project.

A Fallback for Quiet Failures

Good systems have a plan for when automation is down. Leads should still be captured somewhere, even if the instant reply fails, so nothing is lost while the fix is underway. The aim is a graceful failure, not a silent one.

Ask These Questions Before You Start

Want to talk through support and maintenance before committing to anything? See what I do, or book a Free Bottleneck Snapshot and bring your questions about how problems are handled.

I'm currently booking a limited number of Free Bottleneck Snapshots for established Costa del Sol brokerages, 30 minutes, no prep. Bring your questions about support and maintenance.

Book Free Call

FAQ

Small issues are normal over time, usually from changes in connected tools or expired access. Monitoring and maintenance reduce the impact.

This should be agreed in writing before the work starts, including response expectations and who owns the underlying accounts.

It varies by engagement and should be confirmed during scoping, not assumed.

A well-designed setup captures leads somewhere safe even when an automated reply fails, so nothing is lost.