Managing campaigns and donor journeys through Slack

Managing campaigns and donor journeys through Slack

DHM Team
18 November 2026
Beraded handsome man in a brown shirt sitting on the floor and looking concentrated
Busy with work. Beraded handsome man in a brown shirt sitting on the floor and looking concentrated
Beraded handsome man in a brown shirt sitting on the floor and looking concentrated
Busy with work. Beraded handsome man in a brown shirt sitting on the floor and looking concentrated

Managing campaigns and donor journeys through Slack

DHM Team
18 November 2026

Since June 2026, Salesforce Marketing Cloud Next has worked inside Slack, letting marketers and fundraisers ask for a campaign update or a donor segment, right in the channel. The agent handles the request without anyone opening Salesforce itself. Previously, you had to leave the chat to open Salesforce, find the data, and return to share it. Nowadays, ask for a new segment, a journey change, a campaign build or a performance answer in plain language, and the agent handles the request without anyone opening the platform itself.

For a team managing several campaigns at once, whether that’s paid marketing or donor communications, this changes where the daily work happens. The Slack and Salesforce integration already lets teams link Slack channels directly to opportunity and account records, so campaign and donor context has been available inside Slack for a while. What’s new is that asking a question, adjusting a segment or building a journey no longer means leaving the channel to do it.

What it looks like

For marketing teams

Ask the agent why a campaign has slowed down and get an answer without pulling a report first. Describe a new customer segment in plain language, and it maps out the audience attributes behind it. Salesforce’s own Slack marketing team used this approach to rework their paid search strategy, asking the agent to identify keywords related to ones already performing well and pulling performance data for comparison, without leaving their normal workflow.

For fundraising teams

The same pattern applies to donor work. Ask why a segment’s engagement has dropped, or describe a lapsed donor group to re-engage, and the agent builds the segment from your existing donor data. A fundraising team could ask it to find donors who gave in 2024 but haven’t renewed in 2025, and get a working segment back in the same conversation, no trip into Salesforce required.

Journey changes, campaign builds and performance questions all follow the same pattern. The agent drafts or answers, a person reviews it, and the change goes live from there. Approval stays with the team throughout. What changes is the time spent finding the right screen to make the update on.

Why it matters beyond convenience

The obvious benefit is speed, though the less obvious one is where the work happens. When campaign management sits inside the tool a team already uses for daily communication, questions get asked and answered as they come up, inside the conversation the team is already having. It shifts the rhythm of how a marketing or fundraising team works more than any single feature does on its own. It also lowers the bar for who can act on campaign or donor data. A team member who isn’t deep in the platform day-to-day can still ask a plain language question and get a useful answer, without needing to know where to look for it first. 

So, if more people can act on data without knowing the platform well, who’s accountable for what they act on?

Who’s accountable for what the agent does

Routing every action back through Salesforce means the same permissions and profile-based access that already govern who can see and edit a record still apply inside Slack. What’s getting closer attention across the Salesforce ecosystem is governance in the fuller sense, tracking who acted, on what basis, and whether the action was reviewed, alongside who’s allowed to act in the first place. 

Gartner expects more than 40% of agentic AI projects to be shelved by the end of 2027, with weak risk controls named as one of the main reasons alongside cost and unclear value. The projects that hold up tend to be the ones where a person reviews the agent’s work before it goes live, which is how Marketing Cloud Next in Slack is built to run.

That review step matters most where the underlying data does the talking. The agent answers from what’s already in Salesforce, so it’s only as reliable as that data is. It doesn’t independently verify a record before acting on it, so duplicate records, stale segments or incomplete donor histories carry the same risk they always did. Clean data matters more now, not less, because acting on it takes seconds instead of a deliberate trip into the platform.

Getting started

Start with the questions the team already asks each other in Slack, like why a campaign is performing a certain way or whether a segment needs adjusting. Those questions are a natural entry point, because they don’t require building anything new, just asking from where the team already is.

There’s also a lighter starting point: a standing weekly digest. Set the agent to post a pipeline or donor engagement snapshot into a channel ahead of the regular team meeting, so the conversation starts from an answer someone would otherwise have had to assemble first. It’s a low-stakes way to get comfortable with what the agent surfaces before asking it to build or adjust anything.

From there, journey adjustments and segment builds are a natural next step once the team is comfortable with how the agent responds to a simple question. Campaign builds are worth holding until both feel familiar, since more of the campaign depends on getting them right.

Want to see this inside your own Slack workspace? Let’s catch up and we’ll run it against one of your real campaigns or donor segments.

InsightsRecent Articles