Managing Inbound Requests
How to gracefully handle a high volume of intro requests.
The Triage System
When you achieve a certain level of visibility, your inbox becomes a public commons. Managing this without burning relationships requires a systematic approach rather than ad-hoc replies.
The Wrong Way
- Replying "I'll see what I can do" and forgetting.
- Blindly forwarding requests without context.
- Ignoring them completely (damages long-term reputation).
The Protocol Way
- Mandate a forwardable blurb for every ask.
- Batch process intro requests on Friday afternoons.
- Use explicit double opt-in for 100% of outbound forwards.
Volume vs. Capacity Matrix
| Requester Tier | Default Action | SLA |
|---|---|---|
| Tier 1 (Close network, High trust) | Immediate double opt-in request to target | 24 hours |
| Tier 2 (Acquaintances, Vendors) | Request forwardable blurb (creates friction) | 72 hours |
| Tier 3 (Cold outbound) | Polite decline template or ignore | None |
FAQ
Should I use an EA for this? Only if they strictly follow the double opt-in protocol. Assistants who aggressively push for meetings often burn the principal's social capital.
Internal Links: Double Opt-in Standard, Inbound Filter Tool, Homepage, Writing Forwardable Emails, Pricing, All Guides, All Tools, Cost of Context Switching, Sender Reputation, Network Maintenance, ROI Calculator, Network Value, Template Generator, Spam Checker, Time Zone Tool, Follow-up Cadence, Relationship Scorer, Security Policy, Terms of Service, Privacy Policy.