The AI Readiness preset report tells you whether your environment is mapped well enough for Atera AI to run diagnostics and device actions on the correct device for the correct user. It measures one prerequisite: accurate, complete mapping between devices (agents) and the end users (contacts) behind them.
Before you begin
Important: Viewer capabilities on preset reports are available to Expert, Master, and Enterprise users only.
Important: Viewer capabilities on preset reports are available to Growth, Power, and Superpower users only.
Devices must be reporting into Atera before the report returns anything meaningful.
This report is not the same as AI Center analytics. This one measures the inputs going in; AI Center analytics measure what Robin did with them once it is running.
Run the report
- Go to Reports > Analytical reports.
- Under Presets, select AI Readiness.
- Set the filters you need: Agent last seen Date, Site name, Contact mobile phone, and Contact email.
The report returns six tiles across the top and a Detailed Info table below them. Use the tiles for the readiness snapshot, then use the table to find the exact sites, devices, and users that need fixing.
Read the tiles
| Tile | What it counts |
|---|---|
| Total Number of Agents | All devices currently reporting to Atera, based on your filters. |
| AI-ready Agents | Devices that meet the minimum requirements for AI features to consistently run diagnostics and actions on the correct device for the correct user. |
| Agents with contact email | Devices linked to a contact record that has an email address. |
| Agents without contact email | Devices not linked to a contact record with an email address. These are your first fix. |
| Contacts with phone number | Contact records that include a phone number. |
| Contacts without phone number | Contact records with no phone number. These block any flow that needs to reach the end user. |
Read the Detailed Info table
The table under the tiles lists every device in scope, one row each, with the contact data attached to it. Its columns are Customer name, Agent name, Contact email, Last logged user, Agent last seen Date, Agent is online, Contact mobile phone, and Contact phone.
An empty Contact email cell means that device has no contact attached, so it will appear in the Agents without contact email count. Sort by Agent last seen Date to deal with the devices that are actually in use before the dormant ones.
Open a tile to see what is behind the number
Click any tile to open its underlying records. Each one opens with its own filter count, an Explore option, and a Download option.
What you get depends on the tile:
- Total Number of Agents opens the full device inventory, including machine name, OS, memory, serial number, last reboot time, and BIOS detail.
- AI-ready Agents, Agents with contact email, and Agents without contact email open a device list showing agent name, system name, machine name, domain name, and folder, plus per-agent hardware and alert columns.
- Contacts with phone number and Contacts without phone number open a contact list showing Contact first name and Contact last name only.
Tip: The two contact tiles return names, not devices. To find which device belongs to a contact with no phone number, cross-reference the name against the Detailed Info table.
Why missing mappings and phone numbers matter
A device with no contact attached
AI may not be able to confidently associate the device with the right person, which limits its ability to run end-to-end workflows, trigger the right diagnostics, and apply actions with the proper context.
A contact missing a phone number
This can block AI-driven flows that depend on reaching the end user - verification, follow-up, approvals and confirmations where applicable, and local password reset - reducing how far Robin or AI Copilot can go without manual intervention.
Impact on both products
- Robin relies on correct user-device association to automate support flows and drive resolution.
- AI Copilot relies on it to execute device actions confidently and give accurate, contextual guidance.
Warning: A high-risk identity action can write to the mobile number field, which means AI is able to modify the same data this report scores. Decide who governs that before you enable identity writes.
Improve your readiness
There is no single passing score. Prioritize reducing Agents without contact email and Contacts without phone number, starting with your most important sites and the devices that appear most frequently in tickets.
Give every remaining gap an owner rather than leaving it as a number on a report.
