A widget is not a support program
Define hours, queues, routing, escalation, response targets, knowledge, coverage, handoff, offline behavior, and quality review before launch.
Real-time customer support widget
LiveChat for CMS Max Websites
Put a staffed support channel beside the content, products, forms, and checkout moments where customers need help.
The CMS Max LiveChat plugin stores and injects the merchant-provided LiveChat embed code. LiveChat manages the widget and agent experience; the merchant owns staffing, routing, availability, privacy, transcript policy, placement, and service outcomes.
- Embed-code setup
- Sitewide widget
- Provider customization
- Mobile spacing
- Operational ownership
with CMS Max
01Install code
02Configure experience
03Staff + improve
Conversion architecture
A connection earns its place when customers and operators can trust it.
Define the business outcome, data boundary, customer expectation, operating owner, failure path, and measurement plan before installing the technology.
Protect the page experience
Test mobile sticky controls, accessibility tools, cookie choices, forms, cart, checkout, account views, keyboard access, performance, and visual overlap.
Own the data boundary
Document what LiveChat collects, who can access conversations, retention, exports, deletion, subprocessors, consent, security, and incident response.
Current CMS Max capabilities
What the implemented workflow supports.
Availability depends on the plugin or approved embed being active, required provider accounts, current provider features, accurate configuration, consent, source data, plan limits, and tenant setup.
Merchant-provided embed code
Copy the current website widget code from LiveChat and store it in the CMS Max plugin setting for frontend injection.
Website chat entry point
The installed provider script can render the LiveChat customer widget on eligible CMS Max pages so visitors can start a provider-hosted conversation.
Provider-managed widget experience
Configure appearance, position, spacing, visibility, mobile behavior, language, availability, forms, engagement, and other supported options in LiveChat.
Supported JavaScript widget actions
The current LiveChat widget API can support actions such as maximize, minimize, hide, show, and event handling when separately configured and tested.
Support near conversion moments
Place live assistance near product questions, forms, pricing, shipping, returns, and checkout while avoiding obstruction, dark patterns, or collection of sensitive payment data.
Agent workflow remains in LiveChat
LiveChat owns the provider-side inbox and agent tooling. CMS Max connects the widget to the website but does not staff, route, retain, or report conversations itself.
Customer-to-operation flow
Make the handoffs visible from intent to outcome.
Every stage needs clear inputs, an observable result, an exception path, and a named owner.
Discover
Identify the questions and pages that need live help.
Install
Add the current merchant widget code in CMS Max.
Configure
Set appearance, mobile behavior, privacy, and availability.
Staff
Route conversations and own escalation and coverage.
Improve
Review quality, conversion, accessibility, and performance.
Implementation sequence
Move from account access to production confidence.
Use representative content, users, devices, permissions, failures, and provider states before relying on the workflow.
01. Design the service model
Document audiences, use cases, hours, staffing, routing, languages, response targets, escalation, offline capture, prohibited data, and quality review.
02. Prepare LiveChat
Confirm the license owner, authorized users, teams, security, privacy settings, retention, integrations, widget configuration, and billing.
03. Install the current code
Copy the website code from LiveChat, paste it into the CMS Max plugin setting, save, and verify that no obsolete or duplicate snippet remains.
04. Fit the website interface
Configure position and bottom spacing around mobile sticky actions, accessibility controls, cookie tools, and other floating elements.
05. Test every state
Test online, offline, queued, mobile, keyboard, screen zoom, consent choices, route changes, cart, checkout, forms, blocked scripts, and slow networks.
06. Operate and measure
Review response time, abandonment, resolution, escalations, transcript quality, conversion influence, customer feedback, script errors, and page performance.
Operational ownership
Know which system and team controls each outcome.
Clear ownership makes privacy, security, support, changes, billing, measurement, and incident recovery faster.
- CMS Max
- Stores the configured embed code and provides the website context in which the third-party widget is rendered.
- LiveChat
- Owns the widget platform, provider-side configuration, conversation infrastructure, agent tools, account access, and supported APIs.
- Merchant
- Owns staffing, availability, disclosures, consent, retention choices, conversation quality, escalation, security, billing, and customer outcomes.
- Website team
- Owns safe snippet deployment, responsive placement, accessibility, consent behavior, performance, regression testing, and rollback.
Documentation and related resources
Confirm the current provider requirements.
Provider interfaces, plans, policies, APIs, scripts, and supported features can change. Use official documentation and the live account during implementation.
Integration FAQ
Resolve the practical questions before launch.
Turn each answer into configured rules, representative tests, monitoring, and written ownership.
What does the CMS Max LiveChat plugin do?
It stores the merchant-provided LiveChat embed code so the provider widget can be injected into the CMS Max frontend. LiveChat remains the conversation and agent platform.
Where do I customize the chat widget?
Manage supported appearance, position, spacing, visibility, mobile behavior, language, availability, forms, engagement, and security settings in the LiveChat account.
Can CMS Max keep the LiveChat widget maximized?
LiveChat provides widget JavaScript actions such as maximize. Any forced state should be separately configured and tested for consent, mobile usability, accessibility, interruption, and conversion impact.
How do I prevent overlap with mobile buttons?
Configure side and bottom spacing in LiveChat, then test the actual website with sticky actions, accessibility controls, cookie banners, support tools, keyboards, safe areas, and zoom.
Does CMS Max store LiveChat transcripts?
The current plugin is a settings-only embed integration and does not implement a CMS Max transcript model. Review provider storage, retention, access, export, and deletion behavior in LiveChat.
Will adding chat automatically increase conversions?
No. Outcomes depend on traffic, placement, page quality, staffing, response time, relevance, agent knowledge, customer trust, privacy, accessibility, performance, and measurement design.
Connect with purpose
Build a customer workflow the business can operate after launch.
Bring the use case, account, data, consent requirements, owners, content, test plan, failure handling, and success measures. CMS Max will help map the supported path.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.