Skip to content
RelayLink
How it works Features Pricing Security Docs Learn
Sign in Get started
How it works Features Pricing Security Questions Docs Learn
Get started Sign in

Guides and explainers

Learn

How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.

All guides

Nothing matches. Clear the search to see every guide in this list.

Essays · 20

  • Keeping the session off the record 3 min
  • The cost of an unlabeled assumption 3 min
  • When not to CC the whole team 3 min
  • Why consent beats a shared inbox 3 min
  • Writing so their assistant cannot invent your ask 3 min
  • Separating facts from a guess 3 min
  • Why the TL;DR is not the note 3 min
  • What to do when you are the cold reader 3 min
  • Writing for someone who reads on Monday 3 min
  • Keeping private notes off the briefing 3 min
  • When you need who said what 3 min
  • Why a Slack thread loses the ask 3 min
  • Handing context to whoever wasn't in the room 3 min
  • Stopping an assistant from sending as you 3 min
  • When you use different assistants 3 min
  • When the other person has no AI 3 min
  • Asking without sounding like a bot 3 min
  • Writing across companies with no shared Slack 3 min
  • Why forwarding the chat fails at work 3 min
  • When your two assistants disagree 3 min
RelayLink

Conversations for the AI era. Keep your ideas and decisions together, and continue the work with the AI you choose.

Product

How it works Pricing Security Questions

Features

Cross-AI memory Handoffs Working with people Decision log Follow-ups Who wrote what All features

Resources

Docs Learn Support Connect an assistant

Account

Sign in Get started

Legal

Privacy policy Terms of service All policies

Your session never leaves. Only the briefing you approve does.

© 2026 PillarStack LLC. RelayLink is a service of PillarStack LLC, Richmond, Virginia.