Skip to main content

Notifications overview

FunnelStory includes built-in notifications so your team hears about important account activity and signals in Slack and Microsoft Teams. You configure everything in the product UI under Admin → Notifications: which events matter, which accounts are in scope, where messages go, and how they read—no code required for the standard “when this happens, post there” pattern.

That path is ideal when a single rule per configuration is enough: fixed channels, template-based messages, and refresh-aligned delivery.

Built-in channel notifications​

ChannelWhere you configureWhat you get
SlackAdmin → Notifications → new Slack configurationPosts to Slack channels you choose
Microsoft TeamsAdmin → Notifications → new Teams configurationPosts to Teams channels you authorize

See Slack notifications and Microsoft Teams notifications for step-by-step setup (including connecting Slack or Teams under Configure → Connections first).

When you need more than built-in notifications​

Some situations need branching logic, data lookups, LLM judgment, or several actions in one flow—for example “if renewal risk crosses a threshold, summarize the account in Slack, open a task, and only email the CSM when the model says it’s urgent.” For that, use AI Agents. Agents are configurable automations with triggers (schedule, events, SQL rows, manual, and more); they can call the same integrations in richer ways, including Slack, Teams, tasks, and email, plus CRM, datasets, and semantic queries. Read AI agents and notifications for how this fits next to built-in notifications.

Who can configure built-in notifications​

Workspace Admin access is required for Admin → Notifications. If you do not see it, ask a Super Admin or Admin in your organization.

Timing​

Built-in channel notifications are sent after FunnelStory has processed relevant account data—typically within a short window following a model refresh, not the instant an upstream system changes.