> ## 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.

# Understand Hobbes conversation intelligence

> Use summaries, questions, objections, transcripts, and replay to understand what buyers need.

Last reviewed 2026-11-10

Hobbes conversation intelligence helps your team understand what people asked, which product workflows interested them, and what should happen next. A summary gives you a starting point. The transcript and available replay help you check the details.

## When to review a conversation

Use conversation intelligence to prepare a sales follow-up, investigate an unanswered question, or understand how an agent explained your product. Your team needs access to the relevant organization and its conversations.

A fictional reporting-software team notices a buyer asking about sharing dashboards. Before following up, the rep checks whether the buyer wanted a public link, a scheduled report, or access for a colleague. Those needs may call for different answers.

## What the conversation can tell you

| Evidence | How to use it |
| - | - |
| Summary | Find the main topics and proposed next step. |
| Questions and objections | Understand the buyer's needs and unresolved concerns. |
| Qualification and intent | Separate fit with your criteria from interest in buying. |
| Transcript | Check the words behind a summary or assessment. |
| Available replay and moments | Follow the product context around a question. |

## Turn the evidence into a next step

1. Identify the conversation and read its summary.
2. Check the transcript or replay around the question that matters.
3. Choose a relevant follow-up, such as answering a question or involving a product specialist.
4. If the same knowledge gap appears repeatedly, have the agent owner review the supporting material and test the answer again.

A newly completed conversation may need time to finish analysis. A missing assessment does not establish that the buyer lacked interest. Keep a generated summary separate from facts the buyer confirmed.

## Summary

Start with the summary, then verify important details against the conversation. Use that evidence to make follow-up more specific and identify product questions your team should address.

## Related docs

* Understand the people and companies behind conversations. [Accounts and buyer journeys](https://docs.hihobbes.com/guides/accounts-buyer-journeys.md)
* Interpret aggregate results. [Funnel metrics](https://docs.hihobbes.com/guides/funnel-metrics.md)
* Turn a conversation into a team follow-up. [Sales handoffs](https://docs.hihobbes.com/guides/sales-handoffs.md)
* Sign in for the detailed review workflow. [Review a Hobbes conversation](https://docs.hihobbes.com/customer-hub/watch-hobbes-work.md)


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