Send a Slack thread to anyone, without copy-paste

Slack holds a conversation well and holds a record badly. With Email Forwarding, a single envelope reaction sends the full thread to a verified address, whether that is a client, an exec stakeholder, or your own inbox, so decisions live where they need to be read.
Trigger
📧:e-mail:
Lands in
The recipient's inbox
Setup
3 min
Needs
A verified address or a trusted domain
#client-paperco
ViaApp11:26 AM

Thread sent to [email protected]

14 messages and 2 images, formatted as one email

Sent by
@evelyn
View what was sent

Only verified recipients appear in the picker, which is what stops an internal thread reaching a typo.

What this guide produces, as it appears in Slack.

How it works

  1. 1
    Whitelist a recipient, once

    An admin adds [email protected] on the Powers → Email page. Viably emails a verification link to that address, and after one click they are permanently whitelisted.

  2. 2
    React with the envelope on any message

    Viably opens a small picker showing the whitelisted recipients available. Choose one or several, then confirm.

  3. 3
    The thread is sent as a clean email

    Viably formats the entire thread, including message text, replies, and image attachments, into a single email sent from your workspace's branded sender address.

  4. 4
    Or ask Via in chat

    In @Via AI, say “email this thread to [email protected] and [email protected]. Same delivery with no menus, which helps when you are already in a Via conversation.

Verify a recipient once

Verification protects your team from accidentally sending out internal threads to emails you did not intend, or to unverified addresses that might be typos like [email protected]. This also helps protect our domain reputation, so your emails arrive cleanly in the recipient's inbox. Each address must click a one-time link before it can receive any forwards.

  • Pending addresses stay marked pending until the recipient verifies.
  • Verification links do not expire, and re-adding an address sends a fresh one.
  • Admins can remove entries at any time from the dashboard.

Trust your whole company domain

If you want every employee at your org to receive forwards without per-address verification, email [email protected] and we will add your domain. After that, any address ending in @yourdomain.com is implicitly allowed.

Reviewed rather than self-serve

Trusted domains are checked by Viably staff so a public mail provider such as gmail.com cannot be added by accident. There is no self-serve write path.

What keeps it safe

  • Only members of a channel can forward from it, and Viably never reads private channels it has not been added to.
  • Every forward is logged, so admins can audit who sent what and where.
  • Images are uploaded to private storage and referenced through signed URLs that expire, while the email itself carries a permanent inline copy.
  • Disable the power entirely from Powers → Email if you want to switch it off temporarily.

Common questions

What teams ask before they turn this on.

Why not just copy and paste the thread?

A pasted thread loses the attachments, the ordering, and who said what, and it takes minutes each time. One reaction sends the whole thing formatted, from your workspace's branded sender address, so it reads like something your company sent.

Can I email anyone?

Only verified addresses. An admin adds the address, the recipient clicks a one-time link, and after that it is permanently available. This is what stops an internal thread reaching a typo like [email protected].

We forward to colleagues constantly. Is there a faster way?

Ask Viably to trust your company domain and every address ending in it is allowed without per-address verification. Trusted domains are reviewed by staff so public mail providers cannot be added by accident.

Does this connect to anything else in Viably?

Yes. The same verified addresses and trusted domains authorise copying somebody on a reply from the Contacts workspace, so configuring this once covers both.

Get started

Whitelist your first recipient from the Email power page, and forwarding a thread afterwards takes one reaction.

Add Viably to Slack