The same ticket, again

The mundane fix that keeps coming back — the one nobody can be bothered to automate properly, because no single occurrence ever justifies the effort.

You already know which ticket this is

Every helpdesk has one. Perhaps yours is one of these:

• The default PDF handler that quietly resets itself after a feature update.
• The mapped drive that fails to map for exactly one department.
• The OEM bloatware that reappears with every new model refresh.
• The first-run prompts and nag screens nobody ever suppressed properly.
• The power plan that puts the sales team's laptops to sleep mid-presentation.

Something small, well understood, and fixed the same way every time — by a person, by hand, again. It is never the worst ticket in the queue. That is precisely the problem. It never hurts enough to justify stopping everything and killing it properly, so it survives. Sometimes for years.

Why it never gets automated

Automating a mundane fix properly is not a ten-minute job. Done to a standard you would actually defend, it means detection logic, remediation that handles the edge cases, logging so you can prove it worked, testing across hardware models and Windows builds, and documentation so the next person understands what it does. That is days of work to remove a small manual fix each time it recurs — and there is always something above it on the priority list.

So the rational decision, every single week, is to fix it by hand. Nobody on your team is being lazy. The arithmetic simply never works for any one ticket. It only works across all of them — and that is a sum no single in-house team ever gets the time to do.

The library ships those fixes pre-built

Decolla is a product of The Cloud Platform Ltd, a working UK IT consultancy — which means these tickets are ours too. The library inside Decolla is a curated catalogue of 260+ build items across 21 sections: pre-built, industry-tested policies, scripts and fixes, including the recurring mundane helpdesk fixes and the hardening steps most teams intend to get to and rarely finish. They are built and maintained as Decolla's own mechanisms, not a wrapper around someone else's tooling.

Instead of writing detection and remediation from scratch, you pick the fix from the catalogue while you define the build — a job measured in minutes. A conditional engine filters the catalogue down to what is relevant and defaults it intelligently: OEM tooling by make, power behaviour by chassis, drive strategy, locale, existing-versus-new estate. The weeks of do-it-yourself assembly happen in seconds.

It goes in the plan, and it comes with a receipt

Nothing runs on faith. Every item you select lands in an itemised written plan that you read and approve before anything executes. Each line shows its delivery method and its reversibility class — automatic, reversible, or flagged irreversible — so you know before deployment what can be undone and what cannot.

Deployment then runs unattended in your own Microsoft Intune and Autopilot tenant. There is no Decolla-hosted layer holding your devices: it is your tenant and your consent, and the Graph scopes Decolla requests are published in full before you connect anything.

To be equally plain about the limits: Windows installs, the Enrollment Status Page and Intune sync all run at Microsoft's pace. Decolla does not — and cannot — speed those up. What it removes is the assembly and maintenance work around them. And if an item does need to come back out, rollback works per item or per whole build, covering Decolla's own changes only. It will not rescue a failed Microsoft install, and we will not pretend otherwise.

Where this is up to

Decolla is in private build. There are no customers or case studies to show you yet, and we would rather say that plainly than imply otherwise. What exists today is what is described above — the wizard, the plan, the library and the rollback model — being exercised against the same mundane tickets that prompted it.

If a specific fix came to mind while reading the first section — the one your team knows by name, the one nobody can be bothered to automate — that is exactly the fix the library exists to carry for you. The early-access waitlist is the only way in right now, and it is just below.