GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best Customer Service Management Software of 2026
Top 10 ranking of customer service management software with criteria and tradeoffs for teams, plus notes on Help Scout, Intercom, and Re:amaze.
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
Help Scout is the best pick for email-first support teams that want shared inbox case management with reliable automation and a dependable API, whereas Intercom fits when you need conversation-first workflows driven by chat, bots, and integrations.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Help Scout
Shared inboxes with a thread-centric agent workspace keep assignment and collaboration tied to the same conversation timeline.
Built for fits when email-first support teams need shared inbox case management with automation and a dependable API..
Intercom
Editor pickEvent-driven API access to conversation activity enables custom workflows tied to real agent interactions.
Built for fits when support teams need conversation-first workflows with automation and API-driven integrations..
Re:amaze
Editor pickAutomation rules can trigger on conversation state to route and apply response structure during active handling.
Built for fits when mid-market support teams want shared inbox workflows with automation and knowledge use in one place..
Related reading
- Customer Experience In IndustryTop 10 Best Customer Support Management Software of 2026
- Customer Experience In IndustryTop 10 Best Sales Contact Manager Software of 2026
- Customer Experience In IndustryTop 10 Best Customer Service Quality Assurance Software of 2026
- Customer Experience In IndustryTop 10 Best Customer Success Management Software of 2026
Comparison Table
Customer service management software coordinates tickets, messaging channels, and agent workflows so teams can handle higher throughput without losing customer context. This ranked list targets operators and technical evaluators who need concrete integration, automation, and permissions tradeoffs, then validate the fit through independent research rather than vendor claims.
Help Scout
SMBEmail-based customer support tool with shared inbox, knowledge base, and live chat.
Shared inboxes with a thread-centric agent workspace keep assignment and collaboration tied to the same conversation timeline.
Help Scout’s agent workspace is built around a single thread view with conversation history, so follow-ups stay tied to the underlying customer communication. Shared inboxes manage queue work and enable team collaboration through assignment, priorities, and visible status changes. Routing can use rules based on message attributes, while handoffs stay auditable through interaction trails inside the case timeline.
A key tradeoff is that Help Scout’s native coverage is strongest for email-first support rather than deep call-center operations like workforce management and recording. Teams that rely on high-throughput omnichannel contact center features may need additional integrations to reach parity. Help Scout fits when support leaders want consistent case handling, automation around inbox triage, and an API surface for system integrations.
- +Thread-first agent workspace keeps related customer context in one view
- +Shared inbox queues support assignment and status coordination across teams
- +Automation rules handle inbox triage and tag-driven workflow actions
- +API enables integration with CRM, ticket enrichment, and external tools
- –Stronger email workflow than telephony and contact center hardware workflows
- –Advanced governance needs careful role setup to prevent cross-team access
- –Complex routing often depends on well-defined message fields and conventions
- –Deep QA and QA capture features require external tools for coverage
Customer support managers
Track and coordinate shared inbox queues
Faster, consistent handoffs
Support ops teams
Automate triage with rule-based actions
Less manual inbox sorting
Show 2 more scenarios
Integrations teams
Sync cases with external systems
Better unified workflow data
Integrations teams use the Help Scout API to push and pull case and interaction data into other apps.
Customer experience analysts
Measure support outcomes from interaction history
Clearer support trend visibility
Analysts use searchable interaction trails to support reporting on resolution timelines and repeat contacts.
Best for: Fits when email-first support teams need shared inbox case management with automation and a dependable API.
More related reading
Intercom
mid-marketCustomer messaging platform combining live chat, bots, and help desk functionality.
Event-driven API access to conversation activity enables custom workflows tied to real agent interactions.
Intercom ties customer messaging to case-like conversation management, so agents can continue context across channels without manually copying details. Workflow configuration can drive assignment rules, status changes, and routing based on conversation attributes. The agent experience includes fast reply tooling and structured internal fields to reduce context switching during high conversation volume.
A tradeoff appears with governance and custom automation depth, because more complex routing and enrichment logic depends on well-defined events and consistent tagging. Intercom works best when teams already capture reliable customer attributes and want those fields to drive assignment and reporting across conversations.
- +Integrated conversation workspace keeps customer context and agent actions in one thread
- +Strong automation surface for assignment and workflow changes tied to conversation attributes
- +Extensible API supports custom sync and event-driven integrations for conversation workflows
- +Efficient tagging and internal fields help standardize agent notes at scale
- –Advanced routing logic can require careful configuration discipline
- –Queue management flexibility can feel less granular than dedicated contact-center suites
- –Some reporting views depend on consistent taxonomy like tags and statuses
- –Telephony-specific workflows may need additional integration effort for full parity
Support operations teams
Standardize routing using conversation attributes
Faster triage with fewer misroutes
Product support teams
Link feedback threads to customer records
Better continuity across replies
Show 2 more scenarios
Engineering teams
Build custom tooling on conversation events
Lower manual coordination overhead
API access supports automations and external systems that react to conversation lifecycle changes.
Customer support managers
Govern agent work with consistent fields
More consistent case handling
Structured internal notes and standardized tagging improve auditability of what happened and why.
Best for: Fits when support teams need conversation-first workflows with automation and API-driven integrations.
Re:amaze
vertical specialistE-commerce helpdesk combining shared inbox, live chat, and knowledge base for online stores.
Automation rules can trigger on conversation state to route and apply response structure during active handling.
Re:amaze supports an agent workspace where tickets and conversations share interaction history and consistent context for each customer. Conversation tagging and disposition-style handling help teams report on outcomes and keep internal follow-ups organized. Automation rules can move threads to the right queue and apply canned response behavior so agents do not rebuild the same reply structure each time.
A key tradeoff is that deep contact-center functions like workforce scheduling, call recording, and advanced QA workflows are not the core focus, so those requirements may need separate systems. Re:amaze fits teams that manage support volume through inbox triage and repeatable response patterns, with moderate workflow automation rather than complex, multi-stage case pipelines.
- +Unified agent workspace that keeps interaction history visible during replies
- +Automation rules for routing and follow-up that reduce manual triage
- +Knowledge and canned response support for faster, consistent agent replies
- +Integration surface for connecting external systems to support workflows
- –Advanced call center features like call recording require separate tools
- –Complex multi-step escalation rules need careful configuration discipline
- –Queue management depth can feel lighter than enterprise case platforms
- –Reporting customization is not as granular as some specialized ticketing suites
Customer support managers
Route incoming conversations by tags
Fewer missed SLAs
Support operations
Standardize answers with knowledge
Lower average handle time
Show 2 more scenarios
Customer experience teams
Coordinate follow-ups across agents
Improved time to resolution
Tags and internal notes support handoffs so follow-up work stays attached to the original conversation.
Engineering integration teams
Sync customer data into support
Less context switching
Integrations connect external customer systems so agents see needed context during ticket handling.
Best for: Fits when mid-market support teams want shared inbox workflows with automation and knowledge use in one place.
Missive
SMBCollaborative email and chat platform with shared inbox and task management for teams.
Real-time in-thread collaboration with internal comments and per-conversation assignment.
Missive centralizes customer conversations in a shared inbox with real-time collaboration, including internal comments and assignment directly on each thread. It supports multi-channel messaging workflows, with labels, canned replies, and templates that reduce repetitive work.
Case-style organization is handled through conversation grouping and tagging rather than a separate ticket record. Missive also provides automation via rules for routing, assignment, and notifications.
- +Conversation-focused workspace with threaded collaboration and internal comments
- +Rules support routing and assignment based on message attributes
- +Canned replies and templates cut response time for common requests
- +Labels and views keep fast-moving inboxes organized
- –Ticket lifecycle features like SLA tracking are not a core strength
- –Advanced governance controls are limited compared with enterprise case suites
- –Reporting depth for contact center metrics is narrower than dedicated platforms
- –Integrations depend on external setup for deeper workflows
Best for: Fits when teams need collaborative shared inbox workflows with lightweight case handling and routing rules.
Crisp
SMBCustomer messaging platform with live chat, chatbots, and shared inbox for startups.
Trigger-based workflow automation that can change conversation routing and agent assignment during an ongoing thread.
Crisp routes customer conversations and supports case-style collaboration inside an agent workspace. It combines live chat with messaging channels and provides shared visibility into ongoing interaction threads.
Core capabilities include workflow automation with triggers, canned responses and macros for faster handling, and conversation tagging for consistent internal context. Crisp also offers admin controls for team access and reporting views that support operational monitoring across queues and agents.
- +Conversation threads keep agent context in one place for faster follow-ups
- +Automation triggers reduce manual steps for common chat-to-case handoffs
- +Macros and canned responses support consistent replies across teams
- +Conversation tagging improves reporting and internal search by intent
- –Deep contact-center routing and SLA management require careful workflow design
- –Complex governance needs more process discipline than native RBAC granularity
Best for: Fits when support teams need live-chat driven case handling with light workflow automation.
Helpcrunch
SMBCustomer support platform with live chat, help desk, and knowledge base for SaaS and e-commerce.
Built-in macros and canned responses work directly inside ticket replies to speed consistent customer messaging.
Helpcrunch is a customer service management system built around shared team inboxes and real-time customer conversations. It combines ticket workflows with a structured agent workspace that supports internal notes, conversation tagging, and canned responses for faster handling.
Reporting and automation features help teams control assignment, manage follow-ups, and keep support interactions organized across channels. The product is best evaluated on whether its interaction history and workflow configuration match required governance and routing behavior.
- +Shared inbox workflows that keep conversation context during assignment
- +Macros and canned responses reduce repetitive drafting inside the agent workspace
- +Conversation tagging and internal notes support consistent dispositioning
- +Automation rules cover routing and follow-ups without building custom integrations
- –Deep omnichannel routing depends on setup choices and connector availability
- –Advanced SLA management and escalation rules are less comprehensive than contact-center suites
- –Reporting focuses more on operational visibility than agent quality scorecards
- –Governance controls for large multi-team deployments require careful permission design
Best for: Fits when support teams need configurable inbox-driven ticket workflows with fast agent productivity.
Gorgias
vertical specialistE-commerce-focused helpdesk with deep Shopify, Magento, and BigCommerce integrations.
Conversation tagging and automation rules can trigger multi-step agent actions tied to ecommerce customer signals.
Gorgias is a customer service management system built around handling support conversations for ecommerce brands, with a shared agent workspace for email and chat threads. It centralizes interaction history and customer context so agents can act without switching tools.
Automation rules let teams tag conversations, apply canned responses, and route work based on customer and conversation signals. Extensibility through an API supports custom workflows, data lookups, and third-party integrations that connect support actions to business systems.
- +Agent workspace keeps customer context and conversation timeline visible
- +Automation rules apply tags, macros, and statuses to reduce manual work
- +Extensible API enables custom actions tied to support events
- +Strong conversation labeling supports consistent triage and reporting
- –Advanced routing needs thoughtful rule design to avoid misclassification
- –Some workflows require external tools for deeper warehouse or ERP actions
- –Reporting depth favors support operations over QA scoring granularity
- –Omnichannel breadth depends on connected channels and partner apps
Best for: Fits when ecommerce teams need fast agent workflows and automation tied to customer context.
Front
mid-marketShared inbox platform for team email, chat, and SMS collaboration with automation.
Front’s per-message event API supports automation at the point of action, including assignment, label changes, and delivery state updates.
Front brings conversation-based ticketing into a shared agent workspace, with email, chat, and social messaging handled inside one thread per customer. Agents can use templates, macros, and internal notes to keep responses consistent while tracking context in conversation history.
Routing is rule-driven across inboxes, with assignment and status changes designed for queue management workflows. Integrations with common communication tools and an extensive API support automation, provisioning, and custom workflows tied to message events.
- +Threaded customer conversations reduce rework across channels
- +Rule-based inbox routing supports consistent assignment
- +Macros and templates speed up recurring replies with guardrails
- +API event model enables automation around message lifecycle
- –Advanced SLA and escalation workflows need careful configuration
- –Reporting and QA features depend on connected data sources
- –Large multi-team permissioning requires disciplined RBAC setup
- –Complex omnichannel routing can increase admin overhead
Best for: Fits when teams need shared inbox collaboration plus API-driven automation across multiple customer channels.
LiveAgent
SMBHelpdesk and live chat software with ticketing, call center, and social media integration.
Rule-based omnichannel routing that connects incoming messages to queues and agent assignment using configurable escalation logic.
LiveAgent manages customer service workflows with a shared agent workspace, ticket-based case handling, and omnichannel communication across channels. It supports automation using canned responses and macros plus routing driven by rules, queues, and agent assignment.
Reporting covers operational performance and customer feedback signals tied to interactions. Admin controls focus on user roles, permission scoping, and audit visibility for common support operations.
- +Shared agent workspace reduces context switching during multi-channel handling
- +Routing rules and queue management handle high-volume intake consistently
- +Macros and canned responses speed up repetitive replies with consistent phrasing
- +Operational reporting ties interaction activity to support outcomes
- –Complex routing and escalation rules need careful configuration to avoid loops
- –Advanced workforce management is limited compared with dedicated contact center suites
- –Omnichannel configuration can be time-consuming for multi-site deployments
- –Quality assurance coverage is narrower than tools focused on call-centric QA
Best for: Fits when support teams need ticket-based case handling with practical automation and rule-based routing.
Trengo
SMBMulti-channel communication platform combining shared inbox, chat, and voice for support teams.
Trengo conversation automation can trigger reassignment and follow-up steps based on message content and lifecycle events within the shared inbox workflow.
Trengo is a customer service management tool built around shared inboxes, automated conversation handling, and an agent workspace for fast replies.
It supports omnichannel message intake and case workflows that keep interaction context attached to each conversation.
Trengo also includes knowledge-centered service features such as macros and internal guidance so agents can standardize responses.
Automation rules and integrations with external systems are used to route, escalate, and keep teams aligned on service targets.
- +Agent workspace keeps customer context and actions in one view
- +Conversation automation rules can route and reassign without manual steps
- +Macros and internal notes support consistent replies across channels
- +Omnichannel inboxes reduce the need to switch between tools
- –SLA management and escalation rules are less granular than workflow-heavy suites
- –Advanced routing may depend on configuration discipline across teams
- –Reporting is lighter for QA scoring and evaluation workflows
- –Integration options can require custom setup for niche contact center systems
Best for: Fits when support teams need fast omnichannel handling with automation and standardized agent actions.
Conclusion
After evaluating 10 customer experience in industry, Help Scout 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 customer service management software
This guide covers customer service management software for shared inbox and case management workflows, with examples from Help Scout, Intercom, Re:amaze, Missive, Crisp, Helpcrunch, Gorgias, Front, LiveAgent, and Trengo.
It focuses on integration depth, automation behavior, admin governance controls, and the specific workflow shapes each tool supports across email, chat, and omnichannel handling.
Customer service management software that turns customer conversations into governed case workflows
Customer service management software routes inbound customer messages into case-style records, keeps agent work tied to a shared conversation history, and applies rules for assignment, tags, and follow-ups.
Tools like Help Scout and Front center on thread-first shared inbox case management, where status, internal notes, and collaboration live with the same message timeline instead of in separate modules. Teams typically use these systems to reduce manual triage, standardize replies with canned responses and templates, and maintain consistent queue behavior across multiple agents and channels.
Evaluation criteria for case routing, agent workflow control, and operational governance
The deciding factor is how a tool handles customer conversations as the unit of work, then how automation and governance controls shape queue throughput.
Help Scout, Intercom, Front, and Trengo each offer a different balance of conversation workspace, API-driven extensibility, and routing flexibility tied to message lifecycle events.
Thread-centric agent workspace for assignment and collaboration
Shared conversation timelines reduce rework when multiple agents handle the same issue, and Help Scout is designed around a thread-centric workspace that keeps assignment and collaboration tied to the same conversation timeline. Missive delivers real-time in-thread collaboration with internal comments and per-conversation assignment, which supports fast handoffs without switching contexts.
Automation rules that act on conversation state during handling
Automation should trigger on active conversation attributes so routing and response structure changes happen while work is in flight. Crisp uses trigger-based workflow automation that can change routing and agent assignment during an ongoing thread, while Re:amaze supports automation rules that trigger on conversation state to route and apply response structure during active handling.
API and event hooks for syncing conversation activity into external systems
Integration depth matters when customer service data must flow into CRM, data warehouses, and internal tooling without manual exports. Intercom provides event-driven API access to conversation activity for custom workflows tied to real agent interactions, and Front exposes a per-message event API that supports automation at the point of action with assignment, label changes, and delivery state updates.
Inbox queue management with rule-driven routing and assignment consistency
Queue behavior should be predictable under high intake, with rules that connect incoming messages to queues and agent assignment. LiveAgent is built for rule-based omnichannel routing that connects incoming messages to queues and agent assignment using configurable escalation logic, while Helpcrunch supports shared inbox workflows that keep context during assignment and includes automation rules for routing and follow-ups.
Standardized agent replies using macros, canned responses, and templates
Response standardization improves first-contact resolution by reducing repetitive drafting across agents. Helpcrunch includes built-in macros and canned responses directly inside ticket replies to speed consistent customer messaging, and Missive adds canned replies and templates that cut response time for common requests.
Governance and permission design for multi-team access control
Large deployments need controlled access to shared inboxes and case records so teams do not see each other’s work accidentally. Help Scout supports automation and a governance posture that requires careful role setup to prevent cross-team access, and Front notes that large multi-team permissioning requires disciplined RBAC setup for consistent controls.
Decision framework for selecting the right customer service management workflow tool
Start with the workflow shape, then confirm that automation triggers and governance controls match how service work actually moves across agents and teams.
The steps below split choices by conversation-first handling, live chat emphasis, and integration-driven automation requirements across multiple channels.
Choose the conversation work unit: thread-first shared inbox vs chat-first messaging
If the day-to-day workload is email-like issue handling in shared inboxes, Help Scout is a strong match because it routes messages into shared inboxes and emphasizes a thread-centric agent workspace for collaboration. If the primary work begins as chat conversations and must stay unified through live messaging, Intercom fits better with an integrated conversation workspace and strong automation hooks.
Pick an automation philosophy: stateful in-thread routing vs queue-first escalation logic
Select Crisp or Re:amaze when automation must act on conversation state during active handling, because their workflow triggers can change routing and response structure inside an ongoing thread. Choose LiveAgent when the workflow requires rule-based omnichannel routing that connects incoming messages to queues and agent assignment using configurable escalation logic.
Confirm extensibility needs using named event surfaces and integration connectors
If the system must push assignment and conversation activity into custom workflows, Intercom’s event-driven API access to conversation activity is a direct fit. If the system must support point-of-action automation around message events, Front’s per-message event API is the cleanest match.
Validate standard reply tooling inside the agent workspace
For teams that need macros and canned responses built into the reply flow, Helpcrunch is designed for macros and canned responses working directly inside ticket replies. For collaborative shared inbox handling with reusable phrasing, Missive’s templates and canned replies keep fast-moving conversations organized through labels and views.
Match governance depth to team size and shared inbox sharing rules
When cross-team visibility control is strict, Help Scout requires careful role setup to prevent cross-team access, so governance design must be planned upfront. When multi-team permissioning must scale across many communication channels, Front requires disciplined RBAC setup to keep routing and status changes correctly scoped.
Which teams should use customer service management tools like these
Different tools target different operational realities like inbox-first triage, ecommerce context, high-volume omnichannel routing, or multi-channel agent collaboration.
The segments below map directly to the best-for profiles described for each tool.
Email-first support teams that run shared inbox case management
Help Scout fits when teams need shared inbox case management with automation and a dependable API, especially when customer messages are handled as threads with status, internal notes, and searchable conversation history. Front also fits this segment when email, chat, and social-style messages must remain unified inside one thread per customer.
Conversation-first teams that need strong automation hooks and event-driven integrations
Intercom fits teams that require conversation-first workflows with automation tied to conversation attributes and API-driven integrations. Crisp fits teams that need live-chat driven case handling with light workflow automation and trigger-based routing changes inside the thread.
Mid-market ecommerce or store operations that want knowledge and support in one place
Re:amaze fits when mid-market support teams want shared inbox workflows with automation and knowledge use in one place, so agents can answer with knowledge and response structure while handling cases. Gorgias fits when ecommerce teams need fast agent workflows and automation tied to ecommerce customer context, using conversation tagging and automation rules that can trigger multi-step actions.
Teams that prioritize collaborative shared inbox workflows with lightweight case handling
Missive fits teams that need collaborative shared inbox workflows with lightweight case handling and routing rules, supported by in-thread internal comments and per-conversation assignment. Helpcrunch fits when support teams want configurable inbox-driven ticket workflows that keep conversation context attached during assignment.
Organizations that need ticket-based operations with omnichannel routing and escalation logic
LiveAgent fits when teams need ticket-based case handling with practical automation and rule-based routing, including configurable escalation logic for queue assignment. Trengo fits teams that need fast omnichannel handling with automation and standardized agent actions, with conversation automation that can trigger reassignment and follow-up steps based on message content and lifecycle events.
Pitfalls that show up during customer service management tool selection
Most failures come from mismatched workflow assumptions, weak governance planning, or automation that does not align with routing reality.
The pitfalls below map directly to constraints and configuration-heavy behaviors seen across these tools.
Choosing a tool without planning for routing rule conventions
Complex routing often depends on well-defined message fields and conventions, so Help Scout and Helpcrunch need careful setup to avoid misclassification when routing logic uses message attributes. Intercom can also require careful configuration discipline for advanced routing logic so queue flow stays consistent.
Expecting contact-center-grade SLA and escalation depth from inbox-first platforms
SLA management and escalation rule granularity are less comprehensive in tools like Missive, Crisp, and Trengo compared with workflow-heavy contact-center suites. If SLAs and workforce controls are central, LiveAgent is built to handle configurable escalation logic for queue assignment.
Underestimating governance overhead when multiple teams share inboxes
Advanced governance needs careful role setup in Help Scout, and Front requires disciplined RBAC setup for large multi-team permissioning. Without governance planning, shared inbox access can become inconsistent across teams even when routing rules are correct.
Relying on QA and QA capture inside the platform when coverage depends on external tools
Help Scout highlights that deep QA and QA capture features require external tools for coverage, so QA workflows cannot be treated as native to the platform. LiveAgent also reports narrower quality assurance coverage than tools focused on call-centric QA, so evaluation and scoring workflows may need other tools.
How We Selected and Ranked These Tools
We evaluated Help Scout, Intercom, Re:amaze, Missive, Crisp, Helpcrunch, Gorgias, Front, LiveAgent, and Trengo using three scored areas: features, ease of use, and value. Features carried the most weight at forty percent, while ease of use and value each accounted for thirty percent in the overall rating. This ranking reflects editorial research and criteria-based scoring from the documented capabilities in each tool’s reviewed profile rather than hands-on lab testing.
Help Scout separated itself from the lower-ranked tools by combining thread-centric shared inbox case management with an integration-focused API and automation rules for inbox triage, and that combination boosted its features score and its practical value for email-first teams.
Frequently Asked Questions About customer service management software
How do Help Scout and Front handle shared inbox work without losing conversation history?
What API capabilities matter for automation and data syncing across customer service tools?
Which tools support SSO and security controls that map to agent access policies?
How does data migration usually work when moving existing cases, tags, and conversation content?
What admin controls enable governance over assignment, status changes, and workflow configuration?
Which tool fits omnichannel routing needs that include escalation logic rather than simple queue assignment?
When do conversation tagging and canned responses reduce time to resolution, and where does it still fall short?
What breaks if an organization needs a strict ticket record per issue instead of a conversation-thread model?
How do Helpcrunch and Trengo differ in knowledge and response standardization inside the agent workspace?
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→