Skip to main content
Last reviewed 2026-11-06 Bring Hobbes into your product experience through four tasks: invite, coach, launch, and improve. These describe the work your team does, not four required buttons in the app. Acme’s fictional team wants pricing-page visitors to understand its reporting workflow. The team agrees on the audience and intended outcome, reviews a representative conversation, and checks the live experience before launch.

Before you begin

Choose an implementation owner, an administrator, and a teammate who can verify product answers. Agree on the initial audience, the workflows Hobbes should cover, and the next step you want visitors to take. Identify an appropriate product environment and approved source material. Keep account access, credentials, technical integration details, and publishing procedures in the private Customer Hub workflow.

1. Invite Hobbes into the product experience

Decide where Hobbes will meet people and what it should help them do. Select the product workflows, audience, and environment with your implementation team. Set boundaries around what the agent may do and what needs a person’s involvement. Arrange approved product access with your implementation owner using the signed-in product setup guide. This is separate from inviting teammates to your Hobbes organization. For colleagues, use Settings → Members → Invite teammates and choose their access.

2. Coach and test the answers

Provide approved company and product information. Review the facts the agent should use and identify questions it should hand off rather than answer speculatively. Have an administrator test the saved experience with realistic questions and edge cases. The agent preview provides coaching tools. Use the Customer Hub’s source and fact guide and testing checklist for the detailed workflow.

3. Launch to a defined audience

Choose a website entry point or an available demo link. Confirm any inline-embed option with your administrator. Review privacy and consent before exposing it to visitors. Ask your administrator to complete the private review and publishing procedure, and your website owner to complete any site changes. Test the actual visitor entry point. Start with an audience and page set your team can review rather than changing every entry point at once.

4. Improve using conversation evidence

Review real questions, confusing answers, unsupported requests, and failed next steps. Correct the relevant source or guidance, then repeat the affected scenario in a preview. Have the administrator review changes before they reach new visitors.

Success check

You’re ready when the agent handles a normal task and an edge case, the entry point works, and someone owns review after launch.

Limits

Available experiences depend on the product environment and material your team provides. This guide does not grant product access or replace technical setup. Invite, coach, launch, and improve are an ongoing sequence of preparation, testing, and review.

Summary

Agree on the intended audience and workflow before preparing Hobbes. Review the experience, confirm launch readiness, and use observed conversations to guide later improvements. Plan a controlled replacement of an existing programme. Move a demo workflow to Hobbes