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

# Non-Call Sources

> Processing and analyzing text-based data sources in BuildBetter

## Text Data Sources

BuildBetter processes various text sources:

* Support tickets
* Survey responses
* Chat transcripts
* Email communications
* Customer feedback forms

## Data Import

<CardGroup cols={2}>
  <Card title="Direct Upload" icon="upload">
    CSV and text file import
  </Card>

  <Card title="Integration Sync" icon="rotate">
    Connected system import
  </Card>
</CardGroup>

## Supported Formats

### File Types

* **CSV files**: Primary import format for text feedback
* **Text documents**: Via CSV with text content column
* **JSON data**: Via API/GraphQL imports

### Data Structure

* Structured data
* Semi-structured
* Free-form text
* Mixed content
* Metadata fields

## Processing Steps

<Steps>
  <Step title="Data Import" stepNumber={1}>
    Load text content
  </Step>

  <Step title="Format Check" stepNumber={2}>
    Validate structure
  </Step>

  <Step title="Analysis" stepNumber={3}>
    Extract insights
  </Step>

  <Step title="Integration" stepNumber={4}>
    Combine with other data
  </Step>
</Steps>

## Integration Options

<AccordionGroup>
  <Accordion title="Help Desk">
    **Currently Available**:

    * Zendesk
    * Intercom
    * Kustomer

    **Alpha (Request Early Access)**:

    * Freshdesk
    * Front
    * Others - contact [support@buildbetter.app](mailto:support@buildbetter.app)
  </Accordion>

  <Accordion title="Survey & Forms">
    **Currently Available**:

    * Typeform (Alpha)
    * Pendo
    * CSV upload (any survey data)

    **Alpha (Request Early Access)**:

    * SurveyMonkey
    * Google Forms
    * Others - contact [support@buildbetter.app](mailto:support@buildbetter.app)
  </Accordion>
</AccordionGroup>

## Signal Extraction

### Text Analysis

* Topic detection
* Sentiment analysis
* Intent recognition
* Entity extraction

### Signal Types

* Feature requests
* Bug reports
* Feedback items
* Support needs

<Warning>
  Ensure text data is properly formatted and cleaned before processing.
</Warning>

## Data Quality

<CardGroup cols={2}>
  <Card title="Validation" icon="check-double">
    Data quality checks
  </Card>

  <Card title="Cleaning" icon="broom">
    Text preprocessing
  </Card>
</CardGroup>

## Processing Features

### Text Processing

* Language detection
* Text normalization
* Keyword extraction
* Pattern matching

### Enhancement

* Data enrichment
* Context addition
* Metadata tagging
* Cross-referencing

<Note>
  Text processing quality affects signal extraction accuracy.
</Note>

## Best Practices

### Data Preparation

* Clean formatting
* Complete fields
* Consistent structure
* Valid content

### Processing Setup

* Source configuration
* Field mapping
* Rule definition
* Quality checks

<Tip>
  Regular data quality checks improve signal extraction results.
</Tip>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Import Issues">
    * Format errors
    * Missing data
    * Structure problems
    * Encoding issues
  </Accordion>

  <Accordion title="Processing Problems">
    * Analysis errors
    * Quality issues
    * Integration failures
    * Performance problems
  </Accordion>
</AccordionGroup>

## Performance Optimization

### Processing

* Batch operations
* Resource allocation
* Queue management
* Cache usage

### Integration

* Sync scheduling
* Error handling
* Retry logic
* Load balancing

## Privacy & Security

### Data Protection

* Access control
* Data encryption
* Privacy rules
* Retention policies

### Compliance

* GDPR rules
* HIPAA standards
* Data handling
* Audit trails

<Info>
  Regular monitoring ensures efficient text data processing and analysis.
</Info>