Use Insights

Insights are are text-based notes that you can input yourself, or allows you to store and retrieve previously saved AI interactions, making it easy to reuse knowledge from past conversations. This is useful for ensuring consistency in responses and retaining key learnings across teams.

These saved insights act as a personal knowledge base, helping users retain important AI-generated information, streamline workflows, and maintain consistency across multiple interactions. Unlike databases, Insights are stored in full context without chunking, preserving the original message structure for improved retrieval and reuse.

When to Use Insights

• When past AI-generated responses need to be referenced frequently

• When team members share refined prompts or key findings from Data Rooms

• When specific contextual knowledge should be stored for quick access

Sample Use Cases

In Depth Example Use Case of Insights

A customer support team uses Blockbrain to handle common technical troubleshooting requests. Team members frequently ask the AI bot for solutions to repeating customer issues, but responses can vary slightly depending on how the query is phrased.

Insights can improve the workflow of that situation through the following:

1. A support specialist asks the AI for a troubleshooting guide on a common issue and refines the response for accuracy.

2. Once the response is validated, they save it as an Insight so the team can reuse the response instead of regenerating it each time.

3. Now, when another team member encounters the same issue, they can retrieve the saved Insight instantly instead of waiting for a new AI-generated response.

4. Over time, the support team builds a library of verified troubleshooting steps, ensuring consistent and accurate AI-generated answers across the entire team.

Other Use Case of Insights

• Research & Development Knowledge Base: A research team compiles summaries of scientific papers, experimental findings, and competitor analyses into Insights. This allows them to quickly retrieve and reference past knowledge instead of duplicating research efforts.

• Content Marketing & Copywriting: A content marketing team stores brand tone guidelines, product descriptions, and frequently used marketing messages in Insights. Writers can quickly pull pre-approved messaging to maintain brand consistency across multiple campaigns.

  • Create brand tone and guidelines, then save them as an Insight for easy reference when generating future marketing campaign content.

• HR & Employee Training: An HR department uses Insights to store company policies, onboarding procedures, and answers to frequently asked employee questions. This ensures HR representatives provide accurate and consistent responses without searching for documents every time.

Ways to Create an Insight

There are multiple ways to create an insight:

1. Save AI Chat as Insight: Click on the 3-dot icon in the AI chat, select "Save message as an insight," using the AI-generated message as a note;

   • Save message as an insight

2. Manually Add Insight: Navigate to the Insights Tab, click "Add Insights" to type in your own insight, creating a text-based note in your own words.

   • Insights in the Navigation to the Left

   • Adding an Insight

Save message as an Insight

Managing Insights

Accessing Insights

You can access all insights created across all Knowledgebots and Data Rooms in the Knowledge Management Tab under the Insights section.

Searching Insights

Navigate to the Knowledge Management Tab and click the Insights Tab. There are two methods to search for insights:

1. Keyword Search → Use specific keywords to find relevant insights.

2. Insights AI Search → A powerful search tool that allows users to find specific insights based on context, not just keywords, enhancing retrieval efficiency by allowing users to set the number of search results to display.

This feature helps users quickly locate relevant information without manually browsing the Insights Page, which contains all insights created or shared with them.

Best Practices

To maximize the effectiveness of Insights, follow these best practices to ensure consistency, accuracy, and ease of access for your team.

1. Store Only High-Quality, Validated Information

   • Save accurate and well-structured content that has been reviewed or refined.

   • Avoid storing duplicate, outdated, or incorrect responses to maintain reliability.

   • Regularly audit and update Insights to ensure information remains current.

2. Store Only Clear and Focused Threads

   • Save well structured threads that focus on a desired topic

   • Avoid overly complicated threads that may confuse the AI when referenced in the future

3. Use Clear, Consistent, and Descriptive Titles

   • Include relevant keywords in the title to make searching faster and more intuitive.

   • Use consistent naming conventions across teams to improve organization.

   • Example: Instead of "Client Pitch", use "Sales Team: Sales Email Email - Follow up for Company X".

4. Keep Responses Concise and Actionable

   • Store only the necessary details instead of long, unstructured content.

   • Summarize key points clearly to make Insights quick to read and apply.

   • If context is needed, add links to supporting documents instead of storing long explanations.

5. Leverage Insights for Consistency Across Teams

   • Standardize customer support answers, sales scripts, company policies, and technical instructions.

   • Ensure that AI-generated responses align with company-approved messaging.

   • Regularly train team members on how to use Insights to maintain uniformity.

6. Regularly Review and Clean Up Insights

   • Schedule routine audits to remove outdated or redundant information.

   • Ensure Insights remain relevant and useful for evolving business needs.

   • Encourage team feedback on stored Insights to improve quality.

FAQs

• Why should I use Insights?

  • Insights help you quickly save, organize, and retrieve useful AI responses without losing context. They are great for personal reference, collaboration, and sharing specific messages with others.

• How are Insights different from Databases?

  • Unlike databases, which store large volumes of structured data that undergo chunking, Insights are stored in full context, preserving the original message format.

• How should I name my Insights?

  • Use consistent and descriptive titles that include relevant keywords for easy searching. Clear titles help you quickly locate Insights when needed.