Install Humind on an HTML website
Install the Humind Agent once on a general website and validate the real customer experience Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Install the Humind Agent once on a general website and validate the real customer experience This guide keeps the work focused on HTML website deployment and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
Deployment connects a configured Agent to a customer-facing sales channel. The installation method depends on the storefront, but every launch needs an allowed domain, a single valid embed, a visible entry point, and tests on the real site. Workspace testing remains useful, yet it cannot replace validation in the deployed environment.
Before you begin
Access: Agent deployment access and permission to edit the website template or tag manager are required.
- Complete Agent testing before installation.
- Confirm the production hostname is allowed.
- Know where global scripts are loaded on every intended page.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Open Sales channels for the selected Agent and use the HTML installation instructions supplied by Humind.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Place the provided embed in the shared website layout so it loads once, and avoid rewriting identifiers or copying code from another company.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
Deploy the website change through its normal release process, then use Humind verification when available.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Open the production domain in a private session, test the launcher, Knowledge, catalog, and support path, and repeat on a narrow mobile viewport.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in HTML website deployment separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The embed loads once on every intended page.
- The correct Agent and company experience opens.
- The production hostname is accepted.
- Desktop, mobile, navigation, and human support smoke tests pass.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
Humind is not detected
Inspect the deployed page rather than the source template alone. Check content-security rules, script blocking, consent timing, allowed domains, and whether the production release contains the embed.
The launcher appears twice
Search theme, tag manager, app integration, and page-specific templates for another installation. Keep one authoritative embed and remove the duplicate through the owning system.