> ## 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.
# Intelligent Reports (BETA)
> Automated AI-powered reports that analyze your customer signals and deliver actionable insights to your inbox
Intelligent Reports automatically analyzes your customer conversations and feedback, identifies patterns and anomalies, and delivers executive-ready insights directly to your inbox. Get the highlights that matter—without manual data pulls or dashboard reviews.
## What Are Intelligent Reports?
Intelligent Reports is an AI-powered reporting system that transforms your customer signals into actionable intelligence. It automatically clusters feedback, performs statistical analysis to identify trends and anomalies, and generates narrative insights with supporting evidence.
## Interactive Reports
Builder also supports **Interactive Reports**, a report type designed for live exploration and sharing. Interactive Reports can include interactive views, filtering, publishing, scheduling, and run history.
Use Interactive Reports when you want readers to explore the underlying slices of a report instead of receiving only a static narrative.
Interactive Reports support:
* Filterable views
* Sharing and publishing controls
* Scheduling
* Run history
* Owner-based access protections
AI analyzes signals, identifies patterns, and highlights what's changed since your last report
Real statistical analysis including z-scores for anomaly detection and volume trend calculations
Every insight backed by real customer quotes with attribution for credibility
Daily, weekly, or monthly delivery—or let AI recommend the right frequency based on your data
## What's In a Report?
Each Intelligent Report includes:
### Headline & Executive Summary
A single-sentence headline with the most important takeaway, followed by a 2-3 sentence conversational summary. Perfect for quickly understanding what happened.
### Top Insights
3-5 detailed insights, each containing:
* **Theme**: Category like feature request, bug, objection, or praise
* **Key Insight**: One actionable sentence explaining what's happening
* **Root Cause Analysis**: Why this is happening *now*
* **Business Impact**: Which metric is affected—retention, expansion, engagement, or conversion
* **Affected Customers**: Companies and users experiencing this issue
* **Supporting Metrics**: Signal count, volume change, statistical significance
### What's New
Genuinely novel findings that weren't present in previous reports—the unexpected patterns worth your attention.
### Recommended Actions
Specific, actionable next steps with suggested owners. Not generic advice, but tailored recommendations based on the data.
### Visualizations
Charts showing volume trends, issue clustering, severity distribution, and sentiment over time.
## Report Frequencies
**Best for**: High-volume teams, active launches, critical monitoring periods
Get a pulse check every morning on what happened in the last 24 hours. Requires at least 20 signals per day to generate meaningful insights.
**Example use case**: Product team during a major launch monitoring customer reactions in real-time.
**Best for**: Most teams, balanced insight-to-noise ratio
Comprehensive weekly summary delivered on your chosen day. Requires at least 30 signals per week. Captures patterns that emerge over multiple days.
**Example use case**: Customer Success team reviewing account health and escalations every Monday.
**Best for**: Strategic reviews, executive updates, lower-volume organizations
High-level monthly analysis with trend comparisons to the previous month. Requires at least 50 signals. Best for seeing bigger patterns and seasonal trends.
**Example use case**: Leadership receiving monthly customer intelligence briefings.
**Best for**: Teams unsure about frequency, varying signal volumes
Let AI analyze your data and recommend the optimal frequency. It evaluates signal volume, quality, and actionability to suggest daily, weekly, or monthly delivery.
The system will explain its reasoning—for example: "Weekly recommended: You average 45 signals per week, which provides enough data for meaningful patterns without the noise of daily reports."
## Core Capabilities
### Anomaly Detection
Reports automatically identify statistical anomalies using z-score analysis. When a topic suddenly spikes in volume or severity deviates significantly from the norm, it gets flagged—even if you weren't looking for it.
### Period Comparison
Every metric is compared against the previous period (daily vs. yesterday, weekly vs. last week, monthly vs. last month). You'll always know if something is increasing, decreasing, or stable—and by how much.
### Intelligent Clustering
Signals are automatically grouped into themes using AI clustering. Instead of reviewing hundreds of individual data points, you see the 3-5 most important patterns.
### Quote Selection
Every insight includes a real customer quote, automatically selected for clarity and impact. Quotes are attributed to companies or users when available, providing credibility for sharing with stakeholders.
## Personalization
### Your Role
Tell Reports about your role (Product Manager, Customer Success, Sales, Leadership, etc.) to receive insights framed for your priorities. A PM sees feature request analysis; a CS lead sees account health signals.
### Your Interests
Specify topics you care about most—specific features, customer segments, competitors, or themes. Reports will prioritize these areas when generating insights.
### Delivery Schedule
Choose exactly when reports arrive:
* **Day of week**: For weekly reports, pick which day you want them
* **Day of month**: For monthly reports, choose the date
* **Time of day**: Select your preferred delivery time
## Getting Started
Go to **Reports** in the sidebar to access the Intelligent Reports page.
Set your frequency (or choose Intelligent for AI recommendation), delivery schedule, role, and interests.
Click **Generate Preview** to see what your report will look like with your current data. This helps you understand the format before enabling delivery.
Use **Send Test Email** to receive a sample report in your inbox. Verify it looks good and the timing works for your workflow.
Save your preferences to start receiving scheduled reports. You can adjust settings anytime from the Reports page.
## Common Use Cases by Team
**Weekly reports every Monday**
Start your week knowing:
* Top feature requests and how they're trending
* New pain points that emerged
* Which customer segments are most vocal
* Statistical anomalies in feedback patterns
**Interests to configure**: Feature areas, competitors, user segments
**Weekly reports every Friday**
End your week understanding:
* Accounts showing concerning signals
* Common issues across your book of business
* Positive feedback for renewal conversations
* Emerging problems to address proactively
**Interests to configure**: Account health, escalations, renewals
**Weekly reports every Monday**
Prepare for the week with:
* Common objections and their frequency
* Competitive mentions and win/loss patterns
* Feature requests tied to deals
* Customer success stories for pitches
**Interests to configure**: Competitors, pricing, objections, use cases
**Monthly reports on the 1st**
Monthly strategic intelligence:
* High-level trends across customer conversations
* Sentiment trajectory over time
* Major themes compared to last month
* Actions requiring executive attention
**Interests to configure**: Strategic initiatives, market trends, key accounts
## Report History
All generated reports are saved to your history, allowing you to:
* **Review past reports**: See what insights were delivered previously
* **Track patterns over time**: Compare reports across weeks or months
* **Re-send reports**: Forward a historical report to colleagues
* **Verify delivery**: Confirm reports were generated and sent
Access history from the **History** tab on the Reports page.
## Understanding Report Quality
Reports require sufficient data to generate meaningful insights:
| Frequency | Minimum Signals | Recommended |
| --------- | --------------- | ----------- |
| Daily | 20 | 50+ |
| Weekly | 30 | 100+ |
| Monthly | 50 | 200+ |
If your data volume is below these thresholds, the system will:
1. Suggest a longer reporting period
2. Explain what data is available
3. Still generate a report if you proceed (with a quality warning)
If you're seeing "insufficient data" messages, try a longer frequency or ensure your integrations are actively syncing customer feedback.
## Best Practices
### Start with Weekly
Unless you have very high signal volume, weekly reports offer the best balance of insight and signal-to-noise ratio.
### Configure Your Interests
Taking a minute to specify your interests dramatically improves report relevance. Generic reports are less actionable.
### Share with Your Team
Reports are designed to be shared. Forward them to colleagues or use them to start team discussions about customer intelligence.
### Review History Periodically
Looking at reports over time reveals trends that single reports miss. Monthly pattern reviews surface strategic insights.
### Combine with Chat
When a report highlights an interesting insight, use Chat to dig deeper. Ask follow-up questions about the data behind any finding.
## Integration with BuildBetter
### From Signals to Reports
Reports analyze the same signals you see throughout BuildBetter:
1. Signals are extracted from calls, tickets, feedback, and other sources
2. Reports cluster and analyze these signals statistically
3. AI generates narrative insights with supporting evidence
4. Recommendations tie back to your tracked objects and workflows
### With Knowledge Pages
Use report insights to update your Knowledge pages:
* When reports show recurring themes, document them in Knowledge
* Link insights to relevant Knowledge pages for context
* Build a living library of customer intelligence
### With Tracked Objects
Report findings often connect to tracked items:
* Feature requests mentioned in reports may already be tracked
* New commitments identified can be added to Tracked
* Problem patterns inform tracked issues and their priority
## Manual Reports
In addition to AI-generated Intelligent Reports, BuildBetter also supports manual reports—pre-built HTML reports that a BuildBetter team member can help set up for your workspace.
### What Are Manual Reports?
Manual reports are static HTML reports uploaded to your workspace and viewable in the same unified reports inbox as Intelligent Reports. They're ideal for:
* **Custom customer reports**: Tailored reports designed for specific accounts or use cases
* **Periodic business reviews**: Formatted reports for QBRs, executive briefings, or board presentations
* **Specialized analysis**: Reports that require a specific layout or format beyond what AI generates
### How to Get Manual Reports
Manual reports are set up by your BuildBetter team. Contact your account representative or email [support@buildbetter.app](mailto:support@buildbetter.app) to discuss what you need.
Once set up, manual reports appear in your **Reports** inbox alongside Intelligent Reports. Click any report to view it in a secure, sandboxed viewer within BuildBetter.
Intelligent Reports is currently in beta. The feature is available to workspaces with the appropriate access enabled. Contact your workspace admin or support to enable Reports.