Before you begin
Have a Hobbes organization, an administrator responsible for the agent, and access to the website or CMS where it will appear. Choose the initial pages and audience. Review your privacy notice and consent manager with the person responsible for your website. For a website launch, coordinate the site owner and Hobbes administrator. Each may control a different part of the setup.Prepare the installation
- Choose the experience. Choose a website entry point or an available demo link. Use a launcher on your website or share a link to the intended experience. Confirm any inline-embed option with your administrator.
- Decide how visitors open it. In Settings → Deploy → Agent, the website installation options include Chat launcher, Your own button, and Both. Choose the entry point that fits the page rather than adding competing calls to action.
- Coordinate technical setup. Ask your website owner and Hobbes administrator to follow the complete installation guide in the Customer Hub, including its Webflow, Framer, or WordPress walkthrough where relevant. Keep installation snippets, workspace-specific configuration, and integration details in that private workflow.
- Check readiness. Confirm that the intended agent is ready for visitors. Website placements must use an active, published agent before they can be enabled. Have the administrator follow the preview checklist and publishing guide in the Customer Hub.
- Test the actual destination. Open the intended website page or shared link as a visitor. Check the entry point, mobile layout, privacy link, conversation start, and intended next step.
Success check
You’re done when the intended entry point opens the correct experience on the correct pages, a visitor can complete a realistic conversation, and the next step works. Check the published website, not only its CMS preview.Limits
Website builders, consent tools, and security settings can affect whether an experience loads. If the entry point fails, have the site owner inspect those controls using the private installation guide. Avoid installing duplicate copies while troubleshooting. Start with the public missing launcher checks to compare the intended entry point with the published page. The troubleshooting hub covers related CRM and notification symptoms.Summary
Choose how visitors will open Hobbes and confirm who can update the website. Complete the detailed installation in the Customer Hub and test the published visitor experience.Related docs
- Plan the path from preparation to launch. Implementation guide
- Review data collection, storage, and consent. Privacy and cookies
- Roll out a product conversation from your website CTA. Replace a demo form
- Choose where conversation activity goes. Integration capabilities