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 |
Entries are placed on the timeline by when the evidence happened, not when FunnelStory processed it: a conversation or note is dated by its own timestamp, so a meeting from last Tuesday sits at last Tuesday even if it was ingested today. The earliest entry therefore tells you the age of the signal at a glance. Your team's own activity — comments, assignment changes, title edits — is dated when it happened.
Status changes appear as entries showing who changed the status, from what, to what, along with any note. When a needle mover is closed because the evidence shows the issue resolved — for example, FunnelStory resolving a Discovered needle mover once the underlying problem ended — the close is dated to when it resolved, and that's also the needle mover's Closed date.
Sending an email from an Action Card tied to this needle mover adds an Email sent entry: recipient, subject, and Opens / Clicks badges that update as the recipient engages. Expand it to see the full To/Cc/Bcc and message body.
Investigation and Triage
A chat panel sits on the same screen so you can drill deeper without losing context. It's pre-loaded with the needle mover, account, and timeline as grounding — ask it to look into the situation, and it can investigate and create an Action Card directly in the conversation, outreach draft included. This is a different, purpose-built chat from the global Renari assistant — it's the Assist mode of FunnelStory's first built-in agent; see Autosuggested action cards for the same investigation running automatically in the background.
Each finished response has a Copy response button under it that copies the reply as Markdown, ready to paste into an account brief, email, or Slack message. The icon briefly changes to a checkmark to confirm the copy.
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.