> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hihobbes.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hobbes product concepts

> Understand Hobbes product concepts with a glossary of Agent Role, Playbook, Session, Hobbes Link, and related terms.

Last reviewed 2026-11-09

Hobbes combines an AI product agent, a live product experience, and knowledge about your business. It helps people ask questions, understand workflows, and complete tasks within the action rules your team sets.

Acme’s fictional marketing team shares a Hobbes Link with a buyer who asks about reporting. The team distinguishes the agent’s purpose and guidance from that buyer’s individual conversation and resulting evidence.

## When to use this guide

Use these definitions when evaluating Hobbes or planning the buyer experience you want to offer.

## Glossary

| Term | What it means |
| - | - |
| Product agent | The agent that answers questions, guides people through the product, and takes permitted actions. |
| Agent Role | A configured agent for a particular audience and purpose, with its own behavior and access to approved content. This is different from a teammate's workspace permission role. |
| Playbook | The guidance that shapes how an agent approaches a conversation, including its goals, flow, next steps, and guardrails. |
| Session | One interaction with Hobbes, which your team can review for conversation content and engagement. |
| Agent-Led Demo | A conversation that combines buyer questions with a product demonstration. |
| Product experience | The live product, Replica, or recording available for the demonstration. |
| Knowledge | Product and business information your team provides to support answers. |
| Hobbes Link (Custom Link) | A shareable, personalized entry point to a demo experience. |
| Source | Material your team provides to support agent knowledge. |
| Fact | A specific piece of company or product information your team can review with its evidence. |
| Qualification | Whether the available evidence meets your target-customer criteria. |
| Buying intent | Purchasing interest expressed in a conversation. It differs from qualification. |
| Campaign | A group of personalized demo destinations and their engagement. |
| Locale | A language or regional language choice for an experience. |
| Conversation insights | Buyer questions, priorities, objections, and engagement your team can review. |

## How the pieces work together

A buyer evaluating a fictional reporting tool might ask how a manager investigates a change in sales. Hobbes can explain the capability, show the available product experience, and answer the buyer's next question.

Knowledge supports the explanation. The Agent Role sets the intended purpose, and its Playbook guides the conversation. The product experience gives the conversation something concrete to show. The resulting conversation helps your team understand what the buyer wants to learn.

## Live-browser guidance and actions

Hobbes can guide people and perform actions during the same live-browser session. Your team chooses whether the experience runs in a person's own live account or a separate live environment.

| Action boundary | How Hobbes behaves |
| - | - |
| Allowed directly | Executes the action within the rules your team sets. |
| Permission required | Asks the person before taking the action. |
| Restricted | Leaves the action to the person or your team. |

For example, a team might allow navigation, require permission before creating a project, and restrict deleting data. This is an illustrative policy. Your team defines the actual rules for its product and audience.

## Apply the same concepts across use cases

The audience and learning goal shape the experience. New customers can learn a first workflow during [onboarding](https://docs.hihobbes.com/guides/customer-onboarding.md). Existing customers can explore another product area for [expansion](https://docs.hihobbes.com/guides/customer-expansion.md). Teammates can prepare for customer conversations through [enablement](https://docs.hihobbes.com/guides/team-enablement.md), and users can revisit product explanations for [support](https://docs.hihobbes.com/guides/customer-support.md).

## Qualification and buying intent

Qualification answers whether the visitor fits your intended customer profile. Intent answers how much purchasing interest the conversation shows. A qualified visitor can still be researching, while an interested visitor can fall outside your target audience.

Your team defines the fit evidence and reviews the resulting rationale with the conversation. A booking, a company match, and a high-intent label do not mean the same thing. Sign in for [status definitions and assessment evidence](https://docs.hihobbes.com/guides/data-model.md) and the [qualification diagnostic](https://docs.hihobbes.com/customer-hub/troubleshoot-qualification.md).

## Knowledge and improvement

Sources provide supporting material. Facts capture information your team reviews and maintains. The Playbook guides how the agent uses that information during a conversation.

Review conversation evidence to distinguish a factual gap from a behavior change. Customers use Knowledge and Inbox to review sources, facts, and outstanding gaps, then test the affected question again. See the signed-in [sources and facts guide](https://docs.hihobbes.com/customer-hub/company-context.md) and [answer diagnostic](https://docs.hihobbes.com/customer-hub/troubleshoot-answers.md).

## Scope the experience

The available product experience and information determine what Hobbes can explain and demonstrate. Your team should choose material that fits the intended audience and confirm that the experience covers the workflows buyers need.

Customers can sign in to the Customer Hub for detailed setup and operating instructions.

## Summary

The agent guides the conversation, knowledge supports its answers, and the product experience shows the workflow. Conversation insights help your team follow up with context.

## Related docs

* Start with the product overview. [What is Hobbes?](https://docs.hihobbes.com/index.md)
* Understand the demonstration formats. [Demo experiences](https://docs.hihobbes.com/guides/demo-experiences.md)
* Explore how teams share demos. [Outbound and sales follow-up](https://docs.hihobbes.com/guides/outbound-follow-up.md)
* Review the scope of a buyer experience. [Product access and data](https://docs.hihobbes.com/guides/product-access.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.