Skip to main content
Last reviewed 2026-11-09 Hobbes is an AI product agent that answers questions, guides people through your live product, and takes actions within the rules your team sets. These answers cover the product experience and common evaluation questions. Acme’s fictional buyer wants to understand product access, language choices, and what happens after a demo. The buyer uses these answers to assess fit and follows the linked guide when more detail is needed.

Who is Hobbes for?

Hobbes serves B2B teams across growth, sales, customer success, enablement, and support. It helps buyers evaluate the product, customers learn and complete workflows, and teammates build product knowledge.

Can Hobbes help after the sale?

Yes. Hobbes can guide customers and take permitted actions in the live product during onboarding, help existing customers adopt additional workflows for expansion, and help people complete product tasks for support.

Can our own team use it for training?

Yes. Teammates can explore the live product, ask questions, and learn through guided or permitted actions while preparing for customer conversations. See team enablement.

What happens during an Agent-Led Demo?

A buyer asks questions and explores relevant parts of the product with Hobbes. The conversation can cover a use case, explain a capability, or demonstrate a workflow. What Hobbes can show depends on the product experience your team provides.

Does every buyer follow the same path?

Hobbes can respond to the buyer’s questions and interests. A buyer interested in reporting can ask about reporting, while another buyer explores a different available workflow.

Can Hobbes demonstrate our live product?

Yes. Hobbes supports demonstrations through a browser in your live product. It also supports Replicas and recorded demos. Your team chooses the available product experience.

Can Hobbes take actions?

Yes. It can guide the person and take actions within your team’s rules. You choose which actions run directly, which need the person’s permission, and which are restricted.

Does it use a live customer account or a separate environment?

Both are supported. Your team chooses the environment that fits the use case and applies the appropriate action rules.

How does Hobbes learn about our product?

Hobbes uses product and business information your team provides to support explanations and answers. Product experiences give the conversation something concrete to show.

Can buyers explore outside our working hours?

Yes. Buyers can explore and ask questions when your team is offline, then continue the evaluation with a rep.

What happens after a demo?

Hobbes can offer a relevant next step, such as booking a meeting. Your team can review buyer questions, priorities, objections, and engagement to prepare for follow-up. Use conversation intelligence to inspect the evidence, sales handoffs to prepare the next action, and a sales leave-behind when the buyer wants to keep exploring.

How do we understand engagement across conversations?

Use funnel metrics to interpret aggregate activity and accounts and buyer journeys to review available history for a person or company. A link open, a conversation, and a completed booking measure different outcomes.

Which tools does Hobbes connect with?

Hobbes supports HubSpot, Salesforce, Attio, and Pipedrive CRM connections, along with Slack notifications. APIs, webhooks, and supported AI client connections cover other workflows. For connection prerequisites and a live delivery check, use the public guides for HubSpot, Salesforce, Attio, or Pipedrive.

Does Hobbes support multiple languages?

Yes. Hobbes supports most major languages and regional dialects across language and voice experiences. Choose the intended language and voice for your audience. Translated product content has separate readiness and publication checks.

How does our team receive demo alerts?

Teammates currently receive alerts through Slack. Choose the conversation events and destination for the team that will act on them, then verify delivery. Customers can follow the signed-in Slack notification guide. Visitor follow-up recaps are separate from teammate alerts.

Where should we start when something does not work?

The public troubleshooting guide covers first checks for missing CRM activity, a missing website launcher, and missing Slack alerts. Detailed connection and configuration checks remain in the Customer Hub.

Where are setup instructions?

Customers can sign in to the Customer Hub for setup and operating guides. The API reference remains public for teams reviewing the integration contract.

How can we evaluate fit?

Review your intended workflows, audience, and integration needs with the Hobbes team. Use the official Privacy Policy, Terms of Use, and Trust Center to review data-handling and security information.

How do we get started?

Follow the implementation guide to prepare, coach, launch, and review the experience. The public installation guide explains entry options and launch checks.

Can Hobbes replace our demo-request form?

You can offer a product conversation from a website CTA. Use the demo-form replacement guide for rollout and verification, and retain a route to your team for visitors who want a person.

Can we block competitor access?

Hobbes provides domain and email restrictions for demo entry. Access restrictions differ from how an agent handles a question about a competitor. Customers can review the signed-in demo access guide and test both allowed and blocked entry.

How do we improve an incorrect answer?

Review the conversation, supporting facts, and source evidence. Correct information in Knowledge, review outstanding Inbox decisions, and test a new conversation. Change the Playbook when the behavior needs coaching. See Knowledge and improvement.

Does saving a draft update the live agent?

Saving and publishing are separate steps. Customers should review publication checks and verify a new conversation at the actual visitor destination. See the signed-in publication guide.

How long does launch take?

Launch readiness depends on the product experience, approved information, access, website installation, and destination checks. We do not promise a universal launch time. Use the implementation checklist to confirm those prerequisites.

Does a meeting click mean a booking?

No. Verify the completed booking in the scheduling destination. Human-support and purchase handoffs also need their own completion checks. See bookings and next-step handoffs for the distinction, then sign in for the detailed booking and handoff guide.

Summary

Hobbes combines buyer questions with a product demonstration. Confirm the experience, connections, and service scope for your team before rollout. Sign in to follow the operating guide. Configure Hobbes languages and voice