
GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best Customers Software of 2026
Ranked top 10 customers software for service teams, including Salesforce Service Cloud, Zendesk, and Dynamics 365, with Pipedrive, Freshsales, and Streak.
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
Pipedrive is the best fit for sales teams that want clear pipeline-driven workflows and smooth syncing with what you already use, whereas Gorgias is better when you need customer support automation built around an ecommerce-style omnichannel inbox.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Pipedrive
Deal-centric workflow automations trigger on pipeline stage and field changes with API-backed integrations.
Built for fits when sales teams need pipeline-driven workflows and external system sync..
Freshsales
Editor pickBuilt-in lead scoring and lifecycle-driven automation that routes follow-ups based on contact behavior.
Built for fits when shared contact context and CRM automation matter more than full service-desk omnichannel coverage..
Streak
Editor pickStreak’s record-linked email activity keeps message threads attached to pipeline stages for continuous context.
Built for fits when service teams run email-centric workflows and need pipeline automation in Gmail..
Comparison Table
Pipedrive
SMBPipedrive organizes customer contacts, sales pipelines, activities, and communications.
Deal-centric workflow automations trigger on pipeline stage and field changes with API-backed integrations.
Pipedrive’s core CRM model centers on organizations and contacts linked to deals, with activity logging tied to pipeline movement. Teams configure automations for lead and deal progression, assignment rules, and reminders tied to specific fields and stages. For integration depth, it exposes REST API endpoints and webhooks so external systems can push and pull records, update fields, and react to changes.
A key tradeoff is that service-case features are limited compared with dedicated service desk systems, so support operations usually need workarounds. Pipedrive fits situations where customer communication must be tracked alongside pipeline progress, such as sales-led onboarding or renewal motions where account activity maps to deal milestones.
- +Pipeline stages drive automation and reporting without custom code
- +REST API plus webhooks support bidirectional CRM synchronization
- +Activity timeline keeps call and email history near the deal
- +Built-in role-based access controls separate team permissions
- –Limited native customer service ticketing and routing compared with help desks
- –Custom fields and automation rules can become hard to audit at scale
- –Workflow coverage depends on careful configuration of stages and triggers
- –Data import and migration can require mapping discipline for complex histories
Revenue operations teams
Sync CRM deals to billing systems
Fewer manual status updates
Sales managers
Enforce consistent stage progression
More predictable forecasting
Show 2 more scenarios
Customer-facing sales teams
Track onboarding activities as deal milestones
Lower churn from better follow-up
Activity timelines attach communications to deals so lifecycle work stays visible.
Integrations engineers
Create custom lead qualification flows
Faster lead processing
Webhooks and REST endpoints support event-triggered enrichment and record updates.
Best for: Fits when sales teams need pipeline-driven workflows and external system sync.
Freshsales
SMBFreshsales provides CRM tools for customer contacts, sales activities, email, and deal tracking.
Built-in lead scoring and lifecycle-driven automation that routes follow-ups based on contact behavior.
Freshsales fits teams that need sales and service visibility in one CRM record model, with timelines that consolidate interaction history. Lead scoring and lifecycle stages help teams prioritize inbound and outbound contacts, while workflow automation can enforce routing and follow-up logic without custom code. The administration layer includes role-based access controls and organization settings for managing users, fields, and workflow permissions.
A tradeoff appears when service case management and omnichannel ticketing are primary requirements, because Freshsales focuses on CRM operations rather than full service desk depth. Freshsales works well when support, sales, and operations teams share contact context and need consistent assignment logic after form fills, emails, or meeting events.
- +Workflow automation can assign, notify, and follow up from CRM events
- +Contact timelines consolidate interactions for quicker context during outreach
- +Lead scoring and lifecycle stages improve prioritization for reps
- +API supports bidirectional sync for external systems and custom apps
- –Service desk capabilities lag dedicated ticketing and omnichannel suites
- –Complex field and workflow setups require careful governance discipline
- –Deep reporting across multi-system journeys can require extra integration work
- –Extensive customization adds admin overhead for workflow maintenance
Sales and service alignment teams
Unify contact history across functions
Faster handoffs and fewer repeats
Revenue operations teams
Automate lead assignment and tasks
More consistent coverage
Show 2 more scenarios
Marketing operations teams
Sync campaigns into CRM records
Cleaner data and better targeting
Integrations push campaign responses into contacts for scoring and routing decisions inside Freshsales.
Systems integrators
Extend Freshsales with custom workflows
Custom automation without UI limits
Developers use the API to connect fulfillment tools, data sources, and internal applications.
Best for: Fits when shared contact context and CRM automation matter more than full service-desk omnichannel coverage.
Streak
SMBStreak embeds CRM pipelines, customer records, and task tracking inside Gmail.
Streak’s record-linked email activity keeps message threads attached to pipeline stages for continuous context.
Streak’s core model centers on pipelines and records that map to contacts, deals, and related activities, with views that behave like boards and lists. It logs email threads to records and keeps an interaction timeline so that customer context stays tied to the pipeline stage. Automation is driven through workflow rules and actions that can trigger on stage changes, assignments, or updates.
A tradeoff appears when teams need full customer service case management features such as omnichannel routing, SLA tracking, and agent work queues. Streak fits best when the primary workflow is relationship-centric and email-heavy, such as handling inbound leads and outbound follow-up or coordinating partner outreach. It also suits organizations that want code-based extensibility through its API to sync records into their systems of record.
- +Email-thread to record mapping keeps customer history in one place
- +Pipeline boards and stage-based workflows support structured tracking
- +REST API enables custom sync and automation beyond built-in rules
- +Google Workspace-native UI reduces context switching for day-to-day work
- –Limited depth for agent case queues and SLA management
- –Advanced governance depends on careful setup of shared pipelines
- –Omnichannel support features are not the focus compared with service suites
- –Complex reporting may require external exports or API work
Customer success teams
Track renewals from outreach to outcome
Fewer missed follow-ups
Sales operations teams
Synchronize CRM records with internal systems
Consistent record updates
Show 2 more scenarios
Partner management teams
Coordinate co-selling communications
Clear ownership by stage
Shared boards route actions based on partner progress and email engagement.
Inbound support coordinators
Triage requests using email-first pipelines
Faster assignment decisions
Templates and stage workflows standardize intake while preserving thread history.
Best for: Fits when service teams run email-centric workflows and need pipeline automation in Gmail.
Gorgias
vertical specialistGorgias centralizes customer support for ecommerce stores across email, chat, social, and voice.
Rules engine that turns message and customer signals into routing, tagging, and automated actions in one workflow.
Gorgias brings customer service operations into a single conversational workspace that connects customer messages to case management and agent actions. Its core strength is a rules-driven automation layer that can tag, route, and respond based on message content, customer attributes, and workflow triggers.
Gorgias also supports integrations and an API surface used for syncing conversation context and extending automation beyond its built-in rules. Admin controls and audit visibility support day-to-day governance of inbox access, team roles, and operational changes.
- +Automation rules can route and trigger responses from message and customer context
- +Multi-channel inbox keeps case history attached to the same conversation thread
- +API supports building custom sync and extending workflow beyond native actions
- +Team role controls limit inbox access by user and department boundaries
- –Advanced automation needs careful rule ordering to avoid conflicting triggers
- –Deep reporting requires more setup effort than basic ticket analytics
Best for: Fits when service teams need inbox automation and integration depth across customer messaging channels.
Copper
SMBCopper provides CRM software built around Google Workspace contacts, deals, and tasks.
Native email and calendar syncing that writes engagement details into contact records with consistent history.
Copper powers contact and account-based CRM workflows by syncing data from email and calendar activity into shared records. The product focuses on sales execution with task automation, pipeline views, and field-level data capture that reduces manual updates.
Copper also provides an API for integrations and supports extensibility through webhook-based event patterns and custom apps built on its connector ecosystem. Admin controls cover user and permission management, plus activity visibility through logged interactions.
- +Email and calendar sync turns activity into timeline entries automatically
- +Pipeline and task automation reduce manual record keeping during follow-ups
- +API and integration connectors support bi-directional data sync with external systems
- +User and permission controls fit common sales team governance needs
- –Service and case management depth is limited compared with full customer service suites
- –Advanced workflow customization can require careful configuration and process discipline
Best for: Fits when service teams need CRM-grade contact records and automated sales-style follow-ups.
Close
SMBClose combines CRM records with calling, email, SMS, and sales pipeline management.
Close-side task timelines and stage-driven workflows that keep every communication tied to next actions.
Close is a sales-and-support contact center that unifies communications around accounts, tasks, and call or email activity. It centralizes interaction history inside a shared workspace and supports follow-up automation through configurable sequences and status-based workflows.
Close also provides a REST API for two-way integration with CRMs, support tools, and internal systems that need synchronization. Admin controls focus on user permissions, shared settings, and operational visibility across team activity.
- +Contact records tie calls, emails, and tasks into one interaction timeline
- +Workflow automation triggers on lead and opportunity stages without custom code
- +REST API supports custom sync for activities, notes, and entities
- +Team task queues and assignment rules reduce follow-up gaps
- –Case routing and SLA tracking are limited compared with dedicated service suites
- –Automation coverage can require careful configuration for multi-team processes
Best for: Fits when service teams need sales-style follow-up tracking with programmable API sync.
Insightly
SMBInsightly combines contact management, sales pipelines, projects, and customer relationship data.
Insightly’s CRM-to-project workflow linking lets tasks, timelines, and status updates live directly against customer records rather than in a separate system.
Insightly pairs CRM records with a work-management layer for teams that track customer interactions and then execute tasks on those records. Core modules include contact, account, lead, and opportunity management plus pipeline views and activity history for context.
The app supports automation for lead and sales workflows and offers a REST API for syncing data with external systems. Administration includes role-based access and configuration controls that help govern who can view and edit customer data.
- +Native project and task workflows linked to CRM records
- +REST API supports custom integrations and data synchronization
- +Pipeline and activity timeline reduce context switching for reps
- +Workflow automation covers common lead and opportunity moves
- –Advanced automation often needs careful process mapping
- –Reporting coverage for service metrics can feel thinner than pure service suites
- –Data sync design requires disciplined field mapping to avoid drift
- –Role permissions cover access, but audit depth can be limited for audits
Best for: Fits when service and sales teams need CRM records tied to task execution workflows without heavy custom development.
Keap
SMBKeap combines customer management, sales pipelines, billing, appointments, and marketing automation.
Keap automation sequences can run off CRM record and activity triggers to update fields and create tasks.
Keap centralizes contact management, lead tracking, and automation for small business sales and service teams. Its automation builder can trigger sequences from CRM record changes and customer interactions, then update fields and assign tasks without writing custom code.
Keap also provides an integration layer with REST API access and webhooks for syncing customer data between Keap and external systems. Admin controls focus on user permissions inside Keap, while enterprise-grade governance features like audit log exports are not as prominent as in larger service CRMs.
- +Automation builder triggers workflows from CRM updates and activity changes
- +REST API and webhooks support bi-directional sync with external systems
- +Contact and pipeline management keeps sales and follow-ups in one place
- +Task creation and assignment follow automation outcomes without custom development
- –Case management and routing depth lags behind dedicated service CRMs
- –Advanced governance controls like granular audit export are limited
- –Complex multi-object data synchronization can require careful mapping
- –Extending core service workflows usually depends on API plus developer effort
Best for: Fits when small service teams need CRM-led automation and external data sync for follow-up workflows.
SuiteCRM
API-firstSuiteCRM is open-source software for contacts, leads, opportunities, cases, and customer accounts.
REST API with custom module extensibility enables integration and business-rule extensions without replacing the CRM core.
SuiteCRM provides customer case management, contact and account records, and sales-oriented workflows through a configurable CRM interface. It is distinct for staying extensible on top of a modular PHP codebase with a documented REST API surface and an add-on ecosystem that supports custom modules and integrations.
Admins can configure fields, views, and business rules in the UI while still extending logic with custom code when workflow complexity exceeds configuration. Built-in activity tracking and role-based access controls support a governed CRM setup for service and support operations.
- +REST API and module hooks support deeper CRM integrations than basic sync tools
- +Configurable workflows, fields, and views reduce the need for custom development
- +Role-based access controls cover typical service and sales separation needs
- +Activity logging links user actions to records for traceable operations
- –Advanced automation often requires custom logic beyond built-in workflow rules
- –Admin governance and quality controls require stronger internal process discipline
- –UI configuration for complex routing can become time-consuming at scale
- –Omnichannel support coverage is limited compared with dedicated helpdesk platforms
Best for: Fits when service and sales teams need a customizable CRM with API extensibility for internal integration.
EspoCRM
API-firstEspoCRM manages customer accounts, contacts, opportunities, cases, and sales activities.
Case management plus configurable workflow rules let the same CRM entities drive routing, statuses, and follow-ups.
EspoCRM is a self-hostable CRM built around a configurable sales and service workflow with a case-oriented core. It supports entity customization, scripted business rules, and a REST API for integration with external systems like ticketing, telephony, and analytics.
EspoCRM’s extensibility centers on modules, API endpoints, and UI customization that adapts the same data across sales and support processes. For service teams that need full control over deployment and workflow behavior, it offers a narrower ecosystem than enterprise CRM suites.
- +Self-hosting option supports data locality and controlled network access
- +REST API covers common CRM actions and enables system-to-system automation
- +Business rules automate routing and field updates across modules
- +Entity and UI customization supports tailored service workflows
- –Advanced omnichannel and conversational inbox features are limited without add-ons
- –High customization can increase admin effort for ongoing schema and workflow changes
- –Integration with complex enterprise IAM and audit requirements takes extra planning
- –Reporting and dashboards can feel basic for large service analytics needs
Best for: Fits when service teams need configurable CRM workflows with self-host control over data and automation.
Conclusion
After evaluating 10 customer experience in industry, Pipedrive 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 customers software
This buyer’s guide covers customers software options used by service teams, with Pipedrive at the top and adjacent picks including Zendesk and Microsoft Dynamics 365 Customer Service in the broader service desk category. The guide focuses on how each tool handles customer-facing conversations and internal workflow control, then narrows to the integration and automation mechanisms that move cases through teams.
The covered set includes Pipedrive, Freshsales, Streak, Gorgias, Copper, Close, Insightly, Keap, SuiteCRM, and EspoCRM so readers can compare ticket-style service behavior against CRM-led workflows. .
Customers software for service teams that routes conversations, tracks cases, and syncs customer data across systems
Customers software is the set of platforms that records customer interactions and orchestrates follow-up work using automation rules and integrations, often tying message or activity events to a shared customer record. In service-focused workflows, tools like Gorgias use a rules engine to route and trigger actions from message and customer context inside a multi-channel inbox, while CRM-led options like Freshsales emphasize contact timelines and lifecycle-driven automation that routes follow-ups based on contact behavior.
For service teams that need workflow control tied to business stages, Pipedrive builds automations that trigger on pipeline stage and field changes and connects via REST API and webhooks for bidirectional CRM synchronization. To evaluate fit, the practical difference is whether the platform centralizes case queues and routing inside a dedicated service workflow like Gorgias or instead drives execution through CRM pipelines, records, and stage-based automation like Pipedrive.
Conversation routing and workflow automation controls
Some platforms centralize routing inside a multi-channel inbox like Gorgias, while others drive execution through pipeline stages and CRM records like Pipedrive and Close. The difference shows up in how consistently case history stays attached to the same conversation or interaction timeline.
Stage or pipeline-triggered automations
Pipedrive triggers workflow automations on pipeline stage and field changes and supports REST API plus webhooks for bidirectional CRM synchronization. Close triggers automation on lead and opportunity stages and keeps calls, emails, and tasks tied to next actions through stage-driven workflows.
Rules-engine inbox automation with conversation thread context
Gorgias uses an automation rules engine that routes and triggers actions based on message and customer signals inside a multi-channel inbox. Freshsales offers lifecycle-driven automation that routes follow-ups from CRM events, but it is positioned less like a dedicated service desk inbox.
Contact-linked timelines for agent context during follow-ups
Freshsales consolidates interactions in contact timelines so agents see behavior context while outreach is routed by CRM events. Copper writes email and calendar activity into contact records with automated timeline entries so teams keep a consistent engagement history.
Email-thread attachment to structured pipeline records
Streak maps email threads to record-linked pipeline stages so message history stays attached to the right pipeline item. Pipedrive favors pipeline automation for stage and field changes and uses API-backed integrations for CRM synchronization rather than deep SLA-ready case queue depth.
CRM-to-work execution linking for service and sales task delivery
Insightly links CRM customer records to native project and task workflows so execution status and updates live against the same customer data. EspoCRM pairs case management with configurable workflow rules so the same CRM entities can drive routing, statuses, and follow-ups without relying on a separate service desk workflow.
Choose the automation control plane that matches how cases move
A second decision is how the platform connects customer interactions to CRM records so agents can retrieve context quickly during handoffs. Tools that keep interaction history linked to conversation threads or contact timelines reduce the risk of agents acting on partial context.
Pick an inbox-first routing workflow or a CRM-pipeline-first automation workflow
If routing should happen from customer messages inside a shared multi-channel inbox, prioritize Gorgias because its rules engine triggers routing and automated actions from message and customer context. If routing should happen from sales-style stages that drive task assignment and reporting, prioritize Pipedrive because pipeline stage and field changes trigger automation without custom code.
Validate that case queues and SLA mechanics match actual service operations
If SLA tracking and case queue depth are required, treat Streak as a fit only when email-centric tracking is the primary workflow because its depth for agent case queues and SLA management is limited. If SLA-like service control needs are lighter and follow-up routing is more about stages and events, Close fits because case routing and SLA tracking are limited compared with dedicated service suites.
Match your context model to how agents need history during handoffs
If agents need contact behavior context in a single record, Freshsales fits because contact timelines consolidate interactions tied to CRM events. If teams need consistent activity history written automatically from email and calendar into CRM records, Copper fits because it syncs engagement details into contact record timelines.
Stress-test automation governance for multi-team complexity
If complex automation rules could conflict, treat Gorgias as a governance risk area because advanced automation needs careful rule ordering to avoid conflicting triggers. If governance requires careful mapping for custom field and workflow setups, treat Freshsales as a governance risk area because complex field and workflow setups need discipline to manage safely.
Confirm integration direction before standardizing the workflow
For bidirectional CRM synchronization, prioritize Pipedrive because REST API plus webhooks support two-way syncing with CRM data and pipeline changes. For CRM-led integration where external systems must be updated from record and activity triggers, prioritize Close or Keap because both provide API and automation triggers that can coordinate updates across systems.
Choose extensibility depth when built-in workflows are not enough
If the team needs deeper module extensibility and custom business-rule integration without replacing the CRM core, select SuiteCRM because it offers REST API and module hooks for integration and extensions. If the team values self-host control while accepting limited omnichannel capabilities, select EspoCRM because it supports self-hosting and REST API common actions for automation.
Who should buy customers software for service teams
Organizations also benefit when automation writes interaction history into the same customer record that agents use during follow-up. This reduces handoff gaps caused by separate ticket systems or disconnected activity logs.
Service teams that run case work from an inbox with message-based routing
Gorgias fits when routing depends on message and customer signals inside a multi-channel inbox so agents can keep case history attached to the same conversation thread.
Service organizations that coordinate follow-ups from CRM lifecycle behavior
Freshsales fits when contact behavior in CRM drives workflow automation and routing so follow-ups are assigned and notified from CRM events rather than inbox triage alone.
Service and sales hybrids that need stage-driven execution tied to interaction timelines
Pipedrive fits when pipeline stages and field changes drive automation and reporting, while Close fits when interaction timelines tie calls, emails, and tasks to next actions.
Teams that want email-first workflow tracking inside Gmail without heavy service-desk queues
Streak fits when agents need email-thread to record mapping with pipeline boards and stage-based workflows for structured tracking.
Service teams that require self-hosted CRM workflows and controlled network access
EspoCRM fits when self-hosting matters for data locality and network control, while its configurable case management and workflow rules run routing and statuses from the CRM.
Common buying and implementation mistakes
Another frequent issue is building service expectations around CRM pipeline features instead of dedicated case management requirements. This mismatch shows up quickly in SLA tracking, case queue depth, and how reliably handoffs preserve complete context.
Choosing an email-thread tool for full case queue and SLA operations
Streak is limited in depth for agent case queues and SLA management, so teams needing strong case and SLA operations should prioritize Gorgias or a dedicated service suite approach instead.
Letting multi-rule routing grow without ordering discipline
Gorgias can route and trigger automated actions from rules in a way that causes conflicts if rule ordering is not managed, so governance must include explicit rule precedence and testing.
Over-relying on CRM stage automation while service routing needs remain unclear
Close and Pipedrive can drive workflow automation from pipeline or stage triggers, but case routing and SLA tracking are limited compared with dedicated service suites, so service desk requirements must be mapped early.
Using heavy customization without a process for auditability and change control
Pipedrive notes that automation rules and custom fields can become hard to audit at scale, so governance must include change reviews for pipeline stage and field-triggered automation.
Assuming self-host CRM options include modern inbox features out of the box
EspoCRM includes self-hosting and case workflow rules, but advanced omnichannel and conversational inbox features are limited without add-ons, so add-on scope should be planned before rollout.
How We Selected and Ranked These Tools
We evaluated Pipedrive, Freshsales, Streak, Gorgias, Copper, Close, Insightly, Keap, SuiteCRM, and EspoCRM against conversation routing automation control depth and the integration mechanisms used to move customer data between systems. Features accounted for 40% of the score, and ease and value each accounted for 30% of the score, because service teams must adopt routing and automation without spending months on rewrites.
We treated Pipedrive as the top-ranked option because pipeline stages drive automation and reporting without custom code, and its REST API plus webhooks support bidirectional CRM synchronization rather than one-way updates. We used the score spread from each tool card to weight how consistently core workflow mechanisms work for the service use case across teams.
Frequently Asked Questions About customers software
How do Salesforce Service Cloud, Zendesk, and Microsoft Dynamics 365 Customer Service handle inbox routing rules?
Which platform is best for syncing CRM records and support cases through a REST API?
How does data migration work when moving customer history and tickets into a customer service CRM?
What tradeoff appears when selecting Zendesk versus Salesforce Service Cloud for complex admin governance?
How do SSO and RBAC controls usually differ between enterprise service suites and lighter CRMs?
When should automation be implemented with rules versus custom development for case management?
Which tool keeps message-thread context attached to workflow records for faster case follow-ups?
What breaks if an integration fails to match IDs across systems during customer data synchronization?
How do sandbox or testing environments typically work before rolling out workflow changes to production?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Top 10 Best Website Usability Software of 2026
- Top 10 Best Website Tour Software of 2026
- Top 10 Best Website Support Software of 2026
- Top 10 Best Website Spokesperson Software of 2026
- Top 10 Best Website Performance Testing Software of 2026
- Top 10 Best Website Performance Monitoring Software of 2026
- Top 10 Best Website Monitoring Software of 2026
- Top 10 Best Website On Call Software of 2026
- Top 10 Best Website Membership Management Software of 2026
- Top 10 Best Website Link Checker Software of 2026
- Top 10 Best Website Calendar Software of 2026
- Top 10 Best Website Booking Software of 2026
- Top 10 Best Website Booking System Software of 2026
- Top 10 Best Website Appointment Scheduling Software of 2026
- Top 10 Best Web Usage Tracking Software of 2026
- Top 10 Best Web Usage Monitoring Software of 2026
- Top 10 Best Web Traffic Monitoring Software of 2026
- Top 10 Best Web Traffic Monitor Software of 2026
- Top 10 Best Web Sync Software of 2026
- Top 10 Best Web Surfing Monitoring Software of 2026
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→