Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Nothing matches. Clear the search to see every guide in this list.
Guides · 34
- Should a team share one RelayLink account?
- Catching up the person who missed standup
- Swapping a shift without the group chat
- Asking a peer to cover on-call
- Documenting a meeting you skipped
- A weekly status that actually asks for a decision
- Asking a skip-level to unblock a vendor
- Making a decision for someone who is on leave
- Asking a former colleague for a warm intro
- A recruiter note that closes the loop
- Handing a bug from support to engineering
- Asking a staff engineer to challenge an estimate
- Writing to a contractor on your team
- The standup that should have been a briefing
- Asking IT for access, with the context they actually need
- Telling a vendor PM that the integration slipped
- Helping an intern choose a project
- Asking an executive for a yes or no
- A PM and engineering cut decision
- Asking a designer for a review
- Escalating from success to the account executive
- Telling sales that engineering slipped
- Asking finance to approve a purchase
- Asking legal to review a clause
- Sending a hiring-loop debrief to your partner
- Asking another team to review an RFC
- Telling a peer you will miss a deadline
- Asking HR a policy question
- The on-call handoff as a briefing
- A skip-level question that does not ask for a meeting
- Handing a brief to a teammate who uses a different AI
- Writing to a report in another timezone
- Asking your manager for a scope cut
- Setting team norms for AI-drafted communication