Demos for Slack sandbox templates
Partners can select from a number of templates to load test data into a sandbox during provisioning. Follow along with the demo associated with the template to learn more about the template content, or try presenting it to a friend.
Template demos
Marketing
This demo follows a marketing professional through a live campaign launch: six days out, board pressure on, agency still emailing updates. It shows how Slack becomes the go-to-market operating layer from AI-powered revenue signals and real-time Salesforce data to agency collaboration and campaign execution without switching tools.
| Value | Talk track |
|---|---|
| The CMO under pressure | "Only 29% of marketing leaders say they can confidently prove marketing's impact on revenue." (Gartner; CMO Spending Survey) Not because the data doesn't exist, but because it lives in too many places, and nobody has time to pull it together before the 9am meeting. What you want to show is how that changes with collaboration in Slack. Let's follow one campaign: the AI Customer App launch, six days out. |
| Slackbot: the revenue question, before a dashboard | "What pipeline has the AI Customer App campaign influenced so far, and are we on track to hit our Q2 target?" Slackbot pulls from Salesforce campaign data, attribution metrics, and conversations happening across marketing, sales, and connected systems such as Google Drive and Figma. In seconds, one signal stands out: enterprise is converting at 2x mid-market. That's what you walk into the meeting with. The gap isn't data, it's that most AI tools are built to summarize what you already have: one document, one file, one thread. Slackbot connects the entire Go-to-Market (GTM) engine. Other collaboration software just summarizes content; Slackbot is one step ahead answering revenue questions. |
| Campaign channel: the GTM command center | Every conversation, asset, and decision lives in the #ai-customer-app-new-product-launch channel, combining marketing, sales, and agency partners. Haley flagged the enterprise conversion rate this morning. Tracy's account executives are reporting that command center messaging is resonating with VP-level buyers. Luke ran the budget model and routed approval all in-channel, no meeting required. This is the difference between a team that reacts to signals, and one that acts on them. The conversation and decision-making happen in the same place. |
| Canvas: one brief, always current | At the top of the channel is the campaign canvas that includes target segments, messaging, launch milestones, and owners. Every team touching this launch is aligned to the same plan instead of a deck that gets emailed around and forks into twelve versions, or a doc that someone updates and then forgets to share. When something changes, everyone sees it. Marketing, sales, leadership, and agency partners are all on the same page. That's the strategy; now here's how the team executes against it. |
| Lists and workflows: execution without chaos | Launch milestones live in a Slack List: deliverables, owners, due dates, and status. Everyone knows what needs to happen and who owns it in the same channel with no need for context switching. When the budget reallocation needed approval, the team didn't send an email or schedule a meeting. They triggered a workflow, automatically routing the request to the right stakeholders, captured the decision in-channel, and moved on with no need to chase feedback or have a status meeting to stay aligned. Execution happens right here. |
| Slack Connect: agencies in the workflow | Remember version nine of that creative asset that came in via email (logo_final_final2_v9.jpg)? That stops here. Your agency isn't working over email, they're right in your channel via Slack Connect. Creative assets come in here, feedback happens in thread, and branding, legal, and campaign owners are aligned in real time. Since files from Google Drive and Figma are shared directly in Slack, feedback always stays connected to the work itself. That's the difference between a review cycle that takes days or weeks and one that takes hours. |
| Enterprise Search: strategy with memory | "Have enterprise segments outperformed in past campaigns, and did it hold through the funnel?" Enterprise Search surfaces prior campaigns, post-launch analysis, and the decisions you made last time. Not just the files, but the context as well. The retrospective from your last product launch, the thread where you almost missed the same signal, the post-mortem that said next time, move faster on enterprise. Other collaboration software just finds documents; Slack finds the decisions behind them. That's not a small distinction; that's the entire competitive advantage. |
| Tableau: measurement where decisions happen | We confirmed the signal. The budget shifted. The campaign is live. Now the question changes from "are we ready?" to "is it working?" That answer lives right here: embedded in the channel is the Tableau dashboard, which displays pipeline influenced, ROI, and conversion by segment, alongside the conversations interpreting it. That enterprise signal you spotted? It's right there in the data, impossible to miss or ignore. When you see a shift, you don't schedule a readout. You act right here. |
| Slackbot: the recap writes itself | "Summarize campaign performance, key decisions, and what you would do differently." Slackbot pulls from channel activity, Tableau metrics including decisions made, the context behind them, and summarizes what to do differently next time. The work already happened here, so the story surfaces itself. Every tool your team used and every conversation that shaped the campaign all lived in Slack, which means the institutional memory lives here too. |
| Close: marketing as a revenue operating model | Remember where you started? Six days out. Board asking for confidence. VP of Sales questioning the segment strategy. Agency on version nine of the creative asset, still working over email. That CMO just walked into the 9am meeting with an answer: pipeline influenced, enterprise signal identified, spend adjusted, agency aligned, campaign live. The board's question isn't going away: what did marketing actually generate? The CMOs who can answer it aren't the ones with better dashboards; they're the ones who closed the loop between signal and decision before the meeting even happened, and that's what you just saw. |
Sales
This demo follows a sales professional through a high-pressure, quarter-end moment. They have a forecast call in 10 minutes, a deal risk buried in fragmented direct messages, and a key enterprise account showing signs of slipping. This example shows how Slack becomes the revenue execution layer, from AI-powered deal signals and live Salesforce data to account intelligence and institutional memory, all without needing to leave the conversation.
| Value | Talk track | Slack feature |
|---|---|---|
| Executive hook: revenue execution problem | "Sales reps spend 60% of their time on non-selling work." (Salesforce State of Sales, 2026). That's not a sales rep problem, it's a systems problem, and it shows up the same way every quarter: forecast calls turn into status chasing, and the context lives across inboxes and fragmented direct messages. A deal that looks healthy on Monday becomes a surprise by Friday. This demo shows how modern revenue teams operate differently, with Slack as the execution layer. | Title slide |
| Slackbot: revenue radar | "Across all enterprise accounts, flag any competitive mentions, pricing pressure, or stage regression in the last 7 days." In seconds, Slackbot scans Salesforce data, Slack conversations, and connected systems to surface real signals. It flags DataNet, increased discount pressure, and a new stakeholder thread. Other collaboration software summarizes content; Slackbot answers revenue questions across your business. Let's start with DataNet. | Slackbot output |
| Anchor: DataNet account channel | This is the DataNet account channel, tied 1:1 to the Salesforce record. Every conversation, artifact, and decision lives here. AE, SE, CSM, finance teams are all aligned in one place. This isn't chat, it's where decisions about the account get made. This model scales, standardizing how every deal is executed across the business. | Channel view |
| Live CRM context: record details | In the Opportunities Details tab, you have all related opportunity stages, amounts, close dates, and next steps in one place, which all contain live Salesforce data. If you were to update it here, it would update everywhere instantly. This is CRM embedded directly into execution, not something that needs to be manually updated after the fact. | Record tab |
| Strategy and execution | Right next to that is the Deal Strategy Canvas with stakeholder map, positioning, and next steps. The Mutual Close Plan lives as a Slack List, containing owners, milestones, and due dates. This is the difference between a strategy that lives in a deck that nobody updates and a plan that lives where the work actually happens. | Canvas + List |
| Slackbot and executive brief | "Summarize the current state of DataNet: risks and expansion signals." Here, you get an executive-ready brief grounded in CRM and live deal activity. What used to take an hour of preparation now takes a couple minutes. | Slackbot summary |
| Enterprise Search: institutional memory | "What discounts have we offered DataNet in the past?" Enterprise Search surfaces prior Slack threads, Salesforce notes, and approvals, all in one place. You can immediately see the conversations tied to those decisions so you're not guessing how this was handled before. Other collaboration software just finds documents; Slack also finds the decisions behind them. | Search results |
| Close: revenue operating model reframe | What you just saw isn't a faster version of how revenue teams work today; it's a completely different model. The signal found you because the context was already there. You walked into the forecast call with answers instead of questions. The teams that win aren't the ones with more dashboards; they're the ones who see risk sooner, decide faster, and execute together. That's the difference between reporting on revenue and creating it. | Closing |
IT incident management
This demo follows an IT professional through a live Priority 1 (P1) incident. There are alerts firing across five systems, engineers scrambling, and compliance watching. It shows how Slack becomes the intelligent operations layer connecting AI, governance, and the entire tech stack so that incidents resolve faster, knowledge compounds, and risk surfaces before it escalates.
| Value | Talk track | Slack feature |
|---|---|---|
| The integration crisis every CIO is managing | 82% of IT leaders say integration is their biggest barrier to AI success, not budget or talent. What CIOs say is this: "We have the tools. They just don't talk to each other." That's a digital graveyard. Hundreds of licenses, alerts in five different systems, resolutions in email, and governance in spreadsheets. You don't want to show another collaboration tool; you want to show you what it looks like when your AI, your governance controls, and your tech stack operate as one system. | Title slide |
| The live command center | One channel for everything: #it-major-incidents. PagerDuty escalation, API latency thresholds breached, support flagging checkout failures: everything comes through here. You can see alerts coming in from the systems you already rely on such as PagerDuty as well as monitoring tools and deployment updates. The incident manager is already coordinating engineering, and everyone is aligned in one place. | #it-major-incidents |
| Slackbot: signal before the noise | "Summarize the status of our active incidents in #it-major-incidents." In seconds, you get impacted systems, active blockers, owners, and the incidents that need executive attention first. No context switching between tools or digging through threads. This is usually the moment where you get asked: "How is this different from what other collaboration software does?" Other collaboration software just finds documents; Slack surfaces risk. | Slackbot |
| AI-Assisted engineering: acceleration inside governance | The team just identified the bottleneck: a database connection pool hitting capacity during peak load. Now engineering brings an approved AI coding assistant in Slack to analyze the affected service and propose a solution. The entire troubleshooting flow stays right here in the incident channel. Every action taken from analysis to resolution is logged, auditable, and governed. This is acceleration without sacrificing control. | Engineering workflow |
| Knowledge that compounds: resolution to learning | The fix is deployed and latency stabilizes. Customer impact drops to zero, and the team never left the channel. Slackbot generates a resolution summary and converts it into a Canvas that includes the issue timeline, root cause, and next steps. It lives in the channel so the next time this happens, that knowledge is already part of how the team responds. | Canvas + summary |
| Governance: built into every step | That Canvas isn't just a summary for the team; it's also the audit trail. If compliance asks what happened, the answer is already there. Who did what, when, and why is already captured. Audit logs, data protections, and access controls are built in. This isn't speed at the expense of governance; it's governance embedded directly into how work gets done. | Canvas + summary |
| Enterprise Search: from incident to insight | "Have there been any similar Payment API latency incidents over the last 6 months?" Enterprise Search pulls past Salesforce tickets, resolutions, prior Slack threads, and incident records, all in one place. You get a clear answer and the decisions tied to it. This is how you stop reacting to incidents and start preventing them. | Enterprise Search |
| The reframe: from tool sprawl to intelligent operations | Most CIOs aren't short on tools; they're short on cohesion. Slack becomes the layer that connects your systems and your governance model into one way of operating. What you just saw wasn't a faster incident response, it was a different operating model. The signal surfaced before it became a crisis, the team resolved it without leaving the channel, and the knowledge was captured and summarized. The CIOs who win aren't the ones with more tools, they're the ones whose systems actually work together. | Closing |
HR
This demo follows an HR professional through a high-stakes merger & acquisition moment with two hundred new hires from an acquired company starting on day one. It shows how Slack becomes the operating layer for the entire HR integration from executive visibility and change management to scaled onboarding and culture integration without adding headcount.
| Value | Talk track | Slack feature |
|---|---|---|
| Hook: the cost of getting integration wrong | 70% of change initiatives fail because employees don't adopt the change. 88% of organizations say their onboarding is poor. When a new hire doesn't work out, it can cost up to twice their salary. Now put yourself in this situation: it's Monday morning, you just acquired Northstar, and two hundred employees are starting today. If onboarding breaks, culture fractures, and if people get confused, productivity drops fast. HR doesn't get a second shot at that first impression. What you want to show is how that moment gets managed differently. | Title slide |
| The CHRO control tower | The #hr-leadership channel is where the Northstar integration is being coordinated across the leadership team. Every signal, decision, and action lives here. | #hr-leadership |
| Slackbot: executive intelligence in seconds | "Summarize the last week and flag anything tied to Northstar onboarding, including confusion, blockers, or attrition risk." In seconds, you see where employees are confused and where HR needs to step in, no second meeting or slide deck request required. Most AI tools are designed around a single artifact such as a meeting, file, or thread. What Slackbot just did is different: it synthesized signal across every conversation tied to Northstar, across every team. Other collaboration tools just summarize content; Slackbot surfaces organizational risk. | Slackbot summary |
| Change management: alignment at speed | Now, you need to move on it. Integration doesn't fail because people didn't communicate, it fails when alignment breaks and momentum slows. Instead of broadcasting and waiting, you communicate it in one place where you can thread questions and offer real-time answers. If you need to, you can ask Slackbot to draft the welcome message detailing culture, expectations, where to go, and what matters in week one. It lives where the conversation continues, with no need to context switch between tools. Most change management looks like this: someone drafts an announcement, emails it, and hopes it lands. What you just saw is different because it's not a broadcast, it's a conversation. Questions get answered in context, and alignment happens in real time. Other collaboration tools are built for posting messages; Slackbot creates real change. | Executive thread |
| Scaling answers, not headcount | That's how leadership layer stays aligned: ten people, one channel, no status meetings. However, Northstar didn't bring ten people, it brought two hundred, and every single one of them has questions about benefits enrollment, systems access, and what day one actually looks like. HR can't field two hundred individual direct messages, so there's one place every employee goes to get answers: a public help channel called #hr-help-onboarding where workflows handle questions at volume, summarizing frequently asked questions so your team never has to answer the same thing twice. When a question needs a real decision from a real person, such as a system access request or an onboarding exception, a workflow routes it with context and a person can approve it quickly, keeping the momentum going. | #hr-help-onboarding |
| Scaling onboarding for 200 people without scaling HR | The help channel handles what everyone shares. Onboarding isn't just about answering questions though, it's about making sure each person feels set up, supported, and not lost on day one. Every new hire also gets their own dedicated channel, structured from day one. | #onboarding-sandra |
| Canvas: the operating surface for onboarding | At the top is the Welcome Canvas, which contains a first-week schedule, benefits information, systems access, and key contacts. Rather than a document someone forgets to update or a portal no one checks, the Canvas lives here where the questions get asked and the work actually happens. | Canvas |
| Capability: retaining knowledge | "Who owns vendor operations from Northstar?" Slackbot surfaces the right person, the work they've done, and the context behind it. That expertise doesn't stay siloed, it becomes accessible across the organization immediately. | Slackbot |
| Enterprise Search: policy without confusion | "What's our offsite travel guidance for Northstar employees?" You don't just get a document, but the decision, the discussion, and the context behind it. You're aligned with how the organization decided and no one has to guess. | Enterprise Search |
| Culture: belonging that drives performance | The systems are set and the answers are surfaced. However, there's one thing no workflow delivers, and that's the thing that actually determines whether a person stays: the feeling of belonging. Culture integration doesn't happen in an all-hands, it happens here in the flow of work. Things like recognition, collaboration, and day-to-day interaction. That's when employees stop feeling like they simply joined a company and start feeling like they belong, and that's what drives how fast they ramp up and whether they stay. | Culture channels |
| Close: HR as a scalable operating model | Remember those numbers from the title slide? What you just watched is what it looks like when those odds change. HR doesn't scale by adding headcount, it's in the way the company operates and supports the people inside it. What used to take three follow-up meetings now happens in one thread, and the knowledge that used to stay siloed is now accessible the moment someone needs it. Onboarding isn't something you hope goes well, you already know it's going to be successful, and that's the shift. | Closing |
Finance
This demo follows a finance professional through a high-pressure Q4 moment: a $1.1M vendor renewal surfacing as a forecast risk, with a $2.5M budget reallocation on the table. It shows how Slack becomes the operating layer for finance without slowing down the close, from executive visibility and risk detection to governance and audit-ready decisions.
| Value | Talk track | Slack feature |
|---|---|---|
| Executive hook: decision Latency | Let's take a look at how you can achieve 37% faster decision making when the data, people, and decisions all live in one place. | Title slide |
| Slackbot: CFO control tower | "Summarize discussions this week about the Q4 forecast variance and flag any risks tied to the vendor renewal or budget reallocation decisions." Slackbot scans the conversations happening across sales, operations, and finance teams and produces an executive briefing in seconds. Other software collaboration tools can only summarize a document; Slackbot can summarize the work as it's happening across the business. | Slackbot prompt |
| Finance command center: structured channel with Canvases | A $1.1M vendor renewal is due in two weeks. The data, conversation, and decisions are all in one place. | Channel + Canvas |
| Governance: budget reallocation approval | Looking at the data and the conversation, the team proposes reallocating unused budget from another program to cover the renewal. In most companies, this is where things slow down, because approvals happen across spreadsheets and email threads and the decision trail gets lost. In Slack, the finance team runs the approval directly here. The request, discussion, and approval all live together, creating a clean governance trail. Other collaboration software can message about an approval; Slack runs the approval with the decision and audit trail attached. | Approval thread |
| Enterprise Search: financial precedent | "What's our precedent for approving mid-quarter budget reallocations above $50K?" Slack instantly surfaces the last time finance approved a similar exception, including the discussion and supporting documents. Other collaboration software finds files; Slack Enterprise Search finds the decision history behind them. | Enterprise Search results |
| External collaboration: Slack Connect auditors | The decision is documented and the approval is logged. Now, during quarter close, the external auditors collaborate with us in a Slack Connect channel. Finance, legal, and audit teams review documentation and discuss findings in one secure workspace instead of in long email chains. Guest access in other collaboration software is slow and security-limited; Slack Connect gives auditors a persistent shared channel with the full context attached. | Slack Connect channel |
| Slackbot writes to Salesforce | "Log a finance review note on all 3." You've just created an audit trail for reporting purposes without even opening Salesforce. | Slackbot + Salesforce |
| Closing: operating model reframe | The signal surfaced before it became a crisis, the decision happened with the context attached, and the audit trail built itself as the work happened. That's not a faster version of how finance works today, it's a different model entirely. | Closing |
Customer support
This demo follows a customer service professional through a high-stakes incident where DataNet customers can't log in, call volume is spiking, and SLAs are already at risk. It shows how Slack becomes the operating layer for service from executive visibility and real-time incident response, to pattern detection and root cause elimination without the chaos of chasing updates across tools.
| Value | Talk track | Slack feature |
|---|---|---|
| Executive hook: the moment that matters | It's 7am and you're getting alerts that DataNet customers can't log in. This isn't just a bug; it's a P1. Call volume is spiking and SLAs are already at risk. If you don't get ahead of this fast, it could cause customer churn. In fact, half of customers will switch providers after a single bad experience. Yet most service teams still manage moments like this the same way they always have: by reacting to messages, chasing updates, and trying to piece together what's happening across tools. What you want to show is a different way to run customer service where people don't react to incidents, they stay ahead of them. | Title slide |
| Slackbot: instant operational clarity | "Summarize #cs-case-04769507 and identify what's still unresolved." Every AI tool right now promises summaries, but there's a big difference between summarizing a document and summarizing what's happening to your customers in real-time. Slackbot is pulling from your live operation including Slack conversations, connected systems, and real-time incident activity, giving you a current view of what's happening. Other collaboration software can summarize a document or a meeting; Slackbot is summarizing your live operation. | Slackbot |
| The service channel: where resolution actually happens | The #cs-case-04769507 channel combines support, engineering, and product teams so everyone is on the same page, with no need for escalation across different tools. This is where most service teams still struggle, since collaboration happens in one place, and the system of record lives somewhere else. Other collaboration software gives you a place to talk; Slack gives you a channel that's already populated with the right people, where the collaboration and data live in the same place. | #cs-case-04769507 |
| AI Summary: no catch-up required | No one wants to read two hours of messages to find out where things stand. You can generate a summary with key decisions, what's already been tried, what's next. The logs, GitHub issues, and deployment notes are right next to the conversation they informed. This isn't just communication, it's a complete execution history. | AI Summary |
| Slackbot: don't start from zero | "Find similar authentication incidents and how we resolved them." Slackbot surfaces a prior case with the same symptoms, and the same type of resolution path. What used to take hours of searching now takes seconds. This is how your team moves faster; not by working harder, by starting from what's already known. | Slackbot prompt |
| Huddle: resolve in real time, capture everything | With the available context, the team jumps into a huddle. They troubleshoot live and make decisions fast. When it ends, Slack automatically posts a full summary including all the decisions, actions, and next steps. Nothing gets lost in a meeting recording, and everything becomes part of the case history. | Huddle summary |
| Enterprise Search: from incident to pattern | "What authentication error cases have occurred in the last six months?" Enterprise Search pulls prior cases, escalation threads, and resolutions across every system. Here, you can see what happened, how it was handled, and whether it worked. This is how you stop resolving incidents and start eliminating root causes. | Enterprise Search |
| Close: the operating model shift | What you just saw isn't faster case resolution, it's a different mode of operation. The work happened once. Your system of record updated itself automatically. The next time this happens, your team doesn't start from zero. The teams that win aren't the ones who respond the fastest, they're the ones who never have to respond to the same incident twice. | Closing |