Who this is for
An operations manager or business owner whose daily work depends on a handful of automations that nobody has time to watch.
An automation broke quietly last quarter, the person who built it has moved on, or several have started failing now and then.
The result
Before the service starts, each named automation has already delivered a test alert to a shared mailbox this service can read. Each week we review that mailbox and the run history. Each cause of failure we find is investigated on a copy and, within the two repairs a month, ends in a corrected copy for you to switch on, or in a written explanation of what only you or the vendor can change. Causes beyond the two repairs are explained and offered as the matching one-off job at its published price where one exists, otherwise a quote. Each month you see what failed and how it ended.
What is included
- Up to eight named automations on one platform: Zapier, Make or Airtable
- A weekly review of run history for those automations, and of the failure alerts received in the shared mailbox
- Investigation of each cause of failure on a copy, and a corrected copy with change notes for up to two repairs a month
- A plain explanation, with evidence, when the cause is outside the automation, and an offer of the matching one-off job at its published price where one exists, otherwise a quote when more causes arise than the two repairs
- A written monthly summary of failures seen and how each ended
- Terms used here: a failure is a run that the platform shows as errored or failed for a named automation, or an alert received in the shared mailbox; a cause is the reason behind one or more such failures; a repair is one corrected copy, with change notes and a synthetic test, for one cause; a week and a month are calendar weeks and months, and the weekly review happens once in each week on a day agreed in writing
You receive
- A corrected copy of the automation and change notes for each repair, up to two a month
- An explanation of what you need to change, when the cause is a connection, a plan limit or an outage
- A written monthly summary of failures, repairs and anything still open, with the date of each weekly review
What is not included
- Switching any live automation on, off or replacing it: you do that, from our change notes
- Changing credentials, connected accounts, plans or billing
- Building new automations, rebuilding existing ones beyond the two repairs a month, or setting up the failure alerts themselves, which is the separate failure-alerts job
- Automations on n8n or any platform other than Zapier, Make and Airtable: no repair job is published for them, so they are not covered by this service
- Watching alerts as they arrive: the two people you name receive each alert at once, and we read the mailbox at the weekly review
- Out-of-hours cover, round-the-clock monitoring or any guaranteed response time
- Detecting an automation that silently never triggers, unless you name a check for it in writing
What we need from you first
- The platform and the names of up to eight automations you want kept running
- How often they usually fail, as far as you know, and who is told today
- Who switches changes on, and the shared mailbox for alerts
- Do not send passwords, API keys, customer data or an account invitation in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Each named automation has an alert route that delivered a test alert to the shared mailbox before the service started.
- For each repair, the failing behaviour is reproduced on a copy, and the corrected copy passes an agreed synthetic test.
- Each month's summary lists every failure seen in the alerts and in the run history for the named automations, the date of each weekly review, how each cause ended, and any cause offered as a one-off job or a quote because the month's two repairs were used.
You read each monthly summary, and you switch on each corrected copy only when you are satisfied. A repair counts as delivered when you accept it.
When we would stop or decline
- The automations can only be inspected with credentials that give access to live customer data we would have to hold
- Most failures come from causes outside the automations that you cannot or will not fix
- More than two causes a month happen regularly, so we agree a different scope with you
Questions
How is this different from buying one repair?
A one-off repair fixes one failure once. This is a standing responsibility: each week we review the automations you name and take each cause to a corrected copy or an explanation, within two repairs a month.
What counts as a repair, and what if more things fail?
A repair is one corrected copy, with change notes and a synthetic test, for one cause. Unused repairs do not carry over. If more causes arise in a month, we explain each and offer the matching one-off job at its published price where one exists, otherwise a quote.
Do you switch my automations on for me?
No. We hand over corrected copies with notes, and you switch them on. We do not change live automations, credentials, plans or accounts.
Is there a guaranteed response time?
No response-time promise is made. We review once a week, your two named people get each alert as it happens, and a target for finishing a repair is agreed in writing before it starts. The service is not staffed round the clock.
Price and terms
£395/month · untested offer price. Billing is monthly under the written terms we agree with you. Nothing is charged until you have agreed them.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.