How to Use Shared Conversations, Private Notes, and Mentions Strategically in Polymail

Michael Becker

One of my favorite ways to use Polymail is to privately comment on emails and tag my team members for visibility. Polymail gives you three ways to share information inside email threads:

  1. Private Notes
  2. @Mentions (team plans)
  3. Shared Conversation Links

Each serves a different purpose.

The “mistake” most people who don’t use Polymail make is using forward, CC, or BCC to include their team on emails. That creates inbox clutter, context overload, and unnecessary exposure.

This guide breaks down when to:

  • Leave a private note
  • Tag a teammate
  • Forward a thread
  • CC or BCC someone
  • Share a "PLY" link to the entire chain

Feature Breakdown

1. Private Notes

Available to all users. You can leave internal commentary on any email without the recipient seeing it.

Important behavior:

  • Private notes only attach to the specific email you comment on.
  • They do not expose the entire thread.
  • They do not send anything to the external recipient.

This is internal context only.

2. @Mentions (Premium Plans)

Available on Premium plans. If you have a colleague or small team, you can tag them directly inside a private note.

Important behavior:

  • The tagged teammate sees only the specific email you referenced.
  • They do not automatically gain visibility into the entire thread.
  • No external exposure.

This is great for targeted internal alignment.

3. Shared Conversation Links (What I call "PLY" Links)

You can generate a secure PLY link to share:

  • A single email
  • An entire thread

That link can be shared with teammates as well (but not others outside your organization). It opens in a browser view (so there's no email forwarding required to share a thread with someone).

This reduces inbox clutter and expands how email integrates with other systems (e.g., you can drop the link on Slack, inside your project management tool, on a Zoom or Google Meet, in an email, or even in another Polymail private note).

Strategic Decision Logic

Okay, let’s get into use cases and when to use each tool.

When to Use Private Notes

Use private notes when:

  • You want to preserve inbox space.
  • You want to leave commentary without escalating.
  • You want to document internal thinking.
  • The teammate does not need the full thread.
  • When no action is required.

Examples:

FYI visibility: “Interesting objection from client. Worth noting.”

Perspective tagging: “Good example of how they frame pricing pressure.”

Internal reaction: “Flagging this tone shift.”

This is lightweight alignment. Think: commentary, not coordination.

When to Use @Mentions

Use @mentions when:

  • You need a specific teammate’s attention.
  • You want internal alignment before replying.
  • You want input without exposing the full thread.
  • You want to preserve privacy of earlier emails.

Example 1: You receive a pricing objection. You tag your co-founder: “@Alex thoughts on offering phased rollout?”

Example 2: A client makes a technical request. You tag your product lead: “@Sarah is this feasible?”

The external thread remains untouched. Internal discussion happens in context.

This prevents:

  • Accidental reply-alls
  • Premature exposure
  • Inbox overload

When to Forward an Email

Forward an email only when:

  • The teammate needs the entire historical thread.
  • They will become directly involved.
  • They need searchable inbox access.
  • They require full context for execution.

Forwarding = permanent inbox inclusion. Use it when someone is entering the project meaningfully.

As a general rule, do not forward for casual visibility.

When to CC Someone

You should only CC when:

  • They are an active participant.
  • You want them “in the room.”
  • Their voice is required publicly.
  • They may need to reply directly.

CC brings someone into the conversation visibly. This signals shared ownership. Use it intentionally.

When to BCC Someone

BCC when:

  • You want them to observe.
  • They do not need to participate.
  • You want real-time visibility without external signaling.

This is passive observation. It should be used sparingly.

When to Use a Shared Conversation (PLY Link)

Shared conversation links are powerful because they:

  • Eliminate forwarding
  • Reduce inbox clutter
  • Preserve clean inbox architecture
  • Allow cross-platform reference

Use a PLY link when:

  • You want to reference a thread – and this is pretty meta – in another Polymail note or email thread to a colleague.
  • You want to attach an email thread to Trello, Notion, or a CRM.
  • You want visibility without inbox duplication.
  • You want someone to view context without permanently storing it.

Example:

In Slack: “See client objection here: [PLY link]”

In Trello: Attach full thread to project card.

In leadership review: Drop PLY link into performance doc.

This turns email into a shareable system that can be leveraged across platforms.

Strategic Summary

Private Notes = lightweight internal commentary
@Mentions = targeted internal alignment
Forward = full thread inclusion
CC = visible participation
BCC = silent observation
PLY Link = shareable reference without inbox clutter

The strategy is about information containment and intentional exposure.

What to ask before sharing:

  • Does this person need the entire thread?
  • Do they need to act?
  • Should the external party see their involvement?
  • Is inbox duplication necessary?
  • Or is context-only visibility enough?

Most teams default to forward or CC. High-performing teams minimize noise and control visibility.

Practical Use Cases for Real Business Scenarios

1. Founder + Operator

Client pushes back on scope.

Instead of forwarding 12-email thread:

Leave a private note: “@Sam review scope pushback. Worth adjusting?”

Minimal noise. Clear decision.

2. Agency Owner

Client sends tone-heavy message.

You leave a private note: “Flagging this tone shift. Let’s adjust approach. Will discuss on next week’s team sync call.”

No inbox clutter. Context preserved.

3. Consultant Working Across Tools

You copy a PLY link into Notion under “Client Alpha.”

Now your CRM and your inbox stay aligned.

4. Sales Team

AE gets stakeholder pushback.

Instead of CC’ing product lead publicly:

Use @mention first. Align internally, then respond externally.

This prevents confusion and protects authority.

The Core Principle

Shared Conversations and Private Notes are not convenience features. They are information control tools.

They allow you to:

  • Reduce inbox noise
  • Protect thread privacy
  • Coordinate internally
  • Integrate email into broader systems
  • Control exposure deliberately

For our team, together, this set of features drastically reduces the amount of back-and-forth normally required in Slack or typical project management tools. And it ensures there's never a "missed ball."

When your coworkers are all properly aligned on when, where, and how to use these features, in particular, a beautiful synergy is unlocked and internal communication becomes streamlined in a way you never realized was possible... all from the inbox.

If you’d like to implement this internal coordination model inside your own workflow, you can test Shared Conversations, @Mentions, and Private Notes in Polymail here: https://ply.to/VFG3W9

Subscribe to Polymail Blog

Get our updates in your inbox.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.