Atera offers advanced AI agents designed to transform IT management. Our AI capabilities simplify tasks, reduce repetitive work, and help both technicians and end users resolve issues faster, boosting productivity and improving support quality with Autonomous IT.

AI Copilot vs. IT Autopilot

In short:

• IT Autopilot helps end users solve issues on their own, before they reach your team.
• AI Copilot helps technicians solve issues faster and automate their work.
   

Features Valid for Both Co-Pilot and Auto-Pilot

The section below concludes the capabilities that are applicable to both Co-Pilot and Auto-Pilot

Knowledge Base Integration

• Access to customer KB for step-by-step answers.
• Use of Atera’s curated diagnostics/actions repository.
• Customer KB sync time ~30 minutes.

Security & Privacy

• Powered by Azure OpenAI with enterprise-grade security and compliance.
• Tenant data isolation: no cross-customer sharing.
• Data governed by Atera’s DPA, Terms of Use, and platform security controls.
• Any company confidential information inputted into Copilot or Autopilot is treated like other sensitive data in Atera (for example, ticket contents) and is governed by Atera’s Terms of Use and platform security controls.

Model & Learning

• Based on Azure OpenAI GPT models.
• Not self-learning; improved only by Atera updates and curated actions.
• Any limitation from the public GPT model applies.
• Prompts, queries, and KB content from both Copilot and Autopilot do not train public AI models and remain securely within your account context.

Safety of Actions

• Relies on pre-approved/admin-enabled scripts.
• All actions are designed to be safe and controlled.

Requirements / Dependencies

• Linked devices recommended; works best when online.
• Script execution requires admin enablement.

Limitations

• Bound by OpenAI/public model restrictions.
• Cannot self-learn beyond curated actions and KB inputs.
• Falls back to KB/cloud-only answers when devices are offline.

Frequently Asked Questions about AI Copilot

Q: What is the purpose of Atera's AI Copilot?

A: AI Copilot gives your team the purpose-built IT companion they need to exceed their own capabilities. It boosts your team productivity. It helps techs resolve tickets faster (summaries, suggestions, scripts/commands, KB drafting), while end users benefit from quicker, clearer responses—reducing back-and-forth and helping them return to work sooner.

Q: What capabilities does the Atera AI Copilot offer?

A: AI Copilot can:

• Generate scripts (.bat, .ps1, .sh) tailored to your prompt.
• Generate CLI commands and execute them on selected devices.
• Generate OIDs for SNMP monitoring with suggested thresholds.
• Analyze ticket sentiment (latest end-user comment).
• Draft KB articles directly from resolved tickets.
• Compose/rephrase replies (adjust tone and clarity).
• It also provides ticket summaries, operational report summaries, and multi-chat history. For more on Atera’s AI features, see Atera’s AI capabilities.

Q: What are Cloud actions in Copilot? 

A: Cloud actions let Copilot connect to external data sources via API and retrieve live information inside your chat — for example, querying the MITRE vulnerability database for a CVE briefing. Cloud actions are read-only lookups against external services.

Q: What is MCP integration? 

A: Model Context Protocol (MCP) integration lets Copilot take actions inside third-party tools your team already uses (e.g., creating an incident in monday.com with severity, type, and priority pre-filled). Unlike Cloud actions, MCP enables write operations into external systems on your behalf.

Q: Are Cloud actions and MCP integration available to all Atera users? 

A: Yes. Both are included with AI Copilot, which is available to all Atera users at no extra cost.

Q: Where does the AI Copilot gather information to provide suggestions?

A: From your account’s secure context: device and ticket data, your customer Knowledge Base, and Atera’s curated repository of diagnostics/actions..
 

Q: Are the Copilot's AI-generated scripts reliable and safe to use?
A: They’re powerful but may contain inaccuracies. Always review, test, and validate AI-generated scripts before running in production.

Q: Are the script-based actions available for use in the end-user portal reliable and safe to use?
A: End-user actions are built from pre-tested templates designed for safe, basic troubleshooting. Admins control which scripts are enabled.

Q: Does Atera update the version of the AI modules used for the AI features available within the dashboard?
A: Yes. Atera regularly updates its AI modules to improve accuracy, performance, and safety.

Q: Is there a way to turn off/disable specific AI features, while leaving access to others?
A: Most Copilot features are on-demand and built-in. You can opt out of sentiment analysis if preferred.

Q: In which languages does the Atera Copilot operate?
A: Copilot supports English, French, German, Italian, and Spanish. Some features (e.g., certain health checks/actions) may be fully supported in English only.

Q: How does Atera handle AI hallucinations?
A: We rely on Azure OpenAI’s high-quality models, frequent updates, and content filtering. Atera adds governance and best-practice prompts to minimize hallucinations, and recommends human review for critical outputs (e.g., scripts/commands).

Frequently Asked Questions about IT Autopilot

Q: What is the purpose of Atera’s Autopilot?
A: Autopilot acts as a 24/7 AI technician. It helps users troubleshoot and resolve common IT issues on their own, reducing the number of Tier-1 tickets your team needs to handle and improving response times and user satisfaction. Atera’s IT Autopilot is the shift from IT automation to Autonomous IT

Q: What capabilities does the Atera Autopilot offer?
A: Autopilot can:

• Perform local device health checks (CPU, disk, drivers).
• Run pre-approved scripts (marked Enable for AI assistants).
• Reset local, hybrid, and Microsoft Azure Active Directory (Azure AD) passwords with MFA verification.
• Manage group memberships in Azure AD (add/remove within org policies).
• Install/update pre-approved applications (Chocolatey/Homebrew).
• Detect account lockouts, send proactive alerts, and prompt recovery steps.
• Open, update, and resolve tickets — escalating to technicians with full context when needed.
• Provide usage and resolution analytics to admins.

Q: What are the requirements for using Autopilot?
A:

• The agent must be online for local actions.
• User must be a Contact under an enabled Site/Customer.
• A linked device and phone number are needed for MFA actions.
• Azure AD sync is recommended for cloud actions (password resets, group membership, MFA resets).
• Scripts must be enabled for AI assistants.

Q: What are Autopilot’s limitations?
A: Autopilot will not handle:

• Hardware replacements or physical repairs
• License approvals or procurement tasks
• Contacting external vendors/support
• Non-personal or sensitive data requests

If the device is offline or the contact is unassigned, Autopilot will fall back to KB/cloud-only answers or may not respond.

Q: How is Autopilot licensed and billed?
A: Autopilot is a paid add-on billed per user/month on an annual basis. Usage is measured quarterly (max daily active users vs. purchased licenses). Any difference is billed pro-rata for the remaining contract term.

Q: How quickly does new KB content become available to Autopilot?
A: Customer KB updates are available in about 30 minutes.

Q: Does Autopilot affect Copilot or vice versa?
 A: No. Custom instructions or usage in IT Autopilot do not impact AI Copilot features, and vice versa. They’re separate AI assistants serving different audiences.