Needle Mover Notifications
Your team learns about needle movers through in-app activity, email, channel posts (Slack or Microsoft Teams), and mentions in comments. This page describes what to expect by default and where to configure richer routing.
In-app visibility
Anyone with accounts access can open the Needle Movers list and subscribe to views with filters that match their portfolio. New and updated signals appear as you refresh data.
Assignees see ownership changes immediately in the list and on each account record.
Email
Workspace email notifications typically cover:
- Assignment changes when you become the assignee
- @mentions in needle mover comments (always directed at the mentioned user)
Slack and Microsoft Teams
For “post to a channel when something happens” delivery—across needle movers, signals, and other account events—use Admin → Notifications and connect Slack or Teams under Configure → Connections first. See:
Built-in channel notifications fire after FunnelStory processes refreshed account data, aligned with your model refresh cadence—not necessarily the instant an upstream ticket changes.
Mentions in comments
When you @mention a colleague in a needle mover comment, they receive a targeted notification (email and/or in-product, depending on workspace configuration). Use mentions for handoffs, legal review, or leadership visibility without reassigning the entire needle mover.
Assignment and status changes
Becoming assignee or having a needle mover closed usually generates a notification to the people affected. Treat these as lightweight operational pings rather than full narrative digests—the detail view and AI Summary remain the source of truth.
Advanced: AI agents
When you need branching logic, LLM judgment, or multi-step playbooks (for example “if severity is High and renewal is within 60 days, post to #risk and open a task”), use AI Agents with triggers on needle mover or signal events. Agents complement built-in notifications rather than replacing them.