When to use inbound demos
Inbound demos fit product, solution, and campaign pages where visitors need to see a workflow to understand its value. They also give buyers a way to explore outside your team’s working hours.Follow the buyer’s question
A visitor evaluating a fictional project-management tool might want to understand how several teams coordinate a launch. Hobbes can explain the relevant capabilities and guide them through the available product experience. If the buyer asks about reporting, the conversation can move toward that interest. What Hobbes can show depends on the product experience your team provides.Support the next conversation
Hobbes can offer a relevant next step, such as booking a meeting. Your team can review the buyer’s questions and priorities to prepare for follow-up. Conversation insights also help your team identify recurring questions about your product. Use conversation intelligence to inspect the questions behind a sales handoff. A sales leave-behind gives a buyer a way to keep exploring after a meeting. Verify the resulting next step using bookings and handoffs.Before you begin
- Prepare an approved Hobbes agent and a product experience that covers the questions your visitors ask.
- Make sure your website editor can change the CTA and publish the site.
- Agree on the next step your team will offer and where session activity should go.
- Review your website’s privacy notice and consent requirements before loading Hobbes.
Replace a Book a demo form
Use this workflow when your website CTA should open a product conversation rather than a demo-request form. Keep a separate meeting option for visitors who prefer to speak with sales.- Choose the page and button to update. Use a label that accurately describes the experience, such as Explore the product, rather than promising that a click books a meeting.
- Open Settings, then Deploy, and select Agent. Choose Your own button to open Hobbes from an existing button, or Both if your site should also show the Chat launcher.
- Follow the generated instructions for your organization. Your website editor should connect the intended button and publish the website. Keep the organization-specific snippet in your own website setup.
- Keep a clear route to your sales team for visitors who prefer a person. Configure and test the agent’s intended next step using the signed-in Playbook guide.
Test before removing the form
Use a published test page or an approved limited rollout. In a private browser window, check each step below on desktop and phone.
If a check fails, keep the existing form or restore its destination while your team resolves the issue.
Start with the public troubleshooting hub. It covers a missing launcher, missing CRM activity, and missing Slack alerts.
Review after launch
Review visitor questions and the quality of follow-up, not only clicks. Use a comparable date range and separate your team’s test sessions when evaluating results. Coach the agent on unanswered questions and retest the affected workflow before sharing the update. The funnel metrics guide explains how to compare activity consistently. Accounts and buyer journeys helps you review available history for a returning buyer or related company. For CRM follow-up, use the connection guide for HubSpot, Salesforce, Attio, or Pipedrive. Verify delivery with a test session before expanding the rollout.Summary
Inbound demos help interested visitors explore your product through conversation. If you replace a demo-request form, verify the website, agent, next step, and CRM delivery together, and retain a clear path to a person.Related docs
- Choose a demonstration format. Demo experiences
- Prepare and check the website installation. Install Hobbes
- Choose a CRM or notification destination. Integration capabilities
- Test representative questions before sharing. Preview your agent
- Continue the experience after a meeting. Outbound and sales follow-up