Flowridium—AI, Automation & Custom Solutions

01

PROBLEM

A school had high staff turnover every term—10 to 30 leavers and joiners at once. Each joiner needed an on-prem server account with the right folder permissions, plus an Office 365 account. Setting one up manually took about 5 minutes, which stacked into hours with 20–30 joiners at a time.

SOLUTION

A simple CLI tool built in Python and PowerShell. The user types a name and picks from pre-defined permission levels. A 5-minute job became a 10-second one. Once everyone was added, the tool generated a text file listing every email address, permission level and password—ready to copy straight into the report back to the client.

02

PROBLEM

An MSP client came on board with an aggressive rollout plan—800+ sites to onboard over two years. Each site involved configuration across multiple services, following a 30-page onboarding document that took 1–1.5 hours per site and carried a high error rate.

SOLUTION

Using Rewst, workflows and a form were built for the engineer to fill in. The 1–1.5 hour, mistake-prone task became a 5-minute form that produced the same clean result every time—projected to cut total onboarding time from 800–1,200 hours down to around 67.

03

PROBLEM

Engineers weren’t using the Knowledge Base because articles were hard to find. Customers started complaining that tickets were being closed with steps missed or incomplete.

SOLUTION

A dedicated SharePoint site was built to house the KB, every article checked for relevance and renamed to a consistent naming convention. A Copilot chatbot was then trained on the KB content and surfaced inside Teams—so engineers had answers on hand without going looking.

04

PROBLEM

Repetitive service desk tasks—user onboarding, offboarding, group membership, mailbox delegation, email forwarding, out-of-office configuration, password resets—were prone to mistakes and ate into time engineers could spend on more interesting work.

SOLUTION

Using Rewst, a workflow and form were built for each task. Every workflow carries out the job, creates or updates the ticket with notes, closes it, and emails the customer confirmation along with any extra detail needed. If anything goes wrong, it emails the engineer directly with a list of the issues.

05

PROBLEM

Several MSPs had dozens of workflows and forms already built in Rewst, but adoption was low—engineers weren’t using automations that already existed.

SOLUTION

An internal portal was built listing every available automation, alongside a leaderboard tracking each engineer’s time saved.

06

PROBLEM

Customers were complaining about being billed for devices they weren’t using, which meant finance had to do extra work chasing it down and issuing credits.

SOLUTION

A device reconciliation portal was built that shows every device at a glance, flagging anything unseen for 30 or 60 days. Each device has a one-click option for the customer to decommission it themselves.

07

PROBLEM

At the end of each month, finance had to work through an RMM report listing device counts for servers, workstations and laptops, then update Autotask contracts by hand—slow and error-prone.

SOLUTION

Workflows were built to update Autotask contracts automatically on the last day of the month, using RMM as the source of truth. This removed the manual work for finance entirely, and the errors along with it.

08

PROBLEM

The MSP had a set of standards every customer needed checking against—local admin accounts, Windows Firewall status, domain status. All of it was manual: an engineer logged into RMM, found the site, then worked through each machine by hand checking local accounts one at a time. Painfully slow.

SOLUTION

Scripts were written for each standard check, set up as components in Datto RMM and scheduled daily to log results to a user-defined field. A Rewst form let the user pick a customer and the standards to check—workflows pulled the results from the UDFs and emailed a report straight to the engineer.