The Library is your central knowledge repository in Bigmind. It's where you organize and manage all the information your AI agents need to provide intelligent, context-aware assistance. A well-maintained library is key to building effective agents that can reference your products, methodologies, and success stories.
#What is the Library?
The Library is a structured collection of knowledge that your AI agents can access and reference during conversations. Think of it as the "memory" you give to your agents - containing everything from product specifications to sales playbooks to customer success stories.
Key benefits:
- Consistent messaging: Agents always reference the same, approved information
- Up-to-date knowledge: Update once in the library, all agents get the new information
- Organized context: Structure information so agents can find what they need
- Scalable intelligence: Build knowledge once, use it across all agents
#Library Components
The Library consists of several types of content, each serving a specific purpose:
Products
Products are your offerings - software, services, or anything else you sell. Organizing products in the library helps agents understand what you offer and recommend the right solutions.
Product information includes:
- Name and description: What the product is and what it does
- Features and benefits: Key capabilities and value propositions
- Pricing: Cost structures and packaging options
- Use cases: Who the product is for and when to recommend it
- Technical details: Specifications, integrations, requirements
- Competitive positioning: How it compares to alternatives
Product Families:
Products can be organized into families for easier management. A product family groups related products together - for example, "Enterprise Suite" might include "Core Platform", "Advanced Analytics", and "Premium Support".
How agents use products:
- Recommend relevant products based on customer needs
- Provide accurate pricing and feature information
- Suggest product bundles or cross-sell opportunities
- Answer technical questions about capabilities
- Compare products to help with selection
ICPs (Ideal Customer Profiles)
ICPs define your perfect customers - the organizations and individuals most likely to benefit from your products and successfully implement them. ICPs help agents qualify leads and tailor messaging.
ICP attributes include:
- Company characteristics: Size, revenue, industry, geography
- Roles and titles: Decision-makers and influencers to target
- Technology stack: Current solutions they're using
- Pain points: Problems they're experiencing that you solve
- Decision-making process: How they evaluate and buy solutions
- Authority, Need, Priority: Qualification criteria (BANT-style)
How agents use ICPs:
- Qualify leads by matching against ICP criteria
- Tailor messaging to specific customer segments
- Identify which products are best suited for which ICPs
- Recognize expansion opportunities in existing accounts
- Prioritize prospects based on ICP fit
Case Studies
Case studies are customer success stories that demonstrate real-world value. They're powerful tools for building credibility and overcoming objections.
Case study elements include:
- Customer information: Name, industry, size
- Situation: Where the customer started
- Challenge: The specific problem they faced
- Solution: How your product addressed the challenge
- Results: Quantifiable outcomes and benefits
- Metrics: Specific numbers (ROI, time savings, revenue increase, etc.)
- Quote: Customer testimonial
- Assets: Logo, video, PDF versions
How agents use case studies:
- Reference similar customer success during sales conversations
- Provide proof points to overcome objections
- Match prospects with relevant case studies based on industry or use case
- Include case study links in follow-up emails
- Build credibility with specific, measurable results
Playbooks
Playbooks codify your GTM motions and processes. They guide agents (and sales reps) stage-by-stage through proven approaches to winning deals.
Read the full Playbooks guide →
Playbook components include:
- Name and description: What the playbook is for
- Objective: The goal of following this playbook
- Target ICPs: Which customer segments this playbook applies to
- Target products: Which products this playbook focuses on
- Stages: Sequential steps in the sales process
- Checklists: Action items to complete at each stage
- Framework associations: Sales frameworks to apply (MEDDIC, BANT, etc.)
- Expected timeline: Typical sales cycle length
- Budget ranges: Deal size expectations
Playbook stages:
Each playbook consists of stages that represent the sales process:
- Stage name: E.g., "Discovery", "Qualification", "Proposal"
- Description: What happens in this stage
- Exit criteria: What needs to be true to move to the next stage
- Checklists: Specific tasks to complete
How agents use playbooks:
- Suggest next steps based on current deal stage
- Remind reps of critical action items
- Ensure consistent execution of sales methodology
- Guide reps through complex sales processes
- Provide coaching based on proven approaches
For a deeper explanation (and how playbooks differ from scorecards and frameworks), see Playbooks and Concepts.
Documents
Documents are flexible knowledge items that can contain any type of information you want agents to reference. They're perfect for content that doesn't fit into other categories.
Document use cases:
- Competitive battle cards
- Product comparison sheets
- Industry-specific information
- Objection handling guides
- Technical documentation
- Process documentation
- FAQs and talking points
- Regulatory or compliance information
Document features:
- Rich text: Format with headings, lists, tables
- Organization: Group documents in folders
- Versioning: Track changes over time
- Search: Find documents quickly by name or content
How agents use documents:
- Look up specific information on-demand
- Reference battle cards during competitive situations
- Provide answers to complex questions
- Access specialized knowledge for specific scenarios
Templates
Templates are reusable document structures that your AI agents can fill in automatically. They define the layout, headings, and — with AI Instructions — exactly what content the AI should generate in each section and where to get the data.
Read the full Templates guide →
Common template use cases:
- Account plans
- Handover documents
- ROI cases
- Meeting summaries
- Proposals and executive summaries
How agents use templates:
- Generate complete documents using a predefined structure
- Fill in sections automatically based on AI Instructions and research
- Ensure consistent formatting across the team
- Combine data from tools (CRM, meeting notes) with the template structure
#Managing Library Content
You manage library content in Settings → Library, where you'll find dedicated sections for each content type.
Creating Content
- Navigate to the appropriate section (Products, ICPs, etc.)
- Click "Create" or the "+" button
- Fill in the details for your content
- Set status to "Active" when ready for agents to use
- Save to add to the library
Organizing Content
- Use product families to group related products
- Tag content for easier discovery
- Create folders for documents
- Maintain active/inactive status to control what agents can access
Updating Content
Library content should be kept current:
- Review regularly for accuracy
- Update when products, pricing, or processes change
- Add new case studies as they become available
- Refine playbooks based on what's working
- Archive outdated content rather than deleting it
#Adding Library Content to Agents
To make library content available to an agent:
- Open the agent configuration in Settings → AI → Agents
- Navigate to the Knowledge tab
- Click "Add Knowledge"
- Select the category (Products, ICPs, Case Studies, Playbooks, Documents)
- Choose specific items to add
- Save the agent configuration
The agent will now have access to that knowledge during conversations.
Strategic Knowledge Selection
You don't have to add everything to every agent:
- Account agents: Might need all products, key case studies, expansion playbooks
- Deal agents: Might need specific products for that deal, relevant playbooks, qualification ICPs
- SDR agents: Might need qualifying ICPs, top case studies, prospecting playbooks
- Customer Success agents: Might need implementation playbooks, support documents, upsell products
Targeted knowledge keeps agents focused and responses relevant.
#How Agents Access Library Content
When you add library content to an agent's knowledge, it becomes part of the agent's context. The agent can:
- Reference directly: Pull specific information from the library
- Use for reasoning: Make decisions based on library content
- Cite sources: Point users to specific case studies or documents
- Apply methodologies: Follow playbook guidance
Library content is provided to the agent's AI model as part of its system instructions, so it's always "aware" of this information.
#Library vs Tools
It's important to understand the difference between library content (knowledge) and tools (actions):
| Library Content (Knowledge) | Tools (Actions) |
|---|---|
| Static information the agent can reference | Functions the agent can execute |
| Product specs, case studies, playbooks | Fetch CRM data, send emails, research companies |
| Part of agent's "memory" | Part of agent's "capabilities" |
| Added via Knowledge tab | Added via Tools tab |
Agents need both - knowledge to inform their responses and tools to take action.
#Best Practices
Content Quality
- Be specific: Detailed information helps agents provide better answers
- Stay current: Outdated information leads to incorrect responses
- Be consistent: Use consistent terminology across all content
- Include examples: Real examples help agents understand context
Organization
- Use clear naming: Make it easy to find content later
- Tag appropriately: Tags help with discovery and filtering
- Create logical hierarchies: Group related content together
- Maintain status: Mark inactive content so agents don't reference it
Maintenance
- Review quarterly: Check all content for accuracy
- Update promptly: When things change, update the library immediately
- Add progressively: Start with core content, add more over time
- Get feedback: Ask sales reps what knowledge would be helpful
#Common Patterns
Product-ICP-Case Study Connection
Link these together for powerful targeting:
- Define ICPs for each product
- Associate case studies with relevant ICPs
- Create playbooks for specific product-ICP combinations
This allows agents to recommend the right product, reference relevant case studies, and follow appropriate playbooks based on who they're talking to.
Playbook-Based Selling
Build playbooks for different sales motions:
- New logo acquisition: Full sales cycle from prospecting to close
- Expansion: Upselling and cross-selling to existing customers
- Renewal: Retaining customers and preventing churn
- Partner-led: Working through channel partners
Agents can guide reps through the right playbook based on the deal type.
#Troubleshooting
Agent not referencing library content:
- Verify the content is added to the agent in the Knowledge tab
- Check that the content status is "Active"
- Ensure your question is relevant to the content you've added
- Try being more specific in your request (e.g., "Based on our case studies...")
Agent providing outdated information:
- Update the library content with current information
- Agents don't automatically refresh - start a new chat after updating content
- Verify you updated the correct product/case study/etc.
Too much content overwhelming agents:
- Be selective about what knowledge you add to each agent
- Use specific agents for specific purposes rather than one agent with everything
- Consider breaking up very large documents into smaller, focused pieces
#Related Documentation
- Agent Concepts - Understanding AI agents in Bigmind
- Tools - Learn about agent tools