Launch your Agent on a website
Install the tested Agent through the current HTML or Shopify flow, verify detection, and complete a live smoke test.
Launch is the point where a tested Humind configuration becomes visible to shoppers. The current Sales channels page supports a general HTML installation and a Shopify-guided flow when Shopify is connected. Other website platforms shown as disabled, plus messaging, email, and phone channels, must not be treated as available launch paths.
This guide covers the pre-launch gate, both available installation flows, embed verification, and a reversible live check. It does not require exposing private credentials or internal service endpoints.
How this fits into Humind
AI Agent is the configuration space for the customer-facing assistant. Knowledge and Catalog provide facts; Guidance shapes response behavior; Tools add actions; Escalation defines human support; Test surfaces let you review the result before deployment.
Changes can affect many conversations, so test representative buying and support scenarios after each meaningful update. A visually correct chat is not enough: verify the answer, product context, available action, and handoff behavior together.
Before you start
Access: You need Agent configuration access and permission to modify the target website or Shopify theme. Coordinate with the storefront owner when you do not control deployment.
- Complete Knowledge, Catalog, Guidance, Tools, Escalation, and interface review.
- Pass representative scenarios in Playground and any required batch or product tests.
- Confirm the target storefront domain is correct and allowed for the company.
Step-by-step workflow
Open the supported launch flow
Open AI Agent, then Sales channels and stay on the Website tab. Choose HTML for a general website. Choose Shopify only when the company has a connected Shopify shop domain; the Shopify option is disabled otherwise.
Magento, PrestaShop, WooCommerce, Instagram, WhatsApp, email, and phone are not active launch choices in the current interface. Do not improvise an installation path from their visible logos.
Install on a general HTML website
The HTML flow displays the current Humind loader and widget markup for the company's primary domain and provides a copy action. Add the supplied code through the site's normal deployment process rather than rewriting it from memory.
After the change is live, return to the modal and use the verification action. A positive detection result confirms that Humind can see the installation, but you still need to test the shopper experience.
- Keep the copied attributes unchanged.
- Deploy through a reviewable website change.
- Avoid placing duplicate widget elements on the same page.
Install on Shopify
The Shopify flow opens the current theme editor so you can activate the Humind app embed. It then offers the product-page block flow for product questions. Follow the in-product sequence and save the Shopify theme after each change.
Use the verification action in Humind before moving to the next step. If Shopify asks you to reconnect, complete the authorization for the same shop and market, then reopen Sales channels.
Run the live smoke test
Open the storefront in a private browser window. Check a standard page and a product page on desktop and mobile. Confirm the launcher, home screen, one Knowledge answer, one product answer, and the configured human-support path.
Open Inbox and Analytics after the test to confirm the operational surfaces behave as expected. Use a clearly recognizable test question so teammates can distinguish the smoke test from a real shopper conversation.
Permissions and important caveats
- A successful embed-detection check is necessary but does not prove that content, product data, tools, or escalation are correct.
- Use the current code shown by Humind; copied snippets from older documentation may point to obsolete assets or attributes.
- The Shopify flow applies to the connected shop and theme context. Confirm both before saving.
- Only publish a storefront change through the store's approved release process and keep a rollback path.
Verify the result
Use this checklist before considering the work complete:
- Humind reports that the embed is detected.
- The launcher is visible and usable on desktop and mobile without duplicate instances.
- Knowledge, product, and escalation smoke tests produce the expected result.
- The team knows how to disable or roll back the storefront installation if necessary.
Troubleshooting
The Shopify option is disabled
Confirm Shopify is connected for the active company and that its shop domain appears in settings. Reconnect if Humind indicates that authorization is outdated.
Embed verification says not detected
Confirm the website change or Shopify theme is actually published, the code is present only once, and the tested domain matches the company. Then retry verification after the storefront update is live.
The launcher appears but answers are wrong
Treat installation and Agent quality as separate checks. Return to Knowledge, Catalog, Guidance, Tools, or Escalation based on the failing scenario, then retest in Playground before another live smoke test.