GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best After Sales Service Software of 2026
Top 10 after sales service software ranked for support teams with Zoho Desk, Intercom, ClearOps, plus features and pricing comparisons.
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 Desk is the best fit for after-sales teams that want case workflows with SLAs and customer portals already aligned, whereas Intercom is a strong alternative if your post-sale support needs omnichannel case handling with API-driven integration.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Zoho Desk
SLA-based escalation automations trigger actions on breach events across case lifecycles.
Built for fits when support orgs need case workflows, SLAs, and Zoho-aligned automation without heavy custom builds..
Intercom
Editor pickAutomation in the conversation flow can trigger routing, tags, and messages from in-product events.
Built for fits when post-sale support needs omnichannel case handling, automation, and API integrations..
ClearOps
Editor pickWarranty entitlement verification is operationalized inside the service-to-repair workflow, not handled as a separate checklist step.
Built for fits when warranty and repair lifecycles must be consistent across intake, dispatch, and closure..
Related reading
Comparison Table
Zoho Desk
SMBCombines ticket management, workflows, knowledge bases, SLAs, and customer portals.
SLA-based escalation automations trigger actions on breach events across case lifecycles.
Zoho Desk supports case management with routing, assignment, and multi-channel customer messaging so support teams can handle email, chat, and social channels from one queue. Knowledge base authoring and article linking help deflect repeat inquiries and speed resolution by keeping agents on the same reference content. SLA policies attach to cases and trigger escalation actions when response or resolution targets are missed.
A key tradeoff is that deeper workflow automation and external system syncing depend on configuring Zoho automation and integration touchpoints rather than relying only on out-of-the-box templates. Zoho Desk fits teams that already run Zoho CRM or need structured case histories tied to customer records, while still wanting configurable escalation and knowledge workflows.
- +SLA timers and escalation rules enforce response and resolution targets
- +Knowledge base articles link to cases for faster, consistent answers
- +Zoho CRM integration keeps customer context inside support case views
- +RBAC and audit logs support governance across agents and admins
- –Advanced automations require careful workflow design to avoid loops
- –Omnichannel setup needs channel-specific configuration and mapping
- –Some custom reporting needs extra configuration beyond standard dashboards
Customer support operations teams
Enforce SLA and escalation discipline
Fewer missed service targets
Agents in omnichannel helpdesks
Handle multi-channel inquiries in queues
Lower time-to-triage
Show 2 more scenarios
RevOps and CRM admins
Keep customer records synchronized
More accurate customer interactions
Zoho CRM context appears in case handling and helps agents verify account details faster.
Knowledge managers
Reduce repeat questions with articles
Higher first-contact resolution
Article search and linking supports reuse of approved answers during active case work.
Best for: Fits when support orgs need case workflows, SLAs, and Zoho-aligned automation without heavy custom builds.
More related reading
Intercom
API-firstCombines customer messaging, help desk workflows, knowledge content, and support automation.
Automation in the conversation flow can trigger routing, tags, and messages from in-product events.
Intercom provides omnichannel case management with conversation threads, shared team inboxes, and routing controls for customer support handoffs. Automation rules can assign labels, set statuses, and trigger messages based on events, while knowledge articles can be linked to responses to reduce repeat inquiries. Governance is handled through team and role permissions for agents and admins, plus reporting views that separate workload and resolution outcomes.
A tradeoff appears for teams that need work order management, installed-base service history, or serial-number-level warranty entitlement flows, because Intercom does not replace full service management suites. Intercom works best when a warranty or service question arrives as a conversation that can be routed, answered with knowledge, and escalated with structured context.
- +Omnichannel inbox routing keeps agent context in one customer conversation timeline
- +Automation rules handle triage, labels, and follow-up without custom workflow code
- +REST API and webhooks support bidirectional integration with external CRMs and ticket tools
- +RBAC-style team permissions control who can view, manage, and respond
- –Serial-number warranty entitlement workflows require external systems integration
- –Complex multi-step service processes need heavy automation configuration
- –Field dispatch and technician scheduling are not a native focus area
- –Reporting is strong for support operations but thin for lifecycle analytics
Customer support operations teams
Route warranty questions from multiple channels
Faster escalation and consistent handling
Customer success teams
Run proactive post-sale follow-ups
Lower repeat contacts
Show 2 more scenarios
RevOps and integration teams
Sync cases with CRM and ticketing
Reduced manual status updates
Webhooks and the REST API move case data and events between systems for unified records.
Technical support leads
Escalate complex issues with context
Shorter time to technical triage
Teams escalate conversations with tagged evidence and knowledge links for faster resolution handoffs.
Best for: Fits when post-sale support needs omnichannel case handling, automation, and API integrations.
ClearOps
vertical specialistAI-powered after-sales platform for machinery OEMs and dealer networks optimizing spare parts planning and technician availability.
Warranty entitlement verification is operationalized inside the service-to-repair workflow, not handled as a separate checklist step.
ClearOps is a better fit than generic case management when warranty entitlement checks and repair lifecycle steps must move in lockstep with service contracts and installed-base records. Its operational model connects service requests to downstream work orders, technician assignments, and repair outcomes, which reduces the need for separate workflow tools. ClearOps also supports API-driven extensibility so other systems can push service intake, update asset serial status, and record repair completions. The main governance coverage targets service operations roles rather than deep platform engineering teams.
A key tradeoff is that advanced customization depends on configuration plus integration work rather than building every workflow logic natively inside the UI. ClearOps fits teams that already run a service operations backbone and need structured warranty claim processing and repeatable repair workflows that remain consistent across locations. For one-off, highly bespoke customer journeys, configuration effort can outweigh the value of the unified repair lifecycle model.
- +Warranty claim workflow stays connected to repair execution
- +Work-order lifecycle links service outcomes to service history
- +API automation supports system-to-system updates across service events
- +Role-based access supports separation of intake and operations roles
- –Complex workflow logic may require configuration plus integration work
- –Omnichannel customer self-service depth can lag case-only suites
- –Offline mobile workflow support is limited compared with dedicated field-service apps
- –Reporting needs setup to match cross-team operational KPIs
After sales operations teams
Standardize repair lifecycle across sites
Fewer handoff errors
Warranty claims analysts
Verify eligibility during intake
Cleaner claim decisions
Show 2 more scenarios
Installed-base management teams
Track serial-based service events
More accurate asset state
Service updates keep installed-base records aligned with repair completions and statuses.
Service integration teams
Automate updates from CRM and ERP
Lower manual data entry
API-driven integrations push and pull intake, contract context, and repair status changes.
Best for: Fits when warranty and repair lifecycles must be consistent across intake, dispatch, and closure.
More related reading
Gorgias
vertical specialistUnifies ecommerce support tickets, order data, returns, refunds, and customer messaging.
Automation rules that act on inbox conversations with ecommerce context to trigger assignments and response preparation.
Gorgias centralizes omnichannel after-sales support into a unified inbox and focuses automation on case routing, tagging, and response generation. The system connects natively to ecommerce workflows, with rule-based triage that can attach customer data to replies and reduce time spent on repetitive service requests.
Automation is built around triggers, conditions, and actions across channels, while the API supports programmatic case operations and custom integrations. Admin controls support multi-agent work through shared inbox configuration and permission-scoped access to support functions.
- +Rule-based automation for triage, assignment, and tagging across support channels
- +Unified inbox view that reduces context switching during high-volume customer follow-ups
- +REST API supports case updates, conversation handling, and integration-driven workflows
- +Built-in ecommerce context supports faster response drafting from order and customer signals
- –Advanced governance controls are limited compared with enterprise service suites
- –Complex workflow logic can require careful rule design to avoid conflicting outcomes
- –Reporting depth for operational metrics can lag behind dedicated helpdesk analytics
- –Non-ecommerce scenarios rely more on external systems and manual enrichment
Best for: Fits when ecommerce support teams need automation-driven case management without building custom tooling.
HappyFox
SMBHelp desk and ticketing system with asset management and post-sale support workflows.
REST API plus configurable automation lets case fields and status changes drive external updates.
HappyFox runs after-sales workflows from customer service inbox through case handling and workflow routing for support teams. It provides ticket-based case management with shared team views, SLA tracking, and automation rules to route and update work as tickets move.
Reporting and knowledge features support repeatable resolutions and service history access for customer and asset-related contexts. Integration options include REST API and common helpdesk connectivity to connect support events with CRM, ERP, or internal systems.
- +Automation rules can update ticket fields and notify teams during routing
- +SLA monitoring helps track response and resolution targets on active tickets
- +Knowledge base articles link to cases to standardize after-sales resolutions
- +REST API supports custom sync of tickets, contacts, and attachments
- –Advanced governance for large teams can need careful role and workflow design
- –Some after-sales specifics rely on custom fields instead of built-in warranty objects
- –Workflow complexity can slow testing when multiple triggers update the same case
- –Deep ERP and field service alignment often requires middleware mapping
Best for: Fits when after-sales teams need ticket automation, SLA tracking, and API-driven system sync.
Help Scout
SMBCustomer support platform with shared inbox, knowledge base, and post-sale customer communication.
Shared mailbox conversation threads with team collaboration tools, built to keep after sales history readable across reassignment.
Help Scout is an after sales service tool built around email-first support and customer collaboration in a shared inbox. Case management is centered on conversation threads, team workflows, and reporting that maps directly to support output.
Automation is handled through saved replies, macros, and routing rules that trigger at intake without needing custom code. Help Scout also exposes a REST API so teams can connect case data with CRMs and other back office systems.
- +Email thread handling keeps customer context intact across handoffs
- +Macros and routing rules automate intake without custom development
- +REST API supports case and contact synchronization to external systems
- +Admin views clarify assignment rules and team inbox ownership
- –Limited built-in tooling for field service dispatch and technician scheduling
- –No native installed-base or asset serial number workflow module
- –Automation coverage is narrower for multi-step, stateful repair lifecycles
- –Extensibility depends on API work for custom intake and governance flows
Best for: Fits when teams need email-based omnichannel case management and light automation.
More related reading
Front
SMBCustomer operations platform with shared inbox and workflows for post-sale team collaboration.
Shared conversation threads with granular internal assignments let multiple teams collaborate on the same after sales inquiry.
Front is an after sales service inbox for cross-channel case handling with shared team visibility and a routing layer that reduces back-and-forth between agents and departments. It centers omnichannel message threads, internal notes, and automation rules that assign, tag, and notify based on message events.
Front also supports admin controls for team access, audit-relevant activity history, and an extensibility surface via API and webhooks for connecting CRM and ticket systems. For after sales workflows, it pairs well with knowledge base links and repeatable replies to speed warranty and repair communications without forcing a full service CRM rebuild.
- +Threaded shared inbox reduces handoffs during warranty and repair status updates
- +Automation rules can route and tag messages based on sender, keywords, and channel
- +REST API and webhooks support bidirectional sync with ticketing and CRM systems
- +RBAC-style team permissions limit agent access across shared mailboxes
- –Work order and field service scheduling logic is limited without external systems
- –Advanced SLA timers and escalations require careful integration with a case engine
- –Complex case data models like installed-base records need external storage
- –Multi-system reporting depends on pulling events into a reporting layer
Best for: Fits when teams need shared omnichannel inbox workflows with API-driven routing to external service systems.
Re:amaze
vertical specialistCustomer support and help desk platform built for ecommerce with post-sale order management integration.
Conversation-native knowledge base that surfaces articles inside the agent inbox while updating case resolution steps.
Re:amaze focuses on after-sales support with omnichannel messaging, case workflows, and a knowledge base that agents can use inside conversations. It couples customer self-service and agent-assisted handling through a unified inbox, with routing and macros for faster resolution.
Re:amaze also adds automation hooks for notifications, tagging, and tasking across support interactions. The product is best judged on how far its integration depth and API surface go for CRM, ERP, and service systems rather than on generic ticketing alone.
- +Unified inbox for social and messaging channels with shared case context
- +Macros and routing rules reduce repetitive after-sales triage work
- +Knowledge base articles support resolution during active conversations
- +Automation for tagging and follow-up helps standardize handling
- –Field-service workflows like dispatch and technician scheduling are limited
- –Warranty and entitlement workflows are not natively modeled end to end
- –Advanced admin governance needs disciplined configuration to stay consistent
- –Many deep integrations require custom work beyond basic connectors
Best for: Fits when after-sales teams need omnichannel case handling and agent macros over full field-service automation.
More related reading
ServiceFirst
vertical specialistAfter-sales operations software covering warranty management, ticketing, technical support, and spare parts catalogues.
Warranty claim workflow that ties entitlement checks to repair status updates inside the same request.
ServiceFirst is an after sales service software focused on managing customer service requests from intake through resolution. Core capabilities include work order tracking, warranty claim handling, and service history visibility for returning customers.
Automation is centered on status-driven workflows and notifications that route requests to the right team. The product differentiates through operational guidance around field and depot repair processes rather than generic ticketing alone.
- +Work order lifecycle supports multi-step repair and closure tracking.
- +Warranty claim workflows fit common entitlement verification steps.
- +Service history views help agents answer repeat questions faster.
- +Status-driven notifications reduce manual follow-up work.
- –Omnichannel case management and unified communications are limited.
- –API depth for automation and system provisioning is unclear without testing.
- –Installed-base asset serial data capture is not designed for heavy IoT telemetry.
- –Advanced RBAC and audit log controls are not described for complex governance.
Best for: Fits when support teams need end-to-end work order and warranty handling for installed products.
ReverseLogix
enterpriseReverse logistics and warranty claims management system with fraud prevention and financial reconciliation.
Warranty entitlement verification that gates claim workflow stages and drives replacement or repair routing decisions.
ReverseLogix targets after sales operations with a focus on warranty claim workflows, entitlement checks, and service history capture. The system centers on work order and service request processes tied to installed-base and asset serial number tracking.
Automation is oriented around case routing, status management, and document collection that supports repair depot and field handling handoffs. Its differentiation comes from configurable warranty and returns processes that connect eligibility logic to downstream repair or replacement actions.
- +Warranty entitlement workflow ties eligibility to claim progress and outcomes
- +Asset and serial number tracking supports consistent service history and traceability
- +Configurable return and repair depot workflows match common after sales variants
- +Automation around case stages reduces manual status updates
- –Automation depth depends on careful workflow configuration and testing
- –Integration coverage is likely to require custom mapping for ERP and CRM objects
- –Mobile offline and field execution tooling may be less mature than service-first suites
- –Reporting granularity may require administrative tuning for complex KPIs
Best for: Fits when warranty and returns workflows need configurable eligibility logic tied to asset-level tracking.
Conclusion
After evaluating 10 customer experience in industry, Zoho Desk 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 after sales service software
After sales service software manages post-purchase support from intake to repair outcomes, including warranty eligibility steps, work order lifecycles, and resolution histories. This buyer’s guide covers Zoho Desk, Intercom, ClearOps, Gorgias, HappyFox, Help Scout, Front, Re:amaze, ServiceFirst, and ReverseLogix.
Tools in this set differ most in how warranty logic is executed inside the service workflow, how conversation routing ties into case state, and how much automation and API surface exists for system sync. Zoho Desk and ClearOps emphasize SLA-based escalation and repair-connected warranty flows, while Intercom and Front focus on automation inside omnichannel customer conversations.
After sales service software for warranty, work order, and post-purchase case management
After sales service software supports service request intake, warranty claim management, and service history tracking so support teams can resolve issues with traceable outcomes. Systems like Zoho Desk tie SLA-based escalation automations to case lifecycles, so response and resolution targets can trigger actions without manual intervention.
Service-first workflows also matter because warranty entitlement checks must gate claim stages and stay linked to repair execution. ClearOps operationalizes warranty entitlement verification inside the service-to-repair workflow, and ReverseLogix gates warranty claim workflow stages with asset-level eligibility logic tied to serial-number tracking.
After sales service software capabilities to evaluate across warranty and work orders
Warranty handling succeeds when entitlement checks drive downstream work order stages instead of living in a separate checklist. The products in this set differ most in where warranty logic executes, how service outcomes feed back into case state, and how automation and API surface support system sync.
Warranty entitlement gates inside the request workflow
ClearOps ties warranty entitlement verification to the service-to-repair workflow so eligibility stays connected to repair execution from intake through closure. ReverseLogix gates claim workflow stages with asset-level eligibility logic that links eligibility to claim progress and replacement or repair routing decisions.
SLA-based escalation automations across case lifecycles
Zoho Desk triggers escalation actions on SLA breach events across case lifecycles so response and resolution targets can drive follow-up without manual monitoring. Gorgias uses rule-based automation on inbox conversations, but advanced SLA governance is narrower than enterprise service suite patterns.
Omnichannel routing that preserves a single customer conversation timeline
Intercom keeps agent context in one customer conversation timeline and uses omnichannel inbox routing plus conversation-level automation rules for triage and follow-up. Front provides shared conversation threads with granular internal assignments so warranty and repair status updates do not get fragmented across handoffs.
Automation and API surface for external service system sync
HappyFox pairs a REST API with configurable automation so ticket fields and status changes can update external systems during routing. Front adds API-driven routing to external service systems, but field service dispatch and technician scheduling logic stays limited without external systems.
Knowledge and macros embedded in agent workflows
Zoho Desk links knowledge base articles to cases so consistent answers get surfaced during active support work tied to SLA escalation. Re:amaze uses a conversation-native knowledge base that updates case resolution steps inside the agent inbox.
Repair and work order lifecycle linkage to service history
ServiceFirst supports a work order lifecycle that tracks multi-step repair execution and closure while matching warranty claim workflows to entitlement verification steps. ClearOps keeps work-order lifecycle links between service outcomes and service history so service records reflect what repair actually completed.
Choose based on where warranty logic lives, how routing drives case state, and how automation scales
After-sales teams need to decide where warranty and entitlement logic executes: inside ticket workflows, inside service-to-repair workflows, or as an eligibility gate that controls claim stages. They also need to choose how routing and automation connect to system sync through a documented automation and API surface so ERP, CRM, or repair systems stay consistent with case state.
Pick the warranty execution model that matches the service process
Choose ClearOps if warranty entitlement verification must be operationalized inside the service-to-repair workflow so eligibility stays connected to repair execution across dispatch and closure. Choose ReverseLogix if warranty and returns require configurable eligibility logic that gates claim workflow stages tied to asset and serial number tracking.
Select an escalation approach that matches SLA enforcement needs
Choose Zoho Desk when SLA breach events should trigger escalation actions across case lifecycles so response and resolution targets can drive follow-up without manual monitoring. Choose Gorgias when automation should drive triage and response preparation from ecommerce context even if enterprise-grade SLA escalation governance is less complete.
Decide how much omnichannel conversation state matters for agents
Choose Intercom when the requirement centers on omnichannel inbox routing that preserves a single conversation timeline with in-product context driving tags and routing. Choose Help Scout when shared mailbox conversation threads are the priority so customer after-sales history stays readable across reassignment with light automation.
Match automation and API depth to the number of external systems in the workflow
Choose HappyFox when REST API access and automation should update ticket fields and notify teams for external system sync during routing and lifecycle changes. Choose Front when API-driven routing to external service systems is required while accepting that work order and field service scheduling logic stays limited without external systems.
Set governance expectations for complex multi-step service automation
Choose Zoho Desk when complex escalation rules can be designed with careful workflow planning because advanced automations require workflow design to avoid loops. Choose Gorgias when multi-step automation needs may outgrow governance controls because advanced governance for large teams is limited versus enterprise service suites.
Confirm whether field service dispatch and scheduling are native requirements
Choose ServiceFirst or ClearOps when end-to-end work order and repair tracking must stay tied to warranty handling since both connect repair execution to request lifecycle outcomes. Choose Help Scout or Re:amaze when dispatch and technician scheduling are not core requirements because field-service workflows like dispatch and technician scheduling are limited.
Who should buy which after sales service software approach
After sales service software buyers typically need warranty handling that stays synchronized with ticket state and repair execution so agents can close the loop on outcomes. Different tools fit different operations based on whether warranty is modeled inside workflows, whether escalation relies on SLA breach triggers, and whether external systems must be updated through automation and API.
Support organizations running warranty claim workflows tied to repair execution
ClearOps and ServiceFirst keep warranty and repair stages linked to work order lifecycle updates so claim decisions stay connected to what the repair process actually did.
Omnichannel after sales teams that manage inquiries across chat, email, and messaging
Intercom and Front keep routing and conversation context in shared inbox experiences so agents can handle warranty and repair status updates without losing timeline continuity.
Teams that require SLA breach escalation to drive follow-up actions automatically
Zoho Desk is built around SLA timers and escalation rules that enforce response and resolution targets across case lifecycles instead of relying on manual escalation queues.
Ecommerce support groups that need conversation-level automation for triage and assignments
Gorgias and Front support automation rules that act on inbox conversations with channel context for triage, labeling, and assignment decisions without building custom workflow code for basic steps.
Installed-base and asset-level warranty eligibility workflows with serial numbers
ReverseLogix and ClearOps focus on asset and serial-number related eligibility so warranty claim stages can be gated by outcomes and traceable service history.
Common after sales service software buying mistakes
Misalignment usually happens when warranty logic is treated as a separate form instead of a state-gating workflow tied to service outcomes. Another frequent error is assuming field service dispatch and technician scheduling exist natively when the selected tool emphasizes case or conversation management instead.
Buying a case-only workflow tool and then trying to bolt on warranty entitlement as a checklist step
ClearOps operationalizes warranty entitlement verification inside the service-to-repair workflow so eligibility stays connected to repair execution rather than becoming a disconnected approval step.
Assuming advanced escalation governance exists without workflow design discipline
Zoho Desk can enforce SLA timers and escalation rules, but advanced automations require careful workflow design to avoid loops.
Choosing an omnichannel conversation platform when serial-number warranty entitlement needs deep system integration
Intercom and other conversation-first tools may not natively support serial-number warranty entitlement workflows end to end and can require external systems integration.
Expecting native field service dispatch and technician scheduling in email-first or lightweight case suites
Help Scout and Re:amaze keep omnichannel inbox and macro workflows central, but field-service workflows like dispatch and technician scheduling are limited.
Underestimating how much automation logic needs governance when workflows become multi-step
Gorgias supports rule-based automation for triage and tagging, but complex workflow logic may require careful rule design to avoid conflicting outcomes.
How We Selected and Ranked These Tools
We evaluated Zoho Desk, Intercom, ClearOps, Gorgias, HappyFox, Help Scout, Front, Re:amaze, ServiceFirst, and ReverseLogix on feature coverage, automation behavior, and operational fit for after sales support workflows. Features weighed 40% based on whether warranty logic is tied to request or repair execution, how routing keeps conversation context, and whether work order lifecycle linkage supports repair history.
Ease and value each weighed 30% based on workflow usability and the clarity of how teams can run automations and connect external systems. Zoho Desk ranked highest because SLA timers and escalation rules enforce response and resolution targets across case lifecycles, with knowledge base articles linking directly to cases for faster consistent answers.
Frequently Asked Questions About after sales service software
How do Salesforce Service Cloud and Zendesk differ for case workflows in after-sales support?
Which tool handles service contract context and warranty claim processing inside a single operational workflow?
When should warranty entitlement verification be a workflow gate instead of a post-check step?
How do API and webhook capabilities affect integrations between after-sales software and ERP or CRM systems?
Which solutions support SSO and enforce role-based access controls for multi-agent support teams?
How is data migration typically handled for installed-base records and service history when switching tools?
What breaks if after-sales workflow routing relies only on tags instead of status-driven automation?
Where does field service dispatch capability fall short in conversation-first tools compared with work-order execution tools?
How should admins manage configuration across case intake, routing, and escalation rules without breaking existing workflows?
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→