Verify a live installation and avoid duplicate embeds
Prove that the correct Agent is installed once and remains usable across the real storefront Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Prove that the correct Agent is installed once and remains usable across the real storefront This guide keeps the work focused on live Agent installation 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: Read access to deployment settings and permission to inspect the storefront are required. Fixing the embed needs website or Shopify access.
- Use the production URL and intended market.
- Know the expected Agent identity and entry point.
- Prepare one Knowledge, one product, and one support test.
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
Start in a private browser session and inspect several page types after full load and consent choices.
- 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
Confirm there is one launcher or configured entry point, then open and close it through navigation without creating another instance.
- 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
Compare the live Agent, domain, language, market, and catalog response with the selected Humind configuration.
- 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
Run the three prepared scenarios, capture failures precisely, and trace any duplicate installation to theme code, app blocks, tag managers, or page templates.
- 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 live Agent installation separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- One and only one intended entry point is visible.
- Opening, closing, and navigation preserve a usable conversation.
- Knowledge and product answers come from the correct company and market.
- Escalation reaches the expected Inbox workflow.
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
The experience changes after navigation
Check whether the storefront performs full navigation or client-side navigation and whether the embed is inserted repeatedly. Keep initialization in the supported global integration point.
The wrong Agent answers
Compare the deployment selected in Humind with the installed configuration and allowed domain. Remove copied identifiers from another environment and retest in a fresh session.