AI Summaries
AI summaries turn long threads, tickets, and usage context into short, sourced explanations attached to each needle mover. They answer “why is this here?” without asking you to open every underlying document first.
The AI Summary panel
On the needle mover detail view, the left column opens with an AI Summary: a narrative of the theme FunnelStory detected, the direction (risk vs opportunity), and the main evidence. Use Show more when the default paragraph is truncated; the model may surface additional nuance or secondary contributors.
The summary is not a replacement for the activity timeline—it is a guided entry point. When you need citations or raw text, scroll the timeline on the right.
How titles are generated
The title in the list view is a separate, highly compressed line meant for triage at a glance. Titles prioritize:
- The business theme (for example pricing pressure, competitor evaluation, champion departure)
- Severity cues reflected in impact icons
- Recency of the strongest supporting excerpt
If a title feels slightly generic, open the detail view—the summary and timeline usually carry the specificity you need for customer conversations.
Activity timeline entries
Each timeline row represents a source FunnelStory used when building or updating the needle mover. Typical fields include:
| Field | What it shows |
|---|---|
| Source and system | Channel (chat, ticket, meeting, and so on) and which connection supplied the row |
| Category | A topic label the model assigned to that interaction |
| Excerpts | Short quotes that triggered or reinforced detection |
| Participants | People involved, when available from the source |
| Summary | A per-source micro-summary |
| Details | Expandable full text for verification |
The first timeline entry is always Needle mover created with the detection timestamp so you can tell age of signal at a glance.
Inline Renari
Ask Renari Anything sits on the same screen so you can drill deeper without losing context. Renari inherits the needle mover, account, and timeline as grounding—use it to draft follow-up emails, compare similar accounts, or ask for recommended next steps. See Renari.
Quality and limitations
Summaries depend on the quality and coverage of connected data. If a timeline row shows thin excerpts, check whether the upstream integration captures full bodies (some ticketing tools default to short previews).
When the model is uncertain, the summary uses cautious language; pair that with human review before external commitments.