Slack Agent

Slack Agent brings the same agent you use in the dashboard (In-product Agent) into your Slack workspace. Look up profiles, trigger workflows, change preferences, pull delivery analytics, and ask product questions, all from a DM or channel. Two things to know before you install:

Privacy Filter is always on outside 1:1 DMs. Replies are checked for PII before they’re posted to a channel or group DM. A reply flagged as containing PII is shown only to the requester, as a private message in the thread; the channel sees a short notice. The check is model-based and best-effort: if it can’t run, the reply is posted to the channel as usual. See Privacy Filter below.
AI is optional. SuprSend’s notification stack (workflows, templates, channels, preferences, delivery, analytics) does not depend on AI. If your organization can’t share data with third-party model providers, don’t connect the Slack App, and have an admin turn off the In-product Agent. See Settings.

Quick start

Connect Slack. A SuprSend admin clicks Connect to Slack in Account Settings → AI & Agents and approves the app in Slack.
After install, @SuprSend appears as a regular bot user in your workspace. DM it or invite it to any channel. Your Slack email must match a user in your SuprSend organization, or the bot can’t sign you in.
Start asking. Name the SuprSend workspace in your request, for example staging or production. If you don’t, Slack Agent asks which one to use:
- In a channel: type @suprsend followed by your request.
- In a DM: open a direct message with @SuprSend and just type.

@suprsend show the profile for user_123

@suprsend trigger order-confirmation for jane@acme.com

@suprsend what was our email open rate last week?

Privacy Filter

Slack channels are searchable, exportable, and often shared with broader audiences than the people who originally asked. A teammate posting “what’s jane@acme.com’s phone number?” into #growth shouldn’t leak that number to everyone with channel history access. The Privacy Filter is always on in channels and group DMs. It detects when a response would contain PII (emails, phone numbers, push tokens, device identifiers, channel addresses) and, if it does, keeps the reply out of the channel:

The channel sees a short notice in-thread: “This response contains sensitive information — I’ve sent it to you privately.”
The requester gets the full reply as an ephemeral message in the same thread, visible only to them, so the person doing the work still gets what they need.

1:1 DMs are private, so the filter doesn’t apply there, and full identifiers are returned inline. Group DMs are filtered like channels.

Surface	When to use it	What the Privacy Filter does
1:1 direct messages	Private lookups, work tied to a specific user, anything involving identifiers, channel addresses, or device tokens.	Inactive. Emails, phone numbers, push tokens, and other PII are returned in full.
Channels and group DMs	Team-visible work, like analytics summaries, workflow audits, debugging in front of teammates.	Always active. A reply with PII is shown only to the requester, as an ephemeral message; the channel sees a notice instead.

The filter runs at the response layer, not the prompt layer. Teammates can still ask sensitive questions in channels; the filter checks the answer so it doesn’t expose PII in a place it shouldn’t live. Approval prompts for changes (see Approvals) are posted as they are, without the filter. For organizations that don’t want any prompt or response data leaving SuprSend, don’t connect the Slack App, and turn off the In-product Agent in AI & Agents. See Settings below.

What Slack Agent can help with

Data and lookups

Fetch user profiles, preferences, and object or tenant configuration. List workflows, templates, and events.

User and object management

Create or update users and objects. Manage channel addresses (email, SMS, push, Slack, and others). Update notification preferences. Add or remove users from lists, and subscribe users to objects.

Workflows and events

Trigger API-triggered workflows. Track events so event-triggered workflows can run.

Analytics

Query notification delivery stats, engagement rates, and workflow execution counts. Ask for trend summaries or charts for breakdowns over time.

Debugging delivery

Trace why a notification didn’t land for a user. Channels attempted, preferences applied, overrides hit, and execution logs in one explanation.

Documentation

Get answers about how SuprSend works. APIs, SDKs, channels, templates, workflows, preferences, and related concepts.

Slack Agent can’t build workflows or templates. Use the In-product Agent in the dashboard for that.

Approvals

Before Slack Agent changes users, objects, tenants, lists or preferences, tracks an event or triggers a workflow, it posts a confirmation in the thread with Approve and Reject buttons.

Example prompts

Slack Agent works best when prompts include a clear identifier (user distinct ID, object ID, workflow slug, tenant key). Paste these in, swap your own values, and send. Users and preferences

@suprsend Show the profile and preferences for user distinct_id "user_123".

@suprsend Why isn't jane@acme.com getting emails for the payment-reminder workflow?

@suprsend Opt user_456 out of the product-updates category.

Workflows and events

@suprsend List workflows in this workspace and summarize what each one does.

@suprsend Trigger the order-confirmation workflow for user jane@acme.com with a sample payload.

@suprsend Track a checkout-completed event for user_123 with order_id "ORD-9912".

Analytics

@suprsend What were our email delivery and open rates last week?

@suprsend Break down WhatsApp delivery by tenant for the last 30 days.

Documentation

@suprsend How do tenant default preferences interact with user-level overrides?

@suprsend What's the difference between objects and lists in SuprSend?

Settings

Slack App setup lives on the same page as the In-product Agent: Account Settings → AI & Agents. Connecting Slack is admin-only. Once an admin connects the workspace, anyone in Slack whose email matches a user in your SuprSend organization can DM @SuprSend or tag it in a channel. From the settings page, an admin can:

Connect a Slack workspace with Connect to Slack. The row then shows Connected and your Slack workspace ID.
View Slack-attributed credit usage alongside the rest of your AI consumption.

To disconnect, uninstall the SuprSend app from your Slack workspace. SuprSend’s notification infrastructure works the same without it.

AI & Agents settings page with Slack App install — Account Settings → AI & Agents. Connect Slack, turn the In-product Agent on or off, and manage credit usage from one page.

AI usage

Slack Agent shares the same credit pool as the In-product Agent. The settings page shows credits used vs. total for the current cycle, with a per-capability breakdown so you can see how much of your usage is coming from Slack.

For details on plan allowances, overage rates, and Extra Usage, see In-product Agent → AI Usage and credits.

In-product Agent

More tools, including building workflows and templates, inside the SuprSend dashboard.

MCP overview

Model Context Protocol for IDEs. Complementary to chat agents for developers.

Build with AI

MCP

Agent SDK

Quick start

Privacy Filter

What Slack Agent can help with

Data and lookups

User and object management

Workflows and events

Analytics

Debugging delivery

Documentation

Approvals

Example prompts

Settings

AI usage

In-product Agent

MCP overview

​Quick start

​Privacy Filter

​What Slack Agent can help with

Data and lookups

User and object management

Workflows and events

Analytics

Debugging delivery

Documentation

​Approvals

​Example prompts

​Settings

​AI usage

​Related

In-product Agent

MCP overview

Quick start

Privacy Filter

What Slack Agent can help with

Approvals

Example prompts

Settings

AI usage

Related