GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best Desktop Support Software of 2026
Top 10 desktop support software ranked by troubleshooting features for IT teams, with side-by-side comparisons of Zoho Assist, TeamViewer, and Splashtop.
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
Zoho Assist is the best fit for help desks that need both attended troubleshooting and unattended access with session artifacts, while TeamViewer Remote Support is the stronger pick for teams in mixed endpoint environments that want consistent attended support plus session traceability.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Zoho Assist
Session recording captures technician and end-user interaction to support QA and dispute resolution after remote sessions.
Built for fits when help desks need attended support plus unattended access with session artifacts..
TeamViewer Remote Support
Editor pickSession recording with technician activity context for attended troubleshooting review.
Built for fits when help desks need consistent attended troubleshooting and session traceability for mixed endpoint environments..
Splashtop SOS
Editor pickTechnician console plus an end-user launch step supports rapid attended connections with minimal setup friction.
Built for fits when help desks need quick attended remote sessions with controlled technician access for routine troubleshooting..
Related reading
- Customer Experience In IndustryTop 10 Best Computer Support Software of 2026
- Remote And Hybrid Work In IndustryTop 10 Best Desktop Remote Support Software of 2026
- Customer Experience In IndustryTop 10 Best Desktop Crm Software of 2026
- Customer Experience In IndustryTop 10 Best Desktop Appointment Scheduling Software of 2026
Comparison Table
Zoho Assist
SMBCloud-based remote support software with unattended access, file transfer, session recording, and diagnostics.
Session recording captures technician and end-user interaction to support QA and dispute resolution after remote sessions.
Zoho Assist supports attended sessions for live troubleshooting and unattended access for scheduled maintenance and recurring break-fix work. Session recording creates a tangible artifact for post-call review and internal QA, while the technician console keeps tools close to the remediation workflow. File transfer supports sending installers, logs, and small payloads without forcing users to switch channels. Administration centers on managing technician access and session controls for a multi-technician environment.
A tradeoff appears in how much governance is needed to keep session activity aligned with policy, since broad permissioning can raise audit review workload. It fits best when a help desk needs consistent remote control plus session artifacts for quality tracking, not when a team needs heavy on-prem deployment options or deep endpoint management from the same console.
- +Attended and unattended workflows reduce repeated triage for recurring issues
- +Session recording supports review and internal QA for support calls
- +In-session file transfer speeds up log collection and remediation
- +Technician console streamlines remote control operations for help desk staffing
- –Permission design requires discipline to prevent overly broad technician access
- –Advanced endpoint diagnostics are limited compared with full EDR platforms
- –External automation depends on Zoho ecosystem integrations and APIs
- –Agent and deployment behavior may not match strict on-prem constraints
IT help desk teams
Daily remote troubleshooting with consistency
Lower rework from repeat issues
Managed services providers
Unattended maintenance for customer fleets
Faster fix windows
Show 2 more scenarios
Support QA leads
Review recorded sessions for coaching
More consistent support outcomes
Session recording artifacts help QA teams audit troubleshooting steps and adherence to process.
Field support technicians
Send installers and capture logs
Shorter resolution cycles
File transfer reduces back-and-forth during remote control sessions for quick remediation workflows.
Best for: Fits when help desks need attended support plus unattended access with session artifacts.
More related reading
TeamViewer Remote Support
enterpriseRemote support software for unattended access, attended sessions, device management, and troubleshooting.
Session recording with technician activity context for attended troubleshooting review.
Technicians can start an attended support session and guide users through screen sharing and remote control from a technician console, with session tools like file transfer and diagnostic helpers during the same interaction. Admins can manage technician permissions and use audit-oriented reporting to track who accessed which endpoints and when. The product also fits environments that need a quick path from help request to interactive support without building custom endpoint workflows.
A tradeoff appears in deeper automation and governance, because workflow standardization often relies on operational process around technician sessions rather than fully declarative remote automation. TeamViewer Remote Support fits help desks that handle unpredictable incidents and need consistent attended troubleshooting more than background patching or policy-driven remediation.
- +Attended remote control with integrated file transfer for troubleshooting
- +Technician console workflows reduce steps between request and session
- +Session recording supports post-incident review and coaching
- +Permission controls help restrict technician actions
- –Automation depth depends more on support process than scripted enforcement
- –Some governance controls require ongoing admin maintenance
- –Unattended access setups add operational overhead for scaling
- –Large endpoint estates may need separate asset and policy tooling
IT help desk teams
Handle user tickets with remote sessions
Faster incident resolution
Managed service providers
Support multiple client endpoints
Consistent service delivery
Show 2 more scenarios
Desktop support managers
Train and audit technicians
Improved technician quality
Recorded sessions support retrospective review and coaching on troubleshooting steps.
Security and compliance teams
Require access visibility for sessions
Stronger access oversight
Audit-focused reporting and session controls provide evidence of who accessed endpoints.
Best for: Fits when help desks need consistent attended troubleshooting and session traceability for mixed endpoint environments.
Splashtop SOS
SMBOn-demand remote support software for attended and unattended access to desktops and mobile devices.
Technician console plus an end-user launch step supports rapid attended connections with minimal setup friction.
Splashtop SOS is built around attended support sessions that begin when an end user launches a client step and a technician connects through a technician console. Remote control is paired with session recording options and practical in-session tools like chat and file transfer to reduce back-and-forth. Technician access can be segmented with role-based controls, which supports governance for help desk teams that share the same console.
A tradeoff appears when environments need deep integration with identity providers, automated provisioning workflows, or granular endpoint data exports. Splashtop SOS fits best for help desks handling one-off issues like software errors, driver problems, and account lockouts where speed matters more than fleet-wide automation.
- +Attended session flow uses an end-user prompt to reduce technician guesswork
- +In-session file transfer cuts the time to share logs and screenshots
- +Session recording options support review and dispute resolution workflows
- +Technician permissions support controlled access for shared support teams
- –Deeper enterprise automation needs may require adjacent systems
- –Audit and governance visibility can feel lighter than tooling built for large ITIL processes
- –Endpoint inventory workflows are not the primary focus of the SOS support flow
- –Complex identity provider integration may take additional configuration work
IT help desk teams
Resolve office software errors remotely
Faster ticket closure
Managed service providers
Handle intermittent customer support
Reduced on-site visits
Show 2 more scenarios
Small enterprise IT
Triage user access issues
Lower repeat contact rate
Technicians provide guided troubleshooting with session tools while maintaining technician permissions.
Call center tech support
Support non-technical end users
Shorter time to resolve
An end-user prompt and guided console reduce the training burden for first-line support.
Best for: Fits when help desks need quick attended remote sessions with controlled technician access for routine troubleshooting.
AnyDesk Remote Support
SMBRemote desktop software for attended support, unattended access, and cross-platform device connections.
AnyDesk session controls combine remote control with inline file transfer and clipboard handling in the technician console.
AnyDesk Remote Support centers on fast remote control and screen sharing built for day-to-day troubleshooting without requiring deep IT workflow changes. Its technician console supports attended sessions with session controls such as file transfer and clipboard handling during support, plus quick handoff for recurring tasks.
The product includes device-side components and a management layer aimed at keeping endpoints accessible for both ad-hoc and scheduled work. Admin and governance options focus on access management and session traceability rather than deep IT service management automation.
- +Quick session start for attended troubleshooting with responsive remote control.
- +Session controls include file transfer and clipboard features during support.
- +Endpoint access supports unattended-style workflows through device components.
- +Technician console keeps common diagnostics tasks in one place.
- –Limited depth for workflow automation compared with ticket-driven helpdesks.
- –Governance controls depend on careful technician permission management.
- –Session recording and retention controls are less granular than enterprise suites.
- –Deep identity provider integration is not the strongest part of the admin layer.
Best for: Fits when teams need quick, attended desktop support with light governance and practical session controls.
ManageEngine Remote Access Plus
enterpriseRemote desktop support software with troubleshooting, system management, and endpoint diagnostics.
Technician permissions plus session recording combine with audit logs to support reviewable, permission-scoped remote support sessions.
ManageEngine Remote Access Plus provides remote control, screen sharing, and attended or unattended support through an endpoint agent and a technician console. It adds session recording and policy-driven technician permissions to help teams review incidents and constrain what technicians can do.
Integration centers on identity and directory services, plus IT service management links for incident and ticket workflows. Governance options include audit logging for remote sessions and administrative actions, with role-based access controls for technician and admin separation.
- +Session recording supports later review of support interactions
- +Role-based access controls limit technician actions per permission set
- +Audit logs track remote session and administrative activity
- +Unattended access works via endpoint agent rather than only ad-hoc support
- –RBAC setup can take time to map permissions to real support roles
- –Directory integration depends on consistent identity and endpoint enrollment practices
- –Automation depth is weaker than platforms focused on workflow extensibility
- –Screen sharing performance varies by network conditions and endpoint resource limits
Best for: Fits when mid-size support teams need recorded sessions, technician permission controls, and directory-integrated access.
RustDesk
API-firstOpen-source remote desktop software supporting self-hosted and managed remote support deployments.
Self-hostable rendezvous and relay path for remote connections, enabling tighter connectivity control than cloud-only setups.
RustDesk fits teams that need a self-hostable remote desktop service with both attended and unattended access. Its desktop agents provide remote control, screen sharing, and file transfer for support sessions without forcing a browser-only workflow.
Admin capabilities include an address book, device lists, and policies for technician access, with logs available for session auditing. The differentiator is a transport and relay model that can run entirely under an organization’s control, reducing reliance on third-party connectivity.
- +Self-host deployment option for relay and directory components
- +Attended and unattended remote control with session approval flow
- +Built-in file transfer during a remote control session
- +Technician console lists remote devices and manages connections
- –Fewer enterprise governance integrations than toolchains with ITSM and SIEM connectors
- –No documented fine-grained RBAC model for per-action technician privileges
- –Session recording and audit log depth depends on the deployment mode
- –Large endpoint fleets need deliberate provisioning to stay organized
Best for: Fits when a team needs unattended remote access with self-hosted connectivity and basic admin governance.
BeyondTrust Remote Support
enterpriseRemote support software with privileged access controls, session auditing, and technician workflows.
Session audit trails tied to technician permissions provide governance-ready visibility across both attended and unattended sessions.
BeyondTrust Remote Support pairs an attended and unattended remote access workflow with a technician console and an end-user experience for standard screen sharing and remote control tasks. The solution emphasizes governance through granular technician permissions and visibility controls that support enterprise support operations.
Session recording and session audit trails help teams review what happened during support interactions. BeyondTrust Remote Support also supports integration paths for identity and ticketing so remote sessions can align with existing operations and access policies.
- +Granular technician permissions control who can perform remote actions
- +Session recording and audit trails support post-incident review
- +Attended and unattended access workflows cover common support patterns
- +Identity integration supports consistent access policy enforcement
- –Deployment and policy setup requires defined admin governance discipline
- –Advanced workflows can add configuration complexity for small teams
- –File transfer and clipboard controls may need careful policy tuning
- –Admin console learning curve slows early rollout
Best for: Fits when enterprise support teams need governed remote sessions plus audit visibility for regulated workflows.
GoTo Resolve
SMBIT support software combining remote access, endpoint monitoring, ticketing, and device management.
End-user portal session initiation combined with unattended-ready endpoint tooling for consistent support flows.
GoTo Resolve targets desktop support teams that need remote control, screen sharing, and technician-side workflows in one console. It supports an end-user portal model for attended sessions and can run unattended access when agents are installed on endpoints.
Administrators get centralized session policy controls and technician permission controls, with monitoring and reporting that focus on support activity rather than only ticket status. For fast troubleshooting, it pairs remote session tools like file transfer and session recording with integration paths that fit common help-desk deployments.
- +Attended and unattended support use the same technician console workflows
- +End-user portal supports session launch without manual technician outreach
- +Session recording and activity visibility help with internal quality review
- +File transfer and common diagnostic actions stay inside the support session
- –Provisioning and role design require deliberate governance to avoid overbroad access
- –API depth is limited for custom automation compared with ticketing-first ecosystems
- –Automation coverage for complex endpoint remediation depends on external tooling
- –Advanced endpoint data breadth is thinner than inventory-focused suites
Best for: Fits when support teams need attended and unattended desktop sessions with strong technician workflow control.
RemotePC HelpDesk
SMBRemote support software for attended access, unattended computers, file transfer, and technician collaboration.
End-user access link flow that lets technicians initiate sessions without manual IP or RDP details.
RemotePC HelpDesk routes attended and unattended support sessions through a technician console and an end-user access flow. The tool supports remote control, screen sharing, and file transfer for common troubleshooting workflows.
Session management focuses on connection brokering and agent-based endpoint access, which reduces friction compared with manual remote desktop setup. Admin controls center on technician permissions and session policies that govern who can initiate and how sessions are handled.
- +Quick attended session start using an end-user access link flow
- +File transfer built into support sessions for faster remediation
- +Technician console consolidates remote control and support actions
- +Clear technician permission boundaries for support delegation
- –Limited visibility into endpoint change history beyond session context
- –Admin governance depth depends on careful technician permission design
- –Audit coverage is session-focused rather than fully ITSM-native
- –Advanced automation and API extensibility are not a primary focus
Best for: Fits when help desks need attended and unattended support with straightforward session workflows and delegation.
Atera
SMBIT management platform with remote monitoring, remote access, ticketing, automation, and billing.
Technician console ties remote session actions to endpoint inventory and monitoring context for faster triage.
Atera is a desktop support solution that pairs a technician console with an endpoint agent to deliver remote control, screen sharing, and hands-on troubleshooting. It centralizes device inventory and monitoring workflows so administrators can link endpoint context to support sessions.
Atera also provides automation for recurring IT tasks and integrations for connecting remote support operations to ticketing and IT service management systems. Governance features focus on technician permissions and operational visibility for distributed support teams.
- +Unified technician console for remote control, session handling, and endpoint context
- +Device inventory and endpoint monitoring feed support workflows and triage
- +Automation options reduce repetitive configuration and operational tasks
- +ITSM and ticketing integrations connect sessions to existing processes
- –Deeper enterprise rollout depends on careful technician permission design
- –Advanced workflows require more setup than ticket-first support tools
- –Screen sharing session workflows can feel constrained for specialized troubleshooting
- –Large fleets can increase agent management effort for consistent configuration
Best for: Fits when mid-market IT teams need remote support plus inventory and monitoring in one operational workflow.
Conclusion
After evaluating 10 customer experience in industry, Zoho Assist 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 desktop support software
Desktop support software used by help desks turns remote desktop sessions into trackable workflows that mix attended troubleshooting and unattended access. This guide covers Zoho Assist, TeamViewer Remote Support, Splashtop SOS, AnyDesk Remote Support, ManageEngine Remote Access Plus, RustDesk, BeyondTrust Remote Support, GoTo Resolve, RemotePC HelpDesk, and Atera.
The differences that matter show up in session recording, technician console design, and how admin governance limits remote actions. The tools also vary in how quickly technicians can start sessions using end-user portal flows or access link steps, and how much automation they can enforce.
Desktop support software that manages attended and unattended remote sessions
Desktop support software provides a technician console for remote control, file transfer, and diagnostic actions during attended support sessions. Many deployments also include unattended access workflows so technicians can remediate endpoints without real-time end-user participation.
Zoho Assist stands out with session recording that captures technician and end-user interaction to support QA and dispute resolution after remote sessions. BeyondTrust Remote Support prioritizes governance by tying session audit trails to technician permissions so regulated teams can review what each role performed across attended and unattended activity.
Core evaluation criteria for desktop support software workflows
Desktop support software is judged by how reliably it turns remote control into repeatable troubleshooting workflows. The strongest tools pair technician-console speed with governance so support teams can control who can do what and later verify what happened.
Session recording and technician-permission audit trails are the differentiators that prevent disputes and speed QA. Tools like Zoho Assist and BeyondTrust Remote Support add artifacts that help teams review sessions after the fact rather than relying on memory from attended calls.
Session recording and reviewable session artifacts
Zoho Assist records technician and end-user interaction to support QA and dispute resolution after remote sessions. ManageEngine Remote Access Plus also combines session recording with audit logs so recorded sessions map back to what technicians did during support.
Technician console workflow depth for attended troubleshooting
TeamViewer Remote Support uses technician console workflows that reduce steps between request and session while keeping attended troubleshooting structured. Splashtop SOS adds an end-user launch step inside the attended session flow to reduce technician guesswork.
Governed technician permissions tied to what actions are permitted
BeyondTrust Remote Support ties session audit trails to technician permissions so controlled roles can be reviewed across attended and unattended activity. RustDesk lacks a documented fine-grained RBAC model for per-action technician privileges, so governance depends more on the deployment shape and team process than on action-level controls.
End-user session initiation patterns that reduce manual coordination
GoTo Resolve uses an end-user portal session initiation approach that supports attended and unattended-ready support flows using the same technician console. RemotePC HelpDesk uses an end-user access link flow that lets technicians initiate sessions without manual IP or RDP details.
Automation surface and extensibility for scripted operations
Zoho Assist emphasizes support outcomes through session recording, but its permission design still needs discipline to prevent overly broad technician access. TeamViewer Remote Support reports that automation depth depends more on support process than scripted enforcement, which changes how far workflows can be standardized without external tooling.
Connectivity control for unattended access via deployment options
RustDesk offers self-hostable rendezvous and relay paths, which enables tighter connectivity control than cloud-only setups. Zoho Assist is commonly used when help desks need both attended and unattended workflows plus session artifacts for QA.
How to choose desktop support software by governance, workflow control, and automation needs
Start by selecting the workflow pattern that matches how tickets turn into remote sessions. The tools in this list split between attended-first tools that use end-user prompts and mixed attended-plus-unattended tools that rely on consistent technician console workflows.
Then choose the governance model that support leadership can operate day to day. Permission design differences show up in audit trail strength and in whether the tool provides action-scoped technician permissions that administrators can reason about.
Pick the session initiation model that matches help desk staffing
If the help desk needs technicians to start sessions without collecting IP or RDP details, RemotePC HelpDesk’s end-user access link flow is built for that delegation. If the same technician console should handle both attended and unattended support using an end-user portal, GoTo Resolve provides a consistent initiation path.
Choose the governance strength based on how disputes and audits get handled
If support QA and disputes require reviewable evidence from attended and unattended calls, Zoho Assist’s session recording is designed to capture technician and end-user interaction. If regulated workflows demand audit trails tied to technician permissions, BeyondTrust Remote Support provides governance-ready visibility across both session types.
Decide whether action-scoped permissions are mandatory for technician roles
If administrators must restrict what remote actions each technician can perform, BeyondTrust Remote Support’s granular technician permissions control supports that governance expectation. If RBAC action granularity is less critical and a simpler admin governance model is acceptable, RustDesk is viable because it supports self-host deployment with connectivity control but lacks a documented fine-grained RBAC model for per-action technician privileges.
Match attended troubleshooting speed with the tool’s console flow
If attended sessions should minimize back-and-forth using technician console workflows, TeamViewer Remote Support reduces steps between request and session. If attended access should use an end-user prompt to reduce technician guesswork, Splashtop SOS includes an end-user launch step inside the attended session flow.
Select a tool strategy based on connectivity control needs for unattended access
If unattended access must run with tighter control over rendezvous and relay paths, RustDesk’s self-hostable rendezvous and relay path supports that deployment constraint. If unattended access is paired with session artifacts for later review, Zoho Assist fits workflows that need QA after support sessions.
Who desktop support software fits best and why
Desktop support software fits teams that need attended troubleshooting plus unattended remediation without losing traceability of what technicians did. The right tool depends on whether the organization prioritizes reviewable session evidence, action-scoped permissions, or fast session initiation for end users.
This category also varies in how much admin governance discipline is required for permission design and how much automation depth can be enforced through the product versus through support processes.
Help desk teams running frequent attended support calls that require QA and dispute resolution
Zoho Assist records technician and end-user interaction, which supports later QA and dispute resolution after remote sessions. TeamViewer Remote Support also records attended troubleshooting with technician activity context for review.
Regulated IT operations that must map technician permissions to what actions were performed
BeyondTrust Remote Support provides session audit trails tied to technician permissions across attended and unattended sessions. ManageEngine Remote Access Plus pairs role-based access controls with session recording and audit logs for later reviewable support.
Support teams that want unattended access while controlling connectivity components in their own environment
RustDesk supports self-host deployment options for relay and directory components, which enables more control than cloud-only connectivity patterns. This matches teams that want unattended access with deployment-level connectivity control and a lighter governance integration footprint.
IT shops that need consistent technician workflows driven by end-user initiation
GoTo Resolve uses an end-user portal for session initiation that supports attended and unattended using the same technician console workflows. RemotePC HelpDesk uses end-user access link flow so technicians avoid manual IP or RDP details before starting support sessions.
Common mistakes when selecting and operating desktop support software
Teams often pick tools that look similar on remote control features but differ sharply in governance behavior. Permission design discipline decides whether technicians can exceed intended scopes, and the availability of audit trails and recording artifacts decides whether reviews are practical.
Another frequent failure comes from assuming automation depth matches ticketing-first workflows. Some tools require support process scripting outside the product because the built-in automation surface is not meant to enforce complex runbooks end to end.
Assuming permission controls are self-policing without admin governance discipline
Zoho Assist requires permission design discipline to prevent overly broad technician access. BeyondTrust Remote Support also requires defined admin governance discipline when setting policies, so technician permissions must be mapped to real support roles before rollout.
Ignoring the gap between attended session recording and action-level governance
Session recording alone does not restrict what actions technicians can perform, and BeyondTrust Remote Support is the tool in this set that explicitly ties session audit trails to technician permissions for governance-ready visibility. RustDesk supports self-hosted connectivity but does not provide a documented fine-grained RBAC model for per-action technician privileges.
Overestimating built-in automation depth for scripted support workflows
TeamViewer Remote Support notes that automation depth depends more on the support process than on scripted enforcement, so runbook consistency may require operational controls outside the platform. GoTo Resolve reports limited API depth for custom automation compared with ticketing-first ecosystems, so heavy workflow automation may need integration work.
Choosing a tool that adds session initiation steps that the team cannot operationalize
Splashtop SOS uses an end-user launch step inside attended session flow, so support success depends on end-user prompt readiness for each request. AnyDesk Remote Support focuses on quick attended session start and practical session controls, so it can be less dependent on extra end-user steps for routine troubleshooting.
How We Selected and Ranked These Tools
We evaluated each desktop support option using features at 40%, ease and value at 30% each to reflect what help desks need in daily troubleshooting. Zoho Assist set the ranking pace because session recording captures technician and end-user interaction for QA and dispute resolution after remote sessions.
BeyondTrust Remote Support ranked strongly for governance because session audit trails map to technician permissions across attended and unattended activity. TeamViewer Remote Support and Splashtop SOS scored well on attended troubleshooting workflow control, including technician console usability and end-user launch patterns that reduce the steps between request and session.
Frequently Asked Questions About desktop support software
How does session recording differ across Zoho Assist, TeamViewer Remote Support, and BeyondTrust Remote Support?
Which tools support both attended and unattended access for day-to-day help desk triage?
When does an end-user portal or end-user launch flow matter for session initiation?
What breaks if clipboard redirection is required during remote support sessions?
Which products offer the most direct identity integration for access governance and technician control?
How do audit logs and audit trails differ between ManageEngine Remote Access Plus and BeyondTrust Remote Support?
What tradeoff appears when self-hosting or organization-controlled connectivity is required in RustDesk versus cloud-centric tools?
When does endpoint inventory and monitoring need to be part of the remote support workflow instead of being a separate system?
How do integrations into ticketing and IT service management workflows affect remote session handoff?
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
Customer Experience In Industry alternatives
See side-by-side comparisons of customer experience in industry tools and pick the right one for your stack.
Compare customer experience in industry tools→