How an AIRS session works.
A one-off client calls, and the PC has never seen your tools. They open one small app. AIRS does the digging on that machine and writes a fix for it. No fix it writes runs until you sign it.
You give the order. The PC answers.
Pick a step to follow one session from start to finish.
The client
Say what is wrong
The client opens the app, describes the problem in plain words and agrees to this one session. The first time on a PC, you approve it or give them a setup code.
Example session. Not a real customer.
Client: Outlook locks up every morning around 9.
Consent: allowed for this session.
The AI
Look around, read-only
The AI runs checks that only read. The PC itself confirms each one is read-only before it runs, so these need no sign-off.
Example session. Not a real customer.
Check: Outlook add-ins and load times
Check: memory, disk and recent errors
PC: read-only confirmed. Running.
The AI
Write a fix for this machine
The AI explains what it found and writes a script for this exact PC, with a plain explanation and a risk rating.
Example session. Not a real customer.
Found: an old PDF add-in delays every start.
Fix: turn off that add-in for this user.
Risk: low. Can be undone.
You
A person decides
You read the card and sign with a passkey once per session. Later steps take one click, and each one is still signed.
Example session. Not a real customer.
Tech: read script and explanation.
Passkey: session sign-off complete.
Scope: this PC, this session only.
The PC
The PC checks the signature
Before anything runs, the PC verifies the signature for itself. The AIRS server has no key to approve its own commands.
Example session. Not a real customer.
Signature: valid
Script: matches what the tech signed
Device, session, tech: all match
Everyone
Run it and keep the record
The fix runs, the result goes back to the session, and the record is saved. You can approve the fix for next time.
Example session. Not a real customer.
Result: add-in off. Outlook opens normally.
Record: saved to the session log.
Fix library: draft waiting for tech review.
The AI can only reach for 16 reviewed fixes. Anything else that changes the PC needs your signature.
Some steps can't be undone. AIRS spots them in the script itself and asks for a fresh passkey every time.
The 16 reviewed fixes.
The AI can only reach for 16 reviewed fixes. Anything else that changes the PC needs your signature.
The AI picks from a fixed list
The AI can reach for 16 reviewed fixes, like flushing DNS or restarting Outlook, once the client has agreed. It picks from the list and can't write or edit one.
Six just run, ten wait
Six just run, and ten wait for the client's tap. A "Not now" holds for the rest of the session.
You can turn them off
A tech can turn the list off per client or per session, and an admin can turn off single fixes.
Everything else needs your signature
Anything else that changes the PC needs your signature. Read-only checks run on their own, and the PC confirms they're read-only.
The six that just run
- Flush DNS
- Renew DHCP
- Sync the clock
- Re-register in DNS
- Refresh Group Policy
- Restart the print spooler
Limits the PC enforces
- Each fix runs at most twice a session.
- No more than 6 fixes and 12 offers a session.
- They stop after 2 failures in a row.
- Pause stops them.
- Each one is logged in the session record, and you see it.
Show the receipt.
Each session keeps a tamper-evident text record: what was wrong, what was checked, who approved what, and how it ended.
The record of who did what is there if a client ever disputes the work.
- Reuse what worked: solved sessions become fixes you review and approve.
- Give each tech access to only the clients they should see.
Example record. Not a real customer.
Session record: Harbourview Dental, HARBOUR-04, Dana Reyes
What you work from.
Work from a web console, with no remote desktop to wrangle. Read the script, the plain explanation and the risk before you sign.
For your client
- Open one app and say what's wrong in their own words.
- Agree once, for this session only.
- Watch every step, chat, pause or end it at any time.
- Close the app and nothing keeps running.
Got a nervous client? Send them the plain page that says what will happen.
Yes, it's a portable app. Here's how to think about that.
CISA and the NSA warn about portable remote tools that run without being installed, and you should keep blocking the ones you didn't choose. AIRS should get past your app control only because you allowed it.
It comes from your shop
Your client hears about it from a tech they know, and you tell them to expect it. It should never arrive cold.
It needs consent, every session
The client agrees for this session only, and can pause or end it at any time.
Nothing keeps running
Close it and access ends. There's no service and nothing starting with Windows.
It isn't code-signed yet
Expect Windows warnings until it is, and plan for them. A code-signed app is on the way.
What works today, and what doesn't yet.
AIRS is pre-release. Today it runs only at NetDNA, and founding partners are first in line for their own.
Working today
- Diagnosis and bespoke fixes on Windows PCs
- Passkey sign-off, checked again on the PC itself
- Extra sign-off for steps that can't be undone
- A tamper-evident text record of every session
- A fix library your techs review and approve
- 16 reviewed fixes the AI can use, which you can switch off
- Syncro customer and asset matching
On the way
- A code-signed Windows app
- Mac support
- Syncro ticket notes and time entries
- Your own private AIRS instance at launch
Where it won't help
- Macs. It's Windows only, for now.
- A locked-out PC. If they can't sign in to Windows, they can't open the app.
- A dead connection. The internet has to be up.
- An empty desk. It needs admin rights and someone there to say yes.
Questions
Do I need to install anything?
No. AIRS is a small portable app. It asks for admin rights when it opens, and access stops when it closes. It keeps a small private folder on the PC so it can recognise that computer next time. Nothing runs in the background.
Do I have to install anything on every PC?
No install. Staff open the app when there's a problem. The first time on a PC, you approve it or give them a setup code.
Can the AI change a PC on its own?
In one way only. The AI can reach for 16 reviewed fixes, like flushing DNS or restarting Outlook, once the client has agreed. It can't write or edit them. Six just run, and ten wait for the client's tap. You can turn them off per client or per session. Anything else that changes the PC needs your signature. Read-only checks run on their own, and the PC confirms they're read-only.
Why not paste logs into a chatbot?
Your techs can. AIRS reads the machine directly, writes the fix for that PC, gets your tech's sign-off, and keeps the record without anyone copying anything.
What's left on a PC after a session?
Nothing keeps running. The app file stays, plus a small private folder with its ID and logs, so it can recognise the PC next time. Any fix that ran stays too.
Will my client's antivirus or Windows complain?
It might. The app isn't code-signed yet, so Windows may warn about it. Tell your client to expect that, and to call you before clicking through. A code-signed app is on the way.
Is the screen recorded?
No. The record is a written log of steps, not video.
Does this replace the tools I already use?
No. AIRS works alongside them. It's for the moment a real person needs a PC fixed.
Fixed, on the record, and nothing left running.
That's how an AIRS session ends. Join the founding list and be among the first to try it.