Romy / For IT teams

Fewer tickets, same control.

For the solo admin with 200 employees as much as the three-person IT team. This page shows what Romy takes off your plate, where you set the limits and how a new version reaches you.

§ 01Who it is for

Microsoft shops with 100 to 350 employees.

Exactly the size where one admin is CIO, security and helpdesk at once.

Daily work

Lots of small requests.

A slow laptop, a frozen Teams client, a restart that never happened. Each request is small, each costs a context switch.

Responsibility

You answer for it when something breaks.

That is why Romy reads first and changes a device only after a person has confirmed.

Tools

In the Microsoft stack you already run.

Romy uses Entra ID, Intune and Teams as they are. Reading and the restart through Intune need no software on the devices.

Size

Romy grows with you, without a new hire.

More devices bring more requests. Romy takes the repetitive ones off your plate.

§ 02What Romy takes off your plate

The routine nobody wants to do.

Device diagnostics, restarts after confirmation, licence routine. You keep the decision.

Live

Device diagnostics

State, updates and storage of a device from Intune, with a finding and a proposal.

Live

Restart

After confirmation, through the Romy app on the device, otherwise through Intune.

Live

Windows repairs

Such as clearing the Teams, Edge or Chrome cache, through the Romy app, once you have switched them on.

Live

Licence inventory

Paid licences that are assigned to no one.

Live

MFA and Conditional Access

MFA registration and Conditional Access policies from Entra ID, read-only.

Planned

Joiners and leavers

Romy assembles the package for people joining or leaving, a person confirms.

§ 03You set the limits

You decide what Romy may do.

Three switches, all of them yours. Romy works within what you have granted.

1 · Read

Romy Diagnostics

You grant read permissions for the organisation. This app cannot change anything.

2 · Act

Romy Engage

Optional. Only with it can Romy restart a device after confirmation. Wipe, retire and passcode reset stay out of Romy's reach on every path.

3 · Repairs

In the Romy portal

Windows repairs are off until you switch them on, and you can switch them off again at any time.

Each app can be revoked on its own in Entra ID. The full setup with every permission →

§ 04How Romy works in your environment

From the question to the evidence.

Before anyone confirms, the card shows which device is affected, what happens and what the proposal is based on.

1 · Ask

In their own words.

Your people describe the problem. Romy knows who they are from the Microsoft sign-in.

2 · Read

Only this device.

Romy reads what belongs to this question and cites the source.

3 · Confirm

One card, every consequence.

A person confirms. The confirmation is valid for 15 minutes, once, for one device.

4 · Check

Result and log.

Romy checks that it worked. Every step is logged, without message content.

In the Teams chat, Romy answers only agreed pilot users today. The chat carries customer data only once the European data boundary is proven for the Teams channel.

§ 05Releases

How a new version reaches you.

Through the wizard, updates arrive by themselves on the Stable channel, or Beta on request, only after we have tested them on our own devices.

1 · Stable

For all customers.

Every file with its checksum on the releases page.

2 · Beta

On request.

For customers who want to test early.

3 · Your Intune

You approve.

You roll out the Romy app through your Intune assignment.

Releases and what has changed →

Romy for your team.

Start with Diagnostics, read-only. Nothing can change until you grant Engage and someone confirms a card.