GITNUXSOFTWARE ADVICE
Technology Digital MediaTop 10 Best Managed Services Software of 2026
Top 10 managed services software tools ranked for IT teams, with feature comparisons of Kaseya BMS, Atera, and PDQ for IT operations.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Kaseya BMS is the strongest fit when MSPs need ticket-driven execution with SLA control and remote support in one workflow, while Atera works well for teams that want API automation to trigger endpoint actions, and ManageEngine MSP Central is the budget entry if you want tenant-based device management and ticket-linked operations.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Kaseya BMS
Service desk workflow automation that moves cases into technician tasks with SLA-aware escalation logic.
Built for fits when MSPs need ticket-driven execution with SLA control and remote support inside one workflow..
Atera
Editor pickTechnician actions connect directly to service tickets, including remote sessions, deployment, and follow-up documentation.
Built for fits when managed service teams need ticket-driven endpoint actions with API automation..
PDQ
Editor pickAgentless software deployment execution that orchestrates packages from the console to selected endpoints on demand.
Built for fits when an MSP standardizes Windows deployments and patch runbooks across many customer endpoint groups..
Related reading
Comparison Table
Kaseya BMS
enterpriseBusiness management software covering PSA, ticketing, projects, and billing.
Service desk workflow automation that moves cases into technician tasks with SLA-aware escalation logic.
Kaseya BMS provides help desk ticketing with SLA tracking, technician assignment, and customer communications tied to each work item. Remote support and endpoint operations are linked to tickets so dispatching and troubleshooting stay inside the same workflow. It also includes change and asset-related processes so updates and configuration context can be referenced during case handling.
A key tradeoff is that deeper automation and tighter governance require careful workflow configuration across service types, queues, and escalation paths. Kaseya BMS fits situations where an MSP needs consistent service desk execution with measurable outcomes, not just ticket capture.
- +Ticket-to-remote support links reduce context switching during incidents
- +Workflow automation routes work by priority, queue, and service configuration
- +SLA tracking ties customer commitments to operational execution
- +Role-based access controls keep technicians and agents scoped to work
- –Workflow design takes time when many service variants and escalations exist
- –Some advanced integrations rely on external systems to complete data loops
- –Operational reporting depth depends on clean categorization and field discipline
- –UI navigation can feel heavy with large numbers of concurrent work items
MSP service desk teams
Incident intake to technician assignment
Faster resolution within commitments
IT operations coordinators
Change handling tied to tickets
Fewer change-related rework cycles
Show 2 more scenarios
Field services dispatchers
Work order execution scheduling
More predictable technician workload
Scheduling and assignment link customer requests to planned execution with status updates.
Account managers at MSPs
Operational reporting on commitments
Clearer service performance discussions
Resolution and backlog reporting supports SLA performance reviews tied to service groups.
Best for: Fits when MSPs need ticket-driven execution with SLA control and remote support inside one workflow.
More related reading
Atera
SMBIT management platform combining PSA, RMM, ticketing, billing, and reporting.
Technician actions connect directly to service tickets, including remote sessions, deployment, and follow-up documentation.
Atera fits service desks and IT teams that need one place to manage endpoints and deliver remote desktop support while tracking work against tickets. Core workflows include endpoint management, software deployment, patching, and technician-led remote sessions tied back to customer cases. Reporting and governance features center on technician activity, asset inventory, and workflow outcomes rather than only inventory browsing.
A tradeoff appears in how far automation can go without custom integration work, since advanced orchestration usually requires API or webhook glue between Atera and external systems. Atera works best when the team already runs a help desk process and wants device actions that align with ticket stages, like starting a deployment from a request and documenting results back in the service record.
- +Endpoint patching and software deployment run from technician and ticket context
- +API and webhooks support workflow automation across IT tools
- +Centralized asset inventory reduces manual reconciliation for support teams
- +Remote support sessions link back to the same operational workspace
- –Complex automations can require significant configuration and integration work
- –Some advanced governance needs rely on careful role and process design
- –Reporting depth can feel limited for organizations with custom KPIs
- –Multi-environment rollouts may take extra planning to avoid change collisions
Managed services desks
Patch rollout from active tickets
Fewer untracked changes
IT operations teams
Software deployment after ticket approval
Clear execution audit trail
Show 2 more scenarios
Support leadership
Asset visibility for faster triage
Shorter mean response
Device inventory powers targeted remote support and reduces discovery time.
Automation and engineering
Webhook-driven IT workflow chaining
Automated cross-tool handling
APIs and webhooks trigger actions in other systems when cases change.
Best for: Fits when managed service teams need ticket-driven endpoint actions with API automation.
PDQ
vertical specialistPatch management and software deployment tools for IT teams and MSPs.
Agentless software deployment execution that orchestrates packages from the console to selected endpoints on demand.
PDQ centers on deployment and patch workflows that run from a central console and target defined endpoint collections. Execution can be scheduled and constrained by endpoint reachability, status, and selection logic, which supports repeatable change windows. Remote support workflows are present for hands-on troubleshooting, but endpoint management and package orchestration remain the main focus for MSP day-to-day work.
A key tradeoff is that PDQ is most effective in Windows-centric estates and workflows, so organizations with large non-Windows fleets may need additional tooling for full coverage. PDQ is a strong fit when an MSP needs standardized software rollouts and patch compliance across multiple customers with consistent approval and runbook steps.
- +Agentless software deployment workflows reduce endpoint overhead for MSPs
- +Patch orchestration supports repeatable schedules across customer endpoint sets
- +Flexible targeting logic improves control over rollout scope
- +Central console execution history speeds change verification
- –Primarily designed for Windows endpoint estates
- –Deep PSA-style service workflows require external ITSM or PSA tooling
- –Network constraints can block operations if endpoint access paths differ
- –Complex multi-step packages take design discipline to keep maintainable
MSP endpoint management engineers
Standardize Windows app deployments
Repeatable rollouts with controlled scope
Service desk leads
Rapidly remediate client patch gaps
Fewer manual update escalations
Show 1 more scenario
Customer success operations
Provide consistent remote troubleshooting
Faster issue resolution cycles
Use remote support capabilities to validate endpoint state after changes.
Best for: Fits when an MSP standardizes Windows deployments and patch runbooks across many customer endpoint groups.
NinjaOne
SMBUnified IT operations platform with endpoint management and patching for MSPs.
Policy-driven remediation workflows that couple device state collection with guided fixes and reporting for service accountability.
NinjaOne is a managed services system built around endpoint and infrastructure monitoring plus remote remediation workflows. It combines device management, automated patching and software deployment, and centralized policy-driven operations across client environments.
NinjaOne also provides integrated inventory and reporting that supports day-to-day service operations and audit-ready accountability. Administrators can orchestrate actions through its automation and integration surfaces to keep operational changes consistent at scale.
- +Automation and policies drive consistent endpoint actions across many tenants
- +Unified inventory reporting reduces manual asset reconciliation work
- +Remote remediation workflows speed fixes without repeated technician sessions
- +Integration and API surface supports external tooling and custom workflows
- –Initial configuration and permission modeling takes planning for multi-admin teams
- –Some advanced governance steps require deliberate rollout and validation
- –Troubleshooting automation failures can require deeper knowledge of job execution
- –Complex environment modeling can push administrators toward specialized process discipline
Best for: Fits when MSPs need policy-driven endpoint management and automation with strong operational visibility across clients.
Action1
API-firstPatch management and remote monitoring platform for MSPs and IT departments.
Patch management with device-level compliance reporting and remediation tracking driven from the Action1 console and API.
Action1 runs Windows-focused endpoint patching, monitoring, and remote support from a centralized console. Core capabilities include agent-based patch compliance, scripted software deployment, and remote task execution across managed devices.
Reporting and controls support IT operations such as change windows, patch status baselines, and audit-friendly activity visibility. Action1 also provides an API and automation hooks for integrating endpoint inventory, remediation workflows, and help desk operations into existing processes.
- +Agent-based patch compliance views across managed Windows endpoints
- +Script-driven software deployment and remote task execution
- +Automation support via documented API endpoints
- +Activity visibility for operational troubleshooting and audit workflows
- –Windows endpoint focus limits coverage for mixed OS environments
- –Deeper governance needs require process discipline around change windows
- –Enterprise CMDB alignment and data modeling are not a primary strength
- –Complex ITSM workflows may require external tooling integration
Best for: Fits when Windows endpoint teams need patch compliance, scripted remediation, and help desk support integration.
SuperOps
SMBMSP platform for PSA, RMM, ticketing, projects, contracts, and billing.
End-to-end workflow automation that maps service desk steps to concrete managed actions with traceable execution.
SuperOps targets MSPs that need service desk workflows tied to operational execution across endpoints and servers. It centers on automation for provisioning, patch workflows, and remote support actions without forcing teams to stitch everything manually in separate tools.
The product includes integrations and an API surface meant for extending managed services operations into existing monitoring, identity, and ticketing systems. Governance features focus on team roles, change control around managed actions, and auditability of operational activity.
- +Workflow automation ties operational actions to service desk processes
- +Extensible integration and API support for existing MSP tooling
- +Action logs support audit trails for managed execution
- +Repeatable provisioning reduces time spent on first-time setup
- –More configuration needed to align roles with operational permissions
- –Some advanced endpoint management paths depend on add-on components
- –Complex environments may require careful orchestration to avoid overlap
- –Operational governance setup can slow early deployment
Best for: Fits when MSPs need managed service workflows that link tickets to automated execution.
Domotz
vertical specialistRemote network monitoring and management software for MSPs and internal IT teams.
Site maps that combine discovered devices with live health signals for quick network-path troubleshooting.
Domotz is a managed services tool built around visual network monitoring and site health views. It supports agent-based discovery and continuous reachability checks so MSP teams can spot device and link issues without manual ping sweeps.
Its core workflow centers on provisioning monitoring targets, receiving alerts, and drilling into device-level status to support remote troubleshooting. Domotz also offers an automation and integration surface for connecting monitoring results to external operations workflows.
- +Visual site topology view links device status to where issues occur
- +Agent-based discovery plus ongoing reachability checks reduces manual inventory work
- +Alerting supports fast triage with device and network context
- +API enables connecting monitoring events to external ticketing and automation
- –Multi-tenant governance and RBAC coverage can require careful setup
- –Deeper ITSM workflow coverage is limited compared with full PSA suites
- –Automation depends on integration projects for advanced routing logic
- –Large estates may need monitoring design to manage alert volume
Best for: Fits when MSP teams need visual network monitoring across many client sites, plus integration for alert-to-ticket workflows.
Huntress
vertical specialistManaged detection and response platform built specifically for MSPs to protect SMB endpoints.
Automated agent onboarding and policy assignment that standardizes endpoint security rollout across managed tenants.
Huntress is a managed services focused security management suite built around automated endpoint protection workflows. It pairs automated onboarding and policy controls with remote monitoring and support style operations, and it adds security-specific visibility for managed environments.
Core capabilities concentrate on endpoint protection coordination, agent lifecycle management, and alert handling patterns that can be handed off to service desk processes. Administrators get governance primitives for multi-tenant deployments through role-based access controls and audit logging.
- +Managed endpoint onboarding workflow reduces manual agent setup per customer
- +Policy configuration supports repeatable security posture across many endpoints
- +Audit log visibility helps trace administrative changes across managed tenants
- +Alert triage workflows fit handoff to service desk processes
- –Requires careful multi-tenant role design to avoid overly broad access
- –Deep integrations depend on connecting external ticketing and monitoring tools
- –Advanced automation needs knowledge of Huntress workflow configuration
- –Coverage gaps can appear for teams expecting full PSA and ITSM breadth
Best for: Fits when MSPs need centralized endpoint protection operations with strong admin governance for many tenants.
Lansweeper
vertical specialistIT asset discovery and inventory platform used by MSPs for agentless asset management.
Inventory-based relationship mapping that turns scan evidence into CMDB-style views for operational reporting and targeting.
Lansweeper performs automated IT asset discovery and ongoing inventory synchronization across endpoints and networks. It builds an actionable CMDB-style view from scan results, then drives remediation and workflow automation based on device, software, and configuration evidence.
The product also supports integrations for alerting, ticketing, and data exchange, which helps managed service teams operationalize findings without manual spreadsheets. Administrators can tune discovery scope, manage recurring scans, and control who can access reports and management actions.
- +Automated device and software inventory with recurring rescan schedules
- +CMDB-style relationships tie asset attributes to operational reporting
- +Built-in workflow automation from inventory rules and schedules
- +Integration options for alerting and ticketing workflows
- –High-quality results require careful discovery scope and credential setup
- –Complex environment mapping can demand ongoing configuration discipline
- –Deep automation often depends on how well inventory evidence is modeled
- –Some cross-system workflows require administrator scripting for glue
Best for: Fits when managed service teams need evidence-driven asset inventory with rule-based remediation workflows.
ManageEngine MSP Central
SMBUnified MSP platform offering PSA, RMM, and security with component-based pricing.
Tenant-centric onboarding and managed-work workflows that map endpoint tasks to customer service desk activity.
ManageEngine MSP Central targets managed service providers that need a single console for client onboarding, device management, and support workflows across many tenants. It combines endpoint discovery, remote support, and patch and software distribution tasks with service desk processes used to track work through resolution.
The solution also includes automation-oriented management settings that help standardize configurations across managed endpoints. Reporting and operational views tie device activities back to customer outcomes through the MSP-centric workflow model.
- +MSP tenant workflows connect device actions to customer support progress
- +Remote support tooling fits help desk use cases without switching systems
- +Patch and software distribution coverage supports recurring maintenance cycles
- +Centralized client onboarding reduces manual setup across endpoint fleets
- –Governance across large tenant counts can require careful role and policy design
- –Automation depth feels more rules-based than API-first for custom integrations
- –Advanced reporting depends on the quality of input data and labeling hygiene
- –Some multi-step runbooks need more configuration than ticket-driven teams expect
Best for: Fits when an MSP needs tenant-based device management and ticket-linked operations in one console.
Conclusion
After evaluating 10 technology digital media, Kaseya BMS stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right managed services software
Managed services software connects service desk workflows to device and network actions with automation, remote execution, and tenant governance. This guide covers Kaseya BMS, Atera, PDQ, NinjaOne, Action1, SuperOps, Domotz, Huntress, Lansweeper, and ManageEngine MSP Central.
The sections that follow focus on integration depth and operational control, including how tickets trigger technician actions and how administrators manage permissions across tenants. The comparison lens also targets API and automation surface area, since tools like Atera and SuperOps expose workflow hooks tied to execution paths.
Managed services software for ticket-linked endpoint, patch, and network operations
Managed services software coordinates IT delivery across endpoints and networks while keeping execution tied to service desk activity, so incident and change work can drive the next managed action. Kaseya BMS ties service desk workflow automation to technician tasks with SLA-aware escalation logic, which keeps operational timing aligned with ticket outcomes.
Atera and SuperOps take a similar ticket-to-execution posture by running technician actions and managed workflows in context, with automation and API support used to connect managed actions to external IT tools. In practice, these platforms differ in how they orchestrate deployment and remediation, how they handle multi-tenant permissions, and how directly they map service processes to concrete device state changes.
Execution integration, automation surface, and multi-tenant governance controls
Managed services software has to connect ticket and service context to concrete device actions without breaking traceability across many customer tenants. Kaseya BMS and Atera both tie technician execution back to service desk artifacts so incident and request work drives the next managed action.
Automation surface and governance determine whether those workflows stay reliable after onboarding grows. NinjaOne and Action1 emphasize policy and compliance mechanics for endpoint remediation, while SuperOps focuses on mapping service desk steps to traceable managed actions via extensible integration and API.
Ticket-linked workflow automation to technician tasks
Kaseya BMS moves service desk cases into technician tasks with SLA-aware escalation logic, and it routes work by priority, queue, and service configuration. SuperOps ties service desk processes to concrete managed actions with traceable execution, and it exposes integration and API support for workflow connections.
API and webhook-driven technician actions from service context
Atera connects technician actions directly to service tickets, including remote sessions, deployment, and follow-up documentation, and it supports API and webhooks for cross-tool workflow automation. SuperOps also provides an extensible integration and API surface when managed workflows must link into existing MSP tooling.
Agentless software deployment orchestration for standardized runbooks
PDQ provides agentless software deployment that orchestrates packages from the console to selected endpoints on demand. It also supports patch orchestration for repeatable schedules across customer endpoint sets, which supports MSP-standard Windows deployment patterns.
Policy-driven remediation with guided fixes and reporting
NinjaOne couples device state collection with guided fixes inside policy-driven remediation workflows and produces unified inventory reporting to reduce manual reconciliation work. Action1 provides device-level patch compliance reporting and remediation tracking driven from the Action1 console and API, and it supports script-driven software deployment and remote task execution.
Network topology discovery that supports alert-to-ticket workflows
Domotz combines site maps built from discovered devices with live health signals for network-path troubleshooting. It also supports integration for alert-to-ticket workflows, and it uses agent-based discovery plus ongoing reachability checks to reduce manual inventory work.
Evidence-driven inventory mapping for CMDB-style relationship views
Lansweeper turns scan evidence into CMDB-style relationship views for operational reporting and targeting. It uses automated device and software inventory with recurring rescan schedules, and it links asset attributes to operational reporting via discovery scope and credential setup.
How to choose managed services software for your delivery model
Selection should start from how execution should be triggered and governed across tenants, since each tool’s workflow engine emphasizes a different control path. Kaseya BMS and Atera concentrate on ticket-linked execution with different degrees of automation depth and integration dependency.
The next step should define which operations must happen inside the platform versus which can run as external ITSM or PSA workflows. PDQ’s agentless deployment orchestration fits Windows deployment runbooks, while NinjaOne and Action1 emphasize policy or compliance workflows for endpoint state change and remediation tracking.
Choose the platform that owns the ticket-to-action execution loop
If service desk workflow automation must move cases into technician tasks with SLA-aware escalation logic, Kaseya BMS is built around that queue and priority routing. If technician actions must attach directly to service tickets including remote sessions, deployment, and documentation, Atera provides that ticket-driven context plus API and webhooks.
Pick the automation philosophy based on where orchestration logic lives
If most workflow logic must be configured as service desk to managed action paths with traceable execution, SuperOps maps service desk steps to concrete managed actions. If orchestration must standardize on-console package execution with minimal endpoint overhead, PDQ’s agentless software deployment workflow is designed for that model.
Match endpoint remediation style to how change windows and compliance are enforced
For policy-driven remediation with guided fixes and reporting tied to device state collection, NinjaOne fits when repeatable endpoint actions must be governed as policies. For patch compliance with device-level compliance views and script-driven remote task execution, Action1 supports compliance tracking driven from console and API.
Validate multi-admin and multi-tenant governance paths before rollout
If onboarding requires multi-admin permission modeling and deliberate rollout and validation, NinjaOne’s initial configuration and permission modeling needs planning for multi-admin teams. If tenant governance is a key requirement, Domotz and Huntress both call out that multi-tenant governance and RBAC or role design requires careful setup.
Select inventory and network visibility tools based on troubleshooting workflow needs
If network-path troubleshooting needs visual site topology that links device status to where issues occur, Domotz provides site maps plus live health signals. If evidence-driven asset discovery and CMDB-style relationship mapping drive operational targeting, Lansweeper’s scan evidence to relationship views is the closer fit.
Assess platform integration dependencies for advanced workflow completion
If advanced integrations must complete multi-step data loops via external systems, Kaseya BMS signals that some advanced integrations rely on external systems. If deep governance must be paired with workflow automation, Atera’s complex automations may require significant configuration and careful role and process design.
Who managed services software fits best
Managed services software is most valuable when delivery work must remain bound to service desk artifacts while execution happens across endpoints and networks for multiple customers. Tools in this category differ in how they build the control plane around ticket execution, policy remediation, and multi-tenant operations.
Teams that rely on repeatable runbooks and measurable compliance benefit from selecting a platform whose automation and reporting mechanics match their day-to-day workflows.
MSPs running ticket-driven technician execution with SLA escalation
Kaseya BMS is designed to move service desk cases into technician tasks with SLA-aware escalation logic, and it routes work by priority, queue, and service configuration.
Managed service teams that want endpoint actions attached to service tickets with webhooks and APIs
Atera supports technician actions that connect directly to service tickets, including remote sessions and deployments, and it uses API and webhooks for workflow automation across IT tools.
Windows endpoint shops that standardize patch and deployment runbooks across endpoint groups
PDQ provides agentless software deployment and patch orchestration schedules across selected customer endpoint sets, with a focus on Windows endpoint estates.
MSPs that manage endpoint state through policies and remediation reporting
NinjaOne couples device state collection with policy-driven guided fixes and unified inventory reporting, while Action1 centers patch compliance and remediation tracking with console and API control.
Teams that need network visual context and troubleshooting to support alert workflows
Domotz builds site maps from discovered devices and live health signals for quick network-path troubleshooting, and it supports integration for alert-to-ticket workflows.
Common pitfalls when buying managed services software
Mistakes usually happen when workflow automation assumptions do not match the platform’s execution model. Another common issue is underestimating multi-tenant governance work for roles, permissions, and rollout validation.
A final pitfall is choosing an inventory or deployment tool without checking whether ticket-linked workflows and advanced integrations can close the operational loops your team expects.
Buying a ticket-to-action system but building workflows that cannot be finished without external systems
Kaseya BMS warns that some advanced integrations rely on external systems to complete data loops, so workflow prototypes should include those external dependencies before broad rollout.
Overbuilding automations without planning for configuration time and governance design
Atera notes that complex automations can require significant configuration and that advanced governance needs careful role and process design, so automation scope should be validated with role boundaries early.
Assuming a deployment tool also replaces ITSM or PSA service workflow depth
PDQ states it is primarily designed for Windows endpoint estates and that deep PSA-style service workflows require external ITSM or PSA tooling, so the purchasing decision should align with how service processes are managed.
Skipping permission modeling and rollout validation for policy remediation
NinjaOne highlights that initial configuration and permission modeling takes planning for multi-admin teams, so a pilot should include multi-admin workflows and validation steps.
Treating discovery and inventory as plug-and-play without planning discovery scope and credentials
Lansweeper calls out that high-quality CMDB-style relationship views require careful discovery scope and credential setup, so credential coverage should be tested before building operational targeting rules.
How We Selected and Ranked These Tools
We evaluated Kaseya BMS, Atera, PDQ, NinjaOne, Action1, SuperOps, Domotz, Huntress, Lansweeper, and ManageEngine MSP Central using feature depth that maps tickets to execution, automation coverage that connects workflow hooks to managed actions, and integration readiness via API or webhook surface. Features accounted for 40% of the scoring because ticket-linked execution loops and endpoint remediation workflows determine whether daily operations stay consistent across tenants.
Ease and value each accounted for 30% of the scoring because multi-tenant permission modeling, workflow configuration time, and operational overhead affect rollout speed and ongoing administration. Kaseya BMS earned the top position because service desk workflow automation moves cases into technician tasks with SLA-aware escalation logic and because ticket-driven routing reduces context switching during incidents.
Frequently Asked Questions About managed services software
How do integrations and APIs typically connect managed services software to existing monitoring and ticketing tools?
Which tool provides service desk workflow automation that escalates based on SLA and moves cases into technician tasks?
How does SSO and RBAC work in managed services software for multi-tenant admin control?
What data migration steps are usually required before endpoint management and inventory synchronization can run reliably?
How should admin controls be structured to prevent technicians from taking actions outside approved change windows?
When does agentless software deployment change the workflow design compared with agent-based endpoint management?
What breaks if ticket context is not carried into remote support or deployment steps?
Where does network monitoring tooling fall short compared with endpoint-centric patch and deployment workflows?
How can managed services teams extend workflows without rewriting every runbook from scratch?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Technology Digital Media alternatives
See side-by-side comparisons of technology digital media tools and pick the right one for your stack.
Compare technology digital media tools→