Communication Channel Filters
Give each request type a channel with explicit expectations
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 95%
Communication Channel Filters replace a universal contact route with purpose-specific channels. Interview requests go to a publicist, speaking requests to a speaker representative, links to a channel that may be read but will probably not receive a reply, and academic matters to a protected academic address. Each channel explains what the sender should expect, including whether the message reaches the person directly. Strong warnings protect specialized addresses from unrelated outreach. If someone circumvents the published routes and reaches a personal channel, non-response becomes the default final filter, especially when the request is vague or difficult to act on. The system turns inbound communication from an unlimited conversation into a set of explicit interfaces.
Origin
Newport described these as communication channels, formerly called sender filters, and said he still relies on them to manage inbound requests.
Core principles
- 01There should be no unrestricted general-purpose access channel
- 02Different request types need different routes
- 03Every route should state whether a reply is likely
- 04Non-response can be a final filter for vague or unsuitable requests
How to run it
- 1
Classify inbound requests
Identify recurring categories such as interviews, speaking, links, academic questions, or client matters. Separate categories whose handling or owner differs.
Pro tip Review recent inbound messages to find the real categories.
Watch out Do not create a category for every rare edge case.
- 2
Assign destinations
Give each category a specific address, form, representative, or document. Remove the assumption that one inbox handles everything.
Pro tip Delegate categories that do not need your judgement.
Watch out A published personal address undermines the routing system.
- 3
Publish expectations
Explain whether a request will be read, answered, delegated, or ignored. Make prohibited uses of protected channels explicit.
Pro tip State likely response behavior before the sender submits.
Watch out Ambiguous expectations create follow-up messages.
- 4
Apply the final filter
When an unknown sender bypasses the system with an unclear or unsuitable request, default to no response. Let a better-framed request or another route become their next move.
Pro tip Reserve responses for messages that are easy to understand and act on.
Watch out Do not confuse email non-response with ignoring someone speaking to you in person.
In the wild
A visitor with a speaking invitation is directed to the speaking representative rather than to Newport's personal or academic inbox. The route makes the responsible owner and likely next step clear.
→ The request is handled without creating a general-purpose access path to Newport.
Common mistakes
Keeping a universal inbox
A general-purpose route makes every category compete for the same attention and encourages senders to expect direct access.
Hiding response expectations
If senders do not know whether a message will be read or answered, they are more likely to follow up or try another route.
Is it for you?
Best for
People with high inbound volume and clearly separable categories of requests.
Not ideal for
Small, close-knit teams where one shared channel already has low volume and clear norms.
From the transcript
“there is no here is the general way to talk to Cal Newport”
“I have very specific channels for specific reasons with clear expectations”
“if I don't know how to respond to this easily I'm probably just not going to respond to it”
From the episode
#722: Cal Newport — How to Embrace Slow Productivity, Build a Deep Life, Achieve Mastery, and Defend Your Time
Cal Newport