Image of Slackbot message next to headline claiming 50+ billable agency hours saved per month

Slackbot moves work forward faster for Salesforce’s communications team.

With Slackbot, Salesforce’s communications team can turn interviewer backgrounds, talking points, and business context into complete briefing books in minutes.

The Results

50 +

billable agency hours saved per month

98 %

communications team Slackbot adoption

Strategic Work Delayed By Prep

For Salesforce’s global communications team, preparing executives for high-stakes meetings is a constant, no-margin-for-error responsibility. Every meeting requires a briefing book containing objectives, key points, and participant background.

Assembling briefing books used to require team members to manually pull bios, find recent company announcements, and gather approved metrics — all from separate systems. After that, they had to format everything to match each executive's preferred voice and learning style.

At three hours per briefing book, manually assembling the research and materials that go into prep sessions was one of the team’s most time-consuming tasks. That left less time for the strategic and creative work that advances the team toward meeting the rest of their goals.

Briefing Books in Minutes

Slackbot has fundamentally changed how the team prepares executives, turning an hours-long manual process into a conversation. To generate a briefing book, a team member starts a chat, provides the participant’s name and the executive being interviewed, and Slackbot pulls together everything needed to walk into that interview prepared.

The team also added executive voice matching, so any team member can request a briefing book tailored to a specific leader’s tone, cadence, and messaging style. With the briefing book complete, the team can then ask Slackbot to generate supporting assets like podcast scripts or all-company posts — all aligned to the same approved messaging.

Prompt-Driven Speed

The entire capability is built on a custom prompt in a Slack canvas — the brain of the briefing book generator. It defines the structure, governing rules, and source restrictions for every output.

The team built three templates covering different interview and meeting formats, ensuring consistency regardless of who generates the book. The prompt also specifies exactly where Slackbot should look for each piece of information — which curated Google Docs folder holds approved talking points and executive voice examples, and where to find real-time reporter background and relationship context.

When Slackbot is done, it adds the briefing book to a Slack canvas where the team can collaborate to refine it in real time. Because everything happens inside Slack, there’s no context-switching, no exporting, and no starting over.

50+ Agency Hours Saved Per Month

Ninety-eight percent of the communications team is now using Slackbot. A briefing book request that once came in at noon might not have been ready until the next day. Now, an executive can have a fully formatted, on-brand briefing book in hand within 20 minutes of the request.

Keeping up with briefing book requests used to require more than 50 billable hours of help from external agencies each month. With Slackbot handling assembly, the team gets those hours back and can put them toward higher-value, strategic work.

The Salesforce Difference

Contextual Intelligence

Before Slackbot, the team tested Gemini, but Slackbot delivered stronger results. Where Gemini pulled context only from Google Docs, Slackbot searches across Slack conversations, shared files, and connected knowledge repositories, grounding every briefing book in real company history, actual executive voices, and approved messaging.

Controlled Knowledge Access

The prompt controls exactly where Slackbot looks. A curated knowledge base keeps every output accurate and on-brand, with no risk of surfacing off-message or outdated content.

Native to the Flow of Work

There’s no new tool to open. The team builds, refines, and shares briefing books without leaving Slack — and because Slackbot is already embedded in their workflows, adoption followed naturally.