The Signals dashboard shows you the data behind Fern's recommendations - support patterns and product changes that indicate documentation gaps. It's where you can explore the raw signals before they become actionable recommendations.
What's in the dashboard
Open Signals from your sidebar (look for the target icon). You'll see two tabs:
Support requests - Patterns from your support tickets, including common queries, unresolved issues, and tagged intents from Crisp, Intercom, or Zendesk.
Product releases - Changes from your codebase like commits, pull requests, and releases from GitHub or Linear.
At the top, there's a date range picker (defaults to the last 30 days). Adjust it to focus on different periods and see how patterns change over time.
Support requests tab
This tab surfaces patterns from your support data:
Top themes in your inbox
Questions that were answered by your docs
Questions that weren't answered by your docs
Each item links back to the original ticket so you can see the full context. Customer queries with missing documentation are particularly useful - they represent users who couldn't find what they needed in your help center.
Look for patterns across multiple tickets pointing to the same topic. That's usually a high-priority documentation gap.
How to use support signals
Support data helps you spot frequently asked questions, confusing areas where existing docs aren't clear, and topics generating the most volume. You can also track whether recent documentation updates are reducing support tickets.
Product releases tab
This tab shows changes from your codebase:
Recent commits that introduce new features or modify behavior
Pull requests that have been merged
Published releases bundling multiple changes
Breaking changes that affect user workflows
Each item links to the corresponding GitHub commit or PR for technical details.
Taking action
When you spot a documentation opportunity in Signals:
Check your Inbox - Click the Inbox button on the monitoring card to see if Fern already created a recommendation for this pattern. If so, you can assign it to Fern or handle it yourself. Learn more about how Fern generates recommendations.
Create content manually - If you see a clear pattern but no recommendation exists, create or update articles directly.
Run a fresh scan - If you've just connected new integrations or want to analyze very recent data, trigger a manual scan to generate updated recommendations.
Next steps
After exploring Signals:
Review your Inbox to see recommendations based on these patterns
Prioritize documentation work based on signal volume and business impact
Track how your updates affect support request patterns over time
Share insights with your product and support teams to align on priorities
The combination of Signals and your Inbox gives you a complete system for data-driven documentation maintenance.