When to use Hobbes for expansion
Use Hobbes when a customer wants to solve another problem, introduce the product to another team, or start using a capability they have not adopted.Example expansion session
A customer uses a fictional project-management product to track tasks and asks how to report across several teams. Hobbes can navigate to the relevant product area, explain the reporting options, and help the customer build the view they need. An action that changes the account can require confirmation, while restricted actions remain outside the agent’s scope. The same conversation can happen in a separate live environment when the customer wants to evaluate the workflow before using it in their own account.Connect interest to adoption
A live-browser session lets customers move from asking about a capability to seeing and using it. Your team can review the questions that come up and use that context in the next account conversation. Availability in a particular customer’s account still depends on their product access and plan. Your team defines the relevant commercial guidance and action rules.Control actions
Choose which actions Hobbes can execute directly, which need permission, and which are restricted. Apply rules that fit an evaluation environment or the customer’s own account. Detailed configuration belongs in the Customer Hub.Summary
Hobbes can help customers understand and adopt additional capabilities through the live product. Your team controls the environment, available content, and permitted actions.Related docs
- Learn about live-browser guidance and action controls. Product concepts
- Help people get started with a workflow. Customer onboarding
- Support product use after adoption. Support
- Connect engagement to your team. Integration capabilities
- Prepare the account, action boundaries, and success checks for a customer workflow. Prepare a customer workflow