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

# Automatic Signal Extraction

> How BuildBetter automatically identifies and extracts signals from your conversations and data

BuildBetter automatically analyzes your calls, conversations, and imported data to extract key insights called Signals. These insights help you understand customer needs, track issues, and identify patterns without manual tagging.

## What are Signals?

Signals are automatically extracted insights from your data including:

* Customer feedback and feature requests
* Bug reports and technical issues
* Product complaints and pain points
* Success stories and wins
* Competitive mentions
* Action items and decisions
* Questions and objections

## Signal Sources

Signals are automatically extracted from:

<CardGroup cols={2}>
  <Card title="Call Recordings" icon="phone">
    Live conversations, meetings, and sales calls with full transcript analysis
  </Card>

  <Card title="Imported Conversations" icon="message">
    Support tickets (Zendesk, Intercom, Kustomer), chat logs (Slack), and CRM data
  </Card>

  <Card title="Documents & Text" icon="file-lines">
    Uploaded files, meeting notes, and written feedback
  </Card>

  <Card title="External Integrations" icon="cloud">
    CRM systems (Salesforce, HubSpot), surveys (Pendo, Typeform), and more
  </Card>
</CardGroup>

## Automatic Extraction Process

<Steps>
  <Step title="Data Ingestion" stepNumber={1}>
    Content is processed from calls, imports, and integrations
  </Step>

  <Step title="AI Analysis" stepNumber={2}>
    Advanced language models analyze content for meaningful insights
  </Step>

  <Step title="Signal Classification" stepNumber={3}>
    Insights are categorized by type, sentiment, severity, and other properties
  </Step>

  <Step title="Enrichment" stepNumber={4}>
    Signals are enhanced with metadata, context, and entity associations
  </Step>
</Steps>

<Note>
  Extraction happens automatically when calls are processed or data is imported. No manual tagging required.
</Note>

## Signal Types

BuildBetter detects 35+ different signal types across three categories:

### Universal Signals (Internal & External)

Detected in all conversations:

* **Improvement** - Suggestions for enhancements
* **Complaint** - Expressions of dissatisfaction
* **Issue** - Problems or challenges mentioned
* **Inquiry** - Questions or information requests
* **Compliment** - Positive feedback or praise
* **Observation** - Noteworthy comments or insights
* **Testimonial** - Customer success stories
* **Idea** - Creative suggestions or concepts
* **Feedback** - General feedback or opinions
* **Competition** - Mentions of competitors
* **Action Item** - Tasks and next steps

### Internal-Only Signals

Detected in internal conversations (team meetings, planning sessions):

* **Suggestion** - Team improvement ideas
* **Decision** - Key decisions made
* **Feature** - Feature discussions
* **Strategy** - Strategic planning points
* **Change** - Process or product changes
* **Confusion** - Areas of uncertainty
* **Concern** - Worries or risks
* **Challenge** - Obstacles identified
* **Opportunity** - Growth opportunities
* **Achievement** - Milestones reached
* **Milestone** - Project progress markers
* **Update** - Status updates
* **Priority** - Priority discussions
* **Risk** - Risk identification
* **Blockers** - Impediments to progress
* **Customer Insight** - Insights about customers
* **Dependency** - Dependencies identified

### External-Only Signals (Customer-Facing)

Detected in customer conversations:

* **Feature Request** - Explicit feature asks
* **Bug** - Software defects or errors
* **Objection** - Sales or product objections
* **Discovery** - Discovery phase insights
* **Question** - Customer questions
* **Strategic** - Strategic discussions
* **Interest** - Product interest indicators

<Info>
  Signal types can be configured in Settings > Features > AI Labeling to enable/disable specific types for your organization.
</Info>

## Signal Properties

Each extracted signal includes:

### Core Properties

* **Type**: Classification from 35+ signal types
* **Content**: The actual text/quote from the source
* **Summary**: AI-generated concise summary
* **Source**: Original recording, conversation, or import

### Enrichment Properties

* **Sentiment**: Score from -10 (very negative) to +10 (very positive)
* **Severity**: Impact score from -10 to +10
* **Bias**: External signal bias measurement
* **Emotions**: Detected emotions (happiness, frustration, confusion, etc.)
* **Business Impact**: Revenue, adoption, satisfaction, retention, efficiency implications

### Context Properties

* **People**: Associated contacts
* **Companies**: Related organizations
* **Topics**: Detected themes and subjects
* **Timestamp**: Exact moment in source content
* **Personas**: Customer persona associations
* **Tags**: Organizational labels

### Dynamic CRM Properties

Signals inherit metadata from connected systems:

* **Salesforce fields**: Account info, opportunity data, custom fields
* **HubSpot properties**: Contact properties, company data, deal info
* **Custom metadata**: Organization-specific attributes

<Tip>
  Use the properties panel when viewing a signal to see all extracted and enriched data.
</Tip>

## Extraction Configuration

### AI Labeling Settings

Access Settings > Features > AI Labeling to:

* Enable/disable specific signal types
* Configure extraction sensitivity
* Set confidence thresholds
* Customize type definitions for your domain

### Extraction Methods

* **Automatic** (default): AI extracts signals during processing
* **Manual**: Users can create signals directly from transcript selections
* **Custom Signals**: Organization-specific signals can run after standard extraction, with previews, run history, findings, and usage estimates

### Custom Signal Workflow

Use Custom Signals when the standard signal types are not specific enough for your team's operating model.

1. Create or edit a custom signal in AI Labeling settings.
2. Preview the custom signal before enabling it.
3. Review projected usage and credit impact.
4. Enable the custom signal so it runs after standard extraction.
5. Monitor run history and findings.

Active custom signal types appear in Signals v2 filters and signal views alongside the built-in types.

## Signal Quality

### Quality Indicators

* Confidence score for each signal
* Source reliability rating
* Extraction method (automatic vs manual)
* Verification status (if using citation verification feature)

### Improving Accuracy

* Ensure complete, accurate transcripts
* Use proper speaker labeling
* Configure signal types for your industry
* Provide feedback on incorrect extractions

<Warning>
  Signal accuracy depends on transcript quality, speaker identification, and proper source configuration. Review important signals before acting on them.
</Warning>

## Integration with Other Features

### Signals Enable:

* **Document Generation**: Create PRDs, reports from signal collections
* **Datasets**: Organize signals for analysis with custom AI columns
* **Dashboards**: Visualize signal trends and patterns
* **Workflows**: Trigger actions based on signal detection
* **CRM Push**: Send signals to Jira, Linear, Salesforce, HubSpot

## Troubleshooting

<AccordionGroup>
  <Accordion title="Missing Signals">
    * Verify transcript is complete
    * Check speaker labeling accuracy
    * Review signal type configuration
    * Ensure extraction hasn't been disabled for that type
  </Accordion>

  <Accordion title="Incorrect Classification">
    * Review confidence scores
    * Check context and full transcript
    * Verify signal type settings
    * Use manual reclassification if needed
  </Accordion>

  <Accordion title="Duplicate Signals">
    * Signals may appear in multiple related contexts
    * Filter by unique source or timestamp
    * Use deduplication in Saved Search views
  </Accordion>
</AccordionGroup>

<Info>
  Signal extraction runs automatically on all processed content. No manual action required to generate signals from your calls and data.
</Info>