Give Dash feedback so it improves

Dash starts general and gets specific to your team. The way you correct, redirect, and teach it shapes how it answers next time. Here’s the practice.

The three feedback shapes

There are basically three kinds of feedback Dash takes:

1. One-off correction. “That number’s wrong, recount and exclude X.”
2. Persistent definition. “When I say pipeline, I always mean Stage 3+ deals.”
3. Voice or style preference. “Match my tone. Short, no exclamation points, no ‘just circling back.’”

Each is a single Slack message. Dash decides whether to remember (definition/preference) or just fix this one time (correction). You can always be explicit about it.

One-off correction

When Dash gets it wrong this once, just say what’s wrong:

@Dash that number’s wrong. The Pollen deal got marked won yesterday and should be in the closed-won column.

Dash will fix the current answer, confirm what it changed, and re-post. It will not assume this applies to future asks unless you tell it to.

Persistent definition

When you want Dash to use a definition forever, say “from now on” or “always”:

@Dash from now on, when anyone asks about pipeline, only count deals at Stage 3 or higher.

@Dash always exclude the test workspace (workspace_id starts with “test_”) from active workspace counts.

@Dash when I say “the team,” I mean the four leadership members listed in this channel.

Dash will confirm (“got it: pipeline now means Stage 3+ deals, applies to all asks in this workspace”) and write it to the workspace memory. You can list everything it remembers any time:

@Dash what definitions are you using for this workspace?

Dash will print the list and you can remove anything stale.

Voice and style preference

For email drafts, reports, and any document Dash writes, you can lock in voice:

@Dash my outbound voice: short, direct, no exclamation points, never use “just circling back,” “hope this finds you well,” or any other corporate filler. Sign off with “Vinay” only, no “Best,”.

@Dash investor updates should be 4 sections: numbers, wins, asks, hires. No fluff at the top, no aspirational language at the bottom.

@Dash for internal Slack posts, use sentence case for headlines, never Title Case.

Dash applies these immediately and to every future draft. You can also point Dash at an existing document:

@Dash use the voice in our Notion page “PS Voice Guide” for all outbound emails going forward.

Dash will read the doc once, summarize what it learned, and ask if that’s right before locking it in.

When Dash asks for feedback

Sometimes Dash will explicitly ask. Common cases:

• After a recurring report’s first run: “Does this format work for you?”
• After a draft email: “Should I always use this tone for follow-ups to Northbound contacts?”
• After a correction: “Want me to remember this for future asks?”

Say yes or no. Yes locks it in; no keeps it as a one-off.

Removing or changing remembered facts

If Dash is using something outdated, just tell it:

@Dash forget that pipeline means Stage 3+, use all deal stages from now on.

@Dash replace my voice preference. New rule: drafts should be one paragraph, conversational, opener can be casual.

Dash will confirm what it dropped and what’s now in effect.

What Dash does NOT remember

• Conversations from other people’s private DMs with Dash (those are scoped to them).
• Anything in a channel Dash was kicked out of before learning the fact.
• Anything Dash explicitly said it wouldn’t remember.
• Sensitive info Dash flagged as “don’t store” (passwords, PII, etc.).

What’s next

• Ask Dash for a report once you have a few definitions locked in, your reports get sharper fast.
• Set up your morning briefing so Dash uses your custom definitions automatically every day.