GITNUXSOFTWARE ADVICE
Customer Experience In IndustryTop 10 Best Live Chat Room Software of 2026
Top 10 Live Chat Room Software ranking with technical comparisons, including Zendesk Chat, Freshchat, and Intercom, for support teams.
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
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Zendesk Chat
Chat-to-ticket handoff that preserves conversation context in the shared Zendesk data model.
Built for fits when teams need chat-to-ticket continuity with controlled automation and API-driven integration..
Freshchat
Editor pickAutomation rules that trigger on conversation events and drive routing and assignments.
Built for fits when support teams need chat automation plus governed integrations across multiple systems..
Intercom
Editor pickAutomation and API-driven conversation lifecycle actions tied to a unified contact and event model.
Built for fits when mid-size teams need governed chat workflows and extensibility via a documented API..
Related reading
Comparison Table
This comparison table maps Live Chat Room software tools across integration depth, each tool’s data model and schema, and the automation plus API surface used for provisioning and extensibility. It also contrasts admin and governance controls such as RBAC, audit log coverage, configuration boundaries, and operational throughput under concurrent chats. The goal is to show how different architectures affect integration work, automation design, and governance at scale.
Zendesk Chat
helpdesk chatDelivers real-time website and in-app chat with help desk agent workspace, automations, and reporting.
Chat-to-ticket handoff that preserves conversation context in the shared Zendesk data model.
Zendesk Chat routes chat sessions to agents and can create or update Zendesk tickets, which keeps conversation history attached to a single schema across channels. The integration depth is strongest inside the Zendesk ecosystem, where chat triggers ticket fields, assignment, and macros using the same underlying workspace concepts. Extensibility is exposed through Zendesk’s API and app frameworks so systems can ingest chat events, enrich visitors, and synchronize state in external CRMs.
A tradeoff is that governance and automation depend on Zendesk’s configuration model, which can add setup work when chat needs custom routing beyond the supported triggers and macros. Zendesk Chat fits best when teams already run ticketing in Zendesk and need chat to follow the same data model for identity, routing, and escalation. It also works well when predictable throughput and consistent agent context matter more than fully custom UI logic.
Automation and the API surface support event-driven workflows such as assignment rules, proactive messaging, and chat-to-ticket handoff based on conversation attributes. The admin layer supports RBAC scoping for agent access and workspace permissions, which limits who can configure widget settings and routing logic. Audit and change tracking support governance by making it easier to review operational changes that affect routing, visibility, and agent capabilities.
- +Chat sessions can hand off into Zendesk tickets with consistent conversation history
- +Zendesk API and apps support event ingestion and visitor or conversation enrichment
- +RBAC and admin permissions control access to configuration and agent workflows
- +Automation rules connect chat attributes to routing, macros, and assignment behavior
- –Deep custom chat routing can require more work within Zendesk trigger and rule patterns
- –Widget configuration is largely constrained to Zendesk’s supported customization options
Best for: Fits when teams need chat-to-ticket continuity with controlled automation and API-driven integration.
More related reading
Freshchat
customer chat suiteSupports website and mobile chat with conversation routing, knowledge base options, and reporting inside the Freshworks suite.
Automation rules that trigger on conversation events and drive routing and assignments.
Freshchat fits teams that need live chat plus operational control over routing, tagging, and follow-up actions across multiple channels. The data model ties conversations, visitors, and messages into objects that automation rules and integrations can reference, which supports consistent downstream storage and analytics. Integration depth is strongest when third-party systems need chat events such as new conversation creation, assignment changes, or message updates. The automation surface covers common support workflows like proactive handoffs, SLA-related behaviors, and agent assignment logic.
A tradeoff appears when organizations require deep custom schema changes for conversation metadata beyond the provided fields and tags. Teams that standardize on custom data require careful mapping between Freshchat fields and their own ticketing or CRM schema. A common fit is a support operation that routes chat chats by intent and account attributes and then syncs conversation transcripts into an internal case system through API integrations.
- +Conversation, visitor, and message objects enable consistent automation and integration mapping
- +Rules-based automation supports routing, assignment, and follow-up workflows
- +API and webhooks support event-driven sync to CRM, ticketing, and analytics
- +Admin controls include RBAC and activity visibility for operational governance
- –Conversation metadata customizations can be limited to available fields and tags
- –Complex workflow requirements may demand extra integration logic outside Freshchat
Best for: Fits when support teams need chat automation plus governed integrations across multiple systems.
Intercom
messaging platformEnables agent inbox live chat and messaging with customer profiles, bots, and workflow automation for support teams.
Automation and API-driven conversation lifecycle actions tied to a unified contact and event model.
Intercom’s integration depth is centered on its conversation and contact data model, which unifies chat transcripts with customer profiles and events. Live chat sessions can be routed based on attributes and business rules, and agents can use workflow automations to trigger follow-ups from chat outcomes. Extensibility relies on a documented API that supports conversation actions, event ingestion, and integration-driven enrichment of the underlying data model.
A tradeoff is that complex configuration and automation rules can require careful schema mapping and event design to avoid inconsistent state across tools. Intercom fits teams that need chat throughput with tight control over routing logic and downstream actions like ticket creation, CRM sync, or customer messaging triggered from chat events.
- +Conversation and contact data model supports consistent context across chat and workflows
- +API supports conversation actions and event-driven automation for integration breadth
- +RBAC and audit logging support governance over configuration and agent activity
- +Workflow automation can trigger downstream messaging and routing based on chat state
- –Automation rules depend on clean event and attribute mapping to prevent state drift
- –Advanced routing and workflow setups require careful configuration discipline
Best for: Fits when mid-size teams need governed chat workflows and extensibility via a documented API.
LiveChat
chat-focused SaaSOffers real-time website chat with agent tools, triggers, and reporting designed for customer support operations.
Workflow automation with routing and trigger rules tied to conversation and agent states.
LiveChat is a live chat room product with a structured agent workflow and deep third-party integration options. The data model centers on conversations, tickets, tags, and customer profiles, with search and export paths tied to those entities.
Automation can be applied through triggers and rules that route, assign, and respond based on conversation state. An API and app surface support extensibility for event handling, custom provisioning patterns, and integration depth across CRM and support systems.
- +Event-driven API supports conversation and message lifecycle integrations
- +Conversation routing rules reduce manual agent assignment
- +Tagging and transcript exports support audit and reporting workflows
- +Extensive app ecosystem improves integration breadth across support stacks
- –RBAC granularity can lag advanced governance needs
- –Automation rules can be harder to test without sandbox tooling
- –Throughput behavior needs validation during peak chat spikes
- –Some integrations rely on indirect mapping between custom fields
Best for: Fits when mid-size teams need rule-based routing plus API-backed integrations and reporting.
Crisp
developer-friendly chatProvides live chat with web widget, automation, and shared inbox capabilities for support and customer success teams.
Webhooks for real-time conversation and contact events.
Crisp provides a live chat inbox that routes visitor conversations by workspace, team, and channel configuration. It supports message automation through triggers, routing rules, and bot-style flows that act on conversation events and user attributes.
The integration surface includes documented APIs for conversation, contacts, and events, plus webhooks for automating downstream systems. Crisp also adds governance controls such as RBAC, team-based access, and audit logging for administrative actions.
- +Event-driven automation that triggers on conversation and contact changes
- +Webhooks and APIs cover conversations, contacts, and event streams
- +RBAC with workspace and team scoping for agent access boundaries
- +Audit log records admin actions for governance workflows
- –Automation logic becomes complex when combining many triggers
- –Higher control requires careful schema mapping for contact attributes
- –Throughput tuning depends on external queueing patterns
- –Administration overhead increases with multi-channel routing rules
Best for: Fits when mid-market teams need API-driven chat workflows and governed agent access.
Tawk.to
self-serve chatDelivers a website live chat widget with agent dashboard, visitor tracking, and basic engagement workflows.
Event web hooks for chat status and transcript events with third-party app triggers.
Tawk.to fits teams that need live chat with a controllable integration surface for routing, CRM syncing, and internal reporting. Its data model centers on chats, visitors, agents, and transcripts, with configuration for tags, departments, and canned replies to standardize interactions.
The automation surface is primarily exposed through its app integrations and web hooks, which lets external systems react to chat events and update conversation context. Admin tooling supports role-based access for agents and basic governance controls around inbox management and visibility.
- +Web chat widget supports script-based deployment across multiple properties
- +Event integrations enable external systems to react to chat lifecycle
- +Agent assignment can use routing logic via departments and tags
- +Transcript availability supports audit-friendly customer communication records
- –Admin governance is limited beyond inbox configuration and agent roles
- –Automation relies on external stitching rather than first-party workflow builder
- –Advanced data schema controls for chat metadata are not granular
- –Throughput tuning requires careful configuration rather than policy controls
Best for: Fits when support teams need chat integration and basic governance across shared inboxes.
Olark
legacy SaaSProvides website live chat with reporting and agent management features for customer service teams.
Routing rules that assign chats using visitor and conversation attributes.
Olark centers live chat operations around visitor context and configurable routing rules instead of app-style chat embeds. Its integration depth focuses on CRM and helpdesk sync, plus webhooks for event-driven automation.
The data model supports conversations, contact attributes, and assignment history to enable workflow governance. Admin configuration supports team visibility controls and chat transcript access for operational review.
- +Webhooks support event-driven automation around chat lifecycle
- +Conversation data model includes contact attributes and assignment context
- +CRM and helpdesk integrations reduce manual copy-paste workflows
- +Routing rules map visitors to agents without custom code
- –Limited documented API surface for custom data entities
- –Automation depends on webhook events, not a full workflow engine
- –Admin controls offer fewer granular RBAC layers than enterprise suites
- –Throughput tooling is lighter than high-volume enterprise chat stacks
Best for: Fits when teams need configurable routing and event automation without building custom chat infrastructure.
Comm100 Live Chat
contact center add-onSupports multi-channel live chat with ticket handoff, agent management, and customer engagement tools.
Event-driven Live Chat API that supports automation based on conversation lifecycle states.
Comm100 Live Chat is built around configurable chat experiences tied to customer identity flows. It supports integration paths for CRM and support systems, plus an API surface for automation and message handling.
The data model centers on conversations, contacts, transcripts, and agent assignment, which helps governance and reporting. Admin controls include role-based access and audit-style operational visibility for chat actions.
- +API for conversation events, message handling, and automation hooks
- +Clear conversation data model spanning transcripts, routing, and participants
- +Admin RBAC controls for agent access boundaries
- +Extensibility through integration points with support and CRM systems
- –Automation depends on defined event coverage for the desired workflow
- –Complex routing rules can require careful configuration management
- –More admin setup effort than single-vendor widget-only deployments
- –Sandboxing for API changes is not always obvious from docs
Best for: Fits when support teams need conversation governance plus API-driven automation across systems.
Zoho SalesIQ
CRM-integrated chatSupplies website live chat and visitor analytics with routing and CRM integration for sales and support workflows.
CRM-linked visitor matching with event-triggered workflows for routed and tracked live conversations.
Zoho SalesIQ routes website visitor events into live chat sessions with rule-based triggers tied to Zoho identity. It uses a structured visitor and chat data model that connects to Zoho CRM records and supports agent context, handoff, and conversation tagging.
Automation is handled through configuration and Zoho workflow integrations, with an API surface for session, contact, and event operations. Administration emphasizes RBAC across Zoho accounts plus audit-oriented visibility through Zoho’s governance controls.
- +Zoho CRM association maps chats to leads, contacts, and deals.
- +Rule-based routing assigns chats by visitor attributes and page context.
- +Zoho workflow integrations enable multi-step actions on conversation events.
- +API access supports automation on contacts, sessions, and events.
- –Extensibility depends on Zoho ecosystem objects and schemas.
- –Granular chat-level permissions require careful RBAC setup.
- –Advanced analytics exports need extra configuration for reporting workflows.
- –Live chat room performance tuning is limited to platform-level controls.
Best for: Fits when teams need Zoho-integrated live chat automation with governed access and event-driven workflows.
Service Cloud Voice and Chat in Salesforce
CRM-native serviceCombines agent chat and customer service workflows with Salesforce CRM context and service routing capabilities.
Omni-Channel routes chat and voice with the same case context schema.
Service Cloud Voice and Chat in Salesforce fits service orgs that already run cases, routing, and identity in Salesforce and need voice plus chat in one data model. The interaction data ties into the Case and Omni-Channel schema, which keeps channel context consistent for agents and admins.
Automation and extensibility rely on Salesforce APIs, including Events and webhooks-style patterns via Lightning and platform events, plus Apex and integration points for routing and post-interaction actions. Admin control centers on RBAC, session and security policies, and audit log coverage for configuration changes and user access.
- +Voice and chat interactions map into Salesforce Case and Omni-Channel data
- +Routing and service context reuse Omni-Channel configuration for both channels
- +Extensibility via Apex, APIs, and platform events supports workflow automation
- +RBAC and audit log coverage support governance for admin and agent changes
- –Real-time chat controls depend on Salesforce service and agent UI configuration
- –Throughput and latency characteristics depend on org setup and integration design
- –Advanced telephony features often require careful Omni-Channel and CTI configuration
- –Cross-system state consistency needs custom orchestration when external systems own data
Best for: Fits when Salesforce-first service teams need channel-scoped routing and auditable automation without leaving the CRM.
How to Choose the Right Live Chat Room Software
This buyer's guide covers Zendesk Chat, Freshchat, Intercom, LiveChat, Crisp, Tawk.to, Olark, Comm100 Live Chat, Zoho SalesIQ, and Service Cloud Voice and Chat in Salesforce for teams choosing a live chat room product.
The guide focuses on integration depth, the conversation and contact data model, automation and API surface, and admin and governance controls across those tools.
The goal is to map tool capabilities to operational requirements like chat-to-ticket continuity, event-driven automation, and RBAC with audit visibility.
Live chat room platforms that connect visitor messaging to data, routing, and automation
Live chat room software provides a real-time web or in-app chat experience plus an agent workspace for handling visitor conversations, routing, and transcripts.
The category solves problems around turning chat events into structured records and repeatable actions, so chat context can drive ticket handoff, routing, and downstream system updates. Zendesk Chat and Service Cloud Voice and Chat in Salesforce show what this looks like when chat interactions map into a structured support data model used for routing and workflow actions.
Evaluation criteria built around integration, schema, automation, and governance
Choosing a live chat room tool is mostly an integration and control decision because chat events must land in a usable data model and trigger the right actions.
Integration depth, automation and API surface, and admin governance controls determine whether routing, assignment, and handoff remain consistent as conversation volume increases.
Conversation and contact data model for consistent automation inputs
Look for tools that expose conversation, visitor, and contact objects that remain consistent across chat, routing, and workflow actions. Freshchat and Intercom both describe structured conversation and contact models that support event-driven automation without losing context.
Chat-to-ticket or case-context handoff that preserves conversation history
If chat must become a ticket or case, the platform should preserve conversation context in the shared system of record. Zendesk Chat focuses on chat-to-ticket handoff that keeps conversation context in Zendesk’s shared data model, and Service Cloud Voice and Chat in Salesforce ties interactions to Case and Omni-Channel schemas.
Event-driven automation surface plus documented API and webhooks
The safest automation path is one that triggers from conversation lifecycle and emits events through API or webhooks. Crisp provides webhooks for real-time conversation and contact events, Comm100 Live Chat provides an event-driven Live Chat API for automation based on conversation lifecycle states, and Tawk.to uses event webhooks for chat status and transcript events.
Routing and assignment rules tied to conversation and agent state
Routing rules should use chat attributes and conversation state so agents receive the right work with minimal manual triage. LiveChat emphasizes workflow automation with triggers and rules tied to conversation and agent states, and Freshchat highlights rules-based routing and assignment driven by conversation events.
Admin controls with RBAC scoping and audit visibility for configuration changes
Governance matters when multiple teams configure chat routing, triggers, and agent access. Zendesk Chat and Intercom both call out RBAC and audit logging for configuration and conversation changes, and Crisp includes RBAC with workspace and team scoping plus audit log records for admin actions.
Extensibility through app ecosystems and event ingestion patterns
Integration breadth increases when the vendor supports an apps ecosystem or extensibility patterns that ingest events into external systems. Zendesk Chat describes an API and apps ecosystem for event ingestion and visitor or conversation enrichment, while LiveChat points to an extensive app ecosystem and API-backed integrations.
Select a live chat room tool by mapping chat events to your system of record and controls
Start with the operational end state for chat, then work backward to automation triggers, data schema mapping, and governance controls.
The right tool is the one that keeps chat context consistent from the widget or session into routing, assignment, and ticket or case workflows without losing auditability.
Define the system of record target for chat outcomes
If chat must become a Zendesk ticket with preserved conversation context, Zendesk Chat matches that requirement with chat-to-ticket handoff in the shared Zendesk data model. If the service org already runs cases and Omni-Channel routing in Salesforce, Service Cloud Voice and Chat in Salesforce maps chat into Case and Omni-Channel context.
Plan the automation contract using API and event streams
For external workflows that need reliable inputs, prioritize tools that expose event-driven APIs and webhooks like Crisp, Comm100 Live Chat, and Tawk.to. Crisp’s webhooks cover conversation and contact events, while Comm100 Live Chat provides an API intended for automation based on conversation lifecycle states.
Validate routing rule inputs against your available attributes
Routing rules should align with the attributes that exist in the tool’s data model, including visitor and conversation metadata used for assignment. Freshchat excels with automation rules that trigger on conversation events and drive routing and assignments, and Olark focuses on routing rules that assign chats using visitor and conversation attributes.
Check governance needs for RBAC and audit logs on admin actions
For teams with multiple admins and configuration owners, require RBAC plus audit log coverage for configuration and conversation changes. Zendesk Chat and Intercom both mention RBAC and audit logging, and Crisp adds audit log records for administrative actions with workspace and team scoping.
Assess extensibility and integration depth relative to your stack
If multiple support and CRM systems must stay synchronized with chat context, choose tools that offer deep integration breadth through API and apps. Zendesk Chat’s API and apps ecosystem supports provisioning and automation patterns, and LiveChat’s event-driven API and app ecosystem support integrations with CRM and support stacks.
Which teams should choose each live chat room tool
Different teams need different integration end states and governance models, so each tool maps to a distinct operational pattern.
The best-fit selection follows the tool’s best-for fit for chat-to-ticket continuity, governed automation, event webhook delivery, or CRM-specific orchestration.
Support teams that need chat-to-ticket continuity inside Zendesk
Zendesk Chat fits when chat sessions must hand off into Zendesk tickets while preserving conversation context in Zendesk’s shared data model. This tool also pairs that handoff with RBAC and audit log availability for configuration and agent workflow governance.
Teams that need routed and governed chat automation across multiple systems
Freshchat is a fit when conversation events must drive routing, assignment, and follow-up through automation rules plus a documented API and webhooks. Freshchat also includes RBAC and activity visibility that supports operational governance.
Mid-size support orgs that need an agent inbox with lifecycle automation and API extensibility
Intercom fits when teams want governed chat workflows tied to a unified contact and event model with audit logging. Intercom’s automation and API-driven conversation lifecycle actions support integration breadth from chat state.
Mid-size teams that want trigger-based routing tied to conversation and agent state
LiveChat fits when routing and trigger rules must connect to conversation and agent states while still supporting API-backed integrations and reporting. Crisp also targets a similar automation goal but emphasizes webhooks for real-time conversation and contact events with RBAC scoping.
Sales and support teams that already run Salesforce cases and Omni-Channel routing
Service Cloud Voice and Chat in Salesforce fits when voice and chat must reuse Omni-Channel configuration and map into the same Case context. The tool also emphasizes RBAC, session and security policies, and audit log coverage for admin and agent changes.
Practical pitfalls when implementing live chat room automation and governance
Most implementation problems come from mismatched schemas, incomplete event coverage, or governance gaps that show up during configuration changes.
The pitfalls below map to concrete limitations called out across the reviewed tools.
Designing routing automation without validating attribute and event mapping
Intercom’s automation rules depend on clean event and attribute mapping to prevent state drift, so routing logic should be tested against the actual conversation attributes produced by the platform. Freshchat can also require extra integration logic when workflow requirements exceed available metadata fields and tags.
Assuming charting and workflow tests are easy without a sandbox path
LiveChat’s automation rules can be harder to test without sandbox tooling, so teams should plan workflow validation using a controlled configuration workflow. Comm100 Live Chat flags that sandboxing for API changes is not always obvious from docs, so governance for change testing should be part of implementation planning.
Building chat metadata governance around capabilities that are not granular enough
Tawk.to provides limited admin governance beyond inbox configuration and agent roles, so it can be a poor fit for teams that require granular RBAC and policy-level control over chat metadata. Olark also offers fewer granular RBAC layers than enterprise suites, so advanced governance should be confirmed against required RBAC scopes.
Expecting first-party workflow engines for all automation instead of event wiring
Tawk.to and Olark rely on app integrations and webhook events for automation rather than a full workflow builder, so workflow complexity may require external stitching and queueing logic. Crisp and Comm100 Live Chat provide webhook or API surfaces intended for automation, so integration design work should be treated as part of the system.
Not validating throughput behavior during peak chat spikes
LiveChat calls out that throughput behavior needs validation during peak chat spikes, so load expectations should be tested against real routing rules and integrations. Zoho SalesIQ also notes that live chat room performance tuning is limited to platform-level controls, so performance planning should include integration overhead.
How We Selected and Ranked These Tools
We evaluated Zendesk Chat, Freshchat, Intercom, LiveChat, Crisp, Tawk.to, Olark, Comm100 Live Chat, Zoho SalesIQ, and Service Cloud Voice and Chat in Salesforce using a criteria-based scoring approach across features, ease of use, and value. Each tool’s overall rating is a weighted average in which features carry the most weight, then ease of use and value each account for the remaining share of the score. The editorial criteria centered on how well each product’s conversation and contact data model supports integration, automation, and governed workflows via RBAC and audit logging where those controls are explicitly described.
Zendesk Chat separated from lower-ranked options because it preserves conversation context through chat-to-ticket handoff inside the shared Zendesk data model. That capability boosted the features score through end-to-end continuity and it also improved governance confidence because Zendesk Chat pairs the handoff with RBAC and audit log availability for configuration and agent workflow changes.
Frequently Asked Questions About Live Chat Room Software
Which live chat platforms provide the deepest API access to chat events and conversation data?
How do Zendesk Chat and Intercom handle chat-to-ticket handoff without losing context?
What admin governance features are available for role-based access and audit visibility?
Which tools support extensibility through event webhooks for downstream automation?
How do routing and assignment rules differ across LiveChat, Crisp, and Olark?
What approach to data modeling makes Salesforce-first integrations easier with Service Cloud Voice and Chat?
When chat history export or search is required, which products emphasize entity-level reporting?
How do Freshchat and Comm100 Live Chat support conversation governance and lifecycle automation?
What data migration steps are typically required when moving chat history and identities between systems?
Which platform best fits teams that need Zoho identity matching with CRM-linked chat sessions?
Conclusion
After evaluating 10 customer experience in industry, Zendesk Chat 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.
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→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.