Skip to content
Dash Help
Request 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.

In the channel, type:

/invite @Dash

Slack adds Dash to the member list. Dash will post a short hello within a few seconds. Standard greeting:

Hi everyone! I’m Dash, your AI teammate. I can pull data, draft documents, answer questions, and help out with the work this channel does. I won’t post anything unless someone asks me to. Type @Dash help to see what I can do here.

The channel goes quiet. Nobody gets pinged. Dash sits and waits to be talked to.

Channels usually have a topic, but topics are short. Give Dash the longer version once, and it remembers:

@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 (“got it, leadership channel, three named members, focus on weekly numbers and priorities”), and from then on it answers asks in this channel with that frame.

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.

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.
  • What can be posted from this channel? If the channel handles sensitive info, lock it down: @Dash never post anything from this channel into another channel or to anyone outside our four members. Dash will store this rule and refuse cross-channel actions.

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

/kick @Dash

Dash will not read or post in the channel again unless re-invited. Anything Dash already saw before being kicked stays in Dash’s memory for this workspace, but it won’t fetch or reference channel-specific context after removal. To wipe its memory of the channel entirely, ask: @Dash forget everything you saw in #channel-name.

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.