Draft and send an email with Dash

Drafting and sending email is the canonical example of Dash’s approval flow. The draft is free, the send is gated. Here’s how it actually plays out in Slack.

The shape of a good ask

Tell Dash the recipient, the gist, and (optionally) the tone:

@Dash draft a follow-up to Rachel Jiang at Northbound. We left it at the pricing question last Tuesday. Friendly, short, no pressure. Include the case study link.

Dash will pull context from your Gmail (the last thread with Rachel), from HubSpot (the deal stage), and from anywhere else useful. You don’t need to paste the previous email.

What Dash sends back

A typical first draft, in your DM with Dash:

Draft to: [email protected] Subject: Quick question on Q3 timing

Hi Rachel,

Following up on last Tuesday. Wanted to share the Pollen case study we mentioned, since their setup looks close to yours: [link].

Happy to answer the pricing question whenever you have a chance to circle back. No rush.

[Your name]

Approve and send Edit Discard

You see the full body before you do anything. Three actions:

• Approve and send: Dash sends the email through your Gmail. You get a confirmation in DM with the sent timestamp.
• Edit: Opens a modal where you can rewrite the body. Common edits are tone tweaks, swapping a link, or adding a P.S. Save the edit and Dash will re-show the approval prompt with the updated draft.
• Discard: Dash drops the draft. Nothing sends.

Voice and tone

Dash matches your voice by default. If your sent folder is mostly short and direct, drafts will be short and direct. If you have a one-page voice guide, point Dash at it once:

@Dash use the voice guide in our Notion at “Outbound voice” for every cold email from now on.

Dash will remember that and apply it. See Give Dash feedback so it improves for how this learning works.

Send from your account, not Dash’s

Emails go out from your Gmail address. The recipient sees “From: Vinay Patankar” on the email, not “From: Dash.” Dash is the assistant; you are the sender. This matters for trust signals on the receiving end and for any reply going back to you in your normal inbox.

If you want Dash to send from a shared address (sales@, hello@), the workspace admin can configure that. See the docs on [team and shared addresses] if you’re set up for it.

Reply chains

If the recipient replies, the response goes to your inbox like any normal email. You can then loop Dash back in:

@Dash Rachel replied. Draft a response that schedules the call she suggested for next Wednesday.

Dash reads the reply (with your permission), drafts the next move, asks for approval again. The cycle repeats. You never lose visibility.

Bulk outbound

For more than one recipient at a time, see [Outbound that runs itself]. The principle is the same (Dash drafts, you approve), but the approval prompt becomes a batch review where you can approve, edit, or skip per row.

What Dash will NOT do

• Send an email without your approval, ever, regardless of recipient.
• Send from an address you have not authorized.
• Reply to an email Dash hasn’t seen the original of.
• BCC anyone you didn’t tell it to.
• Include attachments you didn’t tell it to.

What’s next

• How approvals work for the full breakdown of what triggers an approval prompt.
• Give Dash feedback so it improves to teach Dash your voice once and never re-teach it.