Skip to content
Dash
Request early access Early access

Bring Dash into a new channel

Dash is only useful where it’s been invited. New channel, new context, new ground rules. Five minutes of setup makes Dash a useful teammate in that channel for the long haul.

Invite Dash

Section titled “Invite Dash”

In the channel, type:

/invite @Dash

Slack adds Dash to the member list. Dash goes quiet — it never posts unprompted, so the channel stays clean until someone @mentions it. That’s by design: an unused Dash is invisible.

To kick things off, just @mention it:

@Dash what can you do here?

Dash will reply with a short read on the tools it has access to and the kinds of things the team could ask it in this channel.

Set the channel’s purpose for Dash

Section titled “Set the channel’s purpose for Dash”

Channels usually have a topic, but topics are short. Give Dash the longer version once, and it remembers (for public channels — see the memory note below):

@Dash for context: this channel is where the leadership team reviews weekly numbers and decides priorities for the next week. Pipeline, MRR, top-of-funnel, and any flags. People here are Vinay (CEO), Aisha (COO), Marcus (Head of Sales). When I ask for “the team,” I mean these three.

Dash will acknowledge and answer future asks in this channel with that frame.

Give Dash the channel’s tools

Section titled “Give Dash the channel’s tools”

If the channel needs a specific tool that Dash hasn’t connected yet, ask in the channel:

@Dash for this channel, I’ll need you to be able to pull from HubSpot and Stripe.

Dash will check what’s already connected and offer one-click links for anything missing. See Connect your first tool for the full flow.

Set the channel’s ground rules

Section titled “Set the channel’s ground rules”

Two common settings worth being explicit about:

  • Auto-post or wait-for-ask? Dash defaults to waiting. If you want Dash to post a recurring report into the channel without being prompted each time, say so: @Dash post the weekly numbers here every Monday at 8 AM and confirm. That runs on Dash’s scheduled-tasks engine.
  • What can be posted from this channel? If the channel handles sensitive info, say so plainly: @Dash never post anything from this channel into another channel or to anyone outside our four members. Dash respects rules like this per-thread.

Where Dash remembers what you tell it — and where it doesn’t

Section titled “Where Dash remembers what you tell it — and where it doesn’t”

Dash’s durable memory is workspace-wide, but it’s only writable from public channels. Conversations in DMs, private channels, and multi-person DMs are read-only — Dash can still read the workspace’s memory, but nothing said in a private conversation gets recorded. So facts you want Dash to remember belong in a public channel.

Remove Dash from a channel

Section titled “Remove Dash from a channel”

If Dash shouldn’t be in a channel anymore (sensitive HR conversation, an investor channel, etc.), kick it:

/kick @Dash

Slack stops sending Dash any events for that channel the moment it’s out, so it can’t read or post there again unless it’s re-invited. Anything Dash learned from that channel earlier and wrote to workspace memory is still there — you can review and prune it from the memory page in the dashboard.

Channels Dash should always be in

Section titled “Channels Dash should always be in”

Some channels make Dash dramatically more useful when it’s there from day one:

  • #leadership (or whatever you call it): so Dash can answer “how are we doing” anywhere in the room
  • #sales or #growth: so Dash can run pipeline asks, ad audits, and outbound drafts
  • #cs or #customers: so Dash can summarize calls, draft renewals, and flag risk
  • #ops or #finance: so Dash can pull reports, reconcile invoices, draft SOPs

Add Dash to these on day one. The marginal cost of having Dash present is zero (it never posts unprompted), and the value of someone in #sales being able to type @Dash pipeline? compounds fast.

What’s next

Section titled “What’s next”