Automation & Scripting

The repetitive ones that are easy to get wrong by hand: disk cleanups and scheduled maintenance, installing a standard set of software on a new machine, the onboarding and offboarding steps when staff join or leave, and remediation that fires when a monitored condition is met, such as a service restarted or a full disk tidied. Judgment calls stay with people; the routine clicks become policy.

Yes. Custom scripts and policies are built around how your business actually works, meaning your applications, your folder structures, your onboarding checklist, not a generic template. We write them, test them on a small group of devices first, and then apply them across the fleet. Every script is documented and lives in the platform, so it keeps running the same way regardless of who on our team is on shift.

Scripts are tested before they are applied broadly, run under policies that limit what they can touch, and log what they did on each device. If one misbehaves, we see it in the logs, pause the policy, correct the affected machines, and fix the script before it runs again. The consistency that makes automation valuable also makes a mistake easy to find and reverse, because every device was treated identically.

No. It is part of the flat monthly fee per device, month to month. Automation is how we deliver the rest of the service at a predictable price instead of billing hours for routine work, so there is no reason to charge for it separately, and for the devices we manage it is simply how the work gets done. A script for a one-off task outside your managed environment would be discussed with you first.