What Business Understanding Shows

Business Understanding is the place to review what FAQ Ally understood as structured business knowledge. It includes structured records, business entities, glossary terms, and identity matches that may need review. Use it when you want to confirm that trained files and snippets produced usable facts before relying on answers.

Open Knowledge → Business Understanding from the Knowledge hub. The summary card shows structured records, business entities, glossary terms, and items that need review.

How to Use the Area

1 Start with Overview

The Overview tab summarizes records, entities, and review status. If nothing needs review, the page confirms that there are no unresolved identity matches right now.

2 Open Records

Use Records to browse structured records extracted from sources. These records help FAQ Ally answer questions about numbers, vendors, policies, assets, operations, and other structured details when the source content supports them.

3 Review Entities

Use Entities to inspect business names and concepts FAQ Ally detected. Examples include vendors, people, departments, systems, products, and other named items found in trained content.

4 Resolve Review Items

Use Review when the badge shows items waiting. Review helps resolve likely matches, ambiguous names, and conflicting identifiers so the same business entity is not treated as several separate items.

How to Read Empty or Low Counts

  • No structured records yet means FAQ Ally has not found supported record-like facts in the trained knowledge available to the current company or agent scope.
  • No business entities yet usually means more training content is needed, or the content does not contain clear named business concepts.
  • No glossary terms yet means FAQ Ally has not found clear term definitions or expansions in trained sources.
  • No entity review needed means there are no unresolved identity matches right now. Check again after new training runs.

Best Practices

  • Train clear source documents first. Records and entities are only as useful as the source content they come from.
  • Review identity matches after training. This keeps duplicate vendor names, department names, and acronyms from confusing later answers.
  • Use glossary terms to explain language. When terms are missing, add clearer definitions to your files or Knowledge Snippets and retrain.
  • Do not treat extraction as approval. Review important records before teams use them for operational decisions.

Related Guides

For source preparation, see Document Best Practices. For short curated notes, see Knowledge Snippets. For connected records and documents, see Knowledge Graph.