> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Document Generation Examples

> Real-world examples of generating documents from calls and signals

Learn how to transform your recordings and signals into structured documents through practical, step-by-step examples.

## Example 1: Meeting Summary from Single Call

**Scenario**: Generate professional meeting notes from a customer call

<Steps>
  <Step title="Open the Recording" stepNumber={1}>
    Navigate to your Recordings and open the call you want to summarize
  </Step>

  <Step title="Start Document Generation" stepNumber={2}>
    From the call details page:

    * Click the **Generate** button (or ••• menu)
    * Select "Generate Document"
  </Step>

  <Step title="Choose Template" stepNumber={3}>
    Select **Meeting Summary** template
  </Step>

  <Step title="Verify Data Source" stepNumber={4}>
    The call should already be selected as the source
  </Step>

  <Step title="Configure Generation" stepNumber={5}>
    * **Title** (optional): "Acme Corp Q1 Review"
    * **Focus** (optional): "Highlight action items and next steps"
    * **Generation Style**: Focused Analysis (default for single call)
    * **Data Format**: Full Context (uses complete transcript)
    * **Visibility**: Private or Workspace
  </Step>

  <Step title="Generate" stepNumber={6}>
    * Click "Create Document"
    * Wait 30-60 seconds
    * Document opens automatically when ready
  </Step>
</Steps>

<Tip>
  Adding a specific focus like "Emphasize technical requirements" helps the AI generate more targeted content.
</Tip>

## Example 2: PRD from Multiple Customer Calls

**Scenario**: Create a product requirements document from 5 customer interviews about the same feature

<Steps>
  <Step title="Organize Calls in Folder" stepNumber={1}>
    * Create a folder called "API Integration Feedback"
    * Add all 5 related customer calls to the folder
  </Step>

  <Step title="Create Document from Folder" stepNumber={2}>
    * Go to **Documents** section
    * Click "Create Document"
  </Step>

  <Step title="Choose PRD Template" stepNumber={3}>
    Select **Product Requirements Document** template
  </Step>

  <Step title="Add Data Sources" stepNumber={4}>
    In the Data step:

    * Click "Folders" tab
    * Select your "API Integration Feedback" folder
    * All 5 calls are now included
  </Step>

  <Step title="Configure Generation" stepNumber={5}>
    * **Title**: "API Integration Feature Requirements"
    * **Focus**: "Extract technical requirements, integration needs, and user pain points for API development"
    * **Generation Style**: Theme Discovery (for multiple calls)
    * **Data Format**: Full Context
    * **Visibility**: Workspace
  </Step>

  <Step title="Generate and Edit" stepNumber={6}>
    * Click "Create Document"
    * Wait 1-2 minutes for processing
    * Review generated PRD
    * Edit directly in the document editor
    * Use document chat for refinements
  </Step>
</Steps>

<Info>
  Theme Discovery mode is best for multiple calls - it identifies patterns and themes across all conversations.
</Info>

## Example 3: Weekly Feature Request Report

**Scenario**: Create a document summarizing all feature requests from the past week

<Steps>
  <Step title="Filter Signals" stepNumber={1}>
    * Go to **Signals** section
    * Filter: Type = "Feature Request"
    * Filter: Date = "Last 7 days"
    * Filter: Interaction = "External"
  </Step>

  <Step title="Save as Saved Search" stepNumber={2}>
    * Click "Create Saved Search"
    * Name: "Weekly Feature Requests"
  </Step>

  <Step title="Generate Document from Saved Search" stepNumber={3}>
    * Go to **Documents** section
    * Click "Create Document"
    * Choose template (e.g., "Status Update" or custom report template)
  </Step>

  <Step title="Add Saved Search as Source" stepNumber={4}>
    * In Data step, click "Saved Searches" tab
    * Select "Weekly Feature Requests" saved search
  </Step>

  <Step title="Configure" stepNumber={5}>
    * **Title**: "Weekly Feature Request Report - \[Date]"
    * **Focus**: "Group by customer account and prioritize by frequency"
    * **Generation Style**: Theme Discovery
    * **Data Format**: Key Insights (using signals)
    * **Visibility**: Workspace
  </Step>

  <Step title="Generate and Share" stepNumber={6}>
    * Generate document
    * Review and edit as needed
    * Copy to share in Slack/email
    * Or share BuildBetter link with team
  </Step>
</Steps>

## Example 4: Customer Feedback Summary (Multiple Sources)

**Scenario**: Combine calls, support tickets, and survey responses into one comprehensive report

<Steps>
  <Step title="Prepare Sources" stepNumber={1}>
    Create a folder called "Q1 Customer Feedback" containing:

    * Customer calls from the quarter
    * Imported Zendesk conversations
    * Survey responses (if using Typeform/Pendo integration)
  </Step>

  <Step title="Create Document" stepNumber={2}>
    * Go to Documents > Create Document
    * Choose a report or summary template
  </Step>

  <Step title="Add Folder" stepNumber={3}>
    * Select "Q1 Customer Feedback" folder as source
    * All content types automatically included
  </Step>

  <Step title="Configure Generation" stepNumber={4}>
    * **Title**: "Q1 Customer Feedback Report"
    * **Focus**: "Identify top pain points, feature requests, and satisfaction trends. Group findings by theme."
    * **Generation Style**: Theme Discovery (for large dataset)
    * **Data Format**: Key Insights
  </Step>

  <Step title="Generate Multi-Source Report" stepNumber={5}>
    * Generate document
    * AI analyzes across all source types
    * Themes emerge from combined data
  </Step>
</Steps>

<Note>
  Combining multiple data source types (calls + tickets + surveys) provides a more complete view than any single source alone.
</Note>

## Example 5: Using Document Chat for Refinement

**Scenario**: The generated document is good but needs specific additions

<Steps>
  <Step title="Open Generated Document" stepNumber={1}>
    Open your newly created document
  </Step>

  <Step title="Access Document Chat" stepNumber={2}>
    Click the chat icon in the top-right corner
  </Step>

  <Step title="Ask for Additions" stepNumber={3}>
    In the chat, request specific changes:

    * "Add a section about pricing concerns mentioned in the calls"
    * "Extract all timeline requirements mentioned"
    * "What specific API endpoints were discussed?"
  </Step>

  <Step title="Apply AI Suggestions" stepNumber={4}>
    * Review AI's response in chat
    * Copy relevant content
    * Paste into your document
    * Edit to integrate smoothly
  </Step>
</Steps>

<Tip>
  Use document chat to iterate on content instead of regenerating the entire document. It's faster and preserves your manual edits.
</Tip>

## Document Generation Best Practices

<Check>
  **Choose the right template**: Match template to document purpose (PRD for requirements, Meeting Summary for notes)
</Check>

<Check>
  **Use appropriate generation style**: Focused Analysis for 1-10 sources, Theme Discovery for 10+ sources
</Check>

<Check>
  **Provide specific focus**: Detailed instructions produce better targeted content
</Check>

<Check>
  **Start with fewer sources**: Test with 2-3 calls before generating from 50+
</Check>

<Check>
  **Edit after generation**: AI provides a strong starting point - add your expertise
</Check>

## Common Document Types

### Meeting Notes

* **Template**: Meeting Summary
* **Sources**: Single call
* **Format**: Full Context
* **Use**: Quick professional notes after any meeting

### Product Requirements

* **Template**: Product Requirements Document (PRD)
* **Sources**: Multiple customer calls or folder
* **Format**: Full Context or Key Insights
* **Use**: Feature planning and development specs

### Status Reports

* **Template**: Status Update
* **Sources**: Saved Search or Collection
* **Format**: Key Insights
* **Use**: Weekly/monthly progress reports

### User Stories

* **Template**: User Stories
* **Sources**: Research calls or feedback signals
* **Format**: Full Context
* **Use**: Development planning and sprint work

<Warning>
  Always review AI-generated documents before sharing externally. Verify accuracy of technical details and customer quotes.
</Warning>

For detailed documentation on document generation, see:

* [Document Generation](/pages/Documents/document-generation)
* [Editing & Refining](/pages/Documents/editing-and-refining)
* [Purpose & Templates](/pages/Documents/purpose-and-templates)