Draft the channels-and-access request
Drafts the concise message listing exactly what channels and access the advisor needs — Slack/Teams, shared calendar, email alias — scoped to communication scaffolding only, without over-asking.
In / outClient's communication stack + agreed async channel → draft access request message listing each item with brief rationale
You might say…
“A long access request list signals I'm going to be high-maintenance. This draft asks for exactly what I need and explains why each item earns its place.”
What it does
Given the client's stack (Slack/Teams, shared calendar, email alias) and the agreed async channel, drafts the concise request listing exactly what the advisor needs added to and why, scoped to communication scaffolding only. Used at kick-off to get the working relationship wired up without over-asking.
Trigger: Use at kick-off to get the working relationship wired up — before the first session, when the client is most motivated to action setup tasks.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation